InlineServiceInstance1

JSON Example

{
    "attachment_point": "string",
    "deployed_to": [
        {
            "is_valid": false,
            "target_display_name": "string",
            "target_id": "string",
            "target_type": "string"
        }
    ],
    "deployment_mode": "string",
    "deployment_spec_name": "string",
    "implementation_type": "string",
    "instance_deployment_config": "InstanceDeploymentConfig Object",
    "instance_deployment_template": "DeploymentTemplate Object",
    "service_deployment_id": "string"
}

string

attachment_point

Required

Attachment point to be used by this service instance for deploying the Service-VM.

Possible values are : TIER0_LR, TIER1_LR, SERVICE_PLANE, HOST,

array of ResourceReference

deployed_to

Required

Constraints: minItems: 1 maxItems: 128

List of resource references where service instance be deployed. Ex. Tier 0 Logical Router in case of N-S ServiceInsertion.

string

deployment_mode

Required

Constraints: default: ACTIVE_STANDBY

Deployment mode specifies where the partner appliance will be deployed in HA or non-HA i.e standalone mode.

Possible values are : STAND_ALONE, ACTIVE_STANDBY,

string

deployment_spec_name

Required

Name of the deployment spec to be used by this service instance.

string

implementation_type

Required

Implementation to be used by this service instance for deploying the Service-VM.

Possible values are : NORTH_SOUTH, EAST_WEST,

InstanceDeploymentConfig

instance_deployment_config

Optional

The Instance Deployment Config contains settings that is applied during install time.

DeploymentTemplate

instance_deployment_template

Required

Deployment Template holds the attributes specific to partner for which the service is created. These attributes are opaque to NSX.

string

service_deployment_id

Optional

Id of the Service Deployment using which the instances were deployed. Its available only for instances that were deployed using service deployment API.

Used By

ServiceInstance