Re: [Puppet Users] Puppet Enterprise 3.0 now available!

2013-06-26 Thread DEGREMONT Aurelien

Hello

It is difficult to find what's inside Puppet Enterprise (which puppet 
version, etc...).
I'm particularly interested to understand what was changed to have such 
gain in performances.


Thanks

Aurélien


Le 25/06/2013 15:37, Nigel Kersten a écrit :

Hello puppet-users,

Puppet Enterprise 3.0 is now available now. You can download it now here:
http://puppetlabs.com/misc/pe-files/


This major release introduces the following new capabilities:

* Enhanced performance and scalability: 200% performance boost and 
100% increase in scalability helps you move faster and respond more 
quickly to changing business needs
* New orchestration capabilities: Dynamically discover resources, then 
fully orchestrate complex management operations on large volumes of 
cloud nodes using Puppet Enterprise's orchestration engine.
* Software-defined infrastructure: Automate the management of not just 
compute resources, but also network and storage resources, with Puppet 
Enterprise's unified, software-defined approach


You can get a full overview of all of the new Puppet Enterprise 
capabilities here:

https://puppetlabs.com/puppet/whats-new/

Or review the docs here:
https://docs.puppetlabs.com/pe/3.0/

I'm hosting live technical webinars and demo on Thursday, June 27.
Register today: https://puppetlabs.com/resources/webinars/

We hope you enjoy this release, and looking forward to your feedback!


Nigel Kersten
CTO, Puppet Labs
@nigelkersten


--
You received this message because you are subscribed to the Google 
Groups Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to puppet-users+unsubscr...@googlegroups.com.

To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




--
You received this message because you are subscribed to the Google Groups Puppet 
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Re: Module for tuned-adm

2013-06-26 Thread Romain Pelisse
Provider for this is overkill was my first impression also, but after
fighting a couple of time against my own exec for it, I just said F**k
that, let's make a proper extension. Also, this is very trivial extension
allowed me to demo how to do such extension in small Puppet workshop that
I gave.




On 18 May 2013 16:45, Matthias Saou matth...@saou.eu wrote:

 shameless plug
 You could also have a look at this other module :
 https://forge.puppetlabs.com/thias/tuned
 /shameless plug

 I just had a look at Romain's, and a provider just for this is
 overkill. As much as I hate exec, it's fine here since the profile name
 is exactly contained in a single configuration file. Also, a class is
 best here instead of a definition since it can only be instantiated
 once per node. Lastly, using a class makes it trivial to tune nodes
 using hiera and class parameter auto-lookup in puppet 3.

 Matthias

 banjer jash...@gmail.com wrote:

  Thanks, I was about to roll out a puppet module for tuned-adm and
  found this.  Easy to use and working great in my environment.
 
  Cheers!
 
  On Friday, January 4, 2013 8:25:16 AM UTC-5, Romain PELISSE wrote:
  
   Hi all,
  
   tuned-adm module: https://github.com/rpelisse/puppet-tuned
  
   I'm using
   tuned-adm
 https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Power_Management_Guide/tuned-adm.html
 to
   tune the kernel of the target system according to a profile. I
   first used exec{} to trigger the profile setting but lead to the
   exec{} being ran at every Puppet run which I found, at beast,
   inelegant. I end up doing this module to more and less properly
   implement the exists? method. The module implementation is rather
   rudimentory but still nice to have - if you need it.
  
   (Note: i've googled a bit before doing that and ran into a couple
   of existing Puppet module or code for tuned-adm but they were
   either using exec() internally or just installing the packages and
   nothing more).
   (Final note: Before XMas, I've already submitted a completely
   useless module extension to handle DNS Name, as it turned out
   Puppet supports this out of the box, so I hope this module proposal
   will be a tidbit more useful ! :) )
  
   --
   Romain PELISSE,
   *The trouble with having an open mind, of course, is that people
   will insist on coming along and trying to put things in it --
   Terry Pratchett* Belaran ins Prussia (blog)
   http://blog.wordpress.belaran.eu/ (... finally up and
   running !)
  
 

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users?hl=en.
 For more options, visit https://groups.google.com/groups/opt_out.





-- 
Romain PELISSE,
*The trouble with having an open mind, of course, is that people will
insist on coming along and trying to put things in it -- Terry Pratchett*
Belaran ins Prussia (blog) http://blog.wordpress.belaran.eu/ (...
finally up and running !)

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Dynamically assign Static IP Addresses

2013-06-26 Thread Johan De Wit
We are using LDAP as our ENC, which contains the  network interfaces as 
a subtree of the HOST tree.


The provisioning system (cobbler) uses ldap for the configuration of the 
installation files (autoyast/kisckstart).


Puppet will handle the re-configuration of the network.

I'm trying (getting on very slowly) to write and hiera ldap backend, 
because since  network config is in a subtree, those data is not 
available as global vars.


Just another method ...

Grts

johan



On 06/25/2013 09:33 PM, Worker Bee wrote:
Thanks, Ken.  It will be a secondary interface and it will 'hopefully' 
be a one-time fix.


I appreciate the feedback and will take a look at this!

Jerald; you are absolutely right, this should be a provisioning task 
but, we I have an OPS team who needs to make a one-tme correction on 
exisiting gear.  DHCP is not an option due to limitations in the 
environment.


Thanks again!

Bee


On Tue, Jun 25, 2013 at 3:27 PM, Ken Barber k...@puppetlabs.com 
mailto:k...@puppetlabs.com wrote:


This module from @finch can do networking configuration:
https://forge.puppetlabs.com/adrien/network ... the mac address of a
host/interface can be gleaned from facts.

Is this change going to occur on your primary interface though (the
one you are talking to your puppetmaster on), or is it for some kind
of secondary interface?

On Tue, Jun 25, 2013 at 8:05 PM, Worker Bee beeworke...@gmail.com
mailto:beeworke...@gmail.com wrote:
 I can think of several ways puppet can do this, I was just
wondering if the
 group might have any ideas/suggestions as to best approaches.
 Obviously, we
 are unable to use DHCP in this particular case, or we would.


 On Tue, Jun 25, 2013 at 2:30 PM, Dan White y...@comcast.net
mailto:y...@comcast.net wrote:

 You are describing DHCP reservations.
 That would be something to do with a DHCP server, not
necessarily with
 Puppet

 “Sometimes I think the surest sign that intelligent life exists
elsewhere
 in the universe is that none of it has tried to contact us.”
 Bill Waterson (Calvin  Hobbes)

 
 From: Worker Bee beeworke...@gmail.com
mailto:beeworke...@gmail.com
 To: puppet-users@googlegroups.com
mailto:puppet-users@googlegroups.com
 Sent: Tuesday, June 25, 2013 2:06:05 PM
 Subject: [Puppet Users] Dynamically assign Static IP Addresses


 Hi Everyone;

 I was wondering if anyone has created ot knows of a module that
can be
 used to assign static IP addresses to hosts post build.  The
addresses will
 be static but, need to be assigned based on MAC address.

 Essentially, we have a file with a list of hostnames/mac
addresses.  I
 need to use puppet to assign the correct IP addrsses to the
correct host.
 Stored Configs is not an option.

 I will be grateful for any advice/feedback!

 Thanks!
 Bee

 --
 You received this message because you are subscribed to the
Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from
it, send an
 email to puppet-users+unsubscr...@googlegroups.com
mailto:puppet-users%2bunsubscr...@googlegroups.com.
 To post to this group, send email to
puppet-users@googlegroups.com mailto:puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.



 --
 You received this message because you are subscribed to the
Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from
it, send an
 email to puppet-users+unsubscr...@googlegroups.com
mailto:puppet-users%2bunsubscr...@googlegroups.com.
 To post to this group, send email to
puppet-users@googlegroups.com mailto:puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




 --
 You received this message because you are subscribed to the
Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from
it, send an
 email to puppet-users+unsubscr...@googlegroups.com
mailto:puppet-users%2bunsubscr...@googlegroups.com.
 To post to this group, send email to
puppet-users@googlegroups.com mailto:puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.



--
You received this message because you are subscribed to the Google
Groups Puppet Users group.
To unsubscribe from this group and stop receiving emails from it,
send an email to 

Re: [Puppet Users] Puppet Enterprise 3.0 now available!

2013-06-26 Thread David Schmitt

On 26.06.2013 10:33, DEGREMONT Aurelien wrote:

Hello

It is difficult to find what's inside Puppet Enterprise (which puppet
version, etc...).
I'm particularly interested to understand what was changed to have such
gain in performances.


[Disclaimer: I've never touched PE]

Presumably PE3 is replacing ActiveRecord based storeconfigs with the 
puppetdb backend. That gives so massive performance improvements (for 
people using storeconfigs).



Regards, David



Thanks

Aurélien


Le 25/06/2013 15:37, Nigel Kersten a écrit :

Hello puppet-users,

Puppet Enterprise 3.0 is now available now. You can download it now here:
http://puppetlabs.com/misc/pe-files/


This major release introduces the following new capabilities:

* Enhanced performance and scalability: 200% performance boost and
100% increase in scalability helps you move faster and respond more
quickly to changing business needs
* New orchestration capabilities: Dynamically discover resources, then
fully orchestrate complex management operations on large volumes of
cloud nodes using Puppet Enterprise's orchestration engine.
* Software-defined infrastructure: Automate the management of not just
compute resources, but also network and storage resources, with Puppet
Enterprise's unified, software-defined approach

You can get a full overview of all of the new Puppet Enterprise
capabilities here:
https://puppetlabs.com/puppet/whats-new/

Or review the docs here:
https://docs.puppetlabs.com/pe/3.0/

I'm hosting live technical webinars and demo on Thursday, June 27.
Register today: https://puppetlabs.com/resources/webinars/

We hope you enjoy this release, and looking forward to your feedback!


Nigel Kersten
CTO, Puppet Labs
@nigelkersten


--
You received this message because you are subscribed to the Google
Groups Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send
an email to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.






--
You received this message because you are subscribed to the Google Groups Puppet 
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Re: Access denied for user 'dashboard'@'localhost' to database 'dashboard_production'

2013-06-26 Thread DJames
Make sure you are able to see the schema.

Do a

mysql show tables;


if you dont see the DB, then you need to make the DB. 

On Friday, July 6, 2012 5:08:53 PM UTC-4, Hai wrote:

 followed the instruction for installing dashboard, and created user

 mysql -pmy_password -e CREATE DATABASE dashboard CHARACTER SET 
 utf8;CREATE USER 'dashboard'@'localhost' IDENTIFIED BY 'my_password'; GRANT 
 ALL PRIVILEGES ON dashboard.* TO 'dashboard'@'localhost';

 however, I keep getting access denied error:

 # rake RAILS_ENV=production db:migrate
 (in /usr/share/puppet-dashboard)
 rake aborted!
 Access denied for user 'dashboard'@'localhost' to database 
 'dashboard_production'

 (See full trace by running task with --trace)


 please help!


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Re: Templates see numbers as strings

2013-06-26 Thread jcbollinger


On Tuesday, June 25, 2013 11:06:21 AM UTC-5, Claudio wrote:


 Given the manifest:

 $a = 1
 $b = 1 + 0
 $c = 1.1
 $d = 1.1 + 0
 $result = inline_template(
 a %= @a.class % %= @a %
 b %= @b.class % %= @b %
 c %= @c.class % %= @c %
 d %= @d.class % %= @d %
 )
 notify {
 $result:
 }



 The output is:

 a String 1
 b Fixnum 1
 c String 1.1
 d Float 1.1



 Is this working as intended?



I think so.  Puppet DSL does not require most string literals to be quoted, 
so it can distinguish numeric-form strings from actual numbers only by how 
they are produced or used.  I think it reasonable for Puppet to treat all 
values as strings except where it has specific reason to do otherwise.  
That's not the only possible approach, but I think it's probably the best 
fit for Puppet.

 


 How can I identify number types within the template without adding + 0 
 on the manifest? I'm aware that it's not a good idea to duck-type on 
 templates but I'm still wondering.


It depends on what you mean by that.  Apparently it's not about identifying 
whether Puppet is treating the value as numeric, so I guess it's about 
whether the value is numeric in form.  Perhaps you could do something along 
these lines:

%
  begin
num = Float(@maybe_num)
# It can be interpreted as a number
  rescue
# It's not numeric
  end
 % 

Really, though, this should not be necessary.  The DSL code calling the 
template should know how to use it appropriately (else it has no business 
using it at all).


John

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Disable certain facter facts?

2013-06-26 Thread RichTea
I dont have Facter 1.7 installed right now but it would guess the disk
facts come from one of the factor scripts (maybe in
/opt/puppet/share/puppet/modules/stdlib/lib/facter/) you could make a
manual edit to exclude some of the FS's

--
-- http://23.me.uk/2 --
--Time flies like an arrow; fruit flies like a banana.  --


On 25 June 2013 18:41, Patrick Carlisle patr...@puppetlabs.com wrote:


 Is it possible to tell facter to ignore certain facts?  Couldn't find a
 config file for it and not sure how puppet tells it to gather facts.


 There's no configuration right now. I think you have a pretty reasonable
 case, and you should file a feature request at
 http://projects.puppetlabs.com/projects/facter.

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Puppi parameters in command line

2013-06-26 Thread NewUser5
Hi , 
I am a new puppet user. As i am not used yet to ruby and puppet  I've 
decided to use the puppi module to deploy web applications in my company. 
I ve created some specific define , scripts  etc and I saw recently that it 
was possible to pass options in command  line .

seen from example42 site :

*puppi deploy myapp -i -o version=1.1 source_url=**
http://dev.example42.com/code/my_app*/http://dev.example42.com/code/my_app/quot:
 
Deploys myapp in interactive mode and sets some custom options that 
override the standard Puppet params.
Note that these parameters change according to the script you use (and the 
scripts must honour this override).

I think it would be a good idea to allow operators to launch custom puppi 
deploy commands on demand .. But ..


But i didn't succeed to override my project define parameters .

Would it be possible for someone ( Alessandro for instance  ;)  )  to give 
me an example of a good use of theses parameters and what i have to modify 
to retrieve them ??

Another question :

Is it possible to embeed puppi calls directly in a rb script ?? For example 
, rather than executing puppi via shell, i'd like to include my puppi 
define and call it like this ( sorry for the syntax, i am not ruby 
compliant for the moment :) , but  you get the idea, I hope )

mypuppiwrapper.rb
include puppi:project:war:myapp

puppi:project:war:myapp  deploy 


Hope you understand me !

Thank you a lot !

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Re: Upgrade from 2.7.20 to 2.7.22 breaks puppet-dashboard

2013-06-26 Thread Bas
Hi,

We do have this same issue when upgrading from 3.1.1 to  3.2.2, any ideas?

- Bas


On Thursday, June 20, 2013 11:29:58 PM UTC+2, Joe Benson wrote:

 I upgraded our puppetmaster from 2.7.20 to 2.7.22 and puppet dashboard 
 quit importing reports.  I'm getting a failed task with this error message. 


 undefined method `=' for nil:NilClass 
 Backtracehttp://puppetconsoletest.prod.utah.gov:3000/delayed_job_failures 
  /usr/share/puppet-dashboard/lib/report_transformer.rb:18:in `apply'  
 /usr/share/puppet-dashboard/lib/report_transformer.rb:8:in 
 `apply'  /usr/share/puppet-dashboard/lib/report_transformer.rb:18:in 
 `inject'  /usr/share/puppet-dashboard/lib/report_transformer.rb:7:in 
 `each'  /usr/share/puppet-dashboard/lib/report_transformer.rb:7:in 
 `inject'  /usr/share/puppet-dashboard/lib/report_transformer.rb:7:in 
 `apply'  /usr/share/puppet-dashboard/app/models/report.rb:112:in 
 `create_from_yaml'  /usr/share/puppet-dashboard/app/models/report.rb:90:in 
 `create_from_yaml_file'

 Installed RPMS from yum.puppetlabs.com

 rpm -qa |grep puppet

 puppet-server-2.7.22-1.el5
 puppet-2.7.22-1.el5
 puppet-dashboard-1.2.23-1.el5

 If I back-rev puppet and puppet-server to 2.7.20 it works. 

 Any Ideas?

 Thanks,

 Joe
  

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] use of exec in puppet

2013-06-26 Thread Rahmathulla Badarudeen
Hi,

I've tried to to exec function in puppet for enabling module for apache. 
Here is the code that I am using:

class apache::mod {
exec { a2enmod :

command =  a2enmod proxy_http,
path = /usr/sbin/,
notify = Class[apache::service],
require = Class[apache::install],
}
}

But in agent I'm getting the following error,

notice: /Stage[main]/Sudo/Package[sudo]/ensure: created
err: /Stage[main]/Apache::Mod/Exec[a2enmod]/returns: change from notrun to 
0 failed: sh: 1: env: not found
Could not read /etc/apache2/envvars

notice: /Stage[main]/Apache::Service/Service[apache2]: Dependency 
Exec[a2enmod] has failures: true

Any idea why it is happening like this?

Regards,
Rahmathulla


-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Upgrade from 2.7.20 to 2.7.22 breaks puppet-dashboard

2013-06-26 Thread Bas Toonk
Hi,

We do have this same issue while upgrading from 3.1.1 to  3.2.2, any ideas?
It looks like only reports from 2.6 agents are failing.

- Bas


On Jun 20, 2013, at 11:29 PM, Joe Benson 
joeben...@gmail.commailto:joeben...@gmail.com wrote:

I upgraded our puppetmaster from 2.7.20 to 2.7.22 and puppet dashboard quit 
importing reports.  I'm getting a failed task with this error message.


undefined method `=' for nil:NilClass
Backtracehttp://puppetconsoletest.prod.utah.gov:3000/delayed_job_failures
/usr/share/puppet-dashboard/lib/report_transformer.rb:18:in `apply'
/usr/share/puppet-dashboard/lib/report_transformer.rb:8:in `apply'
/usr/share/puppet-dashboard/lib/report_transformer.rb:18:in `inject'
/usr/share/puppet-dashboard/lib/report_transformer.rb:7:in `each'
/usr/share/puppet-dashboard/lib/report_transformer.rb:7:in `inject'
/usr/share/puppet-dashboard/lib/report_transformer.rb:7:in `apply'
/usr/share/puppet-dashboard/app/models/report.rb:112:in `create_from_yaml'
/usr/share/puppet-dashboard/app/models/report.rb:90:in `create_from_yaml_file'

Installed RPMS from yum.puppetlabs.comhttp://yum.puppetlabs.com/

rpm -qa |grep puppet

puppet-server-2.7.22-1.el5
puppet-2.7.22-1.el5
puppet-dashboard-1.2.23-1.el5

If I back-rev puppet and puppet-server to 2.7.20 it works.

Any Ideas?

Thanks,

Joe


--
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
puppet-users+unsubscr...@googlegroups.commailto:puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to 
puppet-users@googlegroups.commailto:puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.



-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Puppet for Dynamic Environments (Private or Public Clouds)

2013-06-26 Thread Kanthi Narisetti
I am looking for suggestions from puppet experts on using Puppet in Dynamic 
Environments. For example I have a Master/Client setup in a cloud (public 
or private) and I have Dev,Prod,Test,Stage environments where dev,and test 
environments have dynamic guest virtual machines with new host-names etc 
for new instances,

In this scenario how can puppet agent be installed configured 
(bootstrapped) to the golden images which are used as base for new 
instances.

Any pointers to similar use cases and best practices for the same are 
appreciated.

Regards

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Mvn task at end of chained sequence

2013-06-26 Thread Chris Hagan
Hi puppeteers!

I'm just starting out on this journey, and any help, stylistic or 
functional, would be greatly appreciated.

This is a puppet file describing several chained steps, in a linear 
dependent sequence.  The last, having built up all the systemic 
dependencies, is to run a maven web server task.

The output for this task is returns: executed successfully.  But the 
server hasn't been started and when I look at the directory, it's clear 
that the build and compile haven't even been run.  Is it obvious to anyone 
why this exec step says it's finished but doesn't seem to have done?

centos.pp:

Exec { path = [ usr/local/bin, /bin/, /sbin/ , /usr/bin/, 
/usr/sbin/, /srv/apps/jdk-7/bin, /srv/apps/maven/bin, 
/home/vagrant/bin ] }

java::setup { vagrant-jdk7:
  ensure= 'present',
  source= 'jdk-7u25-linux-x64.tar.gz',
  deploymentdir = '/srv/apps/jdk-7',
  user  = 'vagrant',
  pathfile  = '/home/vagrant/.bashrc'
  } -
  maven::setup { vagrant-maven:
ensure= 'present',
source= 'apache-maven-3.0.5-bin.tar.gz',
deploymentdir = '/srv/apps/maven',
user  = 'vagrant',
pathfile  = '/home/vagrant/.bashrc',
} -
package { 'git':
  ensure = installed,
  } -
  exec { open firewall:
command = 'service iptables stop',
} -
file { '/srv/loadShop/':
  ensure  = 'absent',
  force = 'true',
  } -
  vcsrepo { '/srv/loadShop/':
ensure   = latest,
provider = git,
source   = git server url removed,
} -
exec { run application:
  cwd = '/srv/loadShop/loadShop/',
  command = 'mvn jetty:run ',
  environment = 'MAVEN_OPTS=-XX:+CMSClassUnloadingEnabled 
-XX:PermSize=256M -XX:MaxPermSize=512M',
  logoutput = true,
}

Output:

Notice: 
/Stage[main]//Java::Setup[vagrant-jdk7]/File[/var/run/puppet/java_set 
working-vagrant-jdk7/jdk-7u25-linux-x64.tar.gz]/ensure: 
defined content as md5 removed
Notice: 
/Stage[main]//Java::Setup[vagrant-jdk7]/Exec[extract_java-vagrant-jdk7 returns: 
executed successfully
Notice: /Stage[main]//Exec[open firewall]/returns: executed successfully
Notice: /Stage[main]//File[/srv/loadShop/]/ensure: removed
Notice: /Stage[main]//Vcsrepo[/srv/loadShop/]/ensure: Creating repository 
from latest
Notice: /Stage[main]//Vcsrepo[/srv/loadShop/]/ensure: created
Notice: /Stage[main]//Exec[run application]/returns: executed successfully

Notice: Finished catalog run in 162.61 seconds

Thanks in advance for any advice.

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Mvn task at end of chained sequence

2013-06-26 Thread Ken Barber
 The output for this task is returns: executed successfully.  But the
 server hasn't been started and when I look at the directory, it's clear that
 the build and compile haven't even been run.  Is it obvious to anyone why
 this exec step says it's finished but doesn't seem to have done?

The  symbol at the end of the command backgrounds the task in Unix:

 exec { run application:
   cwd = '/srv/loadShop/loadShop/',
   command = 'mvn jetty:run ',
   environment = 'MAVEN_OPTS=-XX:+CMSClassUnloadingEnabled
 -XX:PermSize=256M -XX:MaxPermSize=512M',
   logoutput = true,
 }

Remove it and see what happens instead. Puppet won't track background
tasks like this, and it might be failing.

ken.

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] The handy Grail of Modules Standards

2013-06-26 Thread jcbollinger


On Tuesday, June 25, 2013 4:49:49 PM UTC-5, Alessandro Franceschi wrote:



 On Tuesday, June 25, 2013 9:16:20 PM UTC+2, jcbollinger wrote:


 So, here is a version of puppet-stdmod without class parameterization: 
 https://github.com/jcbollinger/puppet-stdmod .


 Ok, this is what I expected.



Of course it is.  I told you in advance what it was going to be.

 

 Thank you for your time.
 I can definitively argue that this is not fully reusable
   (So please show me a reusable module without parameters and without 
 hiera functions inside, as that would not be reusable by whoever does not 
 use Hiera.)



And I rejected that standard of reusability, for sound reasons that you did 
not rebut.  Since we are closing off that line of discussion, we will have 
to agree to disagree.



 Yes,
 let's go on.
 I guess the first steps should be to identify a coherent naming pattern, 
 even before single names and define more precisely what parameters might be 
 recommended, optional, or considered extensions . 



Before any decision is made on naming patterns -- or at least in 
conjunction with that -- don't you think we should come to grips with the 
patterns of data to which we hope to assign names?  The Google doc does 
address that topic, at least implicitly, but I think we should be satisfied 
with the coverage and characterization of the data, else we cannot be 
confident that the chosen names are the most appropriate ones.  I will 
devote some attention to that, but I hope I will not be the only one to do 
so.


John

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] use of exec in puppet

2013-06-26 Thread David Schmitt

the env binary is in /usr/bin and therefore your path is not wide enough.

/sbin:/bin:/usr/sbin:/usr/bin is a good default. Adding /usr/local/bin 
and /usr/local/sbin  might be good ideas depending on your setup.



Regards, David

On 26.06.2013 15:08, Rahmathulla Badarudeen wrote:

Hi,

I've tried to to exec function in puppet for enabling module for apache.
Here is the code that I am using:

class apache::mod {
exec { a2enmod :

command =  a2enmod proxy_http,
path = /usr/sbin/,
notify = Class[apache::service],
require = Class[apache::install],
}
}

But in agent I'm getting the following error,

notice: /Stage[main]/Sudo/Package[sudo]/ensure: created
err: /Stage[main]/Apache::Mod/Exec[a2enmod]/returns: change from notrun
to 0 failed: sh: 1: env: not found
Could not read /etc/apache2/envvars

notice: /Stage[main]/Apache::Service/Service[apache2]: Dependency
Exec[a2enmod] has failures: true

Any idea why it is happening like this?

Regards,
Rahmathulla


--
You received this message because you are subscribed to the Google
Groups Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send
an email to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




--
You received this message because you are subscribed to the Google Groups Puppet 
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Puppet for Dynamic Environments (Private or Public Clouds)

2013-06-26 Thread Jason Edgecombe

On 06/25/2013 08:26 PM, Kanthi Narisetti wrote:

I am looking for suggestions from puppet experts on using Puppet in Dynamic
Environments. For example I have a Master/Client setup in a cloud (public
or private) and I have Dev,Prod,Test,Stage environments where dev,and test
environments have dynamic guest virtual machines with new host-names etc
for new instances,

In this scenario how can puppet agent be installed configured
(bootstrapped) to the golden images which are used as base for new
instances.

Any pointers to similar use cases and best practices for the same are
appreciated.

Regards



You can parse the Amazon userdata in puppet. It might even show up 
automatically from facter.


Here are some links:
http://dan.carley.co/blog/2012/08/14/bootstrapping-ec2-with-puppet/

http://www.slideshare.net/PuppetLabs/bestofbothworlds
(start at slide 16)

--
You received this message because you are subscribed to the Google Groups Puppet 
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Mvn task at end of chained sequence

2013-06-26 Thread Jason Edgecombe

On 06/25/2013 05:47 PM, Chris Hagan wrote:

Hi puppeteers!

I'm just starting out on this journey, and any help, stylistic or
functional, would be greatly appreciated.

This is a puppet file describing several chained steps, in a linear
dependent sequence.  The last, having built up all the systemic
dependencies, is to run a maven web server task.

The output for this task is returns: executed successfully.  But the
server hasn't been started and when I look at the directory, it's clear
that the build and compile haven't even been run.  Is it obvious to anyone
why this exec step says it's finished but doesn't seem to have done?

centos.pp:

Exec { path = [ usr/local/bin, /bin/, /sbin/ , /usr/bin/,
/usr/sbin/, /srv/apps/jdk-7/bin, /srv/apps/maven/bin,
/home/vagrant/bin ] }

java::setup { vagrant-jdk7:
   ensure= 'present',
   source= 'jdk-7u25-linux-x64.tar.gz',
   deploymentdir = '/srv/apps/jdk-7',
   user  = 'vagrant',
   pathfile  = '/home/vagrant/.bashrc'
   } -
   maven::setup { vagrant-maven:
 ensure= 'present',
 source= 'apache-maven-3.0.5-bin.tar.gz',
 deploymentdir = '/srv/apps/maven',
 user  = 'vagrant',
 pathfile  = '/home/vagrant/.bashrc',
 } -
 package { 'git':
   ensure = installed,
   } -
   exec { open firewall:
 command = 'service iptables stop',
 } -
 file { '/srv/loadShop/':
   ensure  = 'absent',
   force = 'true',
   } -
   vcsrepo { '/srv/loadShop/':
 ensure   = latest,
 provider = git,
 source   = git server url removed,
 } -
 exec { run application:
   cwd = '/srv/loadShop/loadShop/',
   command = 'mvn jetty:run ',
   environment = 'MAVEN_OPTS=-XX:+CMSClassUnloadingEnabled
-XX:PermSize=256M -XX:MaxPermSize=512M',
   logoutput = true,
 }

Output:

Notice:
/Stage[main]//Java::Setup[vagrant-jdk7]/File[/var/run/puppet/java_set 
working-vagrant-jdk7/jdk-7u25-linux-x64.tar.gz]/ensure:
defined content as md5 removed
Notice:
/Stage[main]//Java::Setup[vagrant-jdk7]/Exec[extract_java-vagrant-jdk7 returns:
executed successfully
Notice: /Stage[main]//Exec[open firewall]/returns: executed successfully
Notice: /Stage[main]//File[/srv/loadShop/]/ensure: removed
Notice: /Stage[main]//Vcsrepo[/srv/loadShop/]/ensure: Creating repository
from latest
Notice: /Stage[main]//Vcsrepo[/srv/loadShop/]/ensure: created
Notice: /Stage[main]//Exec[run application]/returns: executed successfully

Notice: Finished catalog run in 162.61 seconds

Thanks in advance for any advice.



I think that /usr/local/bin needs a leading slash:

Exec { path = [  insert slash here usr/local/bin, /bin/, /sbin/ , 
/usr/bin/,
/usr/sbin/, /srv/apps/jdk-7/bin, /srv/apps/maven/bin,
/home/vagrant/bin ] }


--
You received this message because you are subscribed to the Google Groups Puppet 
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Re: White Paper: Migrating from Redhat satellite server to Puppet + Foreman

2013-06-26 Thread Keiran Sweet
Hey There,
Sorry for the late reply on this, been a bit manic this end and am just
catching up.

To be honest, I don't disagree with you really on most of your points. In
regards to the paper, this was that worked for this environment and there
were some other factors behind the scenes (financial, political and
technical) that drove the approach as well, however things like patch and
release management is something that needs to be looked at going forward.

One thing I opted out of talking about in the paper was that we had to deal
with a just as problematic Spacewalk install, other software repos served
random infrastructure hosts and a mess of other kickstart setups for both
RHEL and CentOS glued together with a web of cobbler, because of this I
opted to centralise all the packages from these locations on a simple
Apache based YUM platform, then revisit it when when I got the chance.

I did have Puppet + Satellite running for a while as well, and it did
function as I expected, although it was pretty slow, but as you mention, it
could have been the age and configuration of the platform as well.

I do appreciate you taking the time to provide feedback, my goal really was
to get information out there about what to expect if/when you migrate,
without the admin having to rediscover every step along the way, and your
comments do provide the other side of the coin.

Cheers,

K






On Thu, Jun 13, 2013 at 2:17 PM, Stephen Benjamin skbe...@gmail.com wrote:

 Hi,

 Interesting paper.   For full disclosure, I do work for Red Hat, so you
 know, I could be biased :)

 I agree about Puppet being miles ahead for configuration.  For customers
 who can, I think they should rely on Puppet instead of Satellite for
 configuration, unless they have simple needs.

 But I prefer Satellite's software management.

 There's no reason you can't use Satellite alongside the Foreman or with
 plain Puppet.  I have many customers who do, and I do on my own home
 network.  The hybrid approach works well. You can, of course, leave
 Satellite to setup your own roll your own yum repos with mrepo/grindr, or
 using Pulp.  IMHO, I think you spend a lot of effort for a solution that's
 not as good.

 Cloned channels, for the moment, is really the best way to lock multiple
 systems to the same versions.  A roll-your-own with yum repos makes that
 difficult --  you're left with having multiple copies of everything on the
 filesystem.  For Pulp, you need at least 2 copies of all the software (the
 mrepo/grindr dump, and the internal pulp copy).  Pulp does has similar
 features like cloned channels but last time I looked it wasn't as mature as
 Satellite's. I also remember having quite a bit of difficulty getting
 install trees to import correctly into Pulp.

 Satellite also gives you a really nice view into the latest errata,
 including security updates, and the ability to compare systems and look at
 their package profiles in detail.

 Overall, I think patch management plan needs a closer look in your
 solution.

 As far as the list of complaints about Satellite, I disagree with most.
  There's two pages of complaing about Satellite when admittedly, you're
 running this on a pretty old version of Satellite.  Most of your complaints
 could be addressed by just upgrading or understanding the product better.

 Just a few notes about your complaints:

 * Reporting for software related information is good - you can see the
 full package set on systems, and do a diff of two systems.

 * You can see what systems are not checking in quite easily...

 * Duplicate node finder was available starting with 5.3 (5.4?) although I
 don't think it's perfect. You're better of making sure you're using
 reactivation keys, which I think are now included in the latest RHN
 registration snippet.

 * Inventory? Satellite has *a lot* of information about a system.  For
 custom data you can use key/value pairs.  For example, I have a script that
 syncs Facter info to Satellite:
 https://github.com/stbenjam/spacewalk-facter

 * Speed complaints - TBH, this sounds like there was some underlying
 problems with your Satellite server.  I'd have opened a ticket with Red Hat
 to have them look at it in detail.  Building a new server total time takes
 under 5 minutes for me, including registration to Satellite.

 * Kickstart - host renaming from localhost is easily fixed by writing a
 better kickstart, e.g. using
 https://github.com/stbenjam/junk-drawer/blob/master/kickstart/pre_parse_kernel_cmdline.txtand
 https://github.com/stbenjam/junk-drawer/blob/master/kickstart/cmdline_network



 - Stephen


 On Monday, June 10, 2013 3:04:17 PM UTC+2, Keiran Sweet wrote:

 Hi Everyone,
 I've written a paper that captures the approach that we took when moving
 from Redhat Satellite for configuration and software management to Puppet
 and Foreman (alongside some other assorted technologies).

 The paper contains a number of lessons learnt in the Ruby, Puppet,
 Foreman and Software 

[Puppet Users] Dashboard in Fedora 18

2013-06-26 Thread Brunno Oliveira Prego
Hi,

I tryed to install puppet dashboard in fedora 18, but it doesn't 
avaliable in http://yum.puppetlabs.com/fedora/f18/.
I tryed a version for RHEL 6 but don't work too.
Anyone here have any information about how to install dashboard in 
fedora 18?

Tanks by attention,

Brunno.

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Puppet Enterprise 3.0 now available!

2013-06-26 Thread Moses Mendoza
On Wed, Jun 26, 2013 at 1:33 AM, DEGREMONT Aurelien
aurelien.degrem...@cea.fr wrote:
 Hello

 It is difficult to find what's inside Puppet Enterprise (which puppet
 version, etc...).
 I'm particularly interested to understand what was changed to have such gain
 in performances.

 Thanks

 Aurélien


Hi Aurélien,

Please see http://docs.puppetlabs.com/pe/latest/overview_whats_new.html
to for new component versions, improvements, etc. in PE 3.0.

Moses


 Le 25/06/2013 15:37, Nigel Kersten a écrit :

 Hello puppet-users,

 Puppet Enterprise 3.0 is now available now. You can download it now here:
 http://puppetlabs.com/misc/pe-files/


 This major release introduces the following new capabilities:

 * Enhanced performance and scalability: 200% performance boost and 100%
 increase in scalability helps you move faster and respond more quickly to
 changing business needs
 * New orchestration capabilities: Dynamically discover resources, then
 fully orchestrate complex management operations on large volumes of cloud
 nodes using Puppet Enterprise's orchestration engine.
 * Software-defined infrastructure: Automate the management of not just
 compute resources, but also network and storage resources, with Puppet
 Enterprise's unified, software-defined approach

 You can get a full overview of all of the new Puppet Enterprise
 capabilities here:
 https://puppetlabs.com/puppet/whats-new/

 Or review the docs here:
 https://docs.puppetlabs.com/pe/3.0/

 I'm hosting live technical webinars and demo on Thursday, June 27.
 Register today: https://puppetlabs.com/resources/webinars/

 We hope you enjoy this release, and looking forward to your feedback!


 Nigel Kersten
 CTO, Puppet Labs
 @nigelkersten


 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.



 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.





--
Moses Mendoza
Puppet Labs

Join us at PuppetConf 2013, August 22-23 in San Francisco -
http://bit.ly/pupconf13
Register now and take advantage of the Early Bird discount - save 25%!

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Puppet Enterprise 3.0 now available!

2013-06-26 Thread Nan Liu
On Wed, Jun 26, 2013 at 1:33 AM, DEGREMONT Aurelien 
aurelien.degrem...@cea.fr wrote:

 It is difficult to find what's inside Puppet Enterprise (which puppet
 version, etc...).
 I'm particularly interested to understand what was changed to have such
 gain in performances.


I believe it's Puppet 3.2.2 and MC 2.2.4. Puppet 3 is overall significantly
faster than Puppet 2.7:
http://somethingsinistral.net/blog/the-angry-guide-to-puppet-3/#puppet-3-is-fast

Nan

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] The handy Grail of Modules Standards

2013-06-26 Thread Alessandro Franceschi


On Wednesday, June 26, 2013 3:37:10 PM UTC+2, jcbollinger wrote:



 On Tuesday, June 25, 2013 4:49:49 PM UTC-5, Alessandro Franceschi wrote:



 On Tuesday, June 25, 2013 9:16:20 PM UTC+2, jcbollinger wrote:


 So, here is a version of puppet-stdmod without class parameterization: 
 https://github.com/jcbollinger/puppet-stdmod .


 Ok, this is what I expected.



 Of course it is.  I told you in advance what it was going to be.

  

 Thank you for your time.
 I can definitively argue that this is not fully reusable
   (So please show me a reusable module without parameters and without 
 hiera functions inside, as that would not be reusable by whoever does not 
 use Hiera.)



 And I rejected that standard of reusability, for sound reasons that you 
 did not rebut.  Since we are closing off that line of discussion, we will 
 have to agree to disagree.


Actually I DID rebut and anticipated them. That module would not work on at 
least ten different Puppet setups where I've worked and Hiera was not used.
But, promise, I won't come back on this, let's happily disagree :-) 



 Yes,
 let's go on.
 I guess the first steps should be to identify a coherent naming pattern, 
 even before single names and define more precisely what parameters might be 
 recommended, optional, or considered extensions . 



 Before any decision is made on naming patterns -- or at least in 
 conjunction with that -- don't you think we should come to grips with the 
 patterns of data to which we hope to assign names?  The Google doc does 
 address that topic, at least implicitly, but I think we should be satisfied 
 with the coverage and characterization of the data, else we cannot be 
 confident that the chosen names are the most appropriate ones.  I will 
 devote some attention to that, but I hope I will not be the only one to do 
 so.


Good point.
In the doc I placed some possible examples on where to assign names, but 
more (or remarks on the ones listed) cases are welcomed.
(Let me have your email for an invitation to edit)

Btw, comments and access to:
https://docs.google.com/a/lab42.it/document/d/1D4OqEI5iuGJe63ODU91N6rnFKcxVAg1sAWbaQrGBlWA
is open to everybody, and whoever writes modules should be somehow 
concerned.
At the moment the discussion seems limited to very few people (even if I 
know various others are silently lurking :-)

The same place of the document is to be considered temporary.

Al

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Re: Node collecting its own exported resource

2013-06-26 Thread mpounsett


On Monday, September 17, 2012 10:32:07 AM UTC-4, jcbollinger wrote:



 On Friday, September 14, 2012 11:51:34 AM UTC-5, Jon McKenzie wrote:

 It seems that nodes are not able to collect their own resource, but they 
 can collect every other resource, with a given tag. I've validated that all 
 of the appropriate resources exist 
 in the storeconfigs database.


 Nodes should be able to collect resources they themselves export.  It 
 sounds like you have a good, simple failure case, so I recommend you file a 
 ticket.


Was a ticket ever opened for this?  I've just run into the same issue, but 
searching the ticket database I'm not able to find anything already open 
for it... I'll submit a ticket if there isn't one already.

 

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Re: How to make a package dependant on a class for the repository.

2013-06-26 Thread Stack Kororā
Thank you very much Joe. I think this exactly the path that I need but I am 
having trouble with it.

As I said, I have multiple systems that this repo class watches over. Thus, 
for one of several instances, I have things like:

if $osfamily == 'RedHat' {
class {'repos::epel': }
}

The sub-class epel.pp file configures the EPEL repository for the RHEL, 
Scientific, CentOS, Fedora, ect. However, trying to anchor that caused a 
bunch of odd errors (it is entirely possible I didn't do it right). 

I also have the main configuration in a large case statement that manages 
the main configuration in sub-classes for all operating systems (thus only 
some sub-classes are ever called). This too is causing me some issues. 

I think it is because I don't fully understand how the anchor is supposed 
to work and the examples listed are a bit simplistic with both a require 
and a notify. But what if I need it to require only if it matches certain 
parameters?

I poked around in a few other modules seeing if I could find more examples, 
but came up empty.

Does anyone know where I can view more examples/code for some guidance?

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Re: How to make a package dependant on a class for the repository.

2013-06-26 Thread Wolf Noble
Hi Stack,

here's an example:
https://github.com/wolfspyre/puppet-mysqlx/blob/master/manifests/v55.pp

in this class I create a pair of bookend anchors, and then shove a yumrepo,
and a file resource between them.


Your other classes/resources can then declare a relationship to the end
anchor to establish the relationship.

some gotchas:

- Make sure to include the class declaring the anchor into the class which
has the dependency.
- Remember that you've just permanently established a relationship between
these two classes. This is important to know, and can take you in a
direction that leads to complications down the road.

- It is common to have specific software classes depend on your base-type
'i set up my package repositories, and some other core things that will
happen most everywhere' resources. The caveat here is that modules you
share with the world will NOT have that base class, and as such may have
dependency issues.

- Use the anchor pattern as sparingly as possible. Consider having to use
it like having to resort to an exec. It is occasionally the right tool for
the job, but not usually.

Hope that helps.




On Wed, Jun 26, 2013 at 7:38 PM, Stack Kororā i.am.st...@gmail.com wrote:

 Thank you very much Joe. I think this exactly the path that I need but I
 am having trouble with it.

 As I said, I have multiple systems that this repo class watches over.
 Thus, for one of several instances, I have things like:

 if $osfamily == 'RedHat' {
 class {'repos::epel': }
 }

 The sub-class epel.pp file configures the EPEL repository for the RHEL,
 Scientific, CentOS, Fedora, ect. However, trying to anchor that caused a
 bunch of odd errors (it is entirely possible I didn't do it right).

 I also have the main configuration in a large case statement that manages
 the main configuration in sub-classes for all operating systems (thus only
 some sub-classes are ever called). This too is causing me some issues.

 I think it is because I don't fully understand how the anchor is supposed
 to work and the examples listed are a bit simplistic with both a require
 and a notify. But what if I need it to require only if it matches certain
 parameters?

 I poked around in a few other modules seeing if I could find more
 examples, but came up empty.

 Does anyone know where I can view more examples/code for some guidance?


 Thanks!

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Puppet Enterprise 3.0 now available!

2013-06-26 Thread Nigel Kersten
On Wed, Jun 26, 2013 at 9:41 AM, Nan Liu nan@gmail.com wrote:

 On Wed, Jun 26, 2013 at 1:33 AM, DEGREMONT Aurelien 
 aurelien.degrem...@cea.fr wrote:

 It is difficult to find what's inside Puppet Enterprise (which puppet
 version, etc...).
 I'm particularly interested to understand what was changed to have such
 gain in performances.


 I believe it's Puppet 3.2.2 and MC 2.2.4. Puppet 3 is overall
 significantly faster than Puppet 2.7:

 http://somethingsinistral.net/blog/the-angry-guide-to-puppet-3/#puppet-3-is-fast


Nan and David are both right. It's the Puppet 2.x - 3.x update, as well as
the use of PuppetDB for fact/catalog storage.

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] IPTables Firewall modules Question

2013-06-26 Thread Stack Kororā
Greetings,

I have a question about best practices for the puppet firewall module. I 
have pasted my basic config files below and I am curious about a few things.

* The ports that all nodes share in common I am adding to the 
modules/my_firewall/manifests/init.pp file, but the ports that are specific 
to a node I am adding to the node definition in manifests/site.pp. What 
should I do to prevent the firewall rules from becoming unwieldy in my 
site.pp file? It is fine if there are only a few ports open, but once I 
start adding a lot of ports to the nodes it gets rather big. Any 
suggestions, or is it common to have rather large node definitions?

* The documentation says that the number should be between 000..999. 
However, I made my post.pp deny rule as 9 so that I could make the 
number the port (makes sense to me and help track which port is for what 
purpose; I made it that high because one app has port 27000). The vast 
majority of the time I don't care what order the ports are in, just so long 
as they appear between the pre and post section. It also helps me remember 
which number the rule should be so I don't have duplicate ID numbers. Does 
anyone else label the ID this way? Is there a problem with making this ID 
so large when the documentation lists the max number as 999 (I am guessing 
it was just a large number the author picked at random and not one with 
significant meaning, but I am curious)?

Also, a semi-related question since I am posting the configs...Did I do it 
right? :-D It works for my test cases so far. Mostly just want to check to 
make sure I didn't misunderstand the documentation. So if I missed 
something or if I goofed something up, I would appreciate a response. 

Thanks!

$ cat manifests/site.pp
node 'puppet.test.domain' {
  include my_firewall
  firewall { '8140 Puppet Master':
  port = 8140,
  proto = 'tcp',
  action = accept,
  state = 'NEW',
  }
} 

$ cat modules/my_firewall/manifests/init.pp
class my_firewall () {
  resources { firewall: purge = true }
Firewall {
  before = Class['my_firewall::post'],
  require = Class['my_firewall::pre'],
}
firewall { '80 Webserver':
  port = 80,
  proto = 'tcp',
  action = accept,
  state = 'NEW',
}
include my_firewall::pre
include my_firewall::post
} 

$ cat modules/my_firewall/manifests/pre.pp
class my_firewall::pre {
  Firewall { require = undef, }
  firewall { '000 accept all icmp':
proto = 'icmp',
action = 'accept',
  }-
  firewall { '001 accept all to lo interface':
proto = 'all',
iniface = 'lo',
action = 'accept',
  }-
  firewall { '002 accept related established rules':
proto = 'all',
state = ['ESTABLISHED' , 'RELATED'],
action = 'accept',
  }
} 

$ cat modules/my_firewall/manifests/post.pp
class my_firewall::post {
firewall { '9 drop all':
  proto = 'all',
action = 'drop',
before = undef,
  }
} 

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Re: How to make a package dependant on a class for the repository.

2013-06-26 Thread Stack Kororā
Thanks for the quick reply! And the example!  Let me review this and try it 
out. I will post back if I run into any issues.

Thanks again!

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Re: Exec onlyif/unless with internal functions instead of external commands?

2013-06-26 Thread Amos Shapira
Response inline.

On Monday, 24 June 2013 11:59:06 UTC+10, Michael Dodwell wrote:

 Take a look at http://docs.puppetlabs.com/guides/custom_functions.html you 
 could write your own fuctions to give you something like this.

 Thanks Michael.
I was hoping to add such a functionality to Puppet.

 

 Puppet hasn't really been designed to be low overhead (with more of a 
 focus on simplicity) and i think the least of it's performance problems 
 come from the fact that it uses an external fork for exec checks.


I hope that's not Puppetlabs' view on performance. Performance and resource 
optimisation should be up there at the top of the feature list just like 
security.


 On Sunday, June 23, 2013 8:39:57 PM UTC+10, Amos Shapira wrote:

 Hi,

 A little annoyance about exec that bothers me is that there is no way 
 to use unless/onlyif except with external commands, even if a simple 
 Ruby function could be used to execute the test.

 e.g. onlyif = 'test -d /data' will fork and exec test to do a simple 
 stat(2) which can be done with much less overhead with Ruby's 
 File.directory?('/data').

 How about allowing passing a none-string value to Exec's onlyif/unless 
 attributes, and consider that as the result? If it's a string then it will 
 be treated as today, otherwise it will be treated as a boolean.

 I don't think this will break any backward compatibility since all Exec's 
 currently expect strings to execute.

 Cheers,

 --Amos



-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Re: Exec onlyif/unless with internal functions instead of external commands?

2013-06-26 Thread Amos Shapira
On Monday, 24 June 2013 15:40:14 UTC+10, David Schmitt wrote:

 Functions are executed on the master, not on the agent, so they won't do 
 what you need. 


Yes I keep forgetting that.


 If you really want to run code on the client it has to be a type/provider. 


I was hoping to get something like to be considered to be built into 
Puppet. 


 If it is only test -e, use File%creates. 


I know about creates parameter, but there are other tests which could be 
easily done with a ruby function/system-call (e.g. file size, type, content 
etc). 


 Regards, David 

 On 24.06.2013 03:59, Michael Dodwell wrote: 
  Take a look at 
  http://docs.puppetlabs.com/guides/custom_functions.html you could write 
  your own fuctions to give you something like this. 
  
  Puppet hasn't really been designed to be low overhead (with more of a 
  focus on simplicity) and i think the least of it's performance problems 
  come from the fact that it uses an external fork for exec checks. 
  
  On Sunday, June 23, 2013 8:39:57 PM UTC+10, Amos Shapira wrote: 
  
  Hi, 
  
  A little annoyance about exec that bothers me is that there is no 
  way to use unless/onlyif except with external commands, even if 
  a simple Ruby function could be used to execute the test. 
  
  e.g. onlyif = 'test -d /data' will fork and exec test to do a 
  simple stat(2) which can be done with much less overhead with Ruby's 
  File.directory?('/data'). 
  
  How about allowing passing a none-string value to Exec's 
  onlyif/unless attributes, and consider that as the result? If it's a 
  string then it will be treated as today, otherwise it will be 
  treated as a boolean. 
  
  I don't think this will break any backward compatibility since all 
  Exec's currently expect strings to execute. 
  
  Cheers, 
  
  --Amos 
  
  -- 
  You received this message because you are subscribed to the Google 
  Groups Puppet Users group. 
  To unsubscribe from this group and stop receiving emails from it, send 
  an email to puppet-users...@googlegroups.com javascript:. 
  To post to this group, send email to 
  puppet...@googlegroups.comjavascript:. 

  Visit this group at http://groups.google.com/group/puppet-users. 
  For more options, visit https://groups.google.com/groups/opt_out. 
  
  



-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Is it possible to pass extra flags to Puppet via rspec?`

2013-06-26 Thread Amos Shapira
Hello,

I'm writing my first puppet function rspec test and am having a problem 
which I don't see how to solve.

The function (and the test) involve access to files through the File 
Server. In order for the function (and the test) to work I need to pass 
--fileserverconf=fileserver.conf parameter to Puppet.

So far I haven't found a way to do that.

If I understand the rspec-puppet source 
at https://github.com/rodjek/rspec-puppet/blob/master/lib/rspec-puppet.rb 
correctly then the list of parameters I can pass is limited to the ones 
mentioned in lines 16-22. Am I right?

Does anyone know how can I pass other parameters, or otherwise affect 
Puppet's configuration to set this value?

Thanks,

--Amos

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Is it possible to pass extra flags to Puppet via rspec?`

2013-06-26 Thread Wolf Noble
Hi Amos,

Here's what I've done:

in spec/spec_helper.rb:

Puppet.settings[:confdir] = spec/fixtures

then in the class I was working on, I made a parameter:


class foo(
  $puppetdir = $settings::confdir
  ){
…
}


then in that class's spec test:

require 'spec_helper'
require 'puppetlabs_spec_helper/module_spec_helper'
foo = Puppet.settings[:confdir]

describe 'foo', :type = :class do

let (:params) do { 'puppetdir' = foo } end


…


it stands to reason that a similar method could be employed to feed your
function, but I'm not certain.






On Wed, Jun 26, 2013 at 9:23 PM, Amos Shapira amos.shap...@gmail.comwrote:

 Hello,

 I'm writing my first puppet function rspec test and am having a problem
 which I don't see how to solve.

 The function (and the test) involve access to files through the File
 Server. In order for the function (and the test) to work I need to pass
 --fileserverconf=fileserver.conf parameter to Puppet.

 So far I haven't found a way to do that.

 If I understand the rspec-puppet source at
 https://github.com/rodjek/rspec-puppet/blob/master/lib/rspec-puppet.rbcorrectly
  then the list of parameters I can pass is limited to the ones
 mentioned in lines 16-22. Am I right?

 Does anyone know how can I pass other parameters, or otherwise affect
 Puppet's configuration to set this value?

 Thanks,

 --Amos

 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Is it possible to pass extra flags to Puppet via rspec?`

2013-06-26 Thread Nan Liu
On Wed, Jun 26, 2013 at 7:23 PM, Amos Shapira amos.shap...@gmail.comwrote:

 I'm writing my first puppet function rspec test and am having a problem
 which I don't see how to solve.

 The function (and the test) involve access to files through the File
 Server. In order for the function (and the test) to work I need to pass
 --fileserverconf=fileserver.conf parameter to Puppet.

 So far I haven't found a way to do that.

 If I understand the rspec-puppet source at
 https://github.com/rodjek/rspec-puppet/blob/master/lib/rspec-puppet.rbcorrectly
  then the list of parameters I can pass is limited to the ones
 mentioned in lines 16-22. Am I right?

 Does anyone know how can I pass other parameters, or otherwise affect
 Puppet's configuration to set this value?


Oddly enough, you can't depend on rspec-puppet to configure the settings
for spec test. For example, puppetlab's spec helper configures the
modulepath [1] to include spec/fixtures/modules, but this does not seem to
configure Puppet[:modulepath] setting. For whatever reason, puppet loads
the modules correctly from spec/fixtures/modules, but when you debug the
spec test, it appears to set the module path to:

(rdb:1) p Puppet[:modulepath]
/dev/null/modules:/usr/share/puppet/modules

You can do what Wolf suggested. File server conf is somewhat inconsistent,
since the setting is actually: Puppet[:fileserverconfig].

HTH,

Nan


1.
https://github.com/puppetlabs/puppetlabs_spec_helper/blob/master/lib/puppetlabs_spec_helper/module_spec_helper.rb#L21-L24

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] most current method of configuring cisco (and force10?) devices

2013-06-26 Thread Nan Liu
On Tue, Jun 25, 2013 at 3:30 PM, Wolf Noble w...@wolfspyre.com wrote:

 I've been asked to explore the landscape of network device management via
 puppet.


There are two approaches, either run an agent on the device such as
juniper, or manage through a proxy agent.

in particular, I'm looking to support cisco, and force10 switches.


I'm not sure the cisco device support that's built in is very robust at the
moment. I've heard someone mention a demo of cisco one pk, but haven't seen
the module anywhere.

I know about the network device system, I'm wondering if that's the way to
 go for both cisco and force10, or if there's a better way for one or both?


I'm assuming you are willing to roll your sleeve to implement this.
Emulating what the network admin would type via CLI is going to be brittle
(i.e. ios commands), so I would look at the device API docs to get a better
idea what it takes to manage them.

I've seen the Juniper netdev module, but haven't the gear to play with it.


I think the netdev module is easier to follow than the cisco resource to
get an idea what is needed to implemented a device resource. IMO, you don't
need to adhere to device resource type, and it's actually easier to
implement support through regular puppet resources.

HTH,

Nan

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Puppet Users] Is it possible to pass extra flags to Puppet via rspec?`

2013-06-26 Thread Justin Stoller
It's been a while since I jumped into this code and it's late, forgive me
if I say something naive inline.


On Wed, Jun 26, 2013 at 8:14 PM, Nan Liu nan@gmail.com wrote:

 On Wed, Jun 26, 2013 at 7:23 PM, Amos Shapira amos.shap...@gmail.comwrote:

 I'm writing my first puppet function rspec test and am having a problem
 which I don't see how to solve.

 The function (and the test) involve access to files through the File
 Server. In order for the function (and the test) to work I need to pass
 --fileserverconf=fileserver.conf parameter to Puppet.

 So far I haven't found a way to do that.

 If I understand the rspec-puppet source at
 https://github.com/rodjek/rspec-puppet/blob/master/lib/rspec-puppet.rbcorrectly
  then the list of parameters I can pass is limited to the ones
 mentioned in lines 16-22. Am I right?


Those are the limit you can pass to the RSpec.configure { ... } block in
your spec helper.


 Does anyone know how can I pass other parameters, or otherwise affect
 Puppet's configuration to set this value?

 Have you tried something like:

describe 'foo' do
before do
Puppet[:fileserverconfig] = '/my/path/to/fileserver.conf'
end

your tests

end


 Oddly enough, you can't depend on rspec-puppet to configure the settings
 for spec test. For example, puppetlab's spec helper configures the
 modulepath [1] to include spec/fixtures/modules, but this does not seem to
 configure Puppet[:modulepath] setting. For whatever reason, puppet loads
 the modules correctly from spec/fixtures/modules, but when you debug the
 spec test, it appears to set the module path to:

 (rdb:1) p Puppet[:modulepath]
 /dev/null/modules:/usr/share/puppet/modules


Nan -

In puppetlabs_spec_helper/puppet_spec_helper[1] which was based on a file
in Puppet[2] the confdir and vardir are explicitly set to '/dev/null' which
causes the modulepath you're seeing in Puppet proper.

I believe, however the subject catalog/function that is tested in each
example group (unless you explicitly create a subject yourself) should mask
that value with what ever is passed into RSpec.configure (like the
modulepath setting in module_spec_helper) for its
compilation/initialization[3][4].


 - Justin

1.
https://github.com/puppetlabs/puppetlabs_spec_helper/blob/master/lib/puppetlabs_spec_helper/puppet_spec_helper.rb#L96-L97
2.
https://github.com/puppetlabs/puppet/blob/master/lib/puppet/test/test_helper.rb#L142-L156
3.
https://github.com/rodjek/rspec-puppet/blob/master/lib/rspec-puppet/example/function_example_group.rb#L10
4.
https://github.com/rodjek/rspec-puppet/blob/master/lib/rspec-puppet/support.rb#L80-L97


 You can do what Wolf suggested. File server conf is somewhat inconsistent,
 since the setting is actually: Puppet[:fileserverconfig].

 HTH,

 Nan


 1.
 https://github.com/puppetlabs/puppetlabs_spec_helper/blob/master/lib/puppetlabs_spec_helper/module_spec_helper.rb#L21-L24


 --
 You received this message because you are subscribed to the Google Groups
 Puppet Users group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to puppet-users+unsubscr...@googlegroups.com.
 To post to this group, send email to puppet-users@googlegroups.com.
 Visit this group at http://groups.google.com/group/puppet-users.
 For more options, visit https://groups.google.com/groups/opt_out.






-- 

Join us at PuppetConf 2013, August 22-23 in San Francisco -
http://bit.ly/pupconf13

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.