Convert core API to use extension framework

Registered by Christopher Yeoh on 2013-04-19

As part of the v2->v3 conversion, convert the core functionality of the v3 API to use the extension framework. This does not change what is considered core, just how it is implmented.

Blueprint information

Status:
Complete
Approver:
Russell Bryant
Priority:
High
Drafter:
None
Direction:
Approved
Assignee:
Christopher Yeoh
Definition:
Approved
Series goal:
Accepted for havana
Implementation:
Implemented
Milestone target:
milestone icon 2013.2
Started by
Russell Bryant on 2013-05-07
Completed by
Christopher Yeoh on 2013-07-16

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/v3-api-core-as-extensions,n,z

Addressed by: https://review.openstack.org/28756
    Ports images and ips api to v3 API

Gerrit topic: https://review.openstack.org/#q,topic:porting-core-api,n,z

Addressed by: https://review.openstack.org/28825
    Port flavors core API to v3 tree

Addressed by: https://review.openstack.org/28921
    Ports image_metaadata API to v3 API

Addressed by: https://review.openstack.org/28928
    Ports consoles API to v3 API

Addressed by: https://review.openstack.org/29369
    Port limits core API to new extension framework

Addressed by: https://review.openstack.org/28298
    API Extensions framework for v3 API Part 2

Addressed by: https://review.openstack.org/29589
    Port server metadata to APIv3

Addressed by: https://review.openstack.org/31632
    Change resource links when url has no project id

Addressed by: https://review.openstack.org/32903
    Organize limits units and per-units constants

Addressed by: https://review.openstack.org/35402
    Port limits core API to API-v3 Part 2

Addressed by: https://review.openstack.org/36455
    Porting server metadata core api to API v3 Part 1

Addressed by: https://review.openstack.org/36454
    Prevents core API v3 to be black or whitelisted

Addressed by: https://review.openstack.org/36453
    Add API-v3 merged core API into core API list

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.