On Mon, Sep 21, 2009 at 03:21:32PM +0100, Michael Hanselmann wrote: > 2009/9/21 Iustin Pop <[email protected]>: > > --- a/doc/design-2.1.rst > > +++ b/doc/design-2.1.rst > > +Introducting persistent UUIDs > > s/Introducting/Introducing/ > > > +Upgrading from Ganeti 2.0 will add automatically uuids to all entities > > +missing them. > > For consistency and because it's an acronym, write “UUID” always in uppercase.
Well, I write ‘uuid’ when I refer to the actual object field. I'll add quotes, is that fine? > > +In the next release (e.g. 2.2), the tracking of objects will change > > s/next release/next minor release/ > > > +from the name to the UUID internally, and externally Ganeti will > > +accept both forms of identification; e.g. an RAPI call would be made > > +either against ``/2/instances/foo.bar`` or against > > +``/2/instances/bb3b2e42…``. > > Not that I expect this to happen, but what if someone used UUIDs to > name existing machines? Should UUID names have a prefix which will no > longer be allowed for instance names? Nah, I don't think so. I would just consider the instance name + instance UUIDs a single namespace, so this would fail with 'Name already used'. > > +Internal tracking refers to the way the configuration is stored; a > > +DRBD disk of an instance refers to the node name (so that IPs can be > > +changed easily), but this is still a problem for name changes; thus > > +these will be changed to point to the node name to ease renames. > > I guess you mean “node UUID” in the last sentence. Yes, thanks. > > +The advantages of this change (after the second round of changes), if > > s/if/is/? ACK. Will resend after we get agreement. thanks, iustin
