Open Stack

> Excerpts from Sławek Kapłoński's message of 2016-11-16 22:36:41 +0100:
>> Hello,
>> So I want to ask all of You how in Your opinion it should be solved.
>> Currently there is inconsistency between CLI clients and
>> API/Horizon/Openstack SDK (I checked that it is possible to create
>> resource without name via SDK).

There are a number of intentional inconsistencies between OSC and the
various REST APIs, precisely because many of the the APIs themselves
are very inconsistent not only between projects but even within each
project.  When those APIs are directly reflected in the CLI, like
happens with many of the project-specific CLIs, the users suffer due
to the inconsistencies.


On Wed, Nov 16, 2016 at 4:03 PM, Doug Hellmann <doug at doughellmann.com> wrote:
> The OpenStackClient team made the decision to always require names
> for newly created resources. Perhaps Dean or Steve can fill in more
> of the background, but my understanding is that this is a design
> decision for the user interface implemented by OSC, and not is not
> considered a bug.

Doug is correct here, we (OpenStackClient) made a specific decision in
the command structure to always use the resource name as the
positional argument of a create command.  In this case I believe the
consistency is worth what pain it may cause to invent a name for a new
policy.

We have done UX surveys with OSC at the last two summits and the
number one favorable comment from the users (varying from cloud
consumers to operators to OpenStack developers) has been regarding how
much they appreciate the command consistency.  This is our biggest
feature.

dt

-- 

Dean Troyer
dtroyer at gmail.com