From f0db7aec98d5d7e84a3f3456b2ea04562ee0090d Mon Sep 17 00:00:00 2001 From: Radhika PC Date: Tue, 30 Jul 2013 17:08:27 +0530 Subject: [PATCH] CLOUDSTACK-478 --- ...ed-zone-physical-network-configuration.xml | 1 + docs/en-US/creating-shared-network.xml | 132 ++++++++++++++++++ docs/en-US/isolated-networks.xml | 25 ++-- docs/en-US/shared-networks.xml | 36 +++-- 4 files changed, 172 insertions(+), 22 deletions(-) create mode 100644 docs/en-US/creating-shared-network.xml diff --git a/docs/en-US/advanced-zone-physical-network-configuration.xml b/docs/en-US/advanced-zone-physical-network-configuration.xml index e47c0fd6da9..cfc6184c000 100644 --- a/docs/en-US/advanced-zone-physical-network-configuration.xml +++ b/docs/en-US/advanced-zone-physical-network-configuration.xml @@ -26,4 +26,5 @@ xmlns:xi="http://www.w3.org/2001/XInclude"/> + diff --git a/docs/en-US/creating-shared-network.xml b/docs/en-US/creating-shared-network.xml new file mode 100644 index 00000000000..6c2b50466ba --- /dev/null +++ b/docs/en-US/creating-shared-network.xml @@ -0,0 +1,132 @@ + + +%BOOK_ENTITIES; +]> + + +
+ Configuring a Shared Guest Network + + + Log in to the CloudPlatform UI as administrator. + + + In the left navigation, choose Infrastructure. + + + On Zones, click View More. + + + Click the zone to which you want to add a guest network. + + + Click the Physical Network tab. + + + Click the physical network you want to work with. + + + On the Guest node of the diagram, click Configure. + + + Click the Network tab. + + + Click Add guest network. + The Add guest network window is displayed. + + + Specify the following: + + + Name: The name of the network. This will be visible + to the user. + + + Description: The short description of the network + that can be displayed to users. + + + VLAN ID: The unique ID of the VLAN. + + + Isolated VLAN ID: The unique ID of the Secondary + Isolated VLAN. + + + Scope: The available scopes are Domain, Account, + Project, and All. + + + Domain: Selecting Domain limits the scope of + this guest network to the domain you specify. The network will not be available for + other domains. If you select Subdomain Access, the guest network is available to all + the sub domains within the selected domain. + + + Account: The account for which the guest + network is being created for. You must specify the domain the account belongs + to. + + + Project: The project for which the guest + network is being created for. You must specify the domain the project belongs + to. + + + All: The guest network is available for all the + domains, account, projects within the selected zone. + + + + + Network Offering: If the administrator has + configured multiple network offerings, select the one you want to use for this + network. + + + Gateway: The gateway that the guests should + use. + + + Netmask: The netmask in use on the subnet the + guests will use. + + + IP Range: A range of IP addresses that are + accessible from the Internet and are assigned to the guest VMs. + If one NIC is used, these IPs should be in the same CIDR in the case of IPv6. + + + IPv6 CIDR: The network prefix that defines the + guest network subnet. This is the CIDR that describes the IPv6 addresses in use in the + guest networks in this zone. To allot IP addresses from within a particular address + block, enter a CIDR. + + + Network Domain: A custom DNS suffix at the level of + a network. If you want to assign a special domain name to the guest VM network, specify + a DNS suffix. + + + + + Click OK to confirm. + + +
diff --git a/docs/en-US/isolated-networks.xml b/docs/en-US/isolated-networks.xml index 671591d161c..c8560445d2f 100644 --- a/docs/en-US/isolated-networks.xml +++ b/docs/en-US/isolated-networks.xml @@ -22,13 +22,20 @@ under the License. -->
- Isolated Networks - An isolated network can be accessed only by virtual machines of a single account. Isolated networks have the following properties. - - Resources such as VLAN are allocated and garbage collected dynamically - There is one network offering for the entire network - The network offering can be upgraded or downgraded but it is for the entire network - - - + Isolated Networks + An isolated network can be accessed only by virtual machines of a single account. Isolated + networks have the following properties. + + + Resources such as VLAN are allocated and garbage collected dynamically + + + There is one network offering for the entire network + + + The network offering can be upgraded or downgraded but it is for the entire + network + + + For more information, see .
diff --git a/docs/en-US/shared-networks.xml b/docs/en-US/shared-networks.xml index 4c323208135..65657cef828 100644 --- a/docs/en-US/shared-networks.xml +++ b/docs/en-US/shared-networks.xml @@ -22,17 +22,27 @@ under the License. -->
- Shared Networks - A shared network can be accessed by virtual machines that belong to many different - accounts. Network Isolation on shared networks is accomplished using techniques such as - security groups (supported only in basic zones). - - Shared Networks are created by the administrator - Shared Networks can be designated to a certain domain - Shared Network resources such as VLAN and physical network that it maps to are designated by the administrator - Shared Networks are isolated by security groups - Public Network is a shared network that is not shown to the end users - - - + Shared Networks + A shared network can be accessed by virtual machines that belong to many different accounts. + Network Isolation on shared networks is accomplished using techniques such as security groups + (supported only in basic zones). + + + Shared Networks are created by the administrator + + + Shared Networks can be designated to a certain domain + + + Shared Network resources such as VLAN and physical network that it maps to are + designated by the administrator + + + Shared Networks are isolated by security groups + + + Public Network is a shared network that is not shown to the end users + + + For information, see .