[install-guide] Modify cinder content for Kilo
Modify cinder content for Kilo as follows: 1) Mostly revert commit 1e494c3e22a24baaafcaf777d4d467eb because cinder and services that use the cinder API such as nova expect the volume service rather than the volumev2 service. 2) Reference the v2 API in the endpoint for both the volume and volumev2 services. 3) Adjust the output of the commands to verify cinder operation. 4) Adjust the output of the commands to attach a volume to an instance. 5) Change tenant to project where applicable. Change-Id: Ibac7ba7a931c889a9424ac944597b263aa16dc3b Implements: blueprint installguide-kilo
This commit is contained in:
Matthew Kassawara
parent
1921f35b37
commit
126b40f63b
@ -76,6 +76,17 @@ Repeat User Password:
|
||||
</step>
|
||||
<step>
|
||||
<para>Create the <literal>cinder</literal> service entities:</para>
|
||||
<screen><prompt>$</prompt> <userinput>openstack service create --type volume \
|
||||
--description "OpenStack Block Storage" cinder</userinput>
|
||||
<computeroutput>+-------------+----------------------------------+
|
||||
| Field | Value |
|
||||
+-------------+----------------------------------+
|
||||
| description | OpenStack Block Storage |
|
||||
| enabled | True |
|
||||
| id | 1e494c3e22a24baaafcaf777d4d467eb |
|
||||
| name | cinder |
|
||||
| type | volume |
|
||||
+-------------+----------------------------------+</computeroutput></screen>
|
||||
<screen><prompt>$</prompt> <userinput>openstack service create --type volumev2 \
|
||||
--description "OpenStack Block Storage" cinderv2</userinput>
|
||||
<computeroutput>+-------------+----------------------------------+
|
||||
@ -87,11 +98,35 @@ Repeat User Password:
|
||||
| name | cinderv2 |
|
||||
| type | volumev2 |
|
||||
+-------------+----------------------------------+</computeroutput></screen>
|
||||
<note>
|
||||
<para>The Block Storage service requires both the
|
||||
<literal>volume</literal> and <literal>volumev2</literal>
|
||||
services. However, both services use the same API
|
||||
endpoint that references the Block Storage version 2 API.</para>
|
||||
</note>
|
||||
</step>
|
||||
</substeps>
|
||||
</step>
|
||||
<step>
|
||||
<para>Create the Block Storage service API endpoint:</para>
|
||||
<para>Create the Block Storage service API endpoints:</para>
|
||||
<screen><prompt>$</prompt> <userinput>openstack endpoint create \
|
||||
--publicurl http://<replaceable>controller</replaceable>:8776/v2/%\(tenant_id\)s \
|
||||
--internalurl http://<replaceable>controller</replaceable>:8776/v2/%\(tenant_id\)s \
|
||||
--adminurl http://<replaceable>controller</replaceable>:8776/v2/%\(tenant_id\)s \
|
||||
--region regionOne \
|
||||
volume</userinput>
|
||||
<computeroutput>+--------------+-----------------------------------------+
|
||||
| Field | Value |
|
||||
+--------------+-----------------------------------------+
|
||||
| adminurl | http://controller:8776/v2/%(tenant_id)s |
|
||||
| id | d1b7291a2d794e26963b322c7f2a55a4 |
|
||||
| internalurl | http://controller:8776/v2/%(tenant_id)s |
|
||||
| publicurl | http://controller:8776/v2/%(tenant_id)s |
|
||||
| region | regionOne |
|
||||
| service_id | 1e494c3e22a24baaafcaf777d4d467eb |
|
||||
| service_name | cinder |
|
||||
| service_type | volume |
|
||||
+--------------+-----------------------------------------+</computeroutput></screen>
|
||||
<screen><prompt>$</prompt> <userinput>openstack endpoint create \
|
||||
--publicurl http://<replaceable>controller</replaceable>:8776/v2/%\(tenant_id\)s \
|
||||
--internalurl http://<replaceable>controller</replaceable>:8776/v2/%\(tenant_id\)s \
|
||||
|
||||
@ -87,10 +87,10 @@
|
||||
underlying operating system manages the devices associated with
|
||||
the volumes. By default, the LVM volume scanning tool scans the
|
||||
<literal>/dev</literal> directory for block storage devices that
|
||||
contain volumes. If tenants use LVM on their volumes, the scanning
|
||||
contain volumes. If projects use LVM on their volumes, the scanning
|
||||
tool detects these volumes and attempts to cache them which can cause
|
||||
a variety of problems with both the underlying operating system
|
||||
and tenant volumes. You must reconfigure LVM to scan only the devices
|
||||
and project volumes. You must reconfigure LVM to scan only the devices
|
||||
that contain the <literal>cinder-volume</literal> volume group. Edit
|
||||
the <filename>/etc/lvm/lvm.conf</filename> file and complete the
|
||||
following actions:</para>
|
||||
|
||||
@ -32,43 +32,50 @@
|
||||
| Binary | Host | Zone | Status | State | Updated_at | Disabled Reason |
|
||||
+------------------+------------+------+---------+-------+----------------------------+-----------------+
|
||||
| cinder-scheduler | controller | nova | enabled | up | 2014-10-18T01:30:54.000000 | None |
|
||||
| cinder-volume | block1 | nova | enabled | up | 2014-10-18T01:30:57.000000 | None |
|
||||
| cinder-volume | block1@lvm | nova | enabled | up | 2014-10-18T01:30:57.000000 | None |
|
||||
+------------------+------------+------+---------+-------+----------------------------+-----------------+</computeroutput></screen>
|
||||
</step>
|
||||
<step>
|
||||
<para>Source the <literal>demo</literal> tenant credentials to perform
|
||||
the following steps as a non-administrative tenant:</para>
|
||||
<para>Source the <literal>demo</literal> credentials to perform
|
||||
the following steps as a non-administrative project:</para>
|
||||
<screen><prompt>$</prompt> <userinput>source demo-openrc.sh</userinput></screen>
|
||||
</step>
|
||||
<step>
|
||||
<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-10-14T23:11:50.870239 |
|
||||
| display_description | None |
|
||||
| display_name | demo-volume1 |
|
||||
| encrypted | False |
|
||||
| id | 158bea89-07db-4ac2-8115-66c0d6a4bb48 |
|
||||
| metadata | {} |
|
||||
| size | 1 |
|
||||
| snapshot_id | None |
|
||||
| source_volid | None |
|
||||
| status | creating |
|
||||
| volume_type | None |
|
||||
+---------------------+--------------------------------------+</computeroutput></screen>
|
||||
<screen><prompt>$</prompt> <userinput>cinder create --name demo-volume1 1</userinput>
|
||||
<computeroutput>+---------------------------------------+--------------------------------------+
|
||||
| Property | Value |
|
||||
+---------------------------------------+--------------------------------------+
|
||||
| attachments | [] |
|
||||
| availability_zone | nova |
|
||||
| bootable | false |
|
||||
| consistencygroup_id | None |
|
||||
| created_at | 2015-04-21T23:46:08.000000 |
|
||||
| description | None |
|
||||
| encrypted | False |
|
||||
| id | 6c7a3d28-e1ef-42a0-b1f7-8d6ce9218412 |
|
||||
| metadata | {} |
|
||||
| multiattach | False |
|
||||
| name | demo-volume1 |
|
||||
| os-vol-tenant-attr:tenant_id | ab8ea576c0574b6092bb99150449b2d3 |
|
||||
| os-volume-replication:driver_data | None |
|
||||
| os-volume-replication:extended_status | None |
|
||||
| replication_status | disabled |
|
||||
| size | 1 |
|
||||
| snapshot_id | None |
|
||||
| source_volid | None |
|
||||
| status | creating |
|
||||
| user_id | 3a81e6c8103b46709ef8d141308d4c72 |
|
||||
| volume_type | None |
|
||||
+---------------------------------------+--------------------------------------+</computeroutput></screen>
|
||||
</step>
|
||||
<step>
|
||||
<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 |
|
||||
<computeroutput>+--------------------------------------+-----------+--------------+------+-------------+----------+-------------+
|
||||
| ID | Status | Name | Size | Volume Type | Bootable | Attached to |
|
||||
+--------------------------------------+-----------+--------------+------+-------------+----------+-------------+
|
||||
| 158bea89-07db-4ac2-8115-66c0d6a4bb48 | available | demo-volume1 | 1 | None | false | |
|
||||
| 6c7a3d28-e1ef-42a0-b1f7-8d6ce9218412 | available | demo-volume1 | 1 | None | false | |
|
||||
+--------------------------------------+-----------+--------------+------+-------------+----------+-------------+</computeroutput></screen>
|
||||
<para>If the status does not indicate <literal>available</literal>,
|
||||
check the logs in the <filename>/var/log/cinder</filename> directory
|
||||
|
||||
@ -282,7 +282,7 @@ $</computeroutput></screen>
|
||||
<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>
|
||||
<para>Source the <literal>demo</literal> credentials:</para>
|
||||
<screen><prompt>$</prompt> <userinput>source demo-openrc.sh</userinput></screen>
|
||||
</step>
|
||||
<step>
|
||||
@ -291,7 +291,7 @@ $</computeroutput></screen>
|
||||
<computeroutput>+--------------------------------------+-----------+--------------+------+-------------+-------------+
|
||||
| ID | Status | Display Name | Size | Volume Type | Attached to |
|
||||
+--------------------------------------+-----------+--------------+------+-------------+-------------+
|
||||
| 158bea89-07db-4ac2-8115-66c0d6a4bb48 | available | demo-volume1 | 1 | None | |
|
||||
| 158bea89-07db-4ac2-8115-66c0d6a4bb48 | available | | 1 | - | |
|
||||
+--------------------------------------+-----------+--------------+------+-------------+-------------+</computeroutput></screen>
|
||||
</step>
|
||||
<step>
|
||||
@ -317,10 +317,10 @@ $</computeroutput></screen>
|
||||
<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 |
|
||||
| 158bea89-07db-4ac2-8115-66c0d6a4bb48 | in-use | | 1 | - | 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
|
||||
<para>The ID of the <literal>demo-volume1</literal> volume should
|
||||
indicate <literal>in-use</literal> status by the ID of the
|
||||
<literal>demo-instance1</literal> instance.</para>
|
||||
</step>
|
||||
<step>
|
||||
|
||||
@ -249,7 +249,7 @@ $</computeroutput></screen>
|
||||
<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>
|
||||
<para>Source the <literal>demo</literal> credentials:</para>
|
||||
<screen><prompt>$</prompt> <userinput>source demo-openrc.sh</userinput></screen>
|
||||
</step>
|
||||
<step>
|
||||
@ -258,7 +258,7 @@ $</computeroutput></screen>
|
||||
<computeroutput>+--------------------------------------+-----------+--------------+------+-------------+-------------+
|
||||
| ID | Status | Display Name | Size | Volume Type | Attached to |
|
||||
+--------------------------------------+-----------+--------------+------+-------------+-------------+
|
||||
| 158bea89-07db-4ac2-8115-66c0d6a4bb48 | available | demo-volume1 | 1 | None | |
|
||||
| 158bea89-07db-4ac2-8115-66c0d6a4bb48 | available | | 1 | - | |
|
||||
+--------------------------------------+-----------+--------------+------+-------------+-------------+</computeroutput></screen>
|
||||
</step>
|
||||
<step>
|
||||
@ -284,10 +284,10 @@ $</computeroutput></screen>
|
||||
<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 |
|
||||
| 158bea89-07db-4ac2-8115-66c0d6a4bb48 | in-use | | 1 | - | 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
|
||||
<para>The ID of the <literal>demo-volume1</literal> volume should
|
||||
indicate <literal>in-use</literal> status by the ID of the
|
||||
<literal>demo-instance1</literal> instance.</para>
|
||||
</step>
|
||||
<step>
|
||||
|
||||
Loading…
Reference in New Issue
Block a user