Cloud.NSX.LoadBalancer
Request schema for provisioning Compute Load Balancer
{
"address": "string",
"constraints": [
{
"tag": "string"
}
],
"count": 0,
"gateway": "string",
"instances": [
"string"
],
"loggingLevel": "string",
"name": "string",
"network": "string",
"providerId": "string",
"resourceName": "string",
"routes": [
{
"algorithm": "string",
"algorithmParameters": "string",
"healthCheckConfiguration": {
"healthyThreshold": 0,
"httpMethod": "string",
"intervalSeconds": 0,
"passiveMonitor": false,
"port": "string",
"protocol": "string",
"requestBody": "string",
"responseBody": "string",
"timeoutSeconds": 0,
"unhealthyThreshold": 0,
"urlPath": "string"
},
"instancePort": "string",
"instanceProtocol": "string",
"persistenceConfig": {
"cookieGarble": false,
"cookieMode": "string",
"cookieName": "string",
"cookieSessionTime": "string",
"ipPurge": false,
"maxAge": 0,
"maxIdle": 0,
"type": "string"
},
"port": "string",
"protocol": "string"
}
],
"tags": [
{
"key": "string",
"value": "string"
}
],
"type": "string"
}
The DNS address of the load balancer.
Load balancer constraints
The number of resource instances to be created.
Gateway to use for creating Load Balancer service.
A list of machines, by ID, to add to the load balancer pool.
The load balancer logging level. The logging levels that you define for any load balancer component on the blueprint apply to all load balancers in the blueprint.The available logging level options are NONE, EMERGENCY, ALERT, CRITICAL, ERROR, WARNING, INFO, DEBUG or NOTICE.
NONE logging level in YAML maps to:
-NSX-V: "Logging Disabled": true and "Log Level": info
-NSXT-T: "Error Log Level": INFO
Load balancer machine name.
The network to attach to the load balancer.
A unique identifier of the resource in the context of the provider.
The actual name of the load balancer machine determined after the allocation.
Settings for incoming requests to reach the load balancer, for requests to be routed to machines in the pool, and for checking the health of machines in the pool.
Resource categorization, in case-sensitive key names, or in key-value pairs.
Load balancers are available in small, medium, and large sizes. Based on the load balancer size, the load balancer can host different virtual servers and pool members.
Translation from YAML to NSX-V endpoint:
-SMALL: compact
-MEDIUM: large
-LARGE: quad-large
-XLARGE: xlarge