[Puppet Users] Puppetserver & content logging

[Thomas Müller]

hi

I thought about capturing catalog requests with puppetserver to gather data 
for a simple load test. 

I've configured another logback logfile* with pattern 
%fullRequest%n%n%fullResponse - it then logs headers but no content. 
logback docs** talk about enabling a TeeFilter to enable those. Is this 
somehow possible to activate this for a non-java/clojure/jetty/logback 
developer?

- Thomas


* https://docs.puppet.com/puppetserver/latest/config_logging_advanced.html
** http://logback.qos.ch/recipes/captureHttp.html

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/07b802da-4715-441f-9f37-d67f39aa00cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet3 | hiera | role -> Problem role/mysql.yaml not used -> example from rnelson0.com with mysql

[Denny Fuchs]

hi,

I try to understand the example from 
https://rnelson0.com/2015/02/02/deploying-mysql-with-puppet-without-disabling-selinux/comment-page-1/
 
with MySQL.

At this moment, most parts are working, except role/mysql.yaml . It seems, 
that this file isn't noticed by hiera/puppet:

:yaml:
  :datadir: "/etc/puppet/environments/%{environment}/hieradata"

:hierarchy:
  - "node/%{::fqdn}"
  - "role/%{::role}"
  - "profile/%{::profile}"
  - "operatingsystem/%{::operatingsystem}/%{::operatingsystemmajrelease}"
  - "operatingsystem/%{::operatingsystem}"
  - "osfamily/%{::osfamily}"
  - "datacenter/%{::datacenter}"
  - "virtual/%{::is_virtual}"
  - common


All other files are copied from the above example, except: 
hiera/puppet_role/ -> hieradata/role/

The problem is (puppet agent -t on the example host):

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Must pass backupuser to Class[Mysql::Server::Backup] at 
/opt/puppet/environments/test/modules/profile/manifests/mysql/server.pp:12 
on node mon.example.com
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

What is wrong, so that 
/opt/puppet/environments/test/hieradata/role/mysql.yaml isn't working on 
the Puppet master.

   - ./manifests/site.pp

hiera_include('classes', '')
node default {
  $role = hiera('role')
  include $role
}

   - manifests/mon.example.com.pp

node 'mon.example.com' {
  include  role::mysql_server
}


   - ...test/hieradata/node/mon.example.com.yaml

# Mon
---
classes: apt
apt::mirror: http://debianmirror.example.bla/pub/linux/debian/debian/
apt::source: true

---
mysql::server::override_options :
  'client':
[...]



Puppet Version is 3.8.7-1puppetlabs1 on Debian 7.11


Any suggestions?


cu denny

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/f512e2d7-5034-424e-a2a3-401bb1c3fd55%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet3 | hiera | role -> Problem role/mysql.yaml not used -> example from rnelson0.com with mysql

[Rob Nelson]

Denny,

Have you tried using the hiera command line utility to see what it returns 
for that key? `hiera mysql::server::backup::backupuser 
::environment=production ::role=mysql --trace` should provide some clues as 
to how hiera is behaving and if it can find the right files. If that 
doesn't find anything, try `environment` and/or `role` (without the ::) as 
hiera does not normalize that, and sometimes it doesn't behave the way you 
would expect. You can also try looking up a key that is present in 
`common.yaml`, just to make sure you have the syntax right.

On Wednesday, December 21, 2016 at 11:37:38 AM UTC-5, Denny Fuchs wrote:
>
> hi,
>
> I try to understand the example from 
> https://rnelson0.com/2015/02/02/deploying-mysql-with-puppet-without-disabling-selinux/comment-page-1/
>  
> with MySQL.
>
> At this moment, most parts are working, except role/mysql.yaml . It seems, 
> that this file isn't noticed by hiera/puppet:
>
> :yaml:
>   :datadir: "/etc/puppet/environments/%{environment}/hieradata"
>
> :hierarchy:
>   - "node/%{::fqdn}"
>   - "role/%{::role}"
>   - "profile/%{::profile}"
>   - "operatingsystem/%{::operatingsystem}/%{::operatingsystemmajrelease}"
>   - "operatingsystem/%{::operatingsystem}"
>   - "osfamily/%{::osfamily}"
>   - "datacenter/%{::datacenter}"
>   - "virtual/%{::is_virtual}"
>   - common
>
>
> All other files are copied from the above example, except: 
> hiera/puppet_role/ -> hieradata/role/
>
> The problem is (puppet agent -t on the example host):
>
> Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
> Must pass backupuser to Class[Mysql::Server::Backup] at 
> /opt/puppet/environments/test/modules/profile/manifests/mysql/server.pp:12 
> on node mon.example.com
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run
>
> What is wrong, so that 
> /opt/puppet/environments/test/hieradata/role/mysql.yaml isn't working on 
> the Puppet master.
>
>- ./manifests/site.pp
>
> hiera_include('classes', '')
> node default {
>   $role = hiera('role')
>   include $role
> }
>
>- manifests/mon.example.com.pp
>
> node 'mon.example.com' {
>   include  role::mysql_server
> }
>
>
>- ...test/hieradata/node/mon.example.com.yaml
>
> # Mon
> ---
> classes: apt
> apt::mirror: http://debianmirror.example.bla/pub/linux/debian/debian/
> apt::source: true
>
> ---
> mysql::server::override_options :
>   'client':
> [...]
>
>
>
> Puppet Version is 3.8.7-1puppetlabs1 on Debian 7.11
>
>
> Any suggestions?
>
>
> cu denny
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/cba3bfe2-c136-48b1-8a03-80c37d00d27f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet3 | hiera | role -> Problem role/mysql.yaml not used -> example from rnelson0.com with mysql

[Denny Fuchs]

hi Rob,

I had to use a slightly different   command:

hiera -c /etc/puppet/hiera.yaml mysql::server::backup::backupuser 
environment=test ::role=mysql_server --debug

[...]
DEBUG: 2016-12-21 19:14:39 +0100: Hiera JSON backend starting
DEBUG: 2016-12-21 19:14:39 +0100: Looking up mysql::server::backup::backupuser 
in JSON backend
DEBUG: 2016-12-21 19:14:39 +0100: Looking for data source role/mysql_server
DEBUG: 2016-12-21 19:14:39 +0100: Cannot find datafile /etc/puppet/hiera/
role/mysql_server.json, skipping
DEBUG: 2016-12-21 19:14:39 +0100: Looking for data source common
DEBUG: 2016-12-21 19:14:39 +0100: Cannot find datafile /etc/puppet/hiera/
common.json, skipping
DEBUG: 2016-12-21 19:14:39 +0100: Hiera YAML backend starting
DEBUG: 2016-12-21 19:14:39 +0100: Looking up mysql::server::backup::backupuser 
in YAML backend
DEBUG: 2016-12-21 19:14:39 +0100: Looking for data source role/mysql_server
DEBUG: 2016-12-21 19:14:39 +0100: Found mysql::server::backup::backupuser in 
role/mysql_server
dbbackup


So, that seems to be working, so something else must be wrong in my config 
files.

cu denny

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/68e1bc79-6709-47a3-a3e3-7a9cbd483a84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Puppet3 | hiera | role -> Problem role/mysql.yaml not used -> example from rnelson0.com with mysql

[Rob Nelson]

Starting with the simplest of solutions, have you restarted the master
service after updating hiera.yaml? If not, it may be using an older
in-memory version of hiera.yaml.


Rob Nelson
rnels...@gmail.com

On Wed, Dec 21, 2016 at 1:16 PM, Denny Fuchs 
wrote:

>
> hi Rob,
>
> I had to use a slightly different   command:
>
> hiera -c /etc/puppet/hiera.yaml mysql::server::backup::backupuser
> environment=test ::role=mysql_server --debug
>
> [...]
> DEBUG: 2016-12-21 19:14:39 +0100: Hiera JSON backend starting
> DEBUG: 2016-12-21 19:14:39 +0100: Looking up mysql::server::backup::
> backupuser in JSON backend
> DEBUG: 2016-12-21 19:14:39 +0100: Looking for data source role/
> mysql_server
> DEBUG: 2016-12-21 19:14:39 +0100: Cannot find datafile /etc/puppet/hiera/
> role/mysql_server.json, skipping
> DEBUG: 2016-12-21 19:14:39 +0100: Looking for data source common
> DEBUG: 2016-12-21 19:14:39 +0100: Cannot find datafile /etc/puppet/hiera/
> common.json, skipping
> DEBUG: 2016-12-21 19:14:39 +0100: Hiera YAML backend starting
> DEBUG: 2016-12-21 19:14:39 +0100: Looking up mysql::server::backup::
> backupuser in YAML backend
> DEBUG: 2016-12-21 19:14:39 +0100: Looking for data source role/
> mysql_server
> DEBUG: 2016-12-21 19:14:39 +0100: Found mysql::server::backup::backupuser
> in role/mysql_server
> dbbackup
>
>
> So, that seems to be working, so something else must be wrong in my config
> files.
>
> cu denny
>
> --
> 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 view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/68e1bc79-6709-47a3-a3e3-7a9cbd483a84%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAC76iT-1v0vgZ1tyLnh9x8FTagT4M%2B-rFDSwNUn%3DfUdVw34usg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Puppet3 | hiera | role -> Problem role/mysql.yaml not used -> example from rnelson0.com with mysql

[Denny Fuchs]

hi,

yep, restarting after every change.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/c1bc2d00-8c3e-411f-b8be-cf1136ddc320%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Puppet3 | hiera | role -> Problem role/mysql.yaml not used -> example from rnelson0.com with mysql

[Rob Nelson]

I guess the next step is to try and run puppet master service in debug
mode. I haven't done that in forever and certainly not on v3. It looks like
https://docs.puppet.com/puppet/latest/services_master_webrick.html#run-puppet-master-on-the-command-line
may be helpful there. You can also check on the agent with `facter -p role`
to make sure it's receiving the role correctly through your custom fact.


Rob Nelson
rnels...@gmail.com

On Wed, Dec 21, 2016 at 2:21 PM, Denny Fuchs 
wrote:

>
> hi,
>
> yep, restarting after every change.
>
> --
> 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 view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/c1bc2d00-8c3e-411f-b8be-cf1136ddc320%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAC76iT-DmiADL%2B1FORxP0n9opc5s22tbqCMfdERa0Hxt3n8hzg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Puppet3 | hiera | role -> Problem role/mysql.yaml not used -> example from rnelson0.com with mysql

[Denny Fuchs]

hi Rob,

maybe it helps: I found something in the Puppet server logs, while calling 
the agent on the node:

[...]
2016-12-21 20:59:16,496 INFO  [puppet-server] Puppet Caching node for mon.
example.com
2016-12-21 20:59:17,236 WARN  [puppet-server] Scope(Class[main]) Could not 
look up qualified variable '::role';
2016-12-21 20:59:17,236 WARN  [puppet-server] Scope(Class[main]) Could not 
look up qualified variable '::profile';
2016-12-21 20:59:17,238 WARN  [puppet-server] Scope(Class[main]) Could not 
look up qualified variable '::datacenter';
2016-12-21 20:59:17,239 WARN  [puppet-server] Scope(Class[main]) Could not 
look up qualified variable '::role';
2016-12-21 20:59:17,240 WARN  [puppet-server] Scope(Class[main]) Could not 
look up qualified variable '::profile';
2016-12-21 20:59:17,241 WARN  [puppet-server] Scope(Class[main]) Could not 
look up qualified variable '::datacenter';
2016-12-21 20:59:17,243 WARN  [puppet-server] Scope(Class[main]) Could not 
look up qualified variable '::role';
2016-12-21 20:59:17,243 WARN  [puppet-server] Scope(Class[main]) Could not 
look up qualified variable '::profile';
2016-12-21 20:59:17,245 WARN  [puppet-server] Scope(Class[main]) Could not 
look up qualified variable '::datacenter';
2016-12-21 20:59:18,406 ERROR [puppet-server] Puppet Must pass backupuser 
to Class[Mysql::Server::Backup] at /opt/puppet/environments/test/modules/
profile/manifests/mysql/server.pp:12 on node mon.example.com
/usr/lib/ruby/vendor_ruby/puppet/util/errors.rb:106:in `fail'
/usr/lib/ruby/vendor_ruby/puppet/resource.rb:482:in `validate_complete'
org/jruby/RubyHash.java:1342:in `each'
[...]

cu denny


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/1140e0f8-ee1a-4fe8-b3b8-3b33dbe1f954%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet3 | hiera | role -> Problem role/mysql.yaml not used -> example from rnelson0.com with mysql

[John Gelnaw]

On Wednesday, December 21, 2016 at 11:37:38 AM UTC-5, Denny Fuchs wrote:
>
> hi,
>
> I try to understand the example from 
> https://rnelson0.com/2015/02/02/deploying-mysql-with-puppet-without-disabling-selinux/comment-page-1/
>  
> with MySQL.
>
> At this moment, most parts are working, except role/mysql.yaml . It seems, 
> that this file isn't noticed by hiera/puppet:
>
> :yaml:
>   :datadir: "/etc/puppet/environments/%{environment}/hieradata"
>
> :hierarchy:
>   - "node/%{::fqdn}"
>   - "role/%{::role}"
>   - "profile/%{::profile}"
>   - "operatingsystem/%{::operatingsystem}/%{::operatingsystemmajrelease}"
>   - "operatingsystem/%{::operatingsystem}"
>   - "osfamily/%{::osfamily}"
>   - "datacenter/%{::datacenter}"
>   - "virtual/%{::is_virtual}"
>   - common
>
>
Everything you're using in your hiera.yaml is OK except the role line-- 
"role" is not a fact (unless you have a custom fact defining it), or a 
top-level variable, so you'll need to define it before any hiera calls that 
might use it.

  ./manifests/site.pp
>
> hiera_include('classes', '')
> node default {
>   $role = hiera('role')
>   include $role
> }
>

Here, you define $role, but you're pulling it from hiera as well-- where is 
this variable defined?

I suspect that if you add:

$role = 'mysql'

to your role/manifests/mysql_server.pp file, that things may improve-- but 
you're also declaring it in your default node definition (or trying to), 
and one thing puppet doesn't tolerate well is defining the same variable 
twice.


   

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/1200b36c-8dd0-413b-8a3a-2017fafba16f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet3 | hiera | role -> Problem role/mysql.yaml not used -> example from rnelson0.com with mysql

[John Gelnaw]

Hate replying to myself.  As you noticed, "profile" and "datacenter" are 
also not defined.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/9cc28a52-645d-44ff-9755-76bae1654c8a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppetserver & content logging

[Jeremy Barlow]

I don't think there's any way to register the TeeFilter without making 
changes to the library, trapperkeeper-webserver-jetty9 
, that Puppet 
Server uses to integrate the Jetty web server. If you just wanted to get 
the response body but didn't need the full request body, you could turn on 
"trace" level logging for the "puppetlabs.ring-middleware.core" namespace 
in the */etc/puppetlabs/puppetserver/logback.xml *file:



With that in place you'd see the response body appear in the 
*/etc/puppetlabs/puppetserver/puppetserver.log* file, like this:

2016-12-21 13:21:08,327 TRACE [qtp993744537-38] [p.r.core] Computed response
: {:status 200, :headers {Content-Type text/pson, X-Puppet-Version 4.8.1}, 
:body 
{"tags":["settings"...

I think we could add some functionality to the 
trapperkeeper-webserver-jetty9 library to enable integration with the 
logback TeeFilter.  If you are interested in pursuing this further, would 
you mind submitting a request for this in a SERVER or TK project ticket at 
https://tickets.puppetlabs.com?

On Wednesday, December 21, 2016 at 2:44:38 AM UTC-8, Thomas Müller wrote:
>
> hi
>
> I thought about capturing catalog requests with puppetserver to gather 
> data for a simple load test. 
>
> I've configured another logback logfile* with pattern 
> %fullRequest%n%n%fullResponse - it then logs headers but no content. 
> logback docs** talk about enabling a TeeFilter to enable those. Is this 
> somehow possible to activate this for a non-java/clojure/jetty/logback 
> developer?
>
> - Thomas
>
>
> * https://docs.puppet.com/puppetserver/latest/config_logging_advanced.html
> ** http://logback.qos.ch/recipes/captureHttp.html
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/28178329-f0dc-498c-a406-0960c3bb6e39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Puppet3 | hiera | role -> Problem role/mysql.yaml not used -> example from rnelson0.com with mysql

[vigilmary via Puppet Users]

On Wed, 12/21/16, Denny Fuchs  wrote:

 Subject: Re: [Puppet Users] Re: Puppet3 | hiera | role -> Problem 
role/mysql.yaml not used -> example from rnelson0.com with mysql
 To: "Puppet Users" 
 Date: Wednesday, December 21, 2016, 10:35 PM
 
 hi Rob,
 
 maybe it helps: I found
 something in the Puppet server logs, while calling the agent
 on the node:
 
 [...]
 2016-12-21
 20:59:16,496
 INFO  [puppet-server]
 Puppet
 Caching
 node for
 mon.example.com
 2016-12-21
 20:59:17,236
 WARN  [puppet-server]
 Scope(Class[main])
 Could
 not
 look up qualified variable '::role';
 2016-12-21
 20:59:17,236
 WARN  [puppet-server]
 Scope(Class[main])
 Could
 not
 look up qualified variable '::profile';
 2016-12-21
 20:59:17,238
 WARN  [puppet-server]
 Scope(Class[main])
 Could
 not
 look up qualified variable '::datacenter';
 2016-12-21
 20:59:17,239
 WARN  [puppet-server]
 Scope(Class[main])
 Could
 not
 look up qualified variable '::role';
 2016-12-21
 20:59:17,240
 WARN  [puppet-server]
 Scope(Class[main])
 Could
 not
 look up qualified variable '::profile';
 2016-12-21
 20:59:17,241
 WARN  [puppet-server]
 Scope(Class[main])
 Could
 not
 look up qualified variable '::datacenter';
 2016-12-21
 20:59:17,243
 WARN  [puppet-server]
 Scope(Class[main])
 Could
 not
 look up qualified variable '::role';
 2016-12-21
 20:59:17,243
 WARN  [puppet-server]
 Scope(Class[main])
 Could
 not
 look up qualified variable '::profile';
 2016-12-21
 20:59:17,245
 WARN  [puppet-server]
 Scope(Class[main])
 Could
 not
 look up qualified variable '::datacenter';
 2016-12-21
 20:59:18,406
 ERROR [puppet-server]
 Puppet
 Must
 pass
 backupuser to Class[Mysql::Server::Backup]
 at /opt/puppet/environments/test/modules/profile/manifests/mysql/server.pp:12
 on node mon.example.com
 /usr/lib/ruby/vendor_ruby/puppet/util/errors.rb:106:in
 `fail'
 /usr/lib/ruby/vendor_ruby/puppet/resource.rb:482:in
 `validate_complete'
 org/jruby/RubyHash.java:1342:in
 `each'
 [...]
 
 cu
 denny
 
 
 
 
 
 
 -- 
 
 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/1140e0f8-ee1a-4fe8-b3b8-3b33dbe1f954%40googlegroups.com.
 
 For more options, visit https://groups.google.com/d/optout.
 ntinuare  si el  pe pozitii de dreapta. in cadrul L.A.N.C. s-a conturat o 
grupare

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/736905549.145219.1482376461771%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.