sort networks and subnetworks by name as default

[Christian Berendt]

I think it's more intuitive to sort networks and subnetworks by name and not by id as default when calling the list methods.

[Salvatore Orlando (salvatore-orlando)]

I think your suggestion makes sense.
This is only for the default sort keys.
Quantum API already supports sorting.

[Joris Roovers (joris-roovers)]

Hi Salvatore,

Being new to neutron dev, I'd be interested to work on this as I assume this is something that is relatively straightforward (sorting a list).

I'll reach out on IRC.

[Eugene Nikanorov (enikanorov)]

Could someone explain why is that a bug for neutron and not for neutron client?
It would be strange to apply sorting for networks only, also I would not introduce sorting into the server directly unless asked from the client.
So to me it seems like a bug for neutron client.

[Joris Roovers (joris-roovers)]

I agree with Eugene, I feel that sorting returned resources is a 'view' manipulation that should happen on the client side.

I did talk this over with Salvatore, and he suggested doing this for all resources that have a 'name' attribute, rather than only subnets and networks. In any case, I still believe if this is desired behavior, it should happen client side.

[Christian Berendt (berendt)]

https://review.openstack.org/#/c/92052/

[OpenStack Infra (hudson-openstack)]

Change abandoned by Christian Berendt (<email address hidden>) on branch: master
Review: https://review.openstack.org/92052

[Armando Migliaccio (armando-migliaccio)]

This bug is > 172 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

[Launchpad Janitor (janitor)]

[Expired for python-neutronclient because there has been no activity for 60 days.]