Chapter 3. Performing basic operations with the Block Storage service (cinder)

Procedure

1. In the dashboard, select Project > Compute > Volumes.

2. Click Create Volume, and edit the following fields:

   Field	Description
   Volume name	Name of the volume.
   Description	Optional, short description of the volume.
   Type	Optional volume type (see Section 2.3, “Group volume configuration with volume types”). If you have multiple Block Storage back ends, you can use this to select a specific back end. See Section 2.10, “Specifying back ends for volume creation”.
   Size (GB)	Volume size (in gigabytes). If you want to create an encrypted volume from an unencrypted image, you must ensure that the volume size is larger than the image size so that the encryption data does not truncate the volume data.
   Availability Zone	Availability zones (logical server groups), along with host aggregates, are a common method for segregating resources within OpenStack. Availability zones are defined during installation. For more information about availability zones and host aggregates, see Creating and managing host aggregates in the Configuring the Compute Service for Instance Creation guide.

3. Specify a Volume Source:

   Source	Description
   No source, empty volume	The volume is empty and does not contain a file system or partition table.
   Snapshot	Use an existing snapshot as a volume source. If you select this option, a new Use snapshot as a source list opens; you can then choose a snapshot from the list. If you want to create a new volume from a snapshot of an encrypted volume, you must ensure that the new volume is at least 1GB larger than the old volume. For more information about volume snapshots, see Section 4.1, “Creating, using, and deleting volume snapshots”.
   Image	Use an existing image as a volume source. If you select this option, a new Use snapshot as a source list opens; you can then choose an image from the list.
   Volume	Use an existing volume as a volume source. If you select this option, a new Use snapshot as a source list opens; you can then choose a volume from the list.

4. Click Create Volume. After the volume is created, its name appears in the Volumes table.

Procedure

1. In the dashboard, select Project > Compute > Volumes.
2. Select the volume’s Edit Volume button.
3. Edit the volume name or description as required.
4. Click Edit Volume to save your changes.

Procedure

1. List the volumes to retrieve the ID of the volume you want to extend:

   $ cinder list

2. To resize the volume, run the following commands to specify the correct API microversion, then pass the volume ID and the new size (a value greater than the old one) as parameters:

   $ OS_VOLUME_API_VERSION=<API microversion>
   $ cinder extend <volume ID> <size>

   Replace <API microversion>, <volume ID>, and <size> with appropriate values. Use the following example as a guide:

   $ OS_VOLUME_API_VERSION=3.42
   $ cinder extend 573e024d-5235-49ce-8332-be1576d323f8 10

Procedure

1. In the dashboard, select Project > Compute > Volumes.
2. In the Volumes table, select the volume to delete.
3. Click Delete Volumes.

Procedure

1. Add an environment file to your deployment command that contains the following parameters:

   parameter_defaults:
     ControllerExtraConfig: # 1
       cinder::config::cinder_config:
         DEFAULT/scheduler_default_filters:
           value: 'AvailabilityZoneFilter,CapacityFilter,CapabilitiesFilter,InstanceLocality'

Procedure

1. In the dashboard, select Project > Compute > Volumes.
2. Select the Edit Attachments action. If the volume is not attached to an instance, the Attach To Instance drop-down list is visible.
3. From the Attach To Instance list, select the instance to which you want to attach the volume.
4. Click Attach Volume.

Procedure

1. In the dashboard, select Project > Compute > Volumes.
2. Select the volume’s Manage Attachments action. If the volume is attached to an instance, the instance’s name is displayed in the Attachments table.
3. Click Detach Volume in this and the next dialog screen.

Procedure

1. If the volume is already attached to an instance, then detach this volume. For more information, see Section 3.7, “Detaching a volume from an instance”.

2. Set the required access rights for this volume:

   • To set the access rights of a volume to read-only:

     # cinder readonly-mode-update <VOLUME-ID> true

   • To set the access rights of a volume to read-write:

     # cinder readonly-mode-update <VOLUME-ID> false

3. If you detached this volume from an instance to change the access rights, then re-attach the volume. For more information, see Section 3.6, “Attaching a volume to an instance”.

Procedure

1. Log in as the volume’s current owner.

2. List the available volumes:

   # cinder list

3. Initiate the volume transfer:

   # cinder transfer-create VOLUME

   Where VOLUME is the name or ID of the volume you wish to transfer. For example,

     +------------+--------------------------------------+
     |  Property  |                Value                 |
     +------------+--------------------------------------+
     |  auth_key  |           f03bf51ce7ead189           |
     | created_at |      2014-12-08T03:46:31.884066      |
     |     id     | 3f5dc551-c675-4205-a13a-d30f88527490 |
     |    name    |                 None                 |
     | volume_id  | bcf7d015-4843-464c-880d-7376851ca728 |
     +------------+--------------------------------------+

   The cinder transfer-create command clears the ownership of the volume and creates an id and auth_key for the transfer. These values can be given to, and used by, another user to accept the transfer and become the new owner of the volume.

4. The new user can now claim ownership of the volume. To do so, the user should first log in from the command line and run:

   # cinder transfer-accept TRANSFERID TRANSFERKEY

   Where TRANSFERID and TRANSFERKEY are the id and auth_key values returned by the cinder transfer-create command, respectively. For example,

   # cinder transfer-accept 3f5dc551-c675-4205-a13a-d30f88527490 f03bf51ce7ead189

Procedure

1. As the volume owner in the dashboard, select Projects > Volumes.
2. In the Actions column of the volume to transfer, select Create Transfer.

3. In the Create Transfer dialog box, enter a name for the transfer and click Create Volume Transfer.

   The volume transfer is created, and in the Volume Transfer screen you can capture the transfer ID and the authorization key to send to the recipient project.

   Click the Download transfer credentials button to download a .txt file containing the transfer name, transfer ID, and authorization key.

   Note

   The authorization key is available only in the Volume Transfer screen. If you lose the authorization key, you must cancel the transfer and create another transfer to generate a new authorization key.

4. Close the Volume Transfer screen to return to the volume list.

   The volume status changes to awaiting-transfer until the recipient project accepts the transfer

1. As the recipient project owner in the dashboard, select Projects > Volumes.
2. Click Accept Transfer.

3. In the Accept Volume Transfer dialog box, enter the transfer ID and the authorization key that you received from the volume owner and click Accept Volume Transfer.

   The volume now appears in the volume list for the active project.