Skip to content

Commit fe6e039

Browse files
author
radhikap
committed
review comments for CLOUDSTACK-2808, CLOUDSTACK-769
1 parent 030fe5b commit fe6e039

2 files changed

Lines changed: 8 additions & 3 deletions

File tree

docs/en-US/add-tier.xml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,8 @@
7575
the VPC, and is not overlapped with the CIDR of any existing tier within the VPC.</para>
7676
</listitem>
7777
<listitem>
78-
<para><emphasis role="bold">VLAN</emphasis>: The VLAN ID for the tier you create. </para>
78+
<para><emphasis role="bold">VLAN</emphasis>: The VLAN ID for the tier that the root admin
79+
creates. </para>
7980
<para>This option is only visible if the network offering you selected is
8081
VLAN-enabled.</para>
8182
<para condition="install">For more information, see the Assigning VLANs to Isolated

docs/en-US/vlan-assign-isolated-nw.xml

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,14 +21,18 @@
2121
-->
2222
<section id="vlan-assign-isolated-nw">
2323
<title>Assigning VLANs to Isolated Networks</title>
24-
<para>&PRODUCT; provides you the ability to control VLAN assignment to Isolated networks. You can
25-
assign a VLAN ID when a network is created, just the way it's done for Shared networks.</para>
24+
<para>&PRODUCT; provides you the ability to control VLAN assignment to Isolated networks. As a
25+
Root admin, you can assign a VLAN ID when a network is created, just the way it's done for
26+
Shared networks.</para>
2627
<para>The former behaviour also is supported &mdash; VLAN is randomly allocated to a network from
2728
the VNET range of the physical network when the network turns to Implemented state. The VLAN is
2829
released back to the VNET pool when the network shuts down as a part of the Network Garbage
2930
Collection. The VLAN can be re-used either by the same network when it is implemented again, or
3031
by any other network. On each subsequent implementation of a network, a new VLAN can be
3132
assigned.</para>
33+
<para>Only the Root admin can assign VLANs because the regular users or domain admin are not aware
34+
of the physical network topology. They cannot even view what VLAN is assigned to a
35+
network.</para>
3236
<para>To enable you to assign VLANs to Isolated networks,</para>
3337
<orderedlist>
3438
<listitem>

0 commit comments

Comments
 (0)