| .. 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. |
| |
| |
| |
| Advanced Zone Physical Network Configuration |
| -------------------------------------------- |
| |
| Within a zone that uses advanced networking, you need to tell the |
| Management Server how the physical network is set up to carry different |
| kinds of traffic in isolation. |
| |
| |
| Configure Guest Traffic in an Advanced Zone |
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| |
| These steps assume you have already logged in to the CloudStack UI. To |
| configure the base guest network: |
| |
| #. In the left navigation, choose Network. |
| |
| #. Click Add network. |
| |
| The Add guest network window is displayed: |
| |
| |addguestnetwork.png| |
| |
| #. Provide the following information for creating an isolated network: |
| |
| - **Name**: The name of the network. This will be user-visible |
| |
| - **Description**: The description of the network. This will be |
| user-visible |
| |
| - **Zone**: The zone in which you are configuring the guest network. |
| |
| - **Network offering**: If the administrator has configured multiple |
| network offerings, select the one you want to use for this network |
| |
| - **Public MTU**: The MTU that will be configured on the public interfaces |
| of the network's VR. |
| **NOTE:** This will not be considered for VPC network tiers, as the |
| public MTU defined at the VPC network creation level will be considered |
| |
| - **Private MTU**: The MTU that will configured on the private interface(s) |
| of the network's VR |
| |
| - **External Id**: ID of the network in an external system. |
| |
| - **Gateway**: The gateway that the guests instances will use. |
| |
| - **Netmask**: The netmask in use on the subnet the guest instances |
| will use. |
| |
| - **DNS**: A set of custom DNS that will be used by the guest network. If not provided then DNS specified for the zone will be used. Available only when the selected network offering supports DNS service. |
| |
| - **IPv6 DNS**: A set of custom IPv6 DNS that will be used by the guest network. If not provided then IPv6 DNS specified for the zone will be used. Available only when the selected network offering is IPv6 enabled and supports DNS service. |
| |
| - **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. |
| |
| .. note:: |
| * In security groups-enabled Advanced zones and Basic zones, creation of VPC and isolated networks are not supported. |
| * MTU options will be shown in the UI and considered only when zone configuration - `allow.end.users.to.specify.vr.mtu` is set to true. Maximum allowed values for public and private MTU can be controlled by zone-level configurations, `vr.public.interface.max.mtu` and `vr.private.interface.max.mtu` respectively. |
| |
| Configure Public Traffic in an Advanced Zone |
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| |
| In a zone that uses advanced networking, you need to configure at least |
| one range of IP addresses for Internet traffic. |
| |
| |
| Configuring a Shared Guest Network |
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| |
| #. Log in to the CloudStack UI as administrator or an end user. |
| |
| #. In the left navigation, choose Network. |
| |
| #. Click the Guest networks tab |
| |
| #. Click the Add network icon. |
| |
| #. Click the Shared tab. |
| |
| The Add guest network window is displayed. |
| |
| |addsharednetwork.png| |
| |
| #. 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. |
| |
| - **Zone**: The zone for the network. |
| |
| - **Physical Network**: The physical network ID the network belongs to. |
| |
| - **VLAN ID**: (Administrators only) The unique ID of the VLAN. |
| |
| - **Secondary VLAN Type**: (Administrators only) The isolation private |
| VLAN type for this network |
| |
| - **Secondary VLAN ID**: (Administrators only) The unique ID of the |
| Secondary Isolated VLAN. |
| |
| - **Bypass VLAN id/range overlap**: (Administrators only) When true |
| bypasses VLAN id/range overlap check during network creation for |
| shared and L2 networks |
| |
| - **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**: (Administrators only) 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. |
| |
| - **Public MTU**: The MTU that will be configured on the public interfaces |
| of the network's VR. This MTU will considered for redundant VRs |
| |
| - **Private MTU**: The MTU that will configured on the private interface(s) |
| of the network's VR |
| |
| - **Associated Network**: The L2 or Isolated network this network is |
| associated to. This network will use same VLAN as associated network. |
| This will be visible if network offering has specifyvlan is false. |
| |
| - **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. |
| |
| - **DNS**: A set of custom DNS that will be used by the network. If not provided then DNS specified for the zone will be used. Available only when the selected network offering supports DNS service. |
| |
| 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. |
| |
| - **IPv6 DNS**: A set of custom IPv6 DNS that will be used by the network. If not provided then IPv6 DNS specified for the zone will be used. Available only when the selected network offering supports DNS service. |
| |
| - **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. |
| |
| .. note:: |
| * End users (not administrator) can only use the network |
| offerings with specifyvlan is false. Please create a network offering |
| with specifyvlan is false to enable this for end users. See |
| `“Creating a New Network Offering” |
| <networking.html#creating-a-new-network-offering>`_. |
| * MTU options will be shown in the UI and considered only when zone configuration - `allow.end.users.to.specify.vr.mtu` is set to true. Maximum allowed values for public and private MTU can be controlled by zone-level configurations, `vr.public.interface.max.mtu` and `vr.private.interface.max.mtu` respectively. |
| |
| |
| .. |addguestnetwork.png| image:: /_static/images/add-guest-network.png |
| :alt: Add Guest network setup in a single zone. |
| |
| .. |addsharednetwork.png| image:: /_static/images/add-shared-network.png |
| :alt: Add Shared Guest network. |