You're quite welcome. I'm happy to help. On Wed, Oct 26, 2016 at 2:14 PM Dan Rough <[email protected]> wrote:
> That's a good idea. Thanks! I hadn't thought of that. That will simplify > things in one or two locations. > > On 26 Oct 2016, at 22:01, Alexander H. Laughlin <[email protected]> > wrote: > > Hi Dan, > > Why not store the values in a dictionary and just pull the values you need > for any given server based on its key? > > Alex > > On Wednesday, October 26, 2016 at 1:39:21 PM UTC-7, Dan Rough wrote: > > Hi, > > I'd like to know how others are dealing with keeping their group_vars > files granular. Ours have become a little unwieldily and we're considering > approaches to breaking them apart. > > When we provision a server, we assign it to a number of groups. Among > those groups, each server is added to at least three groups. Firstly, we > add it to a group which defines its role, for example app_server. Another > group represents the location of the DC that the server is in, which might > be LON, for example. Thirdly, we also add it to a group which denotes > whether it is a production server or a test server, prod, for example. That > allows us to use ansible's patterns when we're configuring the server to do > something like this: - hosts: "prod:&LON:&app_server" or - hosts: > "prod:&ORD:&app_server". > > We have a variables which need to be defined based on these three > variables, Environment, Region and Role. Our current thinking is to create > a group_vars file for each of the possible combinations, > prod_LON_app_server, for example. The affect of this decision will mean > that we're going to see an explosion in the number of groups a server is > added to, and the number of group_vars files we maintain. > > Before we take this route, can anyone tell me if we're missing a trick? Is > there a technique that we're missing? > > Thanks! > > Dan. > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Ansible Project" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/ansible-project/_Fvptfvs-gk/unsubscribe. > To unsubscribe from this group and all its topics, 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/18a8673f-c17a-4ed1-ad15-45c438402166%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/18a8673f-c17a-4ed1-ad15-45c438402166%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Ansible Project" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/ansible-project/_Fvptfvs-gk/unsubscribe. > To unsubscribe from this group and all its topics, 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/922B0762-DDB2-45EC-B688-60CB004F2C14%40gamevy.com > <https://groups.google.com/d/msgid/ansible-project/922B0762-DDB2-45EC-B688-60CB004F2C14%40gamevy.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- A. H. Laughlin Chief Financial Officer Office of Finance Gahan Corporation -- -- 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/CAHu7ygZB9OBzgxK8wUS%2BixMPxcPTNP_qMxjtqYF6_%2BrF93epRQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
