[Puppet Users] Why is 'notify' acting as a 'before' and not a 'require' ?

Why is 'notify' acting as a 'before' and not a 'require' ? Can someone explain why this way is unlogical to Puppet parser, why the 'notify' would create a dependency cycle ? Why would the 'notify' need to create an order ? Isn't it supposed to carry a message, and not a constraint ? Typically i w

Re: [Puppet Users] Why is 'notify' acting as a 'before' and not a 'require' ?

Hi, On 01/24/2012 10:09 AM, Alexandre Fouché wrote: > I find it logical that my 'BackupPC.conf' apache file is put after the > apache package is installed, or more broadly after the apache class is > complete. Afterwards, i put the 'BackupPC.conf' conf, and then > afterwards, i want to notify Exec

[Puppet Users] Cross-module (package) dependencies

Hi, there was a discussion in the "can we deprecate defined() in Telly" thread about how we can even begin to design Forge modules without it. A recurring problem is that multiple modules rely on certain packages, and there is no good model (yet) to unite their resource declarations. Therefore it

Re: [Puppet Users] Re: RFC: Deprecate defined() function for Telly.

On 01/24/2012 01:57 AM, Nigel Kersten wrote: > Felix, could you take this to a new thread please? I'd really like to > keep this one focused on the topic at hand if possible :) I'd had loved to, but I'm apparently too dumb to use E-Mail. Let's try again ;( -- You received this message because yo

[Puppet Users] Cross-module (package) dependencies

Hi, there was a discussion in the "can we deprecate defined() in Telly" thread about how we can even begin to design Forge modules without it. A recurring problem is that multiple modules rely on certain packages, and there is no good model (yet) to unite their resource declarations. Therefore it

[Puppet Users] Re: Why is 'notify' acting as a 'before' and not a 'require' ?

> Think about it. You want puppet to send a notification to a resource. > Puppet must decide whether this notification gets sent. So it must > process the notifying resource. After that, *if* a notification was in > fact generated, it can process the notified resource. I see. I was making a differ

Re: [Puppet Users] Re: Why is 'notify' acting as a 'before' and not a 'require' ?

On 01/24/2012 10:51 AM, Alexandre wrote: > But it seems that for Puppet, > parsing and applying the notified ressource is one operation, which > means, if i understand correctly, that it is not possible to require > and notify the same resource as i was expecting erroneously. It's not. Both notif

Re: [Puppet Users] Cross-module (package) dependencies

On Tue, 24 Jan 2012 10:32:31 +0100 Felix Frank wrote: > Perhaps there needs to be some kind of "Forge common" module that by > policy can only ever declare virtual resources (packages are a > prominent example). This only takes care of the Forge case. The problem of having the same package being

Re: [Puppet Users] Cross-module (package) dependencies

The only "clean" way to handle this that I can think of off the top of my head is for Puppet to start silently discarding duplicate definitions and just using the first one it comes across (with perhaps a message being logged at info level so that it's not completely invisible). This is far from i

Re: [Puppet Users] Cross-module (package) dependencies

On 01/24/2012 12:38 PM, Tim Sharpe wrote: > The only "clean" way to handle this that I can think of off the top of > my head > is for Puppet to start silently discarding duplicate definitions and > just using > the first one it comes across (with perhaps a message being logged at info > level so th

Re: [Puppet Users] Cross-module (package) dependencies

What if there was some standardised way modules expose a sort of list of requirements or an API of some sort? I don't know how this would work in practice since it just popped in my mind, but I imagine for instance a monitoring module would expose some kind of hook that other modules can check for,

[Puppet Users] Re: client not getting updates no error message

finally was able to solve by reinstalling puppet server. On Jan 23, 6:39 pm, bhagyesh wrote: > guys any other suggestions ?still i am not able to find the error. > > On Jan 22, 12:02 am, bhagyesh wrote: > > > > > [root@PROXY-03 puppet]# puppet apply networking/manifests/init.pp -d - > > e 'inclu

Re: [Puppet Users] I just discovered I cannot resource-purge yumrepos -- Is there another way ?

Thank you. Simple enough to ignore the hack-ish nature :) Looks like it will do the job All it needs are a few yum commands to run whenever the file changes to refresh the local databse. I will tinker with that and report back to the list. Pay It Forward ! Share & Enjoy ! “Sometimes I think t

[Puppet Users] A Related Question - (Was: Template Help Please)

What is the minimum version of puppet (and other bits) that this technique will work on ? I am still on 2.6 (latest in EPEL) and I have the impression that this is 2.7+ stuff. “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried

Re: [Puppet Users] difficulty installing dashboard.

On Mon, Jan 23, 2012 at 5:10 PM, Michael Stahnke wrote: > > OS > CentOS release 5.7 (Final) > ruby version > ruby 1.8.5 (2006-08-25) [x86_64-linux] > rubygems version > 1.3.1 > gem list > > > *** LOCAL GEMS *** actionmailer (2.1.1) actionpack (2.1.1) activerecord (2.1.1) activeresource (2

Re: [Puppet Users] Error at the end of a puppet agent run...

On Sun, Jan 22, 2012 at 7:54 PM, Stefan Schulte < stefan.schu...@taunusstein.net> wrote: > > What version of puppet are you using on the agent side and for your > puppet master? Do you use mongrel or passenger or how do you run your > puppet master? > > puppetmasterd2.7.9 puppet agent 2.

Re: [Puppet Users] difficulty installing dashboard.

On Tue, Jan 24, 2012 at 6:32 AM, Peter Berghold wrote: > > > On Mon, Jan 23, 2012 at 5:10 PM, Michael Stahnke > wrote: >> >> >> OS > > > CentOS release 5.7 (Final) > > >> >> ruby version > > ruby 1.8.5 (2006-08-25) [x86_64-linux] Dashboard isn't supported (and doesn't really work) on Ruby 1.8.5.

Re: [Puppet Users] difficulty installing dashboard.

On Tue, Jan 24, 2012 at 11:34 AM, Michael Stahnke wrote: > > > Dashboard isn't supported (and doesn't really work) on Ruby 1.8.5. > 1.8.7 is the minimum requirement. Can you try EL6? > > Oh man... Here is what the installation docs say: Ruby or Ruby Enter

Re: [Puppet Users] best practices for caching packages on EC2

On Mon, Jan 23, 2012 at 4:06 PM, Rayson Ho wrote: > On Mon, Jan 23, 2012 at 5:14 PM, Michael Stahnke > wrote: >> How would Puppet handle it?  It would still have to either cache the >> package locally (eating lots of disk space) or point to a proxy, which >> you can do with Puppet already.  Your

Re: [Puppet Users] difficulty installing dashboard.

On Tue, Jan 24, 2012 at 8:42 AM, Peter Berghold wrote: > > > On Tue, Jan 24, 2012 at 11:34 AM, Michael Stahnke > wrote: >> >> >> >> Dashboard isn't supported (and doesn't really work) on Ruby 1.8.5. >> 1.8.7 is the minimum requirement.  Can you try EL6? >> > > Oh man... > > Here is what the insta

Re: [Puppet Users] difficulty installing dashboard.

On Tue, Jan 24, 2012 at 8:46 AM, Michael Stahnke wrote: > Which docs?  I swear we've had this updated. These, Mike: http://docs.puppetlabs.com/guides/installing_dashboard.html. I've pinged Nick Fagerlund about a fix. Apologies for the bother, Peter. We have this documented in too many place

Re: [Puppet Users] difficulty installing dashboard.

Op dinsdag 24 januari 2012 17:42:08 UTC+1 schreef Salty Old Cowdawg het volgende: > > so... I gotta get 1.8.7 on the box? EL6 is not an option at this point > as this is not a new box and does more than just puppet... > > There is a topic about this from Jo Rhett; https://groups.google.com

Re: [Puppet Users] difficulty installing dashboard.

I think I'm gonna give up on dashboard. Now that I have ruby 1.8.7 (2011-12-28 patchlevel 357) [x86_64-linux] installed there are new messages being spewed: rake --trace RAILS_ENV=production reports:migrate NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2

Re: [Puppet Users] difficulty installing dashboard.

On Tue, Jan 24, 2012 at 10:56 AM, Peter Berghold wrote: > rake aborted! > no such file to load -- rdoc/task You may have other issues (aside from the mass of deprecation warnings ... ew), but this makes it look like you're missing the rdoc gem. r -- You received this message because you are s

Re: [Puppet Users] difficulty installing dashboard.

On Tue, Jan 24, 2012 at 1:59 PM, Randall Hansen wrote: > > You may have other issues (aside from the mass of deprecation warnings > ... ew), but this makes it look like you're missing the rdoc gem. > > puppet-dashboard]# gem list *** LOCAL GEMS *** actionmailer (2.1.1) actionpack (2.1.1) active

Re: [Puppet Users] Cross-module (package) dependencies

I was thinking more in terms of an exception handler: package { "foo": ensure => installed, exceptDefined => skip} Or something of that nature. This could also be used in other situations where you want to bypass default behaviors. We've seen situations where users want to apply a file if it ex

Re: [Puppet Users] Error at the end of a puppet agent run...

If you didn't specifically configure Puppet to use Passenger then you're using Mongrel by default. Scalability => false. On Tue, Jan 24, 2012 at 8:24 AM, Peter Berghold wrote: > > > On Sun, Jan 22, 2012 at 7:54 PM, Stefan Schulte > wrote: >> >> >> What version of puppet are you using on the age

Re: [Puppet Users] Error at the end of a puppet agent run...

Aaron, What does scalability have to do with this case? There are maybe a dozen systems being managed in this case (soon will be more, so then scalability may play into this) and the configs aren't that complicated. On Tue, Jan 24, 2012 at 2:21 PM, Aaron Grewell wrote: > If you didn't specific

Re: [Puppet Users] Cross-module (package) dependencies

On Tue, Jan 24, 2012 at 4:42 AM, Walter Heck wrote: > What if there was some standardised way modules expose a sort of list > of requirements or an API of some sort? I had this thought the other day, but more focused around the higher level problem of dependency specification and consumption th

[Puppet Users] async_storeconfigs updating agent hosts.ip to puppetmaster IP

So we are trying to use async_storeconfigs. It seems when I get it all up and running the hosts.ip for an agent gets its hosts.ip entry in the DB set to the puppetmaster that it got its catalog from instead of its own IP. If I turn async_storeconfigs off and re-run puppet agent on the node that h

Re: [Puppet Users] difficulty installing dashboard.

Just FYI I went through the struggle of getting 1.8.7 on a CentOS 5.7 system and documented it here: http://groups.google.com/group/puppet-users/browse_thread/thread/0904c78fd9c8602c/090371e0efab606f?show_docid=090371e0efab606f&pli=1 Puppet dashboard is up and running fine on CentOS 5.7

Re: [Puppet Users] difficulty installing dashboard.

Install the rdoc gem. You'll always get the deprecation warnings, those are reported in bug https://projects.puppetlabs.com/issues/11669 Michael agreed its a bug, but there's no evidence it's fixed in dashboard 1.2.5 afaict. On Jan 24, 2012, at 10:56 AM, Peter Berghold wrote: > I think I'

Re: [Puppet Users] Error at the end of a puppet agent run...

Depending on your hardware and ruleset a dozen might be more than Mongrel will handle. On Tue, Jan 24, 2012 at 11:32 AM, Peter Berghold wrote: > Aaron, > > What does scalability have to do with this case?  There are maybe a dozen > systems being managed in this case (soon will be more, so then sc

Re: [Puppet Users] scaling projections for dashboard database?

Sorry for the long delay, had my head down on some other issues. Reply below. On Jan 10, 2012, at 10:55 AM, Daniel Pittman wrote: > Yes. It sounds like the current storage of reports isn't going to > work well for you, at least if you want to retain history. This is > absolutely unfortunate, and

Re: [Puppet Users] Error at the end of a puppet agent run...

On Tue, Jan 24, 2012 at 11:24:58AM -0500, Peter Berghold wrote: > On Sun, Jan 22, 2012 at 7:54 PM, Stefan Schulte < > stefan.schu...@taunusstein.net> wrote: > > > > > What version of puppet are you using on the agent side and for your > > puppet master? Do you use mongrel or passenger or how do yo

Re: [Puppet Users] Cross-module (package) dependencies

On Tue, Jan 24, 2012 at 2:53 PM, Nigel Kersten wrote: > > > On Tue, Jan 24, 2012 at 4:42 AM, Walter Heck wrote: >> >> What if there was some standardised way modules expose a sort of list >> of requirements or an API of some sort? > > > I had this thought the other day, but more focused around th

Re: [Puppet Users] Cross-module (package) dependencies

> I had this thought the other day, but more focused around the higher level > problem of dependency specification and consumption than Packages in > particular. Yeah, since that is something that is currently kind of difficult to implement properly. I'd welcome a proper way to do this. > What if

[Puppet Users] constraint checking

Hi, I want to assert a file exists - but in a way that doesn't have the potential to create conflicting resource definitions. I know this has been asked many times before: "How can I check whether a file exists, like 'File.exists?(file)' or '-f $file'?" My very specific use case is with a u

Re: [Puppet Users] scaling projections for dashboard database?

On Tue, Jan 24, 2012 at 14:55, Jo Rhett wrote: > Sorry for the long delay, had my head down on some other issues. Reply > below. > > On Jan 10, 2012, at 10:55 AM, Daniel Pittman wrote: > >> Yes.  It sounds like the current storage of reports isn't going to >> work well for you, at least if you wan

[Puppet Users] hash iteration with erb templates

Hi list, I'm trying to deploy a configuration file via a template (puppet 2.6.13). The problem is that I can't get my iteration right. You can check out the gist here: https://gist.github.com/1674234 But the code is like the following: $drbd_resource = { data_share1 => { 'node1.local' => ['192

Re: [Puppet Users] Cross-module (package) dependencies

On Tue, Jan 24, 2012 at 4:34 PM, Walter Heck wrote: > > I had this thought the other day, but more focused around the higher > level > > problem of dependency specification and consumption than Packages in > > particular. > Yeah, since that is something that is currently kind of difficult to > im

Re: [Puppet Users] Cross-module (package) dependencies

On Wed, Jan 25, 2012 at 05:51, Nigel Kersten wrote: > Yeah. I went for functions to try and hide the fact that this is a resource > underneath, but perhaps modeling this more transparently makes sense. > >> We'd also need a way to test if a capability is being provided by the >> system as a whole.

[Puppet Users] Re: hash iteration with erb templates

Sorted. Thanks Kevin, https://gist.github.com/1674234 On Jan 25, 1:42 pm, denmat wrote: > Hi list, > > I'm trying to deploy a configuration file via a template (puppet 2.6.13). > > The problem is that I can't get my iteration right. > > You can check out the gist here:https://gist.github.com/167