Multi-Site, Multi-Account Deployment Considerations

Be aware that multi-site, multi-account deployments are NOT supported in the following scenarios:

  1. When you migrate or promote deployments. See Deployment, VM, and Container States for additional context.

  2. For single-tier application (for example, interactive applications).

  3. When you use the Benchmark an Application feature.

Multi-Site (Multi-Tier) Cloud Configuration

You can configure a multi-site deployment to enable users to deploy N-Tier applications with each tier being configure in a different cloud or in the same cloud in different segmented networks while ensuring SLA guaranty and data sovereignty. This feature allows you to use different clouds for different tiers.

While the multi-site feature is supported for all supported clouds (see What Is Supported? for a complete list), the Set Defaults functionality is only supported for AWS, OpenStack, and vCenter clouds.

For example, in a 2-Tier application, the load balancer and app cluster can be in AWS or any other public cloud offering and the database can be in the private datacenter like VMware with/without ACI Extensions. This example is also applicable in cases where the two different datacenters (regions) of an enterprise is maintained as two different cloud families and the user wants the different tiers in the application to be deployed to these two datacenters or clouds.

If a deployment environment has more than one cloud selected in the Deployment page, you see a new option in the Cloud dropdown list called Hybrid. When you select this option, you can choose different instance types and provide Advanced cloud/network settings specific to the selected cloud for each tier. The following screenshot shows an example.


Multi-Account Cloud Configuration

You can also configure each application tier to be deployed in different cloud accounts (multi-account) within the same datacenter. The Hybrid option allows you to choose the same cloud and different cloud accounts for each tier.

For example, a datacenter admin maintains a single cloud (for example, VMware) for the entire datacenter but maintains different cloud accounts for different segments that are managed by different Cisco Application Policy Infrastructure Controllers (APICs). In this case, each tier for this application can be deployed to these different segments. The database can be deployed to the pod or segment that has stricter security policies enforced by APIC1 and the AppCluster tier can go into different pod that is managed by a different APIC2.

  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks