On Wednesday, January 30, 2013 4:52:46 AM UTC-6, Sylvain Mougenot wrote:
>
> Hello, I'm new to puppet using a puppet-master. And I couldn't figure out
> what's the best practice I need.
>
> *My context : *
> - puppet-master with a puppet dashboard is setup and running
> - few modules are ready and fully fonctionnal (tested using vagrant and
> "puppet apply")
> - there are some nodes in different "zone" (such as dev, QA, preprod,
> prod, ...)
>
> In fact,
> I've some shared resources in a zone :
> - SQL data-base
> - Mail server
> - ...
> And my apps are running in several nodes (for the same zone) :
> - one node as the front-end role
> - another as the back-office role
> - ....
> So I'd like to setup the configuration variables in one place (by zone)
> and reuse it among nodes in the same zone.
> (Obviously, every node as some specific configurations)
>
> *My question is :*
> - How can I share some variable svalues among nodes (like those in the
> same zone for exemple)?
>
> *What to do ?*
> - I tryed to put the zone specific variables in a dedicated configuration
> file andimport it in the relevant nodes. But this didn't worked telling me
> that I redefined variable (as soon as I've several zones)
> - Should I create a template node by zone with thoses common varaibles?
> - Is there any other way to do?
>
>
There are very few appropriate uses for the 'import' function, and the
situation you describe is not one of them.
There are several ways you could approach the situation, but my first
recommendation would be to store your data in external YAML files and load
it via hiera. Supposing that you have a variable $zone (or similar) by
which a node's zone can be identified, you can configure hiera to provide
values appropriate for the current node's zone. Moreover, where you have
data that are common to most or all zones, you can configure it centrally
instead of duplicating it for each zone.
Alternatively, you can write the per-zone logic into your Puppet manifests,
like so:
case $zone {
'dev': {
$parm1 = 'red'
},
prod: {
$parm1 = 'blue'
}
}
In particular, note that neither the case statement nor the individual
per-case blocks narrow the scope of the declarations within. In the above
example, therefore, the value set in the case statement for variable $parm1
is visible outside. Only class bodies, definition bodies, and node blocks
narrow the scope of declarations within.
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
