Merge "change to section_cli_nova_customize_flavors"

This commit is contained in:
Jenkins
2014-06-16 07:48:23 +00:00
committed by Gerrit Code Review

View File

@@ -201,13 +201,13 @@
</varlistentry>
<varlistentry><term>Bandwidth I/O</term>
<listitem><para>Incoming and outgoing traffic can be shaped independently. The bandwidth element can have at
most one inbound and at most one outbound child element. If you leave any of
these children element out, no quality of service (QoS) is applied on that
most, one inbound and at most, one outbound child element. If you leave any of
these child elements out, no quality of service (QoS) is applied on that
traffic direction. So, if you want to shape only the network's incoming traffic,
use inbound only (and vice versa). Each element has one mandatory attribute
average, which specifies the average bit rate on the interface being shaped.</para>
<para>There are also two optional attributes (integer): <option>peak</option>, which
specifies maximum rate at which bridge can send data (kilobytes/second), and
specifies the maximum rate at which a bridge can send data (kilobytes/second), and
<option>burst</option>, the amount of bytes that can be burst at peak speed
(kilobytes). The rate is shared equally within domains connected to the
network.</para>
@@ -219,7 +219,7 @@
<varlistentry><term>Watchdog behavior</term>
<listitem><para>For the <systemitem>libvirt</systemitem> driver, you can enable and set the behavior of a
virtual hardware watchdog device for each flavor. Watchdog devices keep an eye
on the guest server, and carry out the configured action if the server hangs.
on the guest server, and carry out the configured action, if the server hangs.
The watchdog uses the i6300esb device (emulating a PCI Intel 6300ESB). If
<literal>hw_watchdog_action</literal> is not specified, the watchdog is
disabled.</para>