[Puppet Users] Re: element name as a variable

> You could do: > > define solaris::media($ensure = "present") { >      file { "solaris_media_${name}": >          path => "/opt/SUNWjet/etc/$name", >          content => template("jumpstart/${name}.erb"), >          ensure => $ensure, >          require => File[SUNWjet] # don't you mean Package[S

Re: [Puppet Users] Re: element name as a variable

deet wrote: > Thanks Scott. > Sounds like I'll stick with what I'm doing as it seems the defines > won't save me much work. > Thanks again for the quick reply. > You could do: define solaris::media($ensure = "present") { file { "solaris_media_${name}": path => "/opt/SUNWjet/e

[Puppet Users] Re: element name as a variable

> To answer your question: Yes, you can. You're looking for either the $name or > $title variable (by > default they are both the same). > Thanks Scott. Sounds like I'll stick with what I'm doing as it seems the defines won't save me much work. Thanks again for the quick reply. Happy

Re: [Puppet Users] element name as a variable

deet wrote: >Greetings. > >I'm curious if their are any magic variable builtins that one can > use in situations like the following. > >In the following example the file element name is > "solaris_media_locations". I have that same filename in the path and > content values. Is thei

[Puppet Users] element name as a variable

Greetings. I'm curious if their are any magic variable builtins that one can use in situations like the following. In the following example the file element name is "solaris_media_locations". I have that same filename in the path and content values. Is their any shorthand way to reuse

Re: [Puppet Users] Re: Downgrade package via yum

I was able to perform the downgrade with the patchprovided in the feature request #2866. Dec 23 10:28:00 puppetclient puppetd[17147]: (//Node[ puppetclient.example.com]/common/common::nagios/Package[nrpe_custom]/ensure) e

Re: [Puppet Users] puppetmaster 0.25.x factdir error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > I started testing puppet 0.25.x on my puppetmaster (RH 5.4 x64_64). I > first tried 0.25.1 from EPEL testing, then 0.25.2rc1. I am using > apache/mongrel with 10 ports. My puppetmaster configs are > in /srv/puppet not /var/puppet. When starting p

[Puppet Users] puppetmaster 0.25.x factdir error

Hello... I started testing puppet 0.25.x on my puppetmaster (RH 5.4 x64_64). I first tried 0.25.1 from EPEL testing, then 0.25.2rc1. I am using apache/mongrel with 10 ports. My puppetmaster configs are in /srv/puppet not /var/puppet. When starting puppetmaster I get the following errors: P

Re: [Puppet Users] Re: Downgrade package via yum

Hello, On 23.12.2009 19:45, R.I.Pienaar wrote: > hello, > > - "Silviu Paragina" wrote: > > >> AFAIK for apt/dpkg everything is fine as it is. But I might be wrong, >> it wouldn't be the first time my mind plays tricks on me. :-) >> Haven't used other package providers :"> >> > downgr

Re: [Puppet Users] puppet and sles 11 node

On 23.12.2009 01:13, Matthew Delves wrote: > Hey All, > I seem to be getting errors when running puppet under sles 11. > The first weird issue I'm seeing is that the node information isn't being > sent through to puppet correctly as It doesn't pick up the $operatingsystem > variable correctly and

Re: [Puppet Users] Re: Downgrade package via yum

hello, - "Silviu Paragina" wrote: > AFAIK for apt/dpkg everything is fine as it is. But I might be wrong, > it wouldn't be the first time my mind plays tricks on me. :-) > Haven't used other package providers :"> downgrades fail on debian too. -- You received this message because you are

Re: [Puppet Users] Re: Downgrade package via yum

On 22.12.2009 16:27, jcbollinger wrote: > Yes, I think you read too much into that. I also think that Puppet > could provide better support than it currently does. For instance, it > could perhaps add an "allow_downgrade" parameter to the package type > that, for the yum provider, would cause "--

Re: [Puppet Users] Re: Downgrade package via yum

Thanks all for the comments, I noticed that there is an open request for this: http://projects.reductivelabs.com/issues/2866 @John: both rpms are x86_64 Thanks On Tue, Dec 22, 2009 at 8:27 AM, jcbollinger wrote: > > > On Dec 22, 12:36 am, "Tony G." wrote: > > Running it manually I got: > > > >

[Puppet Users] ANNOUNCE: Puppet 0.25.2rc2 now available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Puppet 0.25.2 - code-named "Zoe" Due to a missing commit in RC1 the 0.25.2 Release Candidate 2 is now available for testing. This is the second release candidate for 0.25.2. The 0.25.2 release is a significant maintenance release (118 tickets closed

[Puppet Users] Re: custom fact and environment variable

The --factsync only works in test mode. And the flag factsync=true in puppet.conf has no effect I want to target a pool of machines that have an environment variable in common. The FAQ says : "Facter has a special types of facts that can be set from environment variables. Any environment variable

[Puppet Users] ANNOUNCE: Puppet 0.25.2rc1 now available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Puppet 0.25.2 - code-named "Zoe" The 0.25.2 Release Candidate 1 is now available for testing. This is the first release candidate for 0.25.2. The 0.25.2 release is a significant maintenance release (118 tickets closed!) in the 0.25.x branch. Thanks