Stig Sandbeck Mathisen writes:
> ,
> | node *.desktops.example.org {
> | case $server_role {
> | /:desktop:/ { include my::desktop::class }
> | /:mission_critical:/ { include corp::absolutely::vital:class }
> | /:whohooo:/ { include rubber::ducky }
> | }
> | }
On Tue, Jan 11, 2011 at 09:05:43AM -0800, Nigel Kersten wrote:
>
> I disagree that this approach is fundamentally wrong, but it's not
> always appropriate.
I'll concede I'm being a little over-emphatic, but the OP's situation
didn't read to me as if it had anything to justify that approach. And
Exinferis writes:
> Is that somehow possible with puppet?
Role-based configuration is possible with puppet. The selection of
available roles will have to be preconfigured, but it is possible.
Instead of selecting on the registered host name you select on the role
it reports to have.
You will
On Tue, Jan 11, 2011 at 8:57 AM, Bruce Richardson wrote:
> On Tue, Jan 11, 2011 at 02:09:27AM -0800, Exinferis wrote:
>> But what we really want to achieve is not to register every node in
>> our master configuration (hostnames can totally vary so no wildcard
>> matching), but to give the nodes th
On Tue, Jan 11, 2011 at 02:09:27AM -0800, Exinferis wrote:
> But what we really want to achieve is not to register every node in
> our master configuration (hostnames can totally vary so no wildcard
> matching), but to give the nodes the possibility to request a specific
> class or to report themse
We are currently using puppet with a node based configuration on the
master, so we have a structure similar to that:
node xyz {
/* do something here */
}
node default {
/* do something here */
}
in the included files and classes we have our setup procedures ongoing
and everything is worki
