cloudstack/engine
Sateesh Chodapuneedi f8899f2d12 CLOUDSTACK-4294 After upgrade of CloudStack to 4.2, support old vswitch type in existing clusters if user changes the vswitch backend to another type of vSwitch
While upgrading to 4.2, the type of vswitch being used by each cluster is persisted to cluster_details table. This helps if user want to change the type of vswitch used in a zone or entire cloud later on but leave existing cluster continue to use old vswitches. Hence even after modifying the type of vswitch at cloud level (by modifying global configuration parameters) or modifying the type vswitch at zone level (by modifying the traffic label) would not disturb operation of existing clusters.

Signed-off-by: Sateesh Chodapuneedi <sateesh@apache.org>
2013-08-19 15:53:57 +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-4294 After upgrade of CloudStack to 4.2, support old vswitch type in existing clusters if user changes the vswitch backend to another type of vSwitch 2013-08-19 15:53:57 +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-4363: fix possible NPE, if copy volume failed. 2013-08-17 17:33:17 -07:00
pom.xml integration test is passed again 2013-05-12 14:41:06 -07:00