Cluster Federation
The goal of this work is to enable account contents to be dispersed across multiple clusters, motivated by (a) accounts that might grow beyond the remaining capacity of a single cluster and (b) clusters offering differentiated service levels such as different levels of redundancy or different storage tiers. Following feedback at the Portland summit, the work is initially limited to dispersal at the container level, i.e. each container within an account may be stored on a different cluster, whereas every object within a container will be stored on the same cluster.
Note that this is distinct from container sync in that objects are only stored in one container.
More detail on wiki link below.
Blueprint information
- Status:
- Started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Good progress
- Milestone target:
- None
- Started by
- John Dickinson
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Store x-container-attr-* headers in container db.
Addressed by: https:/
Middleware module for container forwarding.
Addressed by: https:/
Refactor proxy/controllers obj & base http code
Addressed by: https:/
Container-
Addressed by: https:/
Add container forwarding support to updater daemon
Gerrit topic: https:/
Addressed by: https:/
middleware & proxy-server share http code
Gerrit topic: https:/
Addressed by: https:/
Generic means for persisting system metadata.
Gerrit topic: https:/
Addressed by: https:/
Merge branch 'master' into ec