<div dir="ltr">I totally agree with the direction of OSC and shade.<div>The similar discussion happens in neutronclient side before too.<br><div><br></div><div>From user perspective, 'name' is really useful to identify resources,</div><div>even though admin usually use ID to identify resources.</div><div>In the past neutronclient discussion, requiring at least one parameter is useful</div><div>to avoid issuing a command line by mistake. It is another feedback from user experience.</div><div><br></div><div>The neutronclient bug should be closed with Won't Fix.</div><div><br></div><div>Akihiro<br></div></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-11-17 19:55 GMT+09:00 Sławek Kapłoński <span dir="ltr"><<a href="mailto:slawek@kaplonski.pl" target="_blank">slawek@kaplonski.pl</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
Thx all of You for explanations. So I think that [1] can be closed as<br>
"Won't fix" now. Am I right?<br>
<br>
[1] <a href="https://bugs.launchpad.net/neutron/+bug/1640767" rel="noreferrer" target="_blank">https://bugs.launchpad.net/<wbr>neutron/+bug/1640767</a><br>
<span class="im HOEnZb"><br>
--<br>
Best regards / Pozdrawiam<br>
Sławek Kapłoński<br>
<a href="mailto:slawek@kaplonski.pl">slawek@kaplonski.pl</a><br>
<br>
</span><div class="HOEnZb"><div class="h5">On Wed, 16 Nov 2016, Dean Troyer wrote:<br>
<br>
> > Excerpts from Sławek Kapłoński's message of 2016-11-16 22:36:41 +0100:<br>
> >> Hello,<br>
> >> So I want to ask all of You how in Your opinion it should be solved.<br>
> >> Currently there is inconsistency between CLI clients and<br>
> >> API/Horizon/Openstack SDK (I checked that it is possible to create<br>
> >> resource without name via SDK).<br>
><br>
> There are a number of intentional inconsistencies between OSC and the<br>
> various REST APIs, precisely because many of the the APIs themselves<br>
> are very inconsistent not only between projects but even within each<br>
> project. When those APIs are directly reflected in the CLI, like<br>
> happens with many of the project-specific CLIs, the users suffer due<br>
> to the inconsistencies.<br>
><br>
><br>
> On Wed, Nov 16, 2016 at 4:03 PM, Doug Hellmann <<a href="mailto:doug@doughellmann.com">doug@doughellmann.com</a>> wrote:<br>
> > The OpenStackClient team made the decision to always require names<br>
> > for newly created resources. Perhaps Dean or Steve can fill in more<br>
> > of the background, but my understanding is that this is a design<br>
> > decision for the user interface implemented by OSC, and not is not<br>
> > considered a bug.<br>
><br>
> Doug is correct here, we (OpenStackClient) made a specific decision in<br>
> the command structure to always use the resource name as the<br>
> positional argument of a create command. In this case I believe the<br>
> consistency is worth what pain it may cause to invent a name for a new<br>
> policy.<br>
><br>
> We have done UX surveys with OSC at the last two summits and the<br>
> number one favorable comment from the users (varying from cloud<br>
> consumers to operators to OpenStack developers) has been regarding how<br>
> much they appreciate the command consistency. This is our biggest<br>
> feature.<br>
><br>
> dt<br>
><br>
> --<br>
><br>
> Dean Troyer<br>
> <a href="mailto:dtroyer@gmail.com">dtroyer@gmail.com</a><br>
><br>
> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</div></div><br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br></div>