|
A volume is a detachable block storage device, similar to a USB hard drive. You can attach a volume to only one instance. Use the openstack client commands to create and manage volumes. Create a volume¶This example creates a my-new-volume volume based on an image. List images, and note the ID of the image that you want to use for your volume: $ openstack image list+--------------------------------------+---------------------------------+| ID | Name |+--------------------------------------+---------------------------------+| 8bf4dc2a-bf78-4dd1-aefa-f3347cf638c8 | cirros-0.3.5-x86_64-uec || 9ff9bb2e-3a1d-4d98-acb5-b1d3225aca6c | cirros-0.3.5-x86_64-uec-kernel || 4b227119-68a1-4b28-8505-f94c6ea4c6dc | cirros-0.3.5-x86_64-uec-ramdisk |+--------------------------------------+---------------------------------+
8 Q; A$ ^7 H7 o! X) Y7 ~8 r! o- U+ l9 @; e. `; W2 }- y
List the availability zones, and note the ID of the availability zone in which you want to create your volume: $ openstack availability zone list+------+-----------+| Name | Status |+------+-----------+| nova | available |+------+-----------+
3 x; L- @3 ` c6 o# H
6 d8 s2 {1 L& kCreate a volume with 8 gibibytes (GiB) of space, and specify the availability zone and image: $ openstack volume create --image 8bf4dc2a-bf78-4dd1-aefa-f3347cf638c8 \ --size 8 --availability-zone nova my-new-volume+------------------------------+--------------------------------------+| Property | Value |+------------------------------+--------------------------------------+| attachments | [] || availability_zone | nova || bootable | false || consistencygroup_id | None || created_at | 2016-09-23T07:52:42.000000 || description | None || encrypted | False || id | bab4b0e0-ce3d-4d57-bf57-3c51319f5202 || metadata | {} || multiattach | False || name | my-new-volume || os-vol-tenant-attr:tenant_id | 3f670abbe9b34ca5b81db6e7b540b8d8 || replication_status | disabled || size | 8 || snapshot_id | None || source_volid | None || status | creating || updated_at | None || user_id | fe19e3a9f63f4a14bd4697789247bbc5 || volume_type | lvmdriver-1 |+------------------------------+--------------------------------------+
+ l, G$ R( S1 D5 [% C( e) V7 }
3 ]2 W- J9 s9 o7 v8 I7 yTo verify that your volume was created successfully, list the available volumes: $ openstack volume list+--------------------------------------+---------------+-----------+------+-------------+| ID | DisplayName | Status | Size | Attached to |+--------------------------------------+---------------+-----------+------+-------------+| bab4b0e0-ce3d-4d57-bf57-3c51319f5202 | my-new-volume | available | 8 | |+--------------------------------------+---------------+-----------+------+-------------+
) O. y, J. e9 K+ Q% m6 v' W# i
: V' }+ n$ _3 p, o1 }' sIf your volume was created successfully, its status is available. If its status is error, you might have exceeded your quota.
4 R# V) Q; v( ~7 n; ^: \, M
Volume Types¶Cinder supports these three ways to specify volume type during volume creation. - volume_type
- cinder_img_volume_type (via glance image metadata)
- default_volume_type (via cinder.conf)
: t6 a5 N5 n& G+ x) r9 n4 m
volume-type¶User can specify volume type when creating a volume. $ openstack volume create -h -f {json,shell,table,value,yaml} -c COLUMN --max-width <integer> --noindent --prefix PREFIX --size <size> --type <volume-type> --image <image> --snapshot <snapshot> --source <volume> --description <description> --user <user> --project <project> --availability-zone <availability-zone> --property <key=value> <name>; E" {! T: F4 G+ r1 T
$ K, [, ?2 k+ p% |1 v( G! y
P2 y" H7 ~1 b' J
cinder_img_volume_type¶If glance image has cinder_img_volume_type property, Cinder uses this parameter to specify volume type when creating a volume. Choose glance image which has cinder_img_volume_type property and create a volume from the image. $ openstack image list+----------------------------------+---------------------------------+--------+| ID | Name | Status |+----------------------------------+---------------------------------+--------+| 376bd633-c9c9-4c5d-a588-342f4f66 | cirros-0.3.5-x86_64-uec | active || d086 | | || 2c20fce7-2e68-45ee-ba8d- | cirros-0.3.5-x86_64-uec-ramdisk | active || beba27a91ab5 | | || a5752de4-9faf-4c47-acbc- | cirros-0.3.5-x86_64-uec-kernel | active || 78a5efa7cc6e | | |+----------------------------------+---------------------------------+--------+$ openstack image show 376bd633-c9c9-4c5d-a588-342f4f66d086+------------------------+------------------------------------------------------+| Field | Value |+------------------------+------------------------------------------------------+| checksum | eb9139e4942121f22bbc2afc0400b2a || cinder_img_volume_type | nfstype || container_format | ami || created_at | 2016-10-13T03:28:55Z || disk_format | ami || file | /v2/images/376bd633-c9c9-4c5d-a588-342f4f66d086/file || id | 376bd633-c9c9-4c5d-a588-342f4f66d086 || min_disk | 0 || min_ram | 0 || name | cirros-0.3.5-x86_64-uec || owner | 88ba456e3a884c318394737765e0ef4d || properties | kernel_id='a5752de4-9faf-4c47-acbc-78a5efa7cc6e', || | ramdisk_id='2c20fce7-2e68-45ee-ba8d-beba27a91ab5' || protected | False || schema | /v2/schemas/image || size | 25165824 || status | active || tags | || updated_at | 2016-10-13T03:28:55Z || virtual_size | None || visibility | public |+------------------------+------------------------------------------------------+$ openstack volume create --image 376bd633-c9c9-4c5d-a588-342f4f66d086 \ --size 1 --availability-zone nova test+---------------------+--------------------------------------+| Field | Value |+---------------------+--------------------------------------+| attachments | [] || availability_zone | nova || bootable | false || consistencygroup_id | None || created_at | 2016-10-13T06:29:53.688599 || description | None || encrypted | False || id | e6e6a72d-cda7-442c-830f-f306ea6a03d5 || multiattach | False || name | test || properties | || replication_status | disabled || size | 1 || snapshot_id | None || source_volid | None || status | creating || type | nfstype || updated_at | None || user_id | 33fdc37314914796883706b33e587d51 |+---------------------+--------------------------------------+& z6 O- ^# }5 X; b6 J
& \9 X/ m! z% v7 q) d' T$ O" Z, h' D
default_volume_type¶If above parameters are not set, Cinder uses default_volume_type which is defined in cinder.conf during volume creation. Example cinder.conf file configuration. [default]default_volume_type = lvmdriver-1
) G. Y; V4 ]$ K
# [7 f5 x& w4 z! p, j! n* F1 a
- b% G& R% J- o& V0 {7 W/ j) n V7 i
( k. G3 f+ {; g
: N) P8 V- t$ c6 u7 k- B' b0 uAttach a volume to an instance¶Attach your volume to a server, specifying the server ID and the volume ID: $ openstack server add volume 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 \ 573e024d-5235-49ce-8332-be1576d323f8 --device /dev/vdb# f9 d- @; q* S+ F, ~
% M, i- l- E! J: s: w, E& y: A
Show information for your volume: $ openstack volume show 573e024d-5235-49ce-8332-be1576d323f8+ N5 |+ E5 k' ^
. L# } y, k; C; M$ k# v4 W) Q
The output shows that the volume is attached to the server with ID 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5, is in the nova availability zone, and is bootable. +------------------------------+-----------------------------------------------+| Field | Value |+------------------------------+-----------------------------------------------+| attachments | [{u'device': u'/dev/vdb', || | u'server_id': u'84c6e57d-a || | u'id': u'573e024d-... || | u'volume_id': u'573e024d... || availability_zone | nova || bootable | true || consistencygroup_id | None || created_at | 2016-10-13T06:08:07.000000 || description | None || encrypted | False || id | 573e024d-5235-49ce-8332-be1576d323f8 || multiattach | False || name | my-new-volume || properties | || replication_status | disabled || size | 8 || snapshot_id | None || source_volid | None || status | in-use || type | lvmdriver-1 || updated_at | 2016-10-13T06:08:11.000000 || user_id | 33fdc37314914796883706b33e587d51 |+------------------------------+-----------------------------------------------+
, Q/ C8 Z' u0 z1 M1 N4 }0 A0 I& o5 z7 r% h5 i4 ~0 X3 p8 o/ n( z
+ { i: k6 w8 z5 ~
8 y$ n$ n' t: m) a1 n0 [- k) n8 y7 [Detach a volume from an instance¶Detach your volume from a server, specifying the server ID and the volume ID: $ openstack server remove volume 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 \ 573e024d-5235-49ce-8332-be1576d323f8; {* ^$ Q* S7 D" g- Y; s4 M$ h
( |: {. r: K) } G# Z8 i% ?7 V
Show information for your volume: $ openstack volume show 573e024d-5235-49ce-8332-be1576d323f8
! A0 ?9 Z/ r0 q( ?6 m; U3 H) { E; s) T d% Z9 d y8 l; c
The output shows that the volume is no longer attached to the server: +------------------------------+-----------------------------------------------+| Field | Value |+------------------------------+-----------------------------------------------+| attachments | [] || availability_zone | nova || bootable | true || consistencygroup_id | None || created_at | 2016-10-13T06:08:07.000000 || description | None || encrypted | False || id | 573e024d-5235-49ce-8332-be1576d323f8 || multiattach | False || name | my-new-volume || properties | || replication_status | disabled || size | 8 || snapshot_id | None || source_volid | None || status | in-use || type | lvmdriver-1 || updated_at | 2016-10-13T06:08:11.000000 || user_id | 33fdc37314914796883706b33e587d51 |+------------------------------+-----------------------------------------------+
5 L+ ^" k( a2 k. N
$ w( Q/ A! {1 ~7 l8 u7 F5 M- v: ]. x( @ Z8 l2 ?1 e7 a; i5 E
, Z) X' S) x9 h! F
Delete a volume¶To delete your volume, you must first detach it from the server. To detach the volume from your server and check for the list of existing volumes, see steps 1 and 2 in Resize_a_volume. Delete the volume using either the volume name or ID: $ openstack volume delete my-new-volume
7 B3 \% J" M; p3 F
, j1 G& l0 w: a% r: w2 ]$ EThis command does not provide any output. List the volumes again, and note that the status of your volume is deleting: $ openstack volume list+----------------+-----------------+-----------+------+-------------+| ID | Display Name | Status | Size | Attached to |+----------------+-----------------+-----------+------+-------------+| 573e024d-52... | my-new-volume | deleting | 8 | || bd7cf584-45... | my-bootable-vol | available | 8 | |+----------------+-----------------+-----------+------+-------------+$ [+ a1 M4 k- H3 ]; ^* K
: N j. X# u! l
When the volume is fully deleted, it disappears from the list of volumes: $ openstack volume list+----------------+-----------------+-----------+------+-------------+| ID | Display Name | Status | Size | Attached to |+----------------+-----------------+-----------+------+-------------+| bd7cf584-45... | my-bootable-vol | available | 8 | |+----------------+-----------------+-----------+------+-------------+
8 |' B3 r; K7 s, _4 \& J1 s
( T, D! B9 W% ?) O6 B! H8 ?$ }" D% j+ v2 u
?: v7 B4 f8 |1 {+ I! IResize a volume¶To resize your volume, you must first detach it from the server. To detach the volume from your server, pass the server ID and volume ID to the following command: $ openstack server remove volume 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 573e024d-5235-49ce-8332-be1576d323f8- j* {# A# k1 ]8 [; G4 M1 @4 o
4 L$ p2 o: ]4 C
This command does not provide any output. List volumes: $ openstack volume list+----------------+-----------------+-----------+------+-------------+| ID | Display Name | Status | Size | Attached to |+----------------+-----------------+-----------+------+-------------+| 573e024d-52... | my-new-volume | available | 8 | || bd7cf584-45... | my-bootable-vol | available | 8 | |+----------------+-----------------+-----------+------+-------------++ v- y/ m: n4 `) B; ]/ Q
- F- g( L2 p! k* G l/ U
Note that the volume is now available. Resize the volume by passing the volume ID and the new size (a value greater than the old one) as parameters: $ openstack volume set 573e024d-5235-49ce-8332-be1576d323f8 --size 10
" Q3 P. o. O! E6 I
- j3 I5 [5 ^9 T6 h7 mThis command does not provide any output. 5 j3 B2 {- t) b! O
Note: X5 n. r7 Y( I# a: }# U
When extending an LVM volume with a snapshot, the volume will be deactivated. The reactivation is automatic unless auto_activation_volume_list is defined in lvm.conf. See lvm.conf for more information. " w1 _# [0 t" A7 V" ?
% ?0 g; i3 Y) u, X
$ n" _ l1 _( b- t- EMigrate a volume¶As an administrator, you can migrate a volume with its data from one location to another in a manner that is transparent to users and workloads. You can migrate only detached volumes with no snapshots. Possible use cases for data migration include: - Bring down a physical storage device for maintenance without disrupting workloads.
- Modify the properties of a volume.
- Free up space in a thinly-provisioned back end. s" B2 S3 m# x8 ]3 K- p$ R0 }
Migrate a volume with the openstack volume migrate command, as shown in the following example: $ openstack volume migrate [-h --host <host> [--force-host-copy [--lock-volume] <volume>
: Z& K( j! b+ I- M4 A; e0 R
& g* q* t6 F- J: X/ o( s, Y' k$ VThe arguments for this command are: hostThe destination host in the format host@backend-name#pool.volumeThe ID of the volume to migrate.force-host-copyDisables any driver optimizations and forces the data to be copied by the host.lock-volumePrevents other processes from aborting the migration.( w5 g- m4 ~+ N! F8 f
Note: q4 Q* `( O) [9 D7 Z( c- {# a8 n( k
If the volume has snapshots, the specified host destination cannot accept the volume. If the user is not an administrator, the migration fails. 7 y# E9 A8 p* C& y' S8 B& c4 J
; @& f% S, `) \2 D) u% _Transfer a volume¶You can transfer a volume from one owner to another by using the openstack volume transfer request create command. The volume donor, or original owner, creates a transfer request and sends the created transfer ID and authorization key to the volume recipient. The volume recipient, or new owner, accepts the transfer by using the ID and key. In Rocky, Cinder changes the API behavior for V2 and 3.x < 3.55, snapshots will be transferred with volume by default. That means if the volume has some snapshots, when a user transfers a volume from one owner to another, then those snapshots will be transferred with the volume as well. After microversion 3.55, Cinder supports the ability to transfer volume without snapshots. If users don’t want to transfer snapshots, they need to specify the new optional argument –no_snapshots.
6 H1 B3 }* b. {Note
9 x% _' r+ Q$ J5 l* ^# T4 EThe procedure for volume transfer is intended for projects (both the volume donor and recipient) within the same cloud. # d/ u" r6 A! G9 r
Use cases include: - Create a custom bootable volume or a volume with a large data set and transfer it to a customer.
- For bulk import of data to the cloud, the data ingress system creates a new Block Storage volume, copies data from the physical device, and transfers device ownership to the end user.
6 J+ L9 e' ?# C( X0 r, n5 a
Create a volume transfer request¶While logged in as the volume donor, list the available volumes: $ openstack volume list+-----------------+-----------------+-----------+------+-------------+| ID | Display Name | Status | Size | Attached to |+-----------------+-----------------+-----------+------+-------------+| 72bfce9f-cac... | None | error | 1 | || a1cdace0-08e... | None | available | 1 | |+-----------------+-----------------+-----------+------+-------------+/ z0 W8 Y; J L# d' |9 J- @+ Z
3 t+ r( A+ }3 ^+ W! g0 T6 _3 g
As the volume donor, request a volume transfer authorization code for a specific volume: $ openstack volume transfer request create [--no-snapshots <volume>
1 p" l" w3 Q( d T4 e/ W: I+ h# I9 d4 U( w# E
6 V( Y5 [+ l' d
The arguments to be passed are: <volume> Name or ID of volume to transfer. --no-snapshots Transfer the volume without snapshots. The volume must be in an available state or the request will be denied. If the transfer request is valid in the database (that is, it has not expired or been deleted), the volume is placed in an awaiting-transfer state. For example: $ openstack volume transfer request create a1cdace0-08e4-4dc7-b9dc-457e9bcfe25f3 u; a9 H: ^' _$ g. C5 d
( M' q9 n6 @) V% @9 mThe output shows the volume transfer ID in the id row and the authorization key. +------------+--------------------------------------+| Field | Value |+------------+--------------------------------------+| auth_key | 0a59e53630f051e2 || created_at | 2016-11-03T11:49:40.346181 || id | 34e29364-142b-4c7b-8d98-88f765bf176f || name | None || volume_id | a1cdace0-08e4-4dc7-b9dc-457e9bcfe25f |+------------+--------------------------------------+% M8 ~8 j9 y8 v, C* f! q! k
2 I9 K$ y% T0 i1 s$ X0 G% p/ `, @* ?
Note: @' r: S. B2 Z1 ^/ Y1 s
Optionally, you can specify a name for the transfer by using the --name transferName parameter.
/ r/ a" L! |$ \
% a, a a% D' k b/ c: MNote
8 e+ j# l- R, Y" b9 fWhile the auth_key property is visible in the output of openstack volume transfer request create VOLUME_ID, it will not be available in subsequent openstack volume transfer request show TRANSFER_ID command.
+ q) \, k; s# t3 A6 ^3 u4 ~% ~' {Send the volume transfer ID and authorization key to the new owner (for example, by email). View pending transfers: $ openstack volume transfer request list+--------------------------------------+--------------------------------------+------+| ID | Volume | Name |+--------------------------------------+--------------------------------------+------+| 6e4e9aa4-bed5-4f94-8f76-df43232f44dc | a1cdace0-08e4-4dc7-b9dc-457e9bcfe25f | None |+--------------------------------------+--------------------------------------+------+
F1 g) Y* R8 m9 K4 |) a5 K4 k; `" A1 z$ |( T5 Z( |* e
After the volume recipient, or new owner, accepts the transfer, you can see that the transfer is no longer available: $ openstack volume transfer request list+----+-----------+------+| ID | Volume ID | Name |+----+-----------+------++----+-----------+------+
# g2 W, J7 W# S1 R. V% Q, P
, n" F# i+ } W% ^
1 i& \/ N2 o: G0 s9 P# O ?
; v8 Z3 [2 `9 X) i' Y) P* n U
Accept a volume transfer request¶& M; s5 l" R6 D" |' S: J$ o
Delete a volume transfer¶List available volumes and their statuses: $ openstack volume list+-----------------+-----------------+-----------------+------+-------------+| ID | Display Name | Status | Size | Attached to |+-----------------+-----------------+-----------------+------+-------------+| 72bfce9f-cac... | None | error | 1 | || a1cdace0-08e... | None |awaiting-transfer| 1 | |+-----------------+-----------------+-----------------+------+-------------+
5 R: L6 Z: N8 f# t6 P# W' Y, @1 n7 x% v* W4 L
Find the matching transfer ID: $ openstack volume transfer request list+--------------------------------------+--------------------------------------+------+| ID | VolumeID | Name |+--------------------------------------+--------------------------------------+------+| a6da6888-7cdf-4291-9c08-8c1f22426b8a | a1cdace0-08e4-4dc7-b9dc-457e9bcfe25f | None |+--------------------------------------+--------------------------------------+------+
) T! t6 m5 R- `6 h; g6 [% |. Z% ]1 l: Y
+ C: y4 A5 x! l/ f' PDelete the volume: $ openstack volume transfer request delete <transfer>: W/ W, m: v0 m8 w5 x* \- D3 D# ]
8 H- g/ ~+ r+ G<transfer>Name or ID of transfer to delete. For example: $ openstack volume transfer request delete a6da6888-7cdf-4291-9c08-8c1f22426b8a# e% z7 T: w+ e5 J6 F
' g; V5 s8 X- [, BVerify that transfer list is now empty and that the volume is again available for transfer: $ openstack volume transfer request list+----+-----------+------+| ID | Volume ID | Name |+----+-----------+------++----+-----------+------+
. \+ H8 H* a% J6 n
! @( D, E6 p2 b9 h V; r$ openstack volume list+-----------------+-----------+--------------+------+-------------+----------+-------------+| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |+-----------------+-----------+--------------+------+-------------+----------+-------------+| 72bfce9f-ca... | error | None | 1 | None | false | || a1cdace0-08... | available | None | 1 | None | false | |+-----------------+-----------+--------------+------+-------------+----------+-------------+" a ^- E0 D- s% I
4 U3 e- V# q1 i' A: V$ M! p" t; _ L8 p: I/ l: r) F; t
3 e; o4 u6 A. y) O$ O5 a$ Z! q7 H- L+ V
: K- ?3 e( L$ `" g: dManage and unmanage a snapshot¶A snapshot is a point in time version of a volume. As an administrator, you can manage and unmanage snapshots. Manage a snapshot¶Manage a snapshot with the openstack volume snapshot set command: $ openstack volume snapshot set [-h [--name <name>] [--description <description>] [--no-property] [--property <key=value>] [--state <state>] <snapshot>* [9 u6 ]/ L, F" e f3 `
5 z5 ?# {5 P* T, m( a8 RThe arguments to be passed are: --name <name>New snapshot name--description <description>New snapshot description--no-propertyRemove all properties from <snapshot> (specify both –no-property and –property to remove the current properties before setting new properties.)--property <key=value>Property to add or modify for this snapshot (repeat option to set multiple properties)--state <state>New snapshot state. (“available”, “error”, “creating”, “deleting”, or “error_deleting”) (admin only) (This option simply changes the state of the snapshot in the database with no regard to actual status, exercise caution when using)<snapshot>Snapshot to modify (name or ID)$ openstack volume snapshot set my-snapshot-id& f, Q* z; W" Q3 t/ s: q6 ~
% {: ], p- e4 |+ U. j0 s H$ @
5 L3 X9 S* ^: G w, s: ]5 `( zUnmanage a snapshot¶Unmanage a snapshot with the openstack volume snapshot unset command: $ openstack volume snapshot unset [-h [--property <key>] <snapshot>
/ t% f6 B8 T# Y+ q& Z6 B* i0 F- \# o
The arguments to be passed are: --property <key>Property to remove from snapshot (repeat option to remove multiple properties)<snapshot>Snapshot to modify (name or ID).The following example unmanages the my-snapshot-id image: $ openstack volume snapshot unset my-snapshot-id
& Z& b: ]8 P) D+ f3 s, l3 d j' z3 |) g, P! h
; P2 C, {9 d( j" f0 B3 i+ N
3 R& U- F+ [; B; T( [! m
Report backend state in service list¶Each of the Cinder services report a Status and a State. These are the administrative state and the runtime state, respectively. To get a listing of all Cinder services and their states, run the command: $ openstack volume service list+------------------+-------------------+------+---------+-------+----------------------------+| Binary | Host | Zone | Status | State | Updated At |+------------------+-------------------+------+---------+-------+----------------------------+| cinder-scheduler | tower | nova | enabled | up | 2018-03-30T21:16:11.000000 || cinder-volume | tower@lvmdriver-1 | nova | enabled | up | 2018-03-30T21:16:15.000000 || cinder-backup | tower | nova | enabled | up | 2018-03-30T21:16:14.000000 |+------------------+-------------------+------+---------+-------+----------------------------+$ X9 M5 s8 C8 T. R1 O7 M
( z* ?$ X2 k' h- j1 s$ l5 @( N0 i2 a6 _$ j4 E6 u* d
|
发表于 2021-5-25 01:00:08