Hi!
Here I read
<http://docs.ansible.com/playbooks_best_practices.html#stage-vs-production>
about how to manage differences between staging and production servers.
As I understand it boils down to defining different variables to
different servers.
But what is the good way to handle differences in systems if they are
not only in variables but affect which packages should be installed or not.
In my case development environment is roughly a subset of
production/staging - no need to web-server and queue.
So how in this case how to describe what should go to production and
what in development servers?
I see two ways:
1) Make two host-groups - "base" and "live". in first - there would be
only one host-group - "base" and in second - two "base" and "live" which
would contain same hosts. And also there must be two playbooks -
"base_playbook" and "live_playbook" - first will be applied to "base"
hosts group and second to "live".
2) Second approach is to make variable like "environment" with three
possible values - "production", "staging", "development". And then use
conditional statements in playbooks.
Bot happroaches doesnt seem perfect, maybe there is a better ones?
--
With kind regards, Andrew Pashkin.
cell phone - +7 (985) 898 57 59
Skype - waves_in_fluids
e-mail - [email protected]
--
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/537B8C20.1040304%40gmx.co.uk.
For more options, visit https://groups.google.com/d/optout.
