cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chip Childers" <chipchild...@apache.org>
Subject Re: Review Request 10366: Documentation changes for VMware dvSwitch and Nexus dvSwitch
Date Mon, 08 Jul 2013 20:59:20 GMT


> On June 17, 2013, 1:07 p.m., Chip Childers wrote:
> > Radhika,
> > 
> > Was this committed?  If so, can you please close this review?  If not, what's needed
to help get it done?
> 
> Radhika PC wrote:
>     Hi Chip, 
>     
>     There are many question unanswered. You can check the comments section of this review
request.
>     
>     I shall work with the QA point of contact for 4.2 release, then close this item.
> 
> Sateesh Chodapuneedi wrote:
>     Radhika,
>     I did answer as many questions as I could on 18th April.
>     Since then I have been waiting for feedback over the answers provided to following
questions. Please do provide inputs.
>     
>     Sateesh Chodapuneedi 2 months, 1 week ago (April 18, 2013, 5:52 p.m.)
>     
>         >do we have to note down any parameters, that could be later used in CloudStack
? Please confirm.
>     
>         User might want to specify name of dvSwitch in following places,
>         1) traffic label in physical network page of zone configuration wizard - This
setting dictates name of vSwitch/dvSwitch to be used for virtual network orchestration later.
>         2) public/guest virtual switch na,e - This setting overrides the vSwitch/dvSwitch
name in zone level configuration setting for traffic label. See (1) above.
>     
>         >Is deleting/creating/modifying dvPortGroup similar to deleting dvSwitch ?
Could you please clarify.
>         No.
>     
>         >All the host/cluster resources should be added to dvSwitch before adding
the cluster to CloudStack's pod cluster. (it is not clear this step need to be done on vCenter
or CloudStack). It is very difficult to document such a complex feature without a setup.
>     
>         This step is to be done on vCenter. Its part of dvSwitch deployment & out
of CloudStack's scope.
>         Complete documentation of feature like this should be done after with a setup.
Otherwise, first draft can be made with content from FS & improve the document once setup
is available or handover the documentation task to interested people with setup. Content in
FS is good enough to start with because FS contains all key details which are implemented
in the feature.
>     
>         >(what is the specific number here ?)
>     
>         It's fixed number of dvports which is any where from 1 to maximum number of dvports
allowed by a dvportgroup.
>     
>         >(Is this a limitation? should it be mentioned?) 
>     
>         No.
>     
>         >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 mention what type of switch
to be used ?
>     
>         Its name of dvSwitch. Can be observed in vCenter setup.
>         Yes, good to follow terminology from http://blogs.vmware.com/vsphere/tag/distributed-switch
>

Hi Radhika!

Do Sateesh's comments help clarify enough to get this documentation completed now?


- Chip


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


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, Chip Childers, Jessica Tomechak, David Nalley, Pranav
Saxena, Sateesh Chodapuneedi, and ilya musayev.
> 
> 
> Bugs: CLOUDSTACK-772
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> -------
> 
> Documentation on Distributed Switches: nexus and dvSwitch.
> Prerequisites part of VMware dvSwitch is still unclear. Please provide necessary suggestions.
> 
> 
> Diffs
> -----
> 
>   docs/en-US/Book_Info.xml c125ab8 
>   docs/en-US/add-clusters-vsphere.xml 6b2dff2 
>   docs/en-US/images/add-cluster.png 383f375ebedd62d9b294a56f777ed4b8c0d92e10 
>   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.
> 
> 
> File Attachments
> ----------------
> 
> section 8.3.7. Configuring a vSphere Cluster with VMware Distributed Virtual Switch (page
110)
>   https://reviews.apache.org/media/uploaded/files/2013/04/10/Apache_CloudStack-4.1-Installation_Guide-en-US.pdf
> 
> 
> Thanks,
> 
> Radhika PC
> 
>


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