|
| 1 | +<?xml version='1.0' encoding='utf-8' ?> |
| 2 | +<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ |
| 3 | +<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent"> |
| 4 | +%BOOK_ENTITIES; |
| 5 | +]> |
| 6 | +<!-- Licensed to the Apache Software Foundation (ASF) under one |
| 7 | + or more contributor license agreements. See the NOTICE file |
| 8 | + distributed with this work for additional information |
| 9 | + regarding copyright ownership. The ASF licenses this file |
| 10 | + to you under the Apache License, Version 2.0 (the |
| 11 | + "License"); you may not use this file except in compliance |
| 12 | + with the License. You may obtain a copy of the License at |
| 13 | + http://www.apache.org/licenses/LICENSE-2.0 |
| 14 | + Unless required by applicable law or agreed to in writing, |
| 15 | + software distributed under the License is distributed on an |
| 16 | + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY |
| 17 | + KIND, either express or implied. See the License for the |
| 18 | + specific language governing permissions and limitations |
| 19 | + under the License. |
| 20 | +--> |
| 21 | +<section id="network-rate"> |
| 22 | + <title>Network Throttling</title> |
| 23 | + <para>Network throttling is the process of controlling the network access and bandwidth usage |
| 24 | + based on certain rules. &PRODUCT; controls this behaviour of the guest networks in the cloud by |
| 25 | + using the network rate parameter. This parameter is defined as the default data transfer rate in |
| 26 | + Mbps (Megabits Per Second) allowed in a guest network. It defines the upper limits for network |
| 27 | + utilization. If the current utilization is below the allowed upper limits, access is granted, |
| 28 | + else revoked.</para> |
| 29 | + <para>You can throttle the network bandwidth either to control the usage above a certain limit for |
| 30 | + some accounts, or to control network congestion in a large cloud environment. The network rate |
| 31 | + for your cloud can be configured on the following:</para> |
| 32 | + <itemizedlist> |
| 33 | + <listitem> |
| 34 | + <para>Network Offering</para> |
| 35 | + </listitem> |
| 36 | + <listitem> |
| 37 | + <para>Service Offering</para> |
| 38 | + </listitem> |
| 39 | + <listitem> |
| 40 | + <para>Global parameter</para> |
| 41 | + </listitem> |
| 42 | + </itemizedlist> |
| 43 | + <para>If network rate is set to NULL in service offering, the value provided in the |
| 44 | + vm.network.throttling.rate global parameter is applied. If the value is set to NULL for network |
| 45 | + offering, the value provided in the network.throttling.rate global parameter is |
| 46 | + considered.</para> |
| 47 | + <para>For the default public, storage, and management networks, network rate is set to 0. This |
| 48 | + implies that the public, storage, and management networks will have unlimited bandwidth by |
| 49 | + default. For default guest networks, network rate is set to NULL. In this case, network rate is |
| 50 | + defaulted to the global parameter value.</para> |
| 51 | + <para>The following table gives you an overview of how network rate is applied on different types |
| 52 | + of networks in &PRODUCT;.</para> |
| 53 | + <informaltable> |
| 54 | + <tgroup cols="2" align="left" colsep="1" rowsep="1"> |
| 55 | + <colspec colwidth="1.0*" colname="1" colnum="1"/> |
| 56 | + <colspec colwidth="3.18*" colname="2" colnum="2"/> |
| 57 | + <thead> |
| 58 | + <row> |
| 59 | + <entry><para>Networks</para></entry> |
| 60 | + <entry><para>Network Rate Is Taken from</para></entry> |
| 61 | + </row> |
| 62 | + </thead> |
| 63 | + <tbody> |
| 64 | + <row> |
| 65 | + <entry><para>Guest network of Virtual Router</para></entry> |
| 66 | + <entry><para>Guest Network Offering</para></entry> |
| 67 | + </row> |
| 68 | + <row> |
| 69 | + <entry><para>Public network of Virtual Router</para></entry> |
| 70 | + <entry><para>Guest Network Offering</para></entry> |
| 71 | + </row> |
| 72 | + <row> |
| 73 | + <entry><para>Storage network of Secondary Storage VM</para></entry> |
| 74 | + <entry><para>System Network Offering</para></entry> |
| 75 | + </row> |
| 76 | + <row> |
| 77 | + <entry><para>Management network of Secondary Storage VM</para></entry> |
| 78 | + <entry><para>System Network Offering</para></entry> |
| 79 | + </row> |
| 80 | + <row> |
| 81 | + <entry><para>Storage network of Console Proxy VM</para></entry> |
| 82 | + <entry><para>System Network Offering</para></entry> |
| 83 | + </row> |
| 84 | + <row> |
| 85 | + <entry><para>Management network of Console Proxy VM</para></entry> |
| 86 | + <entry><para>System Network Offering</para></entry> |
| 87 | + </row> |
| 88 | + <row> |
| 89 | + <entry><para>Storage network of Virtual Router</para></entry> |
| 90 | + <entry><para>System Network Offering</para></entry> |
| 91 | + </row> |
| 92 | + <row> |
| 93 | + <entry><para>Management network of Virtual Router</para></entry> |
| 94 | + <entry><para>System Network Offering</para></entry> |
| 95 | + </row> |
| 96 | + <row> |
| 97 | + <entry><para>Public network of Secondary Storage VM</para></entry> |
| 98 | + <entry><para>System Network Offering</para></entry> |
| 99 | + </row> |
| 100 | + <row> |
| 101 | + <entry><para>Public network of Console Proxy VM</para></entry> |
| 102 | + <entry><para>System Network Offering</para></entry> |
| 103 | + </row> |
| 104 | + <row> |
| 105 | + <entry><para>Default network of a guest VM</para></entry> |
| 106 | + <entry><para>Compute Offering</para></entry> |
| 107 | + </row> |
| 108 | + <row> |
| 109 | + <entry><para>Additional networks of a guest VM</para></entry> |
| 110 | + <entry><para>Corresponding Network Offerings</para></entry> |
| 111 | + </row> |
| 112 | + </tbody> |
| 113 | + </tgroup> |
| 114 | + </informaltable> |
| 115 | + <para>A guest VM must have a default network, and can also have many additional networks. |
| 116 | + Depending on various parameters, such as the host and virtual switch used, you can observe a |
| 117 | + difference in the network rate in your cloud. For example, on a VMware host the actual network |
| 118 | + rate varies based on where they are configured (compute offering, network offering, or both); |
| 119 | + the network type (shared or isolated); and traffic direction (ingress or egress). </para> |
| 120 | + <para>The network rate set for a network offering used by a particular network in &PRODUCT; is |
| 121 | + used for the traffic shaping policy of a port group, for example: port group A, for that |
| 122 | + network: a particular subnet or VLAN on the actual network. The virtual routers for that network |
| 123 | + connects to the port group A, and by default instances in that network connects to this port |
| 124 | + group. However, if an instance is deployed with a compute offering with the network rate set, |
| 125 | + and if this rate is used for the traffic shaping policy of another port group for the network, |
| 126 | + for example port group B, then instances using this compute offering are connected to the port |
| 127 | + group B, instead of connecting to port group A.</para> |
| 128 | + <para>The traffic shaping policy on standard port groups in VMware only applies to the egress |
| 129 | + traffic, and the net effect depends on the type of network used in &PRODUCT;. In shared |
| 130 | + networks, ingress traffic is unlimited for &PRODUCT;, and egress traffic is limited to the rate |
| 131 | + that applies to the port group used by the instance if any. If the compute offering has a |
| 132 | + network rate configured, this rate applies to the egress traffic, otherwise the network rate set |
| 133 | + for the network offering applies. For isolated networks, the network rate set for the network |
| 134 | + offering, if any, effectively applies to the ingress traffic. This is mainly because the network |
| 135 | + rate set for the network offering applies to the egress traffic from the virtual router to the |
| 136 | + instance. The egress traffic is limited by the rate that applies to the port group used by the |
| 137 | + instance if any, similar to shared networks. </para> |
| 138 | + <para>For example:</para> |
| 139 | + <para>Network rate of network offering = 10 Mbps</para> |
| 140 | + <para>Network rate of compute offering = 200 Mbps</para> |
| 141 | + <para>In shared networks, ingress traffic will not be limited for &PRODUCT;, while egress traffic |
| 142 | + will be limited to 200 Mbps. In an isolated network, ingress traffic will be limited to 10 Mbps |
| 143 | + and egress to 200 Mbps.</para> |
| 144 | +</section> |
0 commit comments