Availability Zones
Registered by
Julian Edwards
Defining groups of nodes into "zones" through which clients can use as placement constraints.
Blueprint information
- Status:
- Complete
- Approver:
- Julian Edwards
- Priority:
- Essential
- Drafter:
- Julian Edwards
- Direction:
- Approved
- Assignee:
- Julian Edwards
- Definition:
- Approved
- Series goal:
- Accepted for 1.5
- Implementation:
-
Implemented
- Milestone target:
-
14.04
- Started by
- Julian Edwards
- Completed by
- Julian Edwards
Related branches
Related bugs
Sprints
Whiteboard
Use cases:
* client wants to use a node close to another for speed reasons
* client wants to use a node not close to another for HA reasons
* client wants to choose a geographical location
* client wants to define own zones
Zones are a first class citizen. Users will define the zones and then
attach nodes to zones.
Once defined, api clients such as juju will want to specify names of
zones as placement constraints when acquiring nodes.
(?)
Work Items
Work items:
Database modelling of zones and nodes' relation to zones: DONE
UI changes to manage zones and nodes in zones: DONE
Placement constraints for zones: DONE
Default zone for new nodes: DONE
