Aaron Lehmann 9b54994a8a Add support for update order ... This parameter controls the order of operations when rolling out an update task. Either the old task is stopped before starting the new one, or the new task is started first, and the running tasks will briefly overlap. This commit adds Rollout to the API, and --update-order / --rollback-order flags to the CLI. Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>		2017-04-06 17:23:36 -07:00
..
common.go	Fixing #24631, inspect output on swarm object types without labels is empty object {}	2017-02-15 01:25:55 -05:00
container.go	Add --stop-signal for service create and service update	2017-02-21 15:19:45 -08:00
network.go	Allow user to modify ingress network	2017-03-26 15:46:18 -07:00
node.go	added node ip autodetection	2016-11-03 08:10:14 -07:00
secret.go	Do not display the digest or size of swarm secrets	2016-11-22 18:13:27 -05:00
service.go	Add support for update order	2017-04-06 17:23:36 -07:00
swarm.go	api: Omit Cluster, Nodes, and Managers from swarm info when unavailable	2017-03-28 14:20:25 -07:00
task.go	Topology-aware scheduling	2017-02-27 13:29:54 -08:00