Page History

...

1. Single DC will NOT be allowed to be managed by multiple cloudstack deployments. Name space collision issues within DC will be resolved by this.
2. Nexus support needs changes. 1 cluster to 1 Nexus mapping to be removed. Allow Nexus 1000v VSM instance to be added to zone/DC.
3. Impact of (1) this feature on ASA feature needs check.
4. Impact of this feature on refactoring in Vmsync.

...

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)the field 'cloud'.'cluster'.'name' in database to reflect new DC name in cluster name.
      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