> On April 10, 2013, 7:42 a.m., Sateesh Chodapuneedi wrote: > > Section 8.3.7.5 Removing Nexus Virtual Switch is specifying steps to delete > > VMware dvSwitch. This is not correct. There is no notion of deletion of > > VMware dvSwitch (please refer to FS for the feature) in CloudStack. Please > > remove section completely. > > In page 109, replace 'configuring' by 'orchestration of in the line > > "CloudStack supports configuring virtual networks in a deployment with...." > > In page 110, against the table entry "vCenter Host" - description should be > > vCenter host/ip. Presence of Nexus virtual switch is irrelevant for the > > vCenter here. > > In page 110, against the table entry "Guest Traffic vSwitch Name" - > > description 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" > > In page 109, use Distributed Virtual Switch instead of "Virtual Distributed > > Switch" > > In page 109, instead of 'Nexus 1000v Virtual Switch' better to write 'Nexus > > 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 > > datacenter that is containing cluster being managed by cloudstack. > > > > > > Radhika PC wrote: > Is pre-provisioning the dvSwitch in the datacenter is the only > prerequisite? 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/creating/modifying dvPortGroup similar to deleting dvSwitch ? Could > you please clarify.
FS states: Deployment requirements (fresh install vs. upgrade) if any VMware dvSwitch must be already created/configured in the vCenter datacenter deployment (understood!) 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. - 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 Tomechak, > 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 > necessary 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 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. > > > Thanks, > > Radhika PC > >
