[openstack-dev] [Magnum] Does Bay/Baymodel name should be a required option when creating a Bay/Baymodel
eric at windisch.us
Wed Jun 3 03:07:28 UTC 2015
On Tue, Jun 2, 2015 at 10:29 PM, Adrian Otto <adrian.otto at rackspace.com>
> I have reflected on this further and offer this suggestion:
> 1) Add a feature to Magnum to auto-generate human readable names, like
> Docker does for un-named containers, and ElasticSearch does for naming
> cluster nodes. Use this feature if no name is specified upon the creation
> of a Bay or Baymodel.
For what it's worth, I also believe that requiring manual specification of
names, especially if they must be unique is an anti-pattern.
If auto-generation of human readable names is performed and these must be
unique, mind that you will be accepting a limit on the number of bays that
may be created. I think this is perfectly fine, as long as it's reasonably
large and the algorithm is sufficiently intelligent. The UUID algorithm is
good at this, for instance, although it fails at readability. Docker's is
not terribly great and could be limiting if you were looking to run several
thousand containers on a single machine. Something better than Docker's
algorithm but more readable than UUID could be explored.
Also, something to consider is if this should also mean a change to the
UUIDs themselves. You could use UUID-5 to create a UUID from your tenant's
UUID and your unique name. The tenant's UUID would be the namespace, with
the bay's name being the "name" field. The benefit of this is that clients,
by knowing their tenant ID could automatically determine their bay ID,
while also guaranteeing uniqueness (or as unique as UUID gets, anyway).
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev