Re: [Puppet Users] Make puppet indifferent to package

On 01/31/2010 01:44 PM, Dan Bode wrote: > > > On Fri, Jan 29, 2010 at 9:58 AM, Doug Warner > wrote: > > Running puppet 0.24.8, I'd like to make Puppet be indifferent/ignore > whether a > package is installed or not. The hangup here is that I include a > c

[Puppet Users] Re: Make puppet indifferent to package

On Feb 1, 7:28 am, Doug Warner wrote: > I forgot to mention that I've tried "ensure => absent" in my child class but > the package still seems to get installed. [...] > class PkgGroup {} > class PkgGroup::InstallPkg inherits PkgGroup { >   package { coolpkg: ensure => latest, }} > > class PkgG

[Puppet Users] Re: Make puppet indifferent to package

On Feb 1, 8:11 am, jcbollinger wrote: > Since this is a hack anyway, perhaps it would be quicker and easier to > comment out the relevant include statement, or to use an if statement > to disable it for the particular node in question. Apologies for following up on my own post, but I realized a

Re: [Puppet Users] Re: Make puppet indifferent to package

On 02/01/2010 09:11 AM, jcbollinger wrote: > I'm inclined to think, then, that PkgGroup::InstallPkg::disabled is > not being included in the manifest for the affected node. Perhaps > it's part of a conditional branch that's not taken? This is exactly what it seems is going on; I don't see it refe

[Puppet Users] Puppet client - could not parse YAML data

Any ideas? Getting this error below from only 2 out of a total of 200 clients... puppetd[26557]: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not parse YAML data for node : syntax error on line 89, col 7: `' Client and Master Puppet versions are .25.1 -- You receiv

Re: [Puppet Users] Re: Make puppet indifferent to package

On 01/02/10 14:55, Doug Warner wrote: > > Since it's part of my base node that every box inherits, it's pretty painful > to just ignore this one class. And as Dan said, this type of thing should be > easily doable. Here's an alternate approach: 1. Install extlookup 2. In your base class, have s

[Puppet Users] Distributing Facts to client.

I have built my own fact to add to facter. When I manually put the script in /usr/lib/ruby/1.8/facter it works fine. I can run facter and I see the output from my script. My problem is I cannot get puppetmasterd to distribute the fact to my clients. Debian Lenny. Client version of puppet: 0.25.1

[Puppet Users] Live near Oslo? Want to work with Puppet?

We're hiring personnel with sysadmin experience in UNIX based systems. We want someone who has heard of puppet and likes automation! Must haves: * UNIX experience (One or more of Linux, BSD, Solaris et.al.). * Heard of Puppet and like automation. * Good social skills. * Live near Oslo or willing t

[Puppet Users] Re: Puppet client - could not parse YAML data

solved... Need to remove the .yaml files in /var/puppet/yaml/node and /var/puppet/yaml/facts (or where ever you may have these files, search for them). Then the client will run and the files will get rebuilt. On Feb 1, 11:16 am, Jason Amato wrote: > Any ideas? > > Getting this error below from

Re: [Puppet Users] Distributing Facts to client.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2/02/10 2:59 AM, Brian Schrock wrote: > I have built my own fact to add to facter. When I manually put the > script in /usr/lib/ruby/1.8/facter it works fine. I can run facter and > I see the output from my script. > > My problem is I cannot get pu

Re: [Puppet Users] Distributing Facts to client.

On Mon, Feb 1, 2010 at 12:52 PM, James Turnbull wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 2/02/10 2:59 AM, Brian Schrock wrote: >> I have built my own fact to add to facter. When I manually put the >> script in /usr/lib/ruby/1.8/facter it works fine. I can run facter and >> I

Re: [Puppet Users] Distributing Facts to client.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2/02/10 8:46 AM, Nigel Kersten wrote: >> I think this is the bit confusing people. The wiki makes it sound like >> the [plugins] mountpoint is optional, and you only need to worry about >> removing the path parameter if you already have a plugins mo

[Puppet Users] New employee: Michael DeHaan

Hello everyone, We're very excited to announce that Michael DeHaan, the founder of the Cobbler project, has joined Reductive Labs, starting today: Michael lives in Raleigh, North Carolina and has written systems management software for Red Hat (where he wrote Cobbler and also helped creat

Re: [Puppet Users] Distributing Facts to client.

Hi, Nigel Kersten wrote: I think this is the bit confusing people. The wiki makes it sound like the [plugins] mountpoint is optional, and you only need to worry about removing the path parameter if you already have a plugins mountpoint. The [plugins] mount point is optional: I don't even have

Re: [Puppet Users] New employee: Michael DeHaan

Welcome Mike, glad to see you are on board. -Chris On Mon, Feb 1, 2010 at 5:04 PM, Luke Kanies wrote: > Hello everyone, > > We're very excited to announce that Michael DeHaan, the founder of the > Cobbler project, has joined Reductive Labs, starting today: > > Michael lives in Raleigh, North Ca

Re: [Puppet Users] New employee: Michael DeHaan

On Mon, 1 Feb 2010 14:04:40 -0800, Luke Kanies wrote: > Hello everyone, > > We're very excited to announce that Michael DeHaan, the founder of the > Cobbler project, has joined Reductive Labs, starting today: > > Michael lives in Raleigh, North Carolina and has written systems > management

[Puppet Users] cfengine like groups

Greetings, CFEngine 2 (not sure about 3) allows groups definitions such as groups: ntp = { ntpserv1 ntpserv2 } and the ability to negate such as links: !ntp:: /etc/inet/ntp.conf -> /etc/inet/ntp.client I was wondering how I would accomplish something like it in Puppe

[Puppet Users] puppet vs chef

Hi All, if you happen to be in Singapore tomorrow (3/2/2010) I'll be doing the puppet part of PuppetVsChef at the Singapore hacker space. cheers, Ohad -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-

[Puppet Users] Cannot seem to turn off the CA

Trying to manage my certs sanely, upgrading from 0.24.8 -> 0.25.3 I setup one host as the CA and have all my clients point to that. Then I have several puppetmaster's running on other hosts. Problem is, puppetmasterd seems to be hardcoded to be a cert authority Even if I set the 'ca' flag to fals

Re: [Puppet Users] Cannot seem to turn off the CA

On 2/1/10 8:10 PM, nicholas wrote: Trying to manage my certs sanely, upgrading from 0.24.8 -> 0.25.3 I setup one host as the CA and have all my clients point to that. Then I have several puppetmaster's running on other hosts. Problem is, puppetmasterd seems to be hardcoded to be a cert authori