[Puppet Users] Re: Load balancing Puppet Server

[Stefan Wiederoder]

Hello Joao,

sorry - no help, but I'm also looking for a puppet server 2.x howto about 
centralizing the CA.
I'm currently using mod_proxy/mod_passenger with an F5 loadbalancer in 
front of two servers.

I'd be nice if puppetlabs would provide such an howto, it´d help/speedup 
puppetserver adoption.

bye
,
Stefan

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

[Puppet Users] Registering a puppet agent node with alternate short hostname or alias

[Anil Aix]

We were trying to register gcloud instances to puppet master, but the 
instance names are very long with uc1f-coster-xxx02.c.xxxa--xx0.internal
Is it possible to register these nodes with a short hostname or an 
alias...?,

I tried adding below line in /etc/puppet/puppet.cong of client.
dns_alt_names = costerinf2
And ran
puppet cert sign -all  --allow-dns-alt-names on master 
+ "uc1f-cstor-inf02.c.zeta-bonsai-770.internal" (SHA256) xxx  
S:costerinf2", "DNS:uc1f-coster-xxx02.c.xxxa--xx0.internal")
 

But it still registers with the long name, Even in Foreman interface it 
shows long name, is there a way to register and show short names(the alias 
we configured) in puppet.
Please help.

-- 
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/56fdc977-e4f3-4bdd-a40e-f880416dfe1c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Registering a puppet agent node with alternate short hostname or alias

[Rilindo Foster]

By default, the certname is the fully qualified domain. You can change it via 
the node_name_value or node_name_fact; however, you need to have a very good 
reason to change the settings before you move forward with it.

https://docs.puppetlabs.com/references/latest/configuration.html#certname

 - Rilindo

> On May 13, 2015, at 3:22 AM, Anil Aix  wrote:
> 
> We were trying to register gcloud instances to puppet master, but the 
> instance names are very long with uc1f-coster-xxx02.c.xxxa--xx0.internal
> Is it possible to register these nodes with a short hostname or an alias...?,
> 
> I tried adding below line in /etc/puppet/puppet.cong of client.
> dns_alt_names = costerinf2
> And ran
> puppet cert sign -all  --allow-dns-alt-names on master 
> + "uc1f-cstor-inf02.c.zeta-bonsai-770.internal" (SHA256) xxx  S:costerinf2", 
> "DNS:uc1f-coster-xxx02.c.xxxa--xx0.internal")
>  
> 
> But it still registers with the long name, Even in Foreman interface it shows 
> long name, is there a way to register and show short names(the alias we 
> configured) in puppet.
> Please help.
> -- 
> 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/56fdc977-e4f3-4bdd-a40e-f880416dfe1c%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/19E4CA7B-A72A-4429-9B24-6EC87D99B3CD%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] client certificate issue

[Felix Frank]

Hi,

there really is no way for the master to tell directly.

The best approach is to enable storing of reports (e.g. in PuppetDB) so
that you can monitor agent operation. Afflicted agents do not run and do
not report. Tools like Puppet Explorer can indicate this to you very
directly.

HTH,
Felix

On 05/07/2015 04:17 PM, Karel wrote:
> Hi,
> 
> I have a problem with a certificate on some servers.
> 
> C:\Program Files\Puppet Labs\Puppet Enterprise\bin>puppet agent -t
> Error: Could not request certificate: The certificate retrieved from the
> master does not match the agent's private key.
> Certificate fingerprint: 93:85:FC:CF:32:19:43:33:75:43:B0:43:D3:60:4C:69
> To fix this, remove the certificate from both the master and the agent
> and then start a puppet run, which will automatically regenerate a
> certficate.
> On the master:
> puppet cert clean ..
> 
> I would need to know if it is possible to track this issue from Puppet
> Master side. Is this communication logged somewhere to log files on
> Puppet Master servers?
> I need to know a list of clients that have the problem with the cert.
> 
> Thanks,
> Karel

-- 
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/55534887.909%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Preserving single quotes

[Felix Frank]

On 05/05/2015 08:25 PM, Marcos Renato wrote:
> Hi
> 
> how to add this command line (alias ls='ls --color=auto') to a file 
> preserving single quotes?
> 
> Thanks,
> 
> Marcos

Are you trying to pass this through the content property?

-- 
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/55534ABF.7080104%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Hiera single key/value lookup and create_resources for augeas

[Felix Frank]

Well you will have to devise a defined type that takes the variable name
as the resource title, and the value as an argument. Data structure has
to be

my_variables:
   my_project1:
 var1:
   value: value1
 var2:
   value: value2

Then the my_project1 hash is eligible for use with create_resources.

With Puppet 4 you can use iteration over the hash instead, so that no
data restructuring is necessary. If you are on a recent version of
Puppet 3, you can do the same thing using the parser=future setting.

HTH,
Felix

On 05/04/2015 02:56 PM, julien.a...@dayotech.fr wrote:
> Hi
> 
> I want to manage an INI file with an undefined number of key/value records.
> I wish to add each var/value recording in a single file (manage by
> augeas) for each project, but I don't know how to make calls or pass the
> data to create_resources.
> Don't want to have a hash for each var/value, too boring to manage.
> 
> So here's the Hiera file I write :
> ---
> my_variables:
>   my_project1:
> var1:value1
> var2:value2
>   my_project2:
> var1:value1
> var2:value2
> 
> 
> Any idea ?
> 
> 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/55534BAD.8000802%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Load balancing Puppet Server

[Christopher Wood]

I presume one of the hosts is still the puppetmaster, I took the tack of using 
a separate virtual server and pool for the CA. All hosts get catalog requests 
but all hosts are configured to use the CA virtual server for CA work.

On Wed, May 13, 2015 at 02:28:26AM -0700, Stefan Wiederoder wrote:
>Hello Joao,
> 
>sorry - no help, but I'm also looking for a puppet server 2.x howto about
>centralizing the CA.
>I'm currently using mod_proxy/mod_passenger with an F5 loadbalancer in
>front of two servers.
> 
>I'd be nice if puppetlabs would provide such an howto, it´d help/speedup
>puppetserver adoption.
> 
>bye
>,
>Stefan
> 
>--
>You received this message because you are subscribed to the Google Groups
>"Puppet Users" group.
>To unsubscribe from this group and stop receiving emails from it, send an
>email to [1]puppet-users+unsubscr...@googlegroups.com.
>To view this discussion on the web visit
>
> [2]https://groups.google.com/d/msgid/puppet-users/ab35abb4-8ede-4376-9629-9a0db83bce5f%40googlegroups.com.
>For more options, visit [3]https://groups.google.com/d/optout.
> 
> References
> 
>Visible links
>1. mailto:puppet-users+unsubscr...@googlegroups.com
>2. 
> https://groups.google.com/d/msgid/puppet-users/ab35abb4-8ede-4376-9629-9a0db83bce5f%40googlegroups.com?utm_medium=email&utm_source=footer
>3. 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/20150513133327.GA2988%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet Environments change after upgrading to 3.7.5

[Jim Miller]

Done anyone have any thoughts on this?



On Friday, May 8, 2015 at 2:23:27 PM UTC-5, Jim Miller wrote:
>
> Hi all,
>
> Just upgraded from 3.4.something to 3.7.5 and it seems how we were doing 
> environments is depreciated.  I've followed a couple of docs* for how to do 
> this but seem to be missing something. Nodes can't seem to find modules.  
> For now it's not a big deal because it's just a warning but I'd like to 
> address the issue.
>
> *http://docs.puppetlabs.com/puppet/latest/reference/environments.html 
> (and linked docs)
>
> Here's the old config values in /etc/puppet/puppet.conf for environments:
>
> [main]
> 
> 
> modulepath = /etc/puppet/modules
> ...
> ...
> ...
> environment = production
> confdir = /etc/puppet
>
> [production]
> manifest = $confdir/manifests/site.pp
> modulepath = 
> $confdir/environments/production/modules:$confdir/environments/test/site/modules
>
> [test]
> manifest = $confdir/manifests/non-prod_site.pp
> modulepath = 
> $confdir/environments/test/modules:$confdir/environments/test/site/modules
>
> [development]
> manifest = $confdir/manifests/non-prod_site.pp
> modulepath = 
> $confdir/environments/dev/modules:$confdir/environments/dev/site/modules
>
>
>
> PROPOSED:
> [main]
> 
> 
> # modulepath = /etc/puppet/modules
> environmentpath = $confdir/environments
> default_manifest = /etc/puppet/manifests/site.pp
> ...
> ...
> ...
> # environment = production
> confdir = /etc/puppet
>
> # [production]
> # manifest = $confdir/manifests/site.pp
> # modulepath = 
> $confdir/environments/production/modules:$confdir/environments/test/site/modules
>
> # [test]
> #manifest = $confdir/manifests/non-prod_site.pp
> #modulepath = 
> $confdir/environments/test/modules:$confdir/environments/test/site/modules
>
> # [development]
> # manifest = $confdir/manifests/non-prod_site.pp
> # modulepath = 
> $confdir/environments/dev/modules:$confdir/environments/dev/site/modules
>
>
> Environments.conf
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Environments.conf for production:
> manifest = $confdir/manifests/site.pp
> modulepath = 
> $confdir/environments/production/modules:$confdir/puppet/environments/production/site
>
> Environments.conf for testing:
> manifest = $confdir/manifests/non-prod_site.pp
> modulepath = 
> $confdir/environments/test/modules:$confdir/environments/test/site/modules
>
> Environments.conf for dev:
> manifest = $confdir/manifests/non-prod_site.pp
> modulepath = 
> $confdir/environments/dev/modules:$confdir/environments/dev/site/modules
>
>
> Nodes .pp settings for each environment
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> $puppet_env = "production"
>
> $puppet_env = "test"
>
> $puppet_env = "development"
>
>
>
>

-- 
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/b39c2885-ffb7-4c5c-acce-fa70e5b3afee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet Dashboard on Centos 7

[Gabriele Angeli]

Hi guys,

I tried to install puppet dashboard on Centos 7. 

I installed  the right repository for Centos 7 (puppetlabs.repo) but when I 
launch the command "yum install puppet-dashboard" the result is the 
following:


*No package puppet-dashboard available.*
*Error: Nothing to do*

Someone can help me?

Thanks in advance

-- 
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/b1b9c469-32cb-499a-94b1-8cd4efe0048c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Anyone really using Postgres for a Hiera backend?

[leam hall]

Just wondering. I found some options but don't see any under current
development.

Leam


-- 
Mind on a Mission 

-- 
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/CACv9p5p5La7KacvTn1RG-V-E30K77Zt873SBR8_7s%2BbvV6Oy8A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Dashboard on Centos 7

[Ramin K]

On 5/13/15 9:16 AM, Gabriele Angeli wrote:

Hi guys,

I tried to install puppet dashboard on Centos 7.

I installed  the right repository for Centos 7 (puppetlabs.repo) but
when I launch the command "yum install puppet-dashboard" the result is
the following:


*No package puppet-dashboard available.*
*Error: Nothing to do*



puppet-dashboard only works on systems that have Ruby 1.8.7. Centos 
shops 2.0. You can use the src files, RVM, Passenger4, gem install into 
RVM ruby 1.8, etc etc which will work, but requires you to know how all 
those technologies fit together. If you're dead set on using the 
dashboard that has been EOL'ed since 2012, you can use the community 
updated edition which should work with 2.0.


https://github.com/sodabrew/puppet-dashboard/

Other dashboard you might consider are http://theforeman.org/ and 
https://github.com/puppet-community/puppetboard


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/55538842.6010406%40badapple.net.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet Dashboard on Centos 7

[Ramin K]

On 5/13/15 10:22 AM, Ramin K wrote:

Centos shops 2.0


argh. Centos 7 ships 2.0

--
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/5553888D.30408%40badapple.net.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet Environments change after upgrading to 3.7.5

[ess]

We are using PE 3.7.2 with r10k, so I don't know how specifically useful 
this will be, but PE requires the use of basemodulepath.

https://docs.puppetlabs.com/puppet/latest/reference/config_file_environment.html

puppet.conf on master:
[main]
basemodulepath = 
/etc/puppetlabs/puppet/modules:/opt/puppet/share/puppet/modules
environmentpath = /etc/puppetlabs/puppet/environments

In /etc/puppetlabs/puppet/environment/
> Done anyone have any thoughts on this?
>
>
>
> On Friday, May 8, 2015 at 2:23:27 PM UTC-5, Jim Miller wrote:
>>
>> Hi all,
>>
>> Just upgraded from 3.4.something to 3.7.5 and it seems how we were doing 
>> environments is depreciated.  I've followed a couple of docs* for how to do 
>> this but seem to be missing something. Nodes can't seem to find modules.  
>> For now it's not a big deal because it's just a warning but I'd like to 
>> address the issue.
>>
>> *http://docs.puppetlabs.com/puppet/latest/reference/environments.html 
>> (and linked docs)
>>
>> Here's the old config values in /etc/puppet/puppet.conf for environments:
>>
>> [main]
>> 
>> 
>> modulepath = /etc/puppet/modules
>> ...
>> ...
>> ...
>> environment = production
>> confdir = /etc/puppet
>>
>> [production]
>> manifest = $confdir/manifests/site.pp
>> modulepath = 
>> $confdir/environments/production/modules:$confdir/environments/test/site/modules
>>
>> [test]
>> manifest = $confdir/manifests/non-prod_site.pp
>> modulepath = 
>> $confdir/environments/test/modules:$confdir/environments/test/site/modules
>>
>> [development]
>> manifest = $confdir/manifests/non-prod_site.pp
>> modulepath = 
>> $confdir/environments/dev/modules:$confdir/environments/dev/site/modules
>>
>>
>>
>> PROPOSED:
>> [main]
>> 
>> 
>> # modulepath = /etc/puppet/modules
>> environmentpath = $confdir/environments
>> default_manifest = /etc/puppet/manifests/site.pp
>> ...
>> ...
>> ...
>> # environment = production
>> confdir = /etc/puppet
>>
>> # [production]
>> # manifest = $confdir/manifests/site.pp
>> # modulepath = 
>> $confdir/environments/production/modules:$confdir/environments/test/site/modules
>>
>> # [test]
>> #manifest = $confdir/manifests/non-prod_site.pp
>> #modulepath = 
>> $confdir/environments/test/modules:$confdir/environments/test/site/modules
>>
>> # [development]
>> # manifest = $confdir/manifests/non-prod_site.pp
>> # modulepath = 
>> $confdir/environments/dev/modules:$confdir/environments/dev/site/modules
>>
>>
>> Environments.conf
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>> Environments.conf for production:
>> manifest = $confdir/manifests/site.pp
>> modulepath = 
>> $confdir/environments/production/modules:$confdir/puppet/environments/production/site
>>
>> Environments.conf for testing:
>> manifest = $confdir/manifests/non-prod_site.pp
>> modulepath = 
>> $confdir/environments/test/modules:$confdir/environments/test/site/modules
>>
>> Environments.conf for dev:
>> manifest = $confdir/manifests/non-prod_site.pp
>> modulepath = 
>> $confdir/environments/dev/modules:$confdir/environments/dev/site/modules
>>
>>
>> Nodes .pp settings for each environment
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>> $puppet_env = "production"
>>
>> $puppet_env = "test"
>>
>> $puppet_env = "development"
>>
>>
>>
>>

-- 
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/2fcd445d-4ccc-4f00-8405-4ce10ba22ae0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet Environments change after upgrading to 3.7.5

[ess]

Re-sending after reading your situation more carefully.

We are using PE 3.7.2 with r10k and directory environments, so I don't know 
how specifically useful this will be since you're still using config 
environments.  Directory environments / PE use basemodulepath now (I'm not 
sure about config environments).

You might want to consider switching to directory environments (and 
possibly something like r10k) since config environments are deprecated, 
especially if you keep having issues.

For what it's worth, this is what a PE 3.7 directory environment setup 
might look like with regards to module and environment paths.

puppet.conf on master:
[main]
basemodulepath = 
/etc/puppetlabs/puppet/modules:/opt/puppet/share/puppet/modules
environmentpath = /etc/puppetlabs/puppet/environments

In /etc/puppetlabs/puppet/environment/
> Done anyone have any thoughts on this?
>
>
>
> On Friday, May 8, 2015 at 2:23:27 PM UTC-5, Jim Miller wrote:
>>
>> Hi all,
>>
>> Just upgraded from 3.4.something to 3.7.5 and it seems how we were doing 
>> environments is depreciated.  I've followed a couple of docs* for how to do 
>> this but seem to be missing something. Nodes can't seem to find modules.  
>> For now it's not a big deal because it's just a warning but I'd like to 
>> address the issue.
>>
>> *http://docs.puppetlabs.com/puppet/latest/reference/environments.html 
>> (and linked docs)
>>
>> Here's the old config values in /etc/puppet/puppet.conf for environments:
>>
>> [main]
>> 
>> 
>> modulepath = /etc/puppet/modules
>> ...
>> ...
>> ...
>> environment = production
>> confdir = /etc/puppet
>>
>> [production]
>> manifest = $confdir/manifests/site.pp
>> modulepath = 
>> $confdir/environments/production/modules:$confdir/environments/test/site/modules
>>
>> [test]
>> manifest = $confdir/manifests/non-prod_site.pp
>> modulepath = 
>> $confdir/environments/test/modules:$confdir/environments/test/site/modules
>>
>> [development]
>> manifest = $confdir/manifests/non-prod_site.pp
>> modulepath = 
>> $confdir/environments/dev/modules:$confdir/environments/dev/site/modules
>>
>>
>>
>> PROPOSED:
>> [main]
>> 
>> 
>> # modulepath = /etc/puppet/modules
>> environmentpath = $confdir/environments
>> default_manifest = /etc/puppet/manifests/site.pp
>> ...
>> ...
>> ...
>> # environment = production
>> confdir = /etc/puppet
>>
>> # [production]
>> # manifest = $confdir/manifests/site.pp
>> # modulepath = 
>> $confdir/environments/production/modules:$confdir/environments/test/site/modules
>>
>> # [test]
>> #manifest = $confdir/manifests/non-prod_site.pp
>> #modulepath = 
>> $confdir/environments/test/modules:$confdir/environments/test/site/modules
>>
>> # [development]
>> # manifest = $confdir/manifests/non-prod_site.pp
>> # modulepath = 
>> $confdir/environments/dev/modules:$confdir/environments/dev/site/modules
>>
>>
>> Environments.conf
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>> Environments.conf for production:
>> manifest = $confdir/manifests/site.pp
>> modulepath = 
>> $confdir/environments/production/modules:$confdir/puppet/environments/production/site
>>
>> Environments.conf for testing:
>> manifest = $confdir/manifests/non-prod_site.pp
>> modulepath = 
>> $confdir/environments/test/modules:$confdir/environments/test/site/modules
>>
>> Environments.conf for dev:
>> manifest = $confdir/manifests/non-prod_site.pp
>> modulepath = 
>> $confdir/environments/dev/modules:$confdir/environments/dev/site/modules
>>
>>
>> Nodes .pp settings for each environment
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>> $puppet_env = "production"
>>
>> $puppet_env = "test"
>>
>> $puppet_env = "development"
>>
>>
>>
>>

-- 
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/d528e0b6-ecc7-4ad1-b2b9-b8e954e3d63c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Converring floating point to integer

[Bob Vergeer]

It seems that this should be easy but I just can't seem to figure it out.   
The goal is to calculate memory size for a /dev/shm entry in the fstab and 
add an 'M' to the resulting variable.

Something like

$shm =  $memorysize_mb - 1024
file_line { 'shm':
   line => 'non

-- 
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/7c9d96d2-f077-46d4-8046-5f360963cd1a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Convert Floating point to integer

[Bob Vergeer]

Two issues, removing the decimal places and appending a character.
Trying to generate a  /dev/shm line in /etc/fstab that is set to 1G less 
than available RAM. 

The line should appear as follows in /etc/fstab:
...
none /dev/shm tmpfsrw,exec,size=2048M0   0
...

1) How do I convert something like this to integer?  The floating point 
fails
$shm_size = $memorysize_mb - 1024 

2) Used file_line to insert the string in /etc/fstab.  How do I append the 
M to the $shm_size variable without a space between?
line  => 'none/dev/shmtmpfsrw,exec,size=$shm_sizeM   0 
0'


Thanks,
Bob

-- 
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/ba5053ec-2b85-4078-b9ab-1f49ba54aa0b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Anyone really using Postgres for a Hiera backend?

[Martin]

Funny, I'd rather ask: is anyone *not* using Postgres?
On Wed 13 May 2015 at 18:45 leam hall  wrote:

> Just wondering. I found some options but don't see any under current
> development.
>
> Leam
>
>
> --
> Mind on a Mission 
>
> --
> 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/CACv9p5p5La7KacvTn1RG-V-E30K77Zt873SBR8_7s%2BbvV6Oy8A%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAK1mKETPmU6DqAOHVvF90X9SXcTxHXCY9dY1GOGYCHbURWWyWw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] error message when I tried to run puppet and apply changes to the system

[Chris Zou]

I am new to Puppet, and I am trying to follow Quest Learning Machine from 
Puppet Lab.
 
However, every time I tried to run 
puppet apply cowsayings/tests/cowsay.pp
 
Error message comes up like this:
 
Warning: The package type's allow_virtual parameter will be changing its 
default value from false to true in a future release. If you do not want to 
allow virtual packages, please explicitly set allow_virtual to false.
   (at /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/type/package.rb:430:in 
`block (3 levels) in ')
Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list cowsay' returned 1: 
Error: Cannot find a valid baseurl for repo: epel
Could not retrieve mirrorlist 
http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6&arch=i386 error was
14: PYCURL ERROR 7 - "Failed to connect to 2001:4178:2:1269::fed2: Network 
is unreachable"
Error: /Stage[main]/Cowsayings::Cowsay/Package[cowsay]/ensure: change from 
absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y list 
cowsay' returned 1: Error: Cannot find a valid baseurl for repo: epel
Could not retrieve mirrorlist 
http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6&arch=i386
error was
14: PYCURL ERROR 7 - "Failed to connect to 2001:4178:2:1269::fed2: Network 
is unreachable"
 
What does "Cannot find a valid baseurl for repo: epel" mean? How can I fix 
these errors?
 
I really appreciate your help!!

-- 
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/284e8988-4388-40fb-8cae-7f21de4ced28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] error when I run puppet and try to apply changes to the system

[Chris Zou]

Hi,
 
I am new to puppet and I am trying to follow Quest Guide and its VM 
Learning Machine.
 
When I run puppet apply cowsayings/tests/cowsay.pp, I encounter error 
message as following:   

Warning: The package type's allow_virtual parameter will be changing its 
default value from false to true in a future release. If you do not want to 
allow virtual packages, please explicitly set allow_virtual to false.
   (at /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/type/package.rb:430:in 
`block (3 levels) in ')
Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list cowsay' returned 1: 
Error: Cannot find a valid baseurl for repo: epel
Could not retrieve mirrorlist 
http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6&arch=i386 error was
14: PYCURL ERROR 7 - "Failed to connect to 2001:4178:2:1269::fed2: Network 
is unreachable"
Error: /Stage[main]/Cowsayings::Cowsay/Package[cowsay]/ensure: change from 
absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y list 
cowsay' returned 1: Error: Cannot find a valid baseurl for repo: epel
Could not retrieve mirrorlist 
http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6&arch=i386 error was
14: PYCURL ERROR 7 - "Failed to connect to 2001:4178:2:1269::fed2: Network 
is unreachable"
 
 
What does it mean by "Error: Cannot find a valid baseurl for repo: epel"?
Why "network is unreachable"? 
How can I fix it? 
 
 
I really appreciate your help!

-- 
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/3fdadec0-d97b-4d65-abe2-4ce59d633b78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Local Module installation via r10k - puppet ....Help Needed

[Anderson Mills]

Vijayabalan,

So the Puppetfile for r10k is not the same as for Librarian-puppet, and 
there is no :path key for a mod in r10k.

You'll either have to keep them in a repo and specify a :git key, or pull 
them from the forge.

Docs for r10k's use of Puppetfile! 
https://docs.puppetlabs.com/pe/latest/r10k_puppetfile.html
(The docs are for PE 3.8, but r10k is the same between Puppet Enterprise 
and open source.)

This is also an issue that is on the roadmap -- 
https://github.com/puppetlabs/r10k/issues/47

Hope that helps,
Anderson

On Tuesday, May 12, 2015 at 12:57:58 PM UTC-7, Vijayabalan Balakrishnan 
wrote:
>
> -bash-4.1$ r10k deploy environment -pv
> INFO -> Deploying environment 
> /etc/puppetlabs/puppet/environments/operation_production
> INFO -> Deploying environment 
> /etc/puppetlabs/puppet/environments/operation_vijay
>
>
> [root@ puppet]# ls -ltrh 
> /etc/puppetlabs/puppet/environments/operation_vijay/modules/
> total 0
>
> No modules are listed..
>
> Kindly help me.
>
>
> On Tuesday, May 12, 2015 at 9:05:17 PM UTC+5:30, Vijayabalan Balakrishnan 
> wrote:
>>
>> I have configured the puppet PE 3.8 and sucessfully integrated r10k and 
>> git.I am able to download modules from forgeapi.puppetlabs.com and i can 
>> able to populate via r10k for dynamic branches.
>>
>> Now i have downloaded some modules from forgeapi.puppetlabs.com and kept 
>> it to /modules directory
>>
>> my Puppetfile is like below
>>
>> mod 'puppetlabs/apache', :path => '/module/apache'
>> mod 'puppetlabs/vsftpd', :path => '/module/vsftpd'
>> mod 'puppetlabs/portage', :path => '/modules/portage'
>> mod 'puppetlabs/pe_gem', :path => '/modules/pe_gem'
>> mod 'puppetlabs/vcsrepo', :path => '/modules/vcsrepo'
>> mod 'puppetlabs/ntp', :path => '/modules/ntp'
>> mod 'puppetlabs/inifile', :path => '/modules/inifile'
>> mod 'puppetlabs/mysql', :path => '/modules/mysql'
>> mod 'puppetlabs/postgresql', :path => '/modules/postgresql'
>> mod 'puppetlabs/firewall', :path => '/modules/firewall'
>> mod 'puppetlabs/puppetdb', :path => '/modules/puppetdb'
>> mod 'puppetlabs/concat', :path => '/modules/concat'
>> mod 'puppetlabs/stdlib', :path => '/modules/stdlib'
>>
>> when i execute the following command i am getting the below error
>>
>> r10k deploy environment -pv
>>
>> INFO -> Deploying module 
>> /etc/puppetlabs/puppet/environments/operations_vijay/modules/apache
>> INFO -> Deploying module 
>> /etc/puppetlabs/puppet/environments/operations_vijay/modules/vsftpd
>> ERROR-> Command exited with non-zero exit code:
>> Command: puppet module --modulepath 
>> /etc/puppetlabs/puppet/environments/operations_vijay/modules --color false 
>> install --force puppetlabs/vsftpd
>> Stdout:
>> Notice: Preparing to install into 
>> /etc/puppetlabs/puppet/environments/operations_vijay/modules ...
>> Notice: Downloading from https://forgeapi.puppetlabs.com ...
>> Stderr:
>> Error: Could not install 'puppetlabs-vsftpd' (latest)
>>   No releases are available from https://forgeapi.puppetlabs.com
>> Does 'puppetlabs-vsftpd' have at least one published release?
>> Exit code: 1
>> INFO -> Deploying module 
>> /etc/puppetlabs/puppet/environments/operations_vijay/modules/portage
>> ERROR-> Command exited with non-zero exit code:
>> Command: puppet module --modulepath 
>> /etc/puppetlabs/puppet/environments/operations_vijay/modules --color false 
>> install --force puppetlabs/portage
>> Stdout:
>> Notice: Preparing to install into 
>> /etc/puppetlabs/puppet/environments/operations_vijay/modules ...
>> Notice: Downloading from https://forgeapi.puppetlabs.com ...
>> Stderr:
>> Error: Could not install 'puppetlabs-portage' (latest)
>>   No releases are available from https://forgeapi.puppetlabs.com
>> Does 'puppetlabs-portage' have at least one published release?
>> Exit code: 1
>> INFO -> Deploying module 
>> /etc/puppetlabs/puppet/environments/operations_vijay/modules/pe_gem
>> INFO -> Deploying module 
>> /etc/puppetlabs/puppet/environments/operations_vijay/modules/vcsrepo
>> INFO -> Deploying module 
>> /etc/puppetlabs/puppet/environments/operations_vijay/modules/ntp
>> INFO -> Deploying module 
>> /etc/puppetlabs/puppet/environments/operations_vijay/modules/inifile
>> INFO -> Deploying module 
>> /etc/puppetlabs/puppet/environments/operations_vijay/modules/mysql
>> INFO -> Deploying module 
>> /etc/puppetlabs/puppet/environments/operations_vijay/modules/postgresql
>> INFO -> Deploying module 
>> /etc/puppetlabs/puppet/environments/operations_vijay/modules/firewall
>> INFO -> Deploying module 
>> /etc/puppetlabs/puppet/environments/operations_vijay/modules/puppetdb
>> INFO -> Deploying module 
>> /etc/puppetlabs/puppet/environments/operations_vijay/modules/concat
>> INFO -> Deploying module 
>> /etc/puppetlabs/puppet/environments/operations_vijay/modules/stdlib
>> INFO -> Removing unmanaged path 
>> /etc/puppetlabs/puppet/environments/production
>>
>>
>>
>> from this output i dont 

[Puppet Users] Upgrade puppetdb goes wrong

[Arpin Dominique (Nter)]

Hi,

Here my setup :
puppetdb-terminus-2.2.2-1.el6.noarch
puppetdb-2.2.2-1.el6.noarch
postgresql93-libs-9.3.6-1PGDG.rhel6.x86_64
postgresql93-server-9.3.6-1PGDG.rhel6.x86_64
postgresql93-contrib-9.3.6-1PGDG.rhel6.x86_64
postgresql93-9.3.6-1PGDG.rhel6.x86_64
Centos 6.6

I try to upgrade to the latest puppetdb and puppetdb-terminus 3.3.4, but I got 
this error:

clojure.lang.ExceptionInfo: Input to init! does not match schema: [nil (named 
{:ss-ca-cert disallowed-key} config)]
at 
puppetlabs.trapperkeeper.services.webserver.jetty9_core$eval22731$init_BANG___22732.invoke
 (jetty9_core.clj:891)

puppetlabs.trapperkeeper.services.webserver.jetty9_service$reify__23105$service_fnk__17647__auto___positional$reify__23112.ini
t (jetty9_service.clj:35)

puppetlabs.trapperkeeper.services$eval17483$fn__17484$G__17475__17487.invoke 
(services.clj:8)

puppetlabs.trapperkeeper.services$eval17483$fn__17484$G__17474__17491.invoke 
(services.clj:8)
puppetlabs.trapperkeeper.internal$run_lifecycle_fn_BANG_.invoke 
(internal.clj:152)
puppetlabs.trapperkeeper.internal$run_lifecycle_fns.invoke 
(internal.clj:180)
puppetlabs.trapperkeeper.internal$build_app_STAR_$reify__19027.init 
(internal.clj:444)
puppetlabs.trapperkeeper.internal$boot_services_STAR_$fn__19039.invoke 
(internal.clj:470)
puppetlabs.trapperkeeper.internal$boot_services_STAR_.invoke 
(internal.clj:469)
puppetlabs.trapperkeeper.core$boot_with_cli_data.invoke (core.clj:113)
puppetlabs.trapperkeeper.core$run.invoke (core.clj:144)

I follow the upgrade howto 
(https://docs.puppetlabs.com/puppetdb/latest/configure.html#using-postgresql ) 
without success.

And I can connect to the BD:
[root@puppetserver01 conf.d]# psql -h localhost puppetdb puppetdb
Password for user puppetdb:
psql (9.4.1, server 9.3.6)
Type "help" for help.

puppetdb=>

Regards,

 Dominique Arpin


Mise en garde concernant la confidentialité : Le présent message, comprenant 
tout fichier qui y est joint, est envoyé à l'intention exclusive de son 
destinataire; il est de nature confidentielle et peut constituer une 
information protégée par le secret professionnel. Si vous n'êtes pas le 
destinataire, nous vous avisons que toute impression, copie, distribution ou 
autre utilisation de ce message est strictement interdite. Si vous avez reçu ce 
courriel par erreur, veuillez en aviser immédiatement l'expéditeur par retour 
de courriel et supprimer le courriel. Merci!

Confidentiality Warning: This message, including any attachment, is sent only 
for the use of the intended recipient; it is confidential and may constitute 
privileged information. If you are not the intended recipient, you are hereby 
notified that any printing, copying, distribution or other use of this message 
is strictly prohibited. If you have received this email in error, please notify 
the sender immediately by return email, and delete it. Thank you!

-- 
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/C2F62CDF5915D0458F0528664315BAE7608CBDF8%40MTL1EXC01.scqmtl.loto-quebec.com.
For more options, visit https://groups.google.com/d/optout.
<>

[Puppet Users] New MCollective Plugin for OpenSCAP Scanning

[Trevor Vaughan]

Hi All,

I presented a piece on a proof of concept that I put together to perform
OpenSCAP scans against systems using MCollective.

I thought that some of you might be interested. The relevant information is
all linked from my post at
http://www.onyxpoint.com/distributed-openscap-scanning-with-mcollective/.

Thanks,

Trevor

-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvaug...@onyxpoint.com

-- This account not approved for unencrypted proprietary information --

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

[Puppet Users] Learning Custom Types Module

[Trevor Vaughan]

Hi All,

Yesterday, while at Puppet Camp DC, I pushed a module to the forge that's
meant for learning the execution flow of custom types and providers.

You can download it from the forge using 'puppet module install
onyxpoint-learning_custom_types' or you can fork it on GitHub at
https://github.com/onyxpoint/onyxpoint-learning_custom_types.

This is an extension of my presentation on Types and Providers as presented
last year at Puppet Camp DC 2014.

Happy Hacking!

Trevor

-- 
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvaug...@onyxpoint.com

-- This account not approved for unencrypted proprietary information --

-- 
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/CANs%2BFoX5Ue4dzofi%3DO1MRJtNviMr%2BYMfg2cT1uz2OSfA2x6N1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.