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 78811c5
Date Mon, 10 Jun 2013 12:25:48 GMT
Updated Branches:
  refs/heads/master d8a235ee3 -> 78811c500


CLOUDSTACK-2404 more conceptual info


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

Branch: refs/heads/master
Commit: 78811c50021202cb2374ceeb9edf0fdac5c66398
Parents: d8a235e
Author: radhikap <radhika.puthiyetath@citrix.com>
Authored: Fri Jun 7 16:44:02 2013 +0530
Committer: radhikap <radhika.puthiyetath@citrix.com>
Committed: Mon Jun 10 17:55:28 2013 +0530

----------------------------------------------------------------------
 docs/en-US/pvlan.xml | 31 ++++++++++++++++++++++++++++---
 1 file changed, 28 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/cloudstack/blob/78811c50/docs/en-US/pvlan.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/pvlan.xml b/docs/en-US/pvlan.xml
index 96c1a78..5084ec4 100644
--- a/docs/en-US/pvlan.xml
+++ b/docs/en-US/pvlan.xml
@@ -22,15 +22,37 @@
 <section id="pvlan">
   <title>Isolation in Advanced Zone Using Private VLAN</title>
   <para/>
+  <itemizedlist>
+    <listitem>
+      <para>isolate VMs from other VMs on the same network (Shared Networks are the
most common use
+        case) using PVLANs</para>
+    </listitem>
+    <listitem>
+      <para>create a Network Offering enabling PVLAN support</para>
+    </listitem>
+    <listitem>
+      <para>create shared networks based on a network offering which has PVLANs enabled</para>
+    </listitem>
+    <listitem>
+      <para>supported in VPC as well as non-VPC deployments</para>
+    </listitem>
+    <listitem>
+      <para>supported on all Hypervisors</para>
+    </listitem>
+    <listitem>
+      <para>Allow end users to deploy VMs on Isolated Networks or VPC along with the
Shared Networks
+        that have PVLAN support</para>
+    </listitem>
+  </itemizedlist>
   <section id="about-pvlan">
     <title>About Private VLAN</title>
-    <para>In an Ethernet switch, a VLAN is a broadcast domain in which hosts can establish
direct
+    <para>In an Ethernet switch, a VLAN is a broadcast domain where hosts can establish
direct
       communication with each another at Layer 2. Private VLAN is designed as an extension
of VLAN
       standard to add further segmentation of the logical broadcast domain. A regular VLAN
is a
       single broadcast domain, whereas a private VLAN partitions a larger VLAN broadcast
domain into
       smaller sub-domains. A sub-domain is represented by a pair of VLANs: a Primary VLAN
and a
-      Secondary VLAN.  The original VLAN that is being divided into smaller groups is called
-      Primary, That implies all VLAN pairs in a private VLAN share the same Primary VLAN.
All the
+      Secondary VLAN. The original VLAN that is being divided into smaller groups is called
Primary,
+      which implies that all VLAN pairs in a private VLAN share the same Primary VLAN. All
the
       secondary VLANs exist only inside the Primary. Each Secondary VLAN has a specific VLAN
ID
       associated to it, which differentiates one sub-domain from another.</para>
     <para>For further reading:</para>
@@ -50,6 +72,9 @@
       </listitem>
     </itemizedlist>
   </section>
+  <section id="ability-pvlan">
+    <title>Prerequisites</title>
+  </section>
   <section id="prereq-pvlan">
     <title>Prerequisites</title>
     <para>Ensure that you configure private VLAN on your physical switches out-of-band.</para>


Mime
View raw message