Updated Branches: refs/heads/4.1 9419d906e -> 743ba7da2
CLOUDSTACK-1221 Project: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/commit/743ba7da Tree: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/tree/743ba7da Diff: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/diff/743ba7da Branch: refs/heads/4.1 Commit: 743ba7da24f22e454794f47ad5edb00e1743d4fa Parents: 9419d90 Author: Radhika PC <[email protected]> Authored: Thu Feb 28 18:20:09 2013 +0530 Committer: Radhika PC <[email protected]> Committed: Thu Feb 28 18:20:09 2013 +0530 ---------------------------------------------------------------------- docs/en-US/vlan-provisioning.xml | 23 ++++++++++++++++++----- 1 files changed, 18 insertions(+), 5 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/743ba7da/docs/en-US/vlan-provisioning.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/vlan-provisioning.xml b/docs/en-US/vlan-provisioning.xml index 8abd5da..9345647 100644 --- a/docs/en-US/vlan-provisioning.xml +++ b/docs/en-US/vlan-provisioning.xml @@ -21,10 +21,23 @@ specific language governing permissions and limitations under the License. --> - <section id="vlan-provisioning"> - <title>VLAN Provisioning</title> - <para>&PRODUCT; automatically creates and destroys interfaces bridged to VLANs on the hosts. In general the administrator does not need to manage this process.</para> - <para>&PRODUCT; manages VLANs differently based on hypervisor type. For XenServer or KVM, the VLANs are created on only the hosts where they will be used and then they are destroyed when all guests that require them have been terminated or moved to another host.</para> - <para>For vSphere the VLANs are provisioned on all hosts in the cluster even if there is no guest running on a particular Host that requires the VLAN. This allows the administrator to perform live migration and other functions in vCenter without having to create the VLAN on the destination Host. Additionally, the VLANs are not removed from the Hosts when they are no longer needed. </para> + <title>VLAN Provisioning</title> + <para>&PRODUCT; automatically creates and destroys interfaces bridged to VLANs on the hosts. In + general the administrator does not need to manage this process.</para> + <para>&PRODUCT; manages VLANs differently based on hypervisor type. For XenServer or KVM, the + VLANs are created on only the hosts where they will be used and then they are destroyed when all + guests that require them have been terminated or moved to another host.</para> + <para>For vSphere the VLANs are provisioned on all hosts in the cluster even if there is no guest + running on a particular Host that requires the VLAN. This allows the administrator to perform + live migration and other functions in vCenter without having to create the VLAN on the + destination Host. Additionally, the VLANs are not removed from the Hosts when they are no longer + needed.</para> + <para>You can use the same VLANs on different physical networks provided that each physical + network has its own underlying layer-2 infrastructure, such as switches. For example, you can + specify VLAN range 500 to 1000 while deploying physical networks A and B in an Advanced zone + setup. This capability allows you to set up an additional layer-2 physical infrastructure on a + different physical NIC and use the same set of VLANs if you run out of VLANs. Another advantage + is that you can use the same set of IPs for different customers, each one with their own routers + and the guest networks on different physical NICs.</para> </section>
