Hi, I would like to propose a feature around VMware hypervisor support, to map CloudStack Zone with VMware DC in 1:1 fashion. Kindly go through the FS at [1] and let me know your comments.
With this feature, VMware datacenter will be put under management of CloudStack zone. In previous releases, VMware datacenter is hidden behind a CloudStack cluster, we need an explicit mapping policy for VMware datacenter both for zone-wide storage and zone-wide network resources. 1:1 relationship between VMware vSphere DC to CloudStack zone is a natural mapping from resource point of view, whether it's storage (datastore) or network (distributed switches etc.). Hence there is a need to move towards mapping a CloudStack zone with single VMware datacenter to enable consistency in zone wide features. In this explicit model, CloudStack will understand the relationship between a VMware datacenter and resources underneath it, so when resources like a VMware cluster is added to CloudStack, the underlying VMware resource relationship between these objects will become constraint information for CloudStack to use. For example, a VMware cluster can't be added to a CloudStack zone if it's DC is not under the CloudStack zone. The model itself will not limit how many VMware clusters/hosts that will be managed, as long as those cluster/host are within the same DC. Upgrade to new version (with this feature) does not enforce migration of existing CloudStack zones. This means that if an existing zone has clusters from multiple DCs/vCenters, it will be supported as-is. But zone wide features would not be supported on such zone. To quote some, zone wide primary storage, storage live migration across clusters in a zone which might be added to CloudStack in future. Regards, Sateesh [1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Mapping+model+for+CloudStack+zone+and+Vmware+datacenter
