InlineServiceDeployment1
{
"clustered_deployment_count": 0,
"deployed_to": [
{
"is_valid": false,
"target_display_name": "string",
"target_id": "string",
"target_type": "string"
}
],
"deployment_mode": "string",
"deployment_spec_name": "string",
"deployment_type": "string",
"instance_deployment_template": "DeploymentTemplate Object",
"perimeter": "string",
"service_deployment_config": "ServiceDeploymentConfig Object",
"service_id": "string"
}
Number of instances in case of clustered deployment.
List of resource references where service instance be deployed. Ex. Tier 0 Logical Router in case of N-S ServiceInsertion. Service Attachment in case of E-W ServiceInsertion.
Mode of deployment. Currently, only stand alone deployment is supported. It is a single VM deployed through this deployment spec. In future, HA configurations will be supported here.
Name of the deployment spec to be used for deployment, which specifies the OVF provided by the partner and the form factor.
Specifies whether the service VM should be deployed on each host such that it provides partner service locally on the host, or whether the service VMs can be deployed as a cluster. If deployment_type is CLUSTERED, then the clustered_deployment_count should be provided.
Deployment Template holds the attributes specific to partner for which the service is created. These attributes are opaque to NSX.
This indicates the deployment perimeter, such as a VC cluster or a host.
The Deployment Config contains settings that are applied during install time.
The Service to which the service deployment is associated.