[openstack-dev] Volume attach mountpoints

Abel Lopez alopgeek at gmail.com
Thu Apr 4 17:38:37 UTC 2013

I've been dealing with lots of confusion from users, mainly because the
mountpoint they specify in volume-attach really has no bearing onto what
the guest OS does with the volume.

Here's some examples:
m1.tiny has no ephemeral disk, Horizon "Suggests" /dev/vdc as the
mountpoint. The OS assigns the volume to the next available device, which
is /dev/vdb

a flavor with an existing (perhaps unused) ephemeral disk at /dev/vdb, and
the user specifies /dev/vdb in volume-attach, OS will use the next
available device, and confuse the user.

Windows guests - have no /dev/ - volumes show up as disk1, disk2, etc.

Having the mountpoint seems to do more to confuse the users. This is an
option that really doesn't seem to bring anything to the table. We should
really just leave device assignment to the guest OS, no?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130404/9d8043bd/attachment.html>

More information about the OpenStack-dev mailing list