Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of sailaja.mada@citrix.com
 designates 203.166.19.134 as permitted sender)
From: Sailaja Mada <sailaja.mada@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Wed, 13 Mar 2013 14:16:47 +0530
Subject: RE: question on Distributed Virtual Switch support
Thread-Topic: question on Distributed Virtual Switch support
Thread-Index: 
 Ac4cYZRz5Iwz59nTm0yLlgVo/8mFcwAAuNKAAARYhoYAhLl0AAAGxOggAERM70AAAp4asAABAQ+AAABukpA=
Message-ID: 
 <4FCA39B99132DA4EA70BE3CE408C193D0119F25DB263@BANPMAILBOX01.citrite.net>
References: 
 <8dfef2aaxuu0jq2u1p9j6hvl.1362790864946@email.android.com>,<6E004C34C1C59E45A35B4338808BC3150131E74F5A7B@SJCPMAILBOX01.citrite.net>
 <381ghabiskbqvb3cby9dd94i.1362799565240@email.android.com>
 <513DEE48.307@cloudops.com>
 <D2EE6B3265AD864EB3EA4F5C670D256F3593E6@EXMBX01L-CRP-03.webmdhealth.net>
 <97F4356AEA71904482CD192135C038F9011CC2AD005B@BANPMAILBOX01.citrite.net>
 <4FCA39B99132DA4EA70BE3CE408C193D0119F25DB250@BANPMAILBOX01.citrite.net>
 <97F4356AEA71904482CD192135C038F9011CC2AD0082@BANPMAILBOX01.citrite.net>
In-Reply-To: 
 <97F4356AEA71904482CD192135C038F9011CC2AD0082@BANPMAILBOX01.citrite.net>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi Radhika,

I guess you are talking about the options "Override Public-Traffic:"  - Y/N=
  or "Override Guest-Traffic" : Y/N. =20

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

As per FS,  we get to see Nexus in the vSwitch Type  dropdown list only whe=
n 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 "VMw=
are vNetwork Distributed Virtual Switch"=20

Pranav,

Can you please comment if this is not the case?=20

Thanks,
Sailaja.M

-----Original Message-----
From: Radhika Puthiyetath [mailto:radhika.puthiyetath@citrix.com]=20
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=3Dfalse (and vmware.use.dvswitch=3Dtrue), =
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 th=
e  parameters for Nexus/Standard switches are not enabled in the global par=
ameter page.

Is there any reason for displaying Nexus dvSwitch options if vmware.use.nex=
us.vswitch=3Dfalse ?=20

(In this case, if you select Nexus dvSwitch, the UI does not display the op=
tions for specifying the IP address of VMS component and dvSwitch credentia=
ls. That is the reason I confused initially!)


-----Original Message-----
From: Sailaja Mada [mailto:sailaja.mada@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" & "vmw=
are.use.dvswitch"  to true to get Nexus UI options at cluster level.

Thanks,
Sailaja.M

-----Original Message-----
From: Radhika Puthiyetath [mailto:radhika.puthiyetath@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 impa=
ct of the change in the configuration flow (after introducing VMware VDS) o=
n 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 crede=
ntials etc.?

Or am I missing something ?

Thanks
-Radhika

-----Original Message-----
From: Musayev, Ilya [mailto:imusayev@webmd.net]
Sent: Monday, March 11, 2013 9:05 PM
To: cloudstack-dev@incubator.apache.org; fgaudreault@cloudops.com
Subject: RE: question on Distributed Virtual Switch support

Francois,

Good observation, I was only referencing 1GB networks. With 10GB or more, y=
ou should have no issues.

Regards
ilya

> -----Original Message-----
> From: Francois Gaudreault [mailto:fgaudreault@cloudops.com]
> Sent: Monday, March 11, 2013 10:47 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: question on Distributed Virtual Switch support
>=20
> On 2013-03-08 10:26 PM, Musayev, Ilya wrote:
> > There maybe customers who only have 2NICs on their servers and it=20
> > that
> case - if they use DVS, they wont be able to use CS. Also, for most=20
> proof of concept work of CS, people tend to use basic gear with 2 NICs=20
> in LAB, they won't be able to test CS if they used DVS on everything=20
> including management net.
> This is a weird assumption... I am not sure using only 2 NICs is a bad de=
sign.
> Maybe in the 1gbps world, but definitely not in the 10gbps world, and=20
> people are starting to embrace the 10gigE a lot. So my opinion, you=20
> should allow people to use only 2 interfaces, and 1 dVS with CS.
>=20
> --
> Francois Gaudreault
> Architecte de Solution Cloud | Cloud Solutions Architect=20
> fgaudreault@cloudops.com
> 514-629-6775
> - - -
> CloudOps
> 420 rue Guy
> Montr=E9al QC  H3J 1S6
> www.cloudops.com
> @CloudOps_
>=20