I double checked: if vmware.use.dvswitch=true, irrespective of the global parameter settings (T/F) for Nexus, the UI lists all the switches for the vSwitch Type options.
My observation: If vmware.use.dvswitch=false, vmware.use.nexus.dvswitch=true, the UI shows only the option for Nexus dvSwitch. There is no option to set the Traffic Label at the Cluster-level. If vmware.use.dvswitch=true, vmware.use.nexus.dvswitch=false, the UI lists all the switch types of Switch Type. There is an option to set the Traffic Label at the Cluster-level. If vmware.use.dvswitch=true, vmware.use.nexus.dvswitch=true, then all fine :-) You can specify traffic at cluster-level, and all Nexus dvSwitch options (IP address of VMS component, dvSwitch credentials) are displayed. -----Original Message----- From: Radhika Puthiyetath [mailto:radhika.puthiyet...@citrix.com] Sent: Wednesday, March 13, 2013 2:26 PM To: cloudstack-dev@incubator.apache.org Subject: RE: question on Distributed Virtual Switch support Thanks Sailaja. If I do not have any plans to use Nexus, I might not set the vmware.use.nexus.dvswitch flag to true. If I do not want Nexus, why do I need to set the Traffic Label name for Nexus ? I have to worry only about the Switch I want in my setup. -----Original Message----- From: Sailaja Mada [mailto:sailaja.m...@citrix.com] Sent: Wednesday, March 13, 2013 2:17 PM To: cloudstack-dev@incubator.apache.org Subject: RE: question on Distributed Virtual Switch support Hi Radhika, I guess you are talking about the options "Override Public-Traffic:" - Y/N or "Override Guest-Traffic" : Y/N. These are basically to provide the traffic label name . Ex: Port profile in case of Nexus . If you do not set these options by default it would take vswitch0 as the traffic label name. As per FS, we get to see Nexus in the vSwitch Type dropdown list only when the global config "vmware.use.nexus.dvswitch" to true. [Reference: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Integration+of+CloudStack+with+VMware+DVS ] Comment from FS : Default option - if "vmware.use.nexus.dvswitch" is true then use "Cisco Nexus 1000v Distributed Virtual Switch". Otherwise use "VMware vNetwork Distributed Virtual Switch" Pranav, Can you please comment if this is not the case? Thanks, Sailaja.M -----Original Message----- From: Radhika Puthiyetath [mailto:radhika.puthiyet...@citrix.com] Sent: Wednesday, March 13, 2013 1:56 PM To: cloudstack-dev@incubator.apache.org Subject: RE: question on Distributed Virtual Switch support Thanks Sailaja. Even If vmware.use.nexus.vswitch=false (and vmware.use.dvswitch=true), the UI still shows the Nexus dvSwitch in the drop-down list for switch type. I thought in this case, UI should display only VMware dvSwitch because the parameters for Nexus/Standard switches are not enabled in the global parameter page. Is there any reason for displaying Nexus dvSwitch options if vmware.use.nexus.vswitch=false ? (In this case, if you select Nexus dvSwitch, the UI does not display the options for specifying the IP address of VMS component and dvSwitch credentials. That is the reason I confused initially!) -----Original Message----- From: Sailaja Mada [mailto:sailaja.m...@citrix.com] Sent: Wednesday, March 13, 2013 1:25 PM To: cloudstack-dev@incubator.apache.org Subject: RE: question on Distributed Virtual Switch support Hi Radhika, You need to set global config parameters "vmware.use.nexus.vswitch" & "vmware.use.dvswitch" to true to get Nexus UI options at cluster level. Thanks, Sailaja.M -----Original Message----- From: Radhika Puthiyetath [mailto:radhika.puthiyet...@citrix.com] Sent: Wednesday, March 13, 2013 12:19 PM To: cloudstack-dev@incubator.apache.org Subject: RE: question on Distributed Virtual Switch support Hello, One question about the Nexus virtual switch configuration. What is the impact of the change in the configuration flow (after introducing VMware VDS) on Nexus configuration? As per the UI, we are no longer required to specify the IP address of the VSM component of Nexus 1000v virtual switch. I am attaching the screen captures before and after introducing the VMware VDS. My question is (might be a stupid one!) whether Nexus vSwitch is going to work without specifying the IP address of VMS component, dvSwitch credentials etc.? Or am I missing something ? Thanks -Radhika -----Original Message----- From: Musayev, Ilya [mailto:imusa...@webmd.net] Sent: Monday, March 11, 2013 9:05 PM To: cloudstack-dev@incubator.apache.org; fgaudrea...@cloudops.com Subject: RE: question on Distributed Virtual Switch support Francois, Good observation, I was only referencing 1GB networks. With 10GB or more, you should have no issues. Regards ilya > -----Original Message----- > From: Francois Gaudreault [mailto:fgaudrea...@cloudops.com] > Sent: Monday, March 11, 2013 10:47 AM > To: cloudstack-dev@incubator.apache.org > Subject: Re: question on Distributed Virtual Switch support > > On 2013-03-08 10:26 PM, Musayev, Ilya wrote: > > There maybe customers who only have 2NICs on their servers and it > > that > case - if they use DVS, they wont be able to use CS. Also, for most > proof of concept work of CS, people tend to use basic gear with 2 NICs > in LAB, they won't be able to test CS if they used DVS on everything > including management net. > This is a weird assumption... I am not sure using only 2 NICs is a bad design. > Maybe in the 1gbps world, but definitely not in the 10gbps world, and > people are starting to embrace the 10gigE a lot. So my opinion, you > should allow people to use only 2 interfaces, and 1 dVS with CS. > > -- > Francois Gaudreault > Architecte de Solution Cloud | Cloud Solutions Architect > fgaudrea...@cloudops.com > 514-629-6775 > - - - > CloudOps > 420 rue Guy > Montréal QC H3J 1S6 > www.cloudops.com > @CloudOps_ >
