I apologize if this horse has already been beaten to death, but I'm
new here and very, very confused. I'm just starting to work with
Puppet and I can not make heads or tails of the language: specifically
how to use parameterized classes. I've spent a week reading the docs
and testing manifests and
I don't understand Puppet Language. How can you take object-oriented
constructs such as 'class' and 'inheritance' and then not allow things like
multiple instances of a class, albeit with differing parameters. Defined
resource types don't help me as they don't have inheritance (which is
somet
Crap. I'm trying to dump Bcfg2 and move to something reasonable. But so
far, all my initial assumptions and patterns for Puppet fail. I think in
terms of heirarchy and inheritence for my systems (all nodes install a core
set of packages, some have exceptions for those core set of packages, et
I'm having difficulty determining the best course of action how to
implement /etc/resolv.conf on my RHEL5 hosts.
Here's my requirements, IN ORDER OF PRECEDENCE:
* All hosts, regardless of function, need /etc/resolv.conf
* Dependiing upon which environment the host lives in (i.e. Facture
$domain
On Friday, March 16, 2012 1:23:16 PM UTC-4, Peter Horvath wrote:
>
> So basically you want to avoid node config customization?
> You want an ultimate resolv class which will decide everything without
> you defining manually something in the node conf?
>
>
> What I *want* is this:
node basenode {
On Friday, March 16, 2012 1:36:23 PM UTC-4, Tim Mooney wrote:
>
> In regard to: [Puppet Users] Need advice how to architect solution for...:
>
> > I'm having difficulty determining the best course of action how to
> > implement /etc/resolv.conf on my RHEL5 hosts.
> >
> > Here's my requirements, I
