[Puppet Users] Re: Mac Domainname and facter

[Paul Nasrat]

2009/9/23 engle :
>
> So, when I issue the command:
>
> ipconfig getpacket en0
>
> I get the proper domain name from DHCP. But, 'facter', does not
> display this when reporting the 'domain' or in the FQDN . Both of
> these list "local" for the domain name of the computer. In addition,
> in my 'resolv.conf', the correct domain name is listed as a 'search'
> domain as well as a general domain statement.
>
> So, I am still a bit unsure as to where facter is getting its
> infomation.

The current domain name stuff is a bit horky, and there are some
patches/issues for 1.6 to address this:

http://projects.reductivelabs.com/issues/2533

Paul

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Ruby on HP-UX B.11.11 (11iv1)

[Ohad Levy]

it sounds like your ruby is lacking the openssl libs? (or maybe your
system?)
Ohad

On Tue, Sep 22, 2009 at 3:01 AM, Mark Nelson  wrote:

>
> Hello
>
> I am hoping to deploy Puppet 0.25.0  within our Unix infrastructure.
> One of our systems runs on HP-UX B.11.11 (HP-UX 11iv1), I am having
> trouble getting ruby to run on this platform.  The version of ruby that
> is available on the HP-UX Software Archive (http://hpux.connect.org.uk/)
> is 1.8.4, however puppet generates an error when it starts up.
>
>  I have attempted to build 1.8.7 from source, ruby compiles
> successfully.  Puppet generates an SSL error when trying to start,
> unfortunately I am sending this mail from home and don't have a copy of
> the error messages.
>
> Had anyone successfully deployed puppet,  either 0.25.0 or any other
> version on HP-UX B.11.11.  If so where did you get your ruby binary from.
>
> Any help greatfuly received.
>
> Mark.
>
> --
> ---
> Mark Nelson - m...@tardis.cx
> This mail is for the addressee only
>
>
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Announcement: Foreman 0.1-1 is out

[Ohad Levy]

just for a follow up if anyone is having a similar problem :
http://theforeman.org/issues/show/29
Ohad

On Tue, Sep 22, 2009 at 7:51 PM, Matt  wrote:

>
> Hi Ohad,
>
> Great news with the upgrade! :-)
>
> I'm hitting a problem when trying to run import of facts.  It seems to
> work the first few times, but then I start getting this -
>
> # rake puppet:import:hosts_and_facts RAILS_ENV=production --trace
> (in /var/www/html/foreman)
> ** Invoke puppet:import:hosts_and_facts (first_time)
> ** Invoke environment (first_time)
> ** Execute environment
> ** Execute puppet:import:hosts_and_facts
> Importing from /var/lib/puppet/yaml/facts
> Importing server-01
> rake aborted!
> comparison of ActiveSupport::TimeWithZone with String failed
> /var/www/html/foreman/app/models/host.rb:177:in `<'
> /var/www/html/foreman/app/models/host.rb:177:in `importFacts'
> /var/www/html/foreman/app/models/host.rb:166:in `importHostAndFacts'
> /var/www/html/foreman/lib/tasks/puppet.rake:34
> /var/www/html/foreman/lib/tasks/puppet.rake:31:in `each'
> /var/www/html/foreman/lib/tasks/puppet.rake:31
> /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call'
> /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute'
> /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each'
> /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute'
> /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in
> `invoke_with_call_chain'
> /usr/lib/ruby/1.8/monitor.rb:238:in `synchronize'
> /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in
> `invoke_with_call_chain'
> /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke'
> /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task'
> /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level'
> /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each'
> /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level'
> /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in
> `standard_exception_handling'
> /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level'
> /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run'
> /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in
> `standard_exception_handling'
> /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run'
> /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31
> /usr/bin/rake:19:in `load'
> /usr/bin/rake:19
>
>
> 2009/9/21 Ohad Levy :
> > Hello All,
> >
> > I'm happy to announce the next stable release of Foreman, main new
> features
> > include:
> >
> > Integration of Puppet Reports, once enabled you would see a real time
> > overview of all of yours hosts status.
> > Improved support for multiple Puppet Masters (e.g. import facts and
> reports
> > from remote serves over http)
> > Simplified migration from existing external nodes setup, now its possible
> to
> > import your existing classifier data into Foreman.
> >
> > For a complete change log, please visit:
> > http://theforeman.org/projects/changelog/foreman
> > For feature requests, bugs, wiki etc, visit: http://theforeman.org
> >
> > If you already have Foreman installed, make sure you go through
> > http://theforeman.org/wiki/foreman/Upgrade_instructions.
> >
> > 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-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] failing to run a script within puppet

[Asif Iqbal]

I have a perl script that runs fine manually, but fails to run by puppet
Need some help with debug

(root)@scseast:~# cat test.pp
Exec { path =>
"/usr/bin:/usr/sbin:/bin:/usr/local/bin:/usr/local/sbin:/opt/csw/bin:/opt/csw/sbin",
   cwd => "/tmp",
}
exec {"/opt/SUNWcest/bin/cediag":}

(root)@scseast:~# /opt/csw/bin/puppet -d test.pp
debug: Exec[/opt/SUNWcest/bin/cediag]: Adding default for cwd
debug: Exec[/opt/SUNWcest/bin/cediag]: Adding default for path
debug: Creating default schedules
debug: Loaded state in 0.04 seconds
debug: Failed to load library 'shadow' for feature 'libshadow'
debug: //Exec[/opt/SUNWcest/bin/cediag]: Changing returns
debug: //Exec[/opt/SUNWcest/bin/cediag]: 1 change(s)
debug: //Exec[/opt/SUNWcest/bin/cediag]: Executing
'/opt/SUNWcest/bin/cediag'
debug: Executing '/opt/SUNWcest/bin/cediag'
err: //Exec[/opt/SUNWcest/bin/cediag]/returns: change from notrun to 0
failed: /opt/SUNWcest/bin/cediag returned 1 instead of 0 at
/home/iqbala/test.pp:5
debug: Finishing transaction 3483960 with 1 changes
debug: Storing state
debug: Stored state in 0.39 seconds
debug: Calling puppetreports.report
info: Sent transaction report in 0.59 seconds

(root)@scseast:~# /opt/SUNWcest/bin/cediag
Do you accept the licence terms? If so, enter "accept" :
cediag: licence: licence accepted by user

cediag: Revision: 1.94 @ 2007/07/26 22:55:08 UTC
cediag: Analysed System: SunOS 5.8 with KUP 117350-46 (MPR active)
cediag: Pages Retired: 0 (0.00%)
cediag: findings: 0 datapath fault message(s) found
cediag: findings: 0 UE(s) found - there is no rule#3 match
cediag: findings: 0 DIMMs with a failure pattern matching rule#4a
cediag: findings: 0 DIMMs with a failure pattern matching rule#4b
cediag: findings: 0 DIMMs with a failure pattern matching rule#5
cediag: findings: 0 DIMMs with a failure pattern matching rule#5
supplemental
(root)@scseast:~# echo $?
0

(root)@scseast:~# uname -a
SunOS scseast 5.8 Generic_117350-46 sun4u sparc SUNW,Ultra-4

(root)@scseast:~# /opt/csw/bin/puppet --version
0.24.7

(root)@scseast:~# /opt/csw/bin/facter
domain => example.net
facterversion => 1.5.4
fqdn => scseast.example.net
hardwareisa => sparc
hardwaremodel => sun4u
hostname => scseast
id => root
interfaces => lo0,hme0,qfe4
ipaddress => 192.168.1.5
kernel => SunOS
kernelrelease => 5.8
kernelversion => Generic_117350-46
macaddress => 8:0:20:b1:63:81
macaddress_hme0 => 8:0:20:b1:63:81
macaddress_qfe4 => 8:0:20:b1:63:81
netmask_hme0 => 255.255.255.240
netmask_lo0 => 255.0.0.0
netmask_qfe4 => 255.255.255.240
operatingsystem => Solaris
operatingsystemrelease => 5.8
ps => ps -ef
puppetversion => 0.24.7
rubysitedir => /opt/csw/lib/ruby/site_ruby/1.8
rubyversion => 1.8.7
sshdsakey =>
B3NzaC1kc3M+YG5wdFKCrAwmWVMmNKVMfuZFxmq1meshHo5yEsrnriNT6hSvGUrYJHD/cghH2E2/s3TaKOAoUQ6JFF0Dh0Z0V+zD+RPKqITIXfS80ihy1DVSf0xICbOoElPITnhNzjh5tS8BpoqDj0WGK9HU1uuTA==
sshrsakey =>
B3NzaC1yc2E7UH4m8TkeOYiR9nH3FlQ8QB8QCRpUUmRBlcS3YF8W233FdQhU=
timezone => GMT
uniqueid => 80b26481
uptime => 11 day
virtual => physical


-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Mac Domainname and facter

[engle]

So, when I issue the command:

ipconfig getpacket en0

I get the proper domain name from DHCP. But, 'facter', does not
display this when reporting the 'domain' or in the FQDN . Both of
these list "local" for the domain name of the computer. In addition,
in my 'resolv.conf', the correct domain name is listed as a 'search'
domain as well as a general domain statement.

So, I am still a bit unsure as to where facter is getting its
infomation.

-kurt



On Sep 18, 11:33 am, Nigel Kersten  wrote:
> On Fri, Sep 18, 2009 at 11:16 AM, Allan Marcus  wrote:
>
> > /Library/Ruby/Site/1.8/facter/domain.rb
>
> > I think for the Mac you need to set the search domain in the Network
> > System Pref, and that is what facter uses, but I'm not sure I'm
> > reading the code right.
>
> No, if you're using DHCP it should fall to resolv.conf which is
> automatically generated by data provided by DHCP to the interface for
> the SystemConfiguration framework.
>
> It'll try dnsdomainname first, which will fail, thendomainname, which
> will be empty unless you're attached to NIS, then resolv.conf
>
> It will pick any domain entry, if that doesn't exist, then fall back
> to search domains.
>
> You should be getting exactly the same results as you see when dumping
> a DHCP response with
>
> ipconfig getpacket en1 (en0 or whatever)
>
> OS X clients have ComputerName and LocalHostName in
> SystemConfiguration as well, which are what are set via the Sharing
> prefpane. These are independent of actual domain names, but the fact
> that terminal prompts fall back to them in some situations often
> confuses people.
>
> scutil --get ComputerName
> scutil --get LocalHostName
>
>
>
>
>
> > ---
> > Thanks,
>
> > Allan Marcus
> > 505-667-5666
>
> > On Sep 18, 2009, at 10:11 AM, engle wrote:
>
> >> We have a large number of Macs that are using puppet to install
> >> packages. The source of the packages is determined by the domain name
> >> of the client. We are using ISC's dhcpd. The macs seem to pick up the
> >> correct domain name from the dhcp server but facter is not picking it
> >> up. If I type "domainname" at a shell prompt, I get nothing. However,
> >> when the client requests a cert from the puppet server, it is
> >> requested with the FQDN which is correct.
>
> >> So, where does facter get its domain name information from on the
> >> client. I know that Macs have a number of places where they store and
> >> use hostname anddomainname. Which one does facter use?
>
> >> Thanks,
>
> >> -kurt
>
> --
> Nigel Kersten
> nig...@google.com
> System Administrator
> Google Inc.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Monitoring the puppetmaster

[Pete Emerson]

We've got over 150 hosts hitting the one puppetmaster, and based on
what I've seen via searching it seems like we're hitting into
scalability issues with Webrick, and the recommendation is to switch
to Mongrel or Passenger. Looks to me like Passenger is where the focus
is, so I'm working on migrating to 0.25 and Passenger, with multiple
master nodes for redundancy and scalability.

Pete

On Tue, Sep 22, 2009 at 12:41 PM, Clint Savage  wrote:
>
> On Tue, Sep 22, 2009 at 1:38 PM, Pete Emerson  wrote:
>>
>> I'm using 0.24 with Webrick (in the process of migrating to 0.25 / 
>> passenger).
>>
>> Occasionally, the puppetmasterd becomes unavailable, and we see error
>> messages along the lines of:
>>
>> Could not call puppetmaster.getconfig: #> reset by peer>
>>
>> I believe the puppetmasterd does not completely die, so it is still in
>> the process list.
>>
>> I'm wondering what a good way to monitor this would be.
>>
>> I see that I can telnet into port 8140, is there something simple I
>> can send that would give me an indication that everything is okay or
>> not?
>>
>> Any suggestions on monitoring this would be appreciated.
>>
>> Pete
>
> Strangely enough, we had a similar situation here.  Whenever Puppet
> (the client) would reload its own configs, it would die and not start
> again.  So we wrote a nice little nagios script that monitored whether
> puppet was running on each machine.  From that, we could restart or
> send an email or anything we want really.
>
> Cheers,
>
> Clint
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Just checking: newest Facter on box with ancient Puppet

[James Turnbull]

2009/9/23 David Sowder :
>
> I just wanted to double-check with those in the know since "just trying
> it" could miss something small but significant:
>
> Is it generally accepted that while Puppet may require version X of
> Facter, Puppet accepts say version X+3 of Facter?  I'm wondering if I
> can potentially upgrade Facter to the lastest (1.5.6 or 1.5.7) on my
> boxes running Puppet 0.22.4 well before Puppet is upgraded to 0.24.8 or
> 0.25.

Shouldn't be an issue there I wouldn't think.

Regards

James Turnbull

-- 
Author of:
* Pro Linux Systems Administration (http://tinyurl.com/linuxadmin)
* Pulling Strings with Puppet (http://tinyurl.com/pupbook)
* Pro Nagios 2.0 (http://tinyurl.com/pronagios)
* Hardening Linux (http://tinyurl.com/hardeninglinux)

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Ruby on HP-UX B.11.11 (11iv1)

[Andy Bell]

Hi Mark

With regard to ruby there is a way to compile ruby up on HPUX 11.11
and i'll see if i can dig up the information for you (its a
interesting compile if i remember correctly)

Have you considered using cfengine as that works well on HPUX (all
versions).

Andy



--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: SLES 10 Install trouble

[Andy Bell]

Hi

Ive got puppet running on SLES10 SP2 X86_64 must admit though i
installed ruby/puppet from the tarball.

Andy

On Sep 19, 11:27 am, Silviu Paragina  wrote:
>  From what I understand you compiled ruby from source.
>
> Package dependencies only see other packages, as opposed to what is
> actually on the system, so the rpm package for puppet does not see a
> ruby source installation, and that is how packages work.
>
> If you need packages that depend on ruby you should install ruby as a
> package or get the source package for ruby, modify it for your needs and
> build your own ruby package.
>
> Silviu
>
> Hariharan Gopalan wrote:
> > I am having a hard time installing puppet on an SLES 10 system. I
> > managed to install ruby, but the x86_64 rpm of puppet from opensuse
> > repository does not recognize the ruby installation from source.
>
> > Was wondering if any one has puppet running on x86_64 SLES10
>
> > Thanks
> > Hari

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Puppet Camp Schedule Posted

[Dave]

Yes - any view of the presentations would be much appreciated!

Thanks in advance,

Dave

On Sep 21, 10:14 pm, Marc Fournier 
wrote:
> > (I'm working angles to see if we can get presentations
> > streamed/recorded.
>
> +1 for this idea :-)

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Puppet Camp Schedule Posted

[geoffrey papilion]

I'm in San Francisco, but I wasn't really planning on going to this. I
have a Cannon XH A1(good HD camera with XLR inputs), and I'd be
willing to help with the video portion, but I need to see if I can be
down at SFSU for those days(I'm 90% sure I can).

//geoff


On Tue, Sep 22, 2009 at 6:06 AM, Julian Simpson  wrote:
>
> Doesn't have to be high quality video - a Flip cam recording would do
> it.  I'll even lend Paul Nasrat mine ...
>
> J.
>
> 2009/9/22 Peter Burkholder :
>>
>>>
>>> Peter Meier a écrit :
>>> >>> (I'm working angles to see if we can get presentations
>>> >>> streamed/recorded.
>>> >>>
>>> >> +1 for this idea :-)
>>> >>
>>> >
>>> > I'd like to second that. Would be nice!
>>> >
>>> > cheers pete
>>> >
>>> >
>>> o yes , would love that too. Will even pay a few $$ to view it
>>> if if
>>> this help to fund the cost of the recording.
>>
>> Ditto that.
>>>
>>>
>>> regards,
>>> Ghislain.
>>>
>>
>> --
>> Peter Burkholder
>> AARP | Web Strategy & Operations | 601 E Street, NW | Washington, DC
>> 20049
>>  pburkhol...@aarp.org | aim: peterbtech | ph: 202-434-3530 | cell:
>> 202-344-7129 |
>>
>>
>>
>>
>> >
>>
>
>
>
> --
> Julian Simpson
> Software Build and Deployment
> http://www.build-doctor.com
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Monitoring the puppetmaster

[Clint Savage]

On Tue, Sep 22, 2009 at 1:38 PM, Pete Emerson  wrote:
>
> I'm using 0.24 with Webrick (in the process of migrating to 0.25 / passenger).
>
> Occasionally, the puppetmasterd becomes unavailable, and we see error
> messages along the lines of:
>
> Could not call puppetmaster.getconfig: # reset by peer>
>
> I believe the puppetmasterd does not completely die, so it is still in
> the process list.
>
> I'm wondering what a good way to monitor this would be.
>
> I see that I can telnet into port 8140, is there something simple I
> can send that would give me an indication that everything is okay or
> not?
>
> Any suggestions on monitoring this would be appreciated.
>
> Pete

Strangely enough, we had a similar situation here.  Whenever Puppet
(the client) would reload its own configs, it would die and not start
again.  So we wrote a nice little nagios script that monitored whether
puppet was running on each machine.  From that, we could restart or
send an email or anything we want really.

Cheers,

Clint

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Ruby on HP-UX B.11.11 (11iv1)

[Andy Bell]

Hi Mark

With regard to ruby there is a way to compile ruby up on HPUX 11.11
and i'll see if i can dig up the information for you (its a
interesting compile if i remember correctly)

Have you considered using cfengine as that works well on HPUX (all
versions).

Andy


On Sep 21, 8:01 pm, Mark Nelson  wrote:
> Hello
>
> I am hoping to deploy Puppet 0.25.0  within our Unix infrastructure.  
> One of our systems runs on HP-UX B.11.11 (HP-UX 11iv1), I am having
> trouble getting ruby to run on this platform.  The version of ruby that
> is available on the HP-UX Software Archive (http://hpux.connect.org.uk/)
> is 1.8.4, however puppet generates an error when it starts up.
>
>  I have attempted to build 1.8.7 from source, ruby compiles
> successfully.  Puppet generates an SSL error when trying to start,
> unfortunately I am sending this mail from home and don't have a copy of
> the error messages.
>
> Had anyone successfully deployed puppet,  either 0.25.0 or any other
> version on HP-UX B.11.11.  If so where did you get your ruby binary from.
>
> Any help greatfuly received.
>
> Mark.
>
> --
> ---
> Mark Nelson - m...@tardis.cx
> This mail is for the addressee only

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Puppet Camp Schedule Posted

[GinSkipper]

I would appreciate a copy of the slides when they are available.

Cheers

On Sep 21, 10:14 pm, Marc Fournier 
wrote:
> > (I'm working angles to see if we can get presentations
> > streamed/recorded.
>
> +1 for this idea :-)

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: copying file from multiple sources

[Luke Schierer]

On Sat, Sep 19, 2009 at 7:53 AM, Luke Schierer wrote:

> On Sep 19, 2009, at 05:11 EDT, Peter Meier wrote:
>
>>  The standard way to do that is:
 source =>
 ["puppet:///foo/file-$hostname","puppet:///foo/file-$lsbdistcodename
 ","puppet:///foo/file"]
 - check for modules/foo/file-www4, then file-jaunty, then file

 * sourceselect:
>>
>> Whether to copy all valid sources, or just the first one. This parameter
>> is only used in recursive copies; by default, the first valid source is
>> the only one used as a recursive source, but if this parameter is set to
>> all, then all valid sources will have all of their contents copied to
>> the local host, and for sources that have the same file, the source
>> earlier in the list will be used. Valid values are first, all.
>>
>> So you can have both variants.
>>
>> cheers pete
>>
> When I tried to do this with
source => [ 'puppet://host1/files/target','puppet://host2/files/target']
it works fine for the first host, which acts as the puppetmaster, but not
for the second one.  It complains about an unknown CA.

I realize that this is because the CA certificates differ on the two hosts,
and the certificate puppet is using to pull files is only signed by one of
the two, the one it gets its configuration from.

Is there a key or keys I can distribute to each node so that I can pull
files from all of them?

Thanks!

Luke

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Monitoring the puppetmaster

[Pete Emerson]

Ah. I grabbed puppetlast from

http://reductivelabs.com/trac/puppet/attachment/ticket/1188/puppetlast

It doesn't work with 0.24.7-4:

# ./puppetlast
puppetlast
error: undefined method `version' for #

However, it's pretty clear (even to my untrained ruby eyes) what this
script does, so it looks like what I can do is simply check the last
modified time of the last yaml file like this:

stat `ls -tr /var/lib/puppet/yaml/facts/*.yaml | tail -n1`

and then check to make sure that's within reasonable limits.

Pete

On Tue, Sep 22, 2009 at 12:55 PM, Pete Emerson  wrote:
> Sounds promising. Did puppetlast appear after 0.24.7-4? I don't see it
> on my box.
>
> [r...@admin]# rpm -qa | grep ^puppet
> puppet-server-0.24.7-4.el5
> puppet-0.24.7-4.el5
> [r...@admin]# rpm -ql puppet puppet-server | grep puppetlast
> [r...@admin]# find /usr -name "puppetlast"
> [r...@admin]#
>
> Pete
>
> On Tue, Sep 22, 2009 at 12:45 PM, Jeff Adams  wrote:
>>
>> We had this issue while we were using webrick and ended up with the
>> following in cron running every 15 minutes:
>>
>> if [ `/usr/bin/puppetlast |grep -v puppetlast |sort -n -k 4 |head -n
>> 1|awk '{print \$4}'` -ge 15 ]; then /etc/init.d/puppetmaster restart ;fi
>>
>> - Jeff
>>
>> On 09/22/2009 02:38 PM, Pete Emerson wrote:
>>>
>>> I'm using 0.24 with Webrick (in the process of migrating to 0.25 / 
>>> passenger).
>>>
>>> Occasionally, the puppetmasterd becomes unavailable, and we see error
>>> messages along the lines of:
>>>
>>> Could not call puppetmaster.getconfig: #>> reset by peer>
>>>
>>> I believe the puppetmasterd does not completely die, so it is still in
>>> the process list.
>>>
>>> I'm wondering what a good way to monitor this would be.
>>>
>>> I see that I can telnet into port 8140, is there something simple I
>>> can send that would give me an indication that everything is okay or
>>> not?
>>>
>>> Any suggestions on monitoring this would be appreciated.
>>>
>>> Pete
>>>
>>> >
>>
>> >>
>>
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Monitoring the puppetmaster

[Pete Emerson]

Sounds promising. Did puppetlast appear after 0.24.7-4? I don't see it
on my box.

[r...@admin]# rpm -qa | grep ^puppet
puppet-server-0.24.7-4.el5
puppet-0.24.7-4.el5
[r...@admin]# rpm -ql puppet puppet-server | grep puppetlast
[r...@admin]# find /usr -name "puppetlast"
[r...@admin]#

Pete

On Tue, Sep 22, 2009 at 12:45 PM, Jeff Adams  wrote:
>
> We had this issue while we were using webrick and ended up with the
> following in cron running every 15 minutes:
>
> if [ `/usr/bin/puppetlast |grep -v puppetlast |sort -n -k 4 |head -n
> 1|awk '{print \$4}'` -ge 15 ]; then /etc/init.d/puppetmaster restart ;fi
>
> - Jeff
>
> On 09/22/2009 02:38 PM, Pete Emerson wrote:
>>
>> I'm using 0.24 with Webrick (in the process of migrating to 0.25 / 
>> passenger).
>>
>> Occasionally, the puppetmasterd becomes unavailable, and we see error
>> messages along the lines of:
>>
>> Could not call puppetmaster.getconfig: #> reset by peer>
>>
>> I believe the puppetmasterd does not completely die, so it is still in
>> the process list.
>>
>> I'm wondering what a good way to monitor this would be.
>>
>> I see that I can telnet into port 8140, is there something simple I
>> can send that would give me an indication that everything is okay or
>> not?
>>
>> Any suggestions on monitoring this would be appreciated.
>>
>> Pete
>>
>> >
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Monitoring the puppetmaster

[Jeff Adams]

We had this issue while we were using webrick and ended up with the 
following in cron running every 15 minutes:

if [ `/usr/bin/puppetlast |grep -v puppetlast |sort -n -k 4 |head -n 
1|awk '{print \$4}'` -ge 15 ]; then /etc/init.d/puppetmaster restart ;fi

- Jeff

On 09/22/2009 02:38 PM, Pete Emerson wrote:
>
> I'm using 0.24 with Webrick (in the process of migrating to 0.25 / passenger).
>
> Occasionally, the puppetmasterd becomes unavailable, and we see error
> messages along the lines of:
>
> Could not call puppetmaster.getconfig: # reset by peer>
>
> I believe the puppetmasterd does not completely die, so it is still in
> the process list.
>
> I'm wondering what a good way to monitor this would be.
>
> I see that I can telnet into port 8140, is there something simple I
> can send that would give me an indication that everything is okay or
> not?
>
> Any suggestions on monitoring this would be appreciated.
>
> Pete
>
> >

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Monitoring the puppetmaster

[Pete Emerson]

I'm using 0.24 with Webrick (in the process of migrating to 0.25 / passenger).

Occasionally, the puppetmasterd becomes unavailable, and we see error
messages along the lines of:

Could not call puppetmaster.getconfig: #

I believe the puppetmasterd does not completely die, so it is still in
the process list.

I'm wondering what a good way to monitor this would be.

I see that I can telnet into port 8140, is there something simple I
can send that would give me an indication that everything is okay or
not?

Any suggestions on monitoring this would be appreciated.

Pete

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: puppetd --server and server option in puppetd.conf

[David Sowder]

I realized after sending the bit about there being a bug filed that I 
should have checked myself.

As for the RPM, perhaps I'm a little spoiled from the Debian world 
(though not all packages are of equal upgrade automation) and this is 
not the paradigm used by most RPM authors, but I'm used to the upgrading 
of a package taking various steps to smooth the upgrade for me.

R.I.Pienaar wrote:
> hello,
>
>
> - "Neil Prockter"  wrote:
>
>   
>> I have always had /etc/puppet/puppetd.conf managed by puppet so I let
>> puppet delete it.
>>
>> I agree the RPM has /etc/puppet/puppetd.conf in it and it should not
>> (I've only check the 0.24.8 from EPEL that I use)
>> 
>
>
> Take another look, it does not create this file if you're just adding a new 
> package on a clean machine:
>
> %ghost %config(noreplace,missingok) %{_sysconfdir}/puppet/puppetd.conf
>
> From the RPM docs:
>
> " As we mentioned in the Section called The %files List, if a file is 
> specified in the %files list, that file will automatically be included in the 
> package. There are times when a file should be owned by the package but not 
> installed - log files and state files are good examples of cases you might 
> desire this to happen.
>
> The way to achieve this, is to use the %ghost directive. By adding this 
> directive to the line containing a file, RPM will know about the ghosted 
> file, but will not add it to the package. However it still needs to be in the 
> buildroot."
>
> but if you had a package prior to this behavior and you upgrade it wont 
> delete your old {puppetd,puppetmasterd}.conf files, however the bug - that's 
> fixed already in 0.25 - caused that to be a problem, its a common FAQ one 
> that would have been solved in about a minute on the IRC channel.
>
> Problem some kind of release not on the RPM should mention this, but as this 
> is a known bug and a very simple search for "puppetd.conf" on 
> projects.reductivelabs.com would have found the issue I dont know why this is 
> such a big issue.
>
>   


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Just checking: newest Facter on box with ancient Puppet

[David Sowder]

I just wanted to double-check with those in the know since "just trying 
it" could miss something small but significant:

Is it generally accepted that while Puppet may require version X of 
Facter, Puppet accepts say version X+3 of Facter?  I'm wondering if I 
can potentially upgrade Facter to the lastest (1.5.6 or 1.5.7) on my 
boxes running Puppet 0.22.4 well before Puppet is upgraded to 0.24.8 or 
0.25.

-- 
David R. Sowder, Linux Systems Admin (Software Systems Specialist II)
Office of Information Technology, University of Texas at Arlington
   Work: 817-272-1081  dav...@uta.eduhttp://www.uta.edu/
   dav...@talk.uta.edu (Jabber)
Personal:   da...@sowder.com  http://david.sowder.com/

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: puppetd --server and server option in puppetd.conf

[Todd Zullinger]

Neil Prockter wrote:
> I have always had /etc/puppet/puppetd.conf managed by puppet so I
> let puppet delete it.
>
> I agree the RPM has /etc/puppet/puppetd.conf in it and it should not
> (I've only check the 0.24.8 from EPEL that I use)

The EPEL package only provides default permissions and let's rpm know
that it is a config file.  It does not install it or provide any
content for it, the file is marked as %ghost in the spec file).  I've
not looked closely at whether we can or should remove that entirely at
this point, but it shouldn't hurt anything as is.

-- 
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
Duct tape is like the Force. It has a light side, a dark side, and it
holds the universe together
-- Carl Zwanzig



pgpSJSZYgFvin.pgp
Description: PGP signature

[Puppet Users] Re: puppetd --server and server option in puppetd.conf

[R.I.Pienaar]

hello,


- "Neil Prockter"  wrote:

> I have always had /etc/puppet/puppetd.conf managed by puppet so I let
> puppet delete it.
> 
> I agree the RPM has /etc/puppet/puppetd.conf in it and it should not
> (I've only check the 0.24.8 from EPEL that I use)


Take another look, it does not create this file if you're just adding a new 
package on a clean machine:

%ghost %config(noreplace,missingok) %{_sysconfdir}/puppet/puppetd.conf

>From the RPM docs:

" As we mentioned in the Section called The %files List, if a file is specified 
in the %files list, that file will automatically be included in the package. 
There are times when a file should be owned by the package but not installed - 
log files and state files are good examples of cases you might desire this to 
happen.

The way to achieve this, is to use the %ghost directive. By adding this 
directive to the line containing a file, RPM will know about the ghosted file, 
but will not add it to the package. However it still needs to be in the 
buildroot."

but if you had a package prior to this behavior and you upgrade it wont delete 
your old {puppetd,puppetmasterd}.conf files, however the bug - that's fixed 
already in 0.25 - caused that to be a problem, its a common FAQ one that would 
have been solved in about a minute on the IRC channel.

Problem some kind of release not on the RPM should mention this, but as this is 
a known bug and a very simple search for "puppetd.conf" on 
projects.reductivelabs.com would have found the issue I dont know why this is 
such a big issue.

-- 
R.I.Pienaar

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: puppetd --server and server option in puppetd.conf

[Neil Prockter]

I have always had /etc/puppet/puppetd.conf managed by puppet so I let
puppet delete it.

I agree the RPM has /etc/puppet/puppetd.conf in it and it should not
(I've only check the 0.24.8 from EPEL that I use)

David Sowder wrote:
> Is there a bug filed for this ignored command-line argument issue?  Is
> it no longer an issue on 0.25?
> 
> I've done further testing based on your message and it appears that if
> puppetd.conf exists, even if its contents are identical to those of the
> puppet.conf file placed there by the RPM, the command-line arguments are
> ignored.  Perhaps the RPM should migrate old puppetd.conf files to
> puppet.conf or at the least move it out of the way.  (I'll probably mod
> my RPM to move it out of the way since there are no local changes in our
> puppetd.conf files nor do we currently think any are needed to the RPM
> provided puppet.conf file.)
> 
> Tools designed to make a system administrator's life easier shouldn't
> cause such confusion... :)
> 
> Neil Prockter wrote:
>> puppetd.conf is no more, use puppet.conf
>>
>> Many people have had the same confusing situation with --noop being
>> similarly ignored.
>>
>> Neil
>> David Sowder wrote:
>>  
>>> I'm in the process of upgrading a bunch of our Puppet clients from
>>> 0.22.4 to 0.24.8 after recently upgrading our puppetmaster similarly.
>>>
>>> I've run into a problem that seems like it'd be so likely seen by
>>> someone else that if the problem isn't local, I'd be somewhat
>>> surprised, yet at the same time, my install is simply a locally
>>> compiled copy of a source RPM from Fedora's EPEL project IIRC (from
>>> the .spec file changelog: "Mon Mar 23 2009 Todd Zullinger
>>>  - 0.24.8-1.1").
>>>
>>> The client is a RHEL 5 x86_64 box and the issue seems to boil down to
>>> "--server puppet.uta.edu" not working as a command-line argument to
>>> /usr/sbin/puppetd (with no complaint about an unknown argument like
>>> it does with "--Server puppet.uta.edu") but working fine if I specify
>>> a "server = puppet.uta.edu" line in my /etc/puppet/puppetd.conf
>>> file.  It looks like there is some sort of systematic problem since
>>> both "--genconfig" and "--configprint all" don't seem to have any
>>> effect.
>>>
>>> An example of "--server" failing to recognized:
>>>
>>> # /usr/sbin/puppetd --server puppet.uta.edu --test
>>> warning: Certificate validation failed; consider using the certname
>>> configuration option
>>> err: Could not retrieve catalog: Certificates were not trusted:
>>> hostname not match with the server certificate (hostname: puppet 
>>> CNs: puppet.uta.edu, )
>>> warning: Not using cache on failed catalog
>>> #
>>>
>>> (The stuff in parenthesis at the end was a local hack I made to
>>> /usr/lib/ruby/1.8/openssl/ssl.rb when trying to track down the issue.)
>>>
>>> "/usr/sbin/puppetd --test --configprint all" gives the same output as
>>> above.
>>>
>>> Any ideas on what I may have screwed up that causes these
>>> command-line options to be ignored?  "--test" is not ignored, so it
>>> might have something to do with how the options are defined.
>>>
>>> 
>>
>>   
> 


Please access the attached hyperlink for an important electronic communications 
disclaimer: http://www.lse.ac.uk/collections/secretariat/legal/disclaimer.htm

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: puppetd --server and server option in puppetd.conf

[R.I.Pienaar]

hello,


- "David Sowder"  wrote:

> Is there a bug filed for this ignored command-line argument issue?  Is
> it no longer an issue on 0.25?

http://projects.reductivelabs.com/issues/2176


-- 
R.I.Pienaar

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: puppetd --server and server option in puppetd.conf

[David Sowder]

Oh, and I forgot to mention, it appears that unfortunately --config is 
also one of the ignored arguments.

David Sowder wrote:
> Is there a bug filed for this ignored command-line argument issue?  Is 
> it no longer an issue on 0.25?
>
> I've done further testing based on your message and it appears that if 
> puppetd.conf exists, even if its contents are identical to those of 
> the puppet.conf file placed there by the RPM, the command-line 
> arguments are ignored.  Perhaps the RPM should migrate old 
> puppetd.conf files to puppet.conf or at the least move it out of the 
> way.  (I'll probably mod my RPM to move it out of the way since there 
> are no local changes in our puppetd.conf files nor do we currently 
> think any are needed to the RPM provided puppet.conf file.)
>
> Tools designed to make a system administrator's life easier shouldn't 
> cause such confusion... :)
>
> Neil Prockter wrote:
>> puppetd.conf is no more, use puppet.conf
>>
>> Many people have had the same confusing situation with --noop being
>> similarly ignored.
>>
>> Neil
>> David Sowder wrote:
>>  
>>> I'm in the process of upgrading a bunch of our Puppet clients from 
>>> 0.22.4 to 0.24.8 after recently upgrading our puppetmaster similarly.
>>>
>>> I've run into a problem that seems like it'd be so likely seen by 
>>> someone else that if the problem isn't local, I'd be somewhat 
>>> surprised, yet at the same time, my install is simply a locally 
>>> compiled copy of a source RPM from Fedora's EPEL project IIRC (from 
>>> the .spec file changelog: "Mon Mar 23 2009 Todd Zullinger 
>>>  - 0.24.8-1.1").
>>>
>>> The client is a RHEL 5 x86_64 box and the issue seems to boil down 
>>> to "--server puppet.uta.edu" not working as a command-line argument 
>>> to /usr/sbin/puppetd (with no complaint about an unknown argument 
>>> like it does with "--Server puppet.uta.edu") but working fine if I 
>>> specify a "server = puppet.uta.edu" line in my 
>>> /etc/puppet/puppetd.conf file.  It looks like there is some sort of 
>>> systematic problem since both "--genconfig" and "--configprint all" 
>>> don't seem to have any effect.
>>>
>>> An example of "--server" failing to recognized:
>>>
>>> # /usr/sbin/puppetd --server puppet.uta.edu --test
>>> warning: Certificate validation failed; consider using the certname 
>>> configuration option
>>> err: Could not retrieve catalog: Certificates were not trusted: 
>>> hostname not match with the server certificate (hostname: puppet  
>>> CNs: puppet.uta.edu, )
>>> warning: Not using cache on failed catalog
>>> #
>>>
>>> (The stuff in parenthesis at the end was a local hack I made to 
>>> /usr/lib/ruby/1.8/openssl/ssl.rb when trying to track down the issue.)
>>>
>>> "/usr/sbin/puppetd --test --configprint all" gives the same output 
>>> as above.
>>>
>>> Any ideas on what I may have screwed up that causes these 
>>> command-line options to be ignored?  "--test" is not ignored, so it 
>>> might have something to do with how the options are defined.
>>>
>>> 
>>
>>   
>


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: puppetd --server and server option in puppetd.conf

[David Sowder]

Is there a bug filed for this ignored command-line argument issue?  Is 
it no longer an issue on 0.25?

I've done further testing based on your message and it appears that if 
puppetd.conf exists, even if its contents are identical to those of the 
puppet.conf file placed there by the RPM, the command-line arguments are 
ignored.  Perhaps the RPM should migrate old puppetd.conf files to 
puppet.conf or at the least move it out of the way.  (I'll probably mod 
my RPM to move it out of the way since there are no local changes in our 
puppetd.conf files nor do we currently think any are needed to the RPM 
provided puppet.conf file.)

Tools designed to make a system administrator's life easier shouldn't 
cause such confusion... :)

Neil Prockter wrote:
> puppetd.conf is no more, use puppet.conf
>
> Many people have had the same confusing situation with --noop being
> similarly ignored.
>
> Neil
> David Sowder wrote:
>   
>> I'm in the process of upgrading a bunch of our Puppet clients from 0.22.4 to 
>> 0.24.8 after recently upgrading our puppetmaster similarly.
>>
>> I've run into a problem that seems like it'd be so likely seen by someone 
>> else that if the problem isn't local, I'd be somewhat surprised, yet at the 
>> same time, my install is simply a locally compiled copy of a source RPM from 
>> Fedora's EPEL project IIRC (from the .spec file changelog: "Mon Mar 23 2009 
>> Todd Zullinger  - 0.24.8-1.1").
>>
>> The client is a RHEL 5 x86_64 box and the issue seems to boil down to 
>> "--server puppet.uta.edu" not working as a command-line argument to 
>> /usr/sbin/puppetd (with no complaint about an unknown argument like it does 
>> with "--Server puppet.uta.edu") but working fine if I specify a "server = 
>> puppet.uta.edu" line in my /etc/puppet/puppetd.conf file.  It looks like 
>> there is some sort of systematic problem since both "--genconfig" and 
>> "--configprint all" don't seem to have any effect.
>>
>> An example of "--server" failing to recognized:
>>
>> # /usr/sbin/puppetd --server puppet.uta.edu --test
>> warning: Certificate validation failed; consider using the certname 
>> configuration option
>> err: Could not retrieve catalog: Certificates were not trusted: hostname not 
>> match with the server certificate (hostname: puppet  CNs: puppet.uta.edu, )
>> warning: Not using cache on failed catalog
>> #
>>
>> (The stuff in parenthesis at the end was a local hack I made to 
>> /usr/lib/ruby/1.8/openssl/ssl.rb when trying to track down the issue.)
>>
>> "/usr/sbin/puppetd --test --configprint all" gives the same output as above.
>>
>> Any ideas on what I may have screwed up that causes these command-line 
>> options to be ignored?  "--test" is not ignored, so it might have something 
>> to do with how the options are defined.
>>
>> 
>
>   


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: [Puppet-dev] ANNOUNCE Puppet 0.25.1rc1 available

[Todd Zullinger]

James Turnbull wrote:
> Puppet 0.25.1 Release Candidate 1 is now available for testing.

Packages for Fedora 10/11/rawhide and EL 4/5 are available at:

http://tmz.fedorapeople.org/repo/puppet/

Please report any packaging or repository bugs to me and not to the
Puppet or Fedora bug trackers.  And be sure to report any
non-packaging bugs to the Puppet bug tracker. :)

-- 
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
It seems such a pity that Noah and his party did not miss the boat.
-- Mark Twain



pgpcX1ZebDnVM.pgp
Description: PGP signature

[Puppet Users] Re: Puppet Camp Schedule Posted

[Julian Simpson]

Doesn't have to be high quality video - a Flip cam recording would do
it.  I'll even lend Paul Nasrat mine ...

J.

2009/9/22 Peter Burkholder :
>
>>
>> Peter Meier a écrit :
>> >>> (I'm working angles to see if we can get presentations
>> >>> streamed/recorded.
>> >>>
>> >> +1 for this idea :-)
>> >>
>> >
>> > I'd like to second that. Would be nice!
>> >
>> > cheers pete
>> >
>> >
>> o yes , would love that too. Will even pay a few $$ to view it
>> if if
>> this help to fund the cost of the recording.
>
> Ditto that.
>>
>>
>> regards,
>> Ghislain.
>>
>
> --
> Peter Burkholder
> AARP | Web Strategy & Operations | 601 E Street, NW | Washington, DC
> 20049
>  pburkhol...@aarp.org | aim: peterbtech | ph: 202-434-3530 | cell:
> 202-344-7129 |
>
>
>
>
> >
>



-- 
Julian Simpson
Software Build and Deployment
http://www.build-doctor.com

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Puppet Camp Schedule Posted

[Peter Burkholder]

>
> Peter Meier a écrit :
> >>> (I'm working angles to see if we can get presentations
> >>> streamed/recorded.
> >>>
> >> +1 for this idea :-)
> >>
> >
> > I'd like to second that. Would be nice!
> >
> > cheers pete
> >
> >
> o yes , would love that too. Will even pay a few $$ to view it  
> if if
> this help to fund the cost of the recording.

Ditto that.
>
>
> regards,
> Ghislain.
>

--
Peter Burkholder
AARP | Web Strategy & Operations | 601 E Street, NW | Washington, DC  
20049
  pburkhol...@aarp.org | aim: peterbtech | ph: 202-434-3530 | cell:  
202-344-7129 |




--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Ruby on HP-UX B.11.11 (11iv1)

[Mark Plaksin]

Mark Nelson  writes:

> Had anyone successfully deployed puppet,  either 0.25.0 or any other 
> version on HP-UX B.11.11.  If so where did you get your ruby binary from.

Howdy:

We've been running Puppet no HP-UX 11.11 for a while.  We use Ruby from
thewrittenword.com.  The price is pretty amazing for .edus.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Announcement: Foreman 0.1-1 is out

[Matt]

Hi Ohad,

Great news with the upgrade! :-)

I'm hitting a problem when trying to run import of facts.  It seems to
work the first few times, but then I start getting this -

# rake puppet:import:hosts_and_facts RAILS_ENV=production --trace
(in /var/www/html/foreman)
** Invoke puppet:import:hosts_and_facts (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute puppet:import:hosts_and_facts
Importing from /var/lib/puppet/yaml/facts
Importing server-01
rake aborted!
comparison of ActiveSupport::TimeWithZone with String failed
/var/www/html/foreman/app/models/host.rb:177:in `<'
/var/www/html/foreman/app/models/host.rb:177:in `importFacts'
/var/www/html/foreman/app/models/host.rb:166:in `importHostAndFacts'
/var/www/html/foreman/lib/tasks/puppet.rake:34
/var/www/html/foreman/lib/tasks/puppet.rake:31:in `each'
/var/www/html/foreman/lib/tasks/puppet.rake:31
/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call'
/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute'
/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each'
/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute'
/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in
`invoke_with_call_chain'
/usr/lib/ruby/1.8/monitor.rb:238:in `synchronize'
/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in
`invoke_with_call_chain'
/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke'
/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task'
/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level'
/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each'
/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level'
/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in
`standard_exception_handling'
/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level'
/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run'
/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in
`standard_exception_handling'
/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run'
/usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31
/usr/bin/rake:19:in `load'
/usr/bin/rake:19


2009/9/21 Ohad Levy :
> Hello All,
>
> I'm happy to announce the next stable release of Foreman, main new features
> include:
>
> Integration of Puppet Reports, once enabled you would see a real time
> overview of all of yours hosts status.
> Improved support for multiple Puppet Masters (e.g. import facts and reports
> from remote serves over http)
> Simplified migration from existing external nodes setup, now its possible to
> import your existing classifier data into Foreman.
>
> For a complete change log, please visit:
> http://theforeman.org/projects/changelog/foreman
> For feature requests, bugs, wiki etc, visit: http://theforeman.org
>
> If you already have Foreman installed, make sure you go through
> http://theforeman.org/wiki/foreman/Upgrade_instructions.
>
> 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-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Puppet Camp Schedule Posted

[Geoff Newell]

Yes please from those over here in the UK.

2009/9/22 Jean Spirat 

>
> Peter Meier a écrit :
> >>> (I'm working angles to see if we can get presentations
> >>> streamed/recorded.
> >>>
> >> +1 for this idea :-)
> >>
> >
> > I'd like to second that. Would be nice!
> >
> > cheers pete
> >
> >
> o yes , would love that too. Will even pay a few $$ to view it if if
> this help to fund the cost of the recording.
>
> regards,
> Ghislain.
>
>
>
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: environments for several internal customers?

[philipp Hanselmann]

Meanwhile I found a solution ...

I just use environment names which can't be guessed ... like

On puppet.conf on the puppetmaster:
[math-34lkdfjop34j-dev]
modulepath = /etc/puppet/data/math/dev/modules
manifest = /etc/puppet/date/math/dev/manifests/init.pp
[math-34lkdfjop34j-prd]
modulepath = /etc/puppet/data/math/prd/modules
manifest = /etc/puppet/date/math/prd/manifests/init.pp
[infk-.289n3D0dg2-dev]
modulepath = /etc/puppet/data/inf/dev/modules
manifest = /etc/puppet/date/inf/dev/manifests/init.pp
[infk-.289n3D0dg2-prd]
modulepath = /etc/puppet/data/inf/dev/modules
manifest = /etc/puppet/date/inf/prd/manifests/init.pp


So the math department has it's own user math. With this, they have only 
access to /etc/puppet/data/math/
So they know their own environments, but they don't know the environment 
names of the other puppet users.
The puppet.conf on the puppet server is only readable by the 
puppetmaster deamon ...

It this suitable way?


Philipp




Macno schrieb:
> I do that in this way:
>
> On puppet.conf on the puppetmaster:
> ---
> [puppetmasterd]
> reports = store,rrdgraph,tagmail,log
> autosign = true
> environments = alpha,beta,gamma
> manifest = /no/file
>
> [beta]
> modulepath = /etc/puppet/data/beta/
> manifest = /etc/puppet/manifests/site-beta.pp
>
> [alpha]
> modulepath = /etc/puppet/data/alpha/
> manifest = /etc/puppet/manifests/site-alpha.pp
>
> [gamma]
> modulepath = /etc/puppet/data/gamma/
> manifest = /etc/puppet/manifests/site-gamma.pp
> ---
>
>  /etc/puppet/manifests/site-beta.pp has something like:
> import "project_beta" (a module, in  where you define your
> infrastructure, placed in /etc/puppet/data/beta/ )
>
> Permissions on /etc/puppet/data/beta/ are limited to the users/groups
> that can manage files for the beta environment.
>
>
> On puppet.conf on the client (for example of the beta environment):
> [main]
> vardir = /var/lib/puppet
> logdir = /var/log/puppet
> rundir = /var/run/puppet
> ssldir = $vardir/ssl
> environment = beta
>
> [puppetd]
> classfile = $vardir/classes.txt
> localconfig = $vardir/localconfig
> environments = beta
>
>
>
> You can define also testing / production environments for each
> department, with something like:
>
> On clients:
> [main]
> vardir = /var/lib/puppet
> logdir = /var/log/puppet
> rundir = /var/run/puppet
> ssldir = $vardir/ssl
> environment = betaprod
>
> [puppetd]
> classfile = $vardir/classes.txt
> localconfig = $vardir/localconfig
> environments = betatest,betaprod
>
> (normal puppetruns use beta-prod, with "puppetd -t --
> environment=betatest" you run on the test environment of beta).
>
> puppet.conf on the puppet master becomes something like:
> [puppetmasterd]
> reports = store,rrdgraph,tagmail,log
> autosign = true
> environments = alphatest,alphaprod,betatest,betaprod ...
> manifest = /no/file
>
>
> [betatest]
> modulepath = /etc/puppet/data/beta/test/
> manifest = /etc/puppet/manifests/site-beta.pp
>
> [betaprod]
> modulepath = /etc/puppet/data/beta/prod/
> manifest = /etc/puppet/manifests/site-beta.pp
>
>
> /etc/puppet/data/beta/test/ and /etc/puppet/data/beta/prod/ are both
> git clones that pull from something like  /etc/puppet/data/beta/
> gitrepo
>
> My2c
>
> Alessandro Franceschi
>
> On 7 Set, 10:24, philipp Hanselmann 
> wrote:
>   
>> We are planning to use a puppet server for several internal customers at
>> our school (ETHZ - Swiss Fedral Institute of Technology Zürich).
>>
>> One way could be to choose  a separate environment for each customer ...
>>
>> Each customer will get a normal user on the puppet server. With this he
>> can edit his files inside his own environment path ...
>>
>> But how can  we ensure that the customers are separated? It should NOT
>> be possible for customer X to choose a environment from customer Y.
>>
>> Is there a way to implement this?
>>
>> Philipp Hanselmann
>> 
> >
>
>   


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Puppet Camp Schedule Posted

[Jean Spirat]

Peter Meier a écrit :
>>> (I'm working angles to see if we can get presentations
>>> streamed/recorded.
>>>   
>> +1 for this idea :-)
>> 
>
> I'd like to second that. Would be nice!
>
> cheers pete
>
>   
o yes , would love that too. Will even pay a few $$ to view it if if 
this help to fund the cost of the recording.

regards,
Ghislain.




--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] ANNOUNCE Puppet 0.25.1rc1 available

[James Turnbull]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Puppet 0.25.1 Release Candidate 1 is now available for testing.

This is a maintenance release in the 0.25.x branch of release

The release candidate is available as a tarball at:

http://reductivelabs.com/downloads/puppet/puppet-0.25.1rc1.tgz

and a Ruby Gem at:

http://reductivelabs.com/downloads/gems/puppet-0.25.1rc1.gem

Please test the release and report feedback via the Redmine site:

http://projects.reductivelabs.com

Outstanding Issues
- --

We have one outstanding issue with fileserving we're trying to
reproduce and resolve.  Some users are seeing new lines appended to
files being served by Puppet.  This changes the checksum and
triggers related resources and filebuckets, etc.  If you're
experiencing this issue could you please contribute any information
or logs to http://projects.reductivelabs.com/issues/2615.

Release Notes
- -

* We've clarified that the new 'require' function only works for
0.25.x clients.  If the function is specified with 0.24.x or earlier
clients the class will be included but the inherent dependency will
not be created.  A warning message will be generated informing you
of this.

* Node regular expression matching rules have been clarified - see
http://reductivelabs.com/trac/puppet/wiki/LanguageTutorial#matching-nodes-with-regular-expressions.

* The Nagios serviceescalation type now supports the use of the
servicegroup_name attribute.

* The Puppet gem now installs all binaries to the 'bin' directory
because Gems lack support for both a 'bin' and 'sbin' directory.
Facter (version later than 1.5.1) is now also a dependency for the gem.

CHANGELOG
- -

* Bug #2617: Problem with certs upgrading puppetmaster to 0.25.0
* Bug #2664: regexp parse error
* Bug #1538: Yumrepo sets permissions wrongly on files in
/etc/yum.repos.d
* Bug #2508: misleading error about ActiveRecord versions
* Bug #2600: Master under mongrel wrong number of arguments (3
for 2)
* Bug #2601: fqdn_rand raises exception when passed a seed
* Bug #2605: Ruby 1.8.1 compatibility - #1963 fix uses method
not in 1.8.1
* Bug #2606: Gems can't handle binaries in the sbin directory
* Bug #2607: 0.25 gem does not have facter as a dependency
* Bug #2608: install.rb will not run on ruby 1.9.1 due to ftools
being deprecated
* Bug #2612: vim syntax highlighting of new regex language features
* Bug #2613: Autorequire fails when a directory's path has a
trailing /
* Bug #2615: Templates produce incorrect content
* Bug #2616: Locking error in tagmail
* Bug #2618: Spurious test falures when testing redhat service
providers on debian varients
* Bug #2619: Fresh 0.25.0 client cannot 'authenticate' to 0.25.0
puppetmaster.
* Bug #2620: Regex problem in puppetmaster auth.conf
* Bug #2621: possible JSon serialization issue (on
debian/lenny/amd64)
* Bug #2622: puppetdoc returns undefined method '[]'
* Bug #2626: Unhelpful error message
* Bug #2627: Node regular expressions only work in some cases
* Bug #2631: show_diff no longer works
* Bug #2632: require doesnt seem to work
* Bug #2634: nagios type serviceescalation should support
servicegroup_name
* Bug #2637: SSL socket race condition under webrick
* Bug #2638: inconsistent behaviour when more than one "node
/foo/ { }" stanza matches.
* Bug #2639: Fail to store reports in simple default config
* Bug #2640: runit service provider does not create symlinks
* Bug #2642: runit service provider doesn't have a restart command
* Bug #2648: macauthorization provider spuriously changes values
when not needed.
* Bug #2651: Directory permissions on man pages can be incorrect
* Bug #2652: syntax error in lib/puppet/util/selinux.rb
according to Fedora 11 ruby 1.8.6
* Bug #2654: Confusing error message when a provider lacks a feature
* Bug #2656: Puppet --parseonly tests hang forever
* Feature #2393: We should maintain a dynamically-built 'next'
branch

Regards

James Turnbull

- --
Author of:
* Pro Linux Systems Administration (http://tinyurl.com/linuxadmin)
* Pulling Strings with Puppet (http://tinyurl.com/pupbook)
* Pro Nagios 2.0 (http://tinyurl.com/pronagios)
* Hardening Linux (http://tinyurl.com/hardeninglinux)

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBSriPiCFa/lDkFHAyAQLKzggAxe/syQK8UsqVquwBtdwdJI/cntyMxhaK
f7hJY4iHn+OK+5dPpTIqPoJtNxYzsRSR7awHtxroZ7X61uwFCAEF7JgN3szyYlYN
krSsoJuc7WytVUOlzHZYriPrtNNopYnjMalAxjMJpkSegoKQniyTwm4v8KMeBBw7
uqb9UMbh+YAyYA7lHZQ0Ifaw0jywqhOZ3KiUwtwRtZio/sIN3indJgEA0JQcQblo
6+w7UTMpJeH3SWPGtvtlN+nEQZMCxonwKGxSmb95K67VGolaFKhO0actQUTAq7Oi
kYCrsRiPKoGuKkn3/Mx6B++uiGsPsujqJhjWIvyLJ7mIErw1o7M7BA==
=LUo0
-END PGP SIGNATURE-

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Group

[Puppet Users] regarding puppetrun

[lovewadhwa]

Hi all

I have been using puppetrun on puppet master server to replicate my
manifests on all client machines.But when i run puppetrun i receive
the following error:

puppetrun --host HOSTNAME

err: Could not call puppetrunner.run: #
Host "HOSTNAME" failed: HTTP-Error: 500 Internal Server Error
"HOSTNAME"  finished with exit code 2
Failed: "HOSTNAME"

I have checked my  namespaceauth conf file and have allowed the
required machines.Please help.Running the same command with debug
option also doesn't help much.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---

[Puppet Users] Re: Puppet Camp Schedule Posted

[Peter Meier]

>> (I'm working angles to see if we can get presentations
>> streamed/recorded.
>
> +1 for this idea :-)

I'd like to second that. Would be nice!

cheers pete

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---