Refactor nova.image to use an API object like nova.volume and nova.network
For some reason, nova.image does things differently than nova.volume and nova.network. Instead of nova.compute.
This blueprint is around the work to make a new nova.image.api module and have it called like other submodule "internal APIs" in Nova.
Blueprint information
- Status:
- Started
- Approver:
- John Garbutt
- Priority:
- Low
- Drafter:
- Jay Pipes
- Direction:
- Needs approval
- Assignee:
- Jay Pipes
- Definition:
- Pending Approval
- Series goal:
- Accepted for trunk
- Implementation:
-
Slow progress
- Milestone target:
- None
- Started by
- John Garbutt
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
https:/
Once the first patch (or so) is up, and an appropriate milestone is chosen, we can approve this good work --johnthetubaguy (9th April 2014)
Addressed by: https:/
WIP: standardize nova image API
Please choose a milestone, ensure the assignee is correct, before we can set priority and approve this blueprint --johnthetubaguy (28th April 2014)
John, is there anything else you need from me to prioritize this and set the definition to Approved? (jaypipes - May 5th 2014)
Gerrit topic: https:/
Addressed by: https:/
Align internal image API with volume and network
Now a patch is uploaded, and milestone chosen, I have approved this --johnthetubaguy (8th May 2014)
Are we likely to have the other patches for this up for review soon? This is at risk of being pushed out into Juno-2 --johnthetubaguy (30th May 2014)
Yes, remaining patch will be uploaded soon, thx John. (jaypipes, 2nd June, 2014)
Sorry, code not up in time to make it in time for juno-1, moving to juno-2 --johnthetubaguy 10th June 2014
Addressed by: https:/
live migrate conductor tasks to use nova.image.API
Addressed by: https:/
Standardization of nova.image.
Vish, are there any more patches needed for this? Moving to juno-3 for now, as its not clear if everything is up for review. If you can mark it as "Needs Code Review" feel free to move this back into juno-2. Thanks. --johnthetubaguy 15th July 2014
Yes, there are at least 2 more patches coming shortly. (and it's Jay, not Vish) :)
Feature Proposal Freeze means this must not land in juno, because it appears like the code is not all currently ready to be reviewed. To be able to merge in kilo, we would first need to merge a kilo spec. More details on the exact process will be available on the ML shortly. --johnthetubaguy 22nd August 2014
