Submit Job (v2)
|API Details||Release-Specific Information|
|CloudCenter Platform 4x||CloudCenter Suite 5x|
|Name||Submit job (Asynchronous API)|
Submit job-related information for each resource
Modified in CloudCenter Suite 5.0.0
|Back To Links||CloudCenter Platform 4x API||Workload Manager API|
See the Enterprise Service Bus (ESB) section for additional context.
Sample 1 – Governance Mode OFF
1a. Request Body: Batch – AWS
1b. Request Body: NTier – Openstack
1c. Request Body: Multi-Site, NTier – AWS
1d. Request Body: Multi Account Deployments - NTier (AWS)
Example 2 –Governance Mode ON
curl -k -X POST -H "Accept: application/json" -H 'Content-Type: application/json' -u cloudcenteradmin:40E45DBE57E35ECB "https://<HOST>:<PORT>/
Example 3 –
Request Payload: AWS
The availability set is specified as a list of subnet IDs (comma separated) in the first NIC ID of the job submit request payload. See Availability Sets and Zones for additional context.
Example 3.1: Using DHCP allocation mode
Example 3.2: Using Static IP allocation mode
Example 3.3: Using Multiple NICs
AWS support multiple NICs across subnets in the same availability zone
Request Body: OpenStack
The availability set is part of cloud properties of the job payload request. Provide the OpenStack zone information as comma separated zoneIds with name as availabilitySet in the cloud properties. See Availability Sets and Zones for additional context.
Request Body: Azure
Provide the availability set as a boolean flag value in the cloud properties of the job submit payload request. Use the provisionInAvailabilitySet=true setting in the cloud properties to enable Azure's availability set.
Request Body: Google Cloud Platform
The zone is part of cloud properties of the job payload request. Provide the Google Cloud Platfrom zone information as comma separated zoneIds with name as LaunchZone in the cloud properties. See Availability Sets and Zones for additional context.
Example 4 –Node IDs in the Payload
Effective CloudCenter 4.8.0, the Submit Job API is modified to optionally accept nodeIds as input for each tier. In case of a scaled job, provide a list of node IDs for a particular tier. See the Migrating Deployments Use Case for additional details.
Example 5 –OpenStack Resource Placement in the Payload
Request Body (OpenStack)
Example 6 – Sample Kubernetes Payload
Request Body (Container Cloud)