-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Puppet 0.25.1 - code name "zoot" - is now available. The 0.25.1 release
is a maintenance release in the 0.25.x branch.
The release is available at:
http://reductivelabs.com/downloads/puppet/puppet-0.25.1.tar.gz
http://reductivelabs.com/downloads/ge
Hi
> Hi Peter, perhaps you started writing your response before reading
> my entire message. I suggested a possible solution - behavior
> similar to the 'onlyif' option of the exec Type. Look at the docs,
> exec only runs the command on the client if the 'onlyif' command,
> which also r
> I don't want to get deeply into the middle of this (and so will
> leave my contribution to just this e-mail), but there is
> a small point I want to make, that I think Peter touched on, but may
> not have gotten across.
>
> Puppet manifests are declarative, not executable.
>
> The manifests
Nice one Pete -
that's what I was aiming for, but you've probably saved me a day
and half a bottle of rum getting there :)
On Sun, Oct 25, 2009 at 12:30 PM, Peter Meier wrote:
>
> Hi
>
>> Thanks, I've seen that work but the trouble is I want to be able to
>> pass in a $docroot option,
>> or def
> I can't speak to the original poster's goal, but actually implementing
> something that lets me declare what the current state is, really does
> require testing what the current state is. Which, presumably, is why the
> exec type already supports "onlyif" and "unless". Extending those to
> other
> Nice one Pete -
except the minor typo:
if $docroot == $undef { $real_docroot = "/tmp/$name" }
vs.
if $docroot == undef { $real_docroot = "/tmp/$name" }
but I hope you spotted that and now have anyway time to get your
bottle of rum down. ;)
cheers pete
--~--~-~--~~
On Tue, Oct 27, 2009 at 3:45 AM, jcbollinger wrote:
> Where there are dependencies among the managed resources, Puppet will
> choose a path that accommodates them, as long as you describe the
> dependencies accurately. Sometimes you can luck out with
> underspecified dependencies, and sometimes o
Did anyone managed to get augeas running on Ubuntu 8.04? I tried for
hours to get it working, but to no avail: No augeas on ubuntu
repository, making from source fails (and the installation procedure
included with augeas doesn't agree with the file names one can get
from the repositories)...
And o
On Oct 27, 8:00 am, James Turnbull wrote:
> Puppet 0.25.1 - code name "zoot" - is now available. The 0.25.1 release
> is a maintenance release in the 0.25.x branch.
>
> The release is available at:
>
> http://reductivelabs.com/downloads/puppet/puppet-0.25.1.tar.gz
> http://reductivelabs.com/d
James Turnbull wrote :
> Puppet 0.25.1 - code name "zoot" - is now available. The 0.25.1 release
> is a maintenance release in the 0.25.x branch.
I'm seeing something really weird with this release. I wasn't seeing it
with either rc1 or rc2.
When I update my rpm packages on the master (RHEL 5.
hello,
- "Matthias Saou"
wrote:
> James Turnbull wrote :
>
> > Puppet 0.25.1 - code name "zoot" - is now available. The 0.25.1
> release
> > is a maintenance release in the 0.25.x branch.
>
> I'm seeing something really weird with this release. I wasn't seeing
> it
> with either rc1 or
> When I update my rpm packages on the master (RHEL 5.4), when the
> "service puppetmaster stop" command is run, the /usr/sbin/puppetmasterd
> file is removed. Ouch!
>
> I've just done an strace run of "service puppetmaster stop" after
> installing the packages using --noscripts and clearly see th
Matthias Saou wrote:
> When I update my rpm packages on the master (RHEL 5.4), when the
> "service puppetmaster stop" command is run, the
> /usr/sbin/puppetmasterd file is removed. Ouch!
Ouch indeed. This is my fault. :(
> I've just done an strace run of "service puppetmaster stop" after
> insta
Todd Zullinger wrote :
> Matthias Saou wrote:
> > When I update my rpm packages on the master (RHEL 5.4), when the
> > "service puppetmaster stop" command is run, the
> > /usr/sbin/puppetmasterd file is removed. Ouch!
>
> Ouch indeed. This is my fault. :(
>
> > I've just done an strace run of
On Tue, Oct 27, 2009 at 5:58 AM, Martin Englund wrote:
>
>
>
> On Oct 27, 8:00 am, James Turnbull wrote:
>
>> Puppet 0.25.1 - code name "zoot" - is now available. The 0.25.1 release
>> is a maintenance release in the 0.25.x branch.
>>
>> The release is available at:
>>
>> http://reductivelabs.c
Hi.
I'm a little confused about this piece of information on
http://reductivelabs.com/trac/puppet/wiki/UsingMultipleEnvironments
where it says:
==
Only certain parameters make sense to be configured per-environment, and
all of those parameters revolve around specifying what f
Matthias Saou wrote:
> Thanks a lot for your quick reply! Indeed, just adding the pidfile=
> to the script fixes this. I'm not sure how init scripts can be lead
> to think that a file under /usr/sbin/ can be the right one to
> remove, though, that seems like a bug somewhere else.
Yeah, that shocke
Hi,
I've got the following working fine with puppet 0.25.1, which was
previously impossible with 0.24 (yepee!) :
define dirs ( $dirs = [] ) {
# Parent directory for the ones below
file { "/nfs/skel/${title}": ensure => directory }
# Make sure the File namevar is uniqu
On Tue, 2009-10-27 at 17:25 +0100, Matthias Saou wrote:
> I've got the following working fine with puppet 0.25.1, which was
> previously impossible with 0.24 (yepee!) :
>
> define dirs ( $dirs = [] ) {
> # Parent directory for the ones below
> file { "/nfs/skel/${title}": ensu
James Turnbull wrote:
> Puppet 0.25.1 - code name "zoot" - is now available. The 0.25.1
> release is a maintenance release in the 0.25.x branch.
For the moment, I've got packages for Fedora and RHEL/CentOS at
http://tmz.fedorapeople.org/repo/puppet/
We'll work on getting those into the offi
In general, it seems like the best way to handle "must go first"
bootstrap items like that is with environments. (We haven't gotten
there yet, but we're moving in that direction.)
New node comes up in environment bootstrap, where there is a generic
definition and 1 class that just grabs the bare
Brice Figureau wrote :
>
> On Tue, 2009-10-27 at 17:25 +0100, Matthias Saou wrote:
> > I've got the following working fine with puppet 0.25.1, which was
> > previously impossible with 0.24 (yepee!) :
> >
> > define dirs ( $dirs = [] ) {
> > # Parent directory for the ones below
> >
I tried updating one of my clients today from 0.24.8 to the Git head
from 2009-10-23. Unfortunately, I didn't know how imminent the release was.
In my client log, I'm seeing things like:
[r...@ccf-hill019-12 log]# puppetd --no-daemonize --debug --test
--verbose --server FOO
debug: Puppet::Type::U
I am replying to my own question because I want to share this
knowledge of how I resolved this issue.
My objective was to get almost every aspect of system under puppet
control. So I started by installing a very bare Slackware (few
packages, just enough to get machine up and running with ssh. The
Just fired up a new Fedora11 VM puppetmaster and didn't run yum update
prior to install.
Trying to start generated /usr/lib/ruby/site_ruby/1.8/puppet/util/
pidlock.rb:33:in `initialize':
Permission denied - /var/puppet/run/puppetmasterd.pid (Errno::EACCES)
Series of chmod permission or other file
Just thought I'd follow up on my post regarding getting puppet to
compile on ESX 3.5
I had problems with the ruby-augeas bindings, and had to do a manual
workaround.
The problem was that pkg-config wasn't installed on the server and
"rake build" was failing silently. Thanks to this post on the a
Screenshots look nice.
Didn't get it going, error was:
Message: Failed to open file: fopen(/var/puppet/reports/
sizif.servers.creatim.net/2147483647.yaml) [function.fopen]: failed to
open stream: No such file or directory
#0 /var/puppet/puppetsurvey.trunk/application/models/PuppetHost.php
(157):
augeas is packaged for things newer than 8.04. I didn't have any problem
fetching the newer package source and building on 8.04. Of course, the
grub lenses don't seem to work, so I gave up, but augeas itself seems
fine.
It was basically as simple as:
apt-get build-dep augeas
apt-get source a
28 matches
Mail list logo
