On Mon, Mar 21, 2011 at 01:05:56PM -0700, jcbollinger wrote:
>
> On Mar 21, 1:20 pm, Ashley Gould wrote:
> > Please forgive my ignorance. I find myself, a linux admin brought
> > up on howtos and books with animals on the cover, suddenly plunged
> > by puppet into a world of developers and compu
On Mar 21, 2011, at 1:39 PM, jcbollinger wrote:
>
> On Mar 21, 3:15 pm, Brian Gallew wrote:
>> It has occurred to me that another way of doing this would be to use defines
>>
>> define kludge($sudo_add_rule=undef) {
>> node { "${name}":
>> class {sudoers: additional_rules => [$su
On Mar 21, 3:15 pm, Brian Gallew wrote:
> It has occurred to me that another way of doing this would be to use defines
>
> define kludge($sudo_add_rule=undef) {
> node { "${name}":
> class {sudoers: additional_rules => [$sudo_add_rule}}
> }
> }
>
> The beauty of this is th
On Mar 21, 1:40 pm, jcbollinger wrote:
> On Mar 21, 12:20 pm, hai wu wrote:
>
> > I am going to use parameterized class together with extlookup, where
> > extlookup is used to provide different parameter value for different node
> > based on extlookup_precedence, the parameterized class needs t
It has occurred to me that another way of doing this would be to use defines
define kludge($sudo_add_rule=undef) {
node { "${name}":
class {sudoers: additional_rules => [$sudo_add_rule}}
}
}
The beauty of this is that it gets around the traditional problem of node
inherita
On Mar 21, 1:20 pm, Ashley Gould wrote:
> Please forgive my ignorance. I find myself, a linux admin brought
> up on howtos and books with animals on the cover, suddenly plunged
> by puppet into a world of developers and computer scientists. Could
> you explain what is "idempotency" and "support
On Mar 21, 12:20 pm, hai wu wrote:
> I am going to use parameterized class together with extlookup, where
> extlookup is used to provide different parameter value for different node
> based on extlookup_precedence, the parameterized class needs to be declared
> once in parent node, any issues yo
On Mon, Mar 21, 2011 at 04:23:40AM -0700, Bill Proud wrote:
> The following would work:
>
> node default {
> class { sudoers: }
> }
>
> node 'sl11lab02' {
> class { sudoers: additional_rules => [ "$rules_uas" ] }
> }
>
This does work, but I lose inheritance from node default.
In fact, t
On Mon, Mar 21, 2011 at 07:47:14AM -0700, jcbollinger wrote:
>
> Parameterized classes are not resources any more than ordinary classes
> are, syntax similarity notwithstanding. You cannot override the
> parameters of a parameterized class.
>
> Defined types are effectively custom resource type
On Mar 21, 4:56 am, Guillaume Rousse wrote:
> Le 18/03/2011 19:15, jcbollinger a crit :> If you have many nodes with
> various small differences between them,
> > then perhaps it's time to look into an external node classifier.
>
> If I'm understand correctly, this just move the problem elsewhe
I am going to use parameterized class together with extlookup, where
extlookup is used to provide different parameter value for different node
based on extlookup_precedence, the parameterized class needs to be declared
once in parent node, any issues you could forsee with this plan?
- Hai
On Mon,
On Mar 21, 7:10 am, Guillaume Rousse wrote:
> Le 21/03/2011 10:56, Guillaume Rousse a crit :> Le 18/03/2011 19:15,
> jcbollinger a crit :
> >> If you have many nodes with various small differences between them,
> >> then perhaps it's time to look into an external node classifier.
> > If I'm unde
Le 21/03/2011 10:56, Guillaume Rousse a écrit :
> Le 18/03/2011 19:15, jcbollinger a écrit :
>> If you have many nodes with various small differences between them,
>> then perhaps it's time to look into an external node classifier.
> If I'm understand correctly, this just move the problem elsewhere
The following would work:
node default {
class { sudoers: }
}
node 'sl11lab02' {
class { sudoers: additional_rules => [ "$rules_uas" ] }
}
On Mar 18, 12:03 am, Ashley Gould wrote:
> I am exploring usage of parameterized classes. I hit a wall when
> trying to override values of paramet
Le 18/03/2011 19:15, jcbollinger a écrit :
> If you have many nodes with various small differences between them,
> then perhaps it's time to look into an external node classifier.
If I'm understand correctly, this just move the problem elsewhere
(potentially making it easier to solve), as the class
On Fri, Mar 18, 2011 at 7:01 PM, Ashley Gould wrote:
> On Fri, Mar 18, 2011 at 11:15:56AM -0700, jcbollinger wrote:
>>
>>
>> On Mar 17, 6:03 pm, Ashley Gould wrote:
>> > I'm hoping to avoid using subclasses, because there would have to
>> > be oodles of them to accomodate the all the variations b
On Fri, Mar 18, 2011 at 11:15:56AM -0700, jcbollinger wrote:
>
>
> On Mar 17, 6:03 pm, Ashley Gould wrote:
> > I'm hoping to avoid using subclasses, because there would have to
> > be oodles of them to accomodate the all the variations between nodes.
> >
> > node default {
> > class { sudoer
On Mar 17, 6:03 pm, Ashley Gould wrote:
> I'm hoping to avoid using subclasses, because there would have to
> be oodles of them to accomodate the all the variations between nodes.
>
> node default {
> class { sudoers: }
>
> }
>
> node 'sl11lab02' inherits default {
>
> # this runs but do
18 matches
Mail list logo
