Return-Path: X-Original-To: apmail-cloudstack-commits-archive@www.apache.org Delivered-To: apmail-cloudstack-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6E1CE10B94 for ; Wed, 3 Jul 2013 22:25:44 +0000 (UTC) Received: (qmail 73698 invoked by uid 500); 3 Jul 2013 22:25:41 -0000 Delivered-To: apmail-cloudstack-commits-archive@cloudstack.apache.org Received: (qmail 73620 invoked by uid 500); 3 Jul 2013 22:25:41 -0000 Mailing-List: contact commits-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list commits@cloudstack.apache.org Received: (qmail 73523 invoked by uid 99); 3 Jul 2013 22:25:41 -0000 Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org) (140.211.11.114) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Jul 2013 22:25:41 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id 2FFA582A0CE; Wed, 3 Jul 2013 22:25:41 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: ahuang@apache.org To: commits@cloudstack.apache.org Date: Wed, 03 Jul 2013 22:25:48 -0000 Message-Id: In-Reply-To: References: X-Mailer: ASF-Git Admin Mailer Subject: [09/50] [abbrv] git commit: updated refs/heads/vmsync to 78fa5e1 CLOUDSTACK-2808 Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/db5d5262 Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/db5d5262 Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/db5d5262 Branch: refs/heads/vmsync Commit: db5d526269acac3fba357bd9f7ac4638a865fce1 Parents: 43f31dc Author: unknown Authored: Tue Jul 2 19:37:57 2013 +0530 Committer: unknown Committed: Tue Jul 2 19:39:04 2013 +0530 ---------------------------------------------------------------------- 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(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/cloudstack/blob/db5d5262/docs/en-US/creating-network-offerings.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/creating-network-offerings.xml b/docs/en-US/creating-network-offerings.xml index 260751e..6e25b27 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 http://git-wip-us.apache.org/repos/asf/cloudstack/blob/db5d5262/docs/en-US/vlan-assign-isolated-nw.xml ---------------------------------------------------------------------- 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 0000000..82fd5b5 --- /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. + + +
http://git-wip-us.apache.org/repos/asf/cloudstack/blob/db5d5262/docs/en-US/vlan-provisioning.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/vlan-provisioning.xml b/docs/en-US/vlan-provisioning.xml index d37be16..2d1a49e 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.
+