Hello All,
Would someone please explain Ansible process/governance around playbooks.
Thanks
Hello All,
Would someone please explain Ansible process/governance around playbooks.
Thanks
Hello All,
Would someone please explain Ansible process/governance around playbooks.
I think you would need to explain in a bit of detail what you mean by process/governance because that has a similar but different definitions in configuration management, change control and various other programs.
Hi Smooge,
I guess I want to say Governance around Development and Deployment of Ansible playbooks. Does this make more sense?
Hi Smooge,
I guess I want to say Governance around Development and Deployment of Ansible playbooks. Does this make more sense?
It is still fuzzy. Pretty much every site I know follows some governance system which is ‘site local’ which passes whatever control system they are using (ITIL, MOF, ISO-XXX000), and you adapt ansible to meet that. Some people just throw their ansible configs in a git repository and use github pr and issues to change things, others have every system administrator with their own tree, and others are using Tower to deploy and control their systems. [I expect that there are dozens of other methods people use a lot also.] What goes into the playbook and roles is then controlled in a similar method as cfengine, chef, salt or puppet. I am not sure if I am making anything clearer about my confusion on the question