[Puppet Users] ANNOUNCE: Puppet 0.25.1 released!

[James Turnbull]

-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/gems/puppet-0.25.1.gem

Please report issues and feedback via the Reductive Labs Redmine site:

http://projects.reductivelabs.com

Please select an affected version of 0.25.1.

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.

* The zone type now works with OpenSolaris

* You can now specify null values for environment variables in the cron type

* The Vim syntax highlighting now identifies new regex structures

CHANGELOG

*  Bug #1538: Yumrepo sets permissions wrongly on files in /etc/yum.repos.d
* Bug #1719: Puppetd runtime increase dramaticilly after upgrading to 24.6
* Bug #1742: --color accepts parameters other than true, false, ansi,
html - but produces "nil" output
* Bug #1900: Parsing of quoted $ in stdin
* Bug #1908: cron environment does not allow empty values
* Bug #2508: misleading error about ActiveRecord versions
* Bug #2534: Parser should raise an error if you specify the same
property twice
* 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: YAML sometimes modifies the contents of string data
* 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 #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
* Bug #2661: puppetd exits if the master is unreachable.
* Bug #2664: regexp parse error
* Bug #2665: regex problem with package names containing ++
* Bug #2668: Too many facts: request-URI Too Large
* Bug #2672: Cannot have underscores in node name
* Bug #2674: createpackage.sh: problem finding install.rb
* Bug #2676: lib/puppet/agent.rb apparent typo
* Bug #2679: Possible regression
* Bug #2681: "Duplicate generated resource;skipping" for each managed
resource
* Bug #2685: Got an uncaught exception of type TypeError
* Bug #2686: ActiveSupport >= 2.3.3 forces use of defective JSON library
* Bug #2688: macauthorization provider now doesn't deal with booleans
correctly.
* Bug #2689: Running puppet as non-root => getting rid of all those
ownership warnings
* Bug #2691: "Could not retrieve catalog: HTTP-Error: 500 Internal
Server Error" with tagged exported resources
* Bug #2697: provider/portage.rb: update-eix is deprecated
* Bug #2698: provider/portage.rb: format string has changed (again)
* Bug #2699: Configurable port in the included Red Hat init script is broken
* Bug #2702: puppetdoc rdoc mode fails if outputdir not specified
* Bug #2707: 'config_vers

[Puppet Users] Re: Conditional based on existence of a file

[Peter Meier]

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 runs on the client, returns an exitcode of zero.
>
> http://reductivelabs.com/trac/puppet/wiki/TypeReference#id11
>
> So, obviously some commands can be executed on the client and impact  
> what happens next.  I'm saying it would be nice to apply such logic  
> to a block of code instead of an individual exec.

Functions and Variables are executed/evaluated on the master,  
resources are applied/evaluated on the client. As onlyif is part of a  
resource it's clear that this command runs on the client, but you  
shouldn't see it as a command or a function: Your exec example is part  
of the exec-resource to evaluates its state and is not actually meant  
as a condition. Your mixings things which don't belong to each another.

Maybe you have a look at how puppet internally works [1]. The reason  
for this problem is that things get evaluated at two different places,  
which has its reason and is also correct that it works that way.


>> And this makes totally sense due to other reasons.

I should have added an example here. Maybe have a look at the  
ext_lookup function as an example why it makes sense, that functions  
are evaluated on the master.

Besides that, maybe a problem we have in this discussion is that if  
talk about functions we necessary don't mean always the same?!

>> So if you use the client-server setup you're restricted to
>> that. The
>> only information the server can get _from_ the client are
>> facts or
>> information from an external source, which the client would
>> have to feed.
>>
>> But if you would stay with local execution only I think
>> you'll easily
>> able to do what you want.
>
> If it's so easy, please provide an example solution.  And if your  
> example consists of disparate facts to determine if specific files  
> exist, please don't bother because that's specifically what I said I  
> wasn't looking for :-)

simply use puppet as a standalone tool, then your only on one host and  
everything gets evaluated in the same place. The restriction (in your  
terms) that this can only be satisfied using facts is only due to the  
reason that we're in a client/server relation and not everything gets  
evaluated on the same host.

>> > A wise manager once told me that you should
>> > build your systems around the needs of your business
>> instead of
>> > building your business around the capabilities of your
>> systems.
>>
>> What I could always observe is that people asking for such
>> things are
>> trying to get their used script thinking behaviour (to call
>> it like
>> that) into puppet. But one of the main ideas of puppet is
>> that it
>> changes the way how you look at your infrastructure and how
>> you manage
>> your infrastructure. So actually: Yes, puppet changes the
>> way your doing
>> your business.
>
> What I'm looking for here is nothing extreme.  It's very simple.  A  
> set of puppet logic that's only evaluated if a certain condition on  
> the client is met.  What's wrong with that?  It sounds very  
> reasonable to me.  On the contrary, having the mindset that  
> everything should be written as a custom fact, or extension or  
> whatever, illustrates the point I was trying to make.  Sure it  
> works, but it's a work-around.  People get used to the extra effort  
> required and consider it old-hat when in actuality (again, IMHO)  
> it's not ideal and in many scenarios is a serious limitation.
>
> If we use such lines of thinking, then let's just go ahead and get  
> rid of the conditional operators introduced in 0.24.6.  The only  
> test you need is true or false!  Of course I'm kidding here, I love  
> the ability to use more complex expressions.
>
>
> Anyway, it appears that what I'm looking for may not be possible  
> today without custom facts.  Ok, fine.  My next question is, why?   
> If it's because such functionality just hasn't been added yet,  
> that's perfectly reasonable.  I'll be glad to submit a more detailed  
> and descriptive feature request.  However, if the answer is because  
> people (most importantly, puppet developers) believe that what I'm  
> looking for (ability to conditionally process puppet logic based on  
> the result of a command executed on the client) is unwanted by  
> users, well I don't believe that's true.  I definitely want it and  
> it's clear others do as well.

it's mainly due to the reason how puppet works. the client sends its  
facts to the master, this one evaluates the manifests with this  
information and executes the functions and sends down the compiled  
catalog to the client. This one, only applies the catalog and does the  
necessary changes to fit into the described state. As mentioned above  
to onlyif is just

[Puppet Users] Re: Conditional based on existence of a file

[Peter Meier]

> 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 are not a script which is executed in order, but  
> rather a declaration of the state in which the client
> node should be.  Kind of like the difference between Imperative  
> programming (C/Ruby) and Logical programming (PROLOG).
> So you are looking at it saying "I want to evaluate this condition,  
> then execute this bit of code only if the condition
> is true".  Puppet wants to look at the state of the node,  
> compare/contrast to the desired state, then "Make It So".   To
> do that, you need to know various "Facts" about the node.

I'd like to second that. Thanks for your explanations.

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
-~--~~~~--~~--~--~---

[Puppet Users] Re: BUG? $name inside a definition 'method signature' different to within a body ?

[Dick Davies]

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 default to something if one is not there; I suppose I can probably
>> get around it by checking
>> if $docroot is defined and if not setting it or something?
>
> how about:
>
> define bar($docroot = undef) {
>  if $docroot == $undef { $real_docroot = "/tmp/$name" }
>  else { $real_docroot = $docroot }
>
>  file { $real_docroot: ensure => present }
> }
>
> 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
-~--~~~~--~~--~--~---

[Puppet Users] Re: Conditional based on existence of a file

[Peter Meier]

> 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 things doesn't seem crazy. And as it stands, several things I do
> basically come down to syntactic sugar around an exec.

in my opinion it's far beyond "syntactic sugar around an exec".

Your right onlyif is part of the way how to evaluate the state of one  
single resource, but a condition in the manifest is a decision whether  
to manage certain resource(s) at all. This is a decision which is done  
by the master, however the state of one single resource is evaluated  
by the client.

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
-~--~~~~--~~--~--~---

[Puppet Users] Re: BUG? $name inside a definition 'method signature' different to within a body ?

[Peter Meier]

> 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


--~--~-~--~~~---~--~~
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: Module include order?

[John Arundel]

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 overspecified dependencies
> are (mostly) harmless, but both those situations are brittle and
> better avoided.

I think it can be very helpful for beginners to be able to see the
diagram of their dependencies, and where there is a cycle or an
ordering problem, usually seeing it in graphical form makes it clear
what the relationships should be.

I wrote a blog post on the '--graph' option for drawing dependency
graphs which was touched on here a few months ago. If anyone doesn't
know how to do this, or would like to see some example diagrams, have
a look:

http://bitfieldconsulting.com/puppet-dependency-graphs

John
--
http://bitfieldconsulting.com/
http://twitter.com/bitfield

--~--~-~--~~~---~--~~
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] Problem with augeas on Ubuntu 8.04

[Adam Ryczkowski]

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 of course I failed to find any how-to on the web. The closest one
I found is this: 
http://www.mail-archive.com/augeas-de...@redhat.com/msg01076.html

Can someone in the list share his own experience with getting augeas
work with puppet 0.25.1rc2 (or any other) in Ubuntu 8.04?

Thank you very 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: ANNOUNCE: Puppet 0.25.1 released!

[Martin Englund]

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/downloads/gems/puppet-0.25.1.gem
>
I've updated the OpenSolaris package to the 0.25.1 release:


So you just have to run:
pkg install puppet
to get the new package installed.

cheers,
/Martin
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Puppetmaster service removing puppetmasterd executable (was: Re: [Puppet Users] ANNOUNCE: Puppet 0.25.1 released!)

[Matthias Saou]

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.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 this :

[pid   413] execve("/bin/rm", ["rm", "-f", "/usr/sbin/puppetmasterd"],
[/* 6 vars */]) = 0

The packages are using only the init scripts included in the source.

Matthias

-- 
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora release 10 (Cambridge) - Linux kernel
2.6.27.30-170.2.82.fc10.x86_64 Load : 0.44 0.44 0.32

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Puppetmaster service removing puppetmasterd executable (was: Re: [Puppet Users] ANNOUNCE: Puppet 0.25.1 released!)

[R.I.Pienaar]

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 rc2.
> 
> 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 cannot reproduce this behavior, did you have a look at the rc script in 
question, do you see why its doing it?

-- 
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
-~--~~~~--~~--~--~---

Re: Puppetmaster service removing puppetmasterd executable (was: Re: [Puppet Users] ANNOUNCE: Puppet 0.25.1 released!)

[Peter Meier]

> 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 this :
>
> [pid   413] execve("/bin/rm", ["rm", "-f", "/usr/sbin/puppetmasterd"],
> [/* 6 vars */]) = 0
>
> The packages are using only the init scripts included in the source.

the only rm I see there is the one of the lockfile:  
http://github.com/reductivelabs/puppet/raw/master/conf/redhat/server.init

the only change since rc2 imho have been  
http://github.com/reductivelabs/puppet/commit/b62d9668e04f40f2e3aa6c0f26dd26d1f75d8e22

which shouldn't introduce this behaviour... :/

can you reproduce it and find from where the actual call came and then  
file a bug?

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
-~--~~~~--~~--~--~---

Re: Puppetmaster service removing puppetmasterd executable (was: Re: [Puppet Users] ANNOUNCE: Puppet 0.25.1 released!)

[Todd Zullinger]

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
> installing the packages using --noscripts and clearly see this :
>
> [pid   413] execve("/bin/rm", ["rm", "-f", "/usr/sbin/puppetmasterd"],
> [/* 6 vars */]) = 0
>
> The packages are using only the init scripts included in the source.

The puppetmaster init script doesn't have the pidfile var set, and the
killproc function manages to think /usr/sbin/puppetmasterd is the pid
file.  I believe the fix is to add a pidfile setting:

diff --git i/conf/redhat/server.init w/conf/redhat/server.init
index 5505058..4f44206 100644
--- i/conf/redhat/server.init
+++ w/conf/redhat/server.init
@@ -13,6 +13,7 @@ PATH=/usr/bin:/sbin:/bin:/usr/sbin
 export PATH
 
 lockfile=/var/lock/subsys/puppetmaster
+pidfile=/var/run/puppet/puppetmasterd.pid
 
 # Source function library.
 . /etc/rc.d/init.d/functions

I'm very sorry for breaking this.  I'll test and send a patch off
soon.

-- 
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
Remember wisdom is gained through failure as well as success.



pgpQuRDioytJb.pgp
Description: PGP signature

Re: Puppetmaster service removing puppetmasterd executable (was: Re: [Puppet Users] ANNOUNCE: Puppet 0.25.1 released!)

[Matthias Saou]

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 "service puppetmaster stop" after
> > installing the packages using --noscripts and clearly see this :
> >
> > [pid   413] execve("/bin/rm", ["rm", "-f", "/usr/sbin/puppetmasterd"],
> > [/* 6 vars */]) = 0
> >
> > The packages are using only the init scripts included in the source.
> 
> The puppetmaster init script doesn't have the pidfile var set, and the
> killproc function manages to think /usr/sbin/puppetmasterd is the pid
> file.  I believe the fix is to add a pidfile setting:
> 
> diff --git i/conf/redhat/server.init w/conf/redhat/server.init
> index 5505058..4f44206 100644
> --- i/conf/redhat/server.init
> +++ w/conf/redhat/server.init
> @@ -13,6 +13,7 @@ PATH=/usr/bin:/sbin:/bin:/usr/sbin
>  export PATH
>  
>  lockfile=/var/lock/subsys/puppetmaster
> +pidfile=/var/run/puppet/puppetmasterd.pid
>  
>  # Source function library.
>  . /etc/rc.d/init.d/functions
> 
> I'm very sorry for breaking this.  I'll test and send a patch off
> soon.

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.

Matthias

-- 
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora release 10 (Cambridge) - Linux kernel
2.6.27.30-170.2.82.fc10.x86_64 Load : 0.09 0.11 0.13

--~--~-~--~~~---~--~~
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: ANNOUNCE: Puppet 0.25.1 released!

[Nigel Kersten]

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.com/downloads/puppet/puppet-0.25.1.tar.gz
>> http://reductivelabs.com/downloads/gems/puppet-0.25.1.gem
>>
> I've updated the OpenSolaris package to the 0.25.1 release:
> 
>
> So you just have to run:
> pkg install puppet
> to get the new package installed.

Mac packages updated at: https://sites.google.com/a/explanatorygap.net/puppet/

MacPorts patch submitted at: https://trac.macports.org/ticket/22258 so
that should be available on MacPorts within 48 hours or so.


-- 
nigel

--~--~-~--~~~---~--~~
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] Unclear information about using environments

[Sven Mueller]

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 files to use to
compile a client's configuration. Those parameters are:

* modulepath: Where to look for modules. It's best to have a
standard module directory that all environments share and then a
per-environment directory where custom modules can be stored.
* templatedir: Where to look for templates. The modulepath should be
preferred to this setting, but it allows you to have different versions
of a given template in each environment.
* manifest: Which file to use as the main entry point for the
configuration. The Puppet parser looks for other files to compile in the
same directory as this manifest, so this parameter also determines where
other per-environment Puppet manifests should be stored. With a separate
module path, it should be easy to use the same simple manifest in all
environments.
===

Now, it seems the author only sees use in setting those parameters, but
does it also mean that only those parameters can be set inside an
environment?
And if so, wouldn't it also make sense to set "manifestdir" to something
environment specific?

We are thinking about how to use environments to differentiate
production, QA, devel and office servers (which need varying package
versions etc.).

Also: Do I understand the fileserver stuff correctly, so that I could
also have (sort of) environments there?

Like

[files]

[production]

[qa]


etc.?


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Re: Puppetmaster service removing puppetmasterd executable (was: Re: [Puppet Users] ANNOUNCE: Puppet 0.25.1 released!)

[Todd Zullinger]

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 shocked me.  But it is definitely user error (on my part)
as passing -p tells the killproc function that the pidfile will be the
option that follows it.  When that is emtpy, what follows is the name
of the executable.

I still intend to rework the initscripts to be compliant with the
current Fedora guidelines, as right now they are not very close,
especially with respect to return codes and such.  And ideally, we'll
fix up more problems than we cause with that process.

FWIW, running 'sh -x /etc/init.d/puppetmaster stop' made it fairly
easy to see the problem.  Thanks again for reporting it!

-- 
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
When we remember we are all mad, the mysteries of life disappear and
life stands explained.
-- Mark Twain



pgpCP2WAWCFXq.pgp
Description: PGP signature

[Puppet Users] Warnings with regsubst()

[Matthias Saou]

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 unique by prepending the path
$fulldirs = regsubst($dirs, ".*", "/nfs/skel/${title}/\0")
file { $fulldirs: ensure => directory }
}

Then I call it in a way similar to this :

dirs { "dir1": dirs => [ "inc", "bin" ]
dirs { "dir2": dirs => [ "inc", "bin" ]

But then I see warnings in the puppetmaster log :

Puppet (warning): Unrecognised escape sequence '\0' in file foo.pp [...]

I've also tried with "^(.*)$" and \1 but it's the same. So before I go
and report this as a minor bug, am I doing something wrong here?

Matthias

-- 
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora release 10 (Cambridge) - Linux kernel
2.6.27.30-170.2.82.fc10.x86_64 Load : 0.39 0.46 0.35

--~--~-~--~~~---~--~~
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: Warnings with regsubst()

[Brice Figureau]

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}": ensure => directory }
> # Make sure the File namevar is unique by prepending the path
> $fulldirs = regsubst($dirs, ".*", "/nfs/skel/${title}/\0")
> file { $fulldirs: ensure => directory }
> }
> 
> Then I call it in a way similar to this :
> 
> dirs { "dir1": dirs => [ "inc", "bin" ]
> dirs { "dir2": dirs => [ "inc", "bin" ]
> 
> But then I see warnings in the puppetmaster log :
> 
> Puppet (warning): Unrecognised escape sequence '\0' in file foo.pp [...]

I think puppet string interpolation is warning you that inserting a null
byte is forbidden.
Try to escape the \0 so that it isn't eaten by the double quote
interpolation:

$fulldirs = regsubst($dirs, ".*", "/nfs/skel/${title}/\\0")

-- 
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!


--~--~-~--~~~---~--~~
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.1 released!

[Todd Zullinger]

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 official repos soon-ish (barring
any other bugs like the one I introduced to delete puppetmasterd.)

-- 
ToddOpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
There are only 10 kinds of people: Those who understand binary and
those who don't.



pgpjMWrZJLNDb.pgp
Description: PGP signature

[Puppet Users] Re: Explicit Repo, Package ordering

[Disconnect]

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 minimum to make
everything else work. (In our case, that is mostly just the ldap
configuration so that future runs find the users they want.) Then they
update the puppet config to move to a new environment, and the new
environment can ignore all the weird dependencies.

On Sat, Oct 24, 2009 at 11:25 AM, Douglas Garstang
 wrote:
>
> Oh boy. Puppet is frustrating the heck out of me.
> I have this below
>
> node tst_basenode {
>
>    include yum
>
>    Package {
>        require => [
>            Yumrepo["CentOS-Base"],
>            Yumrepo["EPEL-Core"],
>            ...
>        ]
>    }
> }
>
> node tst_childnode inherits tst_basenode {
>    include ldap_client
> }
>
> This generally seems to work, making sure that my yum repo's are in
> place before anything else is done. However, I saw that the
> yum-priorities rpm was being installed way later, and it needs to be
> up there with yum, done initially. So, I added a
> package["yum-priorities"] to require=> in that default package
> definition in the base node and puppet claimed that it found
> dependancy cycles. ARGH!
>
> Actually, if you think about it, there's no guarantee as to when yum
> is installed either. It just happens to already be installed because
> this is CentOS, but if it wasn't installed, yum might get installed
> later, which would break everything.
>
> Quite simply, how do I GUARANTEE that my repos are done FIRST followed
> by any mandatory packages like yum and yum-priorities?
>
> Doug.
>
> >
>

--~--~-~--~~~---~--~~
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: Warnings with regsubst()

[Matthias Saou]

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
> > file { "/nfs/skel/${title}": ensure => directory }
> > # Make sure the File namevar is unique by prepending the path
> > $fulldirs = regsubst($dirs, ".*", "/nfs/skel/${title}/\0")
> > file { $fulldirs: ensure => directory }
> > }
> > 
> > Then I call it in a way similar to this :
> > 
> > dirs { "dir1": dirs => [ "inc", "bin" ]
> > dirs { "dir2": dirs => [ "inc", "bin" ]
> > 
> > But then I see warnings in the puppetmaster log :
> > 
> > Puppet (warning): Unrecognised escape sequence '\0' in file foo.pp [...]
> 
> I think puppet string interpolation is warning you that inserting a null
> byte is forbidden.
> Try to escape the \0 so that it isn't eaten by the double quote
> interpolation:
> 
> $fulldirs = regsubst($dirs, ".*", "/nfs/skel/${title}/\\0")

I could have sworn I had already tried that, but I guess not. Things
still work and the warning is gone. Thanks a lot!

Matthias

-- 
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora release 10 (Cambridge) - Linux kernel
2.6.27.30-170.2.82.fc10.x86_64 Load : 0.42 0.24 0.19

--~--~-~--~~~---~--~~
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] Possible bug 2617 - json - false value when expecting true

[Jason Antman]

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::User::ProviderUser_role_add: file rolemod does not
exist
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Puppet::Type::User::ProviderLdap: true value when expecting false
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl
does not exist
debug: Failed to load library 'ldap' for feature 'ldap'
debug: /File[/var/lib/puppet/ssl/csr_ccf-hill019-12.example.com.pem]:
Autorequiring File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring
File[/var/lib/puppet/ssl/certs]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug:
/File[/var/lib/puppet/ssl/private_keys/ccf-hill019-12.example.com.pem]:
Autorequiring File[/var/lib/puppet/ssl/private_keys]
debug: /File[/var/lib/puppet/client_yaml]: Autorequiring
File[/var/lib/puppet]
debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/log/puppet/http.log]: Autorequiring File[/var/log/puppet]
debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/etc/puppet/namespaceauth.conf]: Autorequiring
File[/etc/puppet]
debug: /File[/var/lib/puppet/state/graphs]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/clientbucket]: Autorequiring
File[/var/lib/puppet]
debug: /File[/var/lib/puppet/classes.txt]: Autorequiring
File[/var/lib/puppet]
debug:
/File[/var/lib/puppet/ssl/public_keys/ccf-hill019-12.example.com.pem]:
Autorequiring File[/var/lib/puppet/ssl/public_keys]
debug: /File[/var/lib/puppet/ssl/certs/ccf-hill019-12.example.com.pem]:
Autorequiring File[/var/lib/puppet/ssl/certs]
debug: /File[/var/lib/puppet/ssl/private]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring
File[/var/lib/puppet/ssl]
debug: Finishing transaction -607050108 with 0 changes
debug: Using cached certificate for ca
debug: Using cached certificate for ccf-hill019-12.example.com
debug: Loaded state in 0.00 seconds
debug: Using cached certificate for ca
debug: Using cached certificate for ccf-hill019-12.example.com
debug: Format s not supported for Puppet::Resource::Catalog; has not
implemented method 'from_s'
debug: Puppet::Network::Format[json]: false value when expecting true
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run

Is this bug 2617? I can't find many mentions of these errors.

I noticed that it *may*/*should* be fixed in 0.25.1. Is that the consensus?

Thanks,
Jason Antman

--~--~-~--~~~---~--~~
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 hangs with 100% CPU usage

[Bostjan Skufca]

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. Then I
started modifications of the system by means of puppet. I built a nice
set of modules which handled the basics, like system config files and
libraries and various tool installations. Then I wrapped all this in a
single class, like this:
class groundwork {
  include 'sys'
  include 'openssl'
  include 'libs'
  include 'tools'
  include 'ssh'
}

Then I started adding real stuff, production services, like httpd,
like this:
class httpd {
  file {file1:...}
  file {file2: ...}
  package { 'httpd': ...}
  file { '/etc/rc.d/rc.httpd': ...}
  file { '/var/www': ...}
  service {'httpd': ...}
}
And there were consequential 'require' relationships to these items
above and the first one included this line:
file {'file1':
  require => Class['groundwork'],
}


And I thought that this line meant a dependency like this:

file1
  |
  | (depends on)
  |
groundwork(class)
  |
  | (which in turn depends on)
  |
ssh (class)
  |
  | (which in turn depends on)
  |
file {'/etc/rc.d/rc.sshd':...}
file {'/etc/ssh/sshd_config':...}
package {'openssh': ...}
etc.

But what it REALLY means is that my item (in this case, file1) was
dependent on every real item in the groundwork class and all the
classes included. Every file from ssh class, and every file from libs
class and every file from SYS class.

This dependency tree grew so large that puppet was unable to walk it
in decent time. Ergo, lesson learned: puppet maintains file
dependencies by itself, so you should only include those dependencies
that your item in question really depends on, not everything that YOU
THINK should be done before.

I hope this information helps someone to avoid spending couple of days
of debugging. And relationship graphs (from relationships.dot and
expanded_relationships.dot) really helped resolving this issue.

Best regards,
b.


On 26 sep., 00:23, Bostjan Skufca  wrote:
> Hi again,
>
> puppetd started to hang with100% CPU usage all of the sudden. Strace
> just keeps repeating these 2 lines:
>
> --- SIGVTALRM (Virtual timer expired) @ 0 (0) ---
> sigreturn()                             = ? (mask now [])
>
> In logs it hangs with this message:
> debug: Calling fileserver.describe
>
> But lots of these fileserver.describe calls prior to hang are
> successful.
>
> If I run it with puppetd --test --debug and hit Ctrl+C when it is
> "hanged", I get this trace:
> debug: Signal caught here:
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:28:in `call'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:28:in `adjacent'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:232:in `adjacent'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:260:in `walk'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:262:in `walk'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:260:in `each'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:260:in `walk'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:262:in `walk'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:260:in `each'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:260:in `walk'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:262:in `walk'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:260:in `each'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:260:in `walk'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:262:in `walk'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:260:in `each'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:260:in `walk'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:262:in `walk'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:260:in `each'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:260:in `walk'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:262:in `walk'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:260:in `each'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:260:in `walk'
> debug: /usr/local/puppet-0.24.8-2/lib/ruby/site_ruby/1.8/puppet/
> simple_graph.rb:262:in `walk'
> debug: /usr/local/puppet-0.24.8-2/

[Puppet Users] Interesting puppet-server-0.24.8-4.fc11 install issue: puppetmasterd.pid (Errno::EACCES)

[EscVector]

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 errors showed in trace...
  /var/puppet/run: Operation not permitted - /var/puppet/run
Oct 27 09:46:06 puppet puppetmasterd[7755]: (/Settings[top]/Settings
[main]/File[/var/puppet/state]/mode) change 

Did yum update, uninstalled puppet-server, deleted /etc/puppet /var/
puppet, re-installed puppet-server and problem is fixed.

--~--~-~--~~~---~--~~
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: install puppet on esx

[John Warburton]

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 augeas-
devel list - http://www.mail-archive.com/augeas-de...@redhat.com/msg02164.html

Also, I install in a non-standard directory, so needed to include that
in the run time libs for augeas, hence my build doc now says:

Install pkg-config-0.23.tar.gz on server in default location

[r...@esxhost tmp]# tar xzf ruby-augeas-0.3.0.tgz
[r...@esxhost tmp]# cd ruby-augeas-0.3.0
[r...@esxhost ruby-augeas-0.3.0]# export PKG_CONFIG_PATH=/apps/puppet/
augeas-0.5.3/lib/pkgconfig
[r...@esxhost ruby-augeas-0.3.0]# export CONFIGURE_ARGS="--with-
ldflags=-Wl,-R/apps/puppet/augeas/lib"
[r...@esxhost ruby-augeas-0.3.0]# rake build
[r...@esxhost ruby-augeas-0.3.0]# cp lib/augeas.rb /apps/puppet/ruby/
lib/ruby/site_ruby/1.8/augeas.rb
[r...@esxhost ruby-augeas-0.3.0]# cd ./ext/augeas/
[r...@esxhost augeas]# make install

Hope this helps

John

On Sep 8, 11:33 am, John Warburton  wrote:
>
> [r...@esxhost augeas-0.5.0]#
>
> [r...@esxhost augeas-0.5.0]# *export
> CPPFLAGS=-I/apps/puppet/readline-4.3/include
> LDFLAGS=-L/apps/puppet/readline-4.3/lib *
>
> [r...@esxhost augeas-0.5.0]# *./configure --prefix=/apps/puppet/augeas-0.5.0
> *
>
> [r...@esxhost augeas-0.5.0]# *make > MAKELOG 2>&1 &*
>
> [r...@esxhost augeas-0.5.0]# *make install > MAKELOG.install 2>&1 &*
>
> [r...@esxhost tmp]# *cd ruby-augeas-0.2.0*
>
> [r...@esxhost ruby-augeas-0.2.0]# */apps/puppet/ruby-1.8.7-p160/bin/ruby
> ext/augeas/extconf.rb
> --with-augeas-config=/apps/puppet/augeas-0.5.0/lib/pkgconfig*
>
> # I can’t get this to work naturally, so have to hack the Makefile, My lack
> of understanding of ruby in general
>
> [r...@esxhost ruby-augeas-0.2.0]# *vi Makefile*
>
> INCFLAGS = -I. -I$(topdir) -I$(hdrdir) -I$(srcdir)
> -I/apps/puppet/augeas/include
>
> CPPFLAGS =   $(DEFS) $(cppflags) -I/apps/puppet/augeas/include
>
> ldflags  = -L.  -rdynamic -Wl,-export-dynamic  -L/apps/puppet/augeas/lib
> -Wl,-R/apps/puppet/augeas/lib
>
> LIBS =    -lrt -ldl -lcrypt -lm   -lc -laugeas -lruby-static
>
> [r...@esxhost ruby-augeas-0.2.0]# *make*
>
> [r...@esxhost ruby-augeas-0.2.0]# *make install*
>
> /usr/bin/install -c -m 0755 _augeas.so
> /apps/puppet/ruby-1.8.7-p160/lib/ruby/site_ruby/1.8/i686-linux
>
> [r...@esxhost ruby-augeas-0.2.0]# *cp lib/augeas.rb
> /apps/puppet/ruby/lib/ruby/site_ruby/1.8/*
>
>
> --
> John Warburton
> Ph: 0417 299 600
> Email: jwarbur...@gmail.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: New webgui to survey your puppet activities

[Bostjan Skufca]

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): Horde_Yaml::loadFile('/var/puppet/rep...')
#1 /var/puppet/puppetsurvey.trunk/application/models/PuppetHost.php
(115): Default_Model_PuppetHost->parsePuppetReports()
#2 /var/puppet/puppetsurvey.trunk/application/models/Report.php(55):
Default_Model_PuppetHost->__construct('sizif.servers.c...')
#3 /var/puppet/puppetsurvey.trunk/application/controllers/
ReportController.php(59): Default_Model_Report->__construct
('sizif.servers.c...')
#4 /usr/local/httpd-2.2.14-1/php-5.2.11-2/lib/php/Zend/Controller/
Action.php(133): ReportController->init()
#5 /usr/local/httpd-2.2.14-1/php-5.2.11-2/lib/php/Zend/Controller/
Dispatcher/Standard.php(262): Zend_Controller_Action->__construct
(Object(Zend_Controller_Request_Http), Object
(Zend_Controller_Response_Http), Array)
#6 /usr/local/httpd-2.2.14-1/php-5.2.11-2/lib/php/Zend/Controller/
Front.php(946): Zend_Controller_Dispatcher_Standard->dispatch(Object
(Zend_Controller_Request_Http), Object(Zend_Controller_Response_Http))
#7 /usr/local/httpd-2.2.14-1/php-5.2.11-2/lib/php/Zend/Application/
Bootstrap/Bootstrap.php(77): Zend_Controller_Front->dispatch()
#8 /usr/local/httpd-2.2.14-1/php-5.2.11-2/lib/php/Zend/Application.php
(358): Zend_Application_Bootstrap_Bootstrap->run()
#9 /var/puppet/puppetsurvey.trunk/public/index.php(26):
Zend_Application->run()
#10 {main}
(this file does not exist, but it's filename seems like the largest
positive int number)

Other glitches:
- hardcoded URIs for images/css/js (have to dedicate a vhost to it)
- graceful error handling missing when misconfigured
- either a documentation of config options or a test.php file which
checks configs and suggests correct options or common mistakes.

You will receive compliments when I get it working, seems
promising. :)

b.




On 26 okt., 21:42, Philip  wrote:
> Hi everybody
>
> I wrote another web application to monitor puppet like puppetview or
> puppetshow. Sorry i was bored by the existing solutions and needed
> something what looked a bit sexy.
>
> Please have a look to
>
> http://puppetsurvey.sourceforge.net
>
> for more information and don't hesitate to contact me for any feedback
>
> Greetings
> Philip
--~--~-~--~~~---~--~~
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: Problem with augeas on Ubuntu 8.04

[seph]

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 augeas
  cd augeas_0.5.1
  debuild -i -us -uc -b

seph

Adam Ryczkowski  writes:

> 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 of course I failed to find any how-to on the web. The closest one
> I found is this: 
> http://www.mail-archive.com/augeas-de...@redhat.com/msg01076.html
>
> Can someone in the list share his own experience with getting augeas
> work with puppet 0.25.1rc2 (or any other) in Ubuntu 8.04?
>
> Thank you very 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
-~--~~~~--~~--~--~---