[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900744#comment-14900744
 ] 

Suresh Kumar Anaparti commented on CLOUDSTACK-7151:
---------------------------------------------------

Design change required for existing VMware cluster level traffic override 
settings to support multiple physical networks defined in the zone for guest 
and public traffic types at zone and cluster level(when defined) without 
impacting existing cluster level override settings. FS/Design details:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Support+multiple+physical+networks+at+cluster+level+for+guest+traffic+over+VMware+deployments

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. 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.


> vmware: Type of vSwitch was not detected correctly while preparing 
> public/guest virtual networks
> ------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7151
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7151
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: VMware
>    Affects Versions: 4.3.0, 4.3.1
>         Environment: VMware ESXi 5.0
> ACS 4.3.0
>            Reporter: Sateesh Chodapuneedi
>            Assignee: Suresh Kumar Anaparti
>
> After upgrade to 4.3.0 from 4.2.0 system vms are not able to start.
> 2014-07-18 07:14:16,732 INFO [c.c.h.v.r.VmwareResource] 
> (DirectAgent-348:ctx-7cf2f084 brvmc01-host01-vmw.vcore.host.net) Prepare 
> network on vmwaresvs Public_Guest_Net with name prefix: cloud.public
>  2014-07-18 07:14:16,778 ERROR [c.c.h.v.m.HypervisorHostHelper] 
> (DirectAgent-348:ctx-7cf2f084 brvmc01-host01-vmw.vcore.host.net) Unable to 
> find vSwitchPublic_Guest_Net
>  2014-07-18 07:14:16,778 WARN [c.c.h.v.r.VmwareResource] 
> (DirectAgent-348:ctx-7cf2f084 brvmc01-host01-vmw.vcore.host.net) StartCommand 
> failed due to Exception: java.lang.Exception
>  Message: Unable to find vSwitchPublic_Guest_Net



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to