So that I can be sure that I don't need my systems to be
forwards-compatible...
I want to say:
- For some combination of server groups, applications and versions:
- Stop all the existing versions of applications on all the servers
they run on (*so I can be sure that old application versions won't
see messages produced by newer versions*)
- When all services have stopped, deploy the new versions of the
services to the appropriate servers (all of our services deploy in an
identical way- download a tar from S3, unpack it, create an upstart
service
that calls run.sh, provided inside the tar)
- Restart the stack
This an old-fashioned way of doing things but we don't need rolling
deployments. All of our services are asynchronous and tolerant of outages.
The cost of downtime during deployment is far less than the cost of having
to think about forwards compatibility everywhere. Backwards compatibility
we're happy to think about.
This doesn't fit my understanding of Ansible's model, where there's not
much coordination between playbooks.
Can anyone suggest a solution? Or maybe there's a better way to achieve the
original goal of avoiding forwards-compatibility?
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/def447fe-670c-486f-9c90-acb8c88c34e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
