[Puppet Users] Puppet Agent Configure Error in EC2

[Jithin Xavier]

Hi All,

While I am trying to install/configure Puppet agent from puppet master in 
ec2 getting this error

"root@PuppetMaster:/home/ubuntu# puppet node install 
--install-script=puppet-enterprise 
--installer-answers=/home/ubuntu/puppet-agent-answers 
--installer-payload=/opt/puppet-enterprise-2.7.1-ubuntu-12.04-amd64.tar.gz 
--keyfile=/home/ubuntu/key.pem --login=ubuntu 
--puppetagent-certname=awspuppetnode 10.0.0.9
notice: Waiting for SSH response ...
notice: Waiting for SSH response ... Done
notice: Uploading Puppet Enterprise tarball ...
notice: Uploading Puppet Enterprise tarball ... Done
notice: Installing Puppet ...
warning: Could not determine the remote puppet agent certificate name using 
sudo puppet agent --configprint certname
puppetagent_certname:
  status: success
"

I have couple of doubts related this one
1. How we can configure Puppet with out adding proper hosts entry in host 
file/etc/hostname in ec2.
2. I can able to launch server/instances from Puppet Master but could not 
able to install Puppet Agent from master. How can I achieve this?

Thanks,
Jithin Xavier

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

Re: [Puppet Users] Re: expect like behavior function?

[Felix Frank]

On 03/01/2013 08:10 PM, Corey Osman wrote:
> 5. Use /bin/true or /bin/yes

Again, please don't even bother with /bin/true.

Cheers,
Felix

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

[Puppet Users] Struggling to get Hiera to work

[Jonathan Gazeley]

I'm setting up Hiera in my multi-environment puppetmaster for the first 
time.


I've written /etc/puppet/hiera.yaml, defined the hierarchies and created 
a couple of data files with sample data in them. When queried from the 
commandline, it works:


[jg4461@puppet ~]$ hiera -d -c /etc/puppet/hiera.yaml motd::banner 
environment=netops_jg4461

DEBUG: Mon Mar 04 11:42:29 + 2013: Hiera YAML backend starting
DEBUG: Mon Mar 04 11:42:29 + 2013: Looking up motd::banner in YAML 
backend

DEBUG: Mon Mar 04 11:42:29 + 2013: Looking for data source netops_jg4461
DEBUG: Mon Mar 04 11:42:29 + 2013: Found motd::banner in netops_jg4461
MOTD BANNER for NETOPS


However, when I try to reference this variable in a manifest with syntax 
like this:


class motd {
  file { 'motd':
name=> '/etc/motd',
mode=> '0644',
owner   => 'root',
group   => 'root',
content => hiera('motd::banner'),
  }
}

It fails with this error:

Error: Could not retrieve catalog from remote server: Error 400 on 
SERVER: Could not find data item motd::banner in any Hiera data file and 
no default supplied at 
/home/jg4461/PUPPETROOT/environments/common/modules/motd/manifests/init.pp:7 
on node **.bris.ac.uk


My hiera.yaml points to the right location (the puppet dev environment 
is being served from my homedir on the puppetmaster but all hiera data 
is stored in /etc/puppet/hiera, with the production puppet environment).


What kind of things should I be looking for here?

Thanks,
Jonathan

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

Re: [Puppet Users] Puppet execution hangs for long periods of time

[Felix Frank]

On 03/01/2013 09:32 PM, Josh Cooper wrote:
> 
> Those are the most repeated patterns.
> I don't know much about Windows' core... I hope this help you identify
> the problem 

No, sorry, I'm pretty much a novice with Windows as well.

HeapAlloc sounds like memory allocation issues. Which can be a
performance criteria.

So basically - what Josh said, also probably some kind of ruby profiling
tool? I don't really know what's out there though.

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

Re: [Puppet Users] Re: Long puppet catalog run times on certain nodes after "using pson" is called

[jcbollinger]

On Sunday, March 3, 2013 3:53:29 AM UTC-6, Brice Figureau wrote:
>
> On 01/03/13 22:24, r.yeo wrote: 
> > Passenger settings are currently - 
> > 
> > PassengerHighPerformance on 
> > PassengerUseGlobalQueue on 
> > 
> > PassengerMaxPoolSize 3 
>
> This parameter means you're allowing only 3 puppet clients to talk to 
> your master at any time. 
>
> I can understand why you've set it up this low, because essentially a 
> puppet master is a CPU bound process, so your master host might not be 
> able to compile more than 3 catalog at one time. 
>
>
I think you're missing the key characteristics of the problem:

   1. The error does not occur during catalog compilation.  That's fast 
   (enough) in all the failure cases.  Instead, the failure occurs during 
   retrieval of 'sourced' files.
   2. On failing nodes, *all* the file retrievals exhibit the same delay.
   3. File retrieval delays are always within a few milliseconds of 75s.

If the problem arose from congestion at the master then the delays would be 
less consistent from file to file and from run to run, and they would 
sometimes affect catalog compilation.


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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: troubleshooting missing facts when run as service?

[jcbollinger]

On Friday, March 1, 2013 10:18:46 AM UTC-6, Trammael wrote:
>
>
> RHEL6 x86_64, Puppet master 2.7.18, clients 2.7.19. 
>
> One of my nodes reports: 
>
> Could not retrieve catalog from remote server: Error 400 on SERVER: 
> Duplicate declaration: Package[undef] is already declared in file 
> /etc/puppet/modules/initial_config/manifests/basic_packages.pp at line 22; 
> cannot redeclare at /etc/puppet/modules/authconfig/manifests/init.pp:7 on 
> node wp-prd.library.northwestern.edu 
>
> However, this only happens when Puppet runs as a service, "puppet agent 
> --test" runs complete fine. 
>
> Packages are specified on a case statement with a trivial custom fact for 
> major RH release[1] 
>
> My guess that during a run as a service, that fact isn't processed, but 
> during a "puppet agent --test" it is.  Any tips on how I might troubleshoot 
> this discrepancy? 
>


You have at least two packages, declared in different modules, whose names 
are not being set as you intend.  The error message tells you [two of] the 
manifests involved, and you would do well to look at the Package 
declarations in those manifests.  The problematic declarations probably 
have this form:

package { $some_module::some_class::some_var:
  # maybe some parameters
}

You should also ensure that all 'case' statements such as the two in the 
manifest fragment you presented have 'default' clauses that catch 
unexpected circumstances and signal you.  For instance, they could execute 
the fail() function to trigger a parse error with a message describing what 
the unexpected fact value was.  Do not let unhandled cases fall through 
unless you intend to do so.  (And where you do intend to do so, be sure to 
document it for yourself.)


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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] AWS OpsWorks Puppet support

[James Turnbull]

Hi all

If you are interested in Puppet support for AWS OpsWorks it'd really
help us if you let Amazon know here:

https://forums.aws.amazon.com/forum.jspa?ref_=tsm_1_tw_s_aws_mihccc&forumID=153

That you're interested in this support.

Thanks

James

-- 
James Turnbull
1-503-734-8571
To schedule a meeting with me: http://doodle.com/jamtur01

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

[Puppet Users] Re: Package and unless

[jcbollinger]

On Friday, March 1, 2013 2:00:24 PM UTC-6, Tiago Cruz wrote:
>
> Hello all!
>
> I would like to install one package, but only with some condition was ok, 
> like:
>
>  package { "nagios-plugins-basic":
> ensure => "1.4.15-personal1",
> unless => "test `ls -ld /opt/nrpe* 2>/dev/null | wc -l` -ge 1",
>   }
>
> but this not work =/
>
> Could not retrieve catalog from remote server: Error 400 on SERVER: 
> Invalid parameter unless at 
> /etc/puppet/modules/nagios/manifests/ubuntu.pp:13 on node 
> domu-12-31-39-0c-24-ce.compute-1.internal
>
> How can I do this?
>
>
If you must do that, then you need to create a custom fact (it's not 
difficult) to report on the condition you want to test (for example, the 
output of `ls -ld /opt/nrpe* 2>/dev/null | wc -l).  Then put your Package 
declaration in an 'if' or 'case' block that selects the desired behavior 
based on the fact value.

With that said, you are probably going about this the wrong way.  It is 
usually better to centralize decisions about how nodes are supposed to be 
configured on the master.  In this case, that would mean Puppet knows, 
based on essential characteristics of the node such as its name, network, 
etc., not only whether the nagios plugins should be present, but also 
whether nrpe should be present.  It can then ensure *both* are installed if 
they are supposed to be there (or that they are absent otherwise).

Also, you should consider whether you are making unnecessary work for 
yourself.  It may be that you are duplicating work that your package 
management system would be happy to do for you.


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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Parameters using other parameters

[jcbollinger]

On Sunday, March 3, 2013 8:00:35 AM UTC-6, Andrei Burd wrote:
>
> Hi, i'm writing a define to custom apache configuration, with nagios 
> check, using Geppeto.
>
> I want to define a parameter to check specific web page for ssl, because 
> not all the site are available trough SSL, just couple of pages. 
> I'm using previously declared parameters to build the whole string:
>
> The thing is it's working great, but Geppeto marks it as uninitialized 
> variable:
>
> define platform::create (
>
> ...
> $ssl_iface = $::ipaddress,
> $ssl_page = "/",
> $nagioscheckssl = "check_https_other_string_sane!${ssl_iface}!
> www.${name}!${ssl_page}!${name}!200"
>  
> <---marked as error/uninitialized
> 
> ]) {...}
> @hlindberg Pointed that it's miracle that it's working, and it's a mistake 
> and should not work.
>
> Please advice is it really not suppose to work and should i do other ways, 
> or to change the Geppetto behavior ?
>


Gepetto is right to flag an error.  Puppet does not support parameter 
defaults that use the values of other parameters of the same class or 
definition.  It does not flag a parse error at present, but the results are 
undefined.  Based on how I think the implementation works, you got lucky on 
a 33% chance that your default value would be interpreted as you intended.  
There is no guarantee that it will continue to work on a different version 
of Puppet or of the Ruby underneath, and it is likely to break if you add, 
remove, or rename parameters.


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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] CFP: UCMS '13 (San Jose - June 24)

[Ashley Penney]

Hi all,

I made the mistake of agreeing to help organize a conference and so now I'm
circling the user groups of all the majorconfiguration management tools
with my cap in hand begging for talks.

It's going to be in San Jose as part of a week of USENIX conferences and
we're looking for interesting uses of conf mgmt or anything else cool to
talk about.

You can find more information at:

https://www.usenix.org/conference/ucms13/call-for-participation

I personally would love to hear from anyone who has an awesome
infrastructure testing setup or interesting testing setup and so if that's
you then I beg you to consider presenting a talk.  I think it's something
that the Puppet community skimps on very often and would be great to get
the word out that testing is useful!

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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Beta release of puppetdbquery module 1.0

[Erik Dalén]

I've released version 1.0.0-pre1 of the dalen-puppetdbquery module, it includes 
the old functions against the PuppetDB api version 1.0. But also some entirely 
new functions that will query the PuppetDB api v2.0 (in puppetdb 1.1 and up).  

These new functions borrow the syntax from Dan Bode's ruby-puppetdb, but are 
entirely rewritten to make use of the 2.0 API.

It now uses a lexer and parser written in rex & racc (ruby versions of lex & 
yacc) to compile a high level query language into PuppetDB queries.

An example of a high level query would be:
Class[Apache]{service_enable=true} and (osfamily=Redhat or osfamily=Debian)

That would find any host with the apache class (notice though that class names 
have to be capitalized in queries) with the parameter service_enable => true 
and osfamily red hat or debian. It does normal operator precedence, so a 
parenthesis is required around that or-statement.

The three new query functions are:
* query_nodes
* query_facts
* query_resources

So far only query_nodes and query_facts accept the new query language. In all 
three functions an array argument instead of string will be treated as a "raw" 
puppetdb query.

Anyway, please test it and send me feedback (dalen on freenode). The old 
functions are left intact but deprecated, so it shouldn't affect any existing 
code using the older functions.

--  
Erik Dalén


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

Re: [Puppet Users] Re: Long puppet catalog run times on certain nodes after "using pson" is called

[Brice Figureau]

On Mon, 2013-03-04 at 06:09 -0800, jcbollinger wrote:
> 
> 
> On Sunday, March 3, 2013 3:53:29 AM UTC-6, Brice Figureau wrote:
> On 01/03/13 22:24, r.yeo wrote: 
> > Passenger settings are currently - 
> > 
> > PassengerHighPerformance on 
> > PassengerUseGlobalQueue on 
> > 
> > PassengerMaxPoolSize 3 
> 
> This parameter means you're allowing only 3 puppet clients to
> talk to 
> your master at any time. 
> 
> I can understand why you've set it up this low, because
> essentially a 
> puppet master is a CPU bound process, so your master host
> might not be 
> able to compile more than 3 catalog at one time. 
> 
> 
> I think you're missing the key characteristics of the problem:
>  1. The error does not occur during catalog compilation.  That's
> fast (enough) in all the failure cases.  Instead, the failure
> occurs during retrieval of 'sourced' files.

I know that the problems appears while trying to get a file resource.

What I was saying is that with such low concurrency allowed on the
master side, there are great chances to have large queue forming in the
case of several lengthy operations (like catalog compilation), and thus
slow metadata retrieval for the other poor node.

Let's take a simple example to show what I really meant:

Concurrency is set at 3, with 4 nodes.

A checks in
B checks in a couple of seconds after
C checks in a couple of seconds after
D has to wait.

Now assuming all hosts take the same time to compile, and the machine is
able to provide enough CPU time for 3 compilation at the same time,
then:

A will gets its catalog
D can now run, because a free "concurrency" slot is available
A will now apply its catalog
A requests for file metadata will wait for at least B to finish its
catalog execution, because the concurrency is at 3.

Rinse & repeat

>  1. On failing nodes, all the file retrievals exhibit the same
> delay.
>  2. File retrieval delays are always within a few milliseconds of
> 75s.
> If the problem arose from congestion at the master then the delays
> would be less consistent from file to file and from run to run, and
> they would sometimes affect catalog compilation.

Well, I've seen stranger things to happen :)

Only the OP can tell us if there is queueing or not, but with this
limited concurrency and depending on the number of checking in clients
that's certainly something to check.
-- 
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!

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

[Puppet Users] Windows MSIs and detecting version changes.

[Nathan Shirlberg]

Puppet Package for windows MSI correctly detects whether the Package is 
installed or not, but will not detect that the new MSI file is newer and 
thus the Package needs to be updated.  My seems almost identical 
to http://projects.puppetlabs.com/issues/13104. Which was closed a year 
ago...  I am using Puppet Community 3.1.0

I want to use Puppet to deploy our software internally.  We run mostly .net 
applications and are coming from an in-house deployment script that is 
lacking in several features that Puppet is really strong in.  My plan is to 
append an MSI generation to the end of each build and then use Puppet to 
selectively install the application(s).  I have created MyApplication.msi 
(version 1.0.1) and a "later" release MyApplicaiton.msi (version 1.0.2).

My Puppet manifest is as follows:
package { 'MyApplication':
  ensure  => installed,
  source  => 
'C:\ProgramData\PuppetLabs\puppet\etc\modules\MyApplication.msi',
  install_options => { 'INSTALLDIR' => 'C:\...\MyApplication' },
}
When I run version 1.0.1, Puppet detects that the Package is missing and 
installs it appropriately.  When I replace the msi with the new version and 
run Puppet, I expect that Puppet would recognize that the Package installed 
is version 1.0.1 and the MSI provided is version 1.0.2 and thus install the 
new version. I have tried setting ensure to be the specific version of the 
new MSI, but that gets an error because Windows Package does not implement 
Versionable.  Any thoughts or suggestions about using this method of 
deployment with Puppet?

I am considering: 
1) modify the 
source
 to 
recognize the versions and require the install
2) aborting the MSI and train developers to write puppet manifests that 
utilize the windows resources directly (files, services, scheduled tasks, 
etc)
3) treating each version as it's own unique package and script the build to 
ensure => absent for the old versions and ensure => installed for the 
latest version

 

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

[Puppet Users] Auto remove certificate from puppet master host

[Roman Alekseev]

Hi,

Does anybody know how to perform auto removing certificate of host which is 
unreachable some period?

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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Error while remotely installing agents on puppet clients

[guptasachin1112mrt]

I had installed puppet master and client on two different machines. machine 
A has puppet master and machine B has client. both are centos6 64 bit 
machines.
Machine B (client) is successfully connected to master (machine A). My aim 
is to install New Relic agent (server monitorinig tool) on different 
client. I had installed new reliec agent on machine A and trying to build a 
module so that I can deploy new Relic agent remotely to my clients. right 
now I have only one client but there can be n number of clients.

steps carried out on puppetmaster Machine A

a) I had created a new module mcollective under /etc/puppet/modules 
directory. 

 b) under manifests, I had created a init.pp with the follwoing contents

#Module: mcollective
#
# Class: mcollective
# Description:
# This class does it all.
#
# Files:
# /etc/yum.repos.d/newrelic.repo
#
#
class mcollective {
$my_repo = 'newrelic_repo'
 if $my_repo { include "mcollective::${my_repo}" }
$my_install = 'install'
 if $my_install { include "mcollective::${my_install}" }
}

class mcollective::newrelic_repo {
file { '/etc/yum.repos.d/newrelic.repo':
 owner => "root",
 group => "root",
 mode => 644,
 source => 'puppet:///modules/mcollective/newrelic.repo',
}
}
class mcollective::install {
exec { 'Installing newrelic-repo':
 command => 'yum -y install newrelic-repo*',
 timeout => 600,
 }
}

c) I had also copied newrelic.repo from /etc/yum.repos.d/newrelic.repo to 
/etc/puppet/modules/manifests

d) under files diretcory, I had created sites.pp as 

import 'mcollective'

node 'basenode' {
include mcollective
include mcollective::newrelic_repo
include mcollective::install
}

node 'WA19487ORACLE01' inherits basenode {
license_key => 'd15ff577e5f27e071fe9b2d6809b9f2950fe87d1',
}
e)  here I have called module and passed the license_key for the node.

f) I have restarted my puppetmaster(machine A) and puppet (machine B). when 
I checked /varlog/messages/ of machine A and machine B, new reliec agent is 
not getting deployed on machine B (clinet).
I think my puppet client is  not able to retrieve the informatiojn from 
puppet master. when I tried to run puppet agent --test on client machine, I 
am gettingt the error message
 
[root@WA19487ORACLE01 ~]# puppet agent --test
notice: Ignoring --listen on onetime run
info: Retrieving plugin
err: /File[/var/lib/puppet/lib]: Failed to generate additional resources 
using 'eval_generate': hostname was not match with the server certificate
err: /File[/var/lib/puppet/lib]: Could not evaluate: hostname was not match 
with the server certificate Could not retrieve file metadata for 
puppet://WA19487PUPPET01/plugins: hostname was not match with the server 
certificate
err: Could not retrieve catalog from remote server: hostname was not match 
with the server certificate
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
Time:
 Last run: 1362381429
err: Could not send report: hostname was not match with the server 
certificate
Please post your suggestions to help me out.
 
Thanks 
Sachin 

 

 

 

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

[Puppet Users] Problem while Installing software (agent) from puppetmaster to clients

[guptasachin1112mrt]

I had installed puppet master and client on two different machines. machine 
A has puppet master and machine B has client. both are centos6 64 bit 
machines.
Machine B (client) is successfully connected to master (machine A). My aim 
is to install New Relic agent (server monitorinig tool) on different 
clients. I had installed new relic agent on machine A and trying to build a 
module so that I can deploy new relic agent remotely to my clients. right 
now I have only one client but there can be n number of clients.

steps carried out on puppetmaster Machine A

a) I had created a new module mcollective under /etc/puppet/modules 
directory. 

 under manifests, I had created a init.pp with the follwoing contents

#Module: mcollective
#
# Class: mcollective
# Description:
# This class does it all.
#
# Files:
# /etc/yum.repos.d/newrelic.repo
#
#
class mcollective {
$my_repo = 'newrelic_repo'
 if $my_repo { include "mcollective::${my_repo}" }
$my_install = 'install'
 if $my_install { include "mcollective::${my_install}" }
}

class mcollective::newrelic_repo {
file { '/etc/yum.repos.d/newrelic.repo':
 owner => "root",
 group => "root",
 mode => 644,
 source => 'puppet:///modules/mcollective/newrelic.repo',
}
}

class mcollective::install {
exec { 'Installing newrelic-repo':
 command => 'yum -y install newrelic-repo*',
 timeout => 600,
 }
}

b)  I had also copied newrelic.repo from /etc/yum.repos.d/newrelic.repo to 
/etc/puppet/modules/manifests

c) under files diretcory, I had created sites.pp as 

import 'mcollective'

node 'basenode' {
include mcollective
include mcollective::newrelic_repo
include mcollective::install
}

node 'WA19487ORACLE01' inherits basenode {
license_key => 'd15ff577e5f27e071fe9b2d6809b9f2950fe87d1',
}
d)  here I have called module and passed the license_key for the node.
e) I had restarted my puppetmaster(machine A) and puppet (machine B). when 
I checked /varlog/messages/ of machine A and machine B, new reliec agent is 
not getting deployed on machine B (clinet).
 
f)  my client is not able to retervie the catalog from puppet master. it 
throws following error  when i run puppet agent --test on clinet I am 
getting the result as
[root@WA19487ORACLE01 ~]# puppet agent --test
notice: Ignoring --listen on onetime run
info: Retrieving plugin
err: /File[/var/lib/puppet/lib]: Failed to generate additional resources 
using 'eval_generate': hostname was not match with the server certificate
err: /File[/var/lib/puppet/lib]: Could not evaluate: hostname was not match 
with the server certificate Could not retrieve file metadata for 
puppet://WA19487PUPPET01/plugins: hostname was not match with the server 
certificate
err: Could not retrieve catalog from remote server: hostname was not match 
with the server certificate
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
Time:
 Last run: 1362381429
err: Could not send report: hostname was not match with the server 
certificate
please post your suggestions to help me out.
 
Thanks
Sachin 

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

Re: [Puppet Users] Re: Can puppet report the console output from service foo status?

[Felix Frank]

Oh, I will :-)

Have you made sure the package is installed prior to the attempt of
starting the service (i.e., does the service require the package?)

The easiest way to go about the problem would be to replace the service
resource with an exec for the sake of debugging (under all other
circumstances, it's lousy design, though).
In the exec, you can specify logoutput => "on_failure" to have puppet
write the output to console or log.

HTH,
Felix

On 03/01/2013 10:24 PM, Ellison Marks wrote:
> Post the actual manifest, or we can only offer conjectures.
> 
> On Friday, March 1, 2013 11:20:26 AM UTC-8, Larry Fast wrote:
> 
> I have an odd problem. The first time I install my new package,
> puppet comes back with "Execution of '/sbin/service chirp_fe start'
> returned 1:"   When I run this command manually and on all
> subsequent puppet runs it succeeds. 
> 
> So I'm looking for a way to capture the console output from the
> invocation of /sbin/service chirp_fe start.   Is there something I
> can turn on in Puppet to capture this output? 

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

Re: [Puppet Users] Pattern for managing software versions?

[Schofield]

On Friday, March 1, 2013 7:46:33 PM UTC-5, Brendan O'Bra wrote:
>
>  I use hiera to externalize the versions, like this:
> package{'jdk':
> ensure => hiera('jdk_version','present'),
> require => [ YumRepo['someyumrepo'] ],
> }
>
> And then just deliver yaml based on environment/version/whatever
>

With this pattern, how do you handle use cases where two different versions 
of the JDK are required on a node and the potential for different 
configurations of the JDK such as different policy files? 

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

[Puppet Users] Using Puppet with Windows MSIs

[Nathan Shirlberg]

I want to use Puppet to manage deployment of internal .Net software.  The 
CI build can generate a versioned MSI file and push that out to Puppet.  I 
am creating an MSI with the same name, but different versions for each 
release.  Puppet detects the missing Package and properly installs the new 
Package from MSI.  However, Puppet does not detect that a new MSI needs to 
replace the already installed package.  My problem seems to be the same as  
this 
closed issue .  I am running 
3.1.0.

My plan for deployment has been to have each CI build create the 
appropriately versioned MSI files and deploy them to Puppet as desired. 
 Then, let Puppet compare the MSI versions to the versions already 
installed and install the new MSI if necessary.

Do I have a simple bug in my implementation or do I have a bad strategy.  I 
am considering the following:
1) Modify puppet windows package source to compare versions installed to 
the version of the MSI.
2) Abort the MSI strategy and have each build generate a manifest that uses 
the windows resources directly to complete the install (file, service, 
scheduled task, IIS, etc).  I think I will need to create an Assembly 
resource that can install dlls to the GAC.
3) Put the version number as part of the package name.  Thus forcing Puppet 
to manage each version as a separate package.  I'd rather not do this 
because it will mean generating quite a bit of manifest code as part of the 
build to ensure that previous versions are uninstalled and adding the new 
version to the manifest.

Thanks,
Nathan

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

[Puppet Users] Re: Windows MSIs and detecting version changes.

[Nathan Shirlberg]

I am sorry to spam the board here, but I did not realize that the post was 
held for moderation and then tried a similar post again.  Please disregard 
this post and reply to this 
one. 
https://groups.google.com/forum/?fromgroups=#!topic/puppet-users/NRYgzNW7ihc

On Monday, March 4, 2013 10:11:01 AM UTC-6, Nathan Shirlberg wrote:
>
> Puppet Package for windows MSI correctly detects whether the Package is 
> installed or not, but will not detect that the new MSI file is newer and 
> thus the Package needs to be updated.  My seems almost identical to 
> http://projects.puppetlabs.com/issues/13104. Which was closed a year 
> ago...  I am using Puppet Community 3.1.0
>
> I want to use Puppet to deploy our software internally.  We run mostly 
> .net applications and are coming from an in-house deployment script that is 
> lacking in several features that Puppet is really strong in.  My plan is to 
> append an MSI generation to the end of each build and then use Puppet to 
> selectively install the application(s).  I have created MyApplication.msi 
> (version 1.0.1) and a "later" release MyApplicaiton.msi (version 1.0.2).
>
> My Puppet manifest is as follows:
> package { 'MyApplication':
>   ensure  => installed,
>   source  => 
> 'C:\ProgramData\PuppetLabs\puppet\etc\modules\MyApplication.msi',
>   install_options => { 'INSTALLDIR' => 'C:\...\MyApplication' },
> }
> When I run version 1.0.1, Puppet detects that the Package is missing and 
> installs it appropriately.  When I replace the msi with the new version and 
> run Puppet, I expect that Puppet would recognize that the Package installed 
> is version 1.0.1 and the MSI provided is version 1.0.2 and thus install the 
> new version. I have tried setting ensure to be the specific version of the 
> new MSI, but that gets an error because Windows Package does not implement 
> Versionable.  Any thoughts or suggestions about using this method of 
> deployment with Puppet?
>
> I am considering: 
> 1) modify the 
> source
>  to 
> recognize the versions and require the install
> 2) aborting the MSI and train developers to write puppet manifests that 
> utilize the windows resources directly (files, services, scheduled tasks, 
> etc)
> 3) treating each version as it's own unique package and script the build 
> to ensure => absent for the old versions and ensure => installed for the 
> latest version
>
>  
>

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

Re: [Puppet Users] Re: defaultto in hash property not obeyed

[Jakov Sosic]

On 02/25/2013 03:55 PM, jcbollinger wrote:
> 
> It looks like you are stumbling over a Ruby syntax ambiguity.  The
> fragment "{}" can be either an empty hash or an empty block.  Because
> the 'defaultto' method can accept a block, Ruby resolves the ambiguity
> in favor of that interpretation.  I think it will work better (and also
> be clearer) if you instead write
> 
> defaultto Hash.new


Thank you, that did it! Really an ambiguity... :)

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

Re: [Puppet Users] Beta release of puppetdbquery module 1.0

[Dan Bode]

On Mon, Mar 4, 2013 at 7:59 AM, Erik Dalén wrote:

> I've released version 1.0.0-pre1 of the dalen-puppetdbquery module, it
> includes the old functions against the PuppetDB api version 1.0. But also
> some entirely new functions that will query the PuppetDB api v2.0 (in
> puppetdb 1.1 and up).
>
> These new functions borrow the syntax from Dan Bode's ruby-puppetdb, but
> are entirely rewritten to make use of the 2.0 API.
>

I also wanted to make sure that Pieter Loubser and RI Pienaar also got a
shout out for helping put together the initial grammar for ruby-puppetdb
(it heavily borrowed from mcollective's syntax, and Piter built the initial
parser)


>
> It now uses a lexer and parser written in rex & racc (ruby versions of lex
> & yacc) to compile a high level query language into PuppetDB queries.
>
> An example of a high level query would be:
> Class[Apache]{service_enable=true} and (osfamily=Redhat or osfamily=Debian)
>
> That would find any host with the apache class (notice though that class
> names have to be capitalized in queries) with the parameter service_enable
> => true and osfamily red hat or debian. It does normal operator precedence,
> so a parenthesis is required around that or-statement.
>
> The three new query functions are:
> * query_nodes
> * query_facts
> * query_resources
>
> So far only query_nodes and query_facts accept the new query language. In
> all three functions an array argument instead of string will be treated as
> a "raw" puppetdb query.
>
> Anyway, please test it and send me feedback (dalen on freenode). The old
> functions are left intact but deprecated, so it shouldn't affect any
> existing code using the older functions.
>
> --
> Erik Dalén
>
>
> --
> 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.
>
>
>

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

[Puppet Users] Re: Struggling to get Hiera to work

[Ellison Marks]

Where are you setting your environment?

On Monday, March 4, 2013 3:49:14 AM UTC-8, Jonathan Gazeley wrote:
>
> I'm setting up Hiera in my multi-environment puppetmaster for the first 
> time. 
>
> I've written /etc/puppet/hiera.yaml, defined the hierarchies and created 
> a couple of data files with sample data in them. When queried from the 
> commandline, it works: 
>
> [jg4461@puppet ~]$ hiera -d -c /etc/puppet/hiera.yaml motd::banner 
> environment=netops_jg4461 
> DEBUG: Mon Mar 04 11:42:29 + 2013: Hiera YAML backend starting 
> DEBUG: Mon Mar 04 11:42:29 + 2013: Looking up motd::banner in YAML 
> backend 
> DEBUG: Mon Mar 04 11:42:29 + 2013: Looking for data source 
> netops_jg4461 
> DEBUG: Mon Mar 04 11:42:29 + 2013: Found motd::banner in netops_jg4461 
> MOTD BANNER for NETOPS 
>
>
> However, when I try to reference this variable in a manifest with syntax 
> like this: 
>
> class motd { 
>file { 'motd': 
>  name=> '/etc/motd', 
>  mode=> '0644', 
>  owner   => 'root', 
>  group   => 'root', 
>  content => hiera('motd::banner'), 
>} 
> } 
>
> It fails with this error: 
>
> Error: Could not retrieve catalog from remote server: Error 400 on 
> SERVER: Could not find data item motd::banner in any Hiera data file and 
> no default supplied at 
> /home/jg4461/PUPPETROOT/environments/common/modules/motd/manifests/init.pp:7 
>
> on node **.bris.ac.uk 
>
> My hiera.yaml points to the right location (the puppet dev environment 
> is being served from my homedir on the puppetmaster but all hiera data 
> is stored in /etc/puppet/hiera, with the production puppet environment). 
>
> What kind of things should I be looking for here? 
>
> Thanks, 
> Jonathan 
>

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

[Puppet Users] puppet-master --compile, output as pson?

[Elad Shmitanka]

is there a way to use the command:
>
> puppet master --compile <*nodename*>

and have the output in PSON and not JSON? 

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

[Puppet Users] Community Badges

[Miguel Di Ciurcio Filho]

Hi there,

What happened with the community logos and badges that were available
at this URL:

https://puppetlabs.com/community/badges/

The link is still on the top menu item Community on PuppetLabs' website.

Regards,

Miguel

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

[Puppet Users] Re: Community Badges

[Dawn Foster]

On Mon, Mar 4, 2013 at 11:08 AM, Miguel Di Ciurcio Filho
 wrote:
> Hi there,
>
> What happened with the community logos and badges that were available
> at this URL:
>
> https://puppetlabs.com/community/badges/
>
> The link is still on the top menu item Community on PuppetLabs' website.

Hi Miguel,

We recently removed this page, since most of those badges are very old
and out of date. It looks like the navigation link was never removed.
I'm hoping to get some new ones designed, but we just haven't had a
chance to do that yet.

Thanks,
Dawn Foster
Puppet Community Lead
http://puppetlabs.com/community

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

[Puppet Users] I moved my modules and manifest directory in puppet master.

[JGonza1]

I also made the changes below in the puppet.conf file to tell puppet where 
to look for the the modules and manifests. I then restart the puppet master 
then ran puppet  command to apply changes to a puppet client it did not 
find anything to change just got these three lines "info: Caching catalog 
for pdlnx-adpt03.kareoprod.ent, info: Applying configuration version 
'1362084986', notice: Finished catalog run in 0.33 seconds". WWhen I put 
the modules and manifests back in the original place puppet works. Is there 
anywhere else where I need to change the path to the modules?
 
 
Changes that I made to puppet.conf file to point to the ne location of the 
modules and manifest.
 
  # The default value is '$confdir/manifests'.
#manifestdir = /etc/puppet/manifests
manifestdir = /etc/puppet2/manifests
 
 
 # The search path for modules, as a list of directories separated by the 
system path separator character. (Th
e POSIX path separator is ':', and the Windows path separator is ';'.)
# The default value is '$confdir/modules:/usr/share/puppet/modules'.
#modulepath = /etc/puppet/modules:/usr/share/puppet/modules
  modulepath = /etc/puppet2/modules:/usr/share/puppet/modules
 
 

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

[Puppet Users] Configure One Host to Not Get Client Configuration, but Instead the Server Config Best Practices

[phundisk]

I have been doing something with puppet that is working for me 100% but I 
am not sure this is the best way to be doing things and wanted to see what 
the community feels about it and if anyone has any suggestions.  This 
problems relates to me having a common 'base' class which I put common 
server configuration in to be distributed to all my servers.  The example I 
am using is with NTP clients and NTP server.

In my base class I have something like this:
  "include ntp"

The issue with this is that the NTP clients and servers need to have 
different ntp.conf files.  For example, I want the NTP clients to be 
configured to use the local NTP server as their NTP server, and my local 
NTP server to use CentOS's NTP servers.  I have been using some basic if 
else logic to deal with this to give it the appropriate server or client 
file.  Is this the best way to do this?  Are there better ways to do this 
besides doing an 'include ntp::client' for every node in my nodes.pp.  I 
like my nodes.pp to be clean and organizes.

*class ntp inherits ntp::params* {
  package { "ntp":
ensure => "installed"
  }
  
  # Black magic to automatically detect the NTP servers and set them as 
servers
  # This works by the params class. If that server's IP is in the 
ntp_servers array,
  # it will be setup as an NTP server.
  if $::ipaddress in $ntp_servers {
  # NTP Server Stuff
  file { "/etc/ntp.conf":
owner => 'root',
group => 'root',
mode => 0444,
source => ["puppet:///modules/ntp/ntp.conf.$::hostname", 
"puppet:///modules/ntp/ntp.conf.server"],
require => Package["ntp"],
  }
  file { "/etc/ntp/step-tickers":
owner => 'root',
group => 'root',
mode => 0444,
source => "puppet:///ntp/step-tickers.server",
require => Package["ntp"],
  }
  }
  else{
  # This is for regular NTP clients
file {"/etc/ntp.conf":
owner => 'root',
group => 'root',
mode => 0444,
require => Package["ntp"],
content => template("ntp/ntp.conf.erb"),
}
file {'/etc/ntp/step-tickers':
owner => 'root',
group => 'root',
mode => 0444,
require => Package["ntp"],
content => template("ntp/step-tickers.erb"),
}
  }

  service { "ntpd":
enable => true,
ensure => "running",
hasrestart => true,
hasstatus => true,
require => Package["ntp"],
  }
  
  exec { "ntpd restart":
path => ["/etc/init.d"],
subscribe => [
File["/etc/ntp/step-tickers"]
],
refreshonly => true,
  }
}

*class ntp::params* {
  case $::environment {
  'production': { $ntp_servers = ['192.168.20.103','192.168.20.115'] }
  default: { $ntp_servers = 
['192.168.5.10','192.168.10.248','192.168.10.247' ] }
  }
}



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

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

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

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To 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.

Re: [Puppet Users] I moved my modules and manifest directory in puppet master.

[Keith Burdis]

Perhaps Puppet is not using the puppet.conf file you think it is. Try
running:

  # puppet agent --configprint confdir

- Keith
 On 4 Mar 2013 20:49, "JGonza1"  wrote:

> I also made the changes below in the puppet.conf file to tell puppet where
> to look for the the modules and manifests. I then restart the puppet master
> then ran puppet  command to apply changes to a puppet client it did not
> find anything to change just got these three lines "info: Caching catalog
> for pdlnx-adpt03.kareoprod.ent, info: Applying configuration version
> '1362084986', notice: Finished catalog run in 0.33 seconds". WWhen I put
> the modules and manifests back in the original place puppet works. Is there
> anywhere else where I need to change the path to the modules?
>
>
> Changes that I made to puppet.conf file to point to the ne location of the
> modules and manifest.
>
>   # The default value is '$confdir/manifests'.
> #manifestdir = /etc/puppet/manifests
> manifestdir = /etc/puppet2/manifests
>
>
>  # The search path for modules, as a list of directories separated by the
> system path separator character. (Th
> e POSIX path separator is ':', and the Windows path separator is ';'.)
> # The default value is '$confdir/modules:/usr/share/puppet/modules'.
> #modulepath = /etc/puppet/modules:/usr/share/puppet/modules
>   modulepath = /etc/puppet2/modules:/usr/share/puppet/modules
>
>
>
> --
> 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.
>
>
>

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

[Puppet Users] Register or submit a talk for PuppetConf 2013

[Dawn Foster]

Here are a few details about PuppetConf 2013
* Where: Historic Fairmont Hotel in San Francisco
* When: August 22-23, 2013
* Registration: The first 150 tickets sold will be available at a 35%
discount: http://puppetconf2013.eventbrite.com/
* Details: http://puppetconf.com/

We are also looking for people to submit talks on a variety of topics
that range from how-to information for beginners to advanced topics
for experts and everything in between.

Here are a few examples of what we would like to see:
* Introductory topics for getting started with Puppet, modules, or
other technologies.
* Tips and tricks for using Puppet, MCollective, PuppetDB, Razor,
Hiera, Facter, etc.
* Case studies with details about how you use Puppet in your
environment. What worked, what didn’t.
* Using Puppet to solve problems related to release management,
continuous delivery, application release automation and similar
processes.
* Interesting new technologies and how they can be used with Puppet.
* Related technologies, like Vagrant and Logstash, that Puppet users
should know about.
* Using Puppet in the cloud with OpenStack, AWS, Rackspace, Eucalyptus, etc.
* Using Puppet with virtualization software, like VMware, Hyper-V,
KVM, Citrix/Xen, etc.
* Advanced Puppet topics and using the related technologies in new and
interesting ways.
* DevOps culture, process and tools along with how to make working in
operations a better experience.

Learn more about submitting a proposal:
http://puppetconf.com/speakers/speaker-proposal/

We are also looking for people to sponsor the event if your company
wants to get more involved in PuppetConf:
http://puppetconf.com/sponsors/

Thanks,
Dawn Foster
Puppet Community Lead
http://puppetlabs.com/community

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

[Puppet Users] Re: I moved my modules and manifest directory in puppet master.

[JGonza1]

I ran the command puppet agent --configprint confdir on both the master and 
the agetn and got the below for both. On the puppet master that is where 
the puppet.conf file is in /etc/puppet directory.
 
[root@ct-eng-pup puppet]# puppet agent --configprint confdir
/etc/puppet
[root@ct-eng-pup puppet]# ll /etc/puppet
total 2092
-rw-r--r--.   1 root   root  2552 Sep  7 00:14 auth.conf
-rw-r--r--.   1 root   root 0 Sep  8 16:07 fileserver.conf
drwxr-xr-x.   3 root   root  4096 Mar  1 17:33 manifests
drwxr-xr-x. 192 root   puppet4096 Feb 27 13:45 modules
-rw-r--r--.   1 root   root61 Sep  7 14:29 namespaceauth.conf
-rw-r--r--.   1 root   root 41346 Feb 28 12:49 puppet.conf
-r-xr-xr-x.   1 root   root  2599 Sep 20 11:09 puppetd
drwxrwx--x.   8 puppet root  4096 Sep  7 00:17 ssl
 
[root@pdlnx-adpt03 ~]# puppet agent --configprint confdir
/etc/puppet
[root@pdlnx-adpt03 ~]# ll /etc/puppet
total 8
-rw-r--r--. 1 root root 2552 Nov 12 13:52 auth.conf
drwxrwx--x. 7 root root 4096 Nov 12 13:58 ssl

On Monday, March 4, 2013 12:49:31 PM UTC-8, JGonza1 wrote:

> I also made the changes below in the puppet.conf file to tell puppet where 
> to look for the the modules and manifests. I then restart the puppet master 
> then ran puppet  command to apply changes to a puppet client it did not 
> find anything to change just got these three lines "info: Caching catalog 
> for pdlnx-adpt03.kareoprod.ent, info: Applying configuration version 
> '1362084986', notice: Finished catalog run in 0.33 seconds". WWhen I put 
> the modules and manifests back in the original place puppet works. Is there 
> anywhere else where I need to change the path to the modules?
>  
>  
> Changes that I made to puppet.conf file to point to the ne location of the 
> modules and manifest.
>  
>   # The default value is '$confdir/manifests'.
> #manifestdir = /etc/puppet/manifests
> manifestdir = /etc/puppet2/manifests
>  
>  
>  # The search path for modules, as a list of directories separated by the 
> system path separator character. (Th
> e POSIX path separator is ':', and the Windows path separator is ';'.)
> # The default value is '$confdir/modules:/usr/share/puppet/modules'.
> #modulepath = /etc/puppet/modules:/usr/share/puppet/modules
>   modulepath = /etc/puppet2/modules:/usr/share/puppet/modules
>  
>  
>

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

[Puppet Users] Re: Configure One Host to Not Get Client Configuration, but Instead the Server Config Best Practices

[Ellison Marks]

In general, the pattern to use here would be to use hiera. It allows 
separation of manifest and data. In your case, instead of having 
conditional logic in the class itself, at compilation time the master would 
look up the value for a variable, say ntp::server, in a hierarchy of data. 
For the master, this would return the centos servers, and for everyone 
else, it would return the master. Then you manage ntp.conf as a template 
instead of a static file.



On Monday, March 4, 2013 12:57:23 PM UTC-8, phundisk wrote:
>
> I have been doing something with puppet that is working for me 100% but I 
> am not sure this is the best way to be doing things and wanted to see what 
> the community feels about it and if anyone has any suggestions.  This 
> problems relates to me having a common 'base' class which I put common 
> server configuration in to be distributed to all my servers.  The example I 
> am using is with NTP clients and NTP server.
>
> In my base class I have something like this:
>   "include ntp"
>
> The issue with this is that the NTP clients and servers need to have 
> different ntp.conf files.  For example, I want the NTP clients to be 
> configured to use the local NTP server as their NTP server, and my local 
> NTP server to use CentOS's NTP servers.  I have been using some basic if 
> else logic to deal with this to give it the appropriate server or client 
> file.  Is this the best way to do this?  Are there better ways to do this 
> besides doing an 'include ntp::client' for every node in my nodes.pp.  I 
> like my nodes.pp to be clean and organizes.
>
> *class ntp inherits ntp::params* {
>   package { "ntp":
> ensure => "installed"
>   }
>   
>   # Black magic to automatically detect the NTP servers and set them as 
> servers
>   # This works by the params class. If that server's IP is in the 
> ntp_servers array,
>   # it will be setup as an NTP server.
>   if $::ipaddress in $ntp_servers {
>   # NTP Server Stuff
>   file { "/etc/ntp.conf":
> owner => 'root',
> group => 'root',
> mode => 0444,
> source => ["puppet:///modules/ntp/ntp.conf.$::hostname", 
> "puppet:///modules/ntp/ntp.conf.server"],
> require => Package["ntp"],
>   }
>   file { "/etc/ntp/step-tickers":
> owner => 'root',
> group => 'root',
> mode => 0444,
> source => "puppet:///ntp/step-tickers.server",
> require => Package["ntp"],
>   }
>   }
>   else{
>   # This is for regular NTP clients
> file {"/etc/ntp.conf":
> owner => 'root',
> group => 'root',
> mode => 0444,
> require => Package["ntp"],
> content => template("ntp/ntp.conf.erb"),
> }
> file {'/etc/ntp/step-tickers':
> owner => 'root',
> group => 'root',
> mode => 0444,
> require => Package["ntp"],
> content => template("ntp/step-tickers.erb"),
> }
>   }
> 
>   service { "ntpd":
> enable => true,
> ensure => "running",
> hasrestart => true,
> hasstatus => true,
> require => Package["ntp"],
>   }
>   
>   exec { "ntpd restart":
> path => ["/etc/init.d"],
> subscribe => [
> File["/etc/ntp/step-tickers"]
> ],
> refreshonly => true,
>   }
> }
>
> *class ntp::params* {
>   case $::environment {
>   'production': { $ntp_servers = ['192.168.20.103','192.168.20.115'] }
>   default: { $ntp_servers = 
> ['192.168.5.10','192.168.10.248','192.168.10.247' ] }
>   }
> }
>
>
>
> _
> This email and any files transmitted with it are confidential and intended 
> solely for the addressee.  If you received this email in error, please do 
> not disclose the contents to anyone; kindly notify the sender by return 
> email and delete this email and any attachments from your system.
>
> © 2011 Currensee Inc. is a member of the National Futures Association 
> (NFA) Member ID 0403251 | Over the counter retail foreign currency (Forex) 
> trading may involve significant risk of loss. It is not suitable for all 
> investors and you should make sure you understand the risks involved before 
> trading and seek independent advice if necessary. Performance, strategies 
> and charts shown are not necessarily predictive of any particular result 
> and past performance is no indication of future results. Investor returns 
> may vary from Trade Leader returns based on slippage, fees, broker spreads, 
> volatility or other market conditions.
>
> Currensee Inc | 54 Canal St 4th Floor | Boston, MA 02114 | +1.617.624.3824
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To 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.

Re: [Puppet Users] Re: I moved my modules and manifest directory in puppet master.

[Keith Burdis]

Ok so Puppet is reading /etc/puppet/puppet.conf. The timestamp on this file
shows is hasn't been changed for a few days though.

Is the output of:

# puppet agent --configprint moduledir
# puppet agent --configprint manifestdir

on the master what you expect?

Perhaps you have a permissions / ownership issue. Try:

  # chown -R puppet:puppet /etc/puppet /etc/puppet2

Also see http://docs.puppetlabs.com/guides/configuring.html

  - Keith

On 4 Mar 2013 21:16, "JGonza1"  wrote:

> I ran the command puppet agent --configprint confdir on both the master
> and the agetn and got the below for both. On the puppet master that is
> where the puppet.conf file is in /etc/puppet directory.
>
> [root@ct-eng-pup puppet]# puppet agent --configprint confdir
> /etc/puppet
> [root@ct-eng-pup puppet]# ll /etc/puppet
> total 2092
> -rw-r--r--.   1 root   root  2552 Sep  7 00:14 auth.conf
> -rw-r--r--.   1 root   root 0 Sep  8 16:07 fileserver.conf
> drwxr-xr-x.   3 root   root  4096 Mar  1 17:33 manifests
> drwxr-xr-x. 192 root   puppet4096 Feb 27 13:45 modules
> -rw-r--r--.   1 root   root61 Sep  7 14:29 namespaceauth.conf
> -rw-r--r--.   1 root   root 41346 Feb 28 12:49 puppet.conf
> -r-xr-xr-x.   1 root   root  2599 Sep 20 11:09 puppetd
> drwxrwx--x.   8 puppet root  4096 Sep  7 00:17 ssl
>
> [root@pdlnx-adpt03 ~]# puppet agent --configprint confdir
> /etc/puppet
> [root@pdlnx-adpt03 ~]# ll /etc/puppet
> total 8
> -rw-r--r--. 1 root root 2552 Nov 12 13:52 auth.conf
> drwxrwx--x. 7 root root 4096 Nov 12 13:58 ssl
>
> On Monday, March 4, 2013 12:49:31 PM UTC-8, JGonza1 wrote:
>
>> I also made the changes below in the puppet.conf file to tell puppet
>> where to look for the the modules and manifests. I then restart the puppet
>> master then ran puppet  command to apply changes to a puppet client it did
>> not find anything to change just got these three lines "info: Caching
>> catalog for pdlnx-adpt03.kareoprod.ent, info: Applying configuration
>> version '1362084986', notice: Finished catalog run in 0.33 seconds". WWhen
>> I put the modules and manifests back in the original place puppet works. Is
>> there anywhere else where I need to change the path to the modules?
>>
>>
>> Changes that I made to puppet.conf file to point to the ne location of
>> the modules and manifest.
>>
>>   # The default value is '$confdir/manifests'.
>> #manifestdir = /etc/puppet/manifests
>> manifestdir = /etc/puppet2/manifests
>>
>>
>>  # The search path for modules, as a list of directories separated by the
>> system path separator character. (Th
>> e POSIX path separator is ':', and the Windows path separator is ';'.)
>> # The default value is '$confdir/modules:/usr/share/**
>> puppet/modules'.
>> #modulepath = /etc/puppet/modules:/usr/**share/puppet/modules
>>   modulepath = /etc/puppet2/modules:/usr/**share/puppet/modules
>>
>>
>>
>  --
> 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.
>
>
>

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

[Puppet Users] Re: I moved my modules and manifest directory in puppet master.

[JGonza1]

I ran the commands and I see that puppt is still pointing to /etc/puppet 
not /etc/puppet2 for both modules and manifests, see below.
 
[root@ct-eng-pup etc]# puppet agent --configprint manifestdir
/etc/puppet/manifests
[root@ct-eng-pup etc]# puppet agent --configprint modulepath
/etc/puppet/modules:/usr/share/puppet/modules
[root@ct-eng-pup etc]#
 

On Monday, March 4, 2013 12:49:31 PM UTC-8, JGonza1 wrote:

> I also made the changes below in the puppet.conf file to tell puppet where 
> to look for the the modules and manifests. I then restart the puppet master 
> then ran puppet  command to apply changes to a puppet client it did not 
> find anything to change just got these three lines "info: Caching catalog 
> for pdlnx-adpt03.kareoprod.ent, info: Applying configuration version 
> '1362084986', notice: Finished catalog run in 0.33 seconds". WWhen I put 
> the modules and manifests back in the original place puppet works. Is there 
> anywhere else where I need to change the path to the modules?
>  
>  
> Changes that I made to puppet.conf file to point to the ne location of the 
> modules and manifest.
>  
>   # The default value is '$confdir/manifests'.
> #manifestdir = /etc/puppet/manifests
> manifestdir = /etc/puppet2/manifests
>  
>  
>  # The search path for modules, as a list of directories separated by the 
> system path separator character. (Th
> e POSIX path separator is ':', and the Windows path separator is ';'.)
> # The default value is '$confdir/modules:/usr/share/puppet/modules'.
> #modulepath = /etc/puppet/modules:/usr/share/puppet/modules
>   modulepath = /etc/puppet2/modules:/usr/share/puppet/modules
>  
>  
>

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

Re: [Puppet Users] Re: PuppetDB queue problem

[Ken Barber]

Any progress today?

On Fri, Mar 1, 2013 at 9:00 AM, ak0ska  wrote:
> Yes, maybe not. The next step will be to recreate it from scratch.
>
>
> On Friday, March 1, 2013 5:47:06 PM UTC+1, Ken Barber wrote:
>>
>>
>> Well, I don't think a vacuum will help you - I imagine something is
>> wrong with the schema right now or some data migration failed during
>> upgrade. Esp. if you had migration issues from your custom PuppetDB.
>> Of course I can't prove this with so little knowledge - but it
>> certainly does raise a red flag.
>>
>> The only other option is to compare the schemas with a known good one,
>> and compare the database data to try and find the fault. This however
>> is prone to error and might be time-consuming. Recreating the database
>> sounds like a far more reliable option with a lot more guarantees
>> around it.
>>
>> 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?hl=en.
> 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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: I moved my modules and manifest directory in puppet master.

[Keith Burdis]

What section of /etc/puppet/puppet.conf is your moduledir etc set in? This
should be in [main] or [master] - see the 'Config Blocks' section in the
docs.

Alternatively perhaps the master has not actually been restarted somehow
and is still using the old config.

  - Keith
On 4 Mar 2013 21:54, "JGonza1"  wrote:

> I ran the commands and I see that puppt is still pointing to /etc/puppet
> not /etc/puppet2 for both modules and manifests, see below.
>
> [root@ct-eng-pup etc]# puppet agent --configprint manifestdir
> /etc/puppet/manifests
> [root@ct-eng-pup etc]# puppet agent --configprint modulepath
> /etc/puppet/modules:/usr/share/puppet/modules
> [root@ct-eng-pup etc]#
>
>
> On Monday, March 4, 2013 12:49:31 PM UTC-8, JGonza1 wrote:
>
>> I also made the changes below in the puppet.conf file to tell puppet
>> where to look for the the modules and manifests. I then restart the puppet
>> master then ran puppet  command to apply changes to a puppet client it did
>> not find anything to change just got these three lines "info: Caching
>> catalog for pdlnx-adpt03.kareoprod.ent, info: Applying configuration
>> version '1362084986', notice: Finished catalog run in 0.33 seconds". WWhen
>> I put the modules and manifests back in the original place puppet works. Is
>> there anywhere else where I need to change the path to the modules?
>>
>>
>> Changes that I made to puppet.conf file to point to the ne location of
>> the modules and manifest.
>>
>>   # The default value is '$confdir/manifests'.
>> #manifestdir = /etc/puppet/manifests
>> manifestdir = /etc/puppet2/manifests
>>
>>
>>  # The search path for modules, as a list of directories separated by the
>> system path separator character. (Th
>> e POSIX path separator is ':', and the Windows path separator is ';'.)
>> # The default value is '$confdir/modules:/usr/share/**
>> puppet/modules'.
>> #modulepath = /etc/puppet/modules:/usr/**share/puppet/modules
>>   modulepath = /etc/puppet2/modules:/usr/**share/puppet/modules
>>
>>
>>
>  --
> 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.
>
>
>

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

Re: [Puppet Users] Puppet execution hangs for long periods of time

[Olivier Trempe]

Ok,

I just tried on Windows 7 and I don't observe the performance issue.

Thanks to all of you.

I will not push this investigation further as I hope to have my linux 
master soon!

On Monday, March 4, 2013 7:32:11 AM UTC-5, Felix.Frank wrote:
>
> On 03/01/2013 09:32 PM, Josh Cooper wrote: 
> > 
> > Those are the most repeated patterns. 
> > I don't know much about Windows' core... I hope this help you identify 
> > the problem 
>
> No, sorry, I'm pretty much a novice with Windows as well. 
>
> HeapAlloc sounds like memory allocation issues. Which can be a 
> performance criteria. 
>
> So basically - what Josh said, also probably some kind of ruby profiling 
> tool? I don't really know what's out there though. 
>

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

Re: [Puppet Users] Re: Long puppet catalog run times on certain nodes after "using pson" is called

[jcbollinger]

On Monday, March 4, 2013 10:25:54 AM UTC-6, Brice Figureau wrote:
>
> On Mon, 2013-03-04 at 06:09 -0800, jcbollinger wrote: 
> > > If the problem arose from congestion at the master then the delays 
> > would be less consistent from file to file and from run to run, and 
> > they would sometimes affect catalog compilation. 
>
> Well, I've seen stranger things to happen :) 
>
> Only the OP can tell us if there is queueing or not, but with this 
> limited concurrency and depending on the number of checking in clients 
> that's certainly something to check. 
>
>
Only the OP can tell us whether there is queueing, but I can tell you that 
if queueing factors into the failure behavior then it's only as part of a 
more complex problem.  Sure, it's worth checking as part of the failure 
analysis that Felix and I each suggested, but if a queueing issue is in 
fact detected then that shouldn't be taken as the final answer.


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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Pattern for managing software versions?

[jcbollinger]

On Monday, March 4, 2013 10:42:32 AM UTC-6, Schofield wrote:
>
>
>
> On Friday, March 1, 2013 7:46:33 PM UTC-5, Brendan O'Bra wrote:
>>
>>  I use hiera to externalize the versions, like this:
>> package{'jdk':
>> ensure => hiera('jdk_version','present'),
>> require => [ YumRepo['someyumrepo'] ],
>> }
>>
>> And then just deliver yaml based on environment/version/whatever
>>
>
> With this pattern, how do you handle use cases where two different 
> versions of the JDK are required on a node and the potential for different 
> configurations of the JDK such as different policy files? 
>

If you want to be able to install multiple versions of some piece of 
software, then you should obtain or create packages that allow it.  For 
example, RedHat-family JDK packages (java--openjdk) support this, 
whereas Oracle's JDK packages for RedHat family systems do not.

Configuration files are a separate question, but I don't see why your 
scenario would constitute a special case for them.  Do you imagine a 
specific problem in that area?


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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Configure One Host to Not Get Client Configuration, but Instead the Server Config Best Practices

[jcbollinger]

On Monday, March 4, 2013 2:57:23 PM UTC-6, phundisk wrote:
>
> I have been doing something with puppet that is working for me 100% but I 
> am not sure this is the best way to be doing things and wanted to see what 
> the community feels about it and if anyone has any suggestions.  This 
> problems relates to me having a common 'base' class which I put common 
> server configuration in to be distributed to all my servers.  The example I 
> am using is with NTP clients and NTP server.
>
> In my base class I have something like this:
>   "include ntp"
>
> The issue with this is that the NTP clients and servers need to have 
> different ntp.conf files.  For example, I want the NTP clients to be 
> configured to use the local NTP server as their NTP server, and my local 
> NTP server to use CentOS's NTP servers.  I have been using some basic if 
> else logic to deal with this to give it the appropriate server or client 
> file.  Is this the best way to do this?  Are there better ways to do this 
> besides doing an 'include ntp::client' for every node in my nodes.pp.  I 
> like my nodes.pp to be clean and organizes.
>
>
The classical solution to this sort of issue was to use class inheritance 
to override the contents of the ntp.conf files of your ntp servers.  Hiera 
is a better solution in many cases, but the inheritance approach might 
still be useful on occasion.  The needed subclass would look something like 
this:

class ntp::server inherits ntp {
  File['/etc/ntp.conf'] {
content => template('ntp_conf_server.erb')
  }
}

Your ntp servers would include that class in addition to the common 
baseline class, but other machines would get the intended (client) 
configuration from the baseline class without any specific mention of ntp.


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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: I moved my modules and manifest directory in puppet master.

[JGonza1]

The paths below are in the main part of the puppet.conf file and I just 
restart the puppet master process again and still nothing. I am thinking of 
creating a production directory in /etc/puppet like so /etc/puppet/prod and 
makeing the change in /etc/puppet/puppet.conf file to see if that works.
  # The default value is '$confdir/manifests'.
#manifestdir = /etc/puppet/manifests
manifestdir = /etc/puppet2/manifests
 
# The search path for modules, as a list of directories separated by 
the system path separator character. (Th
e POSIX path separator is ':', and the Windows path separator is ';'.)
# The default value is '$confdir/modules:/usr/share/puppet/modules'.
#modulepath = /etc/puppet/modules:/usr/share/puppet/modules
  modulepath = /etc/puppet2/modules:/usr/share/puppet/modules
 
On the master server:
[root@ct-eng-pup puppet]# ps -ef |grep puppet
puppet6143 1  0 14:43 ?00:00:00 /usr/bin/ruby 
/usr/bin/puppet master
root  6162  5640  0 14:46 pts/000:00:00 grep puppet
[root@ct-eng-pup puppet]# date
Mon Mar  4 14:54:56 PST 2013
[root@ct-eng-pup puppet]#
 
On the puppet agent.
[root]# puppet agent --server ct-eng-pup.caretools.ent --test --noop
info: Caching catalog for pdlnx-adpt03.kareoprod.ent
info: Applying configuration version '1362437517'
notice: Finished catalog run in 0.33 seconds
[root]#

On Monday, March 4, 2013 12:49:31 PM UTC-8, JGonza1 wrote:

> I also made the changes below in the puppet.conf file to tell puppet where 
> to look for the the modules and manifests. I then restart the puppet master 
> then ran puppet  command to apply changes to a puppet client it did not 
> find anything to change just got these three lines "info: Caching catalog 
> for pdlnx-adpt03.kareoprod.ent, info: Applying configuration version 
> '1362084986', notice: Finished catalog run in 0.33 seconds". WWhen I put 
> the modules and manifests back in the original place puppet works. Is there 
> anywhere else where I need to change the path to the modules?
>  
>  
> Changes that I made to puppet.conf file to point to the ne location of the 
> modules and manifest.
>  
>   # The default value is '$confdir/manifests'.
> #manifestdir = /etc/puppet/manifests
> manifestdir = /etc/puppet2/manifests
>  
>  
>  # The search path for modules, as a list of directories separated by the 
> system path separator character. (Th
> e POSIX path separator is ':', and the Windows path separator is ';'.)
> # The default value is '$confdir/modules:/usr/share/puppet/modules'.
> #modulepath = /etc/puppet/modules:/usr/share/puppet/modules
>   modulepath = /etc/puppet2/modules:/usr/share/puppet/modules
>  
>  
>

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

[Puppet Users] Re: Community Badges

[Miguel Di Ciurcio Filho]

On Mon, Mar 4, 2013 at 4:37 PM, Dawn Foster  wrote:
>
> Hi Miguel,
>
> We recently removed this page, since most of those badges are very old
> and out of date. It looks like the navigation link was never removed.
> I'm hoping to get some new ones designed, but we just haven't had a
> chance to do that yet.
>

Is there any plans on having a branding guide for the PuppetLabs' logos?

Something like these:

- http://www.debian.org/trademark
- https://www.mozilla.org/foundation/trademarks/policy.html
- http://www.zabbix.com/policy.php

I would like to use Puppet's logos and I could not find any guidelines.

Regards,

Miguel

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

[Puppet Users] Re: Community Badges

[Dawn Foster]

On Mon, Mar 4, 2013 at 3:01 PM, Miguel Di Ciurcio Filho
 wrote:
> On Mon, Mar 4, 2013 at 4:37 PM, Dawn Foster  wrote:
>>
>> Hi Miguel,
>>
>> We recently removed this page, since most of those badges are very old
>> and out of date. It looks like the navigation link was never removed.
>> I'm hoping to get some new ones designed, but we just haven't had a
>> chance to do that yet.
>>
>
> Is there any plans on having a branding guide for the PuppetLabs' logos?
>
> Something like these:
>
> - http://www.debian.org/trademark
> - https://www.mozilla.org/foundation/trademarks/policy.html
> - http://www.zabbix.com/policy.php
>
> I would like to use Puppet's logos and I could not find any guidelines.

We're working on that now, too. We're coming up with some new logos for
things like Puppet Camps, for example, but we haven't rolled it out yet, and
we know we need better usage guidelines at the same time. Let me ping the
design team and see if I can find out when we'll have this published.

Thanks,
Dawn Foster

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

[Puppet Users] Re: I moved my modules and manifest directory in puppet master.

[JGonza1]

Moved the modules and manifests into /etc/puppet/prod and changed 
/etc/puppet/puppet.conf. Then I restart the puppet master but does not work.
The entries in /etc/puppet/puppet.conf looks like this now.
 
# Where puppet master looks for its manifests.
# The default value is '$confdir/manifests'.
#manifestdir = /etc/puppet/manifests
manifestdir = /etc/puppet/prod/manifests
 
   # The search path for modules, as a list of directories separated by the 
system path separator character. (The POSIX path separator is ':', and the 
Windows path separator is ';'.)
# The default value is '$confdir/modules:/usr/share/puppet/modules'.
#modulepath = /etc/puppet/modules:/usr/share/puppet/modules
modulepath = /etc/puppet/prod/modules:/usr/share/puppet/modules
 
[root@ct-eng-pup puppet]# ps -ef |grep pup
puppet6356 1  0 15:30 ?00:00:05 /usr/bin/ruby 
/usr/bin/puppet master
 
[root@ct-eng-pup puppet]# puppet agent --configprint modulepath
/etc/puppet/modules:/usr/share/puppet/modules
 

On Monday, March 4, 2013 12:49:31 PM UTC-8, JGonza1 wrote:

> I also made the changes below in the puppet.conf file to tell puppet where 
> to look for the the modules and manifests. I then restart the puppet master 
> then ran puppet  command to apply changes to a puppet client it did not 
> find anything to change just got these three lines "info: Caching catalog 
> for pdlnx-adpt03.kareoprod.ent, info: Applying configuration version 
> '1362084986', notice: Finished catalog run in 0.33 seconds". WWhen I put 
> the modules and manifests back in the original place puppet works. Is there 
> anywhere else where I need to change the path to the modules?
>  
>  
> Changes that I made to puppet.conf file to point to the ne location of the 
> modules and manifest.
>  
>   # The default value is '$confdir/manifests'.
> #manifestdir = /etc/puppet/manifests
> manifestdir = /etc/puppet2/manifests
>  
>  
>  # The search path for modules, as a list of directories separated by the 
> system path separator character. (Th
> e POSIX path separator is ':', and the Windows path separator is ';'.)
> # The default value is '$confdir/modules:/usr/share/puppet/modules'.
> #modulepath = /etc/puppet/modules:/usr/share/puppet/modules
>   modulepath = /etc/puppet2/modules:/usr/share/puppet/modules
>  
>  
>

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

Re: [Puppet Users] Re: PuppetDB queue problem

[Mike Tedesco]

Is puppetdb and postgres on the same server?  
How many node does your environment have?

I had a similar issue and it was linked to I/O.  Can you look at that? 

Mike { Thanks => always }

On Mar 4, 2013, at 4:55 PM, Ken Barber  wrote:

> Any progress today?
> 
> On Fri, Mar 1, 2013 at 9:00 AM, ak0ska  wrote:
>> Yes, maybe not. The next step will be to recreate it from scratch.
>> 
>> 
>> On Friday, March 1, 2013 5:47:06 PM UTC+1, Ken Barber wrote:
>>> 
>>> 
>>> Well, I don't think a vacuum will help you - I imagine something is
>>> wrong with the schema right now or some data migration failed during
>>> upgrade. Esp. if you had migration issues from your custom PuppetDB.
>>> Of course I can't prove this with so little knowledge - but it
>>> certainly does raise a red flag.
>>> 
>>> The only other option is to compare the schemas with a known good one,
>>> and compare the database data to try and find the fault. This however
>>> is prone to error and might be time-consuming. Recreating the database
>>> sounds like a far more reliable option with a lot more guarantees
>>> around it.
>>> 
>>> 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?hl=en.
>> 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?hl=en.
> 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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] load puppet report from file

[cblum...@gmail.com]

This is more of a ruby programming question I think but here goes.

I would like to load a report from a file for some processing that does not 
happen on the puppet master:

#!/usr/bin/env ruby
require 'yaml'
require 'puppet'

report = YAML::load(File.open('/var/lib/puppet/state/last_run_report.yaml', 
'r'))

Puppet::Reports.register_report(:myreport) do
  def process
if self.status == 'failed'
  msg = "failed puppet run for #{self.host} #{self.status}"
else
  msg = "puppet run for #{self.host} #{self.status}"
end
  end
end

I am not sure that using the register report method is the proper way to go 
as this is how you do custom reporting from the master.  I have been 
looking around in the puppet code for a way to get the report yaml into the 
puppet reports class.  What is the class and method that I cannot find?

Chris

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

Re: [Puppet Users] Struggling to get Hiera to work

[Denmat]

Hi,

You can run the master in debug mode and it will show you where puppet is 
looking for the hiera files. 

Give it a whirl,
Den

On 04/03/2013, at 22:49, Jonathan Gazeley  
wrote:

> I'm setting up Hiera in my multi-environment puppetmaster for the first time.
> 
> I've written /etc/puppet/hiera.yaml, defined the hierarchies and created a 
> couple of data files with sample data in them. When queried from the 
> commandline, it works:
> 
> [jg4461@puppet ~]$ hiera -d -c /etc/puppet/hiera.yaml motd::banner 
> environment=netops_jg4461
> DEBUG: Mon Mar 04 11:42:29 + 2013: Hiera YAML backend starting
> DEBUG: Mon Mar 04 11:42:29 + 2013: Looking up motd::banner in YAML backend
> DEBUG: Mon Mar 04 11:42:29 + 2013: Looking for data source netops_jg4461
> DEBUG: Mon Mar 04 11:42:29 + 2013: Found motd::banner in netops_jg4461
> MOTD BANNER for NETOPS
> 
> 
> However, when I try to reference this variable in a manifest with syntax like 
> this:
> 
> class motd {
>  file { 'motd':
>name=> '/etc/motd',
>mode=> '0644',
>owner   => 'root',
>group   => 'root',
>content => hiera('motd::banner'),
>  }
> }
> 
> It fails with this error:
> 
> Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
> Could not find data item motd::banner in any Hiera data file and no default 
> supplied at 
> /home/jg4461/PUPPETROOT/environments/common/modules/motd/manifests/init.pp:7 
> on node **.bris.ac.uk
> 
> My hiera.yaml points to the right location (the puppet dev environment is 
> being served from my homedir on the puppetmaster but all hiera data is stored 
> in /etc/puppet/hiera, with the production puppet environment).
> 
> What kind of things should I be looking for here?
> 
> Thanks,
> Jonathan
> 
> -- 
> 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.
> 
> 

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

Re: [Puppet Users] Re: Puppet agent intermittently stops without doing any thing

[sanjiv singh]

Today, we faced  issue again.i checked apache log at puppet master , 
nothing is there.

Please find attack YAML at agent and master side and  also attached 
master's /var/log/message.  

Nothing specific i can get in /var/log/message. But what i can see is there 
is difference in client and master side YAML.


On Wednesday, 27 February 2013 13:38:28 UTC+5:30, liu.cy wrote:
>
> when this happens again, check apache logs and check client_yaml on your 
> client side. and you can see master's /var/log/message, is there any 
> puppet-master error?
>
> On Wednesday, February 27, 2013 3:02:46 PM UTC+8, sanjiv singh wrote:
>>
>> Adding more on it..
>> As i mentioned , we are using Apache-passenger for puppet master. 
>> Restarting Apache have solved problem after failure.
>>
>>
>>
>> On Wednesday, 27 February 2013 07:22:24 UTC+5:30, 刘长元 wrote:
>>>
>>> first of all, your puppet version is so old..at least, you should 
>>> upgrade to 2.7.
>>> and then, you can check last catalog your client got which stored in 
>>> /var/lib/client_yaml/ folder, if it contains some resources or not.
>>>
>>> On Wednesday, February 27, 2013 9:17:53 AM UTC+8, sanjiv singh wrote:

 Thanks for quick response.Sorry for mentioning wrong version

 $ puppet --version
 0.25.5
  

 On Wednesday, 27 February 2013 06:42:39 UTC+5:30, Adrien Thebo wrote:
>
> Hi Sanjiv,
>
> How are you running Puppet, ie via a cron or as a persistent daemon? 
> You listed the Puppet version as 5.5, but that's not an actual version of 
> Puppet available; could you post the output of `puppet --version` ? 
> Lastly, 
> how is the service stopping? Is it hanging, or is it crashing?
>
>
> On Tue, Feb 26, 2013 at 3:36 PM, sanjiv singh wrote:
>
>>
>> Please help on this...
>>
>>
>> On Thursday, 7 February 2013 12:29:15 UTC+5:30, sanjiv singh wrote:
>>>
>>> Hi All,
>>>
>>> We are observing frequently issue that Puppet agent intermittently 
>>> stops without doing any thing  when lot of puppet agent hitting 
>>> puppet master . In our environment , we have configured puppet master 
>>> over 
>>> Apache-passenger and we have used LDAP as node classifier. 
>>>
>>>
>>>- puppet 5.5
>>>- Apache-passenger 3.0.17
>>>- CentOS 6.3 / 5.5
>>>- OpenLDAP 2.4
>>>
>>> Sometimes restarting Apache **solves the problem and sometimes 
>>> issue resolved automatically when we trigger puppet daemon again.
>>>
>>>
>>> Puppet daemon stops without doing any thing following :
>>>
>>> ^[[0;36mnotice: Ignoring --listen on onetime run^[[0m
>>>
>>> ^[[0;32minfo: Caching catalog for buildsrvtd-1.domain.local^[[0m
>>>
>>> ^[[0;32minfo: Applying configuration version '1355066292'^[[0m
>>>
>>> ^[[0;36mnotice: Finished catalog run in 0.29 seconds^[[0m
>>>
>>>
>>>
>>> Regards,
>>>
>>> Sanjiv Singh
>>>
>>>  -- 
>> 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.
>> To post to this group, send email to puppet...@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.
>>  
>>  
>>
>
>
>
> -- 
> Adrien Thebo | Puppet Labs
>  


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

Re: [Puppet Users] Re: PuppetDB queue problem

[ak0ska]

A little update on our story.

Vacuum full was running for the whole weekend, so we didn't yet have time 
to rebuild indexes, because that would require more downtime, and we're not 
sure how long it would take. The size of the database didn't drop that 
much, it's now ~370Gb.

We already see some improvements. The queue doesn't get insanely large, in 
fact the highest peak we saw since Monday morning was about 20, but mostly 
it's between 0 and 3. That's good. :) One strange benefit is that we now 
see "Resources" and "Resource duplication" values on the Dashboard, those 
were previously just question marks, as you can see on my previous 
screenshots.

However, we still get the constraint violations, steadily 2 violations per 
hour. They appear as "Retried" commands on the dashboard. But if the queue 
reaches the size 0, then does this mean these commands get written to the 
database eventually? The violations seem to happen shortly after puppetdb 
starts garbage collection.

You can see it here: http://pastebin.com/B6VR67LW

We are still thinking about wiping the database, and bringing up a new one, 
as you suggested, but that cannot be done before the next weekend. Perhaps 
we should rebuild the indexes first, and see if it further improves the 
situation.
It's only been 1 day since the restart, but so far it looks a lot better 
then before.

Cheers,

ak0ska

On Monday, March 4, 2013 10:55:37 PM UTC+1, Ken Barber wrote:
>
> Any progress today? 
>
> On Fri, Mar 1, 2013 at 9:00 AM, ak0ska > 
> wrote: 
> > Yes, maybe not. The next step will be to recreate it from scratch. 
> > 
> > 
> > On Friday, March 1, 2013 5:47:06 PM UTC+1, Ken Barber wrote: 
> >> 
> >> 
> >> Well, I don't think a vacuum will help you - I imagine something is 
> >> wrong with the schema right now or some data migration failed during 
> >> upgrade. Esp. if you had migration issues from your custom PuppetDB. 
> >> Of course I can't prove this with so little knowledge - but it 
> >> certainly does raise a red flag. 
> >> 
> >> The only other option is to compare the schemas with a known good one, 
> >> and compare the database data to try and find the fault. This however 
> >> is prone to error and might be time-consuming. Recreating the database 
> >> sounds like a far more reliable option with a lot more guarantees 
> >> around it. 
> >> 
> >> 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...@googlegroups.com . 
> > To post to this group, send email to 
> > puppet...@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. 
> > 
> > 
>

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