cloudstack/engine
Sateesh Chodapuneedi a48e6685a1 CLOUDSTACK-4443 [VMWARE]Failed to deploy VM's on VMWARE Standard vSwitch Legacy Zone after upgrade
While upgrading to 4.2 to support existing clusters working over standard vswitch or nexus dvswitch should be supported as is. To ensure this while upgrading to 4.2, existing cluster's vswitch configuration needs to be persisted to database. If zone level traffic label is empty then default vswitch name would be used.

Signed-off-by: Sateesh Chodapuneedi <sateesh@apache.org>
(cherry picked from commit 808183fdcc)

Signed-off-by: animesh <animesh@apache.org>
2013-08-27 12:56:08 -07:00
..
api Updating pom.xml version numbers for release 4.2.0 2013-08-22 17:15:42 -07:00
components-api Updating pom.xml version numbers for release 4.2.0 2013-08-22 17:15:42 -07:00
compute Updating pom.xml version numbers for release 4.2.0 2013-08-22 17:15:42 -07:00
network Updating pom.xml version numbers for release 4.2.0 2013-08-22 17:15:42 -07:00
orchestration Updating pom.xml version numbers for release 4.2.0 2013-08-22 17:15:42 -07:00
planning/src/org/apache/cloudstack/platform/planning Added engine 2012-11-05 09:14:14 -08:00
schema CLOUDSTACK-4443 [VMWARE]Failed to deploy VM's on VMWARE Standard vSwitch Legacy Zone after upgrade 2013-08-27 12:56:08 -07:00
service Updating pom.xml version numbers for release 4.2.0 2013-08-22 17:15:42 -07:00
storage CLOUDSTACK-1191: Re-enable deployment of SystemVMs on RBD 2013-08-27 12:55:29 -07:00
pom.xml Updating pom.xml version numbers for release 4.2.0 2013-08-22 17:15:42 -07:00