Ask Your Question
2

Accessing Heat-provisioned Cinder volumes

asked 2014-10-10 22:30:08 -0500

larsks gravatar image

The documentation for heat suggests using the /dev/disk/by-id/virtio-<VolumeID> link to access Cinder-provisioned volumes, but I have run into a number of problems with this process. I have a cinder volume available:

$ cinder list
+--------------------------------------+--------+---------------------...
|                  ID                  | Status |                     ...
+--------------------------------------+--------+---------------------...
| 495ad1c1-cc6f-4e81-97aa-4d6a8f982844 | in-use | kube-kube_minions-sm...
+--------------------------------------+--------+---------------------...

On a Fedora 20 system (kernel3.16.3), I have a cloud-init script looking for:

/dev/disk/by-id/virtio-495ad1c1-cc6f-4e81-97aa-4d6a8f982844

But inside that directory is actually:

virtio-495ad1c1-cc6f-4e81-9 -> ../../vdb

Note that the filename has been truncated such that it does not contain the full volume id. This appears to be a fundamental problem; the name is truncated in /sys/class/block/vdb/serial:

# cat /sys/class/block/vdb/serial 
495ad1c1-cc6f-4e81-9

I can obviously work around this by having my cloud-init script truncate the volume id, but is this working for anyone else?

edit retag flag offensive close merge delete

Comments

That seems like what I remember as the expected behaviour (but not very nice IMO).

asalkeld gravatar imageasalkeld ( 2014-11-23 21:41:21 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2015-02-12 20:03:39 -0500

asalkeld gravatar image

I'll also point you to some RHT docs;) https://access.redhat.com/documentati...

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-10-10 22:30:08 -0500

Seen: 281 times

Last updated: Feb 12 '15