openstack/openstack-manuals
Code Issues Proposed changes

Fixing a number of validation errors:

Browse Source 
listitems without para children.
Bad linked in xref (Bug #979413)
Missing xml:ids on sections

Change-Id: Id5a65a295eb9252ecbdcf03d7a4d51f8c7229e0c
This commit is contained in:
dcramer
2012-04-12 09:48:56 -05:00
parent b503b00f48
commit 18c87c0bd0
4 changed files with 23 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/src/docbkx/common/vmware.xml
View File

@@ -36,7 +36,7 @@ xml:id="vmware">
<para>Download the WSDLs from <link xlink:href="http://www.vmware.com/support/developer/vc-sdk/">http://www.vmware.com/support/developer/vc-sdk/</link> and copy the <filename>wsdl</filename> folder into
<filename>/var/lib/tomcat6/webapps</filename>.</para>
</section>
<section>
<section xml:id="VMWare_configuration_options">
<title>VMWare configuration options</title>
<para>Configure nova.conf with the following VMWare-specific config options:
</para>

5
doc/src/docbkx/openstack-compute-admin/computeconfigure.xml
View File

@@ -906,8 +906,7 @@ xenapi_remap_vbd_dev=true
several installation and configuration steps. The
<literal>libvirt_type</literal> configuration option indicates
which hypervisor will be used. Refer to <xref
linkend="hypervisor-configuration-basics"> Hypervisor
configuration basics </xref> for more details.</para>
linkend="hypervisor-configuration-basics"/> for more details.</para>
</section>
<section xml:id="configuring-authentication-authorization">
@@ -918,7 +917,7 @@ xenapi_remap_vbd_dev=true
keystone, or deprecated (which uses nova-manage commands to
create users). With additional configuration, you can use the
OpenStack Identity Service, code-named Keystone. Refer to
<xref linkend="ch_identity_mgmt">Identity Management</xref> for additional information.</para>
<xref linkend="ch-identity-mgmt-config"/> for additional information.</para>
<table rules="all">
<caption>Description of <filename>nova.conf</filename>

14
doc/src/docbkx/openstack-compute-admin/computeinterfaces.xml
View File

@@ -36,13 +36,13 @@
<itemizedlist>
<listitem>
<emphasis role="italic">Glance</emphasis>: An image store endpoint.
<para><emphasis role="italic">Glance</emphasis>: An image store endpoint.</para>
</listitem>
<listitem>
<emphasis role="italic">Swift</emphasis>: An object store endpoint.
<para><emphasis role="italic">Swift</emphasis>: An object store endpoint.</para>
</listitem>
<listitem>
<link xlink:href="http://wiki.openstack.org/Quantum">Quantum</link>: An advanced networking endpoint.
<para><link xlink:href="http://wiki.openstack.org/Quantum">Quantum</link>: An advanced networking endpoint.</para>
</listitem>
</itemizedlist>
</section>
@@ -271,11 +271,11 @@ python tools/install_venv.py
</para>
</section>
</section>
<section>
<section xml:id="Launching_Instances_using_Dashboard">
<title>Launching Instances using Dashboard</title>
<para>The Dashboard can be used to launch instances. This section explains the various steps
to be followed to launch a instance.</para>
<section>
<section xml:id="Modify_Security_Groups">
<title>Modify Security Groups</title>
<para>Before launching a VM, first modify the Security Groups rules to allow us to
ping and SSH to the instances. This is done by editing the default security group or
@@ -298,7 +298,7 @@ python tools/install_venv.py
<para>Select IP protocol ICMP and enter -1 in "From Port" and "To Port" and CIDR
0.0.0.0/0. This allows ping from any IP. If you want ping requests from particular range of IP, provide it in CIDR field.</para>
</section>
<section>
<section xml:id="Adding_Keypair">
<title>Adding Keypair</title>
<para>Next add a Keypair. Once a Keypair is added, the public key would be
downloaded. This key can be used to SSH to the launched instance.</para>
@@ -316,7 +316,7 @@ python tools/install_venv.py
</para>
<para>Once this is done, we are now all set to launch an Instance</para>
</section>
<section>
<section xml:id="Launching_Instance">
<title>Launching Instance</title>
<para>Click Images &amp; Snapshots and launch a required instance from the list of
images available.</para>

26
doc/src/docbkx/openstack-compute-admin/computenetworking.xml
View File

@@ -515,7 +515,7 @@ force_dhcp_release=True
</section>
<section xml:id="associating-public-ip">
<title>Configuring Public (Floating) IP Addresses</title>
<section>
<section xml:id="Private_and_Public_IP_Addresses">
<title>Private and Public IP Addresses</title>
<para>Every virtual instance is automatically assigned a private IP address.
You may optionally assign public IP addresses to instances. OpenStack
@@ -528,7 +528,7 @@ force_dhcp_release=True
<programlisting>public_interface=vlan100</programlisting>
<para>Restart the nova-network service if you change nova.conf while the service is running.</para>
</section>
<section>
<section xml:id="Creating_a_List_of_Available_Floating_IP_Addresses">
<title>Creating a List of Available Floating IP Addresses</title>
<para>Nova maintains a list of floating IP addresses that are
available for assigning to instances. Use the <command>nova-manage floating create</command> command
@@ -540,26 +540,26 @@ force_dhcp_release=True
<para>The following nova-manage commands apply to floating IPs.</para>
<itemizedlist>
<listitem>
<command>nova-manage floating list</command>: List the floating IP addresses in the
pool.
<para><command>nova-manage floating list</command>: List the floating IP addresses in the
pool.</para>
</listitem>
<listitem>
<command>nova-manage floating create [cidr]</command>: Create specific
floating IPs for either a single address or a subnet.
<para><command>nova-manage floating create [cidr]</command>: Create specific
floating IPs for either a single address or a subnet.</para>
</listitem>
<listitem>
<command>nova-manage floating delete [cidr]</command>: Remove floating IP
addresses using the same parameters as the create command.
<para><command>nova-manage floating delete [cidr]</command>: Remove floating IP
addresses using the same parameters as the create command.</para>
</listitem>
</itemizedlist>
</section>
<section>
<section xml:id="Adding_a_Floating_IP_to_an_Instance">
<title>Adding a Floating IP to an Instance</title>
<para>Adding a floating IP to an instance is a two step process:</para>
<orderedlist>
<listitem><command>nova floating-ip-create</command>: Allocate a floating IP address from the list of available addresses.</listitem>
<listitem><command>nova add-floating-ip</command>: Add an allocated floating IP address to a running instance.</listitem>
<listitem><para><command>nova floating-ip-create</command>: Allocate a floating IP address from the list of available addresses.</para></listitem>
<listitem><para><command>nova add-floating-ip</command>: Add an allocated floating IP address to a running instance.</para></listitem>
</orderedlist>
<para>Here's an example of how to add a floating IP to a running
@@ -584,7 +584,7 @@ force_dhcp_release=True
</screen>
</section>
<section>
<section xml:id="Automatically_adding_floating_IPs">
<title>Automatically adding floating IPs</title>
<para>The nova-network service can be configured to automatically
allocate and assign a floating IP address to virtual instances when they are
@@ -598,7 +598,7 @@ auto_assign_floating_ip=True
IP addresses have already been allocated, the
<command>nova boot</command> command will fail with an error.</para>
</section>
<section>
<section xml:id="Troubleshooting">
<title>Troubleshooting</title>
<para>If you aren't able to reach your instances via the floating IP
address, make sure the default security group allows ICMP (ping) and SSH (port 22),