review comments for CLOUDSTACK-2808, CLOUDSTACK-769

This commit is contained in:
radhikap 2013-08-27 11:32:21 +05:30
parent 030fe5b662
commit fe6e0390f8
2 changed files with 8 additions and 3 deletions

View File

@ -75,7 +75,8 @@
the VPC, and is not overlapped with the CIDR of any existing tier within the VPC.</para>
</listitem>
<listitem>
<para><emphasis role="bold">VLAN</emphasis>: The VLAN ID for the tier you create. </para>
<para><emphasis role="bold">VLAN</emphasis>: The VLAN ID for the tier that the root admin
creates. </para>
<para>This option is only visible if the network offering you selected is
VLAN-enabled.</para>
<para condition="install">For more information, see the Assigning VLANs to Isolated

View File

@ -21,14 +21,18 @@
-->
<section id="vlan-assign-isolated-nw">
<title>Assigning VLANs to Isolated Networks</title>
<para>&PRODUCT; provides you the ability to control VLAN assignment to Isolated networks. You can
assign a VLAN ID when a network is created, just the way it's done for Shared networks.</para>
<para>&PRODUCT; provides you the ability to control VLAN assignment to Isolated networks. As a
Root admin, you can assign a VLAN ID when a network is created, just the way it's done for
Shared networks.</para>
<para>The former behaviour also is supported &mdash; VLAN is randomly allocated to a network from
the VNET range of the physical network when the network turns to Implemented state. The VLAN is
released back to the VNET pool when the network shuts down as a part of the Network Garbage
Collection. The VLAN can be re-used either by the same network when it is implemented again, or
by any other network. On each subsequent implementation of a network, a new VLAN can be
assigned.</para>
<para>Only the Root admin can assign VLANs because the regular users or domain admin are not aware
of the physical network topology. They cannot even view what VLAN is assigned to a
network.</para>
<para>To enable you to assign VLANs to Isolated networks,</para>
<orderedlist>
<listitem>