Page History

...

1. Migration support
   1. Existing CloudStack Deployments - Existing cloudstack deployments with clusters from multiple DCs/vCenters require consolidation of clusters into single DC.
   2. Following are options multiple DC's in a zone
   3. Decide a DC as the final DC that contains all clusters.
   4. Move all clusters to the chosen DC.
   5. For each cluster create cluster with same name in target DC.
   6. Edit the field 'cloud'.'cluster'.'name' in database to reflect new DC name in cluster name.
   7. Edit the field 'cloud'.'cluster_details'.'url' in database to reflect new DC name in cluster name.
   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.
   8. Pre-requisite checker tool - This tool should go through existing CloudStack deployment and VMware deployment to check if pre-requisites prerequisites are met. Following are list of pre-requisites before going to prerequisites would be convered during upgrade to new version of product with this feature built-in,
      1. A CloudStack zone should encompass only 1 VMware DC
      2. The VMware DC encompassed by CloudStack zone should not be shared by multiple CloudStack deployments.
2. Guidelines of CloudStack version upgrade
   1. Migration would be offline operation before CloudStack version upgrade operation.
3. Prerequisite checker tool would be run as part of CloudStack upgrade
   1. Choice of migration procedure is option (2) - migration of host across DC by disconnecting from cluster in source DC, followed by connecting it to target cluster in another DC. Following are detailed steps,
      1. Handle the case of clusters from multiple vCenter
         1. Investigation pendingTo be investigated.
      2. Handle the case of clusters from single vCenter but different DCs
         1. Handle the case of deployment using distributed virtual switch (Nexus 1000v or vDS)
            1. Deploy Nexus 1000v or vDS on target DC with same credentials (user/password)
            2. Ensure if 'cloud'.'virtual_supervisor_module' table has the new IP of Nexus 1000v VSM instance.
            3. Create all dvPortgroups required by VMs on the host that is moving across DCs. Make sure all properties of dvPortGroups are in sync, e.g. shaping policy should be same as that of original dvPortGroup in source DC. External switch configuration for trunking/routes is assumed to be taken care of by admin.
      3. Decide a DC as the final DC that contains all clusters.
      4. Create a cluster, in target DC, with same properties as that of original cluster
      5. Unmanage the cluster in CloudStack
      6. Disconnect each host in source cluster
      7. Remove each host from source cluster
      8. Add each host to target cluster
      9. Create all custom properties
         1. Each VM will have custom properties like cloud.nic.mask. This will be lost during above migration operations. Hence need to re-create after adding to target cluster
         2. Each template (user VM and system VM templates) will have custom properties like cloud.uuid. This need to be restored.
      10. Add the target cluster to CloudStack
      11. Make sure that guid field of 'cloud'.'host' table has the valid reference because when host is added to target cluster, it will acquire new unique reference.
      12. Investigation pending for migration of primary/secondary datastore across DCs.
   2. Pre-requisite checker should run successfully before CloudStack upgrade operation.
   3. 1. Make sure the field 'cloud'.'cluster'.'name' in database reflect new DC name in cluster name.
      2. Make sure the field 'cloud'.'cluster_details'.'url' in database reflect new DC name in cluster name
      Run CloudStack version upgrade to complete the upgrade
      1. .

Assumptions

1. Sharing of resources (datastores, virtual switches like vDS, N1kv and ASA1kv etc.) with other entity (cloudstack or non-cloudstack entity) is not allowed.
2. Cloudstack zone doesn't contain multiple hypervisors. A cloudstack zone will have only 1 hypervisor.

...

1. Mapping of Nexus VSM instance with zone
   1. Bring in new APIs to support associate / dis-associate a Nexus VSM instance with a zone
   2. While adding a cluster, let user choose which Nexus VSM to be used for virtual network orchestration. Actually Nexus VSM doesn't care about the cluster but it manages host. So to make the operation valid, it required (a pre-requisite) that all hosts in a cluster should be part of single Nexus VSM instance.
   3. Allow multiple Nexus VSM instances to be associated with single cloudstack zone.
   4. Architecture
      1. While adding a cluster, if N1kv instance is specified, update table cloud.virtual_supervisor_module and cloud.zone_vsm_map to assocaite N1kv VSM instance with zone
      2. Allow multiple N1kv VSM instances to be added to zone.
      3. Avoid cascaded removal of VSM instance upon cluster deletion as the association is now at zone level.
      4. Change cleanup code of N1kv VSM instances as cleanup should happen automatically with zone removal instead of cluster removal earlier.
         1. Constraint checks
         2. Only N1kv VSM of the associated DC can be added to a zone.
         3. N1kv's vCenter server connection's properties would need to be checked to retrieve the association of N1kv with a vCenter and a DC. Compare the retrieved vCenter IP and DC name with vCenter IP and DC name of current zone
   5. DB changes
      1. 'cloud'.'cluster_vsm_map' would be removed.
      2. 'cloud'.'zone_vsm_map' would be added. Also a zone can be associated with more than 1 VSM instances.
      3. Columns in this table are id, zone_id & vsm_id where id is Primary key of this table.
      4. Foreign key vsm_id from virtual_supervisor_module table.
      5. Implement Dao & VO classes for this table.
   6. Zone level Cisco ASA 1000v instance.
   7. CloudStack should be able to add/manage following DC level resources in scope of zone.
      1. Distributed virtual switches for zone wide virtual networks.
         1. Nexus 1000v DVS
         2. VMware DVS - this is already realized by zone wide traffic labels.
   8. UI Flow
      1. Support add/removal of Nexus 1000v device to a zone
      2. Support add/removal of ASA 1000v to a zone.
   9. Track relationship between resources (DC <->
   DVS
   1. vDS <> N1kv <-> ASA etc.) in cloudstack database. Use custom property over vDS to ensure it's associated with single CloudStack deployment.