quantum-client does not support network lookup by label

Bug #979527 reported by Anthony Young
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-neutronclient
Fix Released
Medium
Salvatore Orlando

Bug Description

This is needed in devstack to eliminate the use of mysql:

https://review.openstack.org/#patch,sidebyside,4665,8,exercises/quantum.sh

Revision history for this message
Gary Kotton (garyk) wrote :

Please note that the network name does not need to be unique.

Changed in quantum:
status: New → Confirmed
Revision history for this message
dan wendlandt (danwent) wrote :

we should try to get this as part of the client rewrite that yong is doing.

we can handle this the same way nova does when it lets you use names for VMs. if a VM name is not unique for the tenant, the command fails.

Changed in quantum:
importance: Undecided → Medium
assignee: nobody → yong sheng gong (gongysh)
Revision history for this message
dan wendlandt (danwent) wrote :

removing yong as the assignee, as anyone could really work on this now that the main client changes are in.

tags: added: low-hanging-fruit
Changed in quantum:
assignee: yong sheng gong (gongysh) → nobody
Changed in quantum:
assignee: nobody → Shanthkumar Khandre (shanth-khandre)
Revision history for this message
Shanthkumar Khandre (shanth-khandre) wrote :

HI,

Where you want to use the lookup by label ?

Can you elaborate more?

In Nova, you can boot the vm's with the same names but when deleting the vm's using the names (duplicate i.e., if there is more than one entry with the same name) then it raises the ERROR: Multiple server matches found for 'testnew', use an ID to be more specific.

Thanks,
Shanthkumar khandre

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

The following commands require that a network is specified, and it would be nice if we could provide that network as a name, instead of a UUID (assuming the name can be unambiguously mapped to a UUID for that tenant).

- net-delete
- net-update
- net-show

- subnet-create
- port-create

Changed in quantum:
assignee: Shanthkumar Khandre (shanth-khandre) → nobody
Changed in quantum:
assignee: nobody → Salvatore Orlando (salvatore-orlando)
Changed in python-quantumclient:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Salvatore Orlando (salvatore-orlando)
no longer affects: quantum
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/10276

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

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

commit d16e00a056bbe7ba576c4b7195180bfc383bbfad
Author: Salvatore Orlando <email address hidden>
Date: Tue Jul 24 23:45:10 2012 -0700

    Allow to retrieve objects by name

    Fixes bug 979527

    xxx-show commands now can accept either an id or a name of the resource to
    retrieve, similarly to the "nova get" command. This has been preferred to
    using mutually exclusive keyword argument, in order to avoid confusion
    with other CLI tools.

    NOTE: the current patch allow search by name only for networks.
    The restriction will be lifted once name attributes for port and subnets
    are added.

    Change-Id: Id186139a01c9f2cfc36ca3405b4024bd7780622e

Changed in python-quantumclient:
status: In Progress → Fix Committed
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.

Other bug subscribers

Remote bug watches

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