Implement Registry Database Driver
This change is part of the kill-registry blueprint and is intended to implement a new db driver for the registry service in order to support legacy deployments based on 2 separate services.
Adding a testing plan for folks willing to give this feature a try:
* Install Glance
* Configure as usual but:
* glance-api:
- Make sure Glance's API v2 is enabled in both glance-api.cof and glance-
- Make sure glance-api.conf uses: data_api = glance.
* glance-registry:
- Make sure Glance's Registry API v2 is enabled in glance-
- Make sure glance-
* Use glanceclient normally but make sure it points to the api version 2
- glance --os-image-
Blueprint information
- Status:
- Complete
- Approver:
- Brian Waldon
- Priority:
- High
- Drafter:
- Brian Waldon
- Direction:
- Approved
- Assignee:
- Flavio Percoco
- Definition:
- Approved
- Series goal:
- Accepted for havana
- Implementation:
- Implemented
- Milestone target:
- 2013.2
- Started by
- Flavio Percoco
- Completed by
- Thierry Carrez
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Move sql_conneciton option into sqlalchemy package.
Addressed by: https:/
Add custom RPC(Des|S)erializer to common/rpc.py
Addressed by: https:/
Make db properties functions consistent with the DB API
Addressed by: https:/
DB Driver for the Registry Service
Work Items
Dependency tree
* Blueprints in grey have been implemented.