Aaron Lehmann 6d4b527699 Service update failure thresholds and rollback ... This adds support for two enhancements to swarm service rolling updates: - Failure thresholds: In Docker 1.12, a service update could be set up to either pause or continue after a single failure occurs. This adds an --update-max-failure-ratio flag that controls how many tasks need to fail to update for the update as a whole to be considered a failure. A counterpart flag, --update-monitor, controls how long to monitor each task for a failure after starting it during the update. - Rollback flag: service update --rollback reverts the service to its previous version. If a service update encounters task failures, or fails to function properly for some other reason, the user can roll back the update. SwarmKit also has the ability to roll back updates automatically after hitting the failure thresholds, but we've decided not to expose this in the Docker API/CLI for now, favoring a workflow where the decision to roll back is always made by an admin. Depending on user feedback, we may add a "rollback" option to --update-failure-action in the future. Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>		2016-10-18 10:09:50 -07:00
..
convert	Service update failure thresholds and rollback	2016-10-18 10:09:50 -07:00
executor	Update docker stop and docker restart to allow not specifying timeout and use the one specified at container creation time.	2016-10-17 12:53:35 -07:00
provider	Add engine-api types to docker	2016-09-07 11:05:58 -07:00
cluster.go	Service update failure thresholds and rollback	2016-10-18 10:09:50 -07:00
filters.go	Add engine-api types to docker	2016-09-07 11:05:58 -07:00
helpers.go	Fix spelling in comments, strings and documentation	2016-07-03 20:58:11 +03:00
listen_addr.go	Add fallback to resolveSystemAddr() in linux	2016-09-09 13:27:57 -07:00
listen_addr_linux.go	Add fallback to resolveSystemAddr() in linux	2016-09-09 13:27:57 -07:00
listen_addr_others.go	Add fallback to resolveSystemAddr() in linux	2016-09-09 13:27:57 -07:00