Remove glance-registry server
The glance-registry server is no longer needed. The v1 API implementation still depends on it, so it isn't straightforward to just remove it.
Blueprint information
- Status:
- Complete
- Approver:
- Brian Waldon
- Priority:
- High
- Drafter:
- Brian Waldon
- Direction:
- Approved
- Assignee:
- Brian Waldon
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
- Not started
- Milestone target:
- None
- Started by
- Completed by
- Mark Washenberger
Related branches
Related bugs
Sprints
Whiteboard
UPDATE: Pushing this back to Grizzly as this will cause a lot of trouble downstream if we do it now.
UPDATE 2: Thinking that this should be pushed back further. We'll make it easier to interface with the registry server internally so we don't feel so compelled to kill it.
Second update is now taken as the given approach. Namely, we will create abstractions to hide the registry behind the db api. This way, deployments can use the registry for both api v1 and v2, or for neither. In the process, I expect we will deprecate and probably delete the registry v1 api.
-markwash
I wonder if we still need this blueprint. registry-api-v2 and registry-db-driver should cover the work of making the registry optional. Since we're planning to keep it as an optional deployment strategy I think this blueprint might be a bit confusing for people.
-- flaper87