Add support for multiple swift backends
Currently, glance supports only a single swift store. For instance, when one swift backend is out of space, we need ability to configure a new store.
We need to define a new location format as follows:
swift:/
"store" would denote which backend store we wish to use. We would then define the attributes of that store in the configuration.
That allows us to specify different credentials for each store, but also offers the flexibility to specify different auth url endpoints. (Or even the potential -- with additional functionality -- to migrate from a single tenant store to a multi-tenant store).
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Brian Rosmaita
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Remove user and key from location in swift
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Differentiate user and system created swift location
This blueprint description is a bit confusing, because glance currently supports as many as 1 different swift store per location, since the swift auth_url and user credentials are directly in the image location. Can you clarify the real problem here? Is it just attempting to group the swift stores in a different way?
Thanks!
markwash more-info 2014-02-21
Let's abandon this until we see what happens with the dependency.
rosmaita abandoned 2014-03-28
Addressed by: https:/
Remove user and key from location in swift
Work Items
Dependency tree
* Blueprints in grey have been implemented.
