Create a qos-policy , name attribute is necessary when using openstack command line interface, and it become non essential option when I use API or curl command to create

[dong]

Create a qos-policy , name attribute is necessary when using openstack command line interface,
and it become non essential option when I use API or curl command to create.

creation of net has similar problem.

[Andreas Scheuring (andreas-scheuring)]

Can you please provide
- the OpenStack Neutron version and the command client version
- the exact steps to reproduce
Thanks!

[Reedip (reedip-banerjee-deactivatedaccount)]

Besides, seems to be more of OpenstackClient related issue, than Neutron's

[Slawek Kaplonski (slaweq)]

It looks that it is possible to create QoS policy without name calling API directly (with curl) but it is not possible with neutronclient and openstack client where NAME is required positional attribute.
I checked it on current master of OSC and Neutron.

Now question is: should we change neutronclient/OSC to allow create policy without name or forbid creation of policy without name on Neutron server side?

[Slawek Kaplonski (slaweq)]

I sent an email to openstack-dev ML to see how we could solve it in this and other similar cases. Mail can be found on http://lists.openstack.org/pipermail/openstack-dev/2016-November/107473.html

[Akihiro Motoki (amotoki)]

As we discussed in the above mailing list thread by slaweq, requiring 'name' is a design decision in both OSC and neutronclient CLI. Let's mark this as Won't Fix.