At Wed, 3 Aug 2011 15:41:31 +0100, Chris Webb wrote: > > Chris Webb <[email protected]> writes: > > > MORITA Kazutaka <[email protected]> writes: > > > > > Let me clarify some points. > > > > > > In this approach, when we rename a vdi, we specify the vdi 'id' and > > > change the attribute of the vdi, yes? > > > > > > What is specified in the qemu command line option as a Sheepdog volume > > > name? Is it vdi 'name' (an attribute of the vdi) or vdi 'id' (the 32 > > > bit integer)? > > > > I was imagining that the vdi was internally addressed by its 'id' and the > > name was just an attribute for user convenience, a bit like we fundamentally > > identify snapshots by their vid but might one day give them a convenience > > tag name as qcow2 snapshots have. I'm already using the vdi 'name' in this > > way inside our management system, allocating a unique value to it rather > > than setting it to the user-provided drive name. > > ...and thus the 'id' is what's passed on the qemu command line.
Thanks for your explanation. This is a good use case for Sheepdog vdi attributes. Kazutaka -- sheepdog mailing list [email protected] http://lists.wpkg.org/mailman/listinfo/sheepdog
