Done. Tested root/data disks for CLVM, local, NFS.
On Wed, Oct 9, 2013 at 11:32 PM, Marcus Sorensen wrote:
> Yeah, existing volumes have a path thats already set in stone. It would only
> concern new volumes.
>
> It could cause problems down the line if people get used to them matching
> and deci
Yeah, existing volumes have a path thats already set in stone. It would
only concern new volumes.
It could cause problems down the line if people get used to them matching
and decide to use uuid and path interchangeably. They're not by default
identical though since the path usually contains the d
OK, now I'm really replying to this e-mail thread. :)
I think this is a good idea, Marcus. It gets rid of an unnecessary
translation step.
On Wed, Oct 9, 2013 at 11:23 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:
> I'm sorry!
>
> I sent this e-mail to the wrong discussion thread. :
I'm sorry!
I sent this e-mail to the wrong discussion thread. :)
On Wed, Oct 9, 2013 at 11:05 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:
> Yeah, I'm not really clear how the snapshot strategy works if you have
> multiple vendors that implement that interface either.
>
>
> On Wed,
On 10-Oct-2013, at 9:27 AM, Marcus Sorensen wrote:
> Does anyone have any reservations about changing the volume identifier in
> KVM's volume creation command to be the uuid of the volume? Currently for
> new volumes it generates a random uuid and passes that back to be stored in
> the database.
+1 - happens in lots of places in our code where a random-uuid
associates with a physical resource's uuid.
Will this will happen only for new volumes? Old volumes can still be
listed and found using the old method? I'm specifically concerned
about upgraded systems.
On Wed, Oct 09, 2013 at 11:05:4
Yeah, I'm not really clear how the snapshot strategy works if you have
multiple vendors that implement that interface either.
On Wed, Oct 9, 2013 at 9:57 PM, Marcus Sorensen wrote:
> Does anyone have any reservations about changing the volume identifier in
> KVM's volume creation command to be
