Aaron Lehmann 57ae29aa74 Add failure action for rolling updates ... This changes the default behavior so that rolling updates will not proceed once an updated task fails to start, or stops running during the update. Users can use docker service inspect --pretty servicename to see the update status, and if it pauses due to a failure, it will explain that the update is paused, and show the task ID that caused it to pause. It also shows the time since the update started. A new --update-on-failure=(pause|continue) flag selects the behavior. Pause means the update stops once a task fails, continue means the old behavior of continuing the update anyway. In the future this will be extended with additional behaviors like automatic rollback, and flags controlling parameters like how many tasks need to fail for the update to stop proceeding. This is a minimal solution for 1.12. Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>		2016-07-25 08:51:19 -07:00
..
container.go	Use newer default values for mounts CLI	2016-07-06 22:34:39 -04:00
network.go	Check if DriverState is valid before using in convert	2016-06-17 09:17:03 -07:00
node.go	Replace secrets with join tokens	2016-07-21 15:23:03 -07:00
service.go	Add failure action for rolling updates	2016-07-25 08:51:19 -07:00
swarm.go	Replace secrets with join tokens	2016-07-21 15:23:03 -07:00
task.go	swarm: add log driver support for services	2016-07-15 21:39:27 -07:00