cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Radhika Puthiyetath <>
Subject RE: question on Distributed Virtual Switch support
Date Wed, 13 Mar 2013 06:48:37 GMT

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 ?


-----Original Message-----
From: Musayev, Ilya [] 
Sent: Monday, March 11, 2013 9:05 PM
Subject: RE: question on Distributed Virtual Switch support


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


> -----Original Message-----
> From: Francois Gaudreault []
> Sent: Monday, March 11, 2013 10:47 AM
> To:
> 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 
> 514-629-6775
> - - -
> CloudOps
> 420 rue Guy
> Montréal QC  H3J 1S6
> @CloudOps_

  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message