Hi All, Currently, in cloudstack, the support for cluster level override settings (introduced in 4.2.0 with VMware DVS Integration) for guest and public traffic types blocks support for multiple physical networks defined in the zone for these traffic types over VMware deployments. It is required to support multiple physical networks defined in the zone for these traffic types at zone and cluster level(when defined) without impacting existing cluster level override settings. This would also fix the issue CLOUDSTACK-7151 - vmware: Type of vSwitch was not detected correctly while preparing public/guest virtual networks.
Also, renaming of vSwitch name for guest and public traffic type overridden at cluster in current cloudstack deployment has become troublesome, requiring manual update to database. This need to be addressed such that admin would be able to seamlessly re-name vSwitch name at cluster in Cloudstack whenever required, even in production cloud. There is a design change required for existing cluster level traffic override settings. I'm working on the implementaton. Please take a look at the FS/Design details @ "https://cwiki.apache.org/confluence/display/CLOUDSTACK/Support+multiple+physical+networks+at+cluster+level+for+guest+traffic+over+VMware+deployments"; and share your feedback. Thanks, Suresh
