Proposal: Breaking out roles and leveraging galaxy features

[mattrasband]

Many of us contribute to these roles and need to duplicate the effort for usage in our own projects, which causes some possible fatigue.

I'd like to propose we break out the roles into their own repositories (under pyslackers). We could then create a repo pyslackers/playbooks that leverages ansible-galaxy's requirements.yaml feature.

The current breakdown appears to be:

• common -> pyslackers/ansible-role-common
• nginx -> pyslackers/ansible-role-nginx
• pythonapp -> pyslackers/ansible-role-pythonapp
• system_service -> pyslackers/ansible-role-system_service

Benefits:

• independently testable
• sharable to pyslackers and community members
• versioned independently
• generatable (ansible-galaxy init <nam>)

Drawbacks:

• adds one more step for usage (ansible-galaxy install -r requirements.yml && ansible-playbook website.yml)

An issue that @ovv commented on, and I agree with, when using public galaxy roles - is that we don't control them. This allows us to get both-and.

[mattrasband]

Changes required:

1. Break up the repos
2. Create a new repo for playbooks (this could actually go into each repo, e.g. website/sirbot...)

• Add roles_path = ./galaxy-roles to the ansible.cfg file
• Add the above to the .gitignore
• Create the requirements.yml (see here for using the github links)

[ovv]

👍

And having the playbook alongside the app make sense.