I was just re-reading RFC4122 on UUIDs and the different variants:
http://tools.ietf.org/html/rfc4122.html
and what Python gives you in the UUID class:
http://docs.python.org/library/uuid.html
We need to decide which variant is right for us. With the namespace variant
uuid5(), it is possi
I think Erik's looking for a timeframe for this, too.
We could implement this tomorrow in Glance, but there's been a
conscience decision to use URIs as an image's globally-unique
identifier, and to allow Glance registries to implement whatever image
ID they wanted. This can, of course, change, but
+1
We have blueprints for migrating nova but it will take some time.
On May 27, 2011, at 1:02 PM, Mark Washenberger wrote:
> +1 for UUIDs.
>
> If we agree on this approach, there is some difficulty incorporating it into
> nova as Ed has identified. However, any other projects, especially those
+1 for UUIDs.
If we agree on this approach, there is some difficulty incorporating it into
nova as Ed has identified. However, any other projects, especially those hoping
to be adopted as Openstack projects by the PPB, can probably switch to this
approach more immediately.
Just a thought.
"Ed
On May 27, 2011, at 1:15 PM, Erik Carlin wrote:
> With the proliferation of new openstack services being built, is there any
> reason not to use UUID as the standard resource ID format?
The consensus at the last summit was to move to UUIDs for instance IDs.
The biggest concerns were tha
With the proliferation of new openstack services being built, is there any
reason not to use UUID as the standard resource ID format?
Erik
Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individ
6 matches
Mail list logo
