ACI Multi-Site Extensions
Workload Manager supports integration with the Cisco ACI Multi-Site endpoint through the definition of a ACI Multi-Site extensions. These extensions may be created and viewed from the Workload Manager Extensions page. Once an extension is created and validated, it can be referenced in the Deployment Environment form in the Cloud Settings subsection for a vCenter region or in a network mapping for a vCenter region. Once the extension is referenced in a deployment environment, when the user deploys an application to that environment using the one of the vCenter regions where the Multi-Site endpoint is deployed, the ACI Multi-Site related cloud settings are applied to the deployment at deploy time. Depending on how the the environment is set up, the user may be able to see and modify the cloud settings at deploy time. Workload Manager leverages Cloud Remote when connecting to an Multi-Site endpoint that is not directly accessible to the CloudCenter Suite cluster.
The integration allows the Workload Manager user to specify the following ACI resources during a deployment:
Application Network Profiles (ANP)
Endpoint Groups (EPG)
Be aware of the following requirements to use Multi-Site extensions:
ACI Multi-Site Requirements
ACI Multi-Site 2.0(2c) and 2.1(1i).
All of the sites configures within ACI Multi-Site must adhere to the APIC requirements specified in the ACI Extensions section.
Workload Manager Requirements:
If Multi-Site endpoint not directly accessible form CloudCenter Suite cluster you must use the cloud region that has the applicable Cloud Remote configured.
vCenter Requirements: The following table describes the VMware vCenter requirements.
Requirement Details A working VMware vCenter 5.0/5.5/6.0 environment
The minimum VMware vSphere version is v5.0, but vSphere v5.5 U2 is optimal.
Workload Manager automates the provisioning of virtual machines into the VMware private datacenter. Workload Manager requires access credentials to the vCenter setup. All ESX host(s) must be physically connected to the ACI leaf switches. The prerequisite installation requirements for the datacenter are:
- A physical ESX host capable of running at least 10 medium sized instances
- An ESX cluster (cluster could comprise of just the one host)
- A datastore (or datastore cluster for DRS support), at least 100gb of free space
If the ESXi hosts are Cisco UCS based
- The VLANs for the CMM must be mapped to the vNIC template.
- The uplinks from the Fabric must interconnect trunking VLANs to the leaf switches.
The Extensions page can be reached directly from the Admin menu. This is where you can see all existing ACI, ACI Multi-Site, and ServiceNow extensions that were created by you or shared with you. From here you can perform actions on an existing extension, depending on your permissions, and also create new extensions. A screenshot of the Extensions page which includes ACI Multi-Site extensions is shown below.
The following table summarizes the actions that can be performed from the Extensions page:
|View or edit an extension||Click on a corresponding grow in the list of extensions||The extension edit form is similar to the extension creation form.|
|Create a new extension||Click the Add Extension button in the upper right of the screen||See Create an ACI Multi-Site Extension section below for more details|
|Share an extension||Click in the Actions column for the appropriate row and select Share||See Permission Control > Extension Permissions|
|Delete an extension||Click in the Actions column for the appropriate row and select Delete|
if an ACI Multi-Site extension is referenced in a deployment environment or deployment, it cannot be deleted.
|Re-enable an extension||Click in the Actions column for the appropriate row and select Re-enable||This action is only available for extensions where the Blade Status is Blade Failure. This causes the pod associated with the failed blade to be regenerated.|
The Blade Status column on the Extensions page applies to ACI Multi-Site extensions only. Possible values for Blade Status are summarized in the following table:
|Blade Failure||The pod required to support the extension was not successfully launched|
|Endpoint Inaccessible||The Multi-Site API endpoint could not be accessed|
|Invalid Credentials||The Multi-Site API endpoint could be accessed but the user credentials could not be validated|
|Success||The Multi-Site credentials were accepted and connection established|
Create an ACI Multi-Site Extension
To create a new ACI Multi-Site extension, follow this procedure.
From the Extensions page, click Add Extension in the upper right. The New Extension page displays, as shown in the following screenshot.
- Enter an extension name and select ACI Multi-Site from the dropdown menu. This causes the rest of the form to update and display the ACI Multi-Site specific fields as show in the following screenshot.
Enter the following required fields:
Multi-Site endpoint URL
Multi-Site endpoint user name and password
The Domain ID field is always prepopulated with the domain ID of the default local domain. Update this field if you want to use the domain ID of another domain defined in the Multi-Site endpoint.
If the Multi-Site endpoint endpoint is directly accessible to the Workload Manager cluster, click Save to save the configuration. This also causes Workload Manager to connect with the Multi-Site endpoint and login using the provided credentials. The status of the connection attempt is displayed in the Blade Status column of the Extensions page. Once the connection is successful, a success message is briefly displayed at the top of the Extensions page.
If the Multi-Site endpoint is not directly accessible to the Workload Manager cluster, set the Multi-Site Endpoint Directly Accessible toggle to No. This causes the a new dropdown field, VMware cloud region, to be displayed as shown in the the following screenshot.
Select the vCenter region where the Multi-Site endpoint is hosted, then click Save. This causes Workload Manager to connect with the Multi-Site endpoint through the Cloud Remote appliance in that region.
After clicking Save, the Extensions page refreshes to display the newly added extension appears at the top of the list of extensions.
Referencing an Extension in a Deployment Environment
An ACI Multi-Site extension can only be used when it is referenced in an deployment environment containing a vCenter region hosting the Multi-Site endpoint referenced in the extension. To do this, create a deployment environment as instructed in Deployment Environments > Add a Deployment Environment, with the following extra steps:
From the General Settings tab, make sure you select the vCenter region that is hosting the Multi-Site controller referenced in your extension.
From the Cloud Settings tab, either create a new network mapping, or specify the cloud settings for the vCenter region hosting the Multi-Site endpoint. In either case, specify the data center from the dropdown field and all subsequent deployment resources as you would with any other vCenter region.
If you have read access to at least one ACI or ACI Multi-Site extension, just above the per NIC settings will be a Use Extension toggle which if Off by default. Turn this toggle On.
When you turn on the Use Extension toggle, the display updates with a new section added under the toggle with new extension related fields as shown in the following screenshot.
Click the ACI Multi-Site tab.
Clicking the ACI Multi-Site tab displays the ACI Multi-Site related fields as shown in the following screenshot.
Select the ACI Multi-Site extension you want to use from the first dropdown field. This causes the list of Multi-Site sites associated with the Multi-Site controller to be available in the Multi-Site site dropdown.
Select the Multi-Site from the dropdown field. This causes the list of Virtual Machine Managers associated with the Multi-Site to be available in the Virtual Machine Manager dropdown.
Select the Virtual Machine Manager from the dropdown field. This causes the list of Multi-Site tenants associated with the Virtual Machine Manager to be available in the Multi-Site Tenant dropdown.
Select the Multi-Site Tenant from the dropdown field. This causes the list of L3 Out values associated with the Multi-Site tenant to be available in the L3 Out dropdown.
Select the L3 Out value from the dropdown.
Scroll down to the per NIC settings. When an ACI Multi-Site extension is associated with the region, a tabbed header appears above the NIC settings as shown in the following screenshot.
Select the Cisco ACI Multi-Site tab.
Selecting the ACI Multi-Site tab causes the Network dropdown to be replaced with the EPG Type dropdown as shown in the following screenshot
You can set the EPG Type dropdown to Existing EPG or New EPG.
If you select Exiting EPG, an Existing EPG dropdown field is displayed as shown in the following screenshot.
Select an existing EPG from the dropdown. You are done configuring this NIC.
If you select New EPG for the EGP Type, the Bridge Domain and Contracts dropdown fields are displayed as shown in the following screenshot.
Select a Bridge Domain, and from the Contracts dropdown, select one or more contracts.
Add and configure additional NICs if required.
If you set the cliqrIgnoreAppFailure parameter (see Troubleshooting Parameters), then the APIC resources (ANP, EPGs, Contracts, and so forth) created using the Workload Manager are not removed if the deployment fails. The launched VMs and related APIC policies are only removed when the user terminates the deployment from the Deployments page. See Terminate Protection for additional context.
- No labels