0c739d4e24
This is an untested change because I don't have the same environment as Redbrick, but I think it would be beneficial to deploy the jobs using Ansible. This means that it can be automated in the future. One drawback of this approach is that we don't plan ahead of time, but that should be done as part of a pull request anyways. |
||
|---|---|---|
| .. | ||
| bin | ||
| group_vars | ||
| roles | ||
| templates | ||
| hosts.sample | ||
| README.md | ||
| redbrick-ansible.yml | ||
Redbrick Ansible Playbook
To run various roles, make sure you edit the redbrick-ansible.yml playbook and comment out whatever roles you do not want to run.
This playbook is supposed to used as a starting base, extend or modify it as you see fit. I would suggest you create a copy of it and add that file to the .gitignore file so that you're not constantly reverting your changes.
Running
Below is an example of how to run this playbook:
$ ansible-playbook -i hosts redbrick-ansible.yml
This command assumes hosts is your hosts file, you can copy the sample host file and modify the credentials in group_vars
Contributing
Please add all roles into the roles directory, following the same directory structure.
You should also add the role and a small description of what it does into redbrick-ansible.yml, this is to make it easier to run commands and modify the playbook at a glance.
If you have any questions, please mail/ping distro in Redbrick.