cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkata Siva Vijayendra Bhamidipati (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-3905) [VMWARE]Can not add Standard/DVSwitch when Nexus global config is set to true
Date Fri, 02 Aug 2013 21:45:49 GMT


Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-3905:

The usage of nexus 1000v and vmware dvs are each controlled by their global configuration
flags and vmware.use.dvswitch respectively. If one is set, the other
cannot be used. If both are set, it pretty much boils down to the code that checks for one
flag before the other.

Currently, the mgmt server doesn't have a way to specify mutual exclusivity between global
flags. Either we should put this in, or move these flags from a global config level to the
zone level, where explicit code checks can be put in to disallow both flags to be set.
> [VMWARE]Can not add Standard/DVSwitch when Nexus global config is set to true
> -----------------------------------------------------------------------------
>                 Key: CLOUDSTACK-3905
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Devices
>    Affects Versions: 4.2.0
>            Reporter: Sailaja Mada
>            Priority: Critical
>             Fix For: 4.2.0
> Steps:
> 1. Set below Global config parameters to true :
> vmware.use.dvswitch	Enable/Disable Nexus/Vmware dvSwitch in VMware environment	true	
>	Enable/Disable Cisco Nexus 1000v vSwitch in VMware environment
> 2. Tried to add Standard vSwitch/DVSwitch Cluster  :
> Observations:
> 1. Nexus 1000v Switch configuration details are mandatory to add cluster 
> 2. It will not let to add new cluster with DVS/Standard vSwitch. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message