Sateesh Chodapuneedi 319a7bf05c CLOUDSTACK-4408 [Upgrade 3.0.7 to 4.2] Zone with clusters of multiple hypervisors including VMware should be processed for legacy zone. ... Currently zones with multiple clusters from more than 1 hypervisor including VMware, are being ignored while processing them during upgrade. If a zone has all non-VMware clusters then ignoring the zone is correct. But if a zone has atleast 1 VMware cluster then make sure the zone processed further to mark it as legacy or associate the zone with appropriate VMware DC. Signed-off-by: Sateesh Chodapuneedi <sateesh@apache.org>		2013-08-20 10:31:35 +05:30
..
api	CLOUDSTACK-4288: Fix the way that VmwareClient is using vSphere 5.1 SDK which caused huge memory footprint	2013-08-14 15:00:07 -07:00
components-api	Removing ^M's from code.	2013-04-04 00:53:20 +05:30
compute	CLOUDSTACK-1317: Bump CloudStack package version to 4.2.0-SNAPSHOT in all poms	2013-02-20 16:42:56 +05:30
network	CLOUDSTACK-1317: Bump CloudStack package version to 4.2.0-SNAPSHOT in all poms	2013-02-20 16:42:56 +05:30
orchestration	CLOUDSTACK-3886: check in for review request https://reviews.apache.org/r/13008/	2013-08-07 10:29:18 -07:00
planning/src/org/apache/cloudstack/platform/planning	Added engine	2012-11-05 09:14:14 -08:00
schema	CLOUDSTACK-4408 [Upgrade 3.0.7 to 4.2] Zone with clusters of multiple hypervisors including VMware should be processed for legacy zone.	2013-08-20 10:31:35 +05:30
service	CLOUDSTACK-1317: Bump CloudStack package version to 4.2.0-SNAPSHOT in all poms	2013-02-20 16:42:56 +05:30
storage	CLOUDSTACK-4395:[Object_store_refactor] Default template is not	2013-08-19 17:32:44 -07:00
pom.xml	integration test is passed again	2013-05-12 14:41:06 -07:00