How is this supposed to work?

[bkonetzny]

I'm not sure how this container should work. Are there special named service files needed for this?
On a rolling deploy, I expect that I start new services with updated containers and then shut-down the old services running the old containers.

I have a service template of my-service@.service and tried to run the container like this:

docker run -it yodlr/fleet-rolling-deploys my-service null -n 2 --noetcd

What did happen is that it started two services (my-service@1 and my-service@2) and did not shut down anything. I then re-ran the container call above and expected that two new services would be started (my-service@3 and my-service@4) and the old ones would have been shut down (my-service@1 and my-service@2), but actually nothing happened as the container did tell me everything was already running and there was nothing to destroy.

Could you please clarify how this container should be used and how the service files need to be named in order to work? Thanks in advance! :)

PS: Please let me know if this is only intended for internal use at yodlr, otherwise I would like to support this project and make a few PRs to streamline the code a bit :)

[rosskukulinski]

Goodness me, I never did writeup the documentation for this module. I'll take some time today & tomorrow to write up A) some quick n' dirty docs to get you going and B) Full docs for this and and its partner-in-crime https://github.com/yodlr/fleet-templater