cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From radh...@apache.org
Subject git commit: updated refs/heads/master to d36d709
Date Mon, 26 Aug 2013 11:18:20 GMT
Updated Branches:
  refs/heads/master eeac80eaa -> d36d7090b


CLOUDSTACK-772 dvSwitch comments


Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo
Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/d36d7090
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/d36d7090
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/d36d7090

Branch: refs/heads/master
Commit: d36d7090be9123ae28acb8fb6dba03d7049e459c
Parents: eeac80e
Author: radhikap <radhika.puthiyetath@citrix.com>
Authored: Mon Aug 26 16:47:55 2013 +0530
Committer: radhikap <radhika.puthiyetath@citrix.com>
Committed: Mon Aug 26 16:47:55 2013 +0530

----------------------------------------------------------------------
 docs/en-US/images/vds-name.png                | Bin 0 -> 64739 bytes
 docs/en-US/vmware-cluster-config-dvswitch.xml |  94 +++++++++------------
 docs/en-US/vmware-install.xml                 |   2 +-
 3 files changed, 43 insertions(+), 53 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/cloudstack/blob/d36d7090/docs/en-US/images/vds-name.png
----------------------------------------------------------------------
diff --git a/docs/en-US/images/vds-name.png b/docs/en-US/images/vds-name.png
new file mode 100644
index 0000000..bf5b4fc
Binary files /dev/null and b/docs/en-US/images/vds-name.png differ

http://git-wip-us.apache.org/repos/asf/cloudstack/blob/d36d7090/docs/en-US/vmware-cluster-config-dvswitch.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/vmware-cluster-config-dvswitch.xml b/docs/en-US/vmware-cluster-config-dvswitch.xml
index a3250f4..98bee0e 100644
--- a/docs/en-US/vmware-cluster-config-dvswitch.xml
+++ b/docs/en-US/vmware-cluster-config-dvswitch.xml
@@ -20,11 +20,11 @@
  under the License.
 -->
 <section id="vmware-cluster-config-dvswitch">
-  <title>Configuring a vSphere Cluster with VMware Distributed Virtual Switch</title>
-  <para>&PRODUCT; supports VMware vNetwork Distributed Switch (VDS) for virtual
network configuration
-    in a VMware vSphere environment. This section helps you configure VMware VDS in a &PRODUCT;
-    deployment. Each vCenter server instance can support up to 128 VDS instances and each
VDS
-    instance can manage up to 500 VMware hosts.</para>
+  <title>Configuring a VMware Datacenter with VMware Distributed Virtual Switch</title>
+  <para>&PRODUCT; supports VMware vNetwork Distributed Switch (VDS) for virtual
network
+    configuration in a VMware vSphere environment. This section helps you configure VMware
VDS in a
+    &PRODUCT; deployment. Each vCenter server instance can support up to 128 VDS instances
and each
+    VDS instance can manage up to 500 VMware hosts.</para>
   <section id="about-dvswitch">
     <title>About VMware Distributed Virtual Switch</title>
     <para>VMware VDS is an aggregation of host-level virtual switches on a VMware vCenter
server.
@@ -41,9 +41,7 @@
     <title>Prerequisites and Guidelines</title>
     <itemizedlist>
       <listitem>
-        <para>Do not attempt to configure VDS by altering VMware traffic label when
configuring
-          physical networks. This will only work for Standard Virtual Switch and should not
be
-          distributed.</para>
+        <para>VMware VDS is supported only on Public and Guest traffic in &PRODUCT;.</para>
       </listitem>
       <listitem>
         <para>VMware VDS does not support multiple VDS per traffic type. If a user
has many VDS
@@ -51,20 +49,47 @@
           traffic.</para>
       </listitem>
       <listitem>
+        <para>Additional switches of any type can be added for each cluster in the
same zone. While
+          adding the clusters with different switch type, traffic labels is overridden at
the
+          cluster level.</para>
+      </listitem>
+      <listitem>
         <para>Management and Storage network does not support VDS. Therefore, use Standard
Switch
           for these networks.</para>
       </listitem>
+      <listitem>
+        <para>When you remove a guest network, the corresponding dvportgroup will not
be removed on
+          the vCenter. You must manually delete them on the vCenter.</para>
+      </listitem>
     </itemizedlist>
   </section>
+  <section id="preconfig-checklist-vds">
+    <title>Preparation Checklist</title>
+    <para>For a smoother configuration of VMware VDS, note down the VDS name you have
added in the
+      datacenter before you start:</para>
+    <mediaobject>
+      <imageobject>
+        <imagedata fileref="./images/vds-name.png"/>
+      </imageobject>
+      <textobject>
+        <phrase>vds-name.png: Name of the dvSwitch as specified in the vCenter.</phrase>
+      </textobject>
+    </mediaobject>
+    <para>Use this VDS name when you specify the switch name in the traffic label while
creating the
+      zone. Traffic label format is [["Name of vSwitch/dvSwitch/EthernetPortProfile"][,"VLAN
+      ID"[,"vSwitch Type"]]]</para>
+  </section>
   <section id="enable-dvswitch">
     <title>Enabling Virtual Distributed Switch in &PRODUCT;</title>
     <para>To make a &PRODUCT; deployment VDS enabled, set the vmware.use.dvswitch
parameter to true
       by using the Global Settings page in the &PRODUCT; UI and restart the Management
Server.
       Unless you enable the vmware.use.dvswitch parameter, you cannot see any UI options
specific to
-      VDS, and &PRODUCT; ignores the VDS-specific parameters given in the AddClusterCmd
API call.
-      Additionally, &PRODUCT; uses VDS for virtual network infrastructure if the value
of
-      vmware.use.dvswitch parameter is true and the value of vmware.use.nexus.dvswitch parameter
is
-      false.</para>
+      VDS, and &PRODUCT; ignores the VDS-specific parameters that you specify. Additionally,
+      &PRODUCT; uses VDS for virtual network infrastructure if the value of vmware.use.dvswitch
+      parameter is true and the value of vmware.use.nexus.dvswitch parameter is false. Another
+      global parameter that defines VDS configuration is vmware.ports.per.dvportgroup. This
is the
+      default number of ports per VMware dvPortGroup in a VMware environment. This number
directly
+      associated with the number of guest network you can create.</para>
     <para>&PRODUCT; supports orchestration of virtual networks in a deployment
with a mix of Virtual
       Distributed Switch, Standard Virtual Switch and Nexus 1000v Virtual Switch. </para>
   </section>
@@ -97,12 +122,12 @@
           <row>
             <entry><para>Cluster Name</para></entry>
             <entry><para>Enter the name of the cluster you created in vCenter.
For example,
-                &quot;cloud.cluster&quot;.</para></entry>
+                &quot;cloudcluster&quot;.</para></entry>
           </row>
           <row>
             <entry><para>vCenter Host</para></entry>
-            <entry><para>Enter the name or the IP address of the vCenter host
where you have deployed the VMware
-                VDS.</para></entry>
+            <entry><para>Enter the name or the IP address of the vCenter host
where you have
+                deployed the VMware VDS.</para></entry>
           </row>
           <row>
             <entry><para>vCenter User name</para></entry>
@@ -116,7 +141,7 @@
           <row>
             <entry><para>vCenter Datacenter</para></entry>
             <entry><para>Enter the vCenter datacenter that the cluster is in.
For example,
-                &quot;cloud.dc.VM&quot;.</para></entry>
+                &quot;clouddcVM&quot;.</para></entry>
           </row>
           <row>
             <entry><para>Override Public Traffic</para></entry>
@@ -154,40 +179,5 @@
       </tgroup>
     </informaltable>
   </section>
-  <section id="vmware-dvswitch-remove">
-    <title>Removing VMware Virtual Switch</title>
-    <orderedlist>
-      <listitem>
-        <para>In the vCenter datacenter that is served by the VDS, ensure that you
delete all the
-          hosts in the corresponding cluster.</para>
-      </listitem>
-      <listitem>
-        <para>Log in with Admin permissions to the &PRODUCT; administrator UI.</para>
-      </listitem>
-      <listitem>
-        <para>In the left navigation bar, select Infrastructure.</para>
-      </listitem>
-      <listitem>
-        <para>In the Infrastructure page, click View all under Clusters.</para>
-      </listitem>
-      <listitem>
-        <para>Select the cluster where you want to remove the virtual switch.</para>
-      </listitem>
-      <listitem>
-        <para>In the VMware dvSwitch tab, click the name of the virtual switch.</para>
-      </listitem>
-      <listitem>
-        <para> In the Details page, click Delete VMware dvSwitch icon. <inlinemediaobject>
-            <imageobject>
-              <imagedata fileref="./images/delete-button.png"/>
-            </imageobject>
-            <textobject>
-              <phrase>DeleteButton.png: button to delete dvSwitch</phrase>
-            </textobject>
-          </inlinemediaobject>
-        </para>
-        <para>Click Yes in the confirmation dialog box.</para>
-      </listitem>
-    </orderedlist>
-  </section>
+  
 </section>

http://git-wip-us.apache.org/repos/asf/cloudstack/blob/d36d7090/docs/en-US/vmware-install.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/vmware-install.xml b/docs/en-US/vmware-install.xml
index fd88fc7..282cf2e 100644
--- a/docs/en-US/vmware-install.xml
+++ b/docs/en-US/vmware-install.xml
@@ -406,7 +406,7 @@ esxcfg-firewall -o 59000-60000,tcp,out,vncextras
           before you start:</para>
         <itemizedlist>
           <listitem>
-            <para>vCenter Credentials</para>
+            <para>vCenter credentials</para>
           </listitem>
           <listitem>
             <para>Nexus 1000v VSM IP address</para>


Mime
View raw message