[Puppet Users] Re: access exported resources in template
On Thursday, June 27, 2013 1:30:42 PM UTC-5, Vasiliy Boulytchev wrote: > > Sir, have you been able to find a solution? > The approach the OP proposed is not supported by Puppet. Among the alternatives are: - Use the Concat module. This allows each contributing node to export one or more resources that represent fragments of the target file, which are collected and assembled for the node(s) that needs the whole target file. The fragments can be formatted via templates, but their assembly does not use a template (and therefore does not involve iterating a collection or accessing anything therein from a template). - Record the needed data in an accessible external store in the first place, so that the target node can load it via Hiera (or another data access function) instead of trying to use exported resources as a vehicle for data. - Use a data access function in your template to query puppetdb (supposing you are using Puppet 3) to extract the data you want about other nodes' exported resources. Of those, I would look first at Concat. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Copying files from Windows host to CentOS guest
On Thursday, June 27, 2013 5:38:07 AM UTC-5, Nicholas Shanks wrote:
>
> I have a Vagrant-controlled VM and I am trying to copy in files and
> directories when the VM gets provisioned. I have tried file:///, drive name
> with slashes and drive name with backwards slashes. Cannot get any of those
> to work.
What error messages are you getting? Does running the agent with --debug
output enabled tell you anything new?
> Also, no amount of Googling for relevant terms has turned up results for
> how to create a "puppet:" protocol directory mapping pointing to somewhere
> on my hard disk. How is that supposed to work?
The puppet: protocol cannot map directly to a file; it involves connecting
to a puppetmaster's built-in file server, or at least something emulating
that.
>
> file { "/etc/httpd/conf/httpd.conf":
> source => "file:///E/.../httpd.conf"
> }
>
> file { "/etc/httpd/conf/vhosts":
> ensure => directory,
> source => "E:/.../vhosts",
> recurse => "true"
> }
>
> file { "/etc/php.ini":
> source => "E:\...\php.ini"
> }
>
>
If you were going to copy the file manually (i.e. via the 'cp' command),
what would the fully-qualified source filename be? You should be able to
use that as the value of the 'source' property.
Are you certain that the desired source file is in fact accessible to the
agent?
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Random Yum errors during provisioning
Running Amazon Linux (which is essentially Centos5.5).
Anyone seen random yum errors like this one? I don't think
it's necessarily related to Puppet, but it randomly fails my puppet runs
and I don't know how to fix it.
Jun 28 08:41:34 ip-10-159-65-145 run_puppet: [Notice:
/Stage[main]/Zookeeper/Package[zookeeper]/ensure: created
Jun 28 08:41:34 ip-10-159-65-145 run_puppet: [Notice:
/Stage[main]/Zookeeper/File[/var/lib/zookeeper/data]/ensure: created
Jun 28 08:41:34 ip-10-159-65-145 run_puppet: [Notice:
/Stage[main]/Zookeeper/File[/var/lib/zookeeper/data/myid]/ensure: created
Jun 28 08:41:34 ip-10-159-65-145 run_puppet: [Notice:
/Stage[main]/Yum_repo::Configs/File[/etc/yum.repos.d/inin-epel.repo]/ensure:
defined content as '{md5}b94171f63e31f07b8bd75444073e301c'
Jun 28 08:41:35 ip-10-159-65-145 run_puppet: [Notice:
/Stage[main]/Zookeeper/File[/etc/zookeeper/zookeeper-env.sh]/content:
content changed '{md5}cd666c7520ce5279ddbc185512b0b177' to
'{md5}5cb59b25f5e7567d94ba14b06f6e7081'
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: [Error: Execution of
'/usr/bin/yum -d 0 -e 0 -y install daemonize' returned 1: Existing lock
/var/run/yum.pid: another copy is running as pid 2502.
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Another app is currently
holding the yum lock; waiting for it to exit...
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: The other application is: yum
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Memory : 40 M RSS (235 MB
VSZ)
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Started: Fri Jun 28
08:41:33 2013 - 00:03 ago
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: State : Running, pid: 2502
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Error: database disk image is
malformed
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: [Error:
/Stage[main]/Mcollective/Package[daemonize]/ensure: change from absent to
present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install daemonize'
returned 1: Existing lock /var/run/yum.pid: another copy is running as pid
2502.
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Another app is currently
holding the yum lock; waiting for it to exit...
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: The other application is: yum
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Memory : 40 M RSS (235 MB
VSZ)
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Started: Fri Jun 28
08:41:33 2013 - 00:03 ago
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: State : Running, pid: 2502
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Error: database disk image is
malformed
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: [mNotice:
/Stage[main]/Zookeeper/File[/etc/zookeeper/zoo.cfg]/content: content
changed '{md5}5c543298c5572c3caf40a3d108309019' to
'{md5}31db609f6601a8a02561d411e98db12b'
Jun 28 08:41:39 ip-10-159-65-145 run_puppet: [mNotice:
/Stage[main]/Puppet/File[/usr/local/bin/run_puppet.sh]/content: content
changed '{md5}4e9496313a0b4152c663defce5100af5' to
'{md5}49d78e473fa2202dea13e9b195e63575'
Jun 28 08:41:39 ip-10-159-65-145 run_puppet: [mNotice:
/Stage[main]/Yum_repo::Configs/Exec[puppet_repo]/returns: executed
successfully
Jun 28 08:41:48 ip-10-159-65-145 run_puppet: [mNotice:
/Stage[main]/Mcollective::Common/Package[mcollective-package-agent]/ensure:
created
The problem does not persist. Yum packages are installed by puppet before
and after the errors. A subsequent puppet run installs the previously
skipped packages fine.
It's as if some background process creates a lock, while updating the yum
DB, but when the lock is released, the yum DB is still in a bad state
(momentarily).
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
R: [Puppet Users] Random Yum errors during provisioning
Not puppet related, no. Every rpm deep. Solver as yum, zipper etc put a lock
for protecting the rpm db from concurrent access. So if you are using puppet be
sure to not having long running yum daemons, but if you also use some patch
management system - spacewalk, red hat satellite - this could be difficult.
Best
Messaggio originale
Da: Glenn Poston
Inviato: 28/06/2013, 15:38
A: puppet-users@googlegroups.com
Oggetto: [Puppet Users] Random Yum errors during provisioning
Running Amazon Linux (which is essentially Centos5.5).
Anyone seen random yum errors like this one? I don't think
it's necessarily related to Puppet, but it randomly fails my puppet runs
and I don't know how to fix it.
Jun 28 08:41:34 ip-10-159-65-145 run_puppet: [Notice:
/Stage[main]/Zookeeper/Package[zookeeper]/ensure: created
Jun 28 08:41:34 ip-10-159-65-145 run_puppet: [Notice:
/Stage[main]/Zookeeper/File[/var/lib/zookeeper/data]/ensure: created
Jun 28 08:41:34 ip-10-159-65-145 run_puppet: [Notice:
/Stage[main]/Zookeeper/File[/var/lib/zookeeper/data/myid]/ensure: created
Jun 28 08:41:34 ip-10-159-65-145 run_puppet: [Notice:
/Stage[main]/Yum_repo::Configs/File[/etc/yum.repos.d/inin-epel.repo]/ensure:
defined content as '{md5}b94171f63e31f07b8bd75444073e301c'
Jun 28 08:41:35 ip-10-159-65-145 run_puppet: [Notice:
/Stage[main]/Zookeeper/File[/etc/zookeeper/zookeeper-env.sh]/content:
content changed '{md5}cd666c7520ce5279ddbc185512b0b177' to
'{md5}5cb59b25f5e7567d94ba14b06f6e7081'
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: [Error: Execution of
'/usr/bin/yum -d 0 -e 0 -y install daemonize' returned 1: Existing lock
/var/run/yum.pid: another copy is running as pid 2502.
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Another app is currently
holding the yum lock; waiting for it to exit...
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: The other application is: yum
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Memory : 40 M RSS (235 MB
VSZ)
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Started: Fri Jun 28
08:41:33 2013 - 00:03 ago
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: State : Running, pid: 2502
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Error: database disk image is
malformed
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: [Error:
/Stage[main]/Mcollective/Package[daemonize]/ensure: change from absent to
present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install daemonize'
returned 1: Existing lock /var/run/yum.pid: another copy is running as pid
2502.
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Another app is currently
holding the yum lock; waiting for it to exit...
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: The other application is: yum
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Memory : 40 M RSS (235 MB
VSZ)
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Started: Fri Jun 28
08:41:33 2013 - 00:03 ago
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: State : Running, pid: 2502
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: Error: database disk image is
malformed
Jun 28 08:41:38 ip-10-159-65-145 run_puppet: [mNotice:
/Stage[main]/Zookeeper/File[/etc/zookeeper/zoo.cfg]/content: content
changed '{md5}5c543298c5572c3caf40a3d108309019' to
'{md5}31db609f6601a8a02561d411e98db12b'
Jun 28 08:41:39 ip-10-159-65-145 run_puppet: [mNotice:
/Stage[main]/Puppet/File[/usr/local/bin/run_puppet.sh]/content: content
changed '{md5}4e9496313a0b4152c663defce5100af5' to
'{md5}49d78e473fa2202dea13e9b195e63575'
Jun 28 08:41:39 ip-10-159-65-145 run_puppet: [mNotice:
/Stage[main]/Yum_repo::Configs/Exec[puppet_repo]/returns: executed
successfully
Jun 28 08:41:48 ip-10-159-65-145 run_puppet: [mNotice:
/Stage[main]/Mcollective::Common/Package[mcollective-package-agent]/ensure:
created
The problem does not persist. Yum packages are installed by puppet before
and after the errors. A subsequent puppet run installs the previously
skipped packages fine.
It's as if some background process creates a lock, while updating the yum
DB, but when the lock is released, the yum DB is still in a bad state
(momentarily).
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Raziel - a partial encrypted Hiera backend
Good idea, and much needed IMHO. Thanks! Martijn Op maandag 24 juni 2013 15:26:50 UTC+2 schreef Jens Braeuer het volgende: > > So I would like to make you aware of one of my side-projects called > Raziel. > https://github.com/jbraeuer/raziel/ > http://bit.ly/raziel-slides > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Using Puppet for downgrading Varnish (circular dependency)
Hi all, I am trying to use puppet (2.7.18) for downgrading varnish cache on Centos Linux (6.3). Unfortunately there are two varnish RPMs (which seem to have circular dependencies): varnish-3.0.4-1.el6.x86_64 varnish-libs-3.0.4-1.el6.x86_64 When using "ensure" for downgrading I get a bunch of errors: err: /Stage[main]/Varnish/Package[varnish-libs]/ensure: change from 3.0.4-1.el6 to 3.0.3-1.el6 failed: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y downgrade varnish-libs-3.0.3-1.el6' returned 1: Error: Package: varnish-3.0.4-1.el6.x86_64 (@varnish-3.0) Requires: varnish-libs = 3.0.4-1.el6 Removing: varnish-libs-3.0.4-1.el6.x86_64 (@varnish-3.0) varnish-libs = 3.0.4-1.el6 Downgraded By: varnish-libs-3.0.3-1.el6.x86_64 (varnish-3.0) varnish-libs = 3.0.3-1.el6 Available: varnish-libs-2.1.5-1.el6.i686 (EPEL-RHEL) varnish-libs = 2.1.5-1.el6 Available: varnish-libs-3.0.3-0.rc1.el6.x86_64 (varnish-3.0) varnish-libs = 3.0.3-0.rc1.el6 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest at /etc/puppet/environments/development/modules/varnish/manifests/init.pp:8 err: /Stage[main]/Varnish/Package[varnish]/ensure: change from 3.0.4-1.el6 to 3.0.3-1.el6 failed: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y downgrade varnish-3.0.3-1.el6' returned 1: Error: Package: varnish-3.0.3-1.el6.x86_64 (varnish-3.0) Requires: varnish-libs = 3.0.3-1.el6 Installed: varnish-libs-3.0.4-1.el6.x86_64 (@varnish-3.0) varnish-libs = 3.0.4-1.el6 Available: varnish-libs-2.1.5-1.el6.i686 (EPEL-RHEL) varnish-libs = 2.1.5-1.el6 Available: varnish-libs-3.0.3-0.rc1.el6.x86_64 (varnish-3.0) varnish-libs = 3.0.3-0.rc1.el6 Available: varnish-libs-3.0.3-1.el6.x86_64 (varnish-3.0) varnish-libs = 3.0.3-1.el6 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest at /etc/puppet/environments/development/modules/varnish/manifests/init.pp:8 Whatever I try I do not succeed. My goal is to have a rock-solid puppet manifest for switching between varnish versions in development environments without having to reinstall the whole VM. Using yum to downgrade both packages at the same time (and being able to resolve circular dependencies) succeeds: /usr/bin/yum -d 0 -e 0 -y downgrade varnish-libs-3.0.3-1.el6 varnish-3.0.3-1.el6 Any idea how I can solve this? Kind regards, Stefan -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Puppet user running Apache-Passenger ?
Is there anything in the Puppet/Passenger setup process that edits httpd.conf and sets the User/Group running apache to "puppet" ? A master I set up several months ago is configured that way. I do not recall doing it. But then the high voltage electroshock therapy does have its side effects :) “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin & Hobbes) -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Nagios & Puppet
In my experience, exporting nagios_command resources doesn't work so well.
What I've found works best, is to define nagios_command{}'s directly on the
server, rather than exporting and collecting them there later.
In my setup, the only resource that export is the nagios_host. I define
commands and services on the server, and assign the services to hostgroups.
Hosts then get service checks assigned to them based on which hostgroups I
put them in (usually done via the hosts role definition). I find that this
works well, since it doesn't leave me with multiple exported nagios_service
resources for every single host, that will eventually need to get cleaned
out of PuppetDB when the host is no longer in service.
-Steve
On Thu, Jun 27, 2013 at 12:07 PM, Christian Reiß
wrote:
> Hello folks,
>
> I am currently using Puppet to forge the nagios configuration files. Using
> exported ressources it really works well - to a point.
>
> The one thing I am banging my head against is the service definitions. The
> services use stuff like remote-nrpe-zombie-procs, which of course, is not
> defined anywhere:
>
> define service {
> ## --PUPPET_NAME-- (called '_naginator_name' in the
> manifest)check_zombie_procs_gaming
> useremote-nrpe-zombie-procs
> host_name gaming.alpha-labs.net
> }
>
> So far I am letting puppet generate the three configs:
>
> nagios_host.cfg
> nagios_hostextinfo.cfg
> nagios_service.cfg
>
> Tho for this to work I would need a corresponding commands.cfg and all the
> Howtos out there do not seem to have my problem. The important snipplet
> from my config would be this:
>
>
> Nagios_host <<||>> {
> require => File[resource-d],
> notify => Service[icinga],
> }
>
> Nagios_service <<||>> {
> require => File[resource-d],
> notify => Service[icinga],
> }
>
> Nagios_hostextinfo <<||>> {
> require => File[resource-d],
> notify => Service[icinga],
> }
>
> Nagios_command <<||>> {
> require => File[resource-d],
> notify => Service[icinga],
> }
>
>
> After banging my head for 3 evenings on this I really need your help.
> Thanks for any pointers.
>
> -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.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] stdlib file_line type
Hi
I am just testing file_line type in puppetlabs stdlib library. It is a
very simple line
file_line { 'testing file_line' :
ensure => present,
line => 'This is a test'
path => '/etc/puppet/puppet-test'
}
It works but when I look at client log it seems that in every puppet run,
it removes all of the lines added through file_line and then add it
again. Is it a bug or feature ?
I am using puppet 3.2 and stdlib 4.1.0.
Thanks
Kashif
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Nagios & Puppet
On 06/28/2013 04:57 PM, Stephen Jahl wrote:
In my experience, exporting nagios_command resources doesn't work so
well. What I've found works best, is to define nagios_command{}'s
directly on the server, rather than exporting and collecting them there
later.
In my setup, the only resource that export is the nagios_host. I define
commands and services on the server, and assign the services to
hostgroups. Hosts then get service checks assigned to them based on
which hostgroups I put them in (usually done via the hosts role
definition). I find that this works well, since it doesn't leave me with
multiple exported nagios_service resources for every single host, that
will eventually need to get cleaned out of PuppetDB when the host is no
longer in service.
Yeah, that approach seems better performance-wise. Tank you for sharing :)
--
Jakov Sosic
www.srce.unizg.hr
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Scope variable name is a NilClass
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I try to cleanup my config due to some deprecation warnings but with
"inline_template" i run into some trouble.
This is my class:
> 1 class test { 2 $var1 = 'foo' 3 $var2 = 'bar' 4 $vars =
> ["var1","var2"] 5 notice($var1) 6 notice($var2) 7 notice($vars)
> 8 each($vars) |$var| { 9$vardata = inline_template("<%=
> scope.lookupvar(var) %>") 10notice("$var: $vardata") 11 } 11
> }
If I run this like this
puppet apply --parser future --modulepath=/root/puppet/modules
- --environment=production --loadclasses --noop --verbose puppet/site.pp
I get the following outpu with deprecation warning:
> Notice: Scope(Class[Test]): foo Notice: Scope(Class[Test]): bar
> Notice: Scope(Class[Test]): var1 var2 Warning: Variable access via
> 'var' is deprecated. Use '@var' instead. template[inline]:1 (at
> (erb):1:in `result') Notice: Scope(Class[Test]): var1: foo Notice:
> Scope(Class[Test]): var2: bar
Ok, if I change line 9 to
> 9$vardata = inline_template("<%= scope.lookupvar(@var) %>")
I get this Error:
> Notice: Scope(Class[Test]): foo Notice: Scope(Class[Test]): bar
> Notice: Scope(Class[Test]): var1 var2 Error: Failed to parse
> inline template: Scope variable name is a NilClass, not a string
> at /root/test.pp:14 on node hackweek.office.b1-systems.de Error:
> Failed to parse inline template: Scope variable name is a
> NilClass, not a string at /root/test.pp:14 on node
> hackweek.office.b1-systems.de
Can anyone tell me what I'm doing wrong here?
Regards
Mario van der Linde
- --
Mario van der Linde
Linux Consultant & Trainer
Tel.: +49-151-16879485
Mail: li...@b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlHNtPMACgkQ0xt2iESAuwQ7hQCfSgee4Qy+bJ+94ZH4baSuoXcm
9W0An1GcopqgWRk6RvugZIiN6xyN7POy
=VE8g
-END PGP SIGNATURE-
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Variable parsing and resolving order...
On 01/08/2013 10:07 PM, mmcbr...@spryinc.com wrote: I know this isn't traditionally how puppet works, but I was curious as to any trick that may accomplish something like this. I'm afraid you answered your own question in the first part of the sentence. It's not possible AFAIK. And why would you want that in the first place? Can you provide code sample? give a little context, I want to assign a variable a value that only becomes existent after it is created by the execution of a particular exec resource But when a manifest is applied, variables are checked before resources are executed. If you're talking about facts, they are gathered *before* manifest compilation, so if you depend upon some fact value that is set only after installation of some package, you have to run puppet twice to bring your system to desired state. And, again, can you provide code sample? I apologize if this seems trivial to anyone. No need to apologize. Problem is you are trying to use *declarative* language as a procedural one. In most cases I've seen on this list, you don't need to do that at first place. So please show us your real-world problems and maybe someone can pinpoint solution for you. -- Jakov Sosic www.srce.unizg.hr -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet user running Apache-Passenger ?
On 6/28/2013 7:41 AM, Dan White wrote: Is there anything in the Puppet/Passenger setup process that edits httpd.conf and sets the User/Group running apache to "puppet" ? A master I set up several months ago is configured that way. I do not recall doing it. But then the high voltage electroshock therapy does have its side effects :) The Puppet master Rack process is started by Passenger as the user that owns the config.ru in the path of the Directory in the vhost. Ramin -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Puppet user running Apache-Passenger ?
I understand that, but the apache/httpd processes are also owned by puppet because the User/Group parameters in httpd.conf were changed to "puppet". If I did it manually, I would hope I would have remembered doing it and/or made notes to remind me. I do not remember, and I find no notes, so I am checking other possibilities. “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin & Hobbes) - Original Message - From: "Ramin K" To: puppet-users@googlegroups.com Sent: Friday, June 28, 2013 2:50:57 PM Subject: Re: [Puppet Users] Puppet user running Apache-Passenger ? On 6/28/2013 7:41 AM, Dan White wrote: > Is there anything in the Puppet/Passenger setup process that edits > httpd.conf and sets the User/Group running apache to "puppet" ? > > A master I set up several months ago is configured that way. > I do not recall doing it. > But then the high voltage electroshock therapy does have its side effects :) The Puppet master Rack process is started by Passenger as the user that owns the config.ru in the path of the Directory in the vhost. Ramin -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Ubuntu 11.10 leaving apt.puppetlabs.com
Ubuntu 11.10 Oneiric Ocelot reached end of life on 2013-05-09 [1], so we are no longer building new packages for it and it will be removed from our apt repository on Friday, July 9. [1] https://lists.ubuntu.com/archives/ubuntu-announce/2013-May/000174.html -- Moses Mendoza Puppet Labs Join us at PuppetConf 2013, August 22-23 in San Francisco - http://bit.ly/pupconf13 Register now and take advantage of the Early Bird discount - save 25%! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Announce: Facter 1.7.2-rc1 Available
Facter 1.7.2-rc1 is a bugfix release candidate in the 1.7 series. To see a list of the issues addressed by this release, check out the 1.7.2 version in our issue tracker at: https://projects.puppetlabs.com/versions/403 Downloads are available at: * Source: https://downloads.puppetlabs.com/facter/facter-1.7.2-rc1.tar.gz RPMs are available at https://yum.puppetlabs.com/el or /fedora Rubygem available at http://rubygems.org/gems/facter Debs are available at https://apt.puppetlabs.com Mac package is available at https://downloads.puppetlabs.com/mac/facter-1.7.2-rc1.dmg Please report feedback via the Puppet Labs Redmine site, using an affected version of 1.7.2-rc1: http://projects.puppetlabs.com/projects/facter/ ## Facter 1.7.2-rc1 Bug Fixes ## (#14522) Invalid byte sequence message for virtual fact on Solaris 10 x86_64 The previous attempt fix this issue did not handle the case where the data being read from /proc/self/status was already UTF-8 encoded, resulting in 'Could not retrieve virtual: invalid byte sequence in US-ASCII' messages to still occur. (#19764) Linux ipaddress not captured according to documentation Previously, if the ipconfig command listed the loopback address first, then facter on linux would report the ipaddress fact as nil. Now, facter will continue looking and report on the first non 127.0.0.0/8 subnetted IP it finds. (#20229) Network facts not working on Archlinux with net-tools 1.60 Previously, the ipconfig command with net-tools 1.60 output the netmask differently causing facter's regular expression matching to fail. As a result, the global netmask and per-interface netmask_* facts were nil on Archlinux. (#20236) Refactor the virtual fact Previously, if Facter executed lspci and was unable to determine the virtual platform from the output, dmidecode wass never consulted. Now dmidecode is always consulted regardless of whether lspci is present or not. (#20915) Invalid byte sequence message for virtual fact on Linux Previously, Facter was reading DMI entries from sysfs and interpreting it as an encoded string, resulting in 'Could not retrieve virtual: invalid byte sequence in US-ASCII' messages to occur. Now, Facter reads the data as binary. (#20938) Domain facter print spurious warnings to stderr Previously, if the host and domain information of a system was wrong, then Facter would output warnings to stderr as a result of executing hostname and dnsdomainname commands. Now Facter suppresses these warnings. (#20321) Facter::Util::Resolution::exec should be more descriptive when complaining about shell built-ins Previously, if Facter output a deprecation warning about shell builtins on Windows, it did not specify which command triggered the problem. Now Facter includes the command that triggered the warning. ## Facter 1.7.2-rc1 Changelog ## Adrien Thebo (2): d4fb548 (maint) Use RSpec 2.9 expectations 3f2e478 (maint) Use RSpec 2.9 expectations Andrew Parker (4): f2a1923 (Maint) Remove whitespace errors 1204033 (#20938) Ignore stderr from domain commands 9c0cc1e (Maint) Remove duplication in domain tests a164fe3 (#20915) Read dmi entries as binary data Jeff McCune (9): 819c8db (#14522) Force /proc/self/status encoding to valid UTF-8 (try 2) db5281e (#20236) Add example that reproduces dmidecode issue ef8db18 (#20236) Refactor the virtual fact and fix dmidecode c3a47a5 (#19764) Fix ipaddress issue scanning beyond the first address b858297 (maint) Move facter.gemspec to .gemspec 28408fb (maint) Make facter gemspec report correct version d249246 (#20229) Fix per-interface netmask_* facts with net-tools 1.60 928b7e8 (#20229) Fix netmask fact with Linux net-tools 1.60 423a3bc (maint) De-duplicate parses RSpec alias Josh Cooper (2): 35af4ce (#20301) Handle different error in ruby 1.9 0da8bd7 (#20301) Handle different error in ruby 1.9 Matthaus Owens (3): 1ad5ba7 (packaging) Add raring to the default cows list e8590a6 (packaging) Remove f16 from mocks to build as it is EOL 4b3a085 (packaging) Update FACTERVERSION to 1.7.2-rc1 Moses Mendoza (2): 2029359 (packaging) Use the packaging loader for tasks 9ad6dea (packaging) Remove Ubuntu Oneiric from build targets Stefan Schulte (1): e5b8cd5 (#20321) Be more descriptive in deprecation message -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] passing an environment variable to a command in a provider
All-
We have some custom types & providers related to mysql (mysql_user,
mysql_grant, mysql_db) written by an admin that's no longer here. The
provider just uses the mysql command to run various commands, e.g:
Puppet::Type.type(:mysql_user).provide(:mysql) do
desc "Provider for a mysql user"
optional_commands :mysql => 'mysql'
mk_resource_methods
def create
debug "mysql_user create"
@property_hash[:ensure] = :present
mysql('mysql','-e',"create user '%s' identified by '%s';" %
[@resource[:name].sub("@","'@'"),@resource[:password]])
end
def flush
debug "in flush"
mysql('mysql','-e','flush privileges;')
@property_hash.clear
end
# other stuff elided
end
For this particular provider/type to work, though, it requires that
you actually have root's environment, because it relies on reading some
config from /root/.my.cnf.
That means that on most of our hosts, doing
sudo puppet agent --test
works fine, but on hosts where we use our mysql module with the custom
types and provider, we can't do that. We instead have to
sudo su -
puppet agent --test
to make certain we've picked up root's environment, specifically HOME.
What I would like to do is augment the provider so that the mysql command
is always invoked with the environment augmented with HOME=/root or
(even better) HOME=roots_home_from_facter.
I'm not certain how to pass an environment variable to an external command
that's invoked as part of a puppet provider, though, and the searches I've
done so far haven't turned up anything helpful.
Can anyone that's familiar with writing types and providers shed some
light on what I should be doing to augment this? I know this is as much
ruby ignorance as puppet ignorance, but I have to believe that there are
people here that can point me in the right direction.
Thanks,
Tim
--
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing & Infrastructure 701-231-1076 (Voice)
Room 242-J6, IACC Building 701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] passing an environment variable to a command in a provider
On Fri, Jun 28, 2013 at 2:03 PM, Tim Mooney wrote:
> We have some custom types & providers related to mysql (mysql_user,
> mysql_grant, mysql_db) written by an admin that's no longer here. The
> provider just uses the mysql command to run various commands, e.g:
>
> Puppet::Type.type(:mysql_user)**.provide(:mysql) do
> desc "Provider for a mysql user"
>
> optional_commands :mysql => 'mysql'
>
> mk_resource_methods
>
> def create
> debug "mysql_user create"
> @property_hash[:ensure] = :present
> mysql('mysql','-e',"create user '%s' identified by '%s';" %
> [@resource[:name].sub("@","'@'**"),@resource[:password]])
> end
>
> def flush
> debug "in flush"
> mysql('mysql','-e','flush privileges;')
> @property_hash.clear
> end
>
> # other stuff elided
> end
>
> For this particular provider/type to work, though, it requires that
> you actually have root's environment, because it relies on reading some
> config from /root/.my.cnf.
>
> That means that on most of our hosts, doing
>
> sudo puppet agent --test
>
> works fine, but on hosts where we use our mysql module with the custom
> types and provider, we can't do that. We instead have to
>
> sudo su -
> puppet agent --test
>
> to make certain we've picked up root's environment, specifically HOME.
>
> What I would like to do is augment the provider so that the mysql command
> is always invoked with the environment augmented with HOME=/root or
> (even better) HOME=roots_home_from_facter.
>
> I'm not certain how to pass an environment variable to an external command
> that's invoked as part of a puppet provider, though, and the searches I've
> done so far haven't turned up anything helpful.
>
> Can anyone that's familiar with writing types and providers shed some
> light on what I should be doing to augment this? I know this is as much
> ruby ignorance as puppet ignorance, but I have to believe that there are
> people here that can point me in the right direction.
>
In Puppet 3, home environment can be passed something like:
has_command(:brew, 'brew') do
environment({ 'HOME' => ENV['HOME'] })
end
HTH,
Nan
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Using Puppet for downgrading Varnish (circular dependency)
Hi Stefan,
I've run into similar issues before… I don't have module code handy, but
what I ended up doing was creating an exec which performed something
similar to:
exec{'nuke_pesky_pkg':
command => 'rpm -e $package; touch /etc/package.removed',
creates => '/etc/package.removed'
}
which I run before the package declaration..
I imagine others might have better suggestions?
On Fri, Jun 28, 2013 at 9:11 AM, Stefan Pommerening wrote:
> Hi all,
>
> I am trying to use puppet (2.7.18) for downgrading varnish cache on Centos
> Linux (6.3).
>
> Unfortunately there are two varnish RPMs (which seem to have circular
> dependencies):
>
> varnish-3.0.4-1.el6.x86_64
> varnish-libs-3.0.4-1.el6.x86_64
>
> When using "ensure" for downgrading I get a bunch of errors:
>
> err: /Stage[main]/Varnish/Package[varnish-libs]/ensure: change from
> 3.0.4-1.el6 to 3.0.3-1.el6 failed: Could not update: Execution of
> '/usr/bin/yum -d 0 -e 0 -y downgrade varnish-libs-3.0.3-1.el6' returned 1:
> Error: Package: varnish-3.0.4-1.el6.x86_64 (@varnish-3.0)
>Requires: varnish-libs = 3.0.4-1.el6
>Removing: varnish-libs-3.0.4-1.el6.x86_64 (@varnish-3.0)
>varnish-libs = 3.0.4-1.el6
>Downgraded By: varnish-libs-3.0.3-1.el6.x86_64 (varnish-3.0)
>varnish-libs = 3.0.3-1.el6
>Available: varnish-libs-2.1.5-1.el6.i686 (EPEL-RHEL)
>varnish-libs = 2.1.5-1.el6
>Available: varnish-libs-3.0.3-0.rc1.el6.x86_64 (varnish-3.0)
>varnish-libs = 3.0.3-0.rc1.el6
> You could try using --skip-broken to work around the problem
> You could try running: rpm -Va --nofiles --nodigest
> at
> /etc/puppet/environments/development/modules/varnish/manifests/init.pp:8
> err: /Stage[main]/Varnish/Package[varnish]/ensure: change from 3.0.4-1.el6
> to 3.0.3-1.el6 failed: Could not update: Execution of '/usr/bin/yum -d 0 -e
> 0 -y downgrade varnish-3.0.3-1.el6' returned 1: Error: Package:
> varnish-3.0.3-1.el6.x86_64 (varnish-3.0)
>Requires: varnish-libs = 3.0.3-1.el6
>Installed: varnish-libs-3.0.4-1.el6.x86_64 (@varnish-3.0)
>varnish-libs = 3.0.4-1.el6
>Available: varnish-libs-2.1.5-1.el6.i686 (EPEL-RHEL)
>varnish-libs = 2.1.5-1.el6
>Available: varnish-libs-3.0.3-0.rc1.el6.x86_64 (varnish-3.0)
>varnish-libs = 3.0.3-0.rc1.el6
>Available: varnish-libs-3.0.3-1.el6.x86_64 (varnish-3.0)
>varnish-libs = 3.0.3-1.el6
> You could try using --skip-broken to work around the problem
> You could try running: rpm -Va --nofiles --nodigest
> at
> /etc/puppet/environments/development/modules/varnish/manifests/init.pp:8
>
> Whatever I try I do not succeed. My goal is to have a rock-solid puppet
> manifest for switching between varnish versions in development environments
> without having to reinstall the whole VM.
>
> Using yum to downgrade both packages at the same time (and being able to
> resolve circular dependencies) succeeds:
>
> /usr/bin/yum -d 0 -e 0 -y downgrade varnish-libs-3.0.3-1.el6
> varnish-3.0.3-1.el6
>
> Any idea how I can solve this?
>
> Kind regards,
> Stefan
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Is it possible to pass extra flags to Puppet via rspec?`
Thanks for the tip, Justin and everyone else who replied.
I'll try your suggestion.
Cheers,
--Amos
On 27 June 2013 14:28, Justin Stoller wrote:
> It's been a while since I jumped into this code and it's late, forgive me
> if I say something naive inline.
>
>
> On Wed, Jun 26, 2013 at 8:14 PM, Nan Liu wrote:
>
>> On Wed, Jun 26, 2013 at 7:23 PM, Amos Shapira wrote:
>>
>>> I'm writing my first puppet function rspec test and am having a problem
>>> which I don't see how to solve.
>>>
>>> The function (and the test) involve access to files through the File
>>> Server. In order for the function (and the test) to work I need to pass
>>> "--fileserverconf=fileserver.conf" parameter to Puppet.
>>>
>>> So far I haven't found a way to do that.
>>>
>>> If I understand the rspec-puppet source at
>>> https://github.com/rodjek/rspec-puppet/blob/master/lib/rspec-puppet.rbcorrectly
>>> then the list of parameters I can pass is limited to the ones
>>> mentioned in lines 16-22. Am I right?
>>>
>>
> Those are the limit you can pass to the RSpec.configure { ... } block in
> your spec helper.
>
>>
>>> Does anyone know how can I pass other parameters, or otherwise affect
>>> Puppet's configuration to set this value?
>>>
>>> Have you tried something like:
>
> describe 'foo' do
> before do
> Puppet[:fileserverconfig] = '/my/path/to/fileserver.conf'
> end
>
> your tests
>
> end
>
>>
>> Oddly enough, you can't depend on rspec-puppet to configure the settings
>> for spec test. For example, puppetlab's spec helper configures the
>> modulepath [1] to include spec/fixtures/modules, but this does not seem to
>> configure Puppet[:modulepath] setting. For whatever reason, puppet loads
>> the modules correctly from spec/fixtures/modules, but when you debug the
>> spec test, it appears to set the module path to:
>>
>> (rdb:1) p Puppet[:modulepath]
>> "/dev/null/modules:/usr/share/puppet/modules"
>>
>
> Nan -
>
> In puppetlabs_spec_helper/puppet_spec_helper[1] which was based on a file
> in Puppet[2] the confdir and vardir are explicitly set to '/dev/null' which
> causes the modulepath you're seeing in Puppet "proper".
>
> I believe, however the subject catalog/function that is tested in each
> example group (unless you explicitly create a subject yourself) should mask
> that value with what ever is passed into RSpec.configure (like the
> modulepath setting in module_spec_helper) for its
> compilation/initialization[3][4].
>
>
> - Justin
>
> 1.
> https://github.com/puppetlabs/puppetlabs_spec_helper/blob/master/lib/puppetlabs_spec_helper/puppet_spec_helper.rb#L96-L97
> 2.
> https://github.com/puppetlabs/puppet/blob/master/lib/puppet/test/test_helper.rb#L142-L156
> 3.
> https://github.com/rodjek/rspec-puppet/blob/master/lib/rspec-puppet/example/function_example_group.rb#L10
> 4.
> https://github.com/rodjek/rspec-puppet/blob/master/lib/rspec-puppet/support.rb#L80-L97
>
>>
>> You can do what Wolf suggested. File server conf is somewhat
>> inconsistent, since the setting is actually: Puppet[:fileserverconfig].
>>
>> HTH,
>>
>> Nan
>>
>>
>> 1.
>> https://github.com/puppetlabs/puppetlabs_spec_helper/blob/master/lib/puppetlabs_spec_helper/module_spec_helper.rb#L21-L24
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to puppet-users+unsubscr...@googlegroups.com.
>>
>> To post to this group, send email to puppet-users@googlegroups.com.
>> Visit this group at http://groups.google.com/group/puppet-users.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>
>
> --
>
> Join us at PuppetConf 2013, August 22-23 in San Francisco -
> http://bit.ly/pupconf13
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/ynVp988yEcU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
[image: View my profile on LinkedIn]
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
