Edits in admin-guide-cloud
Move all blockstorage related section files into its own subdirectory like it is done for other section files. Follow conventions for service names/project names and capitalization. Change-Id: Ibaa14ca926975c37305f3a08fa1f4e7d50eea605
This commit is contained in:
Andreas Jaeger
parent
d87badc476
commit
469898a451
@ -1,6 +1,6 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE section [
|
||||
<!ENTITY % openstack SYSTEM "../common/entities/openstack.ent">
|
||||
<!ENTITY % openstack SYSTEM "../../common/entities/openstack.ent">
|
||||
%openstack;
|
||||
]>
|
||||
<section xml:id="backup-block-storage-disks"
|
||||
@ -1,6 +1,6 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE section [
|
||||
<!ENTITY % openstack SYSTEM "../common/entities/openstack.ent">
|
||||
<!ENTITY % openstack SYSTEM "../../common/entities/openstack.ent">
|
||||
%openstack;
|
||||
]>
|
||||
<section xml:id="section_ts_cinder_config"
|
||||
@ -18,4 +18,3 @@
|
||||
storage server.</para>
|
||||
</section>
|
||||
</section>
|
||||
|
||||
@ -19,8 +19,8 @@
|
||||
<command>nova-attach</command> command fails when you
|
||||
use the <code>vdb</code>, <code>vdc</code>, or
|
||||
<code>vdd</code> device names:</para>
|
||||
<screen><prompt>#</prompt> <userinput>ls -al /dev/disk/by-path/
|
||||
total 0
|
||||
<screen><prompt>#</prompt> <userinput>ls -al /dev/disk/by-path/</userinput>
|
||||
<computeroutput>total 0
|
||||
drwxr-xr-x 2 root root 200 2012-08-29 17:33 .
|
||||
drwxr-xr-x 5 root root 100 2012-08-29 17:33 ..
|
||||
lrwxrwxrwx 1 root root 9 2012-08-29 17:33 pci-0000:00:04.0-virtio-pci-virtio0 -> ../../vda
|
||||
@ -30,7 +30,7 @@ lrwxrwxrwx 1 root root 10 2012-08-29 17:33 pci-0000:00:04.0-virtio-pci-virtio0-p
|
||||
lrwxrwxrwx 1 root root 9 2012-08-29 17:33 pci-0000:00:06.0-virtio-pci-virtio2 -> ../../vdb
|
||||
lrwxrwxrwx 1 root root 9 2012-08-29 17:33 pci-0000:00:08.0-virtio-pci-virtio3 -> ../../vdc
|
||||
lrwxrwxrwx 1 root root 9 2012-08-29 17:33 pci-0000:00:09.0-virtio-pci-virtio4 -> ../../vdd
|
||||
lrwxrwxrwx 1 root root 10 2012-08-29 17:33 pci-0000:00:09.0-virtio-pci-virtio4-part1 -> ../../vdd1</userinput></screen>
|
||||
lrwxrwxrwx 1 root root 10 2012-08-29 17:33 pci-0000:00:09.0-virtio-pci-virtio4-part1 -> ../../vdd1</computeroutput></screen>
|
||||
<para>You might also have this problem after attaching and
|
||||
detaching the same volume from the same VM with the same
|
||||
mount point multiple times. In this case, restart the KVM
|
||||
@ -19,4 +19,3 @@ NON_EXISTENT_HOST - HOST '10' was not found to caller.</programlisting>
|
||||
storage server.</para>
|
||||
</section>
|
||||
</section>
|
||||
|
||||
@ -15,4 +15,3 @@
|
||||
domain that the volume was created in.</para>
|
||||
</section>
|
||||
</section>
|
||||
|
||||
@ -99,12 +99,13 @@
|
||||
and labels it as LVM. The network uses the
|
||||
<literal>FlatManager</literal> and
|
||||
<literal>NetworkManager</literal> settings for
|
||||
OpenStack Compute (Nova).</para>
|
||||
OpenStack Compute.</para>
|
||||
<para>The network mode does not interfere with the way cinder
|
||||
works, but you must set up networking for cinder to work.
|
||||
For details, see <xref linkend="ch_networking"/>.</para>
|
||||
<para>To set up Compute to use volumes, ensure that Block
|
||||
Storage is installed along with lvm2. This guide describes
|
||||
Storage is installed along with <package>lvm2</package>. This guide
|
||||
describes
|
||||
how to troubleshoot your installation and back up your
|
||||
Compute volumes.</para>
|
||||
<section xml:id="boot-from-volume">
|
||||
@ -119,32 +120,32 @@
|
||||
Guide</citetitle></link>.</para>
|
||||
</section>
|
||||
<?hard-pagebreak?>
|
||||
<xi:include href="section_nfs_backend.xml"/>
|
||||
<xi:include href="section_glusterfs_backend.xml"/>
|
||||
<xi:include href="section_multi_backend.xml"/>
|
||||
<xi:include href="section_backup-block-storage-disks.xml"/>
|
||||
<xi:include href="section_volume-migration.xml"/>
|
||||
<xi:include href="section_glusterfs_removal.xml"/>
|
||||
<xi:include href="section_volume-backups.xml"/>
|
||||
<xi:include href="section_volume-backups-export-import.xml"/>
|
||||
<xi:include href="blockstorage/section_nfs_backend.xml"/>
|
||||
<xi:include href="blockstorage/section_glusterfs_backend.xml"/>
|
||||
<xi:include href="blockstorage/section_multi_backend.xml"/>
|
||||
<xi:include href="blockstorage/section_backup-block-storage-disks.xml"/>
|
||||
<xi:include href="blockstorage/section_volume-migration.xml"/>
|
||||
<xi:include href="blockstorage/section_glusterfs_removal.xml"/>
|
||||
<xi:include href="blockstorage/section_volume-backups.xml"/>
|
||||
<xi:include href="blockstorage/section_volume-backups-export-import.xml"/>
|
||||
</section>
|
||||
<section xml:id="troubleshooting-cinder-install">
|
||||
<title>Troubleshoot your installation</title>
|
||||
<para>This section provides useful tips to help troubleshoot
|
||||
your Block Storage installation.</para>
|
||||
<xi:include href="section_ts_cinder_config.xml"/>
|
||||
<xi:include href="section_ts_multipath_warn.xml"/>
|
||||
<xi:include href="section_ts_vol_attach_miss_sg_scan.xml"/>
|
||||
<xi:include href="blockstorage/section_ts_cinder_config.xml"/>
|
||||
<xi:include href="blockstorage/section_ts_multipath_warn.xml"/>
|
||||
<xi:include href="blockstorage/section_ts_vol_attach_miss_sg_scan.xml"/>
|
||||
<xi:include
|
||||
href="section_ts_HTTP_bad_req_in_cinder_vol_log.xml"/>
|
||||
<xi:include href="section_ts_duplicate_3par_host.xml"/>
|
||||
href="blockstorage/section_ts_HTTP_bad_req_in_cinder_vol_log.xml"/>
|
||||
<xi:include href="blockstorage/section_ts_duplicate_3par_host.xml"/>
|
||||
<xi:include
|
||||
href="section_ts_failed_attach_vol_after_detach.xml"/>
|
||||
href="blockstorage/section_ts_failed_attach_vol_after_detach.xml"/>
|
||||
<xi:include
|
||||
href="section_ts_failed_attach_vol_no_sysfsutils.xml"/>
|
||||
<xi:include href="section_ts_failed_connect_vol_FC_SAN.xml"/>
|
||||
<xi:include href="section_ts_no_emulator_x86_64.xml"/>
|
||||
<xi:include href="section_ts_non_existent_host.xml"/>
|
||||
<xi:include href="section_ts_non_existent_vlun.xml"/>
|
||||
href="blockstorage/section_ts_failed_attach_vol_no_sysfsutils.xml"/>
|
||||
<xi:include href="blockstorage/section_ts_failed_connect_vol_FC_SAN.xml"/>
|
||||
<xi:include href="blockstorage/section_ts_no_emulator_x86_64.xml"/>
|
||||
<xi:include href="blockstorage/section_ts_non_existent_host.xml"/>
|
||||
<xi:include href="blockstorage/section_ts_non_existent_vlun.xml"/>
|
||||
</section>
|
||||
</chapter>
|
||||
|
||||
@ -4,7 +4,7 @@
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
|
||||
xml:id="ch-identity-mgmt-config">
|
||||
<title>Identity management</title>
|
||||
<para>The OpenStack Identity Service, code-named Keystone, is the
|
||||
<para>The OpenStack Identity Service, code-named keystone, is the
|
||||
default identity management system for OpenStack. After you
|
||||
install the Identity Service, you configure it through the
|
||||
<filename>etc/keystone.conf</filename> configuration file and,
|
||||
|
||||
@ -42,8 +42,8 @@
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>OpenStack Controller host - controlnode</td>
|
||||
<td><para>Runs the Neutron, Keystone, and Nova
|
||||
<td>OpenStack controller host - controlnode</td>
|
||||
<td><para>Runs the Networking, Identity, and Compute
|
||||
services that are required to deploy VMs.
|
||||
The node must have at least one network
|
||||
interface that is connected to the
|
||||
@ -56,8 +56,9 @@
|
||||
</tr>
|
||||
<tr>
|
||||
<td>HostA</td>
|
||||
<td>Runs Nova compute, the Neutron L2 agent and
|
||||
DHCP agent</td>
|
||||
<td>Runs <systemitem
|
||||
class="service">nova-compute</systemitem>, the
|
||||
Neutron L2 agent and DHCP agent</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>HostB</td>
|
||||
@ -69,7 +70,7 @@
|
||||
<section xml:id="multi_agent_demo_configuration">
|
||||
<title>Configuration</title>
|
||||
<procedure>
|
||||
<title>controlnode: Neutron Server</title>
|
||||
<title>controlnode: neutron server</title>
|
||||
<step>
|
||||
<para>Neutron configuration file
|
||||
<filename>/etc/neutron/neutron.conf</filename>:</para>
|
||||
@ -94,7 +95,7 @@ physical_interface_mappings = physnet1:eth0</programlisting>
|
||||
</step>
|
||||
</procedure>
|
||||
<procedure>
|
||||
<title>HostA and HostB: L2 Agent</title>
|
||||
<title>HostA and Hostb: L2 agent</title>
|
||||
<step>
|
||||
<para>Neutron configuration file
|
||||
<filename>/etc/neutron/neutron.conf</filename>:</para>
|
||||
@ -132,7 +133,7 @@ firewall_driver=nova.virt.firewall.NoopFirewallDriver</programlisting>
|
||||
</step>
|
||||
</procedure>
|
||||
<procedure>
|
||||
<title>HostA and HostB: DHCP Agent</title>
|
||||
<title>HostA and HostB: DHCP agent</title>
|
||||
<step>
|
||||
<para>Update the DHCP configuration file
|
||||
<filename>/etc/neutron/dhcp_agent.ini</filename>:</para>
|
||||
@ -149,7 +150,7 @@ interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver</programl
|
||||
<note>
|
||||
<para>Ensure that the following environment variables are
|
||||
set. These are used by the various clients to access
|
||||
Keystone.</para>
|
||||
the Identity Service.</para>
|
||||
<programlisting language="bash">export OS_USERNAME=admin
|
||||
export OS_PASSWORD=adminpassword
|
||||
export OS_TENANT_NAME=admin
|
||||
|
||||
@ -1155,7 +1155,7 @@
|
||||
Then, when ports are created on that network they are automatically created and
|
||||
associated with the specific queue size that was associated with the network.
|
||||
Because one size queue for a every port on a network might not be optimal, a
|
||||
scaling factor from the Nova flavor 'rxtx_factor' is passed in from Compute when
|
||||
scaling factor from the nova flavor 'rxtx_factor' is passed in from Compute when
|
||||
creating the port to scale the queue.</para>
|
||||
<para>Lastly, if you want to set a specific baseline QoS policy for the amount of
|
||||
bandwidth a single port can use (unless a network queue is specified with the
|
||||
@ -1467,7 +1467,7 @@
|
||||
</section>
|
||||
<section xml:id="section_bigswitch_extensions">
|
||||
<title>Big Switch plug-in extensions</title>
|
||||
<para>This section explains the Big Switch Neutron plug-in-specific extension.</para>
|
||||
<para>This section explains the Big Switch neutron plug-in-specific extension.</para>
|
||||
<section xml:id="section_bigswitch_extension_routerrules">
|
||||
<title>Big Switch router rules</title>
|
||||
<para>Big Switch allows router rules to be added to each tenant router. These rules
|
||||
@ -1480,7 +1480,7 @@
|
||||
<para>Each tenant router has a set of router rules associated with it. Each
|
||||
router rule has the attributes in this table. Router rules and their
|
||||
attributes can be set using the <command>neutron router-update</command>
|
||||
command, through the Horizon interface or the Neutron API.</para>
|
||||
command, through the horizon interface or the Networking API.</para>
|
||||
<table rules="all">
|
||||
<caption>Big Switch Router rule attributes</caption>
|
||||
<col width="20%"/>
|
||||
|
||||
@ -75,11 +75,11 @@
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Networking relies on the Identity service
|
||||
(Keystone) for the authentication and
|
||||
(keystone) for the authentication and
|
||||
authorization of all API requests.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Compute (Nova) interacts with Networking
|
||||
<para>Compute (nova) interacts with Networking
|
||||
through calls to its standard API. As part of
|
||||
creating a VM, the <systemitem class="service"
|
||||
>nova-compute</systemitem> service
|
||||
@ -88,7 +88,7 @@
|
||||
network.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>The Dashboard (Horizon) integrates with the
|
||||
<para>The dashboard (horizon) integrates with the
|
||||
Networking API, enabling administrators and
|
||||
tenant users to create and manage network
|
||||
services through a web-based GUI.</para>
|
||||
|
||||
@ -4,7 +4,7 @@
|
||||
xmlns:xi="http://www.w3.org/2001/XInclude"
|
||||
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
|
||||
<title>Introduction to Networking</title>
|
||||
<para>The Networking service, code-named Neutron, provides an API
|
||||
<para>The Networking service, code-named neutron, provides an API
|
||||
that lets you define network connectivity and addressing in
|
||||
the cloud. The Networking service enables operators to
|
||||
leverage different networking technologies to power their
|
||||
@ -1479,8 +1479,8 @@ interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver</programlist
|
||||
<para>Install the agent by running:</para>
|
||||
<screen><prompt>#</prompt> <userinput>apt-get install neutron-metering-agent</userinput></screen>
|
||||
<note><title>Package name prior to Icehouse</title>
|
||||
<para>In releases of Neutron prior to Icehouse, this
|
||||
package was named neutron-plugin-metering-agent.</para>
|
||||
<para>In releases of neutron prior to Icehouse, this
|
||||
package was named <package>neutron-plugin-metering-agent</package>.</para>
|
||||
</note>
|
||||
</step>
|
||||
<step>
|
||||
|
||||
Loading…
Reference in New Issue
Block a user