[openstack-dev] [magnum][osc] What name to use for magnum commands in osc?
adrian.otto at rackspace.com
Mon Mar 20 22:19:14 UTC 2017
On Mar 20, 2017, at 3:02 PM, Clint Byrum <clint at fewbar.com<mailto:clint at fewbar.com>> wrote:
Excerpts from Adrian Otto's message of 2017-03-20 21:16:09 +0000:
On Mar 20, 2017, at 12:35 PM, Jay Pipes <jaypipes at gmail.com<mailto:jaypipes at gmail.com><mailto:jaypipes at gmail.com>> wrote:
On 03/20/2017 03:08 PM, Adrian Otto wrote:
Stephen Watson has been working on an magnum feature to add magnum commands to the openstack client by implementing a plugin:
In review of this work, a question has resurfaced, as to what the client command name should be for magnum related commands. Naturally, we’d like to have the name “cluster” but that word is already in use by Senlin.
Unfortunately, the Senlin API uses a whole bunch of generic terms as top-level REST resources, including "cluster", "event", "action", "profile", "policy", and "node". :( I've warned before that use of these generic terms in OpenStack APIs without a central group responsible for curating the API would lead to problems like this. This is why, IMHO, we need the API working group to be ultimately responsible for preventing this type of thing from happening. Otherwise, there ends up being a whole bunch of duplication and same terms being used for entirely different things.
Stephen opened a discussion with Dean Troyer about this, and found that “infra” might be a suitable name and began using that, and multiple team members are not satisfied with it.
Yeah, not sure about "infra". That is both too generic and not an actual "thing" that Magnum provides.
The name “magnum” was excluded from consideration because OSC aims to be project name agnostic. We know that no matter what word we pick, it’s not going to be ideal. I’ve added an agenda on our upcoming team meeting to judge community consensus about which alternative we should select:
Current choices on the table are:
* c_cluster (possible abbreviation alias for container_infra_cluster)
For example, our selected name would appear in “openstack …” commands. Such as:
$ openstack c_cluster create …
If you have input to share, I encourage you to reply to this thread, or come to the team meeting so we can consider your input before the team makes a selection.
What is Magnum's service-types-authority service_type?
I propose "coe-cluster” for that, but that should be discussed further, as it’s impossible for magnum to conform with all the requirements for service types because they fundamentally conflict with each other:
In the past we referred to this type as a “bay” but found it burdensome for users and operators to use that term when literally bay == cluster. We just needed to call it what it is because there’s a prevailing name for that concept, and everyone expects that’s what it’s called.
I Think Jay was asking for Magnum's name in the catalog:
Which is 'container-infra' according to this:
I was unsure, so I found him on IRC to clarify, and he pointed me to the openstack/service-types-authority repository, where I submitted patch 445694 for review. We have three distinct identifiers in play:
1) Our existing service catalog entry name: container-infra
2) Our openstack client noun: TBD, decision expected from our team tomorrow. My suggestion: "coe cluster”.
3) Our (proposed) service type: coe-cluster
Each identifier has respective guidelines and limits, so they differ.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev