Page History

...

In today's implementation, vSphere VMware DC is invisible to CloudStack, we allow multiple clusters (vSphere VMware DC) even from different vCenter instances to be added to CloudStack zone. This implies following,

1. Multiple vCenter instances can exist in same cloudstack zone.
2. Multiple DCs can exist in same cloudstack zone.
3. 1:1 mapping of N1kv VSM instance with cluster is enforced.
4. 1:1 mapping of ASA instance with cluster is enforced.
5. 1:1 mapping of cluster to vmware DC is recommended to support multiple cloudstack deployments in same DC.
6. vDS - zone wide traffic label override is required in case of a zone with multiple DCs.
7. A primary storage of the scope zone is not inherently possible because datastore is an object scoped at DC, if a zone contains more than 1 DC this is not supported.
8. Live migration of VM across clusters in a zone is not inherently possible if 2 clusters are in different DC's.

To address these issues, let Cloudstack should explicitly manage vSphere DCs. Treat CloudStack zone as capacity-planning and operating unit, in case of deployment with multiple DCs use multiple CloudStack zones configured per DC and share the same network infrastructure, they only need to carefully allocate IPs/VLANs etc. to multiple CloudStack zones to make it happen.

...

1. Migration support
   1. Existing CloudStack Deployments - Existing cloudstack deployments with multiple DC's in a zone
      1. Decide a DC as the final DC that contains all clusters.
      2. Move all clusters to the chosen DC.
      3. For each cluster create cluster with same name in target DC.
      4. Edit dc name to match that of chosen DC where ever the dc name is present (Ex: 'guid' field in hosts table)
      5. Cold migrate each of the instance to this new cluster in chosen DC.
   2. Fresh CloudStack Deployments - Existing VMware deployments with clusters to be managed by cloudstack spread in multiple DC's
      1. Move all clusters meant for single zone into 1 DC
      2. For each cluster create cluster with same name in target DC.
      3. Put each host, in that cluster, in maintenance mode
      4. Remove each host in maintenance mode from the cluster
      5. Add each host to new cluster in target DC
      6. Get the host out of maintenance mode