[Puppet Users] Announce: PuppetDB 3.2.3 is now available!

2016-01-11 Thread Wyatt Alt 
PuppetDB 3.2.3 - January 11, 2016

PuppetDB 3.2.3 Downloads



Available in native package format as part of Puppet Collection 1 (PC1).
More information on the PC1 repositories is available here:
http://bit.ly/1HQJDNb

Binary tarball: http://downloads.puppetlabs.com/puppetdb/

Source: http://github.com/puppetlabs/puppetdb

Please report feedback via the Puppet Labs tickets site, using an affected
PuppetDB version of 3.2.3: https://tickets.puppetlabs.com/browse/PDB

Documentation: http://docs.puppetlabs.com/puppetdb/3.2/

Puppet module: http://forge.puppetlabs.com/puppetlabs/puppetdb

PuppetDB 3.2.3 Release Notes



PuppetDB 3.2.3 is a backward-compatible bugfix release that addresses an
issue affecting new installs on non-english PostgreSQL installations, as
well as submission failures that can occur on catalogs containing large
amounts of binary data. More information on the specifics of the release
can be found in the official release notes:
https://docs.puppetlabs.com/puppetdb/3.2/release_notes.html

Contributors
---
Andrew Roetker, Ken Barber, Rob Browning, Rob Nelson, Russell Mull, Ryan
Senior, and Wyatt Alt

-- 
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/CAJDiH3Hmtu9dAgOmkBxezspkCD7bzGmz3kW_EN%3DemaE1KVmp8g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Missing node_aws sub-command in puppet using Puppet Enterprise 2015.3.1-el-7-x86_64

2016-01-11 Thread Lindsey Smith 
On Thu, Jan 7, 2016 at 11:06 PM, Deepak Agarwal 
wrote:

> I have installed puppetlabs-aws as steps given in github below.
> https://github.com/puppetlabs/puppetlabs-aws
>
>
> The puppet aws module is installed at below path:
>
> $ pwd
> /home/centos/.puppet/modules/aws
>
> $ ls
> bin   checksums.json  CONTRIBUTING.md  fixtures  Guardfile
>  LICENSERakefile   spec
> CHANGELOG.md  contrib examples Gemfile   lib
>  metadata.json  README.md  tests
>
>
>
> But puppet subcommand node_aws is still missing 
>

That's expected as the way of interacting with AWS has changed. The AWS
module provides for Puppet DSL-style creation of infrastructure rather than
a command-line driven "puppet node" operation. See
https://github.com/puppetlabs/puppetlabs-aws#getting-started-with-aws for
an example.


> Is there any PATH environment variable needs to be setup to get node_aws
> in puppet sub-command?
>
> $ puppet help | grep node
>   node  View and manage node definitions.
>   resource_type View classes, defined resource types, and nodes from
> all manifests.
>
> Thanks,
> Deepak
>
>
> On Thursday, 7 January 2016 23:51:44 UTC+5:30, Lindsey Smith wrote:
>>
>>
>>
>> On Thu, Jan 7, 2016 at 6:30 AM, Deepak Agarwal 
>> wrote:
>>
>>> Hello,
>>>
>>> The node_aws cloud provisioning sub-command is missing in puppet.
>>>
>>>
>>> I have installed Puppet Enterprise 2015.3.1-el-7-x86_64 (TRAIL version
>>> tar) with q_puppet_cloud_install='y'
>>>
>>> The OS is 64 bit CentOS 7. The SELinux is disabled
>>>
>>> I have searched a lot and Puppet Enterprise is expected to have
>>> cloud_provisioning inbuilt with q_puppet_cloud_install='y'.
>>> But I am not seeing node_aws in my setup.
>>>
>>>
>>> Please suggest what is missing and why puppet enterprise is not having
>>> node_aws on CentOS 7?
>>>
>>
>> Hi Deepak. Cloud Provisioner was deprecated in the PE 3.8 release and
>> removed in the PE 2015.2 release as noted here
>> http://docs.puppetlabs.com/pe/3.8/cloudprovisioner_overview.html
>>
>> As a replacement, we recommend using the puppetlabs/aws module instead.
>> See
>> https://puppetlabs.com/blog/puppet-aws-module-now-supported-puppet-enterprise
>> for an introduction.
>>
>>
>>
>>>
>>>
>>> -
>>>
>>> $ puppet help | grep node
>>>   node  View and manage node definitions.
>>>   resource_type View classes, defined resource types, and nodes from
>>> all manifests.
>>>
>>>
>>>
>>> --
>>>
>>> $ puppet help node_aws
>>> Error: Could not load help for the face node_aws.
>>> Please check the error logs for more information.
>>>
>>> Detail: "Could not find Puppet Face node_aws"
>>>
>>> Error: Try 'puppet help help help' for usage
>>>
>>>
>>>
>>> --
>>>
>>> answer file:
>>> q_activity_database_name='pe-activity'
>>> q_activity_database_password='cisco123'
>>> q_activity_database_user='pe-activity'
>>> q_all_in_one_install='y'
>>> q_classifier_database_name='pe-classifier'
>>> q_classifier_database_password='cisco123'
>>> q_classifier_database_user='pe-classifier'
>>> q_database_host='ec2-54-201-132-62.us-west-2.compute.amazonaws.com'
>>> q_database_install='y'
>>> q_database_port='5432'
>>> q_database_root_password='cisco123'
>>> q_database_root_user='root'
>>> q_fail_on_unsuccessful_master_lookup='y'
>>> q_install='y'
>>> q_orchestrator_database_name='pe-orchestrator'
>>> q_orchestrator_database_password='cisco123'
>>> q_orchestrator_database_user='pe-orchestrator'
>>> q_pe_check_for_updates='y'
>>> q_pe_database='y'
>>> q_public_hostname='ec2-54-201-132-62.us-west-2.compute.amazonaws.com'
>>> q_puppet_cloud_install='y'
>>> q_puppet_enterpriseconsole_auth_password='cisco123'
>>> q_puppet_enterpriseconsole_httpd_port='443'
>>> q_puppet_enterpriseconsole_install='y'
>>> q_puppet_enterpriseconsole_master_hostname='
>>> ec2-54-201-132-62.us-west-2.compute.amazonaws.com'
>>> q_puppetagent_certname='
>>> ec2-54-201-132-62.us-west-2.compute.amazonaws.com'
>>> q_puppetagent_install='y'
>>> q_puppetagent_server='ec2-54-201-132-62.us-west-2.compute.amazonaws.com'
>>> q_puppetdb_database_name='pe-puppetdb'
>>> q_puppetdb_database_password='cisco123'
>>> q_puppetdb_database_user='pe-puppetdb'
>>> q_puppetdb_hostname='ec2-54-201-132-62.us-west-2.compute.amazonaws.com'
>>> q_puppetdb_install='y'
>>> q_puppetdb_plaintext_port='8080'
>>> q_puppetdb_port='8081'
>>> q_puppetmaster_certname='
>>> ec2-54-201-132-62.us-west-2.compute.amazonaws.com'
>>>
>>> q_puppetmaster_dnsaltnames='ip-172-31-14-31,ip-172-31-14-31.us-west-2.compute.internal,puppet,puppet.us-west-2.compute.internal'
>>> q_puppetmaster_enterpriseconsole_hostname='
>>> ec2-54-201-132-62.us-west-2.compute.amazonaws.com'
>>> q_

[Puppet Users] Re: Serving files from custom mount point in Puppet 4

2016-01-11 Thread Eric Sorenson 
It is not deprecated at all.

Can you please post your configuration (fileserver.conf, auth.conf, and the 
puppet manifest which causes the error) along with the exact error messages?

--eric0

On Monday, January 11, 2016 at 1:57:34 AM UTC-8, kashif wrote:
>
> Hi
>
> Is serving files from custom mount point depreciated in puppet 4? I 
> configured fileserver.conf file in same way as  in puppet 3 but it is not 
> working. I could not find any explicit statement in puppet 4 documents 
> about custom mount points. Has any one managed to serve from custom mount 
> point in puppet 4?
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/52abb73e-2dd1-45f1-b974-761c24fbab85%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] How to cope with accented characters in DisplayName using Puppet 3.8.x on Windows XP?

2016-01-11 Thread Tiago Delboni 
I was able to build Ruby 2.1.7 on XP using mingw32, along with the gems 
listed in %ProgramFiles%\Puppet 
Labs\Puppet\sys\ruby\lib\ruby\gems\1.9.0\gems
However, as I am illiterate on Ruby, I'm not sure I dealt properly with the 
dependencies. Simply replacing %ProgramFiles%\Puppet Labs\Puppet\sys\ruby 
with the new built does not work:

C:\>puppet --version
C:/Arquivos de programas/Puppet 
Labs/Puppet/sys/ruby/lib/ruby/gems/2.1.0/gems/win32-security-0.3.2/lib/win32/security.rb:61:in
 
`block in elevated_security?': ParÔmetro incorreto. - GetTokenInformation 
(SystemCallError)
from C:/Arquivos de programas/Puppet 
Labs/Puppet/sys/ruby/lib/ruby/gems/2.1.0/gems/win32-security-0.3.2/lib/win32/security.rb:41:in
 
`initialize'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/sys/ruby/lib/ruby/gems/2.1.0/gems/win32-security-0.3.2/lib/win32/security.rb:41:in
 
`new'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/sys/ruby/lib/ruby/gems/2.1.0/gems/win32-security-0.3.2/lib/win32/security.rb:41:in
 
`elevated_security?'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/facter/lib/facter/util/windows_root.rb:5:in `root?'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/facter/lib/facter/util/config.rb:41:in 
`setup_default_ext_facts_dirs'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/facter/lib/facter/util/config.rb:69:in `'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/facter/lib/facter/util/config.rb:5:in `'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/facter/lib/facter/util/resolution.rb:2:in `'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/facter/lib/facter/util/fact.rb:2:in `'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/facter/lib/facter.rb:35:in `'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/facter/lib/facter.rb:30:in `'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/puppet/lib/puppet.rb:6:in `'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/puppet/lib/puppet/util/command_line.rb:12:in `'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/sys/ruby/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from C:/Arquivos de programas/Puppet 
Labs/Puppet/puppet/bin/puppet:7:in `'

Em segunda-feira, 11 de janeiro de 2016 09:30:46 UTC-2, Tiago Delboni 
escreveu:
>
> Hi Josh, thanks for the enlightenment! 
> Any chances I can easily upgrade 3.8.x 's Ruby to fix this issue without 
> breaking current manifests and behaviour?
>
> Em sexta-feira, 8 de janeiro de 2016 15:24:27 UTC-2, Josh Cooper escreveu:
>>
>>
>>
>> On Fri, Jan 8, 2016 at 8:20 AM, Tiago Delboni  wrote:
>>
>>> With parser=future it doesn't complain about the escape sequence, but 
>>> keeps creating the package every run. :(
>>>
>>> Copying the accented character to the manifest does not work (tried many 
>>> ways).
>>>
>>>
>>> Em sexta-feira, 8 de janeiro de 2016 13:38:25 UTC-2, Henrik Lindberg 
>>> escreveu:
>>>
 On 2016-08-01 14:23, Tiago Delboni wrote: 
 > Hi! 
 > 
 > On Windows 7 we have Puppet 4.2.x and, in order to deal with accented 
 > characters commonly found in registry key DisplayName, we use unicode 
 > escape sequences in our manifests such as "\u00FA". 
 > 
 > However, on Windows XP,  we couldn't install Puppet 4.2.x so we use 
 > 3.8.x instead. When running the same manifest with escape sequences, 
 > Puppet complains: "Unrecognised escape sequence '\u' in file ...". 
 > 
>

[Puppet Users] Re: server not listed in manifests, but gets catalog

2016-01-11 Thread Andreas Dvorak 
Hi,

now I understand. Thank you.

Andreas

-- 
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/4bf2ea84-059b-4d8d-8cea-39874250f7b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] server not listed in manifests, but gets catalog

2016-01-11 Thread Martin Alfke 
Hi Andreas,
> On 11.01.2016, at 13:47, Andreas Dvorak  wrote:
> 
> Hi,
> 
> after the update of the puppet master from 3.3.1 to 3.6.2 a host gets a 
> catalog even if it is not defined in manifests. Is this a new funcationality? 
> I did not see anything in the release notes.
> It gets a catalog with all the information from profiles::base
> 
> manifests/
> cat site.pp
> node default {
> notify { 'Server ist noch nicht in Puppet definiert': }
> }
> 
> if versioncmp($::puppetversion, '3.6.0') >= 0 {
> Package {
>   allow_virtual => true,
> }
> }
> 
> hiera_include('classes’)

The hiera_include is done in global scope, not within a node scope.
This means, that every node should get classes included from ‘classes’ hiera 
key.

> 
> a nodes.pp with server, but not the one 
> 
> hiera/
> cat common.yaml
> classes:
>   - profiles::base

And this is where the hiera_include gets its classes which should be put into 
the catalog for all nodes.

Nothing uncommon.
Expected behavior.

Best,
Martin

> 
> 
> Best regards
> Andreas
> 
> -- 
> 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/9377c926-8550-40ef-962b-d036e06bf33f%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/B567FEFE-56A8-4A24-8953-2E7E72D711E3%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] server not listed in manifests, but gets catalog

2016-01-11 Thread Andreas Dvorak 
Hi,

after the update of the puppet master from 3.3.1 to 3.6.2 a host gets a 
catalog even if it is not defined in manifests. Is this a new 
funcationality? I did not see anything in the release notes.
It gets a catalog with all the information from profiles::base

manifests/
cat site.pp
node default {
notify { 'Server ist noch nicht in Puppet definiert': }
}

if versioncmp($::puppetversion, '3.6.0') >= 0 {
Package {
  allow_virtual => true,
}
}

hiera_include('classes')

a nodes.pp with server, but not the one 

hiera/
cat common.yaml
classes:
  - profiles::base


Best regards
Andreas

-- 
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/9377c926-8550-40ef-962b-d036e06bf33f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] How to cope with accented characters in DisplayName using Puppet 3.8.x on Windows XP?

2016-01-11 Thread Tiago Delboni 
Hi Josh, thanks for the enlightenment! 
Any chances I can easily upgrade 3.8.x 's Ruby to fix this issue without 
breaking current manifests and behaviour?

Em sexta-feira, 8 de janeiro de 2016 15:24:27 UTC-2, Josh Cooper escreveu:
>
>
>
> On Fri, Jan 8, 2016 at 8:20 AM, Tiago Delboni  > wrote:
>
>> With parser=future it doesn't complain about the escape sequence, but 
>> keeps creating the package every run. :(
>>
>> Copying the accented character to the manifest does not work (tried many 
>> ways).
>>
>>
>> Em sexta-feira, 8 de janeiro de 2016 13:38:25 UTC-2, Henrik Lindberg 
>> escreveu:
>>
>>> On 2016-08-01 14:23, Tiago Delboni wrote: 
>>> > Hi! 
>>> > 
>>> > On Windows 7 we have Puppet 4.2.x and, in order to deal with accented 
>>> > characters commonly found in registry key DisplayName, we use unicode 
>>> > escape sequences in our manifests such as "\u00FA". 
>>> > 
>>> > However, on Windows XP,  we couldn't install Puppet 4.2.x so we use 
>>> > 3.8.x instead. When running the same manifest with escape sequences, 
>>> > Puppet complains: "Unrecognised escape sequence '\u' in file ...". 
>>> > 
>>> Have you tried using 3.8.x with parser=future turned on? That would give 
>>> you support for \u the same way as in puppet 4.x. 
>>>
>>> > Puppet 3.8.x documentation states that it "treats strings as sequences 
>>> > of bytes. It does not recognize encodings or translate between them, 
>>> and 
>>> > non-printing characters are preserved." 
>>> > 
>>> Yes, when you get the waring for \u, it means there will be a literal 
>>> backslash and a literal u in the resulting string. (That is with the 
>>> regular parser since it (as it says) does not support the \u escape for 
>>> unicode chars). 
>>>
>>> > So, how can I deal with software that have accented characters in 
>>> their 
>>> > DisplayName? Assuming that registry's encoding is the same on WXP and 
>>> > W7, I could probably make it work by using Puppet 4.2.x on Windows XP, 
>>> > but I just don't know how to install it successfully. 
>>> > 
>>>
>>> Use puppet 3.8.x (latest) as noted above. The other approach (ugly, and 
>>> horrible work around) is to simply copy/paste the actual character into 
>>> the source file, but that is not guaranteed to work for all characters. 
>>>
>>> Hope that helps 
>>> - henrik 
>>>
>>> > -- 
>>> > 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 view this discussion on the web visit 
>>> > 
>>> https://groups.google.com/d/msgid/puppet-users/12713369-5970-4a43-804a-ca57a400afd0%40googlegroups.com
>>>  
>>> > <
>>> https://groups.google.com/d/msgid/puppet-users/12713369-5970-4a43-804a-ca57a400afd0%40googlegroups..com?utm_medium=email&utm_source=footer>.
>>>  
>>>
>>> > For more options, visit https://groups.google.com/d/optout. 
>>>
>>>
>>> -- 
>>>
>>> Visit my Blog "Puppet on the Edge" 
>>> http://puppet-on-the-edge.blogspot.se/ 
>>>
>>> -- 
>> 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 view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/6084ba68-3ac0-458a-ab7c-292d11663e6b%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> Puppet 3.8.x ships with ruby 1.9.3 (32-bit) and 2.0.0 (64-bit), both of 
> which use ANSI versions of Win32 registry APIs (and not the wide/unicode 
> versions). Puppet uses those methods to scan the registry looking for 
> installed applications, and is likely the cause for the problem you're 
> seeing. See 
> https://tickets.puppetlabs.com/browse/PUP-2937?focusedCommentId=87973&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-87973
>  
> for more information.
>
> Puppet 4.x ships with ruby 2.1.x, which switched to using wide versions of 
> the registry APIs, so I think that's why it's working in that case.
>
> Josh
>
> -- 
> Josh Cooper
> Developer, 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/243e5a09-7779-4d0d-a956-32756d82e639%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Serving files from custom mount point in Puppet 4

2016-01-11 Thread mohammad kashif 
Hi

Is serving files from custom mount point depreciated in puppet 4? I
configured fileserver.conf file in same way as  in puppet 3 but it is not
working. I could not find any explicit statement in puppet 4 documents
about custom mount points. Has any one managed to serve from custom mount
point in puppet 4?

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