You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by pa...@apache.org on 2019/07/22 16:26:24 UTC
[cloudstack-documentation] branch master updated: Network offering
scopes (#55)
This is an automated email from the ASF dual-hosted git repository.
paul_a pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git
The following commit(s) were added to refs/heads/master by this push:
new 663838d Network offering scopes (#55)
663838d is described below
commit 663838db60feba84d9ac7f1c4538146a2f82ba1c
Author: Paul Angus <pa...@shapeblue.com>
AuthorDate: Mon Jul 22 17:26:20 2019 +0100
Network offering scopes (#55)
update network offering configuration text to allow for multi-domain and multi-zone
---
source/_global.rst | 1 +
source/adminguide/networking.rst | 70 ++++++++++++++++++-------------
source/upgrading/upgrade/upgrade-4.12.rst | 1 -
3 files changed, 43 insertions(+), 29 deletions(-)
diff --git a/source/_global.rst b/source/_global.rst
index 7f2b439..d7a83ba 100644
--- a/source/_global.rst
+++ b/source/_global.rst
@@ -24,6 +24,7 @@
.. |documentation_home| replace:: http://docs.cloudstack.apache.org/
.. Latest version systemvm template name
+
.. |sysvm64-name-xen| replace:: systemvm-xenserver-4.11.3
.. |sysvm64-name-kvm| replace:: systemvm-kvm-4.11.3
.. |sysvm64-name-vmware| replace:: systemvm-vmware-4.11.3
diff --git a/source/adminguide/networking.rst b/source/adminguide/networking.rst
index fe16847..ec8d2d3 100644
--- a/source/adminguide/networking.rst
+++ b/source/adminguide/networking.rst
@@ -340,41 +340,40 @@ To create a network offering:
- **LB Isolation**: Specify what type of load balancer isolation you
want for the network: Shared or Dedicated.
- **Dedicated**: If you select dedicated LB isolation, a dedicated
- load balancer device is assigned for the network from the pool of
- dedicated load balancer devices provisioned in the zone. If no
- sufficient dedicated load balancer devices are available in the
- zone, network creation fails. Dedicated device is a good choice
- for the high-traffic networks that make full use of the device's
- resources.
-
- **Shared**: If you select shared LB isolation, a shared load
- balancer device is assigned for the network from the pool of
- shared load balancer devices provisioned in the zone. While
- provisioning CloudStack picks the shared load balancer device that
- is used by the least number of accounts. Once the device reaches
- its maximum capacity, the device will not be allocated to a new
- account.
+ - **Dedicated**: If you select dedicated LB isolation, a dedicated
+ load balancer device is assigned for the network from the pool of
+ dedicated load balancer devices provisioned in the zone. If no
+ sufficient dedicated load balancer devices are available in the
+ zone, network creation fails. Dedicated device is a good choice
+ for the high-traffic networks that make full use of the device's
+ resources.
+
+ - **Shared**: If you select shared LB isolation, a shared load
+ balancer device is assigned for the network from the pool of
+ shared load balancer devices provisioned in the zone. While
+ provisioning CloudStack picks the shared load balancer device that
+ is used by the least number of accounts. Once the device reaches
+ its maximum capacity, the device will not be allocated to a new
+ account.
- **Mode**: You can select either Inline mode or Side by Side mode:
- **Inline mode**: Supported only for Juniper SRX firewall and BigF5
- load balancer devices. In inline mode, a firewall device is placed
- in front of a load balancing device. The firewall acts as the
- gateway for all the incoming traffic, then redirect the load
- balancing traffic to the load balancer behind it. The load
- balancer in this case will not have the direct access to the
- public network.
-
- **Side by Side**: In side by side mode, a firewall device is
- deployed in parallel with the load balancer device. So the traffic
- to the load balancer public IP is not routed through the firewall,
- and therefore, is exposed to the public network.
+ - **Inline mode**: Supported only for Juniper SRX firewall and BigF5
+ load balancer devices. In inline mode, a firewall device is placed
+ in front of a load balancing device. The firewall acts as the
+ gateway for all the incoming traffic, then redirect the load
+ balancing traffic to the load balancer behind it. The load
+ balancer in this case will not have the direct access to the
+ public network.
+
+ - **Side by Side**: In side by side mode, a firewall device is
+ deployed in parallel with the load balancer device. So the traffic
+ to the load balancer public IP is not routed through the firewall,
+ and therefore, is exposed to the public network.
- **Associate Public IP**: Select this option if you want to assign
a public IP address to the VMs deployed in the guest network. This
option is available only if
-
- Guest network is shared.
- StaticNAT is enabled.
@@ -422,5 +421,20 @@ To create a network offering:
this case, when you configure an egress rules for an isolated
guest network, rules are added to allow the specified traffic.
+ - **Public**: Indicate whether the network offering should be available to
+ all domains or only some domains. Choose Yes to make it available to
+ all domains. Choose No to limit the scope to one or more domains.
+
+ - **Domain**: This is only visible When ‘Public’ is unchecked. When visible,
+ this controls the domains which will be able to use this network offering.
+ A multi-selection list box will be displayed. One or more domains can be
+ selected from this list box by holding down the control key and selecting
+ the desired domains.
+
+ - **Zone**: This controls which zones a network offering is available in.
+ ‘All zones’ or only specific zones can be selected. One or more zones can be
+ selected from this list box by holding down the control key and selecting
+ the desired zones.
+
#. Click Add.
diff --git a/source/upgrading/upgrade/upgrade-4.12.rst b/source/upgrading/upgrade/upgrade-4.12.rst
index 310219b..763ba85 100644
--- a/source/upgrading/upgrade/upgrade-4.12.rst
+++ b/source/upgrading/upgrade/upgrade-4.12.rst
@@ -13,7 +13,6 @@
specific language governing permissions and limitations
under the License.
-
.. |version_to_upgrade| replace:: 4.12.x
Upgrade Instruction from |version_to_upgrade|