Re-appropriating (mis-appropriating?) roles - Content organization question

Archives Ansible Project
1

Hi,

I’m looking at the best practices page at Content Organization and Directory Layout.

For our application, I’m considering re-appropriating (or mis-appropriating?) the definition of “roles”. I’d prefer to have “roles” contain a “chunk” of configuration that could then be used by a playbook.

So, for example, I’d have
roles/
MySQL/
MSSQL/
ODBC/
ETC-1/
ETC-2/
ETC-3/

each of these would contain all the steps required for setting up a particular “chunk” of configuration for all platforms we support.

This makes playbooks more lengthy/detailed as they will need to reference many roles, but I’m OK with this. For example.

2

That's reasonable. The best practices gives some guidance about this.
I would suggest setting up a common role too.

http://www.ansibleworks.com/docs/bestpractices.html

-luke