Page History

...

Open Issues

Anchor
OpenIssues OpenIssues

1. Choosing to NOT allowing single DC to be managed by multiple cloudstack deployments. Name space collision issues within DC will be resolved by this.
2. Sharing of resources with other entity (cloudstack or non-cloudstack entity)
3. DC release criteria from association with zone - deletion of last host or last cluster?

1. NA

Impact on other areas/features

...

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 the field 'cloud'.'cluster'.'name' in database to reflect new DC name in cluster name.
      5. Edit the field 'cloud'.'cluster_details'.'url' in database to reflect new DC name in cluster name.
      6. 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

Documentation notes

1. Sharing of resources (datastores, virtual switches like vDS, N1kv and ASA1kv etc.) with other entity (cloudstack or non-cloudstack entity) is not allowed.