from:"Brian"

Thank you for that, Josh, as well as for creating the Powershell module for
Puppet. I hope to meet both you and Rob at PuppetConf next week.

On Thu, Sep 18, 2014 at 4:24 PM, Josh Cooper  wrote:

>
>
> On Thu, Sep 18, 2014 at 2:17 PM, Brian Morris 
> wrote:
>
>> Holy cow, Rob... that was great info! All I did was change "System32" to
>> "sysnative", and it worked on the first try. All of that frustration boiled
>> down to one part of one path...
>>
>> Thank you for the link, too. It helps to understand why this happens.
>> Cheers to you!
>>
>
> I filed https://tickets.puppetlabs.com/browse/FACT-710. as facter should
> use 64-bit powershell when available.
>
>
>> On Thu, Sep 18, 2014 at 1:59 PM, Rob Reynolds  wrote:
>>
>>>
>>>
>>> On Thu, Sep 18, 2014 at 3:54 PM, Rob Reynolds 
>>> wrote:
>>>
>>>>
>>>>
>>>> On Thu, Sep 18, 2014 at 2:11 PM, Brian Morris <
>>>> nomadicextre...@gmail.com> wrote:
>>>>
>>>>> Hello all,
>>>>>
>>>>> I have been banging my head against this one for a couple of days. I
>>>>> am trying to use Powershell to comb the Windows registry for installed
>>>>> applications, such as VMware Tools, to create a custom facter. If I run
>>>>> this code from a PS prompt it works, and returns the expected data:
>>>>>
>>>>> PS C:\> Get-ChildItem
>>>>> hklm:\software\microsoft\windows\currentversion\uninstall | ForEach-Object
>>>>> {Get-ItemProperty $_.ps
>>>>> path} | Where-Object {$_.DisplayName -eq "VMware Tools"} |
>>>>> ForEach-Object -process {$_.DisplayVersion }
>>>>> *9.4.6.1770165*
>>>>>
>>>>>
>>>> This is running in a 64bit process.
>>>>
>>>>
>>>>
>>>>> However, running the same thing through Puppet as a facter yields zero
>>>>> data:
>>>>>
>>>>> --
>>>>> Facter.add("vmtools_version") do
>>>>> confine :osfamily => "Windows"
>>>>>   setcode do
>>>>> 
>>>>> Facter::Util::Resolution.exec('C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
>>>>> -Command
>>>>>
>>>>
>>> C:\Windows\System32 is also subject to File system redirection, which is
>>> also talked about in that post. Likely fixing only this as sysnative will
>>> return the right data because PowerShell will run in 64bit mode. But I
>>> would explore the ruby only way to speed up the fact.
>>>
>>>
>>>> "& {Get-ChildItem
>>>>> hklm:\software\microsoft\windows\currentversion\uninstall | ForEach-Object
>>>>> {Get-ItemProperty $_.pspath} | Where-Object {$_.DisplayName -eq \"VMware
>>>>> Tools\"} | ForEach-Object -process {$_.DisplayVersion } } "')
>>>>> end
>>>>> end
>>>>> --
>>>>>
>>>>
>>>> This is in a 32bit process unless you are on the newest 3.7.0 or 3.7.1
>>>> x64 builds of Puppet. You are hitting registry redirection.  Be sure to
>>>> checkout Common Gotchas[1] especially for how to turn off registry
>>>> redirection in a 32 bit process.
>>>>
>>>>
>>>> [1] http://puppetlabs.com/blog/how-avoid-common-windows-gotchas-puppet
>>>>
>>>>
>>>> More detail:
>>>>
>>>> When a 32 bit process calls the registry and is subject to redirection,
>>>> it only sees the Wow6432Node under software. Check out that link above, it
>>>> explains quite a bit in more detail.
>>>>
>>>>
>>>>
>>>>>
>>>>> The left side shows up in the facters as "vmtools_version", but the
>>>>> right side is always empty. I have tried using the  GetItem module 
>>>>> instead,
>>>>> and tried various combinations of the "-Command" switch, removed the
>>>>> "For-Each" handler to see if would spit out a huge block of text, and even
>>>>> tried wrapping the whole thing in a "try & catch" to see if any error
>>>>> states are generated, but have never gotten any right side output at all.
>>>>>
>>>>> Does anyone have an idea that might make this work?
>>>>

Re: [Puppet Users] Using Powershell in facters yields no data

Holy cow, Rob... that was great info! All I did was change "System32" to
"sysnative", and it worked on the first try. All of that frustration boiled
down to one part of one path...

Thank you for the link, too. It helps to understand why this happens.
Cheers to you!

On Thu, Sep 18, 2014 at 1:59 PM, Rob Reynolds  wrote:

>
>
> On Thu, Sep 18, 2014 at 3:54 PM, Rob Reynolds  wrote:
>
>>
>>
>> On Thu, Sep 18, 2014 at 2:11 PM, Brian Morris 
>> wrote:
>>
>>> Hello all,
>>>
>>> I have been banging my head against this one for a couple of days. I am
>>> trying to use Powershell to comb the Windows registry for installed
>>> applications, such as VMware Tools, to create a custom facter. If I run
>>> this code from a PS prompt it works, and returns the expected data:
>>>
>>> PS C:\> Get-ChildItem
>>> hklm:\software\microsoft\windows\currentversion\uninstall | ForEach-Object
>>> {Get-ItemProperty $_.ps
>>> path} | Where-Object {$_.DisplayName -eq "VMware Tools"} |
>>> ForEach-Object -process {$_.DisplayVersion }
>>> *9.4.6.1770165*
>>>
>>>
>> This is running in a 64bit process.
>>
>>
>>
>>> However, running the same thing through Puppet as a facter yields zero
>>> data:
>>>
>>> --
>>> Facter.add("vmtools_version") do
>>> confine :osfamily => "Windows"
>>>   setcode do
>>> 
>>> Facter::Util::Resolution.exec('C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
>>> -Command
>>>
>>
> C:\Windows\System32 is also subject to File system redirection, which is
> also talked about in that post. Likely fixing only this as sysnative will
> return the right data because PowerShell will run in 64bit mode. But I
> would explore the ruby only way to speed up the fact.
>
>
>> "& {Get-ChildItem
>>> hklm:\software\microsoft\windows\currentversion\uninstall | ForEach-Object
>>> {Get-ItemProperty $_.pspath} | Where-Object {$_.DisplayName -eq \"VMware
>>> Tools\"} | ForEach-Object -process {$_.DisplayVersion } } "')
>>> end
>>> end
>>> --
>>>
>>
>> This is in a 32bit process unless you are on the newest 3.7.0 or 3.7.1
>> x64 builds of Puppet. You are hitting registry redirection.  Be sure to
>> checkout Common Gotchas[1] especially for how to turn off registry
>> redirection in a 32 bit process.
>>
>>
>> [1] http://puppetlabs.com/blog/how-avoid-common-windows-gotchas-puppet
>>
>>
>> More detail:
>>
>> When a 32 bit process calls the registry and is subject to redirection,
>> it only sees the Wow6432Node under software. Check out that link above, it
>> explains quite a bit in more detail.
>>
>>
>>
>>>
>>> The left side shows up in the facters as "vmtools_version", but the
>>> right side is always empty. I have tried using the  GetItem module instead,
>>> and tried various combinations of the "-Command" switch, removed the
>>> "For-Each" handler to see if would spit out a huge block of text, and even
>>> tried wrapping the whole thing in a "try & catch" to see if any error
>>> states are generated, but have never gotten any right side output at all.
>>>
>>> Does anyone have an idea that might make this work?
>>>
>>> --
>>> 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/a76b897f-9f1f-4e82-ab18-344ae9a6e2c7%40googlegroups.com
>>> <https://groups.google.com/d/msgid/puppet-users/a76b897f-9f1f-4e82-ab18-344ae9a6e2c7%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Rob Reynolds
>> Developer, Puppet Labs
>>
>> *Join us at PuppetConf 2014 <http://www.puppetconf.com/>, September
>> 20-24 in San Francisco*
>>
>
>
>
> --
> Rob Reynolds
> Developer, Puppet Labs
>
> *Join us at PuppetConf 2014 <http://www.puppetconf.com/>, September
> 20-24 in San Francisco*
>
> --
> You received this message because you are subscribed

[Puppet Users] Re: Using Powershell in facters yields no data

I almost forgot. I have also tried setting the exec line up as a variable, 
and returning that variable, to no effect.

-- 
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/0f3bf46f-7b96-4035-80a7-2293a0e2e30a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Using Powershell in facters yields no data

Hello all,

I have been banging my head against this one for a couple of days. I am 
trying to use Powershell to comb the Windows registry for installed 
applications, such as VMware Tools, to create a custom facter. If I run 
this code from a PS prompt it works, and returns the expected data:

PS C:\> Get-ChildItem 
hklm:\software\microsoft\windows\currentversion\uninstall | ForEach-Object 
{Get-ItemProperty $_.ps
path} | Where-Object {$_.DisplayName -eq "VMware Tools"} | ForEach-Object 
-process {$_.DisplayVersion }
*9.4.6.1770165*

However, running the same thing through Puppet as a facter yields zero data:

--
Facter.add("vmtools_version") do
confine :osfamily => "Windows"
  setcode do

Facter::Util::Resolution.exec('C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
 
-Command "& {Get-ChildItem 
hklm:\software\microsoft\windows\currentversion\uninstall | ForEach-Object 
{Get-ItemProperty $_.pspath} | Where-Object {$_.DisplayName -eq \"VMware 
Tools\"} | ForEach-Object -process {$_.DisplayVersion } } "')
end
end
--

The left side shows up in the facters as "vmtools_version", but the right 
side is always empty. I have tried using the  GetItem module instead, and 
tried various combinations of the "-Command" switch, removed the "For-Each" 
handler to see if would spit out a huge block of text, and even tried 
wrapping the whole thing in a "try & catch" to see if any error states are 
generated, but have never gotten any right side output at all.

Does anyone have an idea that might make this work?

-- 
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/a76b897f-9f1f-4e82-ab18-344ae9a6e2c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: client not seeing changes made on puppetmaster

2014-09-04 Thread Brian Wilkins

You might want to file a bug, as this was supposed to be fixed in Puppet 2.7

http://projects.puppetlabs.com/issues/5318


On Thursday, September 4, 2014 3:28:10 PM UTC-4, Mike Reed wrote:
>
> Greetings,
>
> I have a class for which I would like to simply print a few parameters 
> about a node, before actually running any additional modules on the client 
> itself.  The problem I'm seeing is that after making changes to the class, 
> I don't see them being propagated to the puppet client.  Occasionally if I 
> restart puppet services on both client and master, the changes will get 
> pulled down.  In other occasions, after a certain amount of time, the 
> changes will just magically appear to get pulled down by the client.  Does 
> anybody know why this may be occurring?  It's driving me mad.
>
> I have a vanilla puppet client running puppet 3.6.2 and a puppet master 
> running version 3.6.2. and both have been recently built.
>
> *Site.pp:*
>
> # test node
> node seanconnery-01 {
>   include role
> }
>
> class role {
>   include profile::base
> }
>
> class profile::base {
>   include sys_ident
> }
>
>
> *sys_ident/init.pp*
>
> class sys_ident {
>   notify { 'system hostname':
> withpath => true,
> name => "my fqdn is $fqdn",
> }
>
>   notify {'network location':
> withpath => true,
> name => "my network is ${network}",
>   }
> }
>
> *Upon running the client, I get the expected output:*
> seanconnery-01:~$ sudo puppet agent -tv
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Info: Loading facts in /var/lib/puppet/lib/facter/network.rb
> Info: Caching catalog for seanconnery-01.domain
> Info: Applying configuration version '1409858463'
> Notice: /Stage[main]/Sys_ident/Notify[network location]/message: my 
> network is greenzone
> Notice: /Stage[main]/Sys_ident/Notify[network location]/message: defined 
> 'message' as 'my network is greenzone'
> Notice: /Stage[main]/Sys_ident/Notify[system hostname]/message: my fqdn is 
> seanconnery-01.domain
> Notice: /Stage[main]/Sys_ident/Notify[system hostname]/message: defined 
> 'message' as 'my fqdn is seanconnery-01.domain
> Notice: Finished catalog run in 0.04 seconds
>
> *However, if I add another notify to the sys_ident/init.pp like so:*
>
> class sys_ident {
>   notify { 'system hostname':
> withpath => true,
> name => "my fqdn is $fqdn",
> }
>
>   notify {'network location':
> withpath => true,
> name => "my network is ${network}",
>   }
>
>   notify {'swapfree':
> withpath => true,
> name => "my swap is ${swapfree}",
>   }
> }
>
> *I get the following on my client:*
> seanconnery-01:~$ sudo puppet agent -tv
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Info: Loading facts in /var/lib/puppet/lib/facter/network.rb
> Info: Caching catalog for seanconnery-01.domain
> Info: Applying configuration version '1409858679'
> Notice: /Stage[main]/Sys_ident/Notify[network location]/message: my 
> network is greenzone
> Notice: /Stage[main]/Sys_ident/Notify[network location]/message: defined 
> 'message' as 'my network is greenzone'
> Notice: /Stage[main]/Sys_ident/Notify[system hostname]/message: my fqdn is 
> seanconnery-01.domain'
> Notice: /Stage[main]/Sys_ident/Notify[system hostname]/message: defined 
> 'message' as 'my fqdn is seanconnery-01.domain'
> Notice: Finished catalog run in 0.04 seconds
>
> After a certain amount of undetermined time, the client will finally 
> pickup the changes but there's no rhyme or reason to it.
> Has anybody else ever seen this behavior?  I can't for the life of me 
> figure it out.
>
> As always, your help is much appreciated.
>
> m.
>
>
>
>
>

-- 
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/7e5f73bc-6050-4db6-803c-ac7d3a62a09c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Puppet 'node data' when using common node_names?

2014-09-02 Thread Brian Wilkins

Matt,

There is a better way and that is to use the roles and profiles pattern. I 
use that and I have a custom facter ruby script that reads the fqdn from a 
yaml and assigns it's role. Puppet takes over from there. 

On Saturday, August 23, 2014 1:46:59 PM UTC-4, Matt W wrote:
>
> Will,
>   Thanks for the response. I know its a bit of a unique model -- but when 
> you think about it, it makes a decent amount of sense. We run hundreds of 
> nodes that are fundamentally similar .. i.e. "this is a web server, it gets 
> the XYZ package installed" and "this is a web server, it gets the ABC 
> package installed". Using hostnames to identify the systems node-definition 
> makes very little sense and leaves quite a bit of room for error. 
> Explicitly setting the node-type as a fact allows us to re-use the same 
> node types but for many different environments and keeps host-names out of 
> the mix. For example, I can quickly boot up a 
> "prod-mwise-dev-test-web-sever-thingy" using the same node definition as 
> our "prod-frontend-host" for some testing, without worrying about the 
> hostname regex structure.
>
>   Anyways that said ... what I'm really interested in knowing is why the 
> puppet-agents are pulling DOWN their "node information" from the puppet 
> masters? Is it possible that they do an upload of node information, then 
> ask for that information back, then somehow use the downloaded information 
> for their catalog request? I could see some interesting race conditions if 
> that was the case.
>
> Matt Wise
> Sr. Systems Architect
> Nextdoor.com
>
>
> On Fri, Aug 22, 2014 at 7:11 PM, Wil Cooley  > wrote:
>
>>
>> On Aug 22, 2014 7:37 AM, "Matt W" > 
>> wrote:
>> >
>> > Anyone have any thoughts on this?
>> >
>>
>> I have to say, using an identical node name as a way of assigning the 
>> node's role is an "interesting" approach. I would not be surprised if you 
>> run into other difficulties with this approach; some even harder to find. 
>> Even something like an appended unique identifier, such as from the host 
>> ID, MAC address, serial number, hashed SHA1, etc would have been better.
>>
>> Be that as it may, life would be dull if we didn't have to live with the 
>> sins of the past. You might check the config guide 
>> https://docs.puppetlabs.com/references/3.6.latest/configuration.html but 
>> in thinking about it, if you found a setting and tried to use a fact in it, 
>> you'd probably just get the master's fact.
>>
>> The reports, at least, should be easy - since they're pluggable, you 
>> could copy the existing "lib/puppet/reports/store.rb" to a new name & 
>> module and tweak the storage location.
>>
>> Wil
>>
>> > On Thursday, August 14, 2014 10:39:16 AM UTC-7, Matt W wrote:
>> >>
>> >> We noticed that our puppet reports and our puppet node data stored on 
>> our puppet servers is always written out in the form of the 'node name'. So 
>> when we use a node name like 'prod_webserver' across many webserver 
>> machines, we get a tree of reports and node data like this:
>> >>
>> >>> /var/lib/puppet/yaml/node/prod_web.yaml
>> >>> /var/lib/puppet/yaml/facts/prod_web.yaml
>> >>> /var/lib/puppet/reports/prod_web
>> >>> /var/lib/puppet/reports/prod_web/201408130200.yaml
>> >>> /var/lib/puppet/reports/prod_web/201408140811.yaml
>> >>> /var/lib/puppet/reports/prod_web/201408121328.yaml
>> >>> /var/lib/puppet/reports/prod_web/201408130743.yaml
>> >>> /var/lib/puppet/reports/prod_web/201408140454.yaml
>> >>
>> >>
>> >> Where each of those reports likely reflects a compilation run for a 
>> different host... and the facts/node files at the top are getting 
>> constantly re-written as new clients come in.
>> >>
>> >> Is there a way to change the behavior of the data there to be written 
>> out based on the ${::fqdn} of the host (or certname) rather than its node 
>> name?
>> >>
>> >> (our client puppet configs ...)
>> >>>
>> >>> [main]
>> >>> ...
>> >>> node_name = facter
>> >>> node_name_fact = puppet_node
>> >>
>> >>
>> >> (a client puppet fact file...)
>> >>>
>> >>> puppet_node=prod_web
>> >>> puppet_environment=production
>> >>> package=frontend=some-version-here
>> >>> app_group=us1
>> >
>> > -- 
>> > 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/40c0048d-fc90-4006-99da-98bfa9ba94a7%40googlegroups.com
>> .
>> >
>> > For more options, visit https://groups.google.com/d/optout.
>>  
>> -- 
>> 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/adxt68xO210/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> puppet-users...@googlegroups.c

Re: [Puppet Users] puppet dead but pid file exists

2014-09-02 Thread Brian Wilkins

It probably died (either ps -ef | grep puppetmaster | awk '{print $2}' | 
xargs kill -9) or otherwise. Just remove the pid file and continue. You can 
examine the pid file to see if a process with that PID and named 
puppetmasterd exists. More than likely not.

On Tuesday, September 2, 2014 10:56:59 AM UTC-4, Spriya wrote:
>
> Hi John
>
> This is the way i am doing:
>
>
>
>
>
>
>
>
>
> *service puppetmaster stopStopping 
> puppetmaster: [FAILED][root@cluster2 
> puppet]# service puppetmaster startStarting 
> puppetmaster: [  OK  ][root@cluster2 
> puppet]# service puppetmaster statuspuppet dead but pid file existsLet me 
> know*
>
>
> On Tuesday, September 2, 2014 7:50:12 AM UTC-7, JohnK wrote:
>>
>> How are you stopping Puppetmaster? If you are not gracefully shutting 
>> puppetmaster down then the PID file will not be deleted.
>>
>>
>> John Kennedy  (_8(|)
>> I have a yellow dog:
>> http://www.theyellowdogproject.com/The_Yellow_Dog_Project/About.html
>>
>> Why would anyone foster a dog/cat?
>> I would rather cry watching them leave our home to live a life of 
>> happiness and joy in a loving home than cry because no one stepped up to 
>> help them and they died alone, frightened, and sad in a shelter.
>>
>>
>> On Tue, Sep 2, 2014 at 10:47 AM, Spriya  wrote:
>>
>>> Hi,
>>>
>>> I am having an issue when restarting puppetmaster.
>>> *$service puppetmaster status*
>>> *puppet dead but pid file exists*
>>>
>>>
>>> Let me know what might be the issue.
>>>
>>> -- 
>>> 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/667caddf-93a3-4f3e-97bb-87c42996b727%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/b9e4f4fd-eb18-45f0-b936-0e012c9920ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Using puppet with Apache mod_disk_cache and passenger over SSL

2014-09-02 Thread Brian Wilkins

I turned off high performance, but every request still hits the 
puppetmaster. Any more ideas?

On Friday, August 29, 2014 5:57:30 PM UTC-4, Wil Cooley wrote:
>
> On Fri, Aug 29, 2014 at 9:50 AM, Brian Wilkins  > wrote:
>
>> # RHEL/CentOS:
>> # And the passenger performance tuning settings:
>> PassengerHighPerformance On
>>
>
> The Passenger doc says that this bypasses several layers of Apache 
> processing, so it is incompatible with mod_rewrite and others -- I would 
> not be surprised if it also was the source of your trouble.
>  
> Wil
>

-- 
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/24ba6a00-15ac-46de-be37-f002c2ab7a1c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Using puppet with Apache mod_disk_cache and passenger over SSL

2014-08-29 Thread Brian Wilkins

I have tried to setup Apache with passenger to host the puppetmaster but I 
also want to cache. I have no problems running puppet within Passenger with 
httpd. I also enabled mod_disk_cache within Apache. However, I still see my 
puppet client htting the puppetmaster and the puppetmaster compiles the 
manifest every time. In /var/cache/mod_cache, I can see that the data was 
properly cached. 

What is wrong with my configuration that still allows httpd to serve up the 
request from the puppetmaster rather than using the cache? I was looking at 
lessening the load on the puppetmaster and have the cache handle common 
requests.

LoadModule ssl_module modules/mod_ssl.so

ServerName hostname

# RHEL/CentOS:
# And the passenger performance tuning settings:
PassengerHighPerformance On
PassengerUseGlobalQueue On
# Set this to about 1.5 times the number of CPU cores in your master:
PassengerMaxPoolSize 6
# Recycle master processes after they service 1000 requests
PassengerMaxRequests 1000
# Stop processes if they sit idle for 10 minutes
PassengerPoolIdleTime 600
PassengerTempDir /var/run/passenger

# Add %D for "The time taken to serve the request, in microseconds."

LogFormat "%h %l %u %t \"%r\" %>s %b %D \"%{Referer}i\" \"%{User-Agent}i\"" 
puppet

Listen 8140

SSLEngine On

# Only allow high security cryptography. Alter if needed for 
compatibility.
SSLProtocol All -SSLv2
SSLCipherSuite  HIGH:!ADH:RC4+RSA:-MEDIUM:-LOW:-EXP
SSLCertificateFile  /var/lib/puppet/ssl/certs/hostname.pem
SSLCertificateKeyFile   /var/lib/puppet/ssl/private_keys/hostname.pem
SSLCertificateChainFile /var/lib/puppet/ssl/ca/ca_crt.pem
SSLCACertificateFile/var/lib/puppet/ssl/ca/ca_crt.pem
SSLCARevocationFile /var/lib/puppet/ssl/ca/ca_crl.pem
SSLVerifyClient optional
SSLVerifyDepth  1
SSLOptions  +StdEnvVars +ExportCertData

# These request headers are used to pass the client certificate
# authentication information on to the puppet master process
RequestHeader set X-SSL-Subject %{SSL_CLIENT_S_DN}e
RequestHeader set X-Client-DN %{SSL_CLIENT_S_DN}e
RequestHeader set X-Client-Verify %{SSL_CLIENT_VERIFY}e

RackAutoDetect On
DocumentRoot /usr/share/puppet/rack/puppetmasterd/public/

Options Indexes
AllowOverride None
Order Allow,Deny
Allow from All



   
  ExpiresActive On
  ExpiresDefault "access plus 30 minutes"
   


   CacheEnable disk /production/file_metadata/
   CacheEnable disk /production/file_metadatas/
   CacheRoot "/var/cache/mod_cache"
   CacheDefaultExpire 1800
   CacheIgnoreNoLastMod On




mod_cache]# ls -la
total 40
drwxr-xr-x  10 apache apache 4096 Aug 29 12:37 .
drwxr-xr-x. 18 root   root   4096 Aug 29 12:36 ..
drwx--   3 apache apache 4096 Aug 29 12:37 Hk
drwx--   3 apache apache 4096 Aug 29 12:37 K5
drwx--   3 apache apache 4096 Aug 29 12:37 Q9
drwx--   3 apache apache 4096 Aug 29 12:37 Rl
drwx--   3 apache apache 4096 Aug 29 12:37 St
drwx--   3 apache apache 4096 Aug 29 12:37 ui
drwx--   3 apache apache 4096 Aug 29 12:37 wV
drwx--   3 apache apache 4096 Aug 29 12:37 _Z


-- 
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/e5761830-21de-4400-879e-218caa2fd004%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Using yaml to create custom array fact

2014-08-28 Thread Brian Wilkins

I would actually put role higher than node simply because you will assign 
the common role parameters first and then node specific parameters last. 
This is how I do it in my hiera.yaml:

---
:backends:
  - yaml
:hierarchy:
  - common
  - "role/%{::system_role}"
  - node/%{::fqdn}
  - "%{environment}"
  - global

:yaml:
  :datadir: /etc/puppet/data

then in my common.yaml:

classes:
  - profiles::common

profiles::nagios_resource::hostgroups: %{::system_role}

profiles::nagios_resource::allowed_hosts:
  - '127.0.0.1'
  - 'hostname'
  - 'hostname'

profiles::logstash::brokers:
  - ip
  - ip

profiles::nagios_resource::connection_to_redis_check::check_host:
  - 'hostname'
  - 'hostname'

profiles::collectd::graphite_host: 'hostname'
profiles::collectd::graphite_port: '2103'

Then I auto assign my roles using facter:

/etc/puppet/modules/roles/lib/facter/system_role.rb

Facter.add(:system_role) do
  setcode do
host = Facter.value(:fqdn)
declared_role = Facter.value(host)
declared_role.nil? ? 'general' : declared_role
  end
end

Under /etc/puppet/modules/roles/files/system_role_fact.yaml

---
host1: admin
host2: servicemix
host3: logstash_indexer
etc


On Thursday, August 28, 2014 10:33:47 AM UTC-4, Mark Rosedale wrote:
>
> Hello,
>
> So I'm using stlib with the /etc/facter/facts.d/ to set up some custom 
> facts of some of my nodes. What I want to do is use yaml to set an array in 
> facter that will then get interpreted by Hiera. 
>
> Let me give an example. I have the following hierarchy. 
> :hierarchy:
>   - "node/%{::fqdn}"
>   - "cust/%{::cust}"
>   - "role/%{::role}"
>   - base
>
> I can set the cust fact and that should just be one customer. But the role 
> may not be. So what I'd like to do is set the role fact to be an array and 
> have that interpreted by hiera. Is this possible? 
>

-- 
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/892484f7-2643-4608-91ef-06086296ebfe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Challenge: who am i and what do i do

2014-08-28 Thread Brian Wilkins

We do the same thing as Ramin. Essentially have a custom role fact that is 
based on hostname. After initial "check-in" with the puppetmaster, the 
agent knows it role and is provisioned as such. We use the role/profile 
design pattern.

On Wednesday, August 27, 2014 1:41:25 AM UTC-4, Ramin K wrote:
>
> On 8/26/2014 12:41 PM, Alex Demitri wrote: 
> > Hi guys - i am fairly new to puppet and i am trying to figure out ways 
> > to implement it in my organization to make good use of it. One thing we 
> > thought would be useful to better our deployment process, is to add a 
> > mechanism that would have a vanilla server getting installed on a VM, 
> > boot up, check into puppet and figure out these three questions: 
> > 
> > 1) Where am I? 
> >  - in what Datacenter/Availability zone am I? Based on that, what 
> > syslog servers do i have to use, NTP servers, etc.. 
> > 2) Who am I? 
> >  - what server am i? What files do i need for basic functions? 
> > 3) What am I supposed to do? 
> >  - based on what server I am, what am i supposed to do? do i have to 
> > run Tomcat? Apache? And if yes, where are my configuration files? 
> > 
> > In short, find a holistic way for a system to come up to speed by 
> > itself. I already thought of using meaningful hostnames for the roles of 
> > the servers but that does not work well in the cloud... 
> > 
> > Thoughts? 
> > 
> > Thanks! 
> > Alex 
>
> When we provision machines the system passes a few flags that do the 
> equivalent of 
>
> sudo FACTER_role=frontend puppet agent --environment stage --certname 
> fe34.usw1.example.com 
>
> role is a custom fact that needs to be set the first time as shown 
> above. Puppet does the Hiera lookup based on $role and $env with 
> $certname or nodename as the final arbiter. That's as much config as we 
> need, but no reason you couldn't add various ec2 facts to the hierarchy. 
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/4e888f46-5e95-455f-8027-d3f0667e2b86%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Report processor failed: wrong status line: ""

2014-08-28 Thread Brian Wilkins

Fixed by removing https from puppet.conf and changing puppet_dashboard.rb:

require 'puppet'

HOST = 'hostname'
PORT = 443

Puppet::Reports.register_report(:puppet_dashboard) do
  desc "Send report information to Puppet-Dashboard"

  def process
https = Net::HTTP.new(HOST, PORT)
https.use_ssl = true
https.verify_mode = OpenSSL::SSL::VERIFY_NONE
https.start do |conn|
  conn.post "/reports/upload", "report=" + CGI.escape(self.to_yaml)
end
  end
end


On Wednesday, August 27, 2014 5:17:07 PM UTC-4, Brian Wilkins wrote:
>
> I am seeing this issue every time puppet runs. I am using Puppet 
> Dashboard. I have reports being delivered via https and my puppetmaster 
> runs in Passenger. I see to have configured everything correctly and even 
> copied over the proper ruby scripts to their directories to get https to 
> work. Any ideas?
>
> puppet.conf
> ---
> [main]
> # The Puppet log directory.
> # The default value is '$vardir/log'.
> logdir = /var/log/puppet
>
> # Where Puppet PID files are kept.
> # The default value is '$vardir/run'.
> rundir = /var/run/puppet
>
> # Where SSL certificates are kept.
> # The default value is '$confdir/ssl'.
> ssldir = $vardir/ssl
>
> # PuppetDB settings to store configurations
> storeconfigs = true
> storeconfigs_backend = puppetdb
>
> pluginsync = true
>
> [master]
> certname = puppetmaster
> # forward reports to puppet dashboard
>
> reports = store, https, puppet_dashboard
> reporturl = https://host/reports/upload
> storeconfigs = true
> storeconfigs_backend = puppetdb
>
> [agent]
> certname = puppetmaster
> # The file in which puppetd stores a list of the classes
> # associated with the retrieved configuratiion.  Can be loaded in
> # the separate ``puppet`` executable using the ``--loadclasses``
> # option.
> # The default value is '$confdir/classes.txt'.
> classfile = $vardir/classes.txt
>
> # Where puppetd caches the local configuration.  An
> # extension indicating the cache format is added automatically.
> # The default value is '$confdir/localconfig'.
> localconfig = $vardir/localconfig
>
> server = host
>
> reports = false
>
>

-- 
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/167b9d51-5fd5-47e3-b3ae-9b2afdb3c5e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Report processor failed: wrong status line: ""

2014-08-27 Thread Brian Wilkins

I am seeing this issue every time puppet runs. I am using Puppet Dashboard.
I have reports being delivered via https and my puppetmaster runs in
Passenger. I see to have configured everything correctly and even copied
over the proper ruby scripts to their directories to get https to work. Any
ideas?

puppet.conf
---
[main]
# The Puppet log directory.
# The default value is '$vardir/log'.
logdir = /var/log/puppet

# Where Puppet PID files are kept.
# The default value is '$vardir/run'.
rundir = /var/run/puppet

# Where SSL certificates are kept.
# The default value is '$confdir/ssl'.
ssldir = $vardir/ssl

# PuppetDB settings to store configurations
storeconfigs = true
storeconfigs_backend = puppetdb

pluginsync = true

[master]
certname = puppetmaster
# forward reports to puppet dashboard

reports = store, https, puppet_dashboard
reporturl = https://host/reports/upload
storeconfigs = true
storeconfigs_backend = puppetdb

[agent]
certname = puppetmaster
# The file in which puppetd stores a list of the classes
# associated with the retrieved configuratiion. Can be loaded in
# the separate ``puppet`` executable using the ``--loadclasses``
# option.
# The default value is '$confdir/classes.txt'.
classfile = $vardir/classes.txt

# Where puppetd caches the local configuration. An
# extension indicating the cache format is added automatically.
# The default value is '$confdir/localconfig'.
localconfig = $vardir/localconfig

server = host

reports = false

--
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/3db31ebf-e152-414d-8409-cb223bda%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Unrecognised escape sequence '\[' in file

2014-08-27 Thread Brian Wilkins


>
> Have you tried with two backslashes '\\' ?
>

Ah, that was it :)

Also, but why not manage multiple files in /etc/nagios/nrpe.d/ based on 
> templates instead of managing a single file, since that's much trickier? 
>

Oh, that is how I am doing it (sort of):

 class profiles::nagios_resource::vsftpd_check (
  $check_interval = $profiles::nagios_resource::settings::check_interval,
  $group = $profiles::nagios_resource::settings::group,
  $mode = $profiles::nagios_resource::settings::mode ) {

  profiles::nagios_resource::service_check { 'vsftpd': }
}

You don't need the '.*' at the end of your regexp if you're not ending it 
> with '$'. 
>

Hmm, will have to try that and see the effects. 

Thanks for the reply.


-- 
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/9674caf5-b44e-4b4e-8277-8744eedb49a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Unrecognised escape sequence '\[' in file

2014-08-27 Thread Brian Wilkins

I am having to escape a regular expression in my match and puppet complains 
on the puppetmaster of an "Unrecognised escape sequence". How do I fix this 
so the logs don't get cluttered with this message? I am using Puppet 3.6.2.

 file_line { "nagios_monitor_check_${title}":
path   => '/etc/nagios/nrpe.cfg',
line   => 
"command[check_${title}]=/usr/lib64/nagios/plugins/check_procs 
${proc_check} ${proc_count}",
match  => "^command\[check_${title}\]=.*",
notify => Service[nrpe],
  }

-- 
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/c6b404de-b241-4fd0-a052-5142925ab8be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Encrypting /var/lib/puppet directory on clients

2014-08-20 Thread Brian Mathis

The only way to mount an encrypted volume on boot is if the password is
stored somewhere on the server itself, such as in /etc/crypttab.  Maybe you
could come up with a system that uses ssh to login and "manually" mount the
volume with a password after the system is booted.

One thing to be aware of is that disk encryption at this level provides no
additional security within the system -- anyone logged in can see and
access all the files (subject to standard file permissions).  It does help
with data on the underlying disk, which is only really of use when the
machine is completely turned off, protecting it from an administrator on
the VM host (though they would have full access to your system anyway), or
from a SAN admin.

❧ Brian Mathis
@orev

On Wed, Aug 20, 2014 at 1:07 PM, Eugene Sapozhnikov 
wrote:

> I have been given a project to secure our client hosts.
>
> One of the requirements was to setup an encrypted volume and mount it over
> /var/puppet/lib .
>
> the other requirement was to have the encryption key reside only on the
> puppet master.
>
> I have been able to use cryptsetup to have puppet configure and mount the
> encrypted volume successfully.
>
> But I am running into a roadblock when the client server reboots and the
> volume is unmounted. I can't use puppet to mount the volume as the puppet
> agent will not connect successfully without the /var/lib/puppet being
> mounted so it can use original SSl cert.
>
>
> Wanted to see if anyone here have tried any similar setups to what i am
> trying to achieve.
>
>
> Thanks.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/a532006d-e3cd-4c1b-bd6f-91a388e68fb0%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/a532006d-e3cd-4c1b-bd6f-91a388e68fb0%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> 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/CALKwpEz7kjusMxbqGPDv%2B10u-AwHd2O_xvfMVVvgyweYJjQPrw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Globally ignore .svn

2014-08-07 Thread Brian Wilkins

Hmm, it's working now! Thanks

On Thursday, August 7, 2014 6:11:41 PM UTC-4, Garrett Honeycutt wrote:
>
> On 8/7/14 9:10 AM, Brian Wilkins wrote: 
> > In Puppet 3.6.2, how do you globally ignore .svn directories? Links on 
> > the internet state to put File { ignore => '.svn' } in site.pp but that 
> > does not work. I tried putting it in nodes.pp, but I receive the error: 
> > "Invalid parameter ignore on File[etc_facter_folder] at  > manifest> on node " 
> > 
>
> Hi Brian, 
>
> Putting that in your site.pp should do it. Perhaps you are using the 
> wrong site.pp. 
>
> I use the following 
>
>
>   # Ignoring version control artifacts 
>   File { 
> backup => 'main', 
> ignore => [ '.svn', 
> '.git', 
> 'CVS', 
> '.bzr' ], 
>   } 
>
>
> https://github.com/transforia/puppet-modules/blob/master/manifests/site.pp#L7-14
>  
>
> Best regards, 
> -g 
>
> -- 
> Garrett Honeycutt 
> @learnpuppet 
> Puppet Training with LearnPuppet.com 
> Mobile: +1.206.414.8658 
>

-- 
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/f24619bd-5dcc-4a1b-ae58-602cff1279ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Globally ignore .svn

2014-08-07 Thread Brian Wilkins

In Puppet 3.6.2, how do you globally ignore .svn directories? Links on the 
internet state to put File { ignore => '.svn' } in site.pp but that does 
not work. I tried putting it in nodes.pp, but I receive the error: "Invalid 
parameter ignore on File[etc_facter_folder] at  on node 
"


-- 
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/0087976b-2094-48c5-8610-d4fc6eaf90c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Set ACLs on Files Logstash Must Monitor

2014-08-04 Thread Brian Wilkins

Rather than typing out hundreds of files that logstash has to monitor and 
put it into my profiles::logstash::acl class, how are others maintaining 
the actions to set the ACLs on files that logstash has to monitor? Right 
now, I am doing this for every file that logstash has to monitor:

exec { 'allow_input_file_read':
  command => "/usr/bin/setfacl -R -m u:logstash:rwx ",
  subscribe   => File_concat['ls-config'],
  refreshonly => true,
}

I monitor the changes to the configuration template that is maintained by 
the puppet forge logstash class so that the ACL is applied or re-applied 
when the logstash configuration changes.

How are others doing this?

-- 
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/fdd179e7-a3e4-4819-9173-b749d2540121%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] use client_data/catalog/.json for nagios check?

2014-07-30 Thread Brian Wilkins

We use this one : 
https://github.com/liquidat/nagios-icinga-checks/blob/master/check_puppetagent

But you have to modify it if you are using an earlier version of Python for 
the date time code to get the difference. 

It's also good if you check the report file for errors. Rather than just 
the summary. We check both.


On Wednesday, July 30, 2014 9:01:48 AM UTC-4, Jason Antman wrote:
>
> I've used two different ways of doing this, depending on whether or not 
> you have this stuff installed/running:
> (1) if you have PuppetDB, just use that. I probably have a (Python) check 
> plugin for this somewhere if you need it.
> (2) use `mco puppet status` and parse the output of that
>
> These also have the advantage that they can be run as cron'ed passive 
> checks, and submit the results very efficiently.
>
>
> On Tue, Jul 22, 2014 at 6:20 PM, Denmat > 
> wrote:
>
>> This one from RIP works ok for me:
>>
>> https://github.com/ripienaar/monitoring-scripts/blob/master/puppet/check_puppet.rb
>>
>>
>> On 23 Jul 2014, at 5:47, Atom Powers > 
>> wrote:
>>
>> I use a script that checks if the puppet client is running and parses the 
>> lastrunreport for last run time and if any errors were reported applying 
>> the catalog.
>>
>>
>> On Tue, Jul 22, 2014 at 12:36 PM, Bernard Clark > > wrote:
>>
>>> We need to be alerted whenever a puppet report from any puppet client is 
>>> late. We were thinking of having Nagios monitor the last modification time 
>>> of a client's /var/lib/puppet/client_data/catalog/.json and alert us 
>>> when that file ages too much. Anyone have a better idea?
>>>  
>>> -- 
>>> 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/5d8181b7-6911-4af1-95dd-24331425d80e%40googlegroups.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> -- 
>> Perfection is just a word I use occasionally with mustard.
>> --Atom Powers-- 
>>
>> -- 
>> 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/CAF-H%3DOkfzUo9JD9Jt_s8z3zr-w5f5M%3DGrZACWc_s%2B52E0DrE4g%40mail.gmail.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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/FF386C74-4A77-4EE4-BE09-62D0ACB129A1%40gmail.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/de6ac3cc-e46e-4b9e-aa1b-962b6382dc3c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Wrap Package in a define

2014-07-21 Thread Brian Wilkins

Thanks David. We have taken the route of downloading the necessary 
dependencies and then explicitly setting the source for each package 
statement. We have an FTP server for our yum repo so we just added a pip 
directory and provide the ftp:// URL to pip. That seems to work.

On Monday, July 21, 2014 5:53:01 AM UTC-4, David Schmitt wrote:
>
>
> Hi Brian, 
>
> On 2014-07-18 14:32, Brian Wilkins wrote: 
> > Hello, 
> > 
> > We are trying to use the puppet-forge graphite module located here: 
> > 
> https://github.com/echocat/puppet-graphite/blob/master/manifests/install.pp 
> > and our servers will not have access to the Internet. So we are 
> > downloading all the pip packages to a local repository and will point 
> > pip to each package. I would like to wrap the Package type so I can 
> > provide the source. How would I do this so that the package name is 
> > passed to the defined type? My intent is to not change much of the code 
> > here: 
> > 
> https://github.com/echocat/puppet-graphite/blob/master/manifests/install.pp 
> > 
> > Otherwise, I will have to comment out alot of the manifest and replace 
> > with exec statements pointing to each individual package. 
>
> As far as I understand the current pip provider code, it won't work 
> anyways without access to the pypi repository. 
>
> Since pip provides a way to globally configure a different index, I 
> think that would be a much better way to achieve your goal: 
>
> > http://pip.readthedocs.org/en/latest/user_guide.html#configuration 
>
>  From a cursory glance over the possibilities, setting an environment 
> variable to override your index location might be another way to avoid 
> poisoning the global pip config. 
>
>
> Regards, David 
> -- 
> * Always looking for people I can help with awesome projects * 
> G+: https://plus.google.com/+DavidSchmitt 
> Blog: http://club.black.co.at/log/ 
> LinkedIn: http://at.linkedin.com/in/davidschmitt 
>

-- 
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/f24ebad4-f27d-41aa-978a-33ca56a9b541%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Wrap Package in a define

2014-07-18 Thread Brian Wilkins

Hello,

We are trying to use the puppet-forge graphite module located here: 
https://github.com/echocat/puppet-graphite/blob/master/manifests/install.pp 
and our servers will not have access to the Internet. So we are downloading 
all the pip packages to a local repository and will point pip to each 
package. I would like to wrap the Package type so I can provide the source. 
How would I do this so that the package name is passed to the defined type? 
My intent is to not change much of the code here: 
https://github.com/echocat/puppet-graphite/blob/master/manifests/install.pp

Otherwise, I will have to comment out alot of the manifest and replace with 
exec statements pointing to each individual package.


-- 
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/7bbc783a-589a-42b3-aaa5-993d43f2026b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] multiple VMs from a single node.pp file

2014-07-15 Thread Brian Mathis

Off the top of my head I would think that you could either use the
'default' node, which would apply to all clients, or use a regular
expression to match the node names.  With the regex you'll need to ensure
that each VM follows a naming convention and you probably also want to make
sure you don't have multiple machines with identical names.  You can read
more about that here:

http://docs.puppetlabs.com/puppet/latest/reference/lang_node_definitions.html#the-default-node

You really don't need to do anything special with the certname -- they can
all be different.  You'll have to sign the cert for each new node as a
developer brings it online, unless you use the autosign option (which has
potential security implications).  After all, Puppet is meant to manage
many nodes with the same configuration.


❧ Brian Mathis
@orev


On Tue, Jul 15, 2014 at 3:09 PM, randal cobb  wrote:

> Hello, all...
>
> I have a scenario where all of our developers (spread geographically
> around the world) use a VMWare or VirtualBox VM on their local desktop to
> develop portions of a single product.  I've seemed to inherit this
> nightmare of a process and believe I can make it much simpler, quicker, and
> cleaner using Puppet.  Currently, they have to download an 80Gb VM image
> from a single server in the US; so, because of the massive size of the VM,
> most developers never upgrade their VMs to the latest image.   I know that
> Puppet can fix this for me, but I have a few questions I'm hoping y'all can
> help answer (I've used puppet for a few months to manage some
> infrastructure servers, so concepts aren't alien to me).  Here are my
> questions:
>
> Supposed I have 200 different machines (VMs) sitting on each developer's
> desktop (rather in their VMware hypervisor)...
> 1) can they all have the same certname, so I only have to maintain a
> single node.pp manifest?
> 2) If so, how are SSL certs maintained, given there would be 200 different
> VMs trying to use the same set of certs.  Or, does that even matter from a
> node perspective?
> 3) If not, do I REALLY have to maintain 200 different manifests; all
> identical to each other?
>
> I've been able to put together a single node.pp file that sets up
> everything for them, so they only download a 2.8Gb bare VM image and puppet
> does the rest.  But, when firing up subsequent VMs, of course the client
> gets all confused because the generated certs don't match up.
>
> Any suggestions for a better solution, or workaround to this one?  (I've
> thought about using NAT and a fixed MAC address, but with so many
> developers out there, I'm sure some will re-create MAC addresses at some
> point during their initial setup, or change their networking type for the
> VM and start flooding the network with duplicated mac errors).
>
> I'm sure I'm not the first person who's wanted to do something like this,
> so I turn to the seasoned puppet veterans for guidance!   I HAVE googled
> for solutions, but I may just not be using the right terminology to search
> with; because I keep coming up blank on how best to tackle this.
>
> Thanks in advance!
> Randy
>
> --
> 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/be08e15f-44da-43f4-9f6a-8d10630ebefa%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/be08e15f-44da-43f4-9f6a-8d10630ebefa%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> 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/CALKwpEw20MY9raz%3D%2BQpNcmdy_Ws4-wo%3D3zRqiCfRGYYbtEEk5g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Stop and Start Services running on Puppet Master or Agent Machine

2014-06-26 Thread Brian Mathis

Your "source" line needs 3 slashes after "puppet:"
source => "puppet:///$puppetserver/modules/httpd/ParserService-1.0.esb",


❧ Brian Mathis
@orev


On Thu, Jun 26, 2014 at 2:47 PM, Satish Katuru 
wrote:

> Hi Brian Mathis,
>
> I tired to copy the jar files and Zip files from Master to agent machine
> but i am unable to do this.
> My init.pp looks like below:
>
> class httpd
> {
>
>
> file {
> "/home/katusa02/soa/jboss-soa-p-5/jboss-as/server/default/deploy/ParserService-1.0.esb":
> ensure => present,
> owner => "katusa02",
> group => "katusa02",
> mode => "0777",
> source => "puppet://$puppetserver/modules/httpd/ParserService-1.0.esb",
>
> }
>
> }
>
> I tired with ensure => file and ensure =>"present" but didn't work.
> Can you please guide me how to do this?
>
> Moreover I got following error message:
>
>
> Error:
> /Stage[main]/Httpd/File[/home/katusa02/soa/jboss-soa-p-5/jboss-as/server/default/deploy/ParserService]:
> Could not evaluate: Could not retrieve information from environment
> production source(s) puppet://
> dayrhetamp076.enterprisenet.org/modules/httpd/ParserService
>
> Regards,
> Sathish.
>
> On Saturday, June 21, 2014 3:56:43 AM UTC+5:30, Brian Mathis wrote:
>
>> Summary: Do not try to control processes directly with Puppet and instead
>> properly integrate your service into your operating system.
>>
>> -
>>
>> It sounds like you are misunderstanding how Puppet integrates into the
>> rest of the system.  Puppet should not "kill processes" directly like you
>> would with the 'kill' command (actually, it can, but this is almost
>> certainly NOT what you want).  I think you may also be misunderstanding
>> some basic concepts of running a Linux/Unix server.
>>
>> A process is not the same thing as a service.  A single service may have
>> many processes, and they are typically controlled by a script in the
>> /etc/init.d directory (or maybe somewhere else if you are on a newfangled
>> system running systemd).  If your process does not have a control script in
>> /etc/init.d, then is is NOT a "service", it's just a process you happen to
>> have running for a long time.  For Puppet to consider it a service, it must
>> be controllable using the 'service' command (on RedHat based systems), or
>> the equivalent for your version of Linux/Unix.
>>
>> What you really want is to be making and installing a bash script to
>> control your java process in /etc/init.d.  Once written, you can use Puppet
>> to install the script by using the "file" resource.  After you have that
>> done, then you can use the "service" resource to control the service as you
>> are tying to do.  The name of the service will be the name that you call
>> your script in /etc/init.d, for example: /etc/init.d/my_service.  Please do
>> not call your service "java", as it makes no sense to name a service after
>> the programming language it is written in.  If it's an accounting system
>> for example, call the service "accounting_system", or something like that.
>>
>>
>> You are bound to get some other replies telling you how to use an 'exec'
>> resource to call the "kill" command, etc..., since this is *possible* with
>> Puppet, but it is grossly abusive of its capabilities and you really should
>> not be doing that.  Please do this correctly by setting up your software as
>> a real service and then control it correctly with the "service" resource in
>> Puppet.
>>
>> I strongly suggest you walk through the Puppet tutorials at
>> https://puppetlabs.com/learn before trying to control your own custom
>> applications with it.
>>
>>
>> ❧ Brian Mathis
>> @orev
>>
>>
>> On Fri, Jun 20, 2014 at 6:02 AM, Satish Katuru 
>> wrote:
>>
>>> Hi,
>>>
>>> I am new to Puppet and We are trying to stop and start any one of the
>>> services running on the Puppet master /agent machine.
>>>
>>> Here is the Scenario:
>>>
>>>
>>> 1. we have a Jboss service running on Puppet master and I am trying to
>>> kill this service thru puppet.(this service is runnning with my userid)
>>>
>>> Service name is "java".
>>>
>>> 2. In /etc/puppet/manifests/nodes.pp I have written code like this
>>>
>>> node "servername"
>>> {
>>>
>>>

Re: [Puppet Users] Stop and Start Services running on Puppet Master or Agent Machine

2014-06-20 Thread Brian Mathis

Summary: Do not try to control processes directly with Puppet and instead
properly integrate your service into your operating system.

-

It sounds like you are misunderstanding how Puppet integrates into the rest
of the system.  Puppet should not "kill processes" directly like you would
with the 'kill' command (actually, it can, but this is almost certainly NOT
what you want).  I think you may also be misunderstanding some basic
concepts of running a Linux/Unix server.

A process is not the same thing as a service.  A single service may have
many processes, and they are typically controlled by a script in the
/etc/init.d directory (or maybe somewhere else if you are on a newfangled
system running systemd).  If your process does not have a control script in
/etc/init.d, then is is NOT a "service", it's just a process you happen to
have running for a long time.  For Puppet to consider it a service, it must
be controllable using the 'service' command (on RedHat based systems), or
the equivalent for your version of Linux/Unix.

What you really want is to be making and installing a bash script to
control your java process in /etc/init.d.  Once written, you can use Puppet
to install the script by using the "file" resource.  After you have that
done, then you can use the "service" resource to control the service as you
are tying to do.  The name of the service will be the name that you call
your script in /etc/init.d, for example: /etc/init.d/my_service.  Please do
not call your service "java", as it makes no sense to name a service after
the programming language it is written in.  If it's an accounting system
for example, call the service "accounting_system", or something like that.

You are bound to get some other replies telling you how to use an 'exec'
resource to call the "kill" command, etc..., since this is *possible* with
Puppet, but it is grossly abusive of its capabilities and you really should
not be doing that.  Please do this correctly by setting up your software as
a real service and then control it correctly with the "service" resource in
Puppet.

I strongly suggest you walk through the Puppet tutorials at
https://puppetlabs.com/learn before trying to control your own custom
applications with it.

❧ Brian Mathis
@orev

On Fri, Jun 20, 2014 at 6:02 AM, Satish Katuru 
wrote:

> Hi,
>
> I am new to Puppet and We are trying to stop and start any one of the
> services running on the Puppet master /agent machine.
>
> Here is the Scenario:
>
>
> 1. we have a Jboss service running on Puppet master and I am trying to
> kill this service thru puppet.(this service is runnning with my userid)
>
> Service name is "java".
>
> 2. In /etc/puppet/manifests/nodes.pp I have written code like this
>
> node "servername"
> {
>
> Service {
>
> "java":
> ensure = >"Stopped",
>
> }
> }
>
> after this I ran this command
>
> puppet apply nodes.pp
>
> Nothing has happend.Still the process is running.(I am able to see the
> process id : ps -ef|grep java)
>
> 3.After this i created a module and place this code in init.pp in
> /etc/puppet/modues/httpd/
>
> node "servername"
> {
> inlcude httpd
> }
>
> puppet apply nodes.pp
>
>
> Nothing happend.
>
> Can you please guide us how to kill a process?
>
>
>
>
>
>
>
>
>  --
> 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/c81e168e-38f0-416c-b0c2-bd0124c9e760%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/c81e168e-38f0-416c-b0c2-bd0124c9e760%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> 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/CALKwpEzK-VLedCmo69J25eNPXRS2zsqbSy%3DErzar5fVftJ-dgA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Is anyone using Puppet for RHEL Patch management ?

2014-06-12 Thread Brian Mathis

Package updates to RHEL systems do not touch config files if they have been
changed, so it's rare that a simple update would cause any configuration to
become invalid (of course, anything is possible).  And you tested updates
and their possible config changes before deployment, right?


❧ Brian Mathis
@orev


On Thu, Jun 12, 2014 at 4:19 AM, Tim Connors 
wrote:

>
> Which means you're running with an invalid config for up to 30 minutes
> before your services are restarted back with your desired config?
>
> On Wed, 11 Dec 2013, Dan White wrote:
>
> > I am using Puppet on RHEL systems.
> >
> > I do not use Puppet to patch the servers. I use Red Hat Network and yum
> update. Puppet then fixes config changes that package updates break.
> >
> >
> > "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: "Unix SA" 
> > To: puppet-users@googlegroups.com
> > Sent: Wednesday, December 11, 2013 11:15:19 AM
> > Subject: [Puppet Users] Is anyone using Puppet for RHEL Patch management
> ?
> >
> >
> > Hello Guys,
> >
> >
> > want to know if anyone is using puppet to apply patches to RedHat
> systems ? i would like to understand architecture of it .. how do you guys
> use it to get patches from RedHat, how do you test and deploy it on prod
> servers ?
> >
> >
> > Regards,
> > DJ
> >
> >
>
> --
> Tim Connors
>
> --
> 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/alpine.DEB.2.02.1406121818570.19118%40dirac.rather.puzzling.org
> .
> 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/CALKwpExn_Qv0vEMJ4CsQkit%2BvHU1A5fyD5ujpDKsz-Lx3ZK%2BiA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Using Puppet to roll out Windows Updates

2014-06-11 Thread Brian Mathis

Why not use WSUS?  This is what it's made for, it's already part of
Windows, and can be easily managed from the WSUS console.  Once you're
operating in a Windows world, your life will be far better by doing things
the "Windows Way" instead of resisting it.

Sounds like a case of: "*if the only tool you have is a hammer, to treat
everything as if it were a nail"*

Incidentally, you typically wouldn't use Puppet to handle OS updates either
(apt-get upgrade, yum update), which is the same thing, so it's not even a
case of a Windows-specific thing.

That's not to say that Puppet couldn't be abused into doing it.


❧ Brian Mathis
@orev


On Wed, Jun 11, 2014 at 12:35 PM, Pskov Shurik 
wrote:

> Hello everyone,
>
> We have recently started using Puppet to do initial system prep on new
> servers, such as Apache, Java installs, hosts file updates etc. However, we
> are now exploring the possibility of extending Puppet to manage Windows
> Updates. Er... has anyone done it?
>
> The requirements are simple: give Puppet a list of KB items to download
> and it would go and deploy these on whatever servers Puppet Agent is
> running on. We are happy for servers to go download a copy of patches, so
> we won't be using Puppet's central repository of installers (since Windows
> update installers are different depending on OS and architecture).
>
> I found a PowerHell script here -
> http://www.flobee.net/programmatically-run-windows-update-as-part-of-a-broader-patch-and-reboot-process/
> - that could probably be, somehow, integrated into Puppet but if there's an
> easier way or modules that do it already, then I would appreciate a pointer.
>
> Thanks
> Alex
>
> --
> 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/87d8f0d8-8c47-4236-843a-5b5f1aa5d1b9%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/87d8f0d8-8c47-4236-843a-5b5f1aa5d1b9%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> 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/CALKwpEzSwtjPR4rfZp1wR9kQboDjWbWnhAjgj0e1DTSOg1_DVg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Exception LoadErrror with Passenger and Apache httpd

2014-06-10 Thread Brian Wilkins

I have been running my puppetmaster with passenger and apache httpd 
successfully for sometime now. During a recent upgrade to Puppet 3.6.1, I 
am seeing this following exception in /var/log/httpd/error_log :

 *** Exception LoadError in PhusionPassenger::Rack::ApplicationSpawner (no 
such file to load -- rack) (process 3072, thread #):

I tried setting my gem environment in the config.ru, but that didn't seem 
to help. I see that the puppet 3.6.1 gem is installed. I installed puppet 
3.6.1 via RPM not gem. I also ran gem clean to no avail.

Any idea how to get past this error? I see that the puppet 3.6.1 gem has a 
rack - maybe it can't be found in my path?

-- 
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/bcd4ecb0-5126-45c7-ae9f-b451da6a6dcc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] rspec - Unable to find class ::logstash

Thanks Johan. It turns out that I had to set my path's explicitly in my 
spec_helper.rb. For some reason, the automatically created spec_helper.rb 
created by rspec-puppet-init did not create a usuable file. My tests are 
running successfully now.

Brian

On Wednesday, June 4, 2014 5:05:05 PM UTC-4, Johan De Wit wrote:
>
>  Hi, 
>
> the scoping of the class is indeed needed, but i believe that is a parser 
> issue.
>
> I did the test wit class { '::vim': version => '7.4' }
>
> on my master with puppet master --compile  i got following :
>
> {
>   "metadata": {
> "api_version": 1
>   },
>   "data": {
> "classes": [
>   "settings",
>
>   
>
>  "vim",
>
> 
>
> And that is what you should check in your rspec file.  
>
> In your manifests, you need indeed the scoping, in your spec, you don't
>
> hth
>
> jo   
>
>
> On 04/06/14 21:56, Brian Wilkins wrote:
>  
> It is needed to disambiguate from profiles::logstash and just logstash 
> classes. If I remove it, then it will complain that logstash is already 
> loaded when it tries to load profiles::logstash.
>
> On Wednesday, June 4, 2014 3:52:01 PM UTC-4, Garrett Honeycutt wrote: 
>>
>> On 6/4/14, 3:13 PM, Brian Wilkins wrote: 
>> > I think you missed the part where it is complaining about line 10 in my 
>> > profiles::logstash::install module 
>> > 
>> > class { '::logstash': 
>> > 
>> > Removing ::logstash from the spec file has the same complaint. 
>> > 
>> > Brian 
>> > 
>> > On Wednesday, June 4, 2014 3:11:14 PM UTC-4, Garrett Honeycutt wrote: 
>> > 
>> > On 6/4/14, 2:30 PM, Brian Wilkins wrote: 
>> > > I am trying to write unit tests of my puppet modules. In my 
>> > > profiles::logstash::install, I disambiguate the call to 
>> > > /etc/puppet/modules/logstash by using ::logstash in my class 
>> > definition 
>> > > like so: 
>> > > 
>> > > class profiles::logstash::install() { 
>> > >   $ensure = $profiles::logstash::enable ? {true => present, 
>> > default => 
>> > > absent} 
>> > >   $status = $profiles::logstash::start ? {true => enabled, 
>> default => 
>> > > disabled} 
>> > > 
>> > >   class { '::logstash': 
>> > > ensure  => $ensure, 
>> > > status  => $status, 
>> > > version => $profiles::logstash::version 
>> > >   } 
>> > > } 
>> > > 
>> > > However, when I run my spec file: 
>> > > 
>> > > require 'spec_helper' 
>> > > 
>> > > describe "profiles::logstash" do 
>> > >   it { should contain_class("::logstash") } 
>> > >   it { should contain_class("profiles::logstash::install") } 
>> > >   it { should contain_class("profiles::logstash::config") } 
>> > > end 
>> > > 
>> > > I get the errors: 
>> > > 
>> > > 1) profiles::logstash 
>> > >  Failure/Error: it { should contain_class("::logstash") } 
>> > >  Puppet::Error: 
>> > >Puppet::Parser::AST::Resource failed with error 
>> ArgumentError: 
>> > > Could not find declared class ::logstash at 
>> > > 
>> > 
>> /etc/puppet/modules/profiles/spec/fixtures/modules/profiles/manifests/logstash/install.pp:10
>>  
>>
>> > 
>> > > on node els4167.els.dev 
>> > >  # ./spec/classes/logstash_spec.rb:4 
>> > > 
>> > >   2) profiles::logstash 
>> > >  Failure/Error: it { should 
>> > > contain_class("profiles::logstash::install") } 
>> > >  Puppet::Error: 
>> > >Puppet::Parser::AST::Resource failed with error 
>> ArgumentError: 
>> > > Could not find declared class ::logstash at 
>> > > 
>> > 
>> /etc/puppet/modules/profiles/spec/fixtures/modules/profiles/manifests/logstash/install.pp:10
>>  
>>
>> > 
>> > > on node els4167.els.dev 
>> > >  # ./spec/classes/logstash_spec.rb:5 
>> > > 
>>

Re: [Puppet Users] rspec - Unable to find class ::logstash

It is needed to disambiguate from profiles::logstash and just logstash 
classes. If I remove it, then it will complain that logstash is already 
loaded when it tries to load profiles::logstash.

On Wednesday, June 4, 2014 3:52:01 PM UTC-4, Garrett Honeycutt wrote:
>
> On 6/4/14, 3:13 PM, Brian Wilkins wrote: 
> > I think you missed the part where it is complaining about line 10 in my 
> > profiles::logstash::install module 
> > 
> > class { '::logstash': 
> > 
> > Removing ::logstash from the spec file has the same complaint. 
> > 
> > Brian 
> > 
> > On Wednesday, June 4, 2014 3:11:14 PM UTC-4, Garrett Honeycutt wrote: 
> > 
> > On 6/4/14, 2:30 PM, Brian Wilkins wrote: 
> > > I am trying to write unit tests of my puppet modules. In my 
> > > profiles::logstash::install, I disambiguate the call to 
> > > /etc/puppet/modules/logstash by using ::logstash in my class 
> > definition 
> > > like so: 
> > > 
> > > class profiles::logstash::install() { 
> > >   $ensure = $profiles::logstash::enable ? {true => present, 
> > default => 
> > > absent} 
> > >   $status = $profiles::logstash::start ? {true => enabled, default 
> => 
> > > disabled} 
> > > 
> > >   class { '::logstash': 
> > > ensure  => $ensure, 
> > > status  => $status, 
> > > version => $profiles::logstash::version 
> > >   } 
> > > } 
> > > 
> > > However, when I run my spec file: 
> > > 
> > > require 'spec_helper' 
> > > 
> > > describe "profiles::logstash" do 
> > >   it { should contain_class("::logstash") } 
> > >   it { should contain_class("profiles::logstash::install") } 
> > >   it { should contain_class("profiles::logstash::config") } 
> > > end 
> > > 
> > > I get the errors: 
> > > 
> > > 1) profiles::logstash 
> > >  Failure/Error: it { should contain_class("::logstash") } 
> > >  Puppet::Error: 
> > >Puppet::Parser::AST::Resource failed with error 
> ArgumentError: 
> > > Could not find declared class ::logstash at 
> > > 
> > 
> /etc/puppet/modules/profiles/spec/fixtures/modules/profiles/manifests/logstash/install.pp:10
>  
>
> > 
> > > on node els4167.els.dev 
> > >  # ./spec/classes/logstash_spec.rb:4 
> > > 
> > >   2) profiles::logstash 
> > >  Failure/Error: it { should 
> > > contain_class("profiles::logstash::install") } 
> > >  Puppet::Error: 
> > >Puppet::Parser::AST::Resource failed with error 
> ArgumentError: 
> > > Could not find declared class ::logstash at 
> > > 
> > 
> /etc/puppet/modules/profiles/spec/fixtures/modules/profiles/manifests/logstash/install.pp:10
>  
>
> > 
> > > on node els4167.els.dev 
> > >  # ./spec/classes/logstash_spec.rb:5 
> > > 
> > >   3) profiles::logstash 
> > >  Failure/Error: it { should 
> > > contain_class("profiles::logstash::config") } 
> > >  Puppet::Error: 
> > >Puppet::Parser::AST::Resource failed with error 
> ArgumentError: 
> > > Could not find declared class ::logstash at 
> > > 
> > 
> /etc/puppet/modules/profiles/spec/fixtures/modules/profiles/manifests/logstash/install.pp:10
>  
>
> > 
> > > on node els4167.els.dev 
> > >  # ./spec/classes/logstash_spec.rb:6 
> > > 
> > > How do I get rspec to find my class /etc/puppet/modules/logstash 
> > and get 
> > > it to reference ::logstash as a disambiguation? 
> > 
> > Hi Brian, 
> > 
> > Using ::class is not needed and should not be done. If you still 
> > want to 
> > do that in your class, try changing the spec by dropping the 
> preceding 
> > double colons. 
> > 
> > Best regards, 
> > -g 
> > 
> > -- 
> > Garrett Honeycutt 
> > @learnpuppet 
> > Puppet Training with LearnPuppet.com 
> > Mobile: +1.206.414.8658 
> > 
>
> Hi Brian, 
>
> Recommend dropping the preceding double colons all around. It is not 
> needed at all. 
>
> Br, 
> -g 
>
>
>
> -- 
> Garrett Honeycutt 
> @learnpuppet 
> Puppet Training with LearnPuppet.com 
> Mobile: +1.206.414.8658 
>

-- 
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/141ee867-2464-4187-9e55-5aab364c1700%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] rspec - Unable to find class ::logstash

I think you missed the part where it is complaining about line 10 in my 
profiles::logstash::install module

class { '::logstash': 

Removing ::logstash from the spec file has the same complaint.

Brian

On Wednesday, June 4, 2014 3:11:14 PM UTC-4, Garrett Honeycutt wrote:
>
> On 6/4/14, 2:30 PM, Brian Wilkins wrote: 
> > I am trying to write unit tests of my puppet modules. In my 
> > profiles::logstash::install, I disambiguate the call to 
> > /etc/puppet/modules/logstash by using ::logstash in my class definition 
> > like so: 
> > 
> > class profiles::logstash::install() { 
> >   $ensure = $profiles::logstash::enable ? {true => present, default => 
> > absent} 
> >   $status = $profiles::logstash::start ? {true => enabled, default => 
> > disabled} 
> > 
> >   class { '::logstash': 
> > ensure  => $ensure, 
> > status  => $status, 
> > version => $profiles::logstash::version 
> >   } 
> > } 
> > 
> > However, when I run my spec file: 
> > 
> > require 'spec_helper' 
> > 
> > describe "profiles::logstash" do 
> >   it { should contain_class("::logstash") } 
> >   it { should contain_class("profiles::logstash::install") } 
> >   it { should contain_class("profiles::logstash::config") } 
> > end 
> > 
> > I get the errors: 
> > 
> > 1) profiles::logstash 
> >  Failure/Error: it { should contain_class("::logstash") } 
> >  Puppet::Error: 
> >Puppet::Parser::AST::Resource failed with error ArgumentError: 
> > Could not find declared class ::logstash at 
> > 
> /etc/puppet/modules/profiles/spec/fixtures/modules/profiles/manifests/logstash/install.pp:10
>  
>
> > on node els4167.els.dev 
> >  # ./spec/classes/logstash_spec.rb:4 
> > 
> >   2) profiles::logstash 
> >  Failure/Error: it { should 
> > contain_class("profiles::logstash::install") } 
> >  Puppet::Error: 
> >Puppet::Parser::AST::Resource failed with error ArgumentError: 
> > Could not find declared class ::logstash at 
> > 
> /etc/puppet/modules/profiles/spec/fixtures/modules/profiles/manifests/logstash/install.pp:10
>  
>
> > on node els4167.els.dev 
> >  # ./spec/classes/logstash_spec.rb:5 
> > 
> >   3) profiles::logstash 
> >  Failure/Error: it { should 
> > contain_class("profiles::logstash::config") } 
> >  Puppet::Error: 
> >Puppet::Parser::AST::Resource failed with error ArgumentError: 
> > Could not find declared class ::logstash at 
> > 
> /etc/puppet/modules/profiles/spec/fixtures/modules/profiles/manifests/logstash/install.pp:10
>  
>
> > on node els4167.els.dev 
> >  # ./spec/classes/logstash_spec.rb:6 
> > 
> > How do I get rspec to find my class /etc/puppet/modules/logstash and get 
> > it to reference ::logstash as a disambiguation? 
>
> Hi Brian, 
>
> Using ::class is not needed and should not be done. If you still want to 
> do that in your class, try changing the spec by dropping the preceding 
> double colons. 
>
> Best regards, 
> -g 
>
> -- 
> Garrett Honeycutt 
> @learnpuppet 
> Puppet Training with LearnPuppet.com 
> Mobile: +1.206.414.8658 
>

-- 
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/213a161f-c1a4-4524-a0e0-d798fde6ef82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] rspec - Unable to find class ::logstash

I am trying to write unit tests of my puppet modules. In my 
profiles::logstash::install, I disambiguate the call to 
/etc/puppet/modules/logstash by using ::logstash in my class definition 
like so:

class profiles::logstash::install() {
  $ensure = $profiles::logstash::enable ? {true => present, default => 
absent}
  $status = $profiles::logstash::start ? {true => enabled, default => 
disabled}

  class { '::logstash':
ensure  => $ensure,
status  => $status,
version => $profiles::logstash::version
  }
}

However, when I run my spec file:

require 'spec_helper'

describe "profiles::logstash" do
  it { should contain_class("::logstash") }
  it { should contain_class("profiles::logstash::install") }
  it { should contain_class("profiles::logstash::config") }
end

I get the errors:

1) profiles::logstash
 Failure/Error: it { should contain_class("::logstash") }
 Puppet::Error:
   Puppet::Parser::AST::Resource failed with error ArgumentError: Could 
not find declared class ::logstash at 
/etc/puppet/modules/profiles/spec/fixtures/modules/profiles/manifests/logstash/install.pp:10
 
on node els4167.els.dev
 # ./spec/classes/logstash_spec.rb:4

  2) profiles::logstash
 Failure/Error: it { should 
contain_class("profiles::logstash::install") }
 Puppet::Error:
   Puppet::Parser::AST::Resource failed with error ArgumentError: Could 
not find declared class ::logstash at 
/etc/puppet/modules/profiles/spec/fixtures/modules/profiles/manifests/logstash/install.pp:10
 
on node els4167.els.dev
 # ./spec/classes/logstash_spec.rb:5

  3) profiles::logstash
 Failure/Error: it { should contain_class("profiles::logstash::config") 
}
 Puppet::Error:
   Puppet::Parser::AST::Resource failed with error ArgumentError: Could 
not find declared class ::logstash at 
/etc/puppet/modules/profiles/spec/fixtures/modules/profiles/manifests/logstash/install.pp:10
 
on node els4167.els.dev
 # ./spec/classes/logstash_spec.rb:6

How do I get rspec to find my class /etc/puppet/modules/logstash and get it 
to reference ::logstash as a disambiguation?

-- 
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/a47b6fdb-519a-453c-92ec-40787c7d2470%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Using Hiera to Populate Defined Type in Puppet 3.6

2014-06-02 Thread Brian Wilkins

FWIW, this is my working solution and I think it is much better:

/etc/puppet/modules/profiles/manifests/logstash/config.pp:

class profiles::logstash::config {
  $brokers = $profiles::logstash::brokers
  $cluster = $profiles::logstash::cluster

  if (!empty($brokers)) and (empty($cluster)) {
notice("This is a shipper.")
logstash::configfile { 'output_broker':
  content => template('profiles/logstash/output_broker.erb'),
  order   => 100
}
  } elsif (!empty($cluster)) and (!empty($brokers)) {
  notice("This is a central indexer.")
  logstash::configfile { 'input_broker':
content => template('profiles/logstash/input_broker.erb'),
order   => 10
  }
  logstash::configfile { 'output_es':
content => template('profiles/logstash/output_es.erb'),
order   => 100
  }
  }
}

/etc/puppet/modules/profiles/manifests/logstash/install.pp

class profiles::logstash::install() {
  $ensure = $profiles::logstash::enable ? {true => present, default => 
absent}
  $status = $profiles::logstash::start ? {true => enabled, default => 
disabled}

  class { '::logstash':
ensure  => $ensure,
status  => $status,
version => $profiles::logstash::version
  }
}

/etc/puppet/modules/profiles/manifests/logstash.pp:

# == Class: profiles::logstash
#
# A basic module to manage logstash
#
# === Parameters
# [*version*]
#   The package version to install
#
# [*brokers*]
#   An array of brokers to use on this node
#
# [*enable*]
#   Should the service be enabled during boot time?
#
# [*start*]
#   Should the service be started by Puppet?
#
# Note: Values here are defaults and can be overriden by Hiera
#   see - /etc/puppet/data/node/.yaml

class profiles::logstash(
   $version = "1.4.1-1_bd507eb",
   $brokers = ["172.16.14.30", "172.16.14.60"],
   $cluster = undef,
   $enable  = true,
   $start   = true
) {
   class{'profiles::logstash::install': } ->
   class{'profiles::logstash::config': } ->
   Class["profiles::logstash"]
}

And my YAML:

classes:
  - roles::logshipper

profiles::logstash::version: '1.4.1-1_bd507eb'
profiles::logstash::enable: true
profiles::logstash::start: false
profiles::logstash::brokers:
  - hostname1
  - hostname2

And my ERB files

/etc/puppet/modules/profiles/templates/logstash/

<% for @host in @brokers %>

input {
  redis {
host  => "<%= @host %>"
type  => "redis-input"
data_type => "list"
key   => "logstash"
  }
}

<% end %>

/etc/puppet/modules/profiles/templates/logstash/output_broker.erb:

<%
# iterate over brokers array passed in via Hiera and concatenate
# redis hosts for logstash configuration
host_string = "["
@brokers.each_with_index { |host,idx|
   host_string << "\"#{host}\"";
   host_string << "," if idx < @brokers.length-1
}
host_string << "]"
%>

output {
  redis {
host => <%= host_string %>
data_type => "list"
key => "logstash"
  }
}

/etc/puppet/modules/profiles/templates/logstash/output_es.erb:

output {
  elasticsearch {
cluster   => "<%= cluster %>"
index => "logstash-%{+.MM.dd.HH}"
  }
}



On Monday, June 2, 2014 11:11:32 AM UTC-4, jcbollinger wrote:
>
>
>
> On Thursday, May 29, 2014 2:39:15 PM UTC-5, Brian Wilkins wrote:
>>
>> Solved it using this tip.. it's odd but it works: 
>> http://serverfault.com/a/538877/26514
>>
>>
>
> That's odd only inasmuch as the original problem in that serverfault 
> question was different from yours.  The OP was trying to achieve a similar 
> structure to the one you are working on, though, so it is natural that what 
> worked for him also works for you.
>
> For what it's worth, I think your original problem was here:
>
> [...]
>
>   profiles::logstash::config { $name:
>content => $content,
>order   => $order,
>   }
>
> [...]
>
> The variables $content and $order had not been assigned any values in that 
> scope (class profiles::logstash::shipper), which is exactly what the error 
> message said.
>
> I think that create_resources() was a red herring.  It should have been 
> possible to use create_resources() more or less as you originally attempted 
> to do, though you should have specified the fully-qualified name of the 
> resource type ("profiles::logstash::config"), which you did not do.  
> Indeed, your final data structure appears still amenable to use with 
> create_resources().
>
>  
>
>> shipper.pp
>>
>&g

Re: [Puppet Users] params.pp/inheritance/defaults/hiera/hiera functions?

2014-06-01 Thread Brian Mathis

On Sat, May 31, 2014 at 4:46 PM, Robin Bowes  wrote:

> On Sat, 2014-05-31 at 07:12 -0700, Daniele Sluijters wrote:
> > > - Don't use automatic hiera lookups.  This removes the magic and
> > makes it more clear to everyone that the data is coming from hiera.
> >
> >
> > Hold on a sec; if you mean data bindings with 'automatic hiera
> > lookups', most certainly use them. Do not ever hardcode hiera()
> > functions in parameter lookups in your module as you module can now
> > _only_ work with Hiera and not everyone uses or wants to use hiera.
> > Instead let data bindings take care of it so that everyone can benefit
> > from your code, Hiera, ENC or by explicitly passing data in.
>
> I think the most important thing is to not hardcode hiera() functions in
> modules. That gives the flexibility for the users of the modules to
> either rely on automatic parameter lookup (APL) or explicitly pass in
> the parameters.
>
> My own preference is to use explicit hiera lookups in "profiles" and
> pass in the data to modules. APL is just a bit too magic, in my
> experience, and avoiding it makes it easier to work out where data comes
> from.
>
> R.
>


Yes, this is what I mean.  Don't use or access hiera from with *component*
modules.  You do need to use it from profile modules.  This assumes that
one is using the profile/roles pattern, which seems to be the current best
practice anyway.


❧ Brian Mathis
@orev

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

Re: [Puppet Users] Re: Puppet 3.6.0... and scaling?

What about staggering your runs? It seems trivial but at least it would reduce 
your load I think.

-- 
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/97a9d7b0-45a0-468c-b981-34ac9221aa40%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Disamiguate Profiles::Logstash and Logstash

Thanks! That worked. I am still learning. I have an additional error. Is 
there a way around this or just combine my service.pp and install.pp 
together?

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Duplicate declaration: Class[Logstash] is already declared in file 
/etc/puppet/modules/profiles/manifests/logstash/install.pp:8; cannot 
redeclare at /etc/puppet/modules/profiles/manifests/logstash/service.pp:7

This is my service.pp:

class profiles::logstash::service() {
  $status = $profiles::logstash::start ? {true => enabled, default => 
disabled}

  class { '::logstash':
status  => $status,
  }
}


On Saturday, May 31, 2014 8:26:54 AM UTC-4, Robin Bowes wrote:
>
> Fully-qualify the class name, ie. use '::logstash'. 
>
> R. 
> On 31 May 2014 13:17, "Brian Wilkins" > 
> wrote:
>
>> I am using the puppet logstash module from Forge installed at 
>> /etc/puppet/modules/logstash
>>
>> I am trying to setup my profile class as profiles::logstash. My manifest 
>> is at /etc/puppet/modules/profiles/manifests/logstash.pp
>>
>> In my /etc/puppet/modules/profiles/manifests/logstash directory I have:
>>
>> install.pp
>> config.pp
>> service.pp
>>
>> In my install.pp:
>>
>> class profiles::logstash::install() {
>>   $ensure = $profiles::logstash::enable ? {true => present, default => 
>> absent}
>>
>>   class { 'logstash':
>> ensure  => $ensure,
>> version => $profiles::logstash::version
>>   }
>> }
>>
>> Here, class refers to the /etc/puppet/modules/logstash  not 
>> /etc/puppet/modules/profiles/manifests/logstash
>>
>> However, when I do a run, it tells me
>>
>> Could not retrieve catalog from remote server: Error 400 on SERVER: 
>> Duplicate declaration: Class[Profiles::Logstash] is already declared; 
>> cannot redeclare at 
>> /etc/puppet/modules/profiles/manifests/logstash/install.pp:8
>>
>> It is referring to the "class {'logstash'" line. 
>>
>> What's the proper way to disambiguate so I can still tell the puppet 
>> logstash module to install logstash and ensure the right version?
>>  
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to puppet-users...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/137a4a4d-46f9-4e1f-841a-cda87c7e8229%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/puppet-users/137a4a4d-46f9-4e1f-841a-cda87c7e8229%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> 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/e8af8d24-21ca-4415-8d30-9a5f8e435477%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Disamiguate Profiles::Logstash and Logstash

Here is my logstash.pp at 
/etc/puppet/modules/profiles/manifests/logstash.pp:

class profiles::logstash(
   $version = "1.4.1-1_bd507eb",
   $enable  = true,
   $start   = true
) {
   class{'profiles::logstash::install': } ->
   class{'profiles::logstash::config': } ~>
   class{'profiles::logstash::service': } ->
   Class["profiles::logstash"]
}


On Saturday, May 31, 2014 8:17:34 AM UTC-4, Brian Wilkins wrote:
>
> I am using the puppet logstash module from Forge installed at 
> /etc/puppet/modules/logstash
>
> I am trying to setup my profile class as profiles::logstash. My manifest 
> is at /etc/puppet/modules/profiles/manifests/logstash.pp
>
> In my /etc/puppet/modules/profiles/manifests/logstash directory I have:
>
> install.pp
> config.pp
> service.pp
>
> In my install.pp:
>
> class profiles::logstash::install() {
>   $ensure = $profiles::logstash::enable ? {true => present, default => 
> absent}
>
>   class { 'logstash':
> ensure  => $ensure,
> version => $profiles::logstash::version
>   }
> }
>
> Here, class refers to the /etc/puppet/modules/logstash  not 
> /etc/puppet/modules/profiles/manifests/logstash
>
> However, when I do a run, it tells me
>
> Could not retrieve catalog from remote server: Error 400 on SERVER: 
> Duplicate declaration: Class[Profiles::Logstash] is already declared; 
> cannot redeclare at 
> /etc/puppet/modules/profiles/manifests/logstash/install.pp:8
>
> It is referring to the "class {'logstash'" line. 
>
> What's the proper way to disambiguate so I can still tell the puppet 
> logstash module to install logstash and ensure the right version?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/b28a3239-f0eb-4ca8-aa35-cb12e2e0ee44%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Disamiguate Profiles::Logstash and Logstash

I am using the puppet logstash module from Forge installed at 
/etc/puppet/modules/logstash

I am trying to setup my profile class as profiles::logstash. My manifest is 
at /etc/puppet/modules/profiles/manifests/logstash.pp

In my /etc/puppet/modules/profiles/manifests/logstash directory I have:

install.pp
config.pp
service.pp

In my install.pp:

class profiles::logstash::install() {
  $ensure = $profiles::logstash::enable ? {true => present, default => 
absent}

  class { 'logstash':
ensure  => $ensure,
version => $profiles::logstash::version
  }
}

Here, class refers to the /etc/puppet/modules/logstash  not 
/etc/puppet/modules/profiles/manifests/logstash

However, when I do a run, it tells me

Could not retrieve catalog from remote server: Error 400 on SERVER: 
Duplicate declaration: Class[Profiles::Logstash] is already declared; 
cannot redeclare at 
/etc/puppet/modules/profiles/manifests/logstash/install.pp:8

It is referring to the "class {'logstash'" line. 

What's the proper way to disambiguate so I can still tell the puppet 
logstash module to install logstash and ensure the right version?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/137a4a4d-46f9-4e1f-841a-cda87c7e8229%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] how to fork a Windows exe

2014-05-30 Thread Brian Mathis

AFAIK, Windows does not have a true "fork" capability.  Here are some ideas
that might help:

- Use srvany (or something else) to define a custom service.  It sounds
like this is probably what you really should be doing anyway.  Puppet is
not meant to control programs over a long term (i.e. services), it's meant
to setup other things that control them.  The Windows service framework is
meant to do that.

- Create a schedule task to run your command

- Use the "start" command to start the process.


❧ Brian Mathis
@orev


On Fri, May 30, 2014 at 12:11 PM, Bill N  wrote:

> Hi,
>
> Just wrote my first puppet module for Windows  provisioning. All is
> working well except I am having a problem running a windows exe file in
> that Puppet appears to wait for the exe to complete. At least this is the
> case when I run Puppet agent --test from the Windows Server command line.
>
> What I want to do here is install a set of files for a Riemann monitoring
> client on several Windows Server 2008 R1 VMs. These files include an exe,
> which I want to start and run in perpetuity. I don't want Puppet to wait
> for this process to complete. It appears I could run the exe in a separate
> shell using cmd.exe, but when I try that on the command line I do not see
> the named process running in the Resource Monitor. I only see cmd.exe
> running. This is not very informative.
>
> My question is, what is the best way to run this executable via Puppet?
> Should I convert the exe to a Windows service, install that and run it as a
> service? Should I use shell cmd and live with the unhelpful Resource
> Monitor listing? Or should I use Power Shell to fork the process like I
> would in linux?
>
> Any help would be most appreciated.
>
> --
> 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/07c840a9-4c52-4b99-b24c-ffc10c1f19a9%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/07c840a9-4c52-4b99-b24c-ffc10c1f19a9%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> 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/CALKwpEwEOoTvVcPRypNSHF%3DZGkw6o6SwtRe_Eafz0uJ6Pzk7ug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] params.pp/inheritance/defaults/hiera/hiera functions?

2014-05-30 Thread Brian Mathis

It sounds like you need to read through these:
http://garylarizza.com/blog/2014/02/17/puppet-workflow-part-1/
http://garylarizza.com/blog/2014/02/17/puppet-workflow-part-2/

I don't see why you'd want to remove parameters from classes.  They are
pretty critical to having a flexible infrastructure.

Some of the smaller points in those posts which I think are important (in
addition to the general pattern):
- Don't use default values in hiera.  If you don't supply (or typo) a
variable name, then the puppet run should fail.
- Don't use automatic hiera lookups.  This removes the magic and makes it
more clear to everyone that the data is coming from hiera.

For your config data showing up in other modules, I think you probably want
role or profile modules, and pass in the data as a parameter.  Your
roles/profiles should have all the custom stuff in it, not the component
modules.

Also make liberal use of the validate_* functions from stdlib to further
check your parameters have been supplied correctly.

Don't set default values to anything that is inappropriate.  If you don't
want a default for your SuperDaemon config and it needs to be explicitly
configured, then you want it to fail if no parameter is given.


❧ Brian Mathis
@orev


On Thu, May 29, 2014 at 1:58 PM, Christopher Wood <
christopher_w...@pobox.com> wrote:

> (I'm not sure how to phrase my question precisely, so this may not all be
> totally clear.)
>
> Has anybody else successfully moved away from using params.pp and default
> values, and if so, what did you do and how did it go? If not, what made you
> go back?
>
> The only answer I can come up with is to stop using class parameters,
> change to hiera functions, and put all my data defaults in common.yaml.
>
> The background:
>
> I've had a couple of odd (lab) situations where much troubleshooting was
> occasioned by how I misspelled a key name in hiera and thus configuration
> data was pulled from a default value (either params.pp or the parameter
> default value). If there was no default value I would simply have gotten an
> error about the lookup failure and fixed that quickly.
>
> In a related matter, sometimes I need a piece of configuration data from
> one module to appear in another module. Faked-up example, my SuperDaemon
> configuration data has to be used by monit to supervise all the worker
> daemons and by logrotate to rotate their individual log files. Some things
> are data bindings, some are hiera()/hiera_array()/hiera_hash() on a case by
> case basis, and it's messy.
>
> In another related matter, explaining the combination of puppet
> inheritance from params.pp, default values, hiera, and hiera functions
> makes people's eyes glaze over. It would be easier to point people at hiera
> and say "source of data, learn these three functions".
>
> Things are mostly fine, I may just be wanting to tweak things, but it
> strikes me there's a way to do all this with much less effort.
>
> --
> 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/20140529175818.GA4308%40iniquitous.heresiarch.ca
> .
> 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/CALKwpEw0SPUjxYv1v2HAruacEP1XKUyvUn3dnhaE1No65ix9mQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet agent unable to pull files with puppetmaster setup in httpd with passenger

2014-05-30 Thread Brian Wilkins

I have my puppetmaster setup with httpd and mod_passenger. My agents can 
successfully pull manifests, but they are unable to pull files. As far as I 
can tell, I do not have any rewrite rules setup in my puppetmaster.conf 
(see below). In my httpd access log, I see that the agent tries to request 
the following:

GET /production/file_content/modules/company/logstash/banner? HTTP/1.1" 404 
69 "-" "-"

But that fails with "Could not find file_content 
modules/company/logstash/banner"

What should be different in my puppetmaster.conf? This is from the 
puppetlabs documentation also:

# RHEL/CentOS:
# And the passenger performance tuning settings:
PassengerHighPerformance On
PassengerUseGlobalQueue On
# Set this to about 1.5 times the number of CPU cores in your master:
PassengerMaxPoolSize 6
# Recycle master processes after they service 1000 requests
PassengerMaxRequests 1000
# Stop processes if they sit idle for 10 minutes
PassengerPoolIdleTime 600
PassengerTempDir /var/run/passenger

Listen 8140

SSLEngine On

# Only allow high security cryptography. Alter if needed for 
compatibility.
SSLProtocol All -SSLv2
SSLCipherSuite  HIGH:!ADH:RC4+RSA:-MEDIUM:-LOW:-EXP
SSLCertificateFile  /var/lib/puppet/ssl/certs/puppetmasterhost.pem
SSLCertificateKeyFile   
/var/lib/puppet/ssl/private_keys/puppetmasterhost.pem
SSLCertificateChainFile /var/lib/puppet/ssl/ca/ca_crt.pem
SSLCACertificateFile/var/lib/puppet/ssl/ca/ca_crt.pem
SSLCARevocationFile /var/lib/puppet/ssl/ca/ca_crl.pem
SSLVerifyClient optional
SSLVerifyDepth  1
SSLOptions  +StdEnvVars +ExportCertData

# These request headers are used to pass the client certificate
# authentication information on to the puppet master process
RequestHeader set X-SSL-Subject %{SSL_CLIENT_S_DN}e
RequestHeader set X-Client-DN %{SSL_CLIENT_S_DN}e
RequestHeader set X-Client-Verify %{SSL_CLIENT_VERIFY}e

RackAutoDetect On
DocumentRoot /usr/share/puppet/rack/puppetmasterd/public/

Options None
AllowOverride None
Order Allow,Deny
Allow from All



-- 
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/a41e1d79-c17d-4f60-8725-9ba8ae9c0409%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Using Hiera to Populate Defined Type in Puppet 3.6

Solved it using this tip.. it's odd but it works: 
http://serverfault.com/a/538877/26514

shipper.pp

class profiles::logstash::shipper() {

  $shipper_array = hiera_array('profiles::logstash::config_array')

  define hash_extract() {
$shipper_hash = hiera_hash('profiles::logstash::config_settings')
$shipper_config = $shipper_hash[$name]

profiles::logstash::config {'shipper':
   content => $shipper_config['content'],
   order   => $shipper_config['order'],
}
notice($shipper_config['content'])
notice($shipper_config['order'])
  }

  hash_extract{$shipper_array:}

  class { 'logstash':
ensure  => 'present',
version => '1.4.1-1_bd507eb',
status  => 'enabled',
  }
  include logstash
}


And in my hostname.yaml:

classes:
  - os::repo
  - profiles::logstash::shipper

profiles::logstash::config_array:
  - inputfile

profiles::logstash::config_settings:
  inputfile:
content: 'this is a test'
order: '10'


On Thursday, May 29, 2014 2:37:31 PM UTC-4, Brian Wilkins wrote:
>
> Yep!
>
> $ sudo hiera --debug profiles::logstash::config_settings ::fqdn=hostname
>
> DEBUG: Thu May 29 14:24:29 -0400 2014: Hiera YAML backend starting
> DEBUG: Thu May 29 14:24:29 -0400 2014: Looking up 
> profiles::logstash::config_settings in YAML backend
> DEBUG: Thu May 29 14:24:29 -0400 2014: Looking for data source 
> node/hostname
> DEBUG: Thu May 29 14:24:29 -0400 2014: Found 
> profiles::logstash::config_settings in node/hostname
> {"input_file"=>{"content"=>"this is a test", "order"=>"10"}}
>
>
> On Thursday, May 29, 2014 2:12:32 PM UTC-4, Doug_F wrote:
>>
>> Does it show up properly if you lookup on the server?
>>
>>
>> On Thu, May 29, 2014 at 12:09 PM, Brian Wilkins wrote:
>>
>>> Hmm, that's not working either. Doesn't look like it is populating my 
>>> define now. Hmm
>>>
>>>
>>> On Thursday, May 29, 2014 1:56:43 PM UTC-4, Doug_F wrote:
>>>
>>>> I think I figured out what was wrong. Dynamic data bindings may be 
>>>> mapping the inputs to the profiles::logstash::config defined type. Also I 
>>>> was in error in modifying your hiera data. 
>>>>
>>>> Try this: 
>>>>
>>>> create_resources('profiles::logstash::config', hiera_hash('profiles::
>>>> logstash::config_settings'))
>>>>
>>>> In Hiera:
>>>> profiles::logstash::config_settings:
>>>>input_file:
>>>>  content: 'this is a test'
>>>>  order: '10'
>>>>
>>>> Add a notice line in your profiles::logstash::config type to:
>>>> notify("name is ${name}") 
>>>> notify("content is ${content}") 
>>>> notify("order is ${order}") 
>>>>
>>>>
>>>> On Thu, May 29, 2014 at 11:25 AM, Brian Wilkins wrote:
>>>>
>>>>> Same problem. It seems like I am close. If only it didn't put all the 
>>>>> data together as one string.
>>>>>
>>>>>
>>>>> On Thursday, May 29, 2014 1:17:07 PM UTC-4, Doug_F wrote:
>>>>>
>>>>>> Maybe try your hiera command right inside your create_resources. 
>>>>>>
>>>>>>
>>>>>> On Thu, May 29, 2014 at 11:13 AM, Brian Wilkins wrote:
>>>>>>
>>>>>>> On puppetmaster:
>>>>>>>
>>>>>>> $ sudo hiera --debug profiles::logstash::config ::fqdn=hostname
>>>>>>>
>>>>>>> DEBUG: Thu May 29 13:12:56 -0400 2014: Hiera YAML backend starting
>>>>>>> DEBUG: Thu May 29 13:12:56 -0400 2014: Looking up 
>>>>>>> profiles::logstash::config in YAML backend
>>>>>>> DEBUG: Thu May 29 13:12:56 -0400 2014: Looking for data source 
>>>>>>> node/hostname
>>>>>>> DEBUG: Thu May 29 13:12:56 -0400 2014: Found 
>>>>>>> profiles::logstash::config in node/hostname
>>>>>>> {"order"=>"10", "content"=>"this is a test"}
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thursday, May 29, 2014 1:11:20 PM UTC-4, Doug_F wrote:
>>>>>>>
>>>>>>>> If you use hiera on the server does it show

Re: [Puppet Users] Using Hiera to Populate Defined Type in Puppet 3.6

Yep!

$ sudo hiera --debug profiles::logstash::config_settings ::fqdn=hostname

DEBUG: Thu May 29 14:24:29 -0400 2014: Hiera YAML backend starting
DEBUG: Thu May 29 14:24:29 -0400 2014: Looking up 
profiles::logstash::config_settings in YAML backend
DEBUG: Thu May 29 14:24:29 -0400 2014: Looking for data source node/hostname
DEBUG: Thu May 29 14:24:29 -0400 2014: Found 
profiles::logstash::config_settings in node/hostname
{"input_file"=>{"content"=>"this is a test", "order"=>"10"}}


On Thursday, May 29, 2014 2:12:32 PM UTC-4, Doug_F wrote:
>
> Does it show up properly if you lookup on the server?
>
>
> On Thu, May 29, 2014 at 12:09 PM, Brian Wilkins 
> 
> > wrote:
>
>> Hmm, that's not working either. Doesn't look like it is populating my 
>> define now. Hmm
>>
>>
>> On Thursday, May 29, 2014 1:56:43 PM UTC-4, Doug_F wrote:
>>
>>> I think I figured out what was wrong. Dynamic data bindings may be 
>>> mapping the inputs to the profiles::logstash::config defined type. Also I 
>>> was in error in modifying your hiera data. 
>>>
>>> Try this: 
>>>
>>> create_resources('profiles::logstash::config', hiera_hash('profiles::
>>> logstash::config_settings'))
>>>
>>> In Hiera:
>>> profiles::logstash::config_settings:
>>>input_file:
>>>  content: 'this is a test'
>>>  order: '10'
>>>
>>> Add a notice line in your profiles::logstash::config type to:
>>> notify("name is ${name}") 
>>> notify("content is ${content}") 
>>> notify("order is ${order}") 
>>>
>>>
>>> On Thu, May 29, 2014 at 11:25 AM, Brian Wilkins wrote:
>>>
>>>> Same problem. It seems like I am close. If only it didn't put all the 
>>>> data together as one string.
>>>>
>>>>
>>>> On Thursday, May 29, 2014 1:17:07 PM UTC-4, Doug_F wrote:
>>>>
>>>>> Maybe try your hiera command right inside your create_resources. 
>>>>>
>>>>>
>>>>> On Thu, May 29, 2014 at 11:13 AM, Brian Wilkins wrote:
>>>>>
>>>>>> On puppetmaster:
>>>>>>
>>>>>> $ sudo hiera --debug profiles::logstash::config ::fqdn=hostname
>>>>>>
>>>>>> DEBUG: Thu May 29 13:12:56 -0400 2014: Hiera YAML backend starting
>>>>>> DEBUG: Thu May 29 13:12:56 -0400 2014: Looking up 
>>>>>> profiles::logstash::config in YAML backend
>>>>>> DEBUG: Thu May 29 13:12:56 -0400 2014: Looking for data source 
>>>>>> node/hostname
>>>>>> DEBUG: Thu May 29 13:12:56 -0400 2014: Found 
>>>>>> profiles::logstash::config in node/hostname
>>>>>> {"order"=>"10", "content"=>"this is a test"}
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thursday, May 29, 2014 1:11:20 PM UTC-4, Doug_F wrote:
>>>>>>
>>>>>>> If you use hiera on the server does it show up as a hash? 
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, May 29, 2014 at 11:08 AM, Brian Wilkins 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Same problem. I see it concatenated in the notice.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thursday, May 29, 2014 1:05:39 PM UTC-4, Doug_F wrote:
>>>>>>>>
>>>>>>>>> Just a thought try changing 
>>>>>>>>>   $shipper_config = hiera('profiles::logstash::config', {}) => 
>>>>>>>>> $shipper_config = hiera_hash('profiles::logstash::config', {})
>>>>>>>>>  
>>>>>>>>>
>>>>>>>>> On Thu, May 29, 2014 at 11:01 AM, Brian Wilkins >>>>>>>> > wrote:
>>>>>>>>>
>>>>>>>>>>  It prints out:
>>>>>>>>>>
>>>>>>>>>> order10contentthis is a test
>>>>>>>>>>
>>>>>>>>>> It concatenated it all together.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>&g

Re: [Puppet Users] Using Hiera to Populate Defined Type in Puppet 3.6

Hmm, that's not working either. Doesn't look like it is populating my 
define now. Hmm

On Thursday, May 29, 2014 1:56:43 PM UTC-4, Doug_F wrote:
>
> I think I figured out what was wrong. Dynamic data bindings may be mapping 
> the inputs to the profiles::logstash::config defined type. Also I was in 
> error in modifying your hiera data. 
>
> Try this: 
>
> create_resources('profiles::logstash::config', 
> hiera_hash('profiles::logstash::config_settings'))
>
> In Hiera:
> profiles::logstash::config_settings:
>input_file:
>  content: 'this is a test'
>  order: '10'
>
> Add a notice line in your profiles::logstash::config type to:
> notify("name is ${name}") 
> notify("content is ${content}") 
> notify("order is ${order}") 
>
>
> On Thu, May 29, 2014 at 11:25 AM, Brian Wilkins 
> 
> > wrote:
>
>> Same problem. It seems like I am close. If only it didn't put all the 
>> data together as one string.
>>
>>
>> On Thursday, May 29, 2014 1:17:07 PM UTC-4, Doug_F wrote:
>>
>>> Maybe try your hiera command right inside your create_resources. 
>>>
>>>
>>> On Thu, May 29, 2014 at 11:13 AM, Brian Wilkins wrote:
>>>
>>>> On puppetmaster:
>>>>
>>>> $ sudo hiera --debug profiles::logstash::config ::fqdn=hostname
>>>>
>>>> DEBUG: Thu May 29 13:12:56 -0400 2014: Hiera YAML backend starting
>>>> DEBUG: Thu May 29 13:12:56 -0400 2014: Looking up 
>>>> profiles::logstash::config in YAML backend
>>>> DEBUG: Thu May 29 13:12:56 -0400 2014: Looking for data source 
>>>> node/hostname
>>>> DEBUG: Thu May 29 13:12:56 -0400 2014: Found profiles::logstash::config 
>>>> in node/hostname
>>>> {"order"=>"10", "content"=>"this is a test"}
>>>>
>>>>
>>>>
>>>> On Thursday, May 29, 2014 1:11:20 PM UTC-4, Doug_F wrote:
>>>>
>>>>> If you use hiera on the server does it show up as a hash? 
>>>>>
>>>>>
>>>>>
>>>>> On Thu, May 29, 2014 at 11:08 AM, Brian Wilkins wrote:
>>>>>
>>>>>> Same problem. I see it concatenated in the notice.
>>>>>>
>>>>>>
>>>>>> On Thursday, May 29, 2014 1:05:39 PM UTC-4, Doug_F wrote:
>>>>>>
>>>>>>> Just a thought try changing 
>>>>>>>   $shipper_config = hiera('profiles::logstash::config', {}) => 
>>>>>>> $shipper_config = hiera_hash('profiles::logstash::config', {})
>>>>>>>  
>>>>>>>
>>>>>>> On Thu, May 29, 2014 at 11:01 AM, Brian Wilkins 
>>>>>>> wrote:
>>>>>>>
>>>>>>>>  It prints out:
>>>>>>>>
>>>>>>>> order10contentthis is a test
>>>>>>>>
>>>>>>>> It concatenated it all together.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thursday, May 29, 2014 12:59:09 PM UTC-4, Doug_F wrote:
>>>>>>>>
>>>>>>>>> Try setting your notice("${shipper_config}") before create 
>>>>>>>>> resources and see what it prints out. 
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, May 29, 2014 at 10:47 AM, Brian Wilkins >>>>>>>> > wrote:
>>>>>>>>>
>>>>>>>>>> Oh ok, makes sense. I did that and now I get "can't convert 
>>>>>>>>>> String into Hash at /etc/puppet/modules/profiles/m
>>>>>>>>>> anifests/logstash/shipper.pp:15"
>>>>>>>>>>
>>>>>>>>>> My shipper.pp
>>>>>>>>>>
>>>>>>>>>> class profiles::logstash::shipper() {
>>>>>>>>>>
>>>>>>>>>>   $shipper_config = hiera('profiles::logstash::config', {})
>>>>>>>>>>   create_resources('profiles::logstash::config', $shipper_config)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>   notice("${shipper_config[name]}"

Re: [Puppet Users] Using Hiera to Populate Defined Type in Puppet 3.6

Same problem. It seems like I am close. If only it didn't put all the data 
together as one string.

On Thursday, May 29, 2014 1:17:07 PM UTC-4, Doug_F wrote:
>
> Maybe try your hiera command right inside your create_resources. 
>
>
> On Thu, May 29, 2014 at 11:13 AM, Brian Wilkins 
> 
> > wrote:
>
>> On puppetmaster:
>>
>> $ sudo hiera --debug profiles::logstash::config ::fqdn=hostname
>>
>> DEBUG: Thu May 29 13:12:56 -0400 2014: Hiera YAML backend starting
>> DEBUG: Thu May 29 13:12:56 -0400 2014: Looking up 
>> profiles::logstash::config in YAML backend
>> DEBUG: Thu May 29 13:12:56 -0400 2014: Looking for data source 
>> node/hostname
>> DEBUG: Thu May 29 13:12:56 -0400 2014: Found profiles::logstash::config 
>> in node/hostname
>> {"order"=>"10", "content"=>"this is a test"}
>>
>>
>>
>> On Thursday, May 29, 2014 1:11:20 PM UTC-4, Doug_F wrote:
>>
>>> If you use hiera on the server does it show up as a hash? 
>>>
>>>
>>>
>>> On Thu, May 29, 2014 at 11:08 AM, Brian Wilkins wrote:
>>>
>>>> Same problem. I see it concatenated in the notice.
>>>>
>>>>
>>>> On Thursday, May 29, 2014 1:05:39 PM UTC-4, Doug_F wrote:
>>>>
>>>>> Just a thought try changing 
>>>>>   $shipper_config = hiera('profiles::logstash::config', {}) => 
>>>>> $shipper_config = hiera_hash('profiles::logstash::config', {})
>>>>>  
>>>>>
>>>>> On Thu, May 29, 2014 at 11:01 AM, Brian Wilkins wrote:
>>>>>
>>>>>>  It prints out:
>>>>>>
>>>>>> order10contentthis is a test
>>>>>>
>>>>>> It concatenated it all together.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thursday, May 29, 2014 12:59:09 PM UTC-4, Doug_F wrote:
>>>>>>
>>>>>>> Try setting your notice("${shipper_config}") before create resources 
>>>>>>> and see what it prints out. 
>>>>>>>
>>>>>>>
>>>>>>> On Thu, May 29, 2014 at 10:47 AM, Brian Wilkins 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Oh ok, makes sense. I did that and now I get "can't convert String 
>>>>>>>> into Hash at /etc/puppet/modules/profiles/m
>>>>>>>> anifests/logstash/shipper.pp:15"
>>>>>>>>
>>>>>>>> My shipper.pp
>>>>>>>>
>>>>>>>> class profiles::logstash::shipper() {
>>>>>>>>
>>>>>>>>   $shipper_config = hiera('profiles::logstash::config', {})
>>>>>>>>   create_resources('profiles::logstash::config', $shipper_config)
>>>>>>>>
>>>>>>>>
>>>>>>>>   notice("${shipper_config[name]}")
>>>>>>>>   class { 'logstash':
>>>>>>>> ensure  => 'present',
>>>>>>>> version => '1.4.1-1_bd507eb',
>>>>>>>> status  => 'enabled',
>>>>>>>>   }
>>>>>>>>
>>>>>>>>   profiles::logstash::config { 'shipper':
>>>>>>>>
>>>>>>>>content => $content,
>>>>>>>>order   => $order,
>>>>>>>>   }
>>>>>>>>
>>>>>>>>   include logstash
>>>>>>>> }
>>>>>>>>
>>>>>>>> Line 15 is the create_resources line.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thursday, May 29, 2014 12:42:15 PM UTC-4, Doug_F wrote:
>>>>>>>>
>>>>>>>>> profiles::logstash::config:
>>>>>>>>>input_file:
>>>>>>>>>  content: 'this is a test'
>>>>>>>>>  order: '10'
>>>>>>>>>
>>>>>>>>> Should probably be 
>>>>>>>>> profiles::logstash::config:
>>>>>>>>>content: 'this is a test'
>>>

Re: [Puppet Users] Using Hiera to Populate Defined Type in Puppet 3.6

On puppetmaster:

$ sudo hiera --debug profiles::logstash::config ::fqdn=hostname

DEBUG: Thu May 29 13:12:56 -0400 2014: Hiera YAML backend starting
DEBUG: Thu May 29 13:12:56 -0400 2014: Looking up 
profiles::logstash::config in YAML backend
DEBUG: Thu May 29 13:12:56 -0400 2014: Looking for data source node/hostname
DEBUG: Thu May 29 13:12:56 -0400 2014: Found profiles::logstash::config in 
node/hostname
{"order"=>"10", "content"=>"this is a test"}


On Thursday, May 29, 2014 1:11:20 PM UTC-4, Doug_F wrote:
>
> If you use hiera on the server does it show up as a hash? 
>
>
>
> On Thu, May 29, 2014 at 11:08 AM, Brian Wilkins 
> 
> > wrote:
>
>> Same problem. I see it concatenated in the notice.
>>
>>
>> On Thursday, May 29, 2014 1:05:39 PM UTC-4, Doug_F wrote:
>>
>>> Just a thought try changing 
>>>   $shipper_config = hiera('profiles::logstash::config', {}) => 
>>> $shipper_config = hiera_hash('profiles::logstash::config', {})
>>>  
>>>
>>> On Thu, May 29, 2014 at 11:01 AM, Brian Wilkins wrote:
>>>
>>>>  It prints out:
>>>>
>>>> order10contentthis is a test
>>>>
>>>> It concatenated it all together.
>>>>
>>>>
>>>>
>>>> On Thursday, May 29, 2014 12:59:09 PM UTC-4, Doug_F wrote:
>>>>
>>>>> Try setting your notice("${shipper_config}") before create resources 
>>>>> and see what it prints out. 
>>>>>
>>>>>
>>>>> On Thu, May 29, 2014 at 10:47 AM, Brian Wilkins wrote:
>>>>>
>>>>>> Oh ok, makes sense. I did that and now I get "can't convert String 
>>>>>> into Hash at /etc/puppet/modules/profiles/m
>>>>>> anifests/logstash/shipper.pp:15"
>>>>>>
>>>>>> My shipper.pp
>>>>>>
>>>>>> class profiles::logstash::shipper() {
>>>>>>
>>>>>>   $shipper_config = hiera('profiles::logstash::config', {})
>>>>>>   create_resources('profiles::logstash::config', $shipper_config)
>>>>>>
>>>>>>
>>>>>>   notice("${shipper_config[name]}")
>>>>>>   class { 'logstash':
>>>>>> ensure  => 'present',
>>>>>> version => '1.4.1-1_bd507eb',
>>>>>> status  => 'enabled',
>>>>>>   }
>>>>>>
>>>>>>   profiles::logstash::config { 'shipper':
>>>>>>
>>>>>>content => $content,
>>>>>>order   => $order,
>>>>>>   }
>>>>>>
>>>>>>   include logstash
>>>>>> }
>>>>>>
>>>>>> Line 15 is the create_resources line.
>>>>>>
>>>>>>
>>>>>> On Thursday, May 29, 2014 12:42:15 PM UTC-4, Doug_F wrote:
>>>>>>
>>>>>>> profiles::logstash::config:
>>>>>>>input_file:
>>>>>>>  content: 'this is a test'
>>>>>>>  order: '10'
>>>>>>>
>>>>>>> Should probably be 
>>>>>>> profiles::logstash::config:
>>>>>>>content: 'this is a test'
>>>>>>>order: '10'
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, May 29, 2014 at 10:27 AM, Brian Wilkins 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I am trying to use hiera to populate a defined type to feed the 
>>>>>>>> puppet-logstash module. So far, I have been unable to send the data 
>>>>>>>> from my 
>>>>>>>> hiera file to my defined type. I have tested my defined type and it is 
>>>>>>>> working, I just can't seem to populate the variables. It tells me that 
>>>>>>>> $content and $order are not set.
>>>>>>>>
>>>>>>>> /etc/puppet/modules/profiles/manifests/logstash/shipper.pp:
>>>>>>>>
>>>>>>>> class profiles::logstash::shipper() {
>>>>>>>>
>>>>>>>>   $shipper_config = hiera('

Re: [Puppet Users] Using Hiera to Populate Defined Type in Puppet 3.6

Same problem. I see it concatenated in the notice.

On Thursday, May 29, 2014 1:05:39 PM UTC-4, Doug_F wrote:
>
> Just a thought try changing 
>   $shipper_config = hiera('profiles::logstash::config', {}) => 
> $shipper_config = hiera_hash('profiles::logstash::config', {})
>
>
> On Thu, May 29, 2014 at 11:01 AM, Brian Wilkins 
> 
> > wrote:
>
>> It prints out:
>>
>> order10contentthis is a test
>>
>> It concatenated it all together.
>>
>>
>>
>> On Thursday, May 29, 2014 12:59:09 PM UTC-4, Doug_F wrote:
>>
>>> Try setting your notice("${shipper_config}") before create resources and 
>>> see what it prints out. 
>>>
>>>
>>> On Thu, May 29, 2014 at 10:47 AM, Brian Wilkins wrote:
>>>
>>>> Oh ok, makes sense. I did that and now I get "can't convert String into 
>>>> Hash at /etc/puppet/modules/profiles/manifests/logstash/shipper.pp:15"
>>>>
>>>> My shipper.pp
>>>>
>>>> class profiles::logstash::shipper() {
>>>>
>>>>   $shipper_config = hiera('profiles::logstash::config', {})
>>>>   create_resources('profiles::logstash::config', $shipper_config)
>>>>
>>>>
>>>>   notice("${shipper_config[name]}")
>>>>   class { 'logstash':
>>>> ensure  => 'present',
>>>> version => '1.4.1-1_bd507eb',
>>>> status  => 'enabled',
>>>>   }
>>>>
>>>>   profiles::logstash::config { 'shipper':
>>>>
>>>>content => $content,
>>>>order   => $order,
>>>>   }
>>>>
>>>>   include logstash
>>>> }
>>>>
>>>> Line 15 is the create_resources line.
>>>>
>>>>
>>>> On Thursday, May 29, 2014 12:42:15 PM UTC-4, Doug_F wrote:
>>>>
>>>>> profiles::logstash::config:
>>>>>input_file:
>>>>>  content: 'this is a test'
>>>>>  order: '10'
>>>>>
>>>>> Should probably be 
>>>>> profiles::logstash::config:
>>>>>content: 'this is a test'
>>>>>order: '10'
>>>>>
>>>>>
>>>>>
>>>>> On Thu, May 29, 2014 at 10:27 AM, Brian Wilkins wrote:
>>>>>
>>>>>> I am trying to use hiera to populate a defined type to feed the 
>>>>>> puppet-logstash module. So far, I have been unable to send the data from 
>>>>>> my 
>>>>>> hiera file to my defined type. I have tested my defined type and it is 
>>>>>> working, I just can't seem to populate the variables. It tells me that 
>>>>>> $content and $order are not set.
>>>>>>
>>>>>> /etc/puppet/modules/profiles/manifests/logstash/shipper.pp:
>>>>>>
>>>>>> class profiles::logstash::shipper() {
>>>>>>
>>>>>>   $shipper_config = hiera('profiles::logstash::config')
>>>>>>   create_resources('config', $shipper_config)
>>>>>>
>>>>>>   notice("${shipper_config[name]}")
>>>>>>   class { 'logstash':
>>>>>> ensure  => 'present',
>>>>>> version => '1.4.1-1_bd507eb',
>>>>>> status  => 'enabled',
>>>>>>   }
>>>>>>
>>>>>>   profiles::logstash::config { $name:
>>>>>>content => $content,
>>>>>>order   => $order,
>>>>>>   }
>>>>>>
>>>>>>   include logstash
>>>>>> }
>>>>>>
>>>>>> /etc/puppet/modules/profiles/manifests/logstash/config.pp:
>>>>>>
>>>>>> define profiles::logstash::config(
>>>>>>   $content = undef,
>>>>>>   $order = undef,
>>>>>> ) {
>>>>>>   logstash::configfile { $name:
>>>>>> content => $content,
>>>>>> order   => $order
>>>>>>   }
>>>>>> }
>>>>>>
>>>>>> /etc/puppet/data/node/els4172.els.dev.yaml:
>>>>&

Re: [Puppet Users] Using Hiera to Populate Defined Type in Puppet 3.6

It prints out:

order10contentthis is a test

It concatenated it all together.


On Thursday, May 29, 2014 12:59:09 PM UTC-4, Doug_F wrote:
>
> Try setting your notice("${shipper_config}") before create resources and 
> see what it prints out. 
>
>
> On Thu, May 29, 2014 at 10:47 AM, Brian Wilkins 
> 
> > wrote:
>
>> Oh ok, makes sense. I did that and now I get "can't convert String into 
>> Hash at /etc/puppet/modules/profiles/manifests/logstash/shipper.pp:15"
>>
>> My shipper.pp
>>
>> class profiles::logstash::shipper() {
>>
>>   $shipper_config = hiera('profiles::logstash::config', {})
>>   create_resources('profiles::logstash::config', $shipper_config)
>>
>>
>>   notice("${shipper_config[name]}")
>>   class { 'logstash':
>> ensure  => 'present',
>> version => '1.4.1-1_bd507eb',
>> status  => 'enabled',
>>   }
>>
>>   profiles::logstash::config { 'shipper':
>>
>>content => $content,
>>order   => $order,
>>   }
>>
>>   include logstash
>> }
>>
>> Line 15 is the create_resources line.
>>
>>
>> On Thursday, May 29, 2014 12:42:15 PM UTC-4, Doug_F wrote:
>>
>>> profiles::logstash::config:
>>>input_file:
>>>  content: 'this is a test'
>>>  order: '10'
>>>
>>> Should probably be 
>>> profiles::logstash::config:
>>>content: 'this is a test'
>>>order: '10'
>>>
>>>
>>>
>>> On Thu, May 29, 2014 at 10:27 AM, Brian Wilkins wrote:
>>>
>>>> I am trying to use hiera to populate a defined type to feed the 
>>>> puppet-logstash module. So far, I have been unable to send the data from 
>>>> my 
>>>> hiera file to my defined type. I have tested my defined type and it is 
>>>> working, I just can't seem to populate the variables. It tells me that 
>>>> $content and $order are not set.
>>>>
>>>> /etc/puppet/modules/profiles/manifests/logstash/shipper.pp:
>>>>
>>>> class profiles::logstash::shipper() {
>>>>
>>>>   $shipper_config = hiera('profiles::logstash::config')
>>>>   create_resources('config', $shipper_config)
>>>>
>>>>   notice("${shipper_config[name]}")
>>>>   class { 'logstash':
>>>> ensure  => 'present',
>>>> version => '1.4.1-1_bd507eb',
>>>> status  => 'enabled',
>>>>   }
>>>>
>>>>   profiles::logstash::config { $name:
>>>>content => $content,
>>>>order   => $order,
>>>>   }
>>>>
>>>>   include logstash
>>>> }
>>>>
>>>> /etc/puppet/modules/profiles/manifests/logstash/config.pp:
>>>>
>>>> define profiles::logstash::config(
>>>>   $content = undef,
>>>>   $order = undef,
>>>> ) {
>>>>   logstash::configfile { $name:
>>>> content => $content,
>>>> order   => $order
>>>>   }
>>>> }
>>>>
>>>> /etc/puppet/data/node/els4172.els.dev.yaml:
>>>>
>>>> classes:
>>>>   - os::repo
>>>>   - profiles::logstash::shipper
>>>>
>>>> profiles::logstash::config:
>>>>input_file:
>>>>  content: 'this is a test'
>>>>  order: '10'
>>>>
>>>>
>>>> My notice is not called, it does not display a thing. Did I use 
>>>> create_resources correctly?
>>>>
>>>>
>>>>
>>>>  -- 
>>>> 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/c162ac6e-257c-4c42-a856-0b2f99dbd7f3%
>>>> 40googlegroups.com<https://groups.google.com/d/msgid/puppet-users/c162ac6e-257c-4c42-a856-0b2f99dbd7f3%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/305d7707-68ca-4814-940e-ef984fcb2c04%40googlegroups.com<https://groups.google.com/d/msgid/puppet-users/305d7707-68ca-4814-940e-ef984fcb2c04%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> 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/09cd7ee2-7231-499f-a05e-e4430389956a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Using Hiera to Populate Defined Type in Puppet 3.6

Oh ok, makes sense. I did that and now I get "can't convert String into 
Hash at /etc/puppet/modules/profiles/manifests/logstash/shipper.pp:15"

My shipper.pp

class profiles::logstash::shipper() {

  $shipper_config = hiera('profiles::logstash::config', {})
  create_resources('profiles::logstash::config', $shipper_config)

  notice("${shipper_config[name]}")
  class { 'logstash':
ensure  => 'present',
version => '1.4.1-1_bd507eb',
status  => 'enabled',
  }

  profiles::logstash::config { 'shipper':
   content => $content,
   order   => $order,
  }

  include logstash
}

Line 15 is the create_resources line.

On Thursday, May 29, 2014 12:42:15 PM UTC-4, Doug_F wrote:
>
> profiles::logstash::config:
>input_file:
>  content: 'this is a test'
>  order: '10'
>
> Should probably be 
> profiles::logstash::config:
>content: 'this is a test'
>order: '10'
>
>
>
> On Thu, May 29, 2014 at 10:27 AM, Brian Wilkins 
> 
> > wrote:
>
>> I am trying to use hiera to populate a defined type to feed the 
>> puppet-logstash module. So far, I have been unable to send the data from my 
>> hiera file to my defined type. I have tested my defined type and it is 
>> working, I just can't seem to populate the variables. It tells me that 
>> $content and $order are not set.
>>
>> /etc/puppet/modules/profiles/manifests/logstash/shipper.pp:
>>
>> class profiles::logstash::shipper() {
>>
>>   $shipper_config = hiera('profiles::logstash::config')
>>   create_resources('config', $shipper_config)
>>
>>   notice("${shipper_config[name]}")
>>   class { 'logstash':
>> ensure  => 'present',
>> version => '1.4.1-1_bd507eb',
>> status  => 'enabled',
>>   }
>>
>>   profiles::logstash::config { $name:
>>content => $content,
>>order   => $order,
>>   }
>>
>>   include logstash
>> }
>>
>> /etc/puppet/modules/profiles/manifests/logstash/config.pp:
>>
>> define profiles::logstash::config(
>>   $content = undef,
>>   $order = undef,
>> ) {
>>   logstash::configfile { $name:
>> content => $content,
>> order   => $order
>>   }
>> }
>>
>> /etc/puppet/data/node/els4172.els.dev.yaml:
>>
>> classes:
>>   - os::repo
>>   - profiles::logstash::shipper
>>
>> profiles::logstash::config:
>>input_file:
>>  content: 'this is a test'
>>  order: '10'
>>
>>
>> My notice is not called, it does not display a thing. Did I use 
>> create_resources correctly?
>>
>>
>>
>>  -- 
>> 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/c162ac6e-257c-4c42-a856-0b2f99dbd7f3%40googlegroups.com<https://groups.google.com/d/msgid/puppet-users/c162ac6e-257c-4c42-a856-0b2f99dbd7f3%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> 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/305d7707-68ca-4814-940e-ef984fcb2c04%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Using Hiera to Populate Defined Type in Puppet 3.6