I recommend you take a step back and look at the problem from the perspective of your overall Configuration Management (CM) process. For example, what are your configuration items (CIs)? What is your change management process? What is your version control process? First document these processes and then adapt Ansible to fit them. In my experience Ansible is very flexible and can fit whatever process you have in place. I wouldn't worry about Ansible's terminology. Roles, Groups, etc. can be whatever you want them to be; they are just arbitrary labels.
The most important thing is to identify your CIs. Then structure your playbooks to manage them. Their level of granularity depends on the level that your CM plan calls for. Each CI should be under version control at the very least. Avoid the mistake of a tool-centric perspective. Focus on good, quality processes and then customize the tools to support them. --Aaron On Tuesday, June 3, 2014 12:38:45 AM UTC-4, David Carmean wrote: > > > I was happy to see "roles" when I came back to Ansible after a few months, > but i've been struggling with how to apply them. I think this is partly > because of cognitive dissonance between my mental model and the current > terminology. > > In my mind, any particular role that a server may fill (and it may fill > more than one), in turn requires one or more "features" or "feature-sets" > in order to be able to fulfill that role. In other words, I think of a > heirarchy that looks like this; > > * appstack_X > ** server_n > *** role_a > **** feature_A > **** feature_E > **** feature_O > *** role_b > **** feature_A > **** feature_B > **** feature_G > > Anyone else gone through this thought process,or organize their configs > like this? > > > > -- 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/2600c6a1-5a6b-46dd-981f-6587ba120308%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
