openstack/openstack-manuals
Code Issues Proposed changes

Update cinder content for Juno

Browse Source 
I updated the cinder content in the installation guide for Juno
as follows:

1) Clarified verify operation section.
2) Added instructions for attaching a volume to an instance. We
   create it, so might as well complete the process and attach
   it to an instance.

Change-Id: I658193599bb7ab91407e0180f686e2e3c6b2bf61
This commit is contained in:
Matthew Kassawara
2014-10-14 21:10:58 -05:00
parent baf833777d
commit 97f43de604
3 changed files with 181 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

43
doc/install-guide/section_cinder-verify.xml
View File

@@ -4,32 +4,35 @@
xmlns:xlink="http://www.w3.org/1999/xlink"
version="5.0"
xml:id="cinder-verify">
<title>Verify the Block Storage installation</title>
<para>To verify that the Block Storage is installed and configured properly,
create a new volume.</para>
<title>Verify operation</title>
<para>This section describes how to verify operation of the Block Storage
service by creating a volume.</para>
<para>For more information about how to manage volumes, see the <link
xlink:href="http://docs.openstack.org/user-guide/content/index.html"
><citetitle>OpenStack User Guide</citetitle></link>.</para>
><citetitle>OpenStack User Guide</citetitle></link>.</para>
<note>
<para>Perform these commands on the controller node.</para>
</note>
<procedure>
<step>
<para>Source the <filename>demo-openrc.sh</filename> file:</para>
<para>Source the <literal>demo</literal> tenant credentials to perform
these steps as a non-administrative tenant:</para>
<screen><prompt>$</prompt> <userinput>source demo-openrc.sh</userinput></screen>
</step>
<step>
<para>Use the <command>cinder create</command> command to create a new volume:</para>
<screen><prompt>$</prompt> <userinput>cinder create --display-name myVolume 1</userinput>
<para>Create a 1 GB volume:</para>
<screen><prompt>$</prompt> <userinput>cinder create --display-name demo-volume1 1</userinput>
<computeroutput>+---------------------+--------------------------------------+
| Property | Value |
+---------------------+--------------------------------------+
| attachments | [] |
| availability_zone | nova |
| bootable | false |
| created_at | 2014-04-17T10:28:19.615050 |
| created_at | 2014-10-14T23:11:50.870239 |
| display_description | None |
| display_name | myVolume |
| display_name | demo-volume1 |
| encrypted | False |
| id | 5e691b7b-12e3-40b6-b714-7f17550db5d1 |
| id | 158bea89-07db-4ac2-8115-66c0d6a4bb48 |
| metadata | {} |
| size | 1 |
| snapshot_id | None |
@@ -39,18 +42,22 @@
+---------------------+--------------------------------------+</computeroutput></screen>
</step>
<step>
<para>Make sure that the volume has been correctly created with the
<command>cinder list</command> command:</para>
<para>Verify creation and availability of the volume:</para>
<screen><prompt>$</prompt> <userinput>cinder list</userinput>
<computeroutput>--------------------------------------+-----------+--------------+------+-------------+----------+-------------+
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+-----------+--------------+------+-------------+----------+-------------+
| 5e691b7b-12e3-40b6-b714-7f17550db5d1 | available | myVolume | 1 | None | false | |
| 158bea89-07db-4ac2-8115-66c0d6a4bb48 | available | demo-volume1 | 1 | None | false | |
+--------------------------------------+-----------+--------------+------+-------------+----------+-------------+</computeroutput></screen>
<para>If the status value is not <literal>available</literal>, the volume
creation failed. Check the log files in the
<filename>/var/log/cinder/</filename> directory on the controller and
volume nodes to get information about the failure.</para>
<para>If the status does not indicate <literal>available</literal>,
check the logs in the <filename>/var/log/cinder</filename> directory
on the controller and volume nodes for more information.</para>
<note>
<para>The
<link linkend="launch-instance">launch an instance</link>
chapter includes instructions for attaching this volume to an
instance.</para>
</note>
</step>
</procedure>
</section>

78
doc/install-guide/section_launch-instance-neutron.xml
View File

@@ -285,6 +285,84 @@ $</computeroutput></screen>
</note>
</step>
</procedure>
<procedure xml:id="launch-instance-neutron-volumeattach">
<title>To attach a Block Storage volume to your instance</title>
<para>If your environment includes the Block Storage service, you can
attach a volume to the instance.</para>
<step>
<para>Source the <literal>demo</literal> tenant credentials:</para>
<screen><prompt>$</prompt> <userinput>source demo-openrc.sh</userinput></screen>
</step>
<step>
<para>List volumes:</para>
<screen><prompt>$</prompt> <userinput>nova volume-list</userinput>
<computeroutput>+--------------------------------------+-----------+--------------+------+-------------+-------------+
| ID | Status | Display Name | Size | Volume Type | Attached to |
+--------------------------------------+-----------+--------------+------+-------------+-------------+
| 158bea89-07db-4ac2-8115-66c0d6a4bb48 | available | demo-volume1 | 1 | None | |
+--------------------------------------+-----------+--------------+------+-------------+-------------+</computeroutput></screen>
</step>
<step>
<para>Attach the <literal>demo-volume1</literal> volume to
the <literal>demo-instance1</literal> instance:</para>
<screen><prompt>$</prompt> <userinput>nova volume-attach demo-instance1 158bea89-07db-4ac2-8115-66c0d6a4bb48</userinput>
<computeroutput>+----------+--------------------------------------+
| Property | Value |
+----------+--------------------------------------+
| device | /dev/vdb |
| id | 158bea89-07db-4ac2-8115-66c0d6a4bb48 |
| serverId | 05682b91-81a1-464c-8f40-8b3da7ee92c5 |
| volumeId | 158bea89-07db-4ac2-8115-66c0d6a4bb48 |
+----------+--------------------------------------+</computeroutput></screen>
<note>
<para>You must reference volumes using the IDs instead of
names.</para>
</note>
</step>
<step>
<para>List volumes:</para>
<screen><prompt>$</prompt> <userinput>nova volume-list</userinput>
<computeroutput>+--------------------------------------+-----------+--------------+------+-------------+--------------------------------------+
| ID | Status | Display Name | Size | Volume Type | Attached to |
+--------------------------------------+-----------+--------------+------+-------------+--------------------------------------+
| 158bea89-07db-4ac2-8115-66c0d6a4bb48 | in-use | demo-volume1 | 1 | None | 05682b91-81a1-464c-8f40-8b3da7ee92c5 |
+--------------------------------------+-----------+--------------+------+-------------+--------------------------------------+</computeroutput></screen>
<para>The <literal>demo-volume1</literal> volume status should indicate
<literal>in-use</literal> by the ID of the
<literal>demo-instance1</literal> instance.</para>
</step>
<step>
<para>Access your instance using SSH from the controller node or any
host on the external network and use the <command>fdisk</command>
command to verify presence of the volume as the
<literal>/dev/vdb</literal> block storage device:</para>
<screen><prompt>$</prompt> <userinput>ssh cirros@203.0.113.102</userinput>
<computeroutput>$ sudo fdisk -l
Disk /dev/vda: 1073 MB, 1073741824 bytes
255 heads, 63 sectors/track, 130 cylinders, total 2097152 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/vda1 * 16065 2088449 1036192+ 83 Linux
Disk /dev/vdb: 1073 MB, 1073741824 bytes
16 heads, 63 sectors/track, 2080 cylinders, total 2097152 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/vdb doesn't contain a valid partition table</computeroutput></screen>
<note>
<para>You must create a partition table and file system to use
the volume.</para>
</note>
</step>
</procedure>
<para>If your instance does not launch or seem to work as you expect, see the
<link xlink:href="http://docs.openstack.org/ops">
<citetitle>OpenStack Operations Guide</citetitle></link> for more

78
doc/install-guide/section_launch-instance-nova.xml
View File

@@ -244,6 +244,84 @@ $</computeroutput></screen>
</note>
</step>
</procedure>
<procedure xml:id="launch-instance-nova-volumeattach">
<title>To attach a Block Storage volume to your instance</title>
<para>If your environment includes the Block Storage service, you can
attach a volume to the instance.</para>
<step>
<para>Source the <literal>demo</literal> tenant credentials:</para>
<screen><prompt>$</prompt> <userinput>source demo-openrc.sh</userinput></screen>
</step>
<step>
<para>List volumes:</para>
<screen><prompt>$</prompt> <userinput>nova volume-list</userinput>
<computeroutput>+--------------------------------------+-----------+--------------+------+-------------+-------------+
| ID | Status | Display Name | Size | Volume Type | Attached to |
+--------------------------------------+-----------+--------------+------+-------------+-------------+
| 158bea89-07db-4ac2-8115-66c0d6a4bb48 | available | demo-volume1 | 1 | None | |
+--------------------------------------+-----------+--------------+------+-------------+-------------+</computeroutput></screen>
</step>
<step>
<para>Attach the <literal>demo-volume1</literal> volume to
the <literal>demo-instance1</literal> instance:</para>
<screen><prompt>$</prompt> <userinput>nova volume-attach demo-instance1 158bea89-07db-4ac2-8115-66c0d6a4bb48</userinput>
<computeroutput>+----------+--------------------------------------+
| Property | Value |
+----------+--------------------------------------+
| device | /dev/vdb |
| id | 158bea89-07db-4ac2-8115-66c0d6a4bb48 |
| serverId | 45ea195c-c469-43eb-83db-1a663bbad2fc |
| volumeId | 158bea89-07db-4ac2-8115-66c0d6a4bb48 |
+----------+--------------------------------------+</computeroutput></screen>
<note>
<para>You must reference volumes using the IDs instead of
names.</para>
</note>
</step>
<step>
<para>List volumes:</para>
<screen><prompt>$</prompt> <userinput>nova volume-list</userinput>
<computeroutput>+--------------------------------------+-----------+--------------+------+-------------+--------------------------------------+
| ID | Status | Display Name | Size | Volume Type | Attached to |
+--------------------------------------+-----------+--------------+------+-------------+--------------------------------------+
| 158bea89-07db-4ac2-8115-66c0d6a4bb48 | in-use | demo-volume1 | 1 | None | 45ea195c-c469-43eb-83db-1a663bbad2fc |
+--------------------------------------+-----------+--------------+------+-------------+--------------------------------------+</computeroutput></screen>
<para>The <literal>demo-volume1</literal> volume status should indicate
<literal>in-use</literal> by the ID of the
<literal>demo-instance1</literal> instance.</para>
</step>
<step>
<para>Access your instance using SSH from the controller node or any
host on the external network and use the <command>fdisk</command>
command to verify presence of the volume as the
<literal>/dev/vdb</literal> block storage device:</para>
<screen><prompt>$</prompt> <userinput>ssh cirros@203.0.113.102</userinput>
<computeroutput>$ sudo fdisk -l
Disk /dev/vda: 1073 MB, 1073741824 bytes
255 heads, 63 sectors/track, 130 cylinders, total 2097152 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/vda1 * 16065 2088449 1036192+ 83 Linux
Disk /dev/vdb: 1073 MB, 1073741824 bytes
16 heads, 63 sectors/track, 2080 cylinders, total 2097152 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/vdb doesn't contain a valid partition table</computeroutput></screen>
<note>
<para>You must create a partition table and file system to use
the volume.</para>
</note>
</step>
</procedure>
<para>If your instance does not launch or seem to work as you expect, see the
<link xlink:href="http://docs.openstack.org/ops">
<citetitle>OpenStack Operations Guide</citetitle></link> for more