Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Content-Type: multipart/alternative;
 boundary="===============2581702084412887977=="
MIME-Version: 1.0
Subject: Re: Review Request: Documentation changes for VMware dvSwitch and
 Nexus
 dvSwitch
From: "Radhika PC" <radhika.puthiyetath@citrix.com>
To: "David Nalley" <david@gnsa.us>,
 "Jessica Tomechak" <jessica.tomechak@gmail.com>,
 "Sateesh Chodapuneedi" <sateesh.chodapuneedi@citrix.com>,
 "ilya musayev" <ilya@cloudsand.com>,
 "Chip Childers" <chipchilders@apache.org>,
 "Pranav Saxena" <pranav.saxena@citrix.com>
Cc: "cloudstack" <cloudstack-dev@incubator.apache.org>,
 "Radhika PC" <radhika.puthiyetath@citrix.com>
Date: Wed, 10 Apr 2013 16:30:08 -0000
Message-ID: <20130410163008.13837.73294@reviews.apache.org>
Auto-Submitted: auto-generated
Sender: "Radhika PC" <noreply@reviews.apache.org>
References: <20130410074237.13808.26791@reviews.apache.org>
In-Reply-To: <20130410074237.13808.26791@reviews.apache.org>
Reply-To: "Radhika PC" <radhika.puthiyetath@citrix.com>

--===============2581702084412887977==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable


> On April 10, 2013, 7:42 a.m., Sateesh Chodapuneedi wrote:
> > Section 8.3.7.5 Removing Nexus Virtual Switch is specifying steps to de=
lete VMware dvSwitch. This is not correct. There is no notion of deletion o=
f VMware dvSwitch (please refer to FS for the feature) in CloudStack. Pleas=
e remove section completely.
> > In page 109,  replace 'configuring' by 'orchestration of in the line "C=
loudStack supports configuring virtual networks in a deployment with...."
> > In page 110, against the table entry "vCenter Host" - description shoul=
d be vCenter host/ip. Presence of Nexus virtual switch is irrelevant for th=
e vCenter here.
> > In page 110, against the table entry "Guest Traffic vSwitch Name" - des=
cription should be "Name of virtual switch to be used for guest traffic"
> > In page 110, against the table entry "Public Traffic vSwitch Name" - de=
scription should be "Name of virtual switch to be used for public traffic"
> > In page 109, use Distributed Virtual Switch instead of "Virtual Distrib=
uted Switch"
> > In page 109, instead of 'Nexus 1000v Virtual Switch' better to write 'N=
exus 1000v Distributed Virtual Switch'
> > Add cluster parameters documented in page 62, is fine, reviewed.
> > As mentioned in FS, pre-requisites is to pre-provision dvSwitch in data=
center that is containing cluster being managed by cloudstack.
> > =

> >
> =

> Radhika PC wrote:
>     Is pre-provisioning the dvSwitch in the datacenter is the only prereq=
uisite? do we have to note down any parameters, that could be later used in=
 CloudStack ? Please confirm.
> =

> Radhika PC wrote:
>     The FS listed the following:
>     =

>     CloudStack does following,
>     Create dvPortGroup over designated dvSwitch - How ? =

>     Modify dvPortGroup over designated dvSwitch -How?
>     Delete dvPortGroup over designated dvSwitch - How ? Is deleting/creat=
ing/modifying dvPortGroup similar to deleting dvSwitch ? Could you please c=
larify.
> =

> Radhika PC wrote:
>     FS states:
>     =

>     Deployment requirements (fresh install vs. upgrade) if any
>     =

>     VMware dvSwitch must be already created/configured in the vCenter dat=
acenter deployment (understood!)
>     =

>     All the host/cluster resources should be added to dvSwitch before add=
ing the cluster to CloudStack's pod cluster. (it is not clear this step nee=
d to be done on vCenter or CloudStack). It is very difficult to document su=
ch a complex feature without a setup.
> =

> Radhika PC wrote:
>     FS states:
>     =

>     Explain performance & scalability implications when feature is used f=
rom small scale to large scale
>     In case of vSphere 4.1 dvPortGroup need to be created with specific n=
umber of dvPorts. In large scale deployment optimum use of dvPorts may not =
be possible due to this pre-allocation. In case of vSphere 5.0 the autoexpa=
nd feature helps in auto increment of number of dvPorts. (what is the speci=
fic number here ?)
>     =

>     Network switches (including the vSwitch in ESXi host) keep a distinct=
 forwarding table for each VLAN; this could lead to an increased overhead i=
n packet forwarding when a considerable number of isolated networks, each o=
ne with a significant number of virtual machines, is configured in a data c=
enter. (Is this a limitation? should it be mentioned?) please clarify
> =

> Radhika PC wrote:
>     The comments states:
>     =

>     In page 110, against the table entry "Guest Traffic vSwitch Name" - d=
escription should be "Name of virtual switch to be used for guest traffic"
>     In page 110, against the table entry "Public Traffic vSwitch Name" - =
description should be "Name of virtual switch to be used for public traffic"
>     =

>     Question: From where do you pick up/ specify a name for the traffic ?=
 Is this something that we get from vCenter setup ? Or are we saying to men=
tion what type of switch to be used ?

Comment states:

In page 109, use Distributed Virtual Switch instead of "Virtual Distributed=
 Switch"

But in VMware terms it is "VMware vSphere Distributed Switch (VDS)" see  se=
e http://blogs.vmware.com/vsphere/tag/distributed-switch

Shouldn't be we following similar terminology ?


- Radhika


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/10366/#review18935
-----------------------------------------------------------


On April 10, 2013, 7:05 a.m., Radhika PC wrote:
> =

> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10366/
> -----------------------------------------------------------
> =

> (Updated April 10, 2013, 7:05 a.m.)
> =

> =

> Review request for cloudstack, David Nalley, Chip Childers, Jessica Tomec=
hak, Pranav Saxena, Sateesh Chodapuneedi, and ilya musayev.
> =

> =

> Description
> -------
> =

> Documentation on Distributed Switches: nexus and dvSwitch.
> Prerequisites part of VMware dvSwitch is still unclear. Please provide ne=
cessary suggestions.
> =

> =

> This addresses bug CLOUDSTACK-772.
> =

> =

> Diffs
> -----
> =

>   docs/en-US/Book_Info.xml c125ab8 =

>   docs/en-US/add-clusters-vsphere.xml 6b2dff2 =

>   docs/en-US/images/add-cluster.png 383f375ebedd62d9b294a56f777ed4b8c0d92=
e10 =

>   docs/en-US/images/dvswitch-config.png PRE-CREATION =

>   docs/en-US/images/dvswitchconfig.png PRE-CREATION =

>   docs/en-US/vmware-cluster-config-dvswitch.xml PRE-CREATION =

>   docs/en-US/vmware-install.xml 467e135 =

> =

> Diff: https://reviews.apache.org/r/10366/diff/
> =

> =

> Testing
> -------
> =

> Publican builds, patch applies.
> =

> =

> Thanks,
> =

> Radhika PC
> =

>


--===============2581702084412887977==--