You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by ra...@apache.org on 2013/08/05 10:45:38 UTC
git commit: updated refs/heads/4.2 to e297ffa
Updated Branches:
refs/heads/4.2 dbd321b02 -> e297ffa45
CLOUDSTACK-850 fixed review comments from sheng/community
Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo
Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/e297ffa4
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/e297ffa4
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/e297ffa4
Branch: refs/heads/4.2
Commit: e297ffa4578dbff58a1e650839742e296c2f6e60
Parents: dbd321b
Author: Radhika PC <ra...@citrix.com>
Authored: Mon Aug 5 14:14:25 2013 +0530
Committer: Radhika PC <ra...@citrix.com>
Committed: Mon Aug 5 14:14:53 2013 +0530
----------------------------------------------------------------------
docs/en-US/pvlan.xml | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cloudstack/blob/e297ffa4/docs/en-US/pvlan.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/pvlan.xml b/docs/en-US/pvlan.xml
index d569507..f647d93 100644
--- a/docs/en-US/pvlan.xml
+++ b/docs/en-US/pvlan.xml
@@ -113,19 +113,19 @@
ports. Configure the switch port connected to the router in PVLAN promiscuous trunk mode,
which would translate an isolated VLAN to primary VLAN for the PVLAN-unaware router. </para>
<para>Note that only Cisco Catalyst 4500 has the PVLAN promiscuous trunk mode to connect
- both normal VLAN and PVLAN to a PVLAN-unaware switch. For other Catalyst PVLAN support
- switch, connect the switch to upper switch by using cables. The number of cables should be
- greater than the number of PVLANs used.</para>
+ both normal VLAN and PVLAN to a PVLAN-unaware switch. For the other Catalyst PVLAN support
+ switch, connect the switch to upper switch by using cables, one each for a PVLAN
+ pair.</para>
</listitem>
<listitem>
<para>Configure private VLAN on your physical switches out-of-band.</para>
</listitem>
<listitem>
- <para>Before you use PVLAN on XenServer and KVM, enable Open vSwitch (OVS) .</para>
+ <para>Before you use PVLAN on XenServer and KVM, enable Open vSwitch (OVS).</para>
<note>
- <para>OVS on XenServer and KVM does not support PVLAN. Therefore, simulate PVLAN on OVS
- for XenServer and KVM by modifying the flow table and tagging every traffic leaving
- guest VMs with the secondary VLAN ID.</para>
+ <para>OVS on XenServer and KVM does not support PVLAN natively. Therefore, &PRODUCT;
+ managed to simulate PVLAN on OVS for XenServer and KVM by modifying the flow
+ table.</para>
</note>
</listitem>
</itemizedlist>
@@ -176,8 +176,8 @@
<para><emphasis role="bold">VLAN ID</emphasis>: The unique ID of the VLAN.</para>
</listitem>
<listitem>
- <para><emphasis role="bold">Isolated VLAN ID</emphasis>: The unique ID of the Secondary
- Isolated VLAN. </para>
+ <para><emphasis role="bold">Secondary Isolated VLAN ID</emphasis>: The unique ID of the
+ Secondary Isolated VLAN. </para>
<para>For the description on Secondary Isolated VLAN, see <xref linkend="about-pvlan"
/>.</para>
</listitem>