date:20121121

Re: [Puppet Users] Re: puppet-dashboard - rake API not working

2012-11-21 Thread Stefan Heijmans

And when you provide the RAILS_ENV you are using? For example;
 
sudo -u puppet-dashboard  rake -f /usr/share/puppet-dashboard/Rakefile 
RAILS_ENV=production  'node:list'
 
 

Op woensdag 21 november 2012 08:12:48 UTC+1 schreef Jacob het volgende:

 I don't get the expected output... (a list of my nodes)..

 only the deprecation warning.





 Il giorno martedì 20 novembre 2012 18:37:49 UTC+1, Bruno Leon ha scritto: 

  Does it fail or only warn ?

 I can only see dprecation warnings in your message.

  

 -- 

 Bruno

  

 On November 19, 2012 11:36:17 PM Jacob wrote:

 Thanks :)

 Now I get

 snip

 # sudo -u puppet-dashboard rake -f /usr/share/puppet-dashboard/Rakefile 
 'node:list'
 (in /usr/share/puppet-dashboard)
 DEPRECATION WARNING: Rake tasks in vendor/plugins/delayed_job/tasks are 
 deprecated. Use lib/tasks instead. (called from 
 /usr/share/puppet-dashboard/vendor/rails/railties/lib/tasks/rails.rb:10)

 /snip



 Il giorno lunedì 19 novembre 2012 19:37:43 UTC+1, Stefan Heijmans ha 
 scritto:

 Yes, I noticed it in 1.2.13 (
 https://groups.google.com/d/msg/puppet-users/-s07XIymxCo/Yp3DpRU4t6EJ) 
 but not in 1.2.14.

 Fixed it by running  the mentioned 'rake gems:refresh_specs' 


 Stefan



 On Monday, November 19, 2012 10:11:35 AM UTC+1, Jacob wrote:

 Hello all,

 I am quite new to the puppet arena, but I am really impressed with puppet 
 as a tool and the possibilities it gives you with regards to managing many 
 systems.

 I am running dashboard 1.2.14 and am trying to query via the rake API: 
 http://docs.puppetlabs.com/dashboard/manual/1.2/rake_api.html

 when I do, I get the following error:

 snip

 # sudo -u puppet-dashboard rake -f /usr/share/puppet-dashboard/Rakefile 
 'node:list'
 (in /var/log)
 config.gem: Unpacked gem daemons-1.0.10 in vendor/gems has no 
 specification file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem rack-1.1.2 in vendor/gems has no specification 
 file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem rspec-1.3.2 in vendor/gems has no specification 
 file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem rdoc-3.6.1 in vendor/gems has no specification 
 file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem rspec-rails-1.3.4 in vendor/gems has no 
 specification file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem thoughtbot-shoulda-2.10.2 in vendor/gems has no 
 specification file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem mocha-0.9.7 in vendor/gems has no specification 
 file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem will_paginate-2.3.15 in vendor/gems has no 
 specification file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem json_pure-1.5.1 in vendor/gems has no 
 specification file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem haml-3.1.2 in vendor/gems has no specification 
 file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem sass-3.1.2 in vendor/gems has no specification 
 file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem factory_girl-1.3.3 in vendor/gems has no 
 specification file. Run 'rake gems:refresh_specs' to fix this.
 DEPRECATION WARNING: Rake tasks in vendor/plugins/delayed_job/tasks are 
 deprecated. Use lib/tasks instead. (called from 
 /usr/share/puppet-dashboard/vendor/rails/railties/lib/tasks/rails.rb:10)



 /snip



 ...I fail to find any info on this online ... has anyone else seen this?

 Thanks,

 //Jacob.

 -- 
 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/-/Q-XcVfScapMJ.
 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/-/tg3uEymfq4UJ.
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: puppet-dashboard - rake API not working

2012-11-21 Thread Jacob

:-) Thank you - that did it!





Il giorno mercoledì 21 novembre 2012 09:04:29 UTC+1, Stefan Heijmans ha 
scritto:

 And when you provide the RAILS_ENV you are using? For example;
  
 sudo -u puppet-dashboard  rake -f /usr/share/puppet-dashboard/Rakefile 
 RAILS_ENV=production  'node:list'
  
  

 Op woensdag 21 november 2012 08:12:48 UTC+1 schreef Jacob het volgende:

 I don't get the expected output... (a list of my nodes)..

 only the deprecation warning.





 Il giorno martedì 20 novembre 2012 18:37:49 UTC+1, Bruno Leon ha scritto: 

  Does it fail or only warn ?

 I can only see dprecation warnings in your message.

  

 -- 

 Bruno

  

 On November 19, 2012 11:36:17 PM Jacob wrote:

 Thanks :)

 Now I get

 snip

 # sudo -u puppet-dashboard rake -f /usr/share/puppet-dashboard/Rakefile 
 'node:list'
 (in /usr/share/puppet-dashboard)
 DEPRECATION WARNING: Rake tasks in vendor/plugins/delayed_job/tasks are 
 deprecated. Use lib/tasks instead. (called from 
 /usr/share/puppet-dashboard/vendor/rails/railties/lib/tasks/rails.rb:10)

 /snip



 Il giorno lunedì 19 novembre 2012 19:37:43 UTC+1, Stefan Heijmans ha 
 scritto:

 Yes, I noticed it in 1.2.13 (
 https://groups.google.com/d/msg/puppet-users/-s07XIymxCo/Yp3DpRU4t6EJ) 
 but not in 1.2.14.

 Fixed it by running  the mentioned 'rake gems:refresh_specs' 


 Stefan



 On Monday, November 19, 2012 10:11:35 AM UTC+1, Jacob wrote:

 Hello all,

 I am quite new to the puppet arena, but I am really impressed with 
 puppet as a tool and the possibilities it gives you with regards to 
 managing many systems.

 I am running dashboard 1.2.14 and am trying to query via the rake API: 
 http://docs.puppetlabs.com/dashboard/manual/1.2/rake_api.html

 when I do, I get the following error:

 snip

 # sudo -u puppet-dashboard rake -f /usr/share/puppet-dashboard/Rakefile 
 'node:list'
 (in /var/log)
 config.gem: Unpacked gem daemons-1.0.10 in vendor/gems has no 
 specification file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem rack-1.1.2 in vendor/gems has no specification 
 file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem rspec-1.3.2 in vendor/gems has no specification 
 file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem rdoc-3.6.1 in vendor/gems has no specification 
 file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem rspec-rails-1.3.4 in vendor/gems has no 
 specification file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem thoughtbot-shoulda-2.10.2 in vendor/gems has no 
 specification file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem mocha-0.9.7 in vendor/gems has no specification 
 file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem will_paginate-2.3.15 in vendor/gems has no 
 specification file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem json_pure-1.5.1 in vendor/gems has no 
 specification file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem haml-3.1.2 in vendor/gems has no specification 
 file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem sass-3.1.2 in vendor/gems has no specification 
 file. Run 'rake gems:refresh_specs' to fix this.
 config.gem: Unpacked gem factory_girl-1.3.3 in vendor/gems has no 
 specification file. Run 'rake gems:refresh_specs' to fix this.
 DEPRECATION WARNING: Rake tasks in vendor/plugins/delayed_job/tasks are 
 deprecated. Use lib/tasks instead. (called from 
 /usr/share/puppet-dashboard/vendor/rails/railties/lib/tasks/rails.rb:10)



 /snip



 ...I fail to find any info on this online ... has anyone else seen this?

 Thanks,

 //Jacob.

 -- 
 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/-/Q-XcVfScapMJ.
 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/-/n6pqYiO6CSYJ.
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: delete a file created with puppet

2012-11-21 Thread Alex Stanhope

Hi Jakov,

On 21 November 2012 02:03, Jakov Sosic wrote:

 exec{'first':
   command = 'cd /tmp  wget mykey',
   creates = '/tmp/mykey',
 }

 exec{'second':
   command = 'echo   /tmp/mykey | tee -a /tmp/mykey2',
   creates = '/tmp/mykey2',
 }


...a really beautiful ugly hack.  I appreciate the input because it sounds 
like I'm not missing anything really obvious.  When coding in a new 
(declarative) language, I'm always mindful that I could be thinking about 
the problem incorrectly.  I'm surprised in this case that more puppeteers 
haven't had the same problem.  Perhaps I should be writing some kind of 
secure ssh-agent based key management plugin for Puppet?

Also John, thanks for the suggestion.  Sending a plaintext password to the 
git clone call is an option, but I've got several git and several SVN 
repos, all connecting over SSH so the agent-play made more sense to me.

Cheers, 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/-/_wHDatM6yEwJ.
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: delete a file created with puppet

2012-11-21 Thread David Schmitt


On 21.11.2012 03:03, Jakov Sosic wrote:

On 11/16/2012 06:17 PM, Alex Stanhope wrote:

On Friday, November 16, 2012 5:11:22 PM UTC, Ellison Marks wrote:

Could you give some more info on what you're trying to accomplish
with this? That way we might offer some ideas to help.


Of course.  I use a temporary file to store a private key passphrase.
  That passphrase is used to allow the client machine to load the
private key, and clone repositories from github.  After puppet has
installed the client machine, I'd like it to delete this temporary file,
so that future logins prompt the user for the password.  It's not the
end of the world to leave it there, or for me to clean it up manually.
  I know I could use passwordless private keys, but I think it's better
security to have passphrases on them.


You can maybe try some mumbo jumbo magic with stages and combining two
exec's.

Like, first exec gets the key:

exec{'first':
   command = 'cd /tmp  wget mykey',
   creates = '/tmp/mykey',
}

exec{'second':
   command = 'echo   /tmp/mykey | tee -a /tmp/mykey2',
   creates = '/tmp/mykey2',
}


Put first in stage before main, second in stage after main, and that
could work. Although it's a really really ugly hack, and circumvention
of Declarative Language nature - to declare states and not to run
scripts...


This will put the passphrase onto the node every time puppet runs. I do 
not see how that will make it any more secure.


To avoid putting sensitive key material into your automation, you'll 
have to try and see whether you cannot access the source without this. 
For example, you could clone internally from a reduced security repo and 
then modify the remote configuration.




Best Regards, David

--
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: Seeking some Puppet advice for a newbie (specifically Virtualmin/CSF related)

2012-11-21 Thread Matthew Burgess

On Tue, Nov 20, 2012 at 9:37 PM, Jakov Sosic jso...@srce.hr wrote:
 On 11/20/2012 03:12 PM, Matthew Burgess wrote:
 This can be mitigated, of

 course, by using 'ensure=installed', but then that means upgrades are
 painful.

 Why? You can always use cexec or mcollective with some kind of custom plugin
 for doing those sort of things.

I knew I should have qualified that statement: It's painful because
I've not had to do it
yet because I use my own repos and couldn't immediately think of a
non-painful way of upgrading packages :-)

Thanks for the MCollective pointer; it's been on my list of things to
investigate for a while now!

Regards,

Matt.

-- 
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: delete a file created with puppet

2012-11-21 Thread Jakov Sosic

On 11/21/2012 11:09 AM, David Schmitt wrote:

 This will put the passphrase onto the node every time puppet runs. I do
 not see how that will make it any more secure.

I do not think it will. Exec will run only if /tmp/mykey does not exist,
and in my case it does exist all the time until you delete it manually.
Take a look:


# cat test.pp
exec {'first':
  command = '/bin/echo something  /tmp/mykey',
  creates = '/tmp/mykey',
}

# puppet apply test.pp
/Stage[main]//Exec[first]/returns: executed successfully
Finished catalog run in 0.16 seconds



# cat test2.pp
exec {'second':
  command = '/bin/echo   /tmp/mykey | /usr/bin/tee -a /tmp/mykey2',
  creates = '/tmp/mykey2',
}


# puppet apply test2.pp
/Stage[main]//Exec[second]/returns: executed successfully
Finished catalog run in 0.30 seconds

# cat /tmp/mykey

# cat /tmp/mykey2
#

# puppet apply test.pp
Finished catalog run in 0.10 seconds

# cat /tmp/mykey




-- 
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] Can I create virtual resources with create_resources function

2012-11-21 Thread Jakov Sosic

On 11/15/2012 11:04 PM, Rajul Vora wrote:
 
 I am trying to add ability to add virtual users to
 the git://github.com/erwbgy/puppet-system.git module as I really want

I've run into same exact problem yesterday, and found patch that Nan Liu
mentions..


What I am interested in is when can we expect Puppet 3.1.0? If someone
can answer me :)

Till then I'm manually patching create_resources.rb :-/

-- 
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] hiera forward reverse lookup webservice

2012-11-21 Thread Erik Dalén

I've just created a small web service for doing hiera lookups. It can be 
installed on your puppet master for example and will fetch facts from PuppetDB 
and look up the desired key in hiera.  

That way you don't need to set up hiera and have access to the data anywhere 
else to be able to lookup keys.

It can also do reverse lookups, telling you what hosts has value x for key y. 
That is really slow for lots of hosts though but it does some caching.

Anyway, available at https://github.com/dalen/hieralookup
patches, praise  criticism welcome :)

--  
Erik Dalén


-- 
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: Array from custom function gets flattened

2012-11-21 Thread KomodoDave

Thank you very much for this jcbollinger - the way you've described it 
makes perfect sense.

Dave


On Tuesday, November 20, 2012 8:36:46 PM UTC, jcbollinger wrote:



 On Tuesday, November 20, 2012 8:42:02 AM UTC-6, KomodoDave wrote:

 I'm trying to use my first custom function *prefixPaths*.

 The function is defined in:

 my_module/lib/puppet/parser/functions/prefixPaths.rb


 Listing:

 module Puppet::Parser::Functions
 newfunction(:prefixPaths, :type = :rvalue) do |args|
 args[1].map{|path| #{args[0]}/#{path}}
 end
 end


 It's usage is e.g. *prefixPaths( 'base', [ 'A', 'path/to/B' ] ) = [ 
 'base/A', 'base/path/to/B' ]*
 *
 *
 I'm trying to use it in a Puppet manifest when creating a set of 
 directories on the client:

 $bashScriptDir  = bash-scripts
 $karafScriptDir = karaf-scripts
 $userTypeDir= user-type-resources
 $resourceDirs   = [$bashScriptDir,$karafScriptDir,$userTypeDir]
 file { 'Create common dirs.':
 path = $localPaths,
 ensure = 'Directory'
 }

 However, when I use this the following error results:

 err: Failed to apply catalog: Parameter path failed: File paths must be 
 fully qualified, not 
 '/fuse/common/bash-scripts/fuse/common/karaf-scripts/fuse/common/user-type-resources'
  
 at /etc/puppet/gitmodules/app_fuse/manifests/init.pp:113


 It looks like it's flattening the array.

 I've seen another conversation on here indicating arrays are permitted to 
 be used as custom function return values.

 Would someone be kind enough to indicate what I'm doing wrong?



 Well, you didn't show how the custom function is actually used there, but 
 I guess you omitted a statement of the form

   $localPaths = prefixPaths('/fuse/common', $resourceDirs)

 , right?

 I suspect the problem is not with your function.  Most likely, the array 
 is getting flattened after it is returned.  In fact, I'd be very surprised 
 if the value you assign to your File's 'path' property were not flattened.  
 As far as I know, the ability to declare multiple, similar resources by 
 using an array as the resource title requires the array to be the actual 
 title.  I don't think you get the same result by assigning an array to the 
 resource's namevar (nor do I think you should).

 So, try this:

 # Manage common directories
 file { $localPaths:
   ensure = 'directory'
 }


 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/-/3j35r9hxfYEJ.
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: Array from custom function gets flattened

2012-11-21 Thread KomodoDave

..or should I say - *John*!


On Tuesday, November 20, 2012 2:42:02 PM UTC, KomodoDave wrote:

 I'm trying to use my first custom function *prefixPaths*.

 The function is defined in:

 my_module/lib/puppet/parser/functions/prefixPaths.rb


 Listing:

 module Puppet::Parser::Functions
 newfunction(:prefixPaths, :type = :rvalue) do |args|
 args[1].map{|path| #{args[0]}/#{path}}
 end
 end


 It's usage is e.g. *prefixPaths( 'base', [ 'A', 'path/to/B' ] ) = [ 
 'base/A', 'base/path/to/B' ]*
 *
 *
 I'm trying to use it in a Puppet manifest when creating a set of 
 directories on the client:

 $bashScriptDir  = bash-scripts
 $karafScriptDir = karaf-scripts
 $userTypeDir= user-type-resources
 $resourceDirs   = [$bashScriptDir,$karafScriptDir,$userTypeDir]
 file { 'Create common dirs.':
 path = $localPaths,
 ensure = 'Directory'
 }

 However, when I use this the following error results:

 err: Failed to apply catalog: Parameter path failed: File paths must be 
 fully qualified, not 
 '/fuse/common/bash-scripts/fuse/common/karaf-scripts/fuse/common/user-type-resources'
  
 at /etc/puppet/gitmodules/app_fuse/manifests/init.pp:113


 It looks like it's flattening the array.

 I've seen another conversation on here indicating arrays are permitted to 
 be used as custom function return values.

 Would someone be kind enough to indicate what I'm doing wrong?

 I'm on Puppet version 2.7.6 .

 Sincere thanks for your time. 


-- 
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/-/ZvV7-l2oH4wJ.
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] puppetlabs-lvm and --guess-fstype

2012-11-21 Thread C R Ritson

I'm testing a fedora 17 deployment and am using puppet 2.7.x and 
puppetlabs-lvm-0.1.1. I have a problem in that a filesystem in a logical volume 
is continually trying to get itself created even though it already exists and 
is mounted. It looks as if this might be because there is no longer a 
--guess-fstype option in the mount command which the lvm module attempts to 
use. I'm not sure how to solve this.

Chris Ritson (Computing Officer and School Safety Officer)

Room 707, Claremont Tower,EMAIL: c.r.rit...@ncl.ac.uk
School of Computing Science,  PHONE: +44 191 222 8175
Newcastle University, FAX  : +44 191 222 8232
Newcastle upon Tyne, UK NE1 7RU.  WEB  : http://www.cs.ncl.ac.uk/


-- 
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 Agent on Windows and file paths 32 or 64 Bit

2012-11-21 Thread r0k5t4r

Hi,

I just started using puppet agent on windows 32Bit and my manfiests are 
working good so far. Now when using the same manifests on a 64Bit Windows 
machine I get trouble about the very special Program Files path. :(

Is there a way of using a variable in puppet manifests and the puppet agent 
automatically uses the correct Program Files (x86) folder on 64Bit 
machines? I checked the facts on the windows machine but it seems that 
64Bit is not correctly reported so using a fact to distinguish is not 
possible atm.

I'm using puppet 2.7.13


-- 
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/-/Pxk5e5OmkPIJ.
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: Array from custom function gets flattened

2012-11-21 Thread KomodoDave

In fact I've since realised that the documents state the 'path' parameter 
is the *namevar* for a file resource type.

So what you've said is spot on.

Thank you again.


On Wednesday, November 21, 2012 3:43:01 PM UTC, KomodoDave wrote:

 ..or should I say - *John*!


 On Tuesday, November 20, 2012 2:42:02 PM UTC, KomodoDave wrote:

 I'm trying to use my first custom function *prefixPaths*.

 The function is defined in:

 my_module/lib/puppet/parser/functions/prefixPaths.rb


 Listing:

 module Puppet::Parser::Functions
 newfunction(:prefixPaths, :type = :rvalue) do |args|
 args[1].map{|path| #{args[0]}/#{path}}
 end
 end


 It's usage is e.g. *prefixPaths( 'base', [ 'A', 'path/to/B' ] ) = [ 
 'base/A', 'base/path/to/B' ]*
 *
 *
 I'm trying to use it in a Puppet manifest when creating a set of 
 directories on the client:

 $bashScriptDir  = bash-scripts
 $karafScriptDir = karaf-scripts
 $userTypeDir= user-type-resources
 $resourceDirs   = [$bashScriptDir,$karafScriptDir,$userTypeDir]
 file { 'Create common dirs.':
 path = $localPaths,
 ensure = 'Directory'
 }

 However, when I use this the following error results:

 err: Failed to apply catalog: Parameter path failed: File paths must be 
 fully qualified, not 
 '/fuse/common/bash-scripts/fuse/common/karaf-scripts/fuse/common/user-type-resources'
  
 at /etc/puppet/gitmodules/app_fuse/manifests/init.pp:113


 It looks like it's flattening the array.

 I've seen another conversation on here indicating arrays are permitted to 
 be used as custom function return values.

 Would someone be kind enough to indicate what I'm doing wrong?

 I'm on Puppet version 2.7.6 .

 Sincere thanks for your time. 



-- 
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/-/Mvqv3oodZSwJ.
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: Array from custom function gets flattened

2012-11-21 Thread KomodoDave

Actually this is interesting: the 'path' parameter has a default value of 
the title. So if you don't specify the path yet specify an array for the 
title, I wonder what the internal logic is?

Intriguing...


On Wednesday, November 21, 2012 4:40:38 PM UTC, KomodoDave wrote:

 In fact I've since realised that the documents state the 'path' parameter 
 is the *namevar* for a file resource type.

 So what you've said is spot on.

 Thank you again.


 On Wednesday, November 21, 2012 3:43:01 PM UTC, KomodoDave wrote:

 ..or should I say - *John*!


 On Tuesday, November 20, 2012 2:42:02 PM UTC, KomodoDave wrote:

 I'm trying to use my first custom function *prefixPaths*.

 The function is defined in:

 my_module/lib/puppet/parser/functions/prefixPaths.rb


 Listing:

 module Puppet::Parser::Functions
 newfunction(:prefixPaths, :type = :rvalue) do |args|
 args[1].map{|path| #{args[0]}/#{path}}
 end
 end


 It's usage is e.g. *prefixPaths( 'base', [ 'A', 'path/to/B' ] ) = [ 
 'base/A', 'base/path/to/B' ]*
 *
 *
 I'm trying to use it in a Puppet manifest when creating a set of 
 directories on the client:

 $bashScriptDir  = bash-scripts
 $karafScriptDir = karaf-scripts
 $userTypeDir= user-type-resources
 $resourceDirs   = [$bashScriptDir,$karafScriptDir,$userTypeDir]
 file { 'Create common dirs.':
 path = $localPaths,
 ensure = 'Directory'
 }

 However, when I use this the following error results:

 err: Failed to apply catalog: Parameter path failed: File paths must be 
 fully qualified, not 
 '/fuse/common/bash-scripts/fuse/common/karaf-scripts/fuse/common/user-type-resources'
  
 at /etc/puppet/gitmodules/app_fuse/manifests/init.pp:113


 It looks like it's flattening the array.

 I've seen another conversation on here indicating arrays are permitted 
 to be used as custom function return values.

 Would someone be kind enough to indicate what I'm doing wrong?

 I'm on Puppet version 2.7.6 .

 Sincere thanks for your time. 



-- 
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/-/EYQsbGApncoJ.
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: Pass Array as param to custom provider...

2012-11-21 Thread Jakov Sosic

On 11/13/2012 08:19 PM, Gavin Williams wrote:
 After a quick google, came up with:
 
 #!/usr/bin/env ruby
 
 grades = { Bob = 82,
Jim = 94,
Billy = 58
  }
 
 grades.each do|name,grade|
   puts #{name}: #{grade}
 end
 
 
 So now all I need to do is pull the existing options values and compile
 a hash to compare in the exists?, and use the above in the create...
 
 Quick question on the create - how will it handle one property that
 matches, but one property that doesn't?

I've done a similar mangling (from/to hashes) in my Cobbler module, I
could send it to you so you can learn by example, if you're interested.

But to answer your main point - if the sorted hashes aren't the same,
provider will try to change the state to the new hash.

-- 
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] Best Practices on node declaration

2012-11-21 Thread AnOnJoe

Hello,

I would like to know what are the best pratices in node declaration.

I tried to play with inheritance with failures : 
Here my* puppet/manifest/site.pp*

node basenode {
 class { 'ssh': }
 class { 'ntp': }
 class { 'users': }
 class { 'sudo': }
 }

 node default inherits basenode {
 }

 
 # serv1
 
 node serv1 inherits basenode {
 class { 'sudo' :
 sudoers = sudoers_serv1
 }
 class { 'debug': }
 }


As you can see i have to manage 2 sudoers file : 
One in almost all server, and an other one in my serv1 server

here is my *sudo class*

class sudo ($sudoers=sudoers) {
 package { 'sudo':
 ensure = installed,
 }
 file { '/etc/sudoers':
 source  = puppet://puppetmaster.foo.com/sudo/$sudoers,
 ensure = file,
 mode   = 440,
 owner   = 'root',
 group   = 'root',
 require = Package['sudo'],
 }
 }



Can you tell me what is the best way to resolve that kind of problems.

Thx 

-- 
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/-/zoT3tKXyIUcJ.
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] Best Practices on node declaration

2012-11-21 Thread Jakov Sosic

On 11/21/2012 06:46 PM, AnOnJoe wrote:
 Hello,
 
 I would like to know what are the best pratices in node declaration.
 
 I tried to play with inheritance with failures :
 Here my*puppet/manifest/site.pp*
 
 node basenode {
 class { 'ssh': }
 class { 'ntp': }
 class { 'users': }
 class { 'sudo': }
 }


First of all, don't instant classes like resources... Use include
instead. So this would look like:

node basenode {
  include ssh
  include ntp
  include users
  include sudo
}


 
 node default inherits basenode {
 }
 
 
 # serv1
 
 node serv1 inherits basenode {
 class { 'sudo' :
 sudoers = sudoers_serv1
 }
 class { 'debug': }
 }

When you instance classes like resources, then you cannot instance it
twice. You can only do it once, and you already did it in the basenode.
This is like defining the same resource twice. Your main problem is in
the basenode.


 As you can see i have to manage 2 sudoers file :
 One in almost all server, and an other one in my serv1 server
 
 here is my *sudo class*
 
 class sudo ($sudoers=sudoers) {
 package { 'sudo':
 ensure = installed,
 }
 file { '/etc/sudoers':
 source  =
 puppet://puppetmaster.foo.com/sudo/$sudoers,
 ensure = file,
 mode   = 440,
 owner   = 'root',
 group   = 'root',
 require = Package['sudo'],
 }

You can use Hiera for this purpose. In the hiera yaml manifests you can
just then define something like:

sudo::sudoers: sudoers_serv1

and your class would get the data from hiera. That way it would be
enough to include it into basenode, and you would have opportunity to
set up each node differently without redefining the classes. I really
urge you to invest some time into learning hiera.

-- 
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] bad network causing puppet runs to hang

2012-11-21 Thread Ellison Marks

Thought I'd ask around here before I go file a bug report.

Basically, I have a few machines administered by puppet which have an 
unreliable internet connection. They talk to my puppetmaster on an internal 
network and have NAT through a router to the internet. The NAT doesn't 
always work. When it doesn't, puppet runs start to hang with a python 
script at /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.py 
just never exiting. if I kill it, the run finishes with no changes. 
Sometimes it will exit on it's own after a few hours.

So, anyone else having this issue, or have I found something new.

os: centos 6
puppet: 3.0.1
ruby: 1.8.7
python: 2.6.6

-- 
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/-/huGsYsbVi6UJ.
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: Nginx + passenger + puppetmaster

2012-11-21 Thread Greg Thompson

On Monday, 22 October 2012 11:03:06 UTC+1, Geert Booster wrote:

Hello,

Op donderdag 7 juni 2012 08:44:54 UTC+2 schreef vulzscht het volgende:

i will dig into it a bit more and provide my results here in case of
success

Did you found any solution? I am looking at the same problems, after a
fresh puppetmaster install with passenger, getting:

err: Could not retrieve catalog from remote server: Error 403 on SERVER:
Forbidden request: FQDN(IP.Addr) access to /catalog/fqdn [find] at line 93

./ssl/certs/ca.pem is available...

Regards,

Geert

Hi Geert,

I'm not sure if you are still having this problem but I was suffering from
it myself. I finally found that the problem was due to the following two
lines in my puppet.conf.

ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY

Once removed puppet works fine under nginx. I had noticed that they were
absent in this set of instructions that I was following
http://z0mbix.github.com/blog/2012/03/01/use-nginx-and-passenger-to-power-your-puppet-master/
but
assumed that they needed to be there was the comment says to uncomment when
using passenger. Hope this helps.

Regards,
Greg

--
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/-/aKHa4HPZArkJ.
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] access exported resources in template

2012-11-21 Thread Bart Swedrowski



On Friday, September 7, 2012 2:01:13 PM UTC+1, ctrlc-root wrote:

 Well, 3 years old or not, this is still in the first page of google 
 results haha. I'm running puppet version 2.7.9 and the result of that 
 template is a blank comment line for every instance of the Firewall::Rule 
 type. If I replace 'resource[:comment]' with 'resource.type' then I can 
 confirm that the iteration is actually working, because I see comment lines 
 like this '# Firewall::Rule'. I tried 'resources[comment]', 
 'resources[:comment]', and 'resources.comment' (with this one triggering an 
 error).

 I wish there was some easy way to get an interactive ruby shell running 
 with the same environment so I could actually test this without running 
 puppet apply every time, if I could I probably would have figured it out on 
 my own already. If you don't know what the answer is, could you maybe point 
 me in the general direction of how you would find out? Perhaps a relevant 
 part of the puppet source code? And thanks for answering.


I just got through Google to this post - have you guys managed to find a 
final solution for this? 

-- 
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/-/fBUhRdGElW8J.
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: Fileserver in standalone mode.

2012-11-21 Thread Scott Smerchek

I'm having this same problem. Is there a solution?

On Thursday, May 24, 2012 11:37:12 AM UTC-5, btimby wrote:

 I am using puppet in standalone mode (puppet apply) to test manifests that 
 I also use in a client/server configuration.

 I have everything working as far as files included in modules. I can 
 reference file source as puppet:///modules/modulename/path/to/file.

 However, some files are not part of a module, so for the client/server 
 portion, I just set up a share called files. However, references to these 
 files puppet://files/path/to/files don't work in standalone mode.

 I understand that standalone mode (puppet apply) command can find the 
 module files because you tell it the path to look in (--modulepath 
 argument). Why is there no argument for adding file shares 
 (--fileserver=files:/path/to/files)? Is there another way to achieve this?

 My workaround for now is to simply move the files to a module named files 
 and reference them as puppet:///modules/files/path/to/file, but it seems 
 like there might be a better solution.

 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/-/vNR34Sd6QisJ.
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] yum repo on same machine as Puppet Master?

2012-11-21 Thread Thomas Linkin

Thomas, 

By design, PE will not interfere with the vendor httpd package. With a small 
setup like that, I do not see keeping your repo there as being something you 
shouldn't do. Just be mindful of the non-puppet services you wish to host from 
the master. If there is any insecurity or vulnerability in the extra services 
you host from your master, then Puppet might not be as secure. 

-- 
Tom Linkin
Professional Services Engineer
http://puppetlabs.com/
twitter: @trlinkin


On Wednesday, November 21, 2012 at 2:41 PM, Thomas wrote:

 I'm a relative newbie using Puppet Enterprise 2.5.3 (I know there are new 
 versions)
 
 I currently have my Yum repo served via HTTP on a different machine from my 
 Puppet Master and I'm considering moving my Yum repo to the same machine that 
 runs the Puppet Master. Is that a good, bad or indifferent practice?
 
 My Puppet Master (for now) will manage less than 10 nodes so I'm not worried 
 about performance.
 
 Thanks! Thomas Kenny 
 
 -- 
 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/-/ZYfycYodG_wJ.
 To post to this group, send email to puppet-users@googlegroups.com 
 (mailto:puppet-users@googlegroups.com).
 To unsubscribe from this group, send email to 
 puppet-users+unsubscr...@googlegroups.com 
 (mailto: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] Puppet IPA client setup

2012-11-21 Thread Peter Brown

Hi Johnathan.

I have just started using FreeIPA but I haven't gotten around to setting it
up with Puppet yet.
If you would like some help with testing or extra functionality let me know.
I have CentOS and Fedora servers.
I did find the docs on how to set it up manually so I was going to use
those as a base. (Shall send the link when I get to work)

Pete.


On 22 November 2012 03:07, Johnathan Phan j.p...@ox-consulting.com wrote:

 Hi everyone,

 I have already started documented and building this privately.

 However I refuse to believe that there is not a module for setting up a
 FreeIPA client server on RHEL to authenticate against an existing IPA
 authentication server.

 Has anyone actually already done this? If not I will probable post a link
 to this email with the puppet module I have built.

 Regards

 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/-/QlJ6Kfm888EJ.
 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] Puppet on OpenSuSE SLES

2012-11-21 Thread Ashley Gould

Hello Niels,

I found this thread and I am installing puppet-3.0.1-2.1.x86_64.rpm from
http://download.opensuse.org/repositories/systemsmanagement:/puppet/SLE_11_SP2/

The init script /etc/init.d/puppet in this rpm has an error and will not run on
puppet 3.0, because the script sets the puppet binary to /usr/sbin/puppetd,
which no longer is used.

I have revised the script for my site, but I would like to see this fixed
in the OBS repo as well. Who should I contact to help contribute changes?
I have not use OBS before to maintain packages.

On Mon, Oct 22, 2012 at 08:08:50AM -0700, Niels Abspoel wrote:
If you don't want to compile it yourself:

Look at these:
home project:
https://build.opensuse.org/package/show?package=puppetproject=home%3Aaboe76%3Abranches%3Asystemsmanagement%3Apuppet%3Adevel

devel project maintainer opensuse
https://build.opensuse.org/project/show?project=systemsmanagement%3Apuppet%3Adevel

official maintainer project:
https://build.opensuse.org/package/show?package=puppetproject=systemsmanagement%3Apuppet

Op donderdag 29 maart 2012 15:03:36 UTC+2 schreef Darin Perusich het
volgende:

You can grab the .spec from the build service project or the srpm links
below.

http://download.opensuse.org/repositories/home:/eclipseagent:/puppet/

https://build.opensuse.org/project/show?project=home%3Aeclipseagent%3Apuppet

--
Later,
Darin

On Thu, Mar 29, 2012 at 5:03 AM, r0k5t4r oliver_...@gmx.de javascript:
wrote:
Hi,

would you mind sharing the specfile you have used to build ruby-shadow?

Regards,
Oliver

Am Montag, 12. März 2012 17:46:17 UTC+1 schrieb Jeffrey Watts:

I took the RHEL/EPEL RPMs for ruby-shadow and puppet and rebuilt them
for
SLES. There are very few things that need changing. The RHEL/EPEL RPMs
have really well put together SPECfiles.

I believe I posted the SPECfile diff for puppet to this list a month or
so
ago. You might search the archives. Mostly what I did was comment out
the
Red Hat specific dependencies - it was really easy. You can build
without
Augeas if you're not using it.

Good luck.
Jeffrey.

On Mon, Mar 12, 2012 at 5:19 AM, Julien C.
corn...@gmail.comjavascript:
wrote:

Hi,

I'm a big fan of Puppet and managed to have my company accept it.
However, I'm having issues deploying it (I'm used to the debian version
which works perfectly out of the box) :

- There doesn't seem to be an official repository for Suse (I've seen
it
mentionned in the bugtracker but yum.puppetlabs.com doesn't contain
SUSE
packages).
- I can't find a package for ruby-shadow.
- I can't find a package for augeas either.

I circumvented these problems by installing Puppet by hand (tarball)
and
writing ugly code (execs) to manage config files and user passwords.
However, I'd like to know if I missed anything or if you can suggest
solutions for any of these 3 issues...

--
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/-/z_oXvCuaLJsJ.

To post to this group, send email to
puppet...@googlegroups.comjavascript:
.
To unsubscribe from this group, send email to
puppet-users...@googlegroups.com javascript:.
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/-/jTcQeG0uAvwJ.
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.

-ashley

Did you try poking at it with a stick?

--
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] Announce: Facter 1.6.15-rc1 Available

2012-11-21 Thread Matthaus Owens

Facter 1.6.15-rc1 is a maintenance release candidate in the 1.6.x
branch with bug fixes.

Downloads are available at:
 * Source: https://downloads.puppetlabs.com/facter/facter-1.6.15-rc1.tar.gz

RPMs are available at https://yum.puppetlabs.com/el or /fedora

Rubygem available at http://rubygems.org/gems/facter or by using
the --pre option to gem install.

Debs are available at https://apt.puppetlabs.com

Mac package is available at
https://downloads.puppetlabs.com/mac/facter-1.6.15-rc1.dmg

See the Verifying Puppet Download section at:
 
http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet#Verifying+Puppet+Downloads

Please report feedback via the Puppet Labs Redmine site, using a
affected version of 1.6.15-rc1:
 http://projects.puppetlabs.com/projects/facter/

Release Notes at: https://projects.puppetlabs.com/projects/facter/wiki/Wiki

Fixes targeted at this version in our bug tracker:
http://projects.puppetlabs.com/versions/341

=
## Facter 1.6.15-rc1 Changelog ##
=
Alex Harvey (1):
  0e72145 (#11612) Add support for processorX facts on HP-UX

Francis Gulotta (1):
  6b9ce2e (#17177) Add MTU information to interfaces

Jeff McCune (4):
  b973caf (maint) Add .yardopts file
  0d66362 (#16511) Do not call arp -an on Solaris nodes
  6ef8cce Fixup whitespace in (#17177) Add MTU information to interfaces
  d46b42a (#17177) Fix spec failure when running on Mac OS X

Josh Cooper (2):
  e3da3c7 (#17493) Safer handling of EC2 'open' calls
  b336259 (#17493) Merge rescue blocks

Matthaus Owens (2):
  4b2baab (maint) Remove hard dependency on rspec from Rakefile
  7aaee5e Updating FACTERVERSION for 1.6.15-rc1

Moses Mendoza (3):
  bcbaffd Update ips ruby libdir to use sitelibdir instead of rubylibdir
  2a9c78a Turn on IPS building for facter
  c31cca5 install.rb doesn't support sbindir, so remove it from ips rules

-- 
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: ssh key collection in puppetdb slow queries/blocking nodes

2012-11-21 Thread Jakov Sosic

On 11/15/2012 09:26 PM, Deepak Giridharagopal wrote:
 We (grim_radical, nlew, and cprice) have continued working with Matt
 (sjoeboo) on the #puppet IRC channel over the last few days. Apologies
 for not updating this thread accordingly!
 

jcbollinger asked about documentation of the schema of database, you
seem to missed that part for some reason?

-- 
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 on OpenSuSE SLES

2012-11-21 Thread Darin Perusich

Ashley,

One of the nice things about OBS is you can branch the package,
update it, and submit your changes back and if/once accepted they'll
be built, packed and available in the repo for general consumption.

--
Later,
Darin

On Wed, Nov 21, 2012 at 3:59 PM, Ashley Gould ago...@ucop.edu wrote:
Hello Niels,

I found this thread and I am installing puppet-3.0.1-2.1.x86_64.rpm from
http://download.opensuse.org/repositories/systemsmanagement:/puppet/SLE_11_SP2/

The init script /etc/init.d/puppet in this rpm has an error and will not run
on
puppet 3.0, because the script sets the puppet binary to /usr/sbin/puppetd,
which no longer is used.