Fixes bug 882781

Change-Id: Ib596617b99d6f2f8aaa33b3af0c39703ac6e5471
This commit is contained in:
annegentle 2011-10-28 10:37:52 -05:00
parent 19cab8ad01
commit 77aea7e82a
1 changed files with 8 additions and 3 deletions

View File

@ -74,8 +74,8 @@ format="SVG" scale="60"/>
public methods on one of the subclasses of NetworkManager. Different networking
strategies are available to the service by changing the network_manager flag to
FlatManager, FlatDHCPManager, or VlanManager (default is VLAN if no other is
specified):</para>
<para><literallayout class="monospaced">nova-network --network_manager=nova.network.manager.FlatManager</literallayout></para>
specified).</para>
</listitem>
</itemizedlist>
<section xml:id="starting-images">
@ -92,7 +92,7 @@ uec-publish-tarball $image [bucket-name] [hardware-arch]</code>
<listitem>
<para>
<emphasis role="bold">Image</emphasis> : a tar.gz file that contains the
system, it's kernel and ramdisk. </para>
system, its kernel and ramdisk. </para>
</listitem>
<listitem>
<para>
@ -2063,6 +2063,11 @@ Then perform the mount. </literallayout></para>
<td>default: ''</td>
<td>IP address; Cloud controller host IP address.</td>
</tr>
<tr>
<td>--multi-host</td>
<td>default: 'false'</td>
<td>Boolean true or false; When true, it enables the system to send all network related commands to the host that the VM is on.</td>
</tr>
<tr>
<td>--network_manager</td>
<td>default: 'nova.network.manager.VlanManager'</td>