[Puppet Users] Re: looking for puppet on redhat el 3

2009-04-01 Thread Vincent Louviaux
That's the problem with this package : # rpm -Uhv augeas-0.2.2-1.el3.rf.i386.rpm warning: augeas-0.2.2-1.el3.rf.i386.rpm: V3 DSA signature: NOKEY, key ID 6b8d79e6 error: Failed dependencies: augeas-libs = 0.2.2-1.el3.rf is needed by augeas-0.2.2-1.el3.rf Thanks for your help Vincent On

[Puppet Users] Re: force backup of config files

2009-04-01 Thread Martin Wheldon
Hi Luke, Would it not be preferable to be able to use a version control system of the implemeters choice. The reason being that some shops may have subversion skills already by not git skills etc... Best Regards Martin On Tue, Mar 31, 2009 at 5:48 PM, Luke Kanies wrote: > > On Mar 31, 2009, a

[Puppet Users] Re: Module for VirtualBox

2009-04-01 Thread paul matthews
That looks pretty good to me. I've been working on the same thing and your method looks a lot neater. The difficulty I've found, is the define statement for the vm itself which I've ended up separating as a separate module / class called vboxinstance. It's still being worked on so it's not worth a

[Puppet Users] Re: Installing 0.24.8 as gem on Debian

2009-04-01 Thread Eric Gerlach
Kyle, Ryan, I'd love it if those instructions made it into the Wiki. The uupdate thing would be hugely helpful to some other Debian administrators, I'm sure. Cheers, Eric On Fri, Mar 27, 2009 at 08:33:43AM -0500, Kyle Cordes wrote: > > Kyle Cordes wrote: > > >> Apply the .diff > > > Ryan

[Puppet Users] ERB docs...

2009-04-01 Thread Craig Dunn
Hi All, I'm struggling to find any decent documentation on ERB templating - theres some limited summaries on puppets' site but I need something a bit more in depth that covers things like arrays, for loops...etc Is there anything out there that might help? Cheers Craig --~--~-~--

[Puppet Users] Re: ERB docs...

2009-04-01 Thread Bjørn Dyre Dyresen
2009/4/1 Craig Dunn > > > > Hi All, > > I'm struggling to find any decent documentation on ERB templating - > theres some limited summaries on puppets' site but I need something a > bit more in depth that covers things like arrays, for loops...etc > > Is there anything out there that might help?

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-01 Thread Nigel Kersten
Keith, can you make sure you bug report this on bugs.debian.org ? A few of us have joined in to help the Debian Puppet packaging project, and we're going to start churning through the reported bugs next week. On Tue, Mar 31, 2009 at 11:37 PM, Keith Edmunds wrote: > > On Tue, 31 Mar 2009 14:35

[Puppet Users] Re: certificate signing error on debian

2009-04-01 Thread Scott Frazer
On Mar 31, 1:43 pm, Trevor Price wrote: > as it turns out the timzones were different.  However , now in > /var/log/syslog I get > Mar 31 18:39:56 debain_client_host puppetd[19020]: Calling puppetca.getcert > Mar 31 18:39:57 debian_client_host puppetd[19020]: Could not request > certificate: Cert

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-01 Thread Keith Edmunds
On Wed, 1 Apr 2009 06:35:04 -0700, nig...@google.com said: > Keith, can you make sure you bug report this on bugs.debian.org ? I don't see a bug. From /usr/share/doc/puppet/NEWS.Debian.gz: "Handling of the rundir setting has been changed; we now store PID files in /var/run/puppet, and the inits

[Puppet Users] Re: Installing 0.24.8 as gem on Debian

2009-04-01 Thread Nigel Kersten
I actually did this yesterday, and it's easier than that. $ mkdir ~/makepuppetdeb $ cd ~/makepuppetdeb $ dget http://ftp.de.debian.org/debian/pool/main/p/puppet/puppet_0.24.7-1.dsc $ wget http://reductivelabs.com/downloads/puppet/puppet.0.24.8.tgz (currently broken, but I imagine will be resolved

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-01 Thread Nigel Kersten
Ah. I misread the thread. Ta. On Wed, Apr 1, 2009 at 8:52 AM, Keith Edmunds wrote: > > On Wed, 1 Apr 2009 06:35:04 -0700, nig...@google.com said: > >> Keith, can you make sure you bug report this on bugs.debian.org ? > > I don't see a bug. From /usr/share/doc/puppet/NEWS.Debian.gz: > > "Handling

[Puppet Users] Puppet 0.24.8 tarball broken.

2009-04-01 Thread Nigel Kersten
http://reductivelabs.com/downloads/puppet/puppet.0.24.8.tgz 0 bytes. -- 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

[Puppet Users] Re: Installing 0.24.8 as gem on Debian

2009-04-01 Thread Nigel Kersten
On Wed, Apr 1, 2009 at 8:53 AM, Nigel Kersten wrote: > I actually did this yesterday, and it's easier than that. > > $ mkdir ~/makepuppetdeb > $ cd ~/makepuppetdeb > $ dget http://ftp.de.debian.org/debian/pool/main/p/puppet/puppet_0.24.7-1.dsc > $ wget http://reductivelabs.com/downloads/puppet/pu

[Puppet Users] Re: Installing 0.24.8 as gem on Debian

2009-04-01 Thread Ryan Steele
You're not properly setting your name in the control/changelog file this way. I'd like to put a mixture of both of our processes on the wiki - if I can't do so already, I'll bug jamtur to give me access. On Apr 1, 12:53 pm, Nigel Kersten wrote: > On Wed, Apr 1, 2009 at 8:53 AM, Nigel Kersten w

[Puppet Users] Re: looking for puppet on redhat el 3

2009-04-01 Thread David Lutterkort
On Wed, 2009-04-01 at 09:11 +0200, Vincent Louviaux wrote: > That's the problem with this package : > # rpm -Uhv augeas-0.2.2-1.el3.rf.i386.rpm > warning: augeas-0.2.2-1.el3.rf.i386.rpm: V3 DSA signature: NOKEY, key > ID 6b8d79e6 > error: Failed dependencies: > augeas-libs = 0.2.2-1.el3.rf

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-01 Thread Rob McBroom
On 2009-Apr-1, at 9:35 AM, Nigel Kersten wrote: > A few of us have joined in to help the Debian Puppet packaging > project, and we're going to start churning through the reported bugs > next week. Will this include getting it added to backports? Thanks. -- Rob McBroom

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-01 Thread Trevor
so this was a problem because 1. apt-get insatll puppet 2. apt-get install puppet- 3. apt-get install puppet/experimental so experimental installs /etc/init.d/puppet.dpkg-dist (/var/run/ puppet/puppet.pid) but non-experimental installs /etc/init.d/puppet(/var/run/ puppet.pid) so I didnt r

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-01 Thread Keith Edmunds
You haven't said which version of Debian you are running. If you are running Etch/oldstable/V4.0, you have a very old version of puppet in the standard repository. If you're running Lenny/stable/5.0, the version in the repository works fine. In neither case would I install from experimental, given

[Puppet Users] Re: Module for VirtualBox

2009-04-01 Thread Rolfs
paul matthews wrote: > define vboxvm::vboxinstance > (vboxif=$vboxif,vboxip=$vboxip,vboxname=$vboxname,vboxpath=$vboxpath,domain_name=$domain_name, > dnsserver1=$dnsserver1,gateway=$gateway,netmask=$netmask,macaddress=$macaddress, > memory=$memory, cpu_count=$cpu_count, ) { > > exec { "create-v

[Puppet Users] Re: Puppet 0.24.8 tarball broken.

2009-04-01 Thread James Turnbull
Nigel Kersten wrote: > http://reductivelabs.com/downloads/puppet/puppet.0.24.8.tgz > > 0 bytes. Maybe I am late to the party but the right URL is: http://reductivelabs.com/downloads/puppet/puppet-0.24.8.tgz Regards James Turnbull -- Author of: * Pro Linux Systems Administration (http://www.a

[Puppet Users] Re: Installing 0.24.8 as gem on Debian

2009-04-01 Thread James Turnbull
Ryan Steele wrote: > You're not properly setting your name in the control/changelog file > this way. I'd like to put a mixture of both of our processes on the > wiki - if I can't do so already, I'll bug jamtur to give me access. > Ryan You don't need to bug me. :) All you need to do is create

[Puppet Users] Re: certificate signing error on debian

2009-04-01 Thread James Turnbull
Scott Frazer wrote: > On Mar 31, 1:43 pm, Trevor Price wrote: >> as it turns out the timzones were different. However , now in >> /var/log/syslog I get >> Mar 31 18:39:56 debain_client_host puppetd[19020]: Calling puppetca.getcert >> Mar 31 18:39:57 debian_client_host puppetd[19020]: Could not re

[Puppet Users] Re: certificate signing error on debian

2009-04-01 Thread James Turnbull
Scott Frazer wrote: > I saw something similar when I tried to preseed the installation of > puppet using "d-i pkgsel/include string puppet" > > The preseed installation used different directory paths than the "apt- > get install puppet" installs I had done previously. When my > centralized puppet

Re: [Puppet-dev] Re: [Puppet Users] Puppet 0.24.8 tarball broken.

2009-04-01 Thread Nigel Kersten
On Wed, Apr 1, 2009 at 2:28 PM, James Turnbull wrote: > Nigel Kersten wrote: >> http://reductivelabs.com/downloads/puppet/puppet.0.24.8.tgz >> >> 0 bytes. > > Maybe I am late to the party but the right URL is: > > http://reductivelabs.com/downloads/puppet/puppet-0.24.8.tgz Sure. The other one le

Re: [Puppet-dev] Re: [Puppet Users] Puppet 0.24.8 tarball broken.

2009-04-01 Thread James Turnbull
Nigel Kersten wrote: > On Wed, Apr 1, 2009 at 2:28 PM, James Turnbull > wrote: >> Nigel Kersten wrote: >>> http://reductivelabs.com/downloads/puppet/puppet.0.24.8.tgz >>> >>> 0 bytes. >> Maybe I am late to the party but the right URL is: >> >> http://reductivelabs.com/downloads/puppet/puppet-0.24

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-01 Thread Russ Allbery
Rob McBroom writes: > On 2009-Apr-1, at 9:35 AM, Nigel Kersten wrote: >> A few of us have joined in to help the Debian Puppet packaging project, >> and we're going to start churning through the reported bugs next week. > Will this include getting it added to backports? Thanks. As long as you c

[Puppet Users] Re: /etc/init.d/puppet on debian

2009-04-01 Thread Russ Allbery
Nigel Kersten writes: > Keith, can you make sure you bug report this on bugs.debian.org ? > > A few of us have joined in to help the Debian Puppet packaging > project, and we're going to start churning through the reported bugs > next week. That's excellent news -- thank you very much for doing

[Puppet Users] Re: certificate signing error on debian

2009-04-01 Thread Scott Frazer
On Apr 1, 4:37 pm, James Turnbull wrote: > Scott Frazer wrote: > > I saw something similar when I tried to preseed the installation of > > puppet using "d-i pkgsel/include string puppet" > > > The preseed installation used different directory paths than the "apt- > > get install puppet" installs

[Puppet Users] Re: certificate signing error on debian

2009-04-01 Thread Mike Renfro
On 4/1/2009 5:26 PM, Scott Frazer wrote: > On Apr 1, 4:37 pm, James Turnbull wrote: >> Why would preseed do installation any differently? d-i pkgsel/include >> should use Debian standard package tool - in this case aptitude - to >> install. > > I'd love to know myself. All I know is that I spe

[Puppet Users] Puppet and pushing changes

2009-04-01 Thread Ohad Levy
Hi All, I've been trying to address the issue of when (once in a while) you need to push something to a client now, cant wait 30 minutes, or its a one time action. The first path I went though was though was to consider something like puppetrun, and as we don't run puppetd as a daemon (running it

[Puppet Users] Re: certificate signing error on debian

2009-04-01 Thread Trevor
as I understand it certname is a puppetmasterd change. Doing so would break the existing dozen centos clients that are working fine. The client side server=FQDN_of_puppet_master and the puppetmaster thinks its name is its FQDN now the puppet clients all have /etc/hosts entries for ip_of_pupp

[Puppet Users] Re: Puppet and pushing changes

2009-04-01 Thread Kyle Cordes
Ohad Levy wrote: > puppetrun, and as we don't run puppetd as a daemon (running it from cron > due to large memory consumption while idle), I went forward and Here is a semi-related thought. Without regard for memory consumption, but rather due to the notion that system-wide, manageable, canon

[Puppet Users] Re: Puppet and pushing changes

2009-04-01 Thread Jason Rojas
Ohad, I have been doing some thinking about this as well. I can definitely see situations where I need a "cap shell" type of approach to push a single change or something else, but usually those are for administration needs. Now feel free to correct me if I am wrong, but puppet's whole goal

[Puppet Users] Re: Puppet and pushing changes

2009-04-01 Thread Ohad Levy
On Thu, Apr 2, 2009 at 10:35 AM, Jason Rojas wrote: > > Ohad, I have been doing some thinking about this as well. I can > definitely see situations where I need a "cap shell" type of approach > to push a single change or something else, but usually those are for > administration needs. sure, this

[Puppet Users] Re: Puppet and pushing changes

2009-04-01 Thread chakkerz
Hello there This might not be a solution to your problem (from a philosophical stance anyway), but you could grant your user to run `puppetd -vt` without password via sudoers on all hosts. Then you could `ssh puppetd -vt` from your workstation (or write a wrapper that takes input from a list or

[Puppet Users] platform(in)dependent facts

2009-04-01 Thread chakkerz
Hello there I want (erm ... need) to write some facts to verify certain packages are installed. I don't think the packages type does the trick because i don't want to force the installation so much as lock down some things. But i don't see how to do this platform independent between solaris and r

[Puppet Users] Re: platform(in)dependent facts

2009-04-01 Thread chakkerz
Upon further consideration ... and this is probably demented ... i could deploy helper scripts which are platform specific and use bash, and name them uniformly and then call them from my facts... one obvious downside is that puppet will fail first run... chakkerz --~--~-~--~~

[Puppet Users] Re: platform(in)dependent facts

2009-04-01 Thread Ohad Levy
you probably want to use something like : confine :kernel => :linux cheers, Ohad On Thu, Apr 2, 2009 at 12:24 PM, chakkerz wrote: > > Upon further consideration ... and this is probably demented ... i > could deploy helper scripts which are platform specific and use bash, > and nam

[Puppet Users] Hoping to document a successful install, Leopard 10.5.6

2009-04-01 Thread Allister Banks
Hello all, After finally hunting down Nigel's presentation from MacWorld 08, I'm raring to get this working for the various businesses my consultancy supports. Unfortunately, I'm not having much success with any of the installation methods available, on PPC or Intel, Leopard 10.5.6. Macport

[Puppet Users] Default Schedule

2009-04-01 Thread Justin Lambert
I am trying to set a default schedule and not having a lot of luck. It doesn't look like they are used a whole lot and I've had a hard time finding documentation. What I would ultimately like is for the default schedule to be daily from "17:00 - 03:00." I'm not sure if it'll work past midnigh

[Puppet Users] Re: ERB docs...

2009-04-01 Thread Burkholder, Peter
http://www.ruby-doc.org/docs/ProgrammingRuby/html/web.html > -Original Message- > From: puppet-users@googlegroups.com > [mailto:puppet-us...@googlegroups.com] On Behalf Of Craig Dunn > Sent: Wednesday, April 01, 2009 9:11 AM > To: puppet-users@googlegroups.com > Subject: [Puppet Users]

[Puppet Users] debugging puppetrun + HTTP 503 error

2009-04-01 Thread chris
Puppet's been super for our installation of ~800 hosts, but I'm trying to figure out why puppetrun isn't working for our us. Nodes work fine as clients, but when I try to use puppetrun, everything looks fine on the client side: puppetd -d -v --no-daemonize gives: ... notice: Finished catalog ru

[Puppet Users] Re: debugging puppetrun + HTTP 503 error

2009-04-01 Thread Jason Rojas
I think I get this as well when I use puppetrun. Are you by change using passenger at all? -Jason On Apr 1, 2009, at 12:03 PM, chris wrote: > > > Puppet's been super for our installation of ~800 hosts, but I'm trying > to figure out why puppetrun isn't working for our us. Nodes work fine > as

[Puppet Users] apache2 template

2009-04-01 Thread ³ª»Û °ÍÀº µèÁöµµ ¸»°í º¸Áöµµ ¸»°í , ¸»ÇÏÁöµµ ¸»¶ó
anyone have an apache2 virtualhosts template they like and would like to share? For example I would like to provision quickly website1.com website2.com website3.com and have the docroots be in /home/vhosts/website1.com/htdocs/ /home/vhosts/website2.com/htdocs/ /home/vhosts/website3.com/htdocs/