Auto generate Bay/BayModel Name

Registered by Guangya Liu (Jay Lau)

Refer to http://markmail.org/thread/jiwnyl5qihdoui5w for more discussion for this.

I have reflected on this further and offer this suggestion:

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.

Blueprint information

Status:
Complete
Approver:
Adrian Otto
Priority:
Low
Drafter:
Guangya Liu (Jay Lau)
Direction:
Approved
Assignee:
Wenzhi Yu
Definition:
Discussion
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Wenzhi Yu
Completed by
Wenzhi Yu

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/auto-generate-name,n,z

Addressed by: https://review.openstack.org/331043
    Auto generate Bay/BayModel name

The original description of this blueprint actually proposed two different features:

1. Auto generate name for bay/baymodel if user does not specify one;
2. Add a configuration directive 'allow_duplicate_baymodel_name'(default=False) to let
   cloud operators to decide whether to enforce name uniqueness or not.

I moved the second feature to a new blueprint duplicate-named-bay-and-baymodel [1]

[1]https://blueprints.launchpad.net/magnum/+spec/duplicate-named-bay-and-baymodel

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.