Convert core API to use extension framework
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:
-
2013.2
- Started by
- Russell Bryant
- Completed by
- Christopher Yeoh
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Ports images and ips api to v3 API
Gerrit topic: https:/
Addressed by: https:/
Port flavors core API to v3 tree
Addressed by: https:/
Ports image_metaadata API to v3 API
Addressed by: https:/
Ports consoles API to v3 API
Addressed by: https:/
Port limits core API to new extension framework
Addressed by: https:/
API Extensions framework for v3 API Part 2
Addressed by: https:/
Port server metadata to APIv3
Addressed by: https:/
Change resource links when url has no project id
Addressed by: https:/
Organize limits units and per-units constants
Addressed by: https:/
Port limits core API to API-v3 Part 2
Addressed by: https:/
Porting server metadata core api to API v3 Part 1
Addressed by: https:/
Prevents core API v3 to be black or whitelisted
Addressed by: https:/
Add API-v3 merged core API into core API list
Work Items
Dependency tree
* Blueprints in grey have been implemented.
