From 97f43de604227948f1d9bf4aa829b5386934a111 Mon Sep 17 00:00:00 2001 From: Matthew Kassawara Date: Tue, 14 Oct 2014 21:10:58 -0500 Subject: [PATCH] Update cinder content for Juno 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 --- doc/install-guide/section_cinder-verify.xml | 43 +++++----- .../section_launch-instance-neutron.xml | 78 +++++++++++++++++++ .../section_launch-instance-nova.xml | 78 +++++++++++++++++++ 3 files changed, 181 insertions(+), 18 deletions(-) diff --git a/doc/install-guide/section_cinder-verify.xml b/doc/install-guide/section_cinder-verify.xml index 8c538a26bb..b5b013896f 100644 --- a/doc/install-guide/section_cinder-verify.xml +++ b/doc/install-guide/section_cinder-verify.xml @@ -4,32 +4,35 @@ xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="cinder-verify"> - Verify the Block Storage installation - To verify that the Block Storage is installed and configured properly, - create a new volume. + Verify operation + This section describes how to verify operation of the Block Storage + service by creating a volume. For more information about how to manage volumes, see the OpenStack User Guide. + >OpenStack User Guide. + + Perform these commands on the controller node. + - Source the demo-openrc.sh file: + Source the demo tenant credentials to perform + these steps as a non-administrative tenant: $ source demo-openrc.sh - - Use the cinder create command to create a new volume: - $ cinder create --display-name myVolume 1 + Create a 1 GB volume: + $ cinder create --display-name demo-volume1 1 +---------------------+--------------------------------------+ | 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 @@ +---------------------+--------------------------------------+ - Make sure that the volume has been correctly created with the - cinder list command: + Verify creation and availability of the volume: $ cinder list --------------------------------------+-----------+--------------+------+-------------+----------+-------------+ | 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 | | +--------------------------------------+-----------+--------------+------+-------------+----------+-------------+ - If the status value is not available, the volume - creation failed. Check the log files in the - /var/log/cinder/ directory on the controller and - volume nodes to get information about the failure. + If the status does not indicate available, + check the logs in the /var/log/cinder directory + on the controller and volume nodes for more information. + + The + launch an instance + chapter includes instructions for attaching this volume to an + instance. + diff --git a/doc/install-guide/section_launch-instance-neutron.xml b/doc/install-guide/section_launch-instance-neutron.xml index 60963a513f..68e6577bbc 100644 --- a/doc/install-guide/section_launch-instance-neutron.xml +++ b/doc/install-guide/section_launch-instance-neutron.xml @@ -285,6 +285,84 @@ $ + + To attach a Block Storage volume to your instance + If your environment includes the Block Storage service, you can + attach a volume to the instance. + + Source the demo tenant credentials: + $ source demo-openrc.sh + + + List volumes: + $ nova volume-list ++--------------------------------------+-----------+--------------+------+-------------+-------------+ +| ID | Status | Display Name | Size | Volume Type | Attached to | ++--------------------------------------+-----------+--------------+------+-------------+-------------+ +| 158bea89-07db-4ac2-8115-66c0d6a4bb48 | available | demo-volume1 | 1 | None | | ++--------------------------------------+-----------+--------------+------+-------------+-------------+ + + + Attach the demo-volume1 volume to + the demo-instance1 instance: + $ nova volume-attach demo-instance1 158bea89-07db-4ac2-8115-66c0d6a4bb48 ++----------+--------------------------------------+ +| Property | Value | ++----------+--------------------------------------+ +| device | /dev/vdb | +| id | 158bea89-07db-4ac2-8115-66c0d6a4bb48 | +| serverId | 05682b91-81a1-464c-8f40-8b3da7ee92c5 | +| volumeId | 158bea89-07db-4ac2-8115-66c0d6a4bb48 | ++----------+--------------------------------------+ + + You must reference volumes using the IDs instead of + names. + + + + List volumes: + $ nova volume-list ++--------------------------------------+-----------+--------------+------+-------------+--------------------------------------+ +| 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 | ++--------------------------------------+-----------+--------------+------+-------------+--------------------------------------+ + The demo-volume1 volume status should indicate + in-use by the ID of the + demo-instance1 instance. + + + Access your instance using SSH from the controller node or any + host on the external network and use the fdisk + command to verify presence of the volume as the + /dev/vdb block storage device: + $ ssh cirros@203.0.113.102 +$ 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 + + You must create a partition table and file system to use + the volume. + + + If your instance does not launch or seem to work as you expect, see the OpenStack Operations Guide for more diff --git a/doc/install-guide/section_launch-instance-nova.xml b/doc/install-guide/section_launch-instance-nova.xml index 2c57fe788f..a59e87b2a3 100644 --- a/doc/install-guide/section_launch-instance-nova.xml +++ b/doc/install-guide/section_launch-instance-nova.xml @@ -244,6 +244,84 @@ $ + + To attach a Block Storage volume to your instance + If your environment includes the Block Storage service, you can + attach a volume to the instance. + + Source the demo tenant credentials: + $ source demo-openrc.sh + + + List volumes: + $ nova volume-list ++--------------------------------------+-----------+--------------+------+-------------+-------------+ +| ID | Status | Display Name | Size | Volume Type | Attached to | ++--------------------------------------+-----------+--------------+------+-------------+-------------+ +| 158bea89-07db-4ac2-8115-66c0d6a4bb48 | available | demo-volume1 | 1 | None | | ++--------------------------------------+-----------+--------------+------+-------------+-------------+ + + + Attach the demo-volume1 volume to + the demo-instance1 instance: + $ nova volume-attach demo-instance1 158bea89-07db-4ac2-8115-66c0d6a4bb48 ++----------+--------------------------------------+ +| Property | Value | ++----------+--------------------------------------+ +| device | /dev/vdb | +| id | 158bea89-07db-4ac2-8115-66c0d6a4bb48 | +| serverId | 45ea195c-c469-43eb-83db-1a663bbad2fc | +| volumeId | 158bea89-07db-4ac2-8115-66c0d6a4bb48 | ++----------+--------------------------------------+ + + You must reference volumes using the IDs instead of + names. + + + + List volumes: + $ nova volume-list ++--------------------------------------+-----------+--------------+------+-------------+--------------------------------------+ +| 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 | ++--------------------------------------+-----------+--------------+------+-------------+--------------------------------------+ + The demo-volume1 volume status should indicate + in-use by the ID of the + demo-instance1 instance. + + + Access your instance using SSH from the controller node or any + host on the external network and use the fdisk + command to verify presence of the volume as the + /dev/vdb block storage device: + $ ssh cirros@203.0.113.102 +$ 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 + + You must create a partition table and file system to use + the volume. + + + If your instance does not launch or seem to work as you expect, see the OpenStack Operations Guide for more