Page History

...

1. addCluster will be modified
   1. Interface perspective - Make Remove parameters vCenter host/ip, username, credentials password and DC name optional based on zone id's presence in zone_dc_map.
   2. Only required parameter is cluster name.
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

...

• Changes required in UI for live migrating a volume from one storage pool to another.
  1. Associate zone with DC
  2. Dis-associate zone with DC
  3. Support adding zone level entities (NexusVSM etc.) to zone.
  4. Add Cluster form in zone wizard
  5. Add Cluster wizard
  6. Add NexusVSM instance to zone
  7. Add ASA instance to zone

Open Issues

Anchor
OpenIssues OpenIssues

1. Need to find migration procedure of choose among the options available for migration (Options are listed in Upgrade section below) to upgrade existing cloudstack deployment with multiple DC's without downtime of VMs.
2. Whether To go for enhancement of impacted features (Nexus 1000v VSM & ASA1kv instance support). Earlier Nexus 1000v VSM instance is associated with cluster in 1:1 fashion. With new mapping model Nexus 1000v VSM instance can be associated with zone in 1(zone):N(Nexus 1000v VSM). This also opens up the chance to have multiple Nexus VSM instances in single cloudstack zone. Should this be supported as well?

Impact on other areas/features

...