Heat Template for Docker Based Bay
The resulting stack should contain N number of nodes running a microOS with Docker, one of the nodes should be designated as master. Non-master nodes should have a single container running the swarm agent. The agent container should persist through reboots so that the node will re-join the cluster after a reboot. A master node should be running two containers, a swarm agent container just like all other nodes, and a separate swarm manager container. Both containers should persis reboots.
It is important to note that while the swarm agents do not need access to the Docker daemon over the network, the swarm manager does. So, the address and port advertised by the swarm agents should be accessible to the swarm manager container. The swarm manager container should also have it's management port exposed.
Blueprint information
- Status:
- Complete
- Approver:
- Adrian Otto
- Priority:
- High
- Drafter:
- Andrew Melton
- Direction:
- Approved
- Assignee:
- Andrew Melton
- Definition:
- Approved
- Series goal:
- Accepted for milestone-2
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Andrew Melton
- Completed by
- Steven Dake
Related branches
Related bugs
Sprints
Whiteboard
Size Estimate: L
Gerrit topic: https:/
Addressed by: https:/
Create heat template for docker-swarm bay
Work Items
Dependency tree
* Blueprints in grey have been implemented.