[Puppet Users] Ruby for HP-UX 11.00

[Alex Harvey]

Hi all,

I have been trying to compile Ruby on HP-UX 11.00 but there are too many 
dependencies and no publicly available packages for these on such an old 
operating system and I'm forced to give up.  As a last resort - and it's a 
long shot indeed! - I am wondering if anyone out there has managed to 
compile ruby for HP-UX 11.00 and if so would they be willing to share their 
packages with me?

Best regards,
Alex

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/lbXWT2-Y2qEJ.
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] $certname in thias-puppet module

[Nitin Sharma]

Hi

I am using thias-puppet to manage puppet agent configuration. And it is 
being done in the following order:

class baseclass {
class puppet::agent {
variables...
}
}

node 'hostname1' {
include baseclass
}

This all above works well. 

But now I wish to include $certname which would be used by the 
template(puppetagent.erb) to generate puppet.conf which will now include 
*certname 
= nodename*. So what would be the changes required or how can value be 
passed so that $certname is taken from the nodename itself automatically.

node 'hostname1' {
$certname = 'hostname1'
include baseclass
}


Thanks,

N.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/HpVAbCuLWzAJ.
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: [Puppet Users] Re: hiera default values for a variable

[Peter Brown]

I worked out my problem.
I spelt hierarchy wrong in my hiera.yaml file...


On 7 December 2012 13:00, Peter Brown  wrote:

> On 7 December 2012 12:11, Ryan Cunningham  > wrote:
>
>> I'm actually having this exact same problem. In my hiera.yaml file I had
>> a hierarchy including two facts and then some strings derived from facter
>> facts.
>>
>
> Nice to know I am not completely insane.
>
> When I run puppet agent --test the hiera vars in files named for the
>> node's $fqdn, etc. aren't found, but if I puppet apply specifying my
>> site.pp manifest the variables contained in yaml files like $fqdn.yaml are
>> found and applied properly. I've gone as far as testing this with masters
>> running 3.0 and 2.7 but haven't seen any difference. For the sake of
>> clarity, the agent is being run on the master.
>>
>> I've tried several permutations of specifying a hierarchy including
>> quoting "%{fqdn}",  using no quotes, using the syntax for a top-level
>> variable ${::fqdn}, etc. Each time running hiera from the CLI works as
>> expected but the master can't be coerced to behave as expected.
>>
>> A bit of pastebin
>> puppet apply (which works): http://pastebin.com/E5iBtt2t
>> puppet agent --test (doesn't work): http://pastebin.com/GsA81Eyx
>
>
> I didn't try using apply but it does look very similar to my problem.
>
> On Thursday, 6 December 2012 18:31:09 UTC-5, Pete wrote:
>>>
>>> On Dec 7, 2012 12:08 AM, "jcbollinger"  wrote:
>>> >
>>> >
>>> >
>>> > On Tuesday, December 4, 2012 8:10:00 PM UTC-6, Pete wrote:
>>> >>
>>> >>
>>> >> One last question.
>>> >> I use a node level variable to specify the location of a node.
>>> >> I use this for setting variables specific to that location like
>>> different puppet master ip and nagios ip for the office and such.
>>> >> I want to use that variable in hiera for the same purpose.
>>> >> I have this in my hiera.yaml file.
>>> >>
>>> >> ---
>>> >> :hierachy:
>>> >>   - %{::clientcert}
>>> >>   - %{::environment}
>>> >>   - %{location}
>>> >>   - virtual_%{::is_virtual}
>>> >>   - common
>>> >> :backends: yaml
>>> >> :yaml:
>>> >>   :datadir: /etc/puppet/hieradata
>>> >>
>>> >> it gets data from the common.yaml file but is seems to not get
>>> anything from any of the other files.
>>> >> it's definitely using the datadir because thats where the common.yaml
>>> file is as well as the rest of the data files.
>>> >> Am I missing something?
>>> >>
>>> >
>>> > You are missing that node variables are not globals, and in fact don't
>>> even have qualified names.  I strongly suspect that that is why Hiera is
>>> not seeing them.
>>>
>>> That explains a why location isn't seen.
>>>
>>> I discovered later that hiera didn't seem to be using the facts either...
>>>
>>> Do I need to  do something else to allow hiera to see facts?
>>> I am assuming if I can use facts I will work out how to set location as
>>> a fact and just use it that way.
>>>
>>> As an aside, are ENC variables global?
>>> I have been tempted to use my freeipa server as an ENC using ldap.
>>>
>>> I have also been tempted to have a go at writing an ldap backend for
>>> hiera but that's another story...
>>>
>>> >
>>> > There are several potential workarounds, among them:
>>> > set the needed variable(s) at top-level, based on some sort of
>>> conditional
>>>
>>> I was under the impression that node level variables were top level
>>> variables but I am guessing I am wrong. Time to find some docs I guess. :)
>>>
>>> > push all the contents of your node blocks into classes, so that the
>>> variables in question become class variables
>>>
>>> I am going to assume from that class variables are global because they
>>> have qualified names?
>>>
>>> > instead of creating a separate hierarchy level with a data file for
>>> each value of (say) $environment,use a hash of hashes in the level below,
>>> with the $environment values as the outer hash keys
>>> >
>>> > Cheers,
>>> >
>>> > John
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> Groups "Puppet Users" group.
>>> > To view this discussion on the web visit https://groups.google.com/d/*
>>> *msg/puppet-users/-/**1Ajo2OXHPC4J
>>> .
>>> >
>>> > To post to this group, send email to puppet...@googlegroups.com.
>>> > To unsubscribe from this group, send email to puppet-users...@**
>>> googlegroups.com.
>>>
>>> > For more options, visit this group at http://groups.google.com/**
>>> group/puppet-users?hl=en
>>> .
>>>
>>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/puppet-users/-/Gjgrw66TRWkJ.
>>
>> 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 a

Re: [Puppet Users] Having puppetmaster checkout manifests from subversion

[Aaron Russo]

Thomas,

Have you looked at SVN's post-commit hooks?  I think it can do what you
want (though, I'm a git guy, so don't take my word for it).

Maybe something like rsync/scp your files over to the puppet masters in
your post-commit hook?

FWIW, we use git and the post-receive hooks to distribute the code to our
masters, then another post-receive hook on each master to handle setting up
our dynamic environments.  The code we run is here:

https://github.com/arusso23/git-hooks/blob/master/vcs/post-receive_distribute
https://github.com/arusso23/git-hooks/blob/master/puppet/post-receive_environments

Cheers,

Aaron Russo
IST Infrastructure Services, Unix Group
UC Berkeley


On Thu, Dec 6, 2012 at 3:55 PM, Peter Brown  wrote:

> Hi Thomas,
>
> About the only way I can see that working is if you setup a cron job on
> the puppet master that updates the svn and then do the remote puppet runs.
>
> Git may be a better way to achieve this.
>
> On 6 December 2012 21:19, Thomas Rasmussen wrote:
>
>> Hi
>>
>> I'm looking into a setup where we'd like the puppetmaster to
>> checkout/update all the manifests from subversion before it compiles the
>> manifests served to puppet nodes. I have been looking through the
>> documentation, and I can't seem to find a way of doing this.
>>
>> We'd like to be able to develop our manifests on our local computers and
>> when committed to subversion, force a puppet agent run and this run would
>> then use the newest manifests available. We are not using automated puppet
>> agent runs, so the problem of a commit suddenly breaking code without
>> noticing should not be a problem.
>>
>> The subversion server is not running on the same server as puppetmaster,
>> so any interaction from subversion to puppet is not possible.
>>
>> Any ideas how this problem can be solved?
>>
>> We are running puppet 2.7.18 on our master server.
>>
>> Regards
>> Thomas
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/puppet-users/-/eIWMOngAR90J.
>> 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.
>>
>
>  --
> 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.
>

-- 
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: need urgent help with including Ruby DSL class from puppet manifests

[Michael Field]

Error:

Must pass a parameter or all necessary values at /etc/puppet/ 
>

Is because when using Ruby DSL, assumed variables $name and $title are not 
passed to Puppet resource. 
For example, fix this:

 create_resource :'server::vhost', 'example',
  :ensure => 'present',
  etc...

To this 

 create_resource :'server::vhost',
  :name => 'example',
  :ensure => 'present',
  etc...

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/1T9MWeV0AUkJ.
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] Is there any ways to fetching custom fact after some resources setuped?

[cynipe]

I'm currently trying to create icinga module and the icinga-web and 
icinga-idoutils-libdbi-mysql from rpmforge
store the initial sql file in version numbered 
directory(/usr/share/doc/icinga-web-1.7.2/~~~).

So, I try to determine the version number from the yum info like as below, 
but that repository installed after my yum module gets work done.
Is there any ways to fetching custom fact after some resources setuped or 
any smart way to do this?

icinga_version.rb

def get_redhat_icinga_version
  version = Facter::Util::Resolution.exec('yum info icinga |grep 
"^Version"')
  if match = /^Version\s*:\s*(\d+\.\d+\.\d+)$/.match(version)
match[1]
  else
nil # should be fail?
  end
end

Facter.add("icinga_version") do
  setcode do
case Facter.value('osfamily')
  when 'RedHat'
get_redhat_icinga_version()
  else
nil # should be fail?
end
  end
end


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/5Fg1Xu6ghSUJ.
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: [Puppet Users] Re: hiera default values for a variable

[Peter Brown]

On 7 December 2012 12:11, Ryan Cunningham
wrote:

> I'm actually having this exact same problem. In my hiera.yaml file I had a
> hierarchy including two facts and then some strings derived from facter
> facts.
>

Nice to know I am not completely insane.

When I run puppet agent --test the hiera vars in files named for the node's
> $fqdn, etc. aren't found, but if I puppet apply specifying my site.pp
> manifest the variables contained in yaml files like $fqdn.yaml are found
> and applied properly. I've gone as far as testing this with masters running
> 3.0 and 2.7 but haven't seen any difference. For the sake of clarity, the
> agent is being run on the master.
>
> I've tried several permutations of specifying a hierarchy including
> quoting "%{fqdn}",  using no quotes, using the syntax for a top-level
> variable ${::fqdn}, etc. Each time running hiera from the CLI works as
> expected but the master can't be coerced to behave as expected.
>
> A bit of pastebin
> puppet apply (which works): http://pastebin.com/E5iBtt2t
> puppet agent --test (doesn't work): http://pastebin.com/GsA81Eyx


I didn't try using apply but it does look very similar to my problem.

On Thursday, 6 December 2012 18:31:09 UTC-5, Pete wrote:
>>
>> On Dec 7, 2012 12:08 AM, "jcbollinger"  wrote:
>> >
>> >
>> >
>> > On Tuesday, December 4, 2012 8:10:00 PM UTC-6, Pete wrote:
>> >>
>> >>
>> >> One last question.
>> >> I use a node level variable to specify the location of a node.
>> >> I use this for setting variables specific to that location like
>> different puppet master ip and nagios ip for the office and such.
>> >> I want to use that variable in hiera for the same purpose.
>> >> I have this in my hiera.yaml file.
>> >>
>> >> ---
>> >> :hierachy:
>> >>   - %{::clientcert}
>> >>   - %{::environment}
>> >>   - %{location}
>> >>   - virtual_%{::is_virtual}
>> >>   - common
>> >> :backends: yaml
>> >> :yaml:
>> >>   :datadir: /etc/puppet/hieradata
>> >>
>> >> it gets data from the common.yaml file but is seems to not get
>> anything from any of the other files.
>> >> it's definitely using the datadir because thats where the common.yaml
>> file is as well as the rest of the data files.
>> >> Am I missing something?
>> >>
>> >
>> > You are missing that node variables are not globals, and in fact don't
>> even have qualified names.  I strongly suspect that that is why Hiera is
>> not seeing them.
>>
>> That explains a why location isn't seen.
>>
>> I discovered later that hiera didn't seem to be using the facts either...
>>
>> Do I need to  do something else to allow hiera to see facts?
>> I am assuming if I can use facts I will work out how to set location as a
>> fact and just use it that way.
>>
>> As an aside, are ENC variables global?
>> I have been tempted to use my freeipa server as an ENC using ldap.
>>
>> I have also been tempted to have a go at writing an ldap backend for
>> hiera but that's another story...
>>
>> >
>> > There are several potential workarounds, among them:
>> > set the needed variable(s) at top-level, based on some sort of
>> conditional
>>
>> I was under the impression that node level variables were top level
>> variables but I am guessing I am wrong. Time to find some docs I guess. :)
>>
>> > push all the contents of your node blocks into classes, so that the
>> variables in question become class variables
>>
>> I am going to assume from that class variables are global because they
>> have qualified names?
>>
>> > instead of creating a separate hierarchy level with a data file for
>> each value of (say) $environment,use a hash of hashes in the level below,
>> with the $environment values as the outer hash keys
>> >
>> > Cheers,
>> >
>> > John
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups "Puppet Users" group.
>> > To view this discussion on the web visit https://groups.google.com/d/**
>> msg/puppet-users/-/**1Ajo2OXHPC4J
>> .
>> >
>> > To post to this group, send email to puppet...@googlegroups.com.
>> > To unsubscribe from this group, send email to puppet-users...@**
>> googlegroups.com.
>>
>> > For more options, visit this group at http://groups.google.com/**
>> group/puppet-users?hl=en
>> .
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/Gjgrw66TRWkJ.
>
> 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.
>

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

Re: [Puppet Users] "Could not render to pson"

[Peter Brown]

Is it possible to install the .so from a package and install it on the node
via a custom repository?
Managing shared libraries via puppet is screaming "Dependency Hell" in my
brain.


On 7 December 2012 01:24, Tom Owens  wrote:

> I found this error in syslog:
>
> Dec  3 16:43:15 0x0x0tuna puppet-agent[16790]:
> (/Stage[main]/Tuna/File[/u/net/profile/common/zoom.so.32/hpsw.so]/content)
> change from {md5}9913d05900c2fd8cd14ef2efec728457 to
> {md5}fe7db3112ffcea0f80fbda99b7da408c failed: Could not back up
> /u/net/profile/common/zoom.so.32/hpsw.so: Could not render to pson:
> "\340\215\203"
>
> As far as I can tell, the agent on this client box is trying to push
> /u/net/profile/common/zoom.so.32/hpsw.so into the filebucket on the puppet
> master and failing.  Since that backup fails, it won't receive the new
> file, which is a problem.
>
> Does anybody have any ideas on how to fix this?  Or at least a better idea
> how to diagnose why it's failing?  I do not have this issue with text
> files.  hpsw.so is a shared library in Linux.
>
> Thanks,
>
> Tom
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/re0nCcocQLQJ.
> 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.
>

-- 
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] Does facter 2.x need cfengine key support?

[John Warburton]

We were tripped up (we shot ourselves) on facter 1.6.x looking in a missing
NFS mounted /usr/local, which got me thinking - does facter 2.x really need
this?

https://github.com/puppetlabs/facter/blob/2.x/lib/facter/Cfkey.rb

John

-- 
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: [Puppet Users] Re: hiera default values for a variable

[Ryan Cunningham]

I'm actually having this exact same problem. In my hiera.yaml file I had a 
hierarchy including two facts and then some strings derived from facter 
facts.

When I run puppet agent --test the hiera vars in files named for the node's 
$fqdn, etc. aren't found, but if I puppet apply specifying my site.pp 
manifest the variables contained in yaml files like $fqdn.yaml are found 
and applied properly. I've gone as far as testing this with masters running 
3.0 and 2.7 but haven't seen any difference. For the sake of clarity, the 
agent is being run on the master.

I've tried several permutations of specifying a hierarchy including quoting 
"%{fqdn}",  using no quotes, using the syntax for a top-level variable 
${::fqdn}, etc. Each time running hiera from the CLI works as expected but 
the master can't be coerced to behave as expected.

A bit of pastebin
puppet apply (which works): http://pastebin.com/E5iBtt2t
puppet agent --test (doesn't work): http://pastebin.com/GsA81Eyx

On Thursday, 6 December 2012 18:31:09 UTC-5, Pete wrote:
>
> On Dec 7, 2012 12:08 AM, "jcbollinger" > 
> wrote:
> >
> >
> >
> > On Tuesday, December 4, 2012 8:10:00 PM UTC-6, Pete wrote:
> >>
> >>
> >> One last question.
> >> I use a node level variable to specify the location of a node.
> >> I use this for setting variables specific to that location like 
> different puppet master ip and nagios ip for the office and such.
> >> I want to use that variable in hiera for the same purpose.
> >> I have this in my hiera.yaml file.
> >>
> >> ---
> >> :hierachy:
> >>   - %{::clientcert}
> >>   - %{::environment}
> >>   - %{location}
> >>   - virtual_%{::is_virtual}
> >>   - common
> >> :backends: yaml
> >> :yaml:
> >>   :datadir: /etc/puppet/hieradata
> >>
> >> it gets data from the common.yaml file but is seems to not get anything 
> from any of the other files.
> >> it's definitely using the datadir because thats where the common.yaml 
> file is as well as the rest of the data files.
> >> Am I missing something?
> >>
> >
> > You are missing that node variables are not globals, and in fact don't 
> even have qualified names.  I strongly suspect that that is why Hiera is 
> not seeing them.
>
> That explains a why location isn't seen.
>
> I discovered later that hiera didn't seem to be using the facts either...
>
> Do I need to  do something else to allow hiera to see facts?
> I am assuming if I can use facts I will work out how to set location as a 
> fact and just use it that way.
>
> As an aside, are ENC variables global?
> I have been tempted to use my freeipa server as an ENC using ldap.
>
> I have also been tempted to have a go at writing an ldap backend for hiera 
> but that's another story...
>
> >
> > There are several potential workarounds, among them:
> > set the needed variable(s) at top-level, based on some sort of 
> conditional
>
> I was under the impression that node level variables were top level 
> variables but I am guessing I am wrong. Time to find some docs I guess. :)
>
> > push all the contents of your node blocks into classes, so that the 
> variables in question become class variables
>
> I am going to assume from that class variables are global because they 
> have qualified names?
>
> > instead of creating a separate hierarchy level with a data file for each 
> value of (say) $environment,use a hash of hashes in the level below, with 
> the $environment values as the outer hash keys
> >
> > Cheers,
> >
> > John
> >
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "Puppet Users" group.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msg/puppet-users/-/1Ajo2OXHPC4J.
> >
> > To post to this group, send email to puppet...@googlegroups.com
> .
> > To unsubscribe from this group, send email to 
> puppet-users...@googlegroups.com .
> > For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en.
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/Gjgrw66TRWkJ.
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: [Puppet Users] Re: puppetlabs-stdlib

[Russell Harrison]

On Thursday, August 30, 2012 6:01:43 PM UTC-4, Jeff McCune wrote:
>
> On Wed, Aug 29, 2012 at 12:20 PM, Douglas Garstang 
> 
> > wrote:
>
>> Really? From the function reference at:
>> http://docs.puppetlabs.com/references/latest/function.html
>>
>> Common ones seem to be create_resources, crit, defined, err,
>> extlookup, fail, file  and so on.
>
>
> I've fixed up the README, the function list in the doc is accurate for the 
> 3.0.0 release of stdlib.
>
> https://github.com/puppetlabs/puppetlabs-stdlib/blob/master/README.markdown
>
> Hope this helps,
> -Jeff
>

Would it be possible to get the 2.x branches of stdlib  updated as well as 
the forge entry.  They still don't reflect the actual contents of the 
module.

Thanks!
Russell

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/DtVXtLv-qDEJ.
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: Solaris processor count facts - bug or feature?

[Alex Harvey]

> I prefer the core count definition, but whatever it is, it should be 
> consistent between Linux and Solaris. 
>

Yes it certainly should be the same on all platforms - the question is if 
we change it who is going to be impacted and how can we manage the change?  
I believe the vast majority of Puppet users run linux so probably the 
Solaris code needs to be changed to conform to the linux rather than vice 
versa.  Unless lots of people think the linux fact is in fact the one 
that's 'wrong'?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/zZSTUqGrMRAJ.
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 ca list --all ERROR

[Rodolfo Pilas]

Following my previous message, do you think that the problem may be:

puppet master:
# puppet -V
3.0.1


puppet agent:
# puppet -V
0.25.4



I am testing a 3 version of master with my old deploy of agents.


---
Rodolfo Pilas
http://www.pilas.net
@ysidorito


El jueves, 6 diciembre 2012 a las 20:17 , Rodolfo Pilas escribió:

>  
> I have just installed a puppet master 3.0.1 under Debian 6.0 Squeeze.
>  
> As soon as I have installed puppet ca list --all works ok:
>  
> # puppet ca list --all
> + master1.domain  (SHA256) 
> AB:E1:EE:F5:9C:C7:F5:4F:37:76:A0:AB:93:60:9A:E9:69:58:12:A6:37:4E:29:CD:7C:B7:A1:07:80:3B:13:47
>  
> and I "puppet agent -t" from self mater1.domain and all worked ok.
>  
> The signature of the first node showed the certificate ( I had not seen this 
> at previous puppet versions).
>  
> # puppet ca list
>   agent1.domain  (MD5) F9:88:19:CF:82:84:AD:AE:F8:EC:0B:A3:04:E8:65:CC
>  
> # puppet ca sign agent1.domain
> Signed certificate request for agent1.domain
> Removing file Puppet::SSL::CertificateRequest agent1.domain at 
> '/var/lib/puppet/ssl/ca/requests/agent1.domain.pem'
> "-BEGIN 
> CERTIFICATE-\nMIID2TCCAcGgAwIBAgIBAzANBgkqhkiG9w0BAQsFADAoMSYwJAYDVQQDDB1QdXBw\nZXQgQ0E6IGN1dHRlci5yb290d2F5LmNvbTAeFw0xMjEyMDUyMTA2MTdaFw0xNzEy\nMDUyMTA2MTdaMB4xHDAaBgNVBAMME3Rlc3Rhd3Mucm9vdHdheS5jb20wgZ8wDQYJ\nKoZIhvcNAQEBBQADgY0AMIGJAoGBALggbp23HqJJvloI7WHH/EMMBj1W5JS3ctNn\n82Z66HTnwe6pbNw4l654nNJWsdxgIc6Bia23DoQejUmNrQ9nKN+63JK7lXQ//88k\nt19ixI6dMst/p1B7LGUBH1CE542/5MifU70+mOIdTfUzRTra9C0CuoyAh6LeLPNj\nu7Ov6d5jAgMBAAGjgZswgZgwDAYDVR0TAQH/BAIwADA3BglghkgBhvhCAQ0EKhYo\nUHVwcGV0IFJ1YnkvT3BlblNTTCBJbnRlcm5hbCBDZXJ0aWZpY2F0ZTAOBgNVHQ8B\nAf8EBAMCBaAwHQYDVR0OBBYEFEqIAYrvXq1/SB4SCcvqQ/xkbtFQMCAGA1UdJQEB\n/wQWMBQGCCsGAQUFBwMBBggrBgEFBQcDAjANBgkqhkiG9w0BAQsFAAOCAgEAdmDO\n5N4pq73lu6FLagVBwDFgw0813EHj1uBodkYtm7Lg3PaxLhTepn+gZF4vXQbLJTO3\njCpAxj3jsuiuGiYUscV2VGnRBVX5LrFdugg1R14XfSHmBSin8YhhkdKD8F8xP/Pl\ncNCRVOOl8+as+SjvtXpF/5EoAxsEi/aBRET/HM3EEPPEweeRuT5S6R1XSRSGUX7g\nQpSQw1D3M12FYYHTbWSA8kQX6B/KCgeHTzHsPPEbqtS2fsfFHzKYvLNzbf2IAvJL\ncAobf+IQkqgdNTehTftx/DWRkahIGN7Joaza19e45z8fIsqOROx74HaZTxZN7WDu\ns+7XrNt0kvsaVcW/ro/8chheIpeHXkrerPPcZA+ToPR3uN+O/OFkzxVbFMcCYwKr\nag1GgnWRH8TSMatMbqeqJjsUGaEDxaYG+7UigUEzvSvohalNC18yKHnX+hhB9QF0\nDr2fSvYbF8TCTEqckZC4O3JNYLqqV7n2dZ5eo/e/9d/MYzzfRUSyWtL05yCY6II5\nAuD3X1ZvzWUJUY1tVmqO7PyzV/LwBxB/25sfXVKyn0pffkP0WtkycgQtarRxLmLw\nibIbZg7QunADecve+nTk/3KMAwbBRRaoO2wVEdcm0BqLDvRGRNcR+P4kjz0eZ/FQ\nHLyd1G25T/bdL9RFkqXVXHMAQOf8PKT1jNdZBm0=\n-END
>  CERTIFICATE-\n"
>  
>  
> After that I was unable to list --all again:
>  
> # puppet ca list --all
> Error: The certificate retrieved from the master does not match the agent's 
> private key.
> Certificate fingerprint: 
> 47:86:DF:83:53:A3:14:AB:C6:9B:B6:2A:30:A3:61:DB:DC:17:7A:40:CA:AC:33:12:BB:67:07:9F:2A:77:DA:CF
> To fix this, remove the certificate from both the master and the agent and 
> then start a puppet run, which will automatically regenerate a certficate.
> On the master:
>   puppet cert clean master1.domain
> On the agent:
>   rm -f /var/lib/puppet/ssl/certs/master1.domain.pem
>   puppet agent -t
>  
> I have complete remove /var/lib/puppet/ssl and recreate all certificates with 
> THE SAME steps and error.  
>  
> Suggestions?
>  
> ---
> Rodolfo Pilas
> http://www.pilas.net
> @ysidorito
>  

-- 
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: [Puppet Users] Having puppetmaster checkout manifests from subversion

[Peter Brown]

Hi Thomas,

About the only way I can see that working is if you setup a cron job on the
puppet master that updates the svn and then do the remote puppet runs.

Git may be a better way to achieve this.

On 6 December 2012 21:19, Thomas Rasmussen wrote:

> Hi
>
> I'm looking into a setup where we'd like the puppetmaster to
> checkout/update all the manifests from subversion before it compiles the
> manifests served to puppet nodes. I have been looking through the
> documentation, and I can't seem to find a way of doing this.
>
> We'd like to be able to develop our manifests on our local computers and
> when committed to subversion, force a puppet agent run and this run would
> then use the newest manifests available. We are not using automated puppet
> agent runs, so the problem of a commit suddenly breaking code without
> noticing should not be a problem.
>
> The subversion server is not running on the same server as puppetmaster,
> so any interaction from subversion to puppet is not possible.
>
> Any ideas how this problem can be solved?
>
> We are running puppet 2.7.18 on our master server.
>
> Regards
> Thomas
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/eIWMOngAR90J.
> 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.
>

-- 
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: [Puppet Users] Re: hiera default values for a variable

[Peter Brown]

On Dec 7, 2012 12:08 AM, "jcbollinger"  wrote:
>
>
>
> On Tuesday, December 4, 2012 8:10:00 PM UTC-6, Pete wrote:
>>
>>
>> One last question.
>> I use a node level variable to specify the location of a node.
>> I use this for setting variables specific to that location like
different puppet master ip and nagios ip for the office and such.
>> I want to use that variable in hiera for the same purpose.
>> I have this in my hiera.yaml file.
>>
>> ---
>> :hierachy:
>>   - %{::clientcert}
>>   - %{::environment}
>>   - %{location}
>>   - virtual_%{::is_virtual}
>>   - common
>> :backends: yaml
>> :yaml:
>>   :datadir: /etc/puppet/hieradata
>>
>> it gets data from the common.yaml file but is seems to not get anything
from any of the other files.
>> it's definitely using the datadir because thats where the common.yaml
file is as well as the rest of the data files.
>> Am I missing something?
>>
>
> You are missing that node variables are not globals, and in fact don't
even have qualified names.  I strongly suspect that that is why Hiera is
not seeing them.

That explains a why location isn't seen.

I discovered later that hiera didn't seem to be using the facts either...

Do I need to  do something else to allow hiera to see facts?
I am assuming if I can use facts I will work out how to set location as a
fact and just use it that way.

As an aside, are ENC variables global?
I have been tempted to use my freeipa server as an ENC using ldap.

I have also been tempted to have a go at writing an ldap backend for hiera
but that's another story...

>
> There are several potential workarounds, among them:
> set the needed variable(s) at top-level, based on some sort of conditional

I was under the impression that node level variables were top level
variables but I am guessing I am wrong. Time to find some docs I guess. :)

> push all the contents of your node blocks into classes, so that the
variables in question become class variables

I am going to assume from that class variables are global because they have
qualified names?

> instead of creating a separate hierarchy level with a data file for each
value of (say) $environment,use a hash of hashes in the level below, with
the $environment values as the outer hash keys
>
> Cheers,
>
> John
>
> --
> You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
> To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/1Ajo2OXHPC4J.
>
> 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.

-- 
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: [Puppet Users] custom define type for array with 'case' argument pass to it

[Jakov Sosic]

On 12/07/2012 12:20 AM, iamauser wrote:

Thanks, but we are still running EL5. Do you have rpm available for this ?


Yeah it's easy just replace el6 with el5 ;)

http://ftp.srce.hr/srce-redhat/base/el5/x86_64/rubygem-puppet-lint-0.1.13-1.el5.srce.noarch.rpm


Although I don't have all packages build for both versions (el5 & el6) 
and all architectures (x86_64 & i386), I sure try my best. When I get 
Koji up and working it should be easier to provide all the packages...


--
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: [Puppet Users] custom define type for array with 'case' argument pass to it

[iamauser]

Thanks, but we are still running EL5. Do you have rpm available for this ?



On Thursday, December 6, 2012 5:12:33 PM UTC-6, Jakov Sosic wrote:
>
> On 12/06/2012 08:00 PM, iamauser wrote: 
>
> >> Are you using RHEL od RHEL derivative? If yes, I can provide you RPM. 
> > 
> > Yes, I am. That will be a lot helpful. Thanks a lot. 
>
>
> http://ftp.srce.hr/srce-redhat/base/el6/x86_64/rubygem-puppet-lint-0.1.13-1.el6.srce.noarch.rpm
>  
>
>
>
> -- 
> Jakov Sosic 
> www.srce.unizg.hr 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/iCGkEYWrghcJ.
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: [Puppet Users] custom define type for array with 'case' argument pass to it

[Jakov Sosic]

On 12/06/2012 08:00 PM, iamauser wrote:


Are you using RHEL od RHEL derivative? If yes, I can provide you RPM.


Yes, I am. That will be a lot helpful. Thanks a lot.


http://ftp.srce.hr/srce-redhat/base/el6/x86_64/rubygem-puppet-lint-0.1.13-1.el6.srce.noarch.rpm



--
Jakov Sosic
www.srce.unizg.hr

--
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] puppet ca list --all ERROR

[Rodolfo Pilas]

I have just installed a puppet master 3.0.1 under Debian 6.0 Squeeze.

As soon as I have installed puppet ca list --all works ok:

# puppet ca list --all
+ master1.domain  (SHA256) 
AB:E1:EE:F5:9C:C7:F5:4F:37:76:A0:AB:93:60:9A:E9:69:58:12:A6:37:4E:29:CD:7C:B7:A1:07:80:3B:13:47

and I "puppet agent -t" from self mater1.domain and all worked ok.

The signature of the first node showed the certificate ( I had not seen this at 
previous puppet versions).

# puppet ca list
  agent1.domain  (MD5) F9:88:19:CF:82:84:AD:AE:F8:EC:0B:A3:04:E8:65:CC

# puppet ca sign agent1.domain
Signed certificate request for agent1.domain
Removing file Puppet::SSL::CertificateRequest agent1.domain at 
'/var/lib/puppet/ssl/ca/requests/agent1.domain.pem'
"-BEGIN 
CERTIFICATE-\nMIID2TCCAcGgAwIBAgIBAzANBgkqhkiG9w0BAQsFADAoMSYwJAYDVQQDDB1QdXBw\nZXQgQ0E6IGN1dHRlci5yb290d2F5LmNvbTAeFw0xMjEyMDUyMTA2MTdaFw0xNzEy\nMDUyMTA2MTdaMB4xHDAaBgNVBAMME3Rlc3Rhd3Mucm9vdHdheS5jb20wgZ8wDQYJ\nKoZIhvcNAQEBBQADgY0AMIGJAoGBALggbp23HqJJvloI7WHH/EMMBj1W5JS3ctNn\n82Z66HTnwe6pbNw4l654nNJWsdxgIc6Bia23DoQejUmNrQ9nKN+63JK7lXQ//88k\nt19ixI6dMst/p1B7LGUBH1CE542/5MifU70+mOIdTfUzRTra9C0CuoyAh6LeLPNj\nu7Ov6d5jAgMBAAGjgZswgZgwDAYDVR0TAQH/BAIwADA3BglghkgBhvhCAQ0EKhYo\nUHVwcGV0IFJ1YnkvT3BlblNTTCBJbnRlcm5hbCBDZXJ0aWZpY2F0ZTAOBgNVHQ8B\nAf8EBAMCBaAwHQYDVR0OBBYEFEqIAYrvXq1/SB4SCcvqQ/xkbtFQMCAGA1UdJQEB\n/wQWMBQGCCsGAQUFBwMBBggrBgEFBQcDAjANBgkqhkiG9w0BAQsFAAOCAgEAdmDO\n5N4pq73lu6FLagVBwDFgw0813EHj1uBodkYtm7Lg3PaxLhTepn+gZF4vXQbLJTO3\njCpAxj3jsuiuGiYUscV2VGnRBVX5LrFdugg1R14XfSHmBSin8YhhkdKD8F8xP/Pl\ncNCRVOOl8+as+SjvtXpF/5EoAxsEi/aBRET/HM3EEPPEweeRuT5S6R1XSRSGUX7g\nQpSQw1D3M12FYYHTbWSA8kQX6B/KCgeHTzHsPPEbqtS2fsfFHzKYvLNzbf2IAvJL\ncAobf+IQkqgdNTehTftx/DWRkahIGN7Joaza19e45z8f
IsqOROx74HaZTxZN7WDu\ns+7XrNt0kvsaVcW/ro/8chheIpeHXkrerPPcZA+ToPR3uN+O/OFkzxVbFMcCYwKr\nag1GgnWRH8TSMatMbqeqJjsUGaEDxaYG+7UigUEzvSvohalNC18yKHnX+hhB9QF0\nDr2fSvYbF8TCTEqckZC4O3JNYLqqV7n2dZ5eo/e/9d/MYzzfRUSyWtL05yCY6II5\nAuD3X1ZvzWUJUY1tVmqO7PyzV/LwBxB/25sfXVKyn0pffkP0WtkycgQtarRxLmLw\nibIbZg7QunADecve+nTk/3KMAwbBRRaoO2wVEdcm0BqLDvRGRNcR+P4kjz0eZ/FQ\nHLyd1G25T/bdL9RFkqXVXHMAQOf8PKT1jNdZBm0=\n-END
 CERTIFICATE-\n"


After that I was unable to list --all again:

# puppet ca list --all
Error: The certificate retrieved from the master does not match the agent's 
private key.
Certificate fingerprint: 
47:86:DF:83:53:A3:14:AB:C6:9B:B6:2A:30:A3:61:DB:DC:17:7A:40:CA:AC:33:12:BB:67:07:9F:2A:77:DA:CF
To fix this, remove the certificate from both the master and the agent and then 
start a puppet run, which will automatically regenerate a certficate.
On the master:
  puppet cert clean master1.domain
On the agent:
  rm -f /var/lib/puppet/ssl/certs/master1.domain.pem
  puppet agent -t

I have complete remove /var/lib/puppet/ssl and recreate all certificates with 
THE SAME steps and error. 

Suggestions?

---
Rodolfo Pilas
http://www.pilas.net
@ysidorito

-- 
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: [Puppet Users] Puppet report aggregation

[John Warburton]

On 6 December 2012 20:29, Luke Bigum  wrote:

> I haven't looked at The Foreman in a while but in my mind it's more like
> Puppet Dashboard - correct me if I'm wrong. What I'm aiming for is a tool
> that can aid change / release management where we run Puppet --noop across
> the estate, gather all the reports, then summarise what changes will be
> applied (resolv.conf changes on all hosts, fstab changes on 20 hosts,
> service X refreshes on Y hosts).
>
> I don't really want to be searching for explicit resources changing across
> hosts, it's the resources I don't know about that worry me ;-) Is the
> foreman worth a look in this case?
>
> Luke, we use the puppet dashboard which aggregates all the reports and
then lets us suck down a CSV ("Export nodes as CSV" on front page) which
contains a status of all resources on all machine reporting. We run puppet
in noop all the time, so need similar reports you are requesting. It is
just a matter of slicing & dicing the csv to get what you want

% wget http://localhost:3000/nodes.csv

# Omit all the resources in sync
% egrep -v ',0,0,false,false' nodes.csv | wc -l
146057
% wc -l nodes.csv
612762 nodes.csv
% echo "scale=2; 146057*100/612762" | bc
23.83

Almost 24% of all resources (600K mind you) out of sync

We can check our security module compliance:
% egrep -v ',0,0,false,false' nodes.csv | grep modules/security|wc -l
6992
% grep modules/security nodes.csv|wc -l
30433
% echo "scale=2; 6992*100/130433" | bc
5.36

5% *resources* out of sync from our security module. Not bad. We can dice
it to give percentages of hostnames too

Top 10 resources out of sync:
% egrep -v ',0,0,false,false' nodes.csv | awk -F, '{print $7, $8}' | sort |
uniq -c | sort -rn | head
898 File /etc/sudoers
801 File /opt/local/sbin/run-puppet.sh
792 File ntp.conf
754 File vposend-test.pl
752 File /opt/local/sbin/puppet-register.sh
751 File /var/puppet/etc/local_puppet_info
745 File /etc/default/passwd
711 File /local/apps
710 File /etc/default/nfs
705 File /etc/ssh/sshd_config

John

-- 
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: daemontools service provider doesn't support "restart" parameter?

[Amos Shapira]

I copied the question to issue http://projects.puppetlabs.com/issues/18021 
since I think I stumbled on a bug.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/8Wk9pD2EZ7gJ.
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: [Puppet Users] Re: gem error installing rack

[DJames]

Thanks i found this.

http://www.rubyenterpriseedition.com/download.html

On Thursday, December 6, 2012 1:59:31 PM UTC-5, Matthaus Litteken wrote:
>
> If you go to https://rubygems.org/gems/rack there is a download link 
> to download the gem as well as links to previous versions. Once you 
> have the gem locally, you can run `gem install 
> /path/to/rack-1.2.3.gem` to install the gem. 
>
> HTH 
>
> On Thu, Dec 6, 2012 at 10:39 AM, DJames > 
> wrote: 
> > how can i manually install these then? 
> > 
> > 
> > On Thursday, December 6, 2012 9:32:18 AM UTC-5, DJames wrote: 
> >> 
> >> # gem install rack 
> >> 
> >> 
> >> ERROR:  http://rubygems.org/ does not appear to be a repository 
> >> ERROR:  Could not find a valid gem 'rack' (>= 0) in any repository 
> >> 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "Puppet Users" group. 
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msg/puppet-users/-/JwDDwnu5cuwJ. 
> > 
> > To post to this group, send email to 
> > puppet...@googlegroups.com. 
>
> > To unsubscribe from this group, send email to 
> > puppet-users...@googlegroups.com . 
> > For more options, visit this group at 
> > http://groups.google.com/group/puppet-users?hl=en. 
>
>
>
> -- 
> Matthaus Owens 
> Release Manager, Puppet Labs 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/CVOjSjbpXMAJ.
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: [Puppet Users] Puppet Agent on Windows and file paths 32 or 64 Bit

[ad]

Hey Oliver,

I finally got around to working on this today, and discovered I fixed it 
long ago and completely forgot to push the change to github. oops :)

Looks like I took a different approach.

https://github.com/adenning/winfacts/blob/master/lib/facter/os_architecture.rb

I only run Puppet on Windows 7 and XP nodes (yeah that's right), but I can 
confirm this handles 32-bit OS on x64 and accounts for some variations I 
ran into with various embedded Windows.

Adam

On Friday, November 30, 2012 9:27:05 AM UTC-6, r0k5t4r wrote:
>
> Hi Adam,
>
> The class 
> Win32_OperatingSystemexists
>  on Vista and above. For older systems you can use 
> Win32_ComputerSystem.
>  
> I found this information here:
>
>
> http://www.adminarsenal.com/admin-arsenal-blog/bid/19689/Determining-OS-Architecture
>
> The following minor change did the trick for windows 2003.
>
> Facter.add(:os_architecture) do
>   confine :operatingsystem => :windows
>   setcode do
> result = ''
> require 'win32ole'
> wmi = WIN32OLE.connect('winmgmts://./root/CIMV2')
> winver = Facter.value('kernelmajversion')
> case winver
> when /5.2|5.1|5.0/
> query = wmi.ExecQuery('select SystemType from 
> Win32_ComputerSystem')
> query.each do |os|
> result = os.SystemType
> break
> end
> if result == "X86-based PC"
> result = "32-bit"
> else
> result = "64-bit"
> end
> result
> else
> query = wmi.ExecQuery('select OSArchitecture from 
> Win32_OperatingSystem')
> query.each do |os|
> result = os.OSArchitecture
> break
> end
> result
> end
>   end
> end
>
> Have a nice weekend.
>
>
> On Friday, November 30, 2012 2:16:11 PM UTC+1, r0k5t4r wrote:
>>
>> Hi Adam,
>>
>> thanks a lot. I have successfully implemented your or_architecture fact 
>> on our machines. But it looks like it is not workung under Windows 2003 
>> 32Bit.I have to check this...
>>
>> Regards,
>> Oli
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/dwLVirsRsswJ.
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: [Puppet Users] Catalog into something "human readable"

[Deepak Giridharagopal]

On Thu, Dec 6, 2012 at 4:50 AM, ollies...@googlemail.com <
paul.seym...@barcap.com> wrote:

> Hello,
>
> Is there anyway to parse a catalog generated with something like:-
>
>  puppet master --compile  > .cat
>
> That looks vaguely human readable. I have tried the "puppet catalog print"
> face but cannot seem to get it to parse for some reason
>
> # puppet catalog print --catalog /var/tmp/.cat
> err: undefined method `preferred_run_mode=' for
> #
> err: Try 'puppet help catalog print' for usage
>
> This is on a 2.7.16 master BTW
>
> Or indeed anything in the PuppetDB that can pull this and parse it ?
>

On the PuppetDB side, there are two ways off the top of my head (newer
versions will pretty-print the output, making it more human-readable JSON).
These assume you're on the same machine PuppetDB is on:

* you can issue a query for all resources for , like so:

curl -G -H "Accept: application/json" 'http://localhost:8080/resources'
--data-urlencode 'query=["=", ["node", "name"], ""]'

Note that you won't get dependency or containment edges here, but you will
get all parameters for all resources for the host. This is much easier with
the changes in the PuppetDB master branch (hasn't been released yet, but
figured i'd mention it), which lets you just hit
/v2/nodes//resources to get all of them without requiring a query.

* you can use the experimental "catalog" endpoint:

curl -v -H 'Accept: application/json' '
http://localhost:8080/experimental/catalog/'

That will give you all dependency edges, all containment edges, and all
resources + parameters.

deepak

-- 
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: [Puppet Users] custom define type for array with 'case' argument pass to it

[iamauser]

On Thursday, December 6, 2012 11:20:08 AM UTC-6, Jakov Sosic wrote:

> On 12/06/2012 05:51 PM, iamauser wrote: 
> > Hi, 
> > 
> > I had tried installing puppet-lint sometime ago, and tried this again as 
> > you wrote, but I get a bunch of buffer overflow (see below). I have 
> > reported an issue with rodjek's github and let's see if I get an answer. 
> > Any suggestion from this forum will certainly help. 
>
> Are you using RHEL od RHEL derivative? If yes, I can provide you RPM. 
>
>
Yes, I am. That will be a lot helpful. Thanks a lot.


 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/zBVtiSmWvHYJ.
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: [Puppet Users] Re: gem error installing rack

[Matthaus Owens]

If you go to https://rubygems.org/gems/rack there is a download link
to download the gem as well as links to previous versions. Once you
have the gem locally, you can run `gem install
/path/to/rack-1.2.3.gem` to install the gem.

HTH

On Thu, Dec 6, 2012 at 10:39 AM, DJames  wrote:
> how can i manually install these then?
>
>
> On Thursday, December 6, 2012 9:32:18 AM UTC-5, DJames wrote:
>>
>> # gem install rack
>>
>>
>> ERROR:  http://rubygems.org/ does not appear to be a repository
>> ERROR:  Could not find a valid gem 'rack' (>= 0) in any repository
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/JwDDwnu5cuwJ.
>
> 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.



-- 
Matthaus Owens
Release Manager, Puppet Labs

-- 
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: [Puppet Users] Puppet report aggregation

[Ohad Levy]

On Thu, Dec 6, 2012 at 11:29 AM, Luke Bigum  wrote:

> On Wednesday, December 5, 2012 12:50:43 PM UTC, ohad wrote:
>
>> You could use foreman for that? filtering the hosts via search should
>> allow you to find the exact resources you are looking for?
>>
>> Ohad
>>
>>
> Hi Ohad,
>
> I haven't looked at The Foreman in a while but in my mind it's more like
> Puppet Dashboard - correct me if I'm wrong. What I'm aiming for is a tool
> that can aid change / release management where we run Puppet --noop across
> the estate, gather all the reports, then summarise what changes will be
> applied (resolv.conf changes on all hosts, fstab changes on 20 hosts,
> service X refreshes on Y hosts).
>
>
You should be able to setup a search term that would match your requirement
it might be best to use the API for that (http://bit.ly/Uq033I), since you
would get all of your reports already parsed and you could cross reference
the info with a puppet env, fact etc.

Ohad

> I don't really want to be searching for explicit resources changing across
> hosts, it's the resources I don't know about that worry me ;-) Is the
> foreman worth a look in this case?
>
> -Luke
>
>
>>
>> On Tue, Dec 4, 2012 at 11:00 PM, Luke Bigum  wrote:
>>
>>> Hi all,
>>>
>>> Can anyone recommend any tools for Puppet report aggregation? I'm
>>> interested in something that can take a given set of Puppet reports and
>>> summarise to me what resources have changed across all hosts.
>>>
>>> If nothing exists I will look to write one myself. In that case, is
>>> Puppet report format 3 valid for Puppet 3.0?
>>>
>>> http://projects.puppetlabs.**com/projects/puppet/wiki/**Report_Format_3
>>>
>>> Thanks,
>>>
>>> -Luke
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Puppet Users" group.
>>> To view this discussion on the web visit https://groups.google.com/d/**
>>> msg/puppet-users/-/**Fcx6zByYGPQJ
>>> .
>>> To post to this group, send email to puppet...@googlegroups.com.
>>> To unsubscribe from this group, send email to puppet-users...@**
>>> googlegroups.com.
>>>
>>> For more options, visit this group at http://groups.google.com/**
>>> group/puppet-users?hl=en
>>> .
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/zk_ospPVmYkJ.
>
> 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.
>

-- 
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: gem error installing rack

[DJames]

how can i manually install these then?

On Thursday, December 6, 2012 9:32:18 AM UTC-5, DJames wrote:
>
> # gem install rack
>
>
> ERROR:  http://rubygems.org/ does not appear to be a repository
> ERROR:  Could not find a valid gem 'rack' (>= 0) in any repository
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/JwDDwnu5cuwJ.
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: [Puppet Users] Proper way to call variables from a parent class to a child class

[Gary Larizza]

Hi there,

This is an example of dynamic scoping, and there is a good help document
here --> http://docs.puppetlabs.com/guides/scope_and_puppet.html  That page
should describe what you're seeing and how to clarify it.


On Thu, Dec 6, 2012 at 10:17 AM, phundisk wrote:

> I currently have a child class of a parent one.  The parent defines
> some variable that I need to use in the child class.  I am also using
> gepetto.  Gepetto is complaining about the syntax of the child variable.
>  It is saying that "$parentVar" should be "$::parentVar" however, when
> changing to what Gepetto wants to use this breaks my classes.  Does anyone
> know the proper method of doing this?  Currently the "$parentVar" method
> below works fine, its just causing an error with Gepetto.
>
> class test::parent {
> $parentVar = "abc"
> include test::child
> }
>
> class test::child {
> notify { "The variable is: $parentVar":}
> }
>
> __**___
> This email and any files transmitted with it are confidential and intended
> solely for the addressee.  If you received this email in error, please do
> not disclose the contents to anyone; kindly notify the sender by return
> email and delete this email and any attachments from your system.
>
> © 2011 Currensee Inc. is a member of the National Futures Association
> (NFA) Member ID 0403251 | Over the counter retail foreign currency (Forex)
> trading may involve significant risk of loss. It is not suitable for all
> investors and you should make sure you understand the risks involved before
> trading and seek independent advice if necessary. Performance, strategies
> and charts shown are not necessarily predictive of any particular result
> and past performance is no indication of future results. Investor returns
> may vary from Trade Leader returns based on slippage, fees, broker spreads,
> volatility or other market conditions.
>
> Currensee Inc | 54 Canal St 4th Floor | Boston, MA 02114 | +1.617.624.3824
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/0h82g6XX0FoJ.
> 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.
>



-- 

Gary Larizza
Professional Services Engineer
Puppet Labs

-- 
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] Proper way to call variables from a parent class to a child class

[phundisk]

I currently have a child class of a parent one.  The parent defines 
some variable that I need to use in the child class.  I am also using 
gepetto.  Gepetto is complaining about the syntax of the child variable. 
 It is saying that "$parentVar" should be "$::parentVar" however, when 
changing to what Gepetto wants to use this breaks my classes.  Does anyone 
know the proper method of doing this?  Currently the "$parentVar" method 
below works fine, its just causing an error with Gepetto.

class test::parent {
$parentVar = "abc"
include test::child 
}

class test::child {
notify { "The variable is: $parentVar":}
}

-- 
_
This email and any files transmitted with it are confidential and intended 
solely for the addressee.  If you received this email in error, please do 
not disclose the contents to anyone; kindly notify the sender by return 
email and delete this email and any attachments from your system.

© 2011 Currensee Inc. is a member of the National Futures Association (NFA) 
Member ID 0403251 | Over the counter retail foreign currency (Forex) 
trading may involve significant risk of loss. It is not suitable for all 
investors and you should make sure you understand the risks involved before 
trading and seek independent advice if necessary. Performance, strategies 
and charts shown are not necessarily predictive of any particular result 
and past performance is no indication of future results. Investor returns 
may vary from Trade Leader returns based on slippage, fees, broker spreads, 
volatility or other market conditions.

Currensee Inc | 54 Canal St 4th Floor | Boston, MA 02114 | +1.617.624.3824

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/0h82g6XX0FoJ.
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: [Puppet Users] Catalog into something "human readable"

[R.I.Pienaar]

- Original Message -
> From: "ollies...@googlemail.com" 
> To: puppet-users@googlegroups.com
> Sent: Thursday, December 6, 2012 1:50:56 PM
> Subject: [Puppet Users] Catalog into something "human readable"
> 
> Hello,
> 
> Is there anyway to parse a catalog generated with something like:-
> 
> puppet master --compile  > .cat
> 
> That looks vaguely human readable. I have tried the "puppet catalog
> print" face but cannot seem to get it to parse for some reason
> 
> # puppet catalog print --catalog /var/tmp/.cat
> err: undefined method `preferred_run_mode=' for
> #
> err: Try 'puppet help catalog print' for usage
> 
> This is on a 2.7.16 master BTW


the print face needs puppet 3.

you can try an older version that was just a script @ 
https://github.com/ripienaar/puppet-parselocalconfig/tree/5430c173d373052f0cdf764cb30a590ec3e729d1

-- 
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: [Puppet Users] How to group hosts?

[Joe Topjian]

Hello,

I do this using facter-dot-d.

For my environment, I group by physical location, so I have a text file
"/etc/facter/facts.d/location.txt" with contents of:

location=foobar

Then "facter -p location" will output the location of the node.

Then throughout my manifests, I use the meta-parameter "tag" to tag various
resources by location:

tag => $::location

You can also use hiera in this way by having one of your hiera hierarchies
be %{location}.

Note that "location" is just arbitrary - you can use something like "role"
instead:

/etc/facter/facts.d/role.txt:
role=storage_nodes

Hope that helps,
Joe


On Thu, Dec 6, 2012 at 10:27 AM, Jakov Sosic  wrote:

> Hi.
>
> I'm currently using hiera in a very rudimentary way, using only perhost
> and common.
>
> Now, I'm trying to group my hosts a little bit, so for example web
> servers could have their own yaml with data. Problem is I don't have an
> idea how to group hosts? How can I say to puppet that for example hosts:
>
> storage01
> storage02
> storage03
> storage04
>
> belong to group storage_nodes, and
>
> web01
> web02
>
> belong to group web_nodes?
>
>
> How do you do that?
>
>
> Thank you
>
> --
> 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.
>
>


-- 
Joe Topjian
Systems Administrator
Cybera Inc.

www.cybera.ca

Cybera is a not-for-profit organization that works to spur and support
innovation, for the economic benefit of Alberta, through the use
of cyberinfrastructure.

-- 
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: [Puppet Users] How to group hosts?

[Stefan Goethals]

Hi,

You could use facter-dot-d to set a fact on those servers specifying the
name of a storagegroup or a webcluster
and then use that fact in your hiera hierarchy

so you could have
/etc/facter/facts.d/servertype.yaml with content

servertype: storage_node   ( or web_node )

Have in /etc/puppet/hiera.yaml

:hierarchy:
  - %{servertype}

and in your hieradata dir a file storage_node.yaml and web_node.yaml with
the settings you like.

Another way is to set the param servertype via an ENC and use the same
hierarchy and files.


Regards,

Stefan Goethals


On Thu, Dec 6, 2012 at 6:27 PM, Jakov Sosic  wrote:

> Hi.
>
> I'm currently using hiera in a very rudimentary way, using only perhost
> and common.
>
> Now, I'm trying to group my hosts a little bit, so for example web
> servers could have their own yaml with data. Problem is I don't have an
> idea how to group hosts? How can I say to puppet that for example hosts:
>
> storage01
> storage02
> storage03
> storage04
>
> belong to group storage_nodes, and
>
> web01
> web02
>
> belong to group web_nodes?
>
>
> How do you do that?
>
>
> Thank you
>
> --
> 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.
>
>

-- 
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: [Puppet Users] pasenger does not start puppet master under nginx

[Craig White]

On Dec 6, 2012, at 3:17 AM, Anadi Misra wrote:

> On the server
> 
> [root@bangvmpllDA02 logs]# ruby -v
> ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
> 
> [root@bangvmpllDA02 logs]# puppet --version
> 3.0.1
> 
> and
> 
> [root@bangvmpllDA02 logs]# service nginx configtest
> nginx: the configuration file /apps/nginx/nginx.conf syntax is ok
> nginx: configuration file /apps/nginx/nginx.conf test is successful
> 
> [root@bangvmpllDA02 logs]# service nginx status
> nginx (pid 25923 25921 25920 25917 25908) is running...
> [root@bangvmpllDA02 logs]# 
> 
> however none of my agents are able to connect to the master, they all fail 
> with errors like so
> 
> [amisr1@blramisr195602 ~]$ puppet agent --test --verbose --server 
> bangvmpllda02.X.com
> Info: Creating a new SSL certificate request for blramisr195602.X.com
> Info: Certificate Request fingerprint (SHA256): 
> 26:EB:08:1F:82:32:E4:03:7A:64:8E:30:A3:99:93:26:E6:66:B9:B0:49:B6:08:F9:67:CA:1B:0C:00:B9:1D:41
> Error: Could not request certificate: Error 405 on SERVER: 
> 405 Not Allowed
> 
> 405 Not Allowed
> nginx
> 
> 
> 
> Exiting; failed to retrieve certificate and waitforcert is disabled
> 
> when I check logs on puppet master
> 
> [root@bangvmpllDA02 logs]# tail puppet_access.log
> [05/Dec/2012:17:45:18 +0530] "GET /production/certificate/ca? HTTP/1.1" 404 
> 162 "-" "Ruby"
> [05/Dec/2012:18:32:23 +0530] "PUT 
> /production/certificate_request/sl63anadi.X.com HTTP/1.1" 405 166 "-" "-"
> [05/Dec/2012:18:33:33 +0530] "GET 
> /production/certificate/sl63anadi.X.com? HTTP/1.1" 404 162 "-" "-"
> [05/Dec/2012:18:33:33 +0530] "GET 
> /production/certificate_request/sl63anadi.X.com? HTTP/1.1" 404 162 "-" "-"
> [05/Dec/2012:18:33:33 +0530] "PUT 
> /production/certificate_request/sl63anadi.X.com HTTP/1.1" 405 166 "-" "-"
> 
> and the error logs show that nginx is not really able to process the request 
> well
> 
> 2012/12/05 18:33:33 [error] 25920#0: *23 open() 
> "/etc/puppet/rack/public/production/certificate/sl63anadi.X.com" failed 
> (2: No such file or directory), client: 10.209.47.26, server: , request: "GET 
> /production/certificate/sl63anadi.X.com? HTTP/1.1", host: 
> "bangvmpllda02.X.com:8140"
> 2012/12/05 18:33:33 [error] 25920#0: *24 open() 
> "/etc/puppet/rack/public/production/certificate_request/sl63anadi.X.com" 
> failed (2: No such file or directory), client: 10.209.47.26, server: , 
> request: "GET /production/certificate_request/sl63anadi.X.com? HTTP/1.1", 
> host: "bangvmpllda02.X.com:8140"
> 2012/12/05 18:47:56 [error] 25923#0: *27 open() 
> "/etc/puppet/rack/public/production/certificate/ca" failed (2: No such file 
> or directory), client: 10.209.47.31, server: , request: "GET 
> /production/certificate/ca? HTTP/1.1", host: "bangvmpllda02.X.com:8140"
> 2012/12/05 18:47:56 [error] 25923#0: *28 open() 
> "/etc/puppet/rack/public/production/certificate_request/blramisr195602.X.com"
>  failed (2: No such file or directory), client: 10.209.47.31, server: , 
> request: "GET /production/certificate_request/blramisr195602.X.com? 
> HTTP/1.1", host: "bangvmpllda02.X.com:8140"
> 
> Passenger does not show any application groups either
> 
> [root@bangvmpllDA02 nginx]# passenger-status 
> --- General information ---
> max  = 15
> count= 0
> active   = 0
> inactive = 0
> Waiting on global queue: 0
> 
> --- Application groups ---
> [root@bangvmpllDA02 nginx]#
> 
> here's my nginx configuration
> 
> user  puppet;
> worker_processes  4;
> 
> #error_log  logs/error.log;
> #error_log  logs/error.log  notice;
> error_log  logs/error.log  info;
> 
> #pidlogs/nginx.pid;
> 
> 
> events {
> use epoll;
> worker_connections  1024;
> }
> 
> 
> http {
> include   mime.types;
> default_type  application/octet-stream;
> 
> log_format  main  '$remote_addr - $remote_user [$time_local] 
> "$request" '
>   '$status $body_bytes_sent "$http_referer" '
>   '"$http_user_agent" "$http_x_forwarded_for"';
> 
> access_log  logs/access.log  main;
> 
> sendfileon;
> #tcp_nopush on;
> server_tokens off;
> #keepalive_timeout  0;
> keepalive_timeout  120;
> 
> gzip  on;
> gzip_http_version 1.1;
> gzip_disable "msie6";
> gzip_vary on;
> gzip_min_length 1100;
> gzip_buffers 64 8k;
> gzip_comp_level 3;
> gzip_proxied any;
> gzip_types text/plain text/css application/x-javascript text/xml 
> application/xml;
> 
> server {
> listen   80;
> server_name  bangvmpllda02.XX.com;
> 
> charset utf-8;
> 
> #access_log  logs/http.access.log  main;
> 
> location / {
> root   html;
> index  index.html index.htm index.php;
> }
> 
> #err

[Puppet Users] How to group hosts?

[Jakov Sosic]

Hi.

I'm currently using hiera in a very rudimentary way, using only perhost
and common.

Now, I'm trying to group my hosts a little bit, so for example web
servers could have their own yaml with data. Problem is I don't have an
idea how to group hosts? How can I say to puppet that for example hosts:

storage01
storage02
storage03
storage04

belong to group storage_nodes, and

web01
web02

belong to group web_nodes?


How do you do that?


Thank you

-- 
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: [Puppet Users] custom define type for array with 'case' argument pass to it

[Jakov Sosic]

On 12/06/2012 05:51 PM, iamauser wrote:
> Hi,
> 
> I had tried installing puppet-lint sometime ago, and tried this again as
> you wrote, but I get a bunch of buffer overflow (see below). I have
> reported an issue with rodjek's github and let's see if I get an answer.
> Any suggestion from this forum will certainly help.

Are you using RHEL od RHEL derivative? If yes, I can provide you RPM.

-- 
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: [Puppet Users] custom define type for array with 'case' argument pass to it

[iamauser]

Hi,

I had tried installing puppet-lint sometime ago, and tried this again as 
you wrote, but I get a bunch of buffer overflow (see below). I have 
reported an issue with rodjek's github and let's see if I get an answer. 
Any suggestion from this forum will certainly help.

]# gem install puppet-lint
*** buffer overflow detected ***: /usr/bin/ruby terminated
=== Backtrace: =
/lib64/libc.so.6(__chk_fail+0x2f)[0x2af4423bffaf]
/usr/lib64/ruby/1.8/x86_64-linux/syck.so(rb_syck_mktime+0x48e)[0x2af44284149e]
/usr/lib64/ruby/1.8/x86_64-linux/syck.so(yaml_org_handler+0x860)[0x2af442841db0]
/usr/lib64/ruby/1.8/x86_64-linux/syck.so(syck_defaultresolver_node_import+0x39)[0x2af442841fb9]
/usr/lib64/libruby.so.1.8[0x2af441737a9e]
/usr/lib64/libruby.so.1.8[0x2af441737fb8]
/usr/lib64/libruby.so.1.8[0x2af441738562]
.
.
and goes on...

am I missing something trivial in here ?

]# gem --version
1.3.1
]# ruby --version
ruby 1.8.5 (2006-08-25) [x86_64-linux]

#



On Thursday, December 6, 2012 9:11:17 AM UTC-6, nikolavp wrote:
>
> You should consider using a good editor which will show those error for 
> you. You can incorporate puppet-lint for example and it will spot most 
> of the problems and warn you about the double quotes for performance and 
> clarity reasons. 
>
> Hope that helps :-) 
>
> Best, Nikola 
>
> On Wed, Dec 05, 2012 at 04:19:35PM -0800, iamauser wrote: 
> > No worries. Your comment helped me to notice the dollar sign in front of 
> > the linkcase. That actually solved the issue. Now it works and yes, I 
> have 
> > added a default case as well :) 
> > 
> > Thanks 
> > 
> > 
> > On Wednesday, December 5, 2012 6:16:55 PM UTC-6, Jakov Sosic wrote: 
> > > 
> > > On 12/06/2012 12:58 AM, iamauser wrote: 
> > > > First of all, I didn't copy paste my code, rather typed it here, so 
> > > > indentation should be ignored. 
> > > > You are right, dollar sign shouldn't be there, and I think it was a 
> typo 
> > > > on my part that I failed to notice. I disagree with your comment 
> about 
> > > > singlequote or doublequote for "var". That shouldn't be an issue 
> here as 
> > > > it will consider this as string of characters. 
> > > 
> > > Sorry if my comments sounded harsh, I didn't mean to offend you. Just 
> > > urge you to incorporate those tools into your daily practice, which 
> > > would save you a lot of time and nerves ;) 
> > > 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "Puppet Users" group. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msg/puppet-users/-/I07DoBUDI_gJ. 
> > To post to this group, send email to 
> > puppet...@googlegroups.com. 
>
> > To unsubscribe from this group, send email to 
> puppet-users...@googlegroups.com . 
> > For more options, visit this group at 
> http://groups.google.com/group/puppet-users?hl=en. 
> > 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/-HUe5ZaJeB4J.
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] Puppet Camp Ghent Jan 31 & Feb 1 (before FOSDEM)

[Dawn Foster]

I wanted to let everyone know that we're holding Puppet Camp Ghent on
January 31 and February 1. For those of you attending FOSDEM, don't
worry, you will have plenty of time to catch the train (it's a 30
minute trip) from Ghent to Brussels for the FOSDEM Friday Beer Event
after we wrap up Puppet Camp :)

I've posted all of the details here:
http://puppetlabs.com/blog/puppet-camp-ghent-register-or-submit-a-talk/

But here's the quick summary:
* Registration is open now: http://puppetcampghent2013.eventbrite.com/
* We're looking for sponsors: please email j...@puppetlabs.com for details.
* We need you to submit a talk:
https://docs.google.com/spreadsheet/viewform?formkey=dDVtQUJYbDVEOTQ3UnVHZWVsdC1oeEE6MQ

For those of you also attending FOSDEM, you should consider submitting
a talk for the Configuration/Systems Management DevRoom:
https://lists.fosdem.org/pipermail/config-mgmt-devroom/2012-November/00.html

Note: I've cross posted this (BCC) to puppet-announce and puppet-dev,
but please post any replies to puppet-users to keep the thread in one
place.

Let me know if you have any questions, and I hope to see many of you there!

Regards,
Dawn Foster

-- 
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: Error: Could not request certificate: Connection refused - connect(2)

[Diogo Martinez]

The solutions went start master pid and redo the ssl certificates with 
puppet cert clean host_name and deleting var/lib/puppet/ssl.
 
thanks Fran and Jc!!!
Em quarta-feira, 5 de dezembro de 2012 08h16min58s UTC-2, Diogo Martinez 
escreveu:

> Hi all,
> I am new at puppet and Im using the puppet learning tutorial. I execute 
> until Basic agent/master puppet. Everything worked ok but after 2 or 3 
> days, running the command "puppet agent --test", start throw the error in 
> subject. That left me with the following questions:
>  
> how to puppet agent connect to master without service started on master?
>  
> If this connection is possible ( worked firsts times )what are the 
> possibilities I to be receiving this error?
>  
> I needed install puppet using tarball because a business rules is that 
> servers have not internet access.
>  
> Thanks in advance, and sorry for the bad English.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/ayaaMisQ6F4J.
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: [Puppet Users] Re: managing exceptions/specifics on file content / source

[Martin Willemsma]

Thanks for the pointer, Evelio

For others needed something similar: I created a key in hiera, defaulting
to template

$config_src = hiera("openssh_config_src", "template")

My code now looks like this:

file {
$config :
ensure => file,
owner => 0,
group => 0,
mode => 0600,
content => $config_src ? {
source => undef,
default => template("${module_name}/${config_tpl}")
},
source => $config_src ? {
source =>
"puppet:///private/${module_name}/sshd_config",
default => undef,
},
require => Package[$pkg_name],
notify => Service[$svc_name],
}

For unique configs I now use a fileshare called 'private' and put the files
there. I think I will use the same for ntp until I find something better.





2012/12/6 Evelio VILA 

> HI,
>
> Le jeudi 6 décembre 2012 13:07:19 UTC+1, mawi a écrit :
>
>> Hi,
>>
>> I'm looking for help on this use case:
>>
>> I have several modules managing e.g. ntp and ssh on some nodes. The
>> content of ntp.conf and sshd_config are generated from templates for most
>> of the nodes. Now we have a use case where some nodes need specific
>> sshd_config or other admins need to make permanent local edits to those
>> files or even provide their own sshd_config.
>>
>> How can I select between source and template for file resouces and how do
>> I organize this in my VCS?
>>
>> Snippet from ssh module =>
>>
>> file {
>> $config :
>> ensure => file,
>> owner => 0,
>> group => 0,
>> mode => 0600,
>> content => template("${module_name}/${**
>> config_tpl}"),
>> require => Package[$pkg_name],
>> notify => Service[$svc_name]
>> }
>>
>> How can I incorporate a selector that checks for a source first on the
>> fileserver? and defaults to the sshd_config template?
>>
>
> you may want take a look at hiera.
>
>>
>> if
>> source => "puppet://private/${module_**name}/file/sshd_config
>> else
>>   content => template("${module_name}/${**config_tpl}")
>> end
>>
>
>
> however be aware, using  something like
> $module_name in hiera.yaml won't work as expected, at least in my
> experience.
>
>   evelio
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/LXRhCghCx1cJ.
> 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.
>



-- 
Met vriendelijke groet, Kind Regards,

Martin Willemsma

-- 
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] "Could not render to pson"

[Tom Owens]

I found this error in syslog:

Dec  3 16:43:15 0x0x0tuna puppet-agent[16790]: 
(/Stage[main]/Tuna/File[/u/net/profile/common/zoom.so.32/hpsw.so]/content) 
change from {md5}9913d05900c2fd8cd14ef2efec728457 to 
{md5}fe7db3112ffcea0f80fbda99b7da408c failed: Could not back up 
/u/net/profile/common/zoom.so.32/hpsw.so: Could not render to pson: 
"\340\215\203"

As far as I can tell, the agent on this client box is trying to push 
/u/net/profile/common/zoom.so.32/hpsw.so into the filebucket on the puppet 
master and failing.  Since that backup fails, it won't receive the new 
file, which is a problem.

Does anybody have any ideas on how to fix this?  Or at least a better idea 
how to diagnose why it's failing?  I do not have this issue with text 
files.  hpsw.so is a shared library in Linux.

Thanks,

Tom

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/re0nCcocQLQJ.
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] Puppet+Passenger: Client can get cert signed, but then errors

[Emil Flink]

Puppet + webbrick = No problems
Puppet + Passenger = Client can connect and get its certificate signed, but 
then get heaploads of SSL errors .

I have tried regenerating all certificates by running *rm -R 
/var/lib/puppet/ssl/** on both the master and the client.

Apache virtualhost: http://pastebin.com/2Ma5XSBW
/etc/puppet/auth.conf: http://pastebin.com/VvmMq9fC
/etc/puppet/puppet.conf: http://pastebin.com/fNeSEfsk

root@puppetmaster:/etc/puppet# tree
.
├── auth.conf
├── files
│   ├── apache2.conf
│   └── test
├── fileserver.conf
├── manifests
│   └── site.pp
├── modules
├── puppet.conf
├── rack
│   ├── public
│   │   ├── config.ru
│   │   ├── files
│   │   │   ├── apache2.conf
│   │   │   └── test
│   │   └── manifest.pp
│   └── README
└── templates

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/_SD8Sj98NEQJ.
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] pasenger does not start puppet master application under nginx

[Anadi Misra]

On the server

[root@bangvmpllDA02 logs]# ruby -v
ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]

[root@bangvmpllDA02 logs]# puppet --version
3.0.1

and

[root@bangvmpllDA02 logs]# service nginx configtest
nginx: the configuration file /apps/nginx/nginx.conf syntax is ok
nginx: configuration file /apps/nginx/nginx.conf test is successful

[root@bangvmpllDA02 logs]# service nginx status
nginx (pid 25923 25921 25920 25917 25908) is running...
[root@bangvmpllDA02 logs]# 

however none of my agents are able to connect to the master, they all fail 
with errors like so

[amisr1@blramisr195602 ~]$ puppet agent --test --verbose --server 
bangvmpllda02.X.com
Info: Creating a new SSL certificate request for blramisr195602.X.com
Info: Certificate Request fingerprint (SHA256): 
26:EB:08:1F:82:32:E4:03:7A:64:8E:30:A3:99:93:26:E6:66:B9:B0:49:B6:08:F9:67:CA:1B:0C:00:B9:1D:41
Error: Could not request certificate: Error 405 on SERVER: 
405 Not Allowed

405 Not Allowed
nginx



Exiting; failed to retrieve certificate and waitforcert is disabled

when I check logs on puppet master

[root@bangvmpllDA02 logs]# tail puppet_access.log
[05/Dec/2012:17:45:18 +0530] "GET /production/certificate/ca? HTTP/1.1" 404 
162 "-" "Ruby"
[05/Dec/2012:18:32:23 +0530] "PUT 
/production/certificate_request/sl63anadi.X.com HTTP/1.1" 405 166 "-" 
"-"
[05/Dec/2012:18:33:33 +0530] "GET 
/production/certificate/sl63anadi.X.com? HTTP/1.1" 404 162 "-" "-"
[05/Dec/2012:18:33:33 +0530] "GET 
/production/certificate_request/sl63anadi.X.com? HTTP/1.1" 404 162 "-" 
"-"
[05/Dec/2012:18:33:33 +0530] "PUT 
/production/certificate_request/sl63anadi.X.com HTTP/1.1" 405 166 "-" 
"-"

and the error logs show that nginx is not really able to process the 
request well

2012/12/05 18:33:33 [error] 25920#0: *23 open() 
"/etc/puppet/rack/public/production/certificate/sl63anadi.X.com" failed 
(2: No such file or directory), client: 10.209.47.26, server: , request: 
"GET /production/certificate/sl63anadi.X.com? HTTP/1.1", host: 
"bangvmpllda02.X.com:8140"
2012/12/05 18:33:33 [error] 25920#0: *24 open() 
"/etc/puppet/rack/public/production/certificate_request/sl63anadi.X.com" 
failed (2: No such file or directory), client: 10.209.47.26, server: , 
request: "GET /production/certificate_request/sl63anadi.X.com? 
HTTP/1.1", host: "bangvmpllda02.X.com:8140"
2012/12/05 18:47:56 [error] 25923#0: *27 open() 
"/etc/puppet/rack/public/production/certificate/ca" failed (2: No such file 
or directory), client: 10.209.47.31, server: , request: "GET 
/production/certificate/ca? HTTP/1.1", host: "bangvmpllda02.X.com:8140"
2012/12/05 18:47:56 [error] 25923#0: *28 open() 
"/etc/puppet/rack/public/production/certificate_request/blramisr195602.X.com"
 
failed (2: No such file or directory), client: 10.209.47.31, server: , 
request: "GET /production/certificate_request/blramisr195602.X.com? 
HTTP/1.1", host: "bangvmpllda02.X.com:8140"

Passenger does not show any application groups either

[root@bangvmpllDA02 nginx]# passenger-status 
--- General information ---
max  = 15
count= 0
active   = 0
inactive = 0
Waiting on global queue: 0

--- Application groups ---
[root@bangvmpllDA02 nginx]#

here's my nginx configuration

user  puppet;
worker_processes  4;

#error_log  logs/error.log;
#error_log  logs/error.log  notice;
error_log  logs/error.log  info;

#pidlogs/nginx.pid;


events {
use epoll;
worker_connections  1024;
}


http {
include   mime.types;
default_type  application/octet-stream;

log_format  main  '$remote_addr - $remote_user [$time_local] 
"$request" '
  '$status $body_bytes_sent "$http_referer" '
  '"$http_user_agent" "$http_x_forwarded_for"';

access_log  logs/access.log  main;

sendfileon;
#tcp_nopush on;
server_tokens off;
#keepalive_timeout  0;
keepalive_timeout  120;

gzip  on;
gzip_http_version 1.1;
gzip_disable "msie6";
gzip_vary on;
gzip_min_length 1100;
gzip_buffers 64 8k;
gzip_comp_level 3;
gzip_proxied any;
gzip_types text/plain text/css application/x-javascript text/xml 
application/xml;

server {
listen   80;
server_name  bangvmpllda02.XX.com;

charset utf-8;

#access_log  logs/http.access.log  main;

location / {
root   html;
index  index.html index.htm index.php;
}

#error_page  404  /404.html;

# redirect server error pages to the static page /50x.html
#
error_page   500 502 503 504  /50x.html;
location = /50x.html {
root   html;
}

# proxy the PHP scripts to Apache listening on 127.0.0.1:80
  

Re: [Puppet Users] Re: Unnecessary changes when creating facts.yaml

[Konrad Scherer]

On 12/05/2012 10:22 AM, Andrew Beresford wrote:

I've ended up separating the template into an external file and then doing
something horrible;

out=scope.to_hash.reject { |k,v| k.to_s =~
/(uptime.*|timestamp|.*free|macaddress.*|ipaddress)/ }.to_yaml.split "\n"
header = out.shift
header = header+"\n"
sorted = out.sort
sorted_string = sorted.join "\n"
header << sorted_string

This only works because the structure of the facts.yaml content is very simple,
and I'd much rather replace it with something more elegant.

I was originally trying to override the Hash to_yaml method to output the keys
in alphabetical order, but I ended up fighting with it too much and gave up as I
had other more important stuff to work on.


I had the same problem and tried an equally ugly hack which worked until the 
yaml started containing perfectly legal yaml anchors and aliases (&id001 and 
*id001)[1]. My current solution is:


  cron {
'generate_facts':
  command => '/usr/bin/facter --puppet --yaml > 
/etc/mcollective/facter.yaml 2> /dev/null',

  minute  => '0';
  }

This does miss the puppet variables in the current scope (move to custom fact?) 
and potentially quickly changing facts (handled with facter_dot_d?). But this 
works for my needs. If anyone has a better idea I would be very interested.


[1]: http://yaml.org/spec/1.2/spec.html#id2760395

--
Konrad Scherer, Sr. Engineer, Linux Products Group, Wind River
direct 613-963-1342   fax 613-592-2283

--
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] pasenger does not start puppet master under nginx

[Anadi Misra]

On the server

[root@bangvmpllDA02 logs]# ruby -v
ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]

[root@bangvmpllDA02 logs]# puppet --version
3.0.1

and

[root@bangvmpllDA02 logs]# service nginx configtest
nginx: the configuration file /apps/nginx/nginx.conf syntax is ok
nginx: configuration file /apps/nginx/nginx.conf test is successful

[root@bangvmpllDA02 logs]# service nginx status
nginx (pid 25923 25921 25920 25917 25908) is running...
[root@bangvmpllDA02 logs]# 

however none of my agents are able to connect to the master, they all fail 
with errors like so

[amisr1@blramisr195602 ~]$ puppet agent --test --verbose --server 
bangvmpllda02.X.com
Info: Creating a new SSL certificate request for blramisr195602.X.com
Info: Certificate Request fingerprint (SHA256): 
26:EB:08:1F:82:32:E4:03:7A:64:8E:30:A3:99:93:26:E6:66:B9:B0:49:B6:08:F9:67:CA:1B:0C:00:B9:1D:41
Error: Could not request certificate: Error 405 on SERVER: 
405 Not Allowed

405 Not Allowed
nginx



Exiting; failed to retrieve certificate and waitforcert is disabled

when I check logs on puppet master

[root@bangvmpllDA02 logs]# tail puppet_access.log
[05/Dec/2012:17:45:18 +0530] "GET /production/certificate/ca? HTTP/1.1" 404 
162 "-" "Ruby"
[05/Dec/2012:18:32:23 +0530] "PUT 
/production/certificate_request/sl63anadi.X.com HTTP/1.1" 405 166 "-" 
"-"
[05/Dec/2012:18:33:33 +0530] "GET 
/production/certificate/sl63anadi.X.com? HTTP/1.1" 404 162 "-" "-"
[05/Dec/2012:18:33:33 +0530] "GET 
/production/certificate_request/sl63anadi.X.com? HTTP/1.1" 404 162 "-" 
"-"
[05/Dec/2012:18:33:33 +0530] "PUT 
/production/certificate_request/sl63anadi.X.com HTTP/1.1" 405 166 "-" 
"-"

and the error logs show that nginx is not really able to process the 
request well

2012/12/05 18:33:33 [error] 25920#0: *23 open() 
"/etc/puppet/rack/public/production/certificate/sl63anadi.X.com" failed 
(2: No such file or directory), client: 10.209.47.26, server: , request: 
"GET /production/certificate/sl63anadi.X.com? HTTP/1.1", host: 
"bangvmpllda02.X.com:8140"
2012/12/05 18:33:33 [error] 25920#0: *24 open() 
"/etc/puppet/rack/public/production/certificate_request/sl63anadi.X.com" 
failed (2: No such file or directory), client: 10.209.47.26, server: , 
request: "GET /production/certificate_request/sl63anadi.X.com? 
HTTP/1.1", host: "bangvmpllda02.X.com:8140"
2012/12/05 18:47:56 [error] 25923#0: *27 open() 
"/etc/puppet/rack/public/production/certificate/ca" failed (2: No such file 
or directory), client: 10.209.47.31, server: , request: "GET 
/production/certificate/ca? HTTP/1.1", host: "bangvmpllda02.X.com:8140"
2012/12/05 18:47:56 [error] 25923#0: *28 open() 
"/etc/puppet/rack/public/production/certificate_request/blramisr195602.X.com"
 
failed (2: No such file or directory), client: 10.209.47.31, server: , 
request: "GET /production/certificate_request/blramisr195602.X.com? 
HTTP/1.1", host: "bangvmpllda02.X.com:8140"

Passenger does not show any application groups either

[root@bangvmpllDA02 nginx]# passenger-status 
--- General information ---
max  = 15
count= 0
active   = 0
inactive = 0
Waiting on global queue: 0

--- Application groups ---
[root@bangvmpllDA02 nginx]#

here's my nginx configuration

user  puppet;
worker_processes  4;

#error_log  logs/error.log;
#error_log  logs/error.log  notice;
error_log  logs/error.log  info;

#pidlogs/nginx.pid;


events {
use epoll;
worker_connections  1024;
}


http {
include   mime.types;
default_type  application/octet-stream;

log_format  main  '$remote_addr - $remote_user [$time_local] 
"$request" '
  '$status $body_bytes_sent "$http_referer" '
  '"$http_user_agent" "$http_x_forwarded_for"';

access_log  logs/access.log  main;

sendfileon;
#tcp_nopush on;
server_tokens off;
#keepalive_timeout  0;
keepalive_timeout  120;

gzip  on;
gzip_http_version 1.1;
gzip_disable "msie6";
gzip_vary on;
gzip_min_length 1100;
gzip_buffers 64 8k;
gzip_comp_level 3;
gzip_proxied any;
gzip_types text/plain text/css application/x-javascript text/xml 
application/xml;

server {
listen   80;
server_name  bangvmpllda02.XX.com;

charset utf-8;

#access_log  logs/http.access.log  main;

location / {
root   html;
index  index.html index.htm index.php;
}

#error_page  404  /404.html;

# redirect server error pages to the static page /50x.html
#
error_page   500 502 503 504  /50x.html;
location = /50x.html {
root   html;
}

# proxy the PHP scripts to Apache listening on 127.0.0.1:80
  

[Puppet Users] Re: how to use vcsrepo?¿

[Drew Blessing]

Hi Fran,

There's a couple of things you can try.  First, make sure you have the 
module in your modules directory.  I'm fairly sure you have this step done 
but just in case.  Then, since vcsrepo uses plugins to accomplish it's 
tasks you need to ensure that the plugins are on both the puppet master and 
on the client.  Do a puppet run on both the puppet master and the client 
with the --pluginsync flag and you will likely see a bunch of plugins being 
installed at the beginning of those puppet runs.  You will probably not see 
the errors any more.  

On Wednesday, December 5, 2012 11:00:20 AM UTC-6, Fran Rodríguez wrote:
>
> Hi, i spent all day trying to work the vcsrepo module, without success. Im 
> doing my own class like this:
>
> class rta-frontend {   
> 
> 
> 
>   vcsrepo { "/var/www/home":   
> 
> 
> 
> ensure   => present,   
> 
> 
> 
> provider => git,   
> 
> 
> 
> source   => "g...@home.org:home.git",   
> 
> 
> require  => [ File["/root/.ssh/id_rsa.pub"], Package["git"] ], 
> 
> 
> 
>   }   
> 
> 
>  
>   class { "nginx": 
> 
> 
> 
> worker_connections => 4096,   
> 
> 
>  
> keepalive_timeout => 120, 
> 
> 
>  
> client_max_body_size => "200m",   
> 
> 
>  
>   }   
> 
> 
>  
>   nginx::vhost { "$fqdn" : 
> 
> 
> 
> docroot => "/var/www/home",   
> 
> 
>  
>   }   
> 
> 
>  
> }   
>
> I dont know why but im getting this error...
>
> Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error 
> ArgumentError: Invalid resource type vcsrepo
>
> Any ideas?¿ Cheers!
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/uOR73TFdZK4J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe 

[Puppet Users] Re: Error: can't instantiate uninitialized class

[Luca Gioppo]

Ruby version 1.8.7 on both master and agent.

But on the agent I get:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
can't instantiate uninitialized class
Debug: Using cached catalog for jbossm.cortile.cloudlabcsi.local
Using cached catalog

So the problem should be in the puppet master and not in the agent.

Luca

Il giorno giovedì 6 dicembre 2012 12:14:51 UTC+1, Luca Gioppo ha scritto:
>
> OK I'm getting mad.
>
> All of a sudden after a few mods I received this error from the 
> puppet_master.
>
> I reverted all the changes done up to a last working set but no prize 
> still this error and I cannot understand what is happening it seems that it 
> manages to finish the catalog but than it stops.
>
> Here is a chunk of the output any idea on ohw to raise the level of debug 
> and getting something more useful?
> Puppet version 3.0.0
> Thanks
> Luca
>
> Compiled catalog for jbossm.cortile.cloudlabcsi.local in environment 
> production in 1.53 seconds
> Info: Caching catalog for jbossm.cortile.cloudlabcsi.local
> Debug: Searched for resources in 0.01 seconds
> Error: can't instantiate uninitialized class
> Debug: Finishing transaction 69873076055740
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/N5tJC5sC3-AJ.
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: [Puppet Users] custom define type for array with 'case' argument pass to it

[Nikola Petrov]

You should consider using a good editor which will show those error for
you. You can incorporate puppet-lint for example and it will spot most
of the problems and warn you about the double quotes for performance and
clarity reasons.

Hope that helps :-)

Best, Nikola

On Wed, Dec 05, 2012 at 04:19:35PM -0800, iamauser wrote:
> No worries. Your comment helped me to notice the dollar sign in front of 
> the linkcase. That actually solved the issue. Now it works and yes, I have 
> added a default case as well :)
> 
> Thanks
> 
> 
> On Wednesday, December 5, 2012 6:16:55 PM UTC-6, Jakov Sosic wrote:
> >
> > On 12/06/2012 12:58 AM, iamauser wrote: 
> > > First of all, I didn't copy paste my code, rather typed it here, so 
> > > indentation should be ignored. 
> > > You are right, dollar sign shouldn't be there, and I think it was a typo 
> > > on my part that I failed to notice. I disagree with your comment about 
> > > singlequote or doublequote for "var". That shouldn't be an issue here as 
> > > it will consider this as string of characters. 
> >
> > Sorry if my comments sounded harsh, I didn't mean to offend you. Just 
> > urge you to incorporate those tools into your daily practice, which 
> > would save you a lot of time and nerves ;) 
> >
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To view this discussion on the web visit 
> https://groups.google.com/d/msg/puppet-users/-/I07DoBUDI_gJ.
> 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.
> 

-- 
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: [Puppet Users] gem error installing rack

[Stefan Goethals]

This is not a puppet error..

But i think the name rubygems.org is not resolving on your server and/or a
firewall is blocking access to the site...

Regards,

Stefan.

On Thu, Dec 6, 2012 at 3:32 PM, DJames  wrote:

> # gem install rack
>
>
> ERROR:  http://rubygems.org/ does not appear to be a repository
> ERROR:  Could not find a valid gem 'rack' (>= 0) in any repository
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/gdHrgrFB264J.
> 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.
>

-- 
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] gem error installing rack

[DJames]

# gem install rack


ERROR:  http://rubygems.org/ does not appear to be a repository
ERROR:  Could not find a valid gem 'rack' (>= 0) in any repository

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/gdHrgrFB264J.
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: Error: can't instantiate uninitialized class

[jcbollinger]

On Thursday, December 6, 2012 5:14:51 AM UTC-6, Luca Gioppo wrote:
>
> OK I'm getting mad.
>
> All of a sudden after a few mods I received this error from the 
> puppet_master.
>
> I reverted all the changes done up to a last working set but no prize 
> still this error and I cannot understand what is happening it seems that it 
> manages to finish the catalog but than it stops.
>
> Here is a chunk of the output any idea on ohw to raise the level of debug 
> and getting something more useful?
> Puppet version 3.0.0
> Thanks
> Luca
>
> Compiled catalog for jbossm.cortile.cloudlabcsi.local in environment 
> production in 1.53 seconds
> Info: Caching catalog for jbossm.cortile.cloudlabcsi.local
> Debug: Searched for resources in 0.01 seconds
> Error: can't instantiate uninitialized class
> Debug: Finishing transaction 69873076055740
>


That error message is being emitted by the agent, not the master.  Run the 
agent with the --debug flag to get the most detailed information available, 
but it looks like you may already be doing that.

That doesn't look like a Puppet error message, however.  Puppet doesn't 
have a sense of "initializing" classes, nor really of "instantiating" 
them.  The latter, especially, is an OO concept, and Puppet's "classes" are 
not classes in the OO sense.

I would guess, therefore, that the error is being emitted at a lower level 
of the software stack, probably in Ruby itself.  If it's there then it 
could arise from a Puppet bug, a Ruby bug, or an incompatibility between 
Puppet and your Ruby implementation.  Which Ruby is that, by the way?


John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/xo8Ho9oSA7gJ.
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: [Puppet Users] Re: hiera default values for a variable

[jcbollinger]

On Tuesday, December 4, 2012 8:10:00 PM UTC-6, Pete wrote:
>
>
> One last question.
> I use a node level variable to specify the location of a node.
> I use this for setting variables specific to that location like different 
> puppet master ip and nagios ip for the office and such.
> I want to use that variable in hiera for the same purpose.
> I have this in my hiera.yaml file.
>
> ---
> :hierachy:
>   - %{::clientcert}
>   - %{::environment}
>   - %{location}
>   - virtual_%{::is_virtual}
>   - common
> :backends: yaml
> :yaml:
>   :datadir: /etc/puppet/hieradata
>
> it gets data from the common.yaml file but is seems to not get anything 
> from any of the other files.
> it's definitely using the datadir because thats where the common.yaml file 
> is as well as the rest of the data files.
> Am I missing something?
>
>
You are missing that node variables are not globals, and in fact don't even 
have qualified names.  I strongly suspect that that is why Hiera is not 
seeing them.

There are several potential workarounds, among them:

   - set the needed variable(s) at top-level, based on some sort of 
   conditional
   - push all the contents of your node blocks into classes, so that the 
   variables in question become class variables
   - instead of creating a separate hierarchy level with a data file for 
   each value of (say) $environment,use a hash of hashes in the level below, 
   with the $environment values as the outer hash keys


Cheers,

John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/1Ajo2OXHPC4J.
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: managing exceptions/specifics on file content / source

[Evelio VILA]

HI,

Le jeudi 6 décembre 2012 13:07:19 UTC+1, mawi a écrit :
>
> Hi, 
>
> I'm looking for help on this use case: 
>
> I have several modules managing e.g. ntp and ssh on some nodes. The 
> content of ntp.conf and sshd_config are generated from templates for most 
> of the nodes. Now we have a use case where some nodes need specific 
> sshd_config or other admins need to make permanent local edits to those 
> files or even provide their own sshd_config. 
>
> How can I select between source and template for file resouces and how do 
> I organize this in my VCS? 
>
> Snippet from ssh module => 
>
> file {
> $config :
> ensure => file,
> owner => 0,
> group => 0,
> mode => 0600,
> content => template("${module_name}/${config_tpl}"),
> require => Package[$pkg_name],
> notify => Service[$svc_name]
> }
>   
> How can I incorporate a selector that checks for a source first on the 
> fileserver? and defaults to the sshd_config template? 
>
 
you may want take a look at hiera. 

>
> if 
> source => "puppet://private/${module_name}/file/sshd_config
> else 
>   content => template("${module_name}/${config_tpl}")
> end 
>


however be aware, using  something like
$module_name in hiera.yaml won't work as expected, at least in my 
experience. 

  evelio
 

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/LXRhCghCx1cJ.
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] managing exceptions/specifics on file content / source

[Martin Willemsma]

Hi,

I'm looking for help on this use case:

I have several modules managing e.g. ntp and ssh on some nodes. The content
of ntp.conf and sshd_config are generated from templates for most of the
nodes. Now we have a use case where some nodes need specific sshd_config or
other admins need to make permanent local edits to those files or even
provide their own sshd_config.

How can I select between source and template for file resouces and how do I
organize this in my VCS?

Snippet from ssh module =>

file {
$config :
ensure => file,
owner => 0,
group => 0,
mode => 0600,
content => template("${module_name}/${config_tpl}"),
require => Package[$pkg_name],
notify => Service[$svc_name]
}

How can I incorporate a selector that checks for a source first on the
fileserver? and defaults to the sshd_config template?

if
source => "puppet://private/${module_name}/file/sshd_config
else
  content => template("${module_name}/${config_tpl}")
end

I have seen some post showing a select like this inside the module, but
every module has its own repository and I don't want these node specific
configs inside the module.

source =>
"puppet:///files/modules/${module_name}/etc/ssh/sshd_config.$hostname",
"puppet:///files/modules/${module_name}/etc/ssh/sshd_config.$hostname",

Hope someone can give me some pointers on how you (would) do this.  Thank
you!

-- 
Met vriendelijke groet, Kind Regards,

Martin Willemsma

-- 
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] Catalog into something "human readable"

[ollies...@googlemail.com]

Hello,

Is there anyway to parse a catalog generated with something like:-

 puppet master --compile  > .cat

That looks vaguely human readable. I have tried the "puppet catalog print" 
face but cannot seem to get it to parse for some reason

# puppet catalog print --catalog /var/tmp/.cat
err: undefined method `preferred_run_mode=' for 
#
err: Try 'puppet help catalog print' for usage

This is on a 2.7.16 master BTW

Or indeed anything in the PuppetDB that can pull this and parse it ?

Thanks


-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/u4awwsOj2uAJ.
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] Having puppetmaster checkout manifests from subversion

[Thomas Rasmussen]

Hi

I'm looking into a setup where we'd like the puppetmaster to 
checkout/update all the manifests from subversion before it compiles the 
manifests served to puppet nodes. I have been looking through the 
documentation, and I can't seem to find a way of doing this.

We'd like to be able to develop our manifests on our local computers and 
when committed to subversion, force a puppet agent run and this run would 
then use the newest manifests available. We are not using automated puppet 
agent runs, so the problem of a commit suddenly breaking code without 
noticing should not be a problem. 

The subversion server is not running on the same server as puppetmaster, so 
any interaction from subversion to puppet is not possible.

Any ideas how this problem can be solved? 

We are running puppet 2.7.18 on our master server.

Regards
Thomas

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/eIWMOngAR90J.
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] Error: can't instantiate uninitialized class

[Luca Gioppo]

OK I'm getting mad.

All of a sudden after a few mods I received this error from the 
puppet_master.

I reverted all the changes done up to a last working set but no prize still 
this error and I cannot understand what is happening it seems that it 
manages to finish the catalog but than it stops.

Here is a chunk of the output any idea on ohw to raise the level of debug 
and getting something more useful?
Puppet version 3.0.0
Thanks
Luca

Compiled catalog for jbossm.cortile.cloudlabcsi.local in environment 
production in 1.53 seconds
Info: Caching catalog for jbossm.cortile.cloudlabcsi.local
Debug: Searched for resources in 0.01 seconds
Error: can't instantiate uninitialized class
Debug: Finishing transaction 69873076055740

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/hfBeyiixO4AJ.
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: Storeconfigs parsing

[Andrei Burd]

https://groups.google.com/forum/?fromgroups=#!topic/puppet-users/5jMB2RxcKMU

here's the answer =)

On Wednesday, December 5, 2012 9:20:48 PM UTC+2, Or Elimelech wrote:
>
> Hello everyone,
> We have installed new puppetmaster on debian squeeze with storeconfigs 
> using postgresql
> we've migrated all manifests/modules from our old one that used to parse 
> everything correctly the way it is...
> with the new one I get 
>
> "Could not retrieve catalog from remote server: wrong header line format"
>
> and on the master it says that it has problem with parsing quotes
> we have an exec resource with the name
> exec { "asterisk -rx \"sip reload\"":
>
> Versions installed of software:
> puppetmaster: 2.7.18
> puppet: 2.7.18
> postgresql-9.1
> postgresql-server-dev-9.1
>
>
> Please tell me what's wrong?
>
> Thanks in advance 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/ofIbgraFLJUJ.
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: quotes in templates/manifests using storeconfigs

[Andrei Burd]

we figured out, that the problem was that in Postgres 9.1 they made
*standard_conforming_strings*  was ON by default, that causes problem in 
inserting escape characters  to DB.

On Wednesday, December 5, 2012 9:30:28 PM UTC+2, Andrei Burd wrote:
>
> Hi everyone!
> we installed Puppet master 2.7.18  from debian backports
> Configured it with storeconfig  using Postgresql 9.1 and ENC Foreman 1.0.1
> When we started migration from old puppet master with LDAP ENC we received 
> parser errors  that he could not insert to db tempate with string 
> *; Use Sybase-style magic quotes (escape ' with '' instead of \').*
> and it look like he does not escapes the quotes. we have pg 0.14.1
>
> any suggestions why is it so?
> on old puppetmaster it worked great.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/ZvuJ21YMbwMJ.
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: [Puppet Users] Puppet report aggregation

[Luke Bigum]

On Wednesday, December 5, 2012 12:50:43 PM UTC, ohad wrote:

> You could use foreman for that? filtering the hosts via search should 
> allow you to find the exact resources you are looking for?
>
> Ohad
>
>
Hi Ohad,

I haven't looked at The Foreman in a while but in my mind it's more like 
Puppet Dashboard - correct me if I'm wrong. What I'm aiming for is a tool 
that can aid change / release management where we run Puppet --noop across 
the estate, gather all the reports, then summarise what changes will be 
applied (resolv.conf changes on all hosts, fstab changes on 20 hosts, 
service X refreshes on Y hosts).

I don't really want to be searching for explicit resources changing across 
hosts, it's the resources I don't know about that worry me ;-) Is the 
foreman worth a look in this case?

-Luke
 

>
> On Tue, Dec 4, 2012 at 11:00 PM, Luke Bigum 
> > wrote:
>
>> Hi all,
>>
>> Can anyone recommend any tools for Puppet report aggregation? I'm 
>> interested in something that can take a given set of Puppet reports and 
>> summarise to me what resources have changed across all hosts.
>>
>> If nothing exists I will look to write one myself. In that case, is 
>> Puppet report format 3 valid for Puppet 3.0?
>>
>> http://projects.puppetlabs.com/projects/puppet/wiki/Report_Format_3
>>
>> Thanks,
>>
>> -Luke
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Puppet Users" group.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msg/puppet-users/-/Fcx6zByYGPQJ.
>> To post to this group, send email to puppet...@googlegroups.com
>> .
>> To unsubscribe from this group, send email to 
>> puppet-users...@googlegroups.com .
>> For more options, visit this group at 
>> http://groups.google.com/group/puppet-users?hl=en.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/puppet-users/-/zk_ospPVmYkJ.
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.