Swarm High Availability
Swarm bay types currently do not support high availability. For example, only a single swarm master can be deployed even though the bay api supports the --master-count attribute. Key services such as the Swarm API, the k/v store (i.e. etcd), etc.. should have the option to be highly available through the --master-count attribute.
Blueprint information
- Status:
- Complete
- Approver:
- Adrian Otto
- Priority:
- Low
- Drafter:
- Daneyon Hansen
- Direction:
- Approved
- Assignee:
- Eli Qiao
- Definition:
- Approved
- Series goal:
- Accepted for mitaka
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Eli Qiao
- Completed by
- Eli Qiao
Related branches
Related bugs
Sprints
Whiteboard
Swarm HA Guide: https:/
I would like to take, can you assign to me -(eliqiao)taget-9
The following patch (abandoned) included support for etcd HA:
https:/
The above patch was replaced by several smaller patches:
https:/
https:/
https:/
Etcd HA was removed from the above patches since it's not required to add the Magnum CNM to Swarm. I suggest leveraging some of the code in patch 224367 for your Swarm HA work.
Gerrit topic: https:/
Addressed by: https:/
Swarm: Split swarm.yaml to swarmcluster.yaml and swarmmaster.yaml
Gerrit topic: https:/
Addressed by: https:/
WIP Swarm: Add swarm master HA support
Addressed by: https:/
Functional: Use Magnum client to test container actions on Swarm bay
Addressed by: https:/
Set DEFAULT_
Addressed by: https:/
Share get_discovery_url in templates
Work Items
Dependency tree
* Blueprints in grey have been implemented.
