On 8/12/2013 9:37 AM, Greg Poirier wrote:
Oh, we don't want to get super fancy with it. We would probably only
support one filesystem type and not partitions. E.g. You request a 120GB
volume and you get a 120GB Ext4 FS mountable by label.
I'm not following something here. What is the point
This would need to happen on the cinder side on creation. I don't think it is
safe for nova to be modifying the contents of the volume on attach. That said
nova does currently set the serial number on attach (for libvirt at least) so
the volume will show up as:
/dev/disk/by-id/virtio-uuid
On Mon, Aug 12, 2013 at 9:15 AM, Vishvananda Ishaya
vishvana...@gmail.comwrote:
This would need to happen on the cinder side on creation. I don't think it
is safe for nova to be modifying the contents of the volume on attach. That
said nova does currently set the serial number on attach (for
On Mon, Aug 12, 2013 at 9:18 AM, John Griffith
john.griff...@solidfire.comwrote:
On Mon, Aug 12, 2013 at 9:15 AM, Vishvananda Ishaya vishvana...@gmail.com
wrote:
This would need to happen on the cinder side on creation. I don't think
it is safe for nova to be modifying the contents of the
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] Extension to volume creation (filesystem and
label)
On Mon, Aug 12, 2013 at 9:18 AM, John Griffith
john.griff...@solidfire.commailto:john.griff...@solidfire.com wrote:
On Mon, Aug 12, 2013 at 9:15 AM, Vishvananda Ishaya vishvana
On Mon, Aug 12, 2013 at 10:26 AM, Clint Byrum cl...@fewbar.com wrote:
Like others, I am a little dubious about adding a filesystem to these
disks for a number of reasons. It feels like a violation of its just
a bunch of bits.
I actually think that it's a valid concern. I've been trying to
Since we can't guarantee that a volume, when attached, will become a
specified device name, we would like to be able to create a filesystem and
label it (so that we can programmatically interact with it when
provisioning systems, services, etc).
What we are trying to decide is whether this should