Final Features needed in nova to run cinder separately
Remove remaining coupling between nova-compute and nova-volumes so cinder can run stand-alone
Blueprint information
- Status:
- Complete
- Approver:
- Vish Ishaya
- Priority:
- Essential
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Vish Ishaya
- Definition:
- Approved
- Series goal:
- Accepted for folsom
- Implementation:
-
Implemented
- Milestone target:
-
2012.2
- Started by
- Vish Ishaya
- Completed by
- Vish Ishaya
Related branches
Related bugs
Sprints
Whiteboard
1. Convert Volume id to UUIDs (DONE - vish + jgriffith)
https:/
https:/
https:/
2. Stop messing with volumes db/volume_api in live migration(DONE - vish)
https:/
3. Remove instances foreign key and fix: (DONE - jgriffith)
https:/
4. Remove the following from volumes/api (IN PROGRESS - vish)
https:/
5. Expose the following apis as extensions (MOVED TO CINDER, IN REVIEW - sleepsonthefloor) https:/
attach
detach
reserve_volume
unreserve_
initialize_
terminate_
check_detach (no need to make extension, calling side only)
check_attach (no need to make extension, calling side only)
5. Add extensions to cinderclient (MERGED - sleepsonthefloo
6. Make alternative volume_api that uses cinder client (IN PROGRESS - sleepsonthefloor jgriffith) (covered in https:/
Gerrit topic: https:/
Addressed by: https:/
Add Cinder Volume API to Nova
Addressed by: https:/
Modify ec2/cloud to be able to user Cinder
Addressed by: https:/
Add ServiceCatalog entries to enable Cinder usage
Work Items
Dependency tree

* Blueprints in grey have been implemented.