python-novaclient should use volumes endpoint instead of extensions

Bug #940017 reported by Vish Ishaya
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
High
Vish Ishaya

Bug Description

Now that nova-volumes has its own endpoint, python-novaclient should use it. Eventually these will move into a volume specific client.

Changed in nova:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Vish Ishaya (vishvananda)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-novaclient (master)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-novaclient (master)

Reviewed: https://review.openstack.org/4481
Committed: http://github.com/openstack/python-novaclient/commit/03f54c57e13f27324f0ac5aa556bf4ca94e3ed0e
Submitter: Jenkins
Branch: master

commit 03f54c57e13f27324f0ac5aa556bf4ca94e3ed0e
Author: Vishvananda Ishaya <email address hidden>
Date: Fri Feb 24 02:30:48 2012 +0000

    Makes novaclient use the volumes endpoint

     * Depends on https://review.openstack.org/#change,4479
     * Adds support to change service type including tests
     * Adds decorator for methods that need to use another service type
     * Changes volume and snapshots to use the volume endpoint
     * These extensions will move into the volume client once it exists
     * Fixes bug 940017

    Change-Id: I683e4ca6c67e278d8aa8a9acec3dc0f1872f43f2

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → essex-4
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: essex-4 → 2012.1
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.