From db5d526269acac3fba357bd9f7ac4638a865fce1 Mon Sep 17 00:00:00 2001 From: unknown Date: Tue, 2 Jul 2013 19:37:57 +0530 Subject: [PATCH] CLOUDSTACK-2808 --- docs/en-US/creating-network-offerings.xml | 4 +- docs/en-US/vlan-assign-isolated-nw.xml | 72 +++++++++++++++++++++++ docs/en-US/vlan-provisioning.xml | 1 + 3 files changed, 76 insertions(+), 1 deletion(-) create mode 100644 docs/en-US/vlan-assign-isolated-nw.xml diff --git a/docs/en-US/creating-network-offerings.xml b/docs/en-US/creating-network-offerings.xml index 260751ea079..6e25b27e9ad 100644 --- a/docs/en-US/creating-network-offerings.xml +++ b/docs/en-US/creating-network-offerings.xml @@ -68,7 +68,9 @@ Specify VLAN. (Isolated guest networks only) - Indicate whether a VLAN should be specified when this offering is used. + Indicate whether a VLAN could be specified when this offering is used. If you select + this option and later use this network offering while creating a VPC tier or an isolated + network, you will be able to specify a VLAN ID for the network you create. VPC. This option indicate whether the guest network diff --git a/docs/en-US/vlan-assign-isolated-nw.xml b/docs/en-US/vlan-assign-isolated-nw.xml new file mode 100644 index 00000000000..82fd5b58b41 --- /dev/null +++ b/docs/en-US/vlan-assign-isolated-nw.xml @@ -0,0 +1,72 @@ + + +%BOOK_ENTITIES; +]> + + +
+ Assigning VLANs to Isolated Networks + &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. + Additionally, a network with VLAN ID can be excluded from the Network Garbage Collection. + The former behaviour also is supported — 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. + + + Log in to the CloudPlatform UI as an administrator or end user. + + + Ensure that the VLAN range does not already exist. + + + Check whether the new VLAN range overlaps with any existing ones. If overlaps, extend + the existing range. If does not overlap, add the new range. + + + In the left navigation, choose Infrastructure. On Zones, click View More, then click the + zone to which you want to work with. + + + Click Physical Network. + + + In the Guest node of the diagram, click Configure. + + + Click Add VLAN Ranges button + + + + + add-vlan-ico.png: button to add a VLAN range. + + + The Add VLAN Ranges dialog is displayed. + + + Specify the start and end of the VLAN range. + + + Click OK. + + +
diff --git a/docs/en-US/vlan-provisioning.xml b/docs/en-US/vlan-provisioning.xml index d37be16fe5e..2d1a49e04c5 100644 --- a/docs/en-US/vlan-provisioning.xml +++ b/docs/en-US/vlan-provisioning.xml @@ -42,4 +42,5 @@ and the guest networks on different physical NICs. +