neutron

limit default set of fields shown in *-list cmds

Bug #1036051 reported by dan wendlandt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Medium
yong sheng gong
neutron 2012.2 "folsom"
python-neutronclient
Fix Released
Undecided
yong sheng gong
python-neutronclient 2.1

Bug Description

Our list commands default to showing every field in an API entity, which means the tables always wrap and are a total mess in a reasonably sized terminal. At least with nova, only a subset of the columns are shown for list, and if more details are needed, it requires running show on a specific UUID/name (or in the case of quantum, specifying -c with list). With Quantum, I find that I regularly run quantum net-list -c id -c name to make sure the output is readable.

I'd suggest we have the following columns display by default:

quantum net-list: name, id, subnets (ideally, subnet cidrs, using verbose=True query)

quantum subnet-list: subnet-name, id, subnet-cidr, allocation-pools (really this command is less useful if we do a good job with net-list)

quantum port-list: port name, port id, port fixed-ips

You'd still be able to use the -c flag to define the set of columns that *-list returns, this is just about defining the default behavior. I image that most scripts would use -c, so I see this as mainly a question about human operators, particular newbie human operators.

dan wendlandt (danwent)
Changed in quantum:
status: New → Confirmed
importance: Undecided → Medium
milestone: none → folsom-3
tags: added: low-hanging-fruit
yong sheng gong (gongysh)
Changed in quantum:
assignee: nobody → yong sheng gong (gongysh)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to quantum (master)

Fix proposed to branch: master
Review: https://review.openstack.org/11323

Changed in quantum:
status: Confirmed → In Progress
Revision history for this message
yong sheng gong (gongysh) wrote :

I don't think it has something to do with quantum-client

yong sheng gong (gongysh)
Changed in python-quantumclient:
status: New → Invalid
Revision history for this message
dan wendlandt (danwent) wrote :

seems there is disagreement here on whether this should be fixed client or server side.

Changed in quantum:
milestone: folsom-3 → folsom-rc1
Revision history for this message
dan wendlandt (danwent) wrote :

Hi Yong,

Can you update this bug? Review seems to imply that this will be handled in the client (https://review.openstack.org/#/c/11323/), which conflicts with the status of this bug (invalid in client, valid in server).

Also, do we think this is doable for RC1, or should we drop it? I think it would help usability, but we're at the point where we really have to start dropping non-bugs, so unless we think this will be done in a day or two, we should probably drop it.

Revision history for this message
yong sheng gong (gongysh) wrote :

Hi Dan,
I don't object it should be done on the client side.
The whole effors should be less than one day, but I am at a conference on a business trip. Have no much time for it.

If no other guy wants to do it, I will do it tonight.

Thanks

Revision history for this message
dan wendlandt (danwent) wrote :

Ok, I think it would be very valuable to all new quantum users to have this completed for Folsom, so if we get it done in the next few days, let's keep it for Folsom. If we can't get it done by then, we'll have to target it to Grizzly. Thanks.

Changed in python-quantumclient:
status: Invalid → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-quantumclient (master)

Fix proposed to branch: master
Review: https://review.openstack.org/12044

Changed in python-quantumclient:
assignee: nobody → yong sheng gong (gongysh)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-quantumclient (master)

Reviewed: https://review.openstack.org/12044
Committed: http://github.com/openstack/python-quantumclient/commit/62f508939e367733552570cc3bac15b82436b981
Submitter: Jenkins
Branch: master

commit 62f508939e367733552570cc3bac15b82436b981
Author: yong sheng gong <email address hidden>
Date: Sat Sep 1 11:38:45 2012 +0800

    *-list command shows only limited fields normally.

    Bug #1036051

    We add list_columns in list commands to limit the output columns.
    The behaviour is overriden if we use -c in command.

    Change-Id: I0fa6c73cd7270d86aff01d3790d59c8d4e8a235a

Changed in python-quantumclient:
status: In Progress → Fix Committed
dan wendlandt (danwent)
Changed in quantum:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in quantum:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in quantum:
milestone: folsom-rc1 → 2012.2
Mark McClain (markmcclain)
Changed in python-quantumclient:
milestone: none → 2.1
Akihiro Motoki (amotoki)
Changed in python-quantumclient:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.