Upgrade playbook for docker
Since Mitaka version of kolla will use things like named volumes or thin containers, we need to include docker version bump as part of upgrade process
Blueprint information
- Status:
- Complete
- Approver:
- Michał Jastrzębski
- Priority:
- Undefined
- Drafter:
- Michał Jastrzębski
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Mark Goddard
- Completed by
- Mark Goddard
Related branches
Related bugs
Sprints
Whiteboard
Since we start using new docker features as in Mitaka (named volumes, shared net namespace to mention a few) we need to upgrade docker. As for now it is impossible without creating a container downtime, which means restarting vms on it.
Upgrading docker is the deployers concern. We do not upgrade docker. Just like we do not deploy docker initially (thats up to the deployer to setup docker). This blueprint must only be for documentation then? --SamYaple
There are three options. We could either document how to do an upgrade, or write a simple playbook or do both. The playbook would obviously go in a different repository such as kolla-ansible-host and be a different delivery in our project governance repository. Note this fits in well with our future direction from feedback I receive - people want us to deploy dependencies and manage them in concert with Kolla operation. --sdake
If we get the stable branch on docker 1.10.1 we won't have to worry about this. I'd recommend focusing our effort on that after mitaka-1 is cut and we resolve any critical issues prior to summit. --sdake
mgoddard: It's possible to upgrade docker by running bootstrap-servers again.
