Resource Placement and Validation Callout
The CloudCenter platform has the ability to deploy enterprise applications over public, private, or hybrid clouds by configuring user-specified cloud settings in the CCM UI > Environments > Edit Deployment Environment > Define Default Cloud Settings page.
The following integration features extend the CloudCenter platform capabilities:
Resource Placement allows users to define cloud settings based on third-party infrastructure tools or quota management tools using automated scripts instead of manually-selected settings.
Resource Validation blocks new deployments if users reach a configured threshold limit when using Cloud Resources (for example, restricting VMs being launched only if cloud resources consume < 75% of your maximum capacity).
You can configure these integrations using an automation callout script.
Resource Placement Flow
To use the resource placement script, specify a URL to the script that you want to run. The resource placement script runs inside a Docker container on the CCO. You cannot pass in any custom values. Your script must output the values specified in this section.
The Resource Placement feature is only supported for AWS, VMware, and OpenStack clouds.
This script is executed for each Node launch (called for each VM). For example, if you have a single-tier application with the minimum number of nodes set to 2, then this script is executed twice – 1 tier x 2 nodes = 2 executions. However, the CloudCenter platform passes variables such as service types which allows you to decide where to place it in the VM.
Toggle the switch to YES in the Resource Placement section, as shown in the following screenshot.
If this feature is enabled, the Cloud Settings form in the Deployment Environments > Cloud Defaults page will be disabled.
Identify the script location and the specific script for the Resource Placement Configuration. Based on the cloud account details received through the environment variables, the script can query the target cloud and return the cloud settings to be used for a deployment.
The following table describes available (input) environment variables for the Resource Placement script.
Environment Variable Description Cloud
The tier name.
All clouds, except Container Clouds and Cisco UCSD.
The Instance Type of the tier.
The image Name (for example: CentOS 6.x).
The service name to identify settings like private subnet for a database service.
The unique Job Name for the deployment.
The cloud account ID.
The cloud account password (for AWS, access key).
The cloud account username (for AWS, account email ID).
The cloud family of the region in the %wm.
The AWS account secret key
The SDK URL for VMware.
The default OpenStack domain ID.
The OpenStack Keystone authentication endpoint.
The OpenStack default tenant name.
The OpenStack default domain name.
The OpenStack password.
The OpenStack region.
The OpenStack user name for this account.
The OpenStack default tenant ID.
The cloud settings listed in the following tables are returned for AWS, OpenStack, and VMware.
- AWS Options
The following table describes AWS-specific cloud settings for the resource placement callout script.
AWS Setting Description
The VPC for the node to be deployed.
The subnet where the node should be deployed in the above VPC.
The security groups where the node should be associated in the above VPC.
The AWS tags to associate with the node.
Identifies if the node should be assigned with a public IP.
Customizable node Information detail that is displayed in the %wm UI Job Details Page for each node. If not provided, the %wm generates the default nodeInfo based on the provided values.
- OpenStack Options
The following table describes OpenStack-specific cloud settings for the resource placement callout script.
OpenStack Setting Description
The name of OpenStack tenant.
The availability zone as described in Availability Sets and Zones > OpenStack.
The OpenStack network interface information.
The private IP allocation strategy (DHCP or PREALLOCATE_IP).
The OpenStack Network ID.
A flag to allocate the public IP address (Boolean: true/false).
Customizable node Information detail that is displayed in the %wm UI Job Details Page for each node. If not provided, the %wm generates the default nodeInfo.
- vCenter Options
The following table describes vCenter-specific cloud settings for the resource placement callout script:
VMware Setting Description
The AWS tags to associate with the node.
The datacenter to deploy the node.
The cluster to deploy the node in the above datacenter.
The resource pool used to deploy the node.
The datastore cluster or datastore associated with the node. Datastore can be specified here, only if the datastore is not part of any datastore cluster.
Specific datastore within the datastore cluster associated with the node. If this value is populated, it is mandatory to specify the datastore cluster that the datastore belongs to, in UserDatastoreCluster.
The user folder used for the node deployment.
The value set to enable or disable the storage DRS.
Identifies if the root disk is resizable (Boolean: true/false).
The Root Disk setting is available as a separate field and you can only select the Root Disk size if the Cloning Mode is set to Full Clone (Enable Full Clone = Selected). See VMware Network Settings for additional context.
Identifies if the node to be launched is with full clone (Boolean: true/false).
The folder from which the template is selected.
The list of networks to attach to the node. The following table describes the format that various network types require. See vCenter Configurations > Resource Placement for additional context.
DVS and ACI networks
The ESX host to which the node is launched.
DisableStorageDRS If you enable the Disable storage DRS for this virtual machine flag in the script, the values for the following variables are returned: UserDataCenterName, UserClusterName, and UserDatastoreCluster. Note that the UserDatastoreCluster value must be set to the exact datastore used from a DRS-enabled DS cluster, for example, datastore-151.
- vCenter Media Related Attributes
You can specify media attributes for deployed VMs in vCenter for the following applications:
1. Single Root I/O Virtualization (SR-IOV)
2. PCI passthrough
3. Shared PCI passthrough(vGPU)
4. Available USB license dongles
5. CPU pinning(CPU affinity)
The following are sample callout scripts.
Container-Specific Resource Placement
A placement group represents a container pod and a tier in the application profile. A placement group is represented by a rectangle that you add to the topology modeler canvas by clicking the Create A Group button as indicated in the following screenshot. This support is available for some services like Apache, Nginx, MongoDB, and MySQL.
You can only drag and drop supported containers into the Create a Group rectangle.
Click and drag container-based services from the services palate on the left side of the topology modeler tab to the placement group rectangle, similar to the Apache2 profile and MongoDB profile that are visible in the canvas displayed in the following screenshot.
The properties panel on the right displays the properties for the currently selected object, which in this case is the last container dragged into the placement group, MongoDB. Notice that the minimum and maximum replicas fields in the General Settings section are not available, and the Network Services and Firewall Rules sections are also not available for this container. This is because these parameters are properties of the tier/pod. To see these parameters, click on the border of the placement group to select the placement group as a whole.
After selecting the placement group, notice the following in the Properties panel:
The name of the placement group contains the name of the first container dragged to the group (but you can edit this field).
Expanding the sections for Network Services and then Firewall Rules reveals that these sections automatically contain the union of the corresponding network services and firewall rules of the constituent containers.
The sections for Volumes, Deployment Parameters, and Minimum Resource Specifications are gone as these are specific to each container in the pod.
When deploying an application with a container tier that contains multiple containers, each container is listed within the corresponding per tier section on Page 1 of the deploy form.
If the container has visible parameters (defined in the application profile), an expand triangular icon appears to the left of the container name. Click on the expand icon to expand that section and display the deployment parameters.
On Page 2 of the deploy form, you have the option to specify the instance type for each container separately.
After the application successfully deploys, the individual containers within each replica of the pod are shown in the deployment Details page as described in the Deployment Details section.
The following screenshot is an example of a Kubernetes console.
In the above screenshot:
The Port Name in the in the CloudCenter variable syntax (displayed in the following screenshot of the CCM UI Properties pane) is the <service_name> in the Kubernetes console.
The string displayed in the Kubernetes console as http-668-335a5a is the longer unique name created by the CCO and passed to Kubernetes when the app is launched.
See CloudCenter-Defined Parameters > for additional context.
See Container Service for service-specific details.