mirror of
https://github.com/apache/cloudstack.git
synced 2025-11-04 00:02:37 +01:00
67 lines
3.3 KiB
XML
67 lines
3.3 KiB
XML
<?xml version='1.0' encoding='utf-8' ?>
|
|
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
|
<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
|
|
%BOOK_ENTITIES;
|
|
]>
|
|
|
|
<!-- Licensed to the Apache Software Foundation (ASF) under one
|
|
or more contributor license agreements. See the NOTICE file
|
|
distributed with this work for additional information
|
|
regarding copyright ownership. The ASF licenses this file
|
|
to you under the Apache License, Version 2.0 (the
|
|
"License"); you may not use this file except in compliance
|
|
with the License. You may obtain a copy of the License at
|
|
http://www.apache.org/licenses/LICENSE-2.0
|
|
Unless required by applicable law or agreed to in writing,
|
|
software distributed under the License is distributed on an
|
|
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
|
KIND, either express or implied. See the License for the
|
|
specific language governing permissions and limitations
|
|
under the License.
|
|
-->
|
|
<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. 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 — 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>
|
|
<para>Create a network offering by specifying the following:</para>
|
|
<itemizedlist>
|
|
<listitem>
|
|
<para><emphasis role="bold">Guest Type</emphasis>: Select Isolated.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para><emphasis role="bold">Specify VLAN</emphasis>: Select the option.</para>
|
|
</listitem>
|
|
</itemizedlist>
|
|
<para condition="install">For more information, see <xref linkend="creating-network-offerings"
|
|
/>.</para>
|
|
<para condition="admin">For more information, see the &PRODUCT; Installation Guide.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Using this network offering, create a network.</para>
|
|
<para>You can create a VPC tier or an Isolated network.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Specify the VLAN when you create the network.</para>
|
|
<para>When VLAN is specified, a CIDR and gateway are assigned to this network and the state is
|
|
changed to Setup. In this state, the network will not be garbage collected.</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
<note>
|
|
<para>You cannot change a VLAN once it's assigned to the network. The VLAN remains with the
|
|
network for its entire life cycle.</para>
|
|
</note>
|
|
</section>
|