Comment #4 on issue 994 by [email protected]: Support Setting the UUID
of a ganeti instance explicitly add instance creation time
https://code.google.com/p/ganeti/issues/detail?id=994
Note: UUIDs serve as primary keys in various data structures; also,
being universally unique tools building on top of Ganeti might cache
them for their own purpose, even over cluster boarders.
If I understand the use case correctly, setting them once and for all
on instance creation should suffice.
The use case has mostly to do with instance moves from an old cluster to a
new one, in a manual way: create new instances in the new cluster and copy
disks from the old one. Since applications running inside the instance may
be bound to the system UUID, cloned instances must keep that. Setting the
UUID at instance creation would be enough, provided that you already know
(and remember) that you have to do so. But what if you don't know from the
beginning that some applications are bound to the system UUID and found out
that later? In that case, it would be handy if you could just change the
UUID and restart the instance and not having to recreate the instance with
the correct UUID and reclone disks.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
