Page History

...

1. addCluster will be modified
   1. Interface perspective - Make parameters vCenter host/ip, credentials and DC name optional based on zone id's presence in zone_dc_map.
2. associateZoneWithDc -
   1. Maps a cloudstack zone with specified VMware DC.
   2. Throws RemoteException if vCenter is not reachable or any other server side Exception caught.
   3. Upon failure in successful parameter validation throw InvalidParameterValueException
   4. Parameters are,
      1. zoneId - required
      2. dcName - required
      3. vCenterHost - required
      4. vCenterUser - required
      5. vCenterPassword - required
3. disAssocaiteZoneWithDc -
   1. Unmaps a cloudstack zone from a VMWare DC that is associated with it earlier.
   2. If no association exists already, then throw CloudRuntimeException.
   3. If no such zone exists, throw InvalidParameterValueException
   4. If zone is have one or more clusters / elements, then throw ResourceInUseException - Zone should be empty (no clusters or other elements like Nexus 1000v VSM instance)
   5. Parameter are,
      1. zoneId - required
4. disassociateZoneWithDc

UI Flow

• Changes required in UI for live migrating a volume from one storage pool to another.
  1. Add Cluster form in zone wizard
  2. Add Cluster wizard
  3. Add NexusVSM instance to zone
  4. Add ASA instance to zone

...

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. Options to migrate VM across datacenters
         1. Cold migrate each of the instance to this new cluster in chosen DC.
         2. Hot migrate the VMs by using disconnecting all hosts from source cluster followed by deletion of source cluster from source DC and adding all hosts to cluster in target DC.
         3. Hot migrate the VMs after suspending the VMs. Need to power on (mean resume) VMs after migration is complete. This needs the virtual disks of VM to be placed on shared storage before triggering the migration operation.
   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 Disconnect each host, in that cluster, in maintenance modeRemove each host in maintenance mode from the clusterfrom source cluster.
      4. Remove cluster from source DC
      5. Add each host to new cluster in target DCGet 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.