[Puppet Users] Re: Best way to do custom facts based on 3rd party data

2014-10-24 Thread 'Kimo Rosenbaum' via Puppet Users 
Thanks. Here's a simplified version of what I ended up doing (for anyone 
searching for a similar thing):

In custom_functions/lib/puppet/parser/functions/determine_role.rb:

module Puppet::Parser::Functions
  newfunction(:determine_role, :type => :rvalue) do |args|
# args[0] should be a fact name like clientcert or fqdn.
hostname = lookupvar(args[0])
matches = hostname.match(/^([^0-9.]+)[0-9.]/).captures
role = matches[0]
return role
  end
end

In manifests/site.pp

$role = determine_role('clientcert')

node default {
  hiera_include('classes')
}

-- 
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/d416e2fd-4731-4e10-852a-f3663e61e3e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] hiera-eyaml - performance implications?

2014-10-24 Thread Ramin K 

On 10/24/14 12:01 PM, Tim Skirvin wrote:

 I've started investigating hiera-eyaml as a tool for managing
secrets within our puppet repository.  It looks pretty promising,
especially in connection with 'show_diff => false'.  For those that
haven't seen it:

 http://puppetlabs.com/blog/encrypt-your-data-using-hiera-eyaml

 That said, I'm not sure what its performance implications are, and
how many decryption calls we can afford.  Has anybody played with this
enough to be able to know how how these decryption calls will affect
performance problems?

 More concretely: I'm currently supporting ~1250 nodes with two
fairly-hefty puppet servers, but we're not managing much in the way of
secrets.  If I were to, say, start managing the root password on all of
our nodes using this tool, should I expect our entirely environment to
melt down?

 - Tim Skirvin (tskir...@fnal.gov)



My experience is the same as Christopher's though our frontend servers 
pull 50+ encrypted keys for everything from db credentials to third 
party shared secrets per environment. I didn't notice a change when we 
switched to eyaml, but I also coupled it with a upgrade to Ruby 1.9.3 
from 1.8.7. Also we have only 150 nodes.


I'd say start slowly or on your stage master, but don't be surprised if 
adding a few keys fails to impact performance.


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

Re: [Puppet Users] hiera-eyaml - performance implications?

2014-10-24 Thread Christopher Wood 
On Fri, Oct 24, 2014 at 02:01:27PM -0500, Tim Skirvin wrote:
> I've started investigating hiera-eyaml as a tool for managing
> secrets within our puppet repository.  It looks pretty promising,
> especially in connection with 'show_diff => false'.  For those that
> haven't seen it:
> 
> http://puppetlabs.com/blog/encrypt-your-data-using-hiera-eyaml
> 
> That said, I'm not sure what its performance implications are, and
> how many decryption calls we can afford.  Has anybody played with this
> enough to be able to know how how these decryption calls will affect
> performance problems?

I haven't noticed any performance issues. On the other hand, maybe I would if I 
didn't have so many classes, resources, and hiera lookups.

> More concretely: I'm currently supporting ~1250 nodes with two
> fairly-hefty puppet servers, but we're not managing much in the way of
> secrets.  If I were to, say, start managing the root password on all of
> our nodes using this tool, should I expect our entirely environment to
> melt down?

Since you can revert the password-managing commit quite quickly, perhaps you 
could tell us how it goes? :D

> - Tim Skirvin (tskir...@fnal.gov)
> -- 
> HPC Systems Administrator / Developerhttp://www.linkedin.com/in/tskirvin
>USCMS-T1 Collaboration   Fermilab Scientific Computing


-- 
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/20141024191149.GA1404%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] hiera-eyaml - performance implications?

2014-10-24 Thread Tim Skirvin 
I've started investigating hiera-eyaml as a tool for managing
secrets within our puppet repository.  It looks pretty promising,
especially in connection with 'show_diff => false'.  For those that
haven't seen it:

http://puppetlabs.com/blog/encrypt-your-data-using-hiera-eyaml

That said, I'm not sure what its performance implications are, and
how many decryption calls we can afford.  Has anybody played with this
enough to be able to know how how these decryption calls will affect
performance problems?

More concretely: I'm currently supporting ~1250 nodes with two
fairly-hefty puppet servers, but we're not managing much in the way of
secrets.  If I were to, say, start managing the root password on all of
our nodes using this tool, should I expect our entirely environment to
melt down?

- Tim Skirvin (tskir...@fnal.gov)
-- 
HPC Systems Administrator / Developerhttp://www.linkedin.com/in/tskirvin
   USCMS-T1 Collaboration   Fermilab Scientific Computing


pgpagPT0qfbq2.pgp
Description: PGP signature

[Puppet Users] schedule metaparameter

2014-10-24 Thread Mark Rosedale 
Hello,

I'm looking to start to implement scheduling for certain resources within 
puppet. My one question is this. 

If I have a schedule set on resource 'foo' does that prohibit that resource 
from being updated if I run puppet agent by hand? What I'm wondering is if 
I end up needing to do puppet work manually, but am outside of a my 
maintenance window do I have to edit my puppet code to apply foo or can I 
override it somehow? 

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/6c7e15c6-4f2c-473b-98c7-230eac37d8cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] command 'store report' version 2 is deprecated?

2014-10-24 Thread Ken Barber 
> I recently changed over to a postgres back end. Now puppetdb.log seems to be
> awash in these errors.
>
> I'm pretty sure everything is up to date:
>
>
> # rpm -qa | grep puppet
> puppetlabs-release-6-11.noarch
> puppet-server-3.7.2-1.el6.noarch
> puppetdb-2.2.2-1.el6.noarch
> puppet-3.7.2-1.el6.noarch
> puppetdb-terminus-2.2.2-1.el6.noarch
> vim-puppet-2.7.20-1.el6.rf.noarch
>
>
> Did I miss a step somewhere?

Very likely you haven't restart your puppet master yet. Thats a
necessary step for the terminus upgrade to take hold, and use the
latest commands.

ken.

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

[Puppet Users] command 'store report' version 2 is deprecated?

2014-10-24 Thread JonY 
I recently changed over to a postgres back end. Now puppetdb.log seems to 
be awash in these errors.

I'm pretty sure everything is up to date:


# rpm -qa | grep puppet
puppetlabs-release-6-11.noarch
puppet-server-3.7.2-1.el6.noarch
puppetdb-2.2.2-1.el6.noarch
puppet-3.7.2-1.el6.noarch
puppetdb-terminus-2.2.2-1.el6.noarch
vim-puppet-2.7.20-1.el6.rf.noarch


Did I miss a step somewhere?



-- 
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/0a058565-db50-4611-9625-9826409f0dd4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] pull defined type into puppet template?

2014-10-24 Thread Wil Cooley 
On Fri, Oct 24, 2014 at 10:07 AM, Wil Cooley  wrote:

>  as Trey suggested, the `concat::fragment` type in the puppetlabs/concat
> module,
>

Er, as James suggested; sorry.

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

Re: [Puppet Users] pull defined type into puppet template?

2014-10-24 Thread Wil Cooley 
On Thu, Oct 23, 2014 at 8:50 AM, Trey Ormsbee  wrote:

> I working with a dynamic config file template,  I have a section for
> global options,  then a dynamic section that i want to populate with
> multiple defined entries.
>
> example config file
>
> #global options
> config_option1=setting1
> config_option2=setting2
> config_option3=setting3
> ...
> #dynamic section
> entry=dynamic entry number 1
> option1=setting1
> option2=setting2
> option3=setting3
>
> entry=dynamic entry number 2
> option1=setting1
> option2=setting2
> option3=setting3
>
> 
>
> Is there a way i can dynamically create these entries in a single template?
>
> for instance a defined type:
>
> define application::configs (
>
>   $entry,
>
>   $option1
>
>   $option2
>
>   $option3
>
> ) {
>
> #not sure what I would put here
>
>  }
> Then pull those entries into the .erb with some kind of function?  Is this
> even possible to do?
>

And you then want to declare multiple application::config resources and
have them all show up in the resulting file, generated from a template?

It's not possible to have many-to-1 like that with the contents of a File
resource, although I myself have wished for something like that. Instead,
you can model your configs at a more finely-grained level than just a File
resource using other resources/modules, as Trey suggested, the
`concat::fragment` type in the puppetlabs/concat module, `ini_setting` type
in the puppetlabs/inifile module, or by using Augeas.

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

Re: [Puppet Users] example hiera.yaml that uses example42-network?

2014-10-24 Thread Wil Cooley 
On Fri, Oct 24, 2014 at 7:49 AM, Anthony Clark 
wrote:

> Hi All,
>
> Does anyone use example42-network with Hiera?  I'm trying to find an
> example in Hiera that configures that module.
>
> https://forge.puppetlabs.com/example42/network/readme
>
> So far I've tried, in .yaml (Hiera works OK with hostname,
> environment, etc etc)
>
> ---
> network::interfaces_hash:
>   eth1:
> ipaddress: 1.2.3.4
> netmask: 255.255.0.0
> gateway: 1.2.3.1
>
> Which I think should work, based on the Puppet example from the Forge
> module readme:
>
> class { 'network': interfaces_hash =>
>   { 'eth0' => { enable_dhcp => true, },
> 'eth1' => { ipaddress => '10.42.42.50', netmask => '255.255.255.0', },
>   },
> }
>

What's actually happening when you do this?

I assume you also have "include network" in your manifests?

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

Re: [Puppet Users] Puppet agent message: Could not retrieve local facts: Could not find fact 'define_fact'

2014-10-24 Thread Wil Cooley 
On Thu, Oct 23, 2014 at 9:52 AM, Andreas Dvorak 
wrote:

> Dear all,
>
> since today the puppet agent does not work anymore if it is executed by
> service.
> I prints out:
> Could not retrieve local facts: Could not find fact 'define_fact'
>
> If I run puppet agent -t I do not get the message.
> I have updated facter from 1.7.1 to 2.1 and hiera from 1.2.1 to 1.3.4
>

Did you restart the Puppet Agent after the upgrade?

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/CAMmm3r4PXNiwLAOfbW9iM-XC%2BX-OyOkmKHRt%3D83-Tyrbc9qoWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Puppet agent message: Could not retrieve local facts: Could not find fact 'define_fact'

2014-10-24 Thread Andreas Dvorak 
Hi,

thank you for the answer.
No I don't have multiple facter installed.
find / -name facter
/usr/bin/facter
/usr/lib/ruby/site_ruby/1.8/facter
/var/lib/puppet/lib/facter

Andreas

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

[Puppet Users] Re: Questions about puppet classes and parameters

2014-10-24 Thread liu.cy 
in general, /etc/puppet/manifests/site.pp is the entry point of puppet 
manifests, the content always be [import 'nodes/*.pp'].
create pp file in /etc/puppet/manifests/nodes directory to save your all 
node definitions.
node definition contains variables, expressions, classes. it defines which 
function should run in your servers, like nginx, memcached or tomcat. and 
the port that your want your application listen, memory size or other 
parameter it use. pass it to the classes which do the actually things.

the nginx class contains package, service, file resources, accept assigned 
parameters do the installation, configuration steps.(actually it ensure 
nginx package is installed and nginx service is running)

is that ok for you?

ps: excuse my syntax, I'm Chinese.

On Friday, October 24, 2014 9:47:21 AM UTC+8, Rohit wrote:
>
> Hi, 
>
> I am looking at ways to configure my puppet module (which justs uses 
> another module from puppet forge) to set configuration data. What I want to 
> do is this:
>
> I have a puppet module called 'testing' and created class testing::haproxy 
> in it. I basically want to use this class to setup all configuration 
> parameters which puppetlabs-haproxy module supports - like setting up 
> default options, global options, frontends and backends. I am not sure on 
> how to set haproxy variables/parameters in my 'testing' module. 
>
> I just got started with puppet and looking for some direction regarding 
> this. BTW, I am running open source puppet. 
>
> Thanks for your help in advance. 
>
> Regards, 
> Rohit
>

-- 
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/63bf3401-d6d3-4280-ae36-ab2ef19ede79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Error: Could not run: SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read finished A

2014-10-24 Thread Jeff Sparrow 


I am trying to copy a current Puppet Master server on one domain and move 
it to another. Im finding that its very hard to try to change all the 
config remanence. Is there an easy way to do this, or a step by step best 
practice? I have grepped most of the old fqdn name and changed it to the 
new one, yet when I delete all certs, and re-issue new ones on the master, 
it wants to keep pulling a cert for the old FQDN.

*Edit 1:* I have resolved many of the issues I was previously getting. 
However I can not get past this SSL issue for the life of me.

[root@puppet lib]# puppet resource service apache2 ensure=running
Error: Could not run: SSL_connect returned=1 errno=0 state=SSLv3 read server 
certificate B: certificate verify failed: [unable to get local issuer 
certificate for /CN=puppet.foundry.test]

I have attempted to completely purge all certs from the master, using this 
link 
,
 
and then regenerate all. But I still keep getting the same errors:

Error: Could not run: SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read 
finished A

-- 
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/1a493bac-8788-4c70-9019-32033a557366%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: pull defined type into puppet template?

2014-10-24 Thread Trey Ormsbee 
James  thanks for suggesting concat,  it worked perfectly;  the examples on 
the page were more then enough to get me going.

Thanks,


On Friday, October 24, 2014 9:08:18 AM UTC-5, Trey Ormsbee wrote:
>
> Concat might work,  let me toy with this,  ill post back if i get a 
> working example.
>
>

-- 
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/7dd84340-0c1d-485f-aac3-6bb66925f8a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] example hiera.yaml that uses example42-network?

2014-10-24 Thread Anthony Clark 
Hi All,

Does anyone use example42-network with Hiera?  I'm trying to find an 
example in Hiera that configures that module.

https://forge.puppetlabs.com/example42/network/readme

So far I've tried, in .yaml (Hiera works OK with hostname, 
environment, etc etc)

---
network::interfaces_hash:
  eth1:
ipaddress: 1.2.3.4
netmask: 255.255.0.0
gateway: 1.2.3.1

Which I think should work, based on the Puppet example from the Forge 
module readme:

class { 'network': interfaces_hash => 
  { 'eth0' => { enable_dhcp => true, },
'eth1' => { ipaddress => '10.42.42.50', netmask => '255.255.255.0', },
  },
}

So, any pointers on where I'm going wrong?

Thanks in advance,

Anthony

-- 
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/c4870356-c879-4db8-864d-bd6aca71a2e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] It's possible create fact search messages error

2014-10-24 Thread Felix Frank 
On 10/21/2014 06:06 PM, New wrote:
> Hello
> I need create fact that check the messages log and find any error with
> every execution of puppet.
> The objective is check if any error appear in any execution of puppet
> and return the name of the class fail.
> Thanks!!!

Hi,

have you tried storing reports on the master/in PuppetDB and examining
those?

Specifically, PuppetBoard and PuppetExplorer may be good starting points
for you to get a quick visual of the data that is available. Scripting
your own retrieval and monitoring should be rather simple then.

Best regards,
Felix

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

[Puppet Users] Re: pull defined type into puppet template?

2014-10-24 Thread Trey Ormsbee 
Concat might work,  let me toy with this,  ill post back if i get a working 
example.

-- 
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/89380947-11bb-4b63-8489-a1dbd0d8c956%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: Puppet agent message: Could not retrieve local facts: Could not find fact 'define_fact'

2014-10-24 Thread Kylo Ginsberg 
On Fri, Oct 24, 2014 at 5:43 AM, Andreas Dvorak 
wrote:

> After downgrade facter to 1.7.1 the error is gone.
> Then I did the update again and the error was back again.
>

Can you double-check that this server doesn't have multiple versions of
facter installed? E.g. this can happen with one installed from packages and
one from gem, etc.

Kylo


>
> I have many server that already have the version 2.1, without an update.
>
> I don't understand why the update does not 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/e6383291-1fee-4fe1-abf0-73f9e627e737%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Kylo Ginsberg | k...@puppetlabs.com | irc: kylo | twitter: @kylog

*Join us at **PuppetConf 2015, October 5-9 in Portland, OR - *
http://2015.puppetconf.com.
*Register early to save 40%!*

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

Re: [Puppet Users] apache::vhost add prefix to logfiles

2014-10-24 Thread Christopher Webber 
Maybe do something with create_resources and hiera? It has been a while since I 
have done it so I don’t have code handy but it is worth looking at.

— cwebber

> On Oct 24, 2014, at 5:41 AM, Denny  wrote:
> 
> thanks, but this would be far to much work for like 100 vhosts, which I want 
> to sort into 2-3 groups of vhosts
> 
> in fact, it's probably easier to put them into different directories
> 
> Am Freitag, 24. Oktober 2014 14:27:47 UTC+2 schrieb cwebber:
> Ok,
> 
> So when you call `access_log_file => “wordpress_${access_log_file}”` puppet 
> is pulling $access_log_file from the scope in which you called apache::vhost 
> what you probably want to do is something like:
> 
> $vhost_name = ‘vhost.example.com '
> $vhost_type = ‘wordpress’
> 
> apache::vhost {$vhost_name:
>   port=> 80,
>   docroot => "/var/www/html/${vhost_name}”,
>   serveradmin => ‘ihaz...@mail.com ’,
>   access_log_file => “${vhost_type}_${vhost_name}_access.log”,
>   error_log_file  => “${vhost_type}_${vhost_name}_error.log”
> }
> 
>> On Oct 24, 2014, at 5:17 AM, Denny > wrote:
>> 
>> puppetlabs-apache (v1.1.1)
>> 
>> Am Freitag, 24. Oktober 2014 13:35:23 UTC+2 schrieb cwebber:
>> Denny,
>> 
>> Which apache module are you using?
>> 
>> — cwebber
>> 
>>> On Oct 24, 2014, at 12:32 AM, Denny > wrote:
>>> 
>>> Hi there,
>>> 
>>> this is - for sure - pretty easy to solve but I'm a bit stuck right now...
>>> 
>>> I want to add a prefix to my apache-vhost access and error logs depending 
>>> on what kind of application is installed on this vhost
>>> 
>>> Right now my config looks something like this:
>>> 
>>> apache::vhost { 'vhost.example.com ':
>>>   port=> '80',
>>>   docroot => '/var/www/html/someprettywebsite',
>>>   serveradmin => 'dontc...@example.com <>',
>>> }
>>> 
>>> which produces two log files: 
>>> /var/log/http/vhost.example.com _error.log 
>>> /var/log/http/vhost.example.com _access.log
>>> 
>>> 
>>> but what I want is something like:
>>> 
>>> /var/log/http/wordpress_vhost.example.com _error.log 
>>> /var/log/http/wordpress_vhost.example.com 
>>> _access.log
>>> 
>>> I've tried things like the example below, but didn't work :(
>>> 
>>> apache::vhost { 'vhost.example.com ':
>>>   port=> '80',
>>>   docroot => '/var/www/html/someprettywebsite',
>>>   serveradmin => 'dontc...@example.com <>',
>>>   access_log_file => "wordpress_${access_log_file}",
>>> }
>>> 
>>> 
>>> Any suggestions are welcome,
>>> 
>>> Denny
>>> 
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Puppet Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to puppet-users...@googlegroups.com <>.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/puppet-users/0931-1ab3-462a-9441-2ded4a79a879%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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/298497a4-6140-4c52-b544-9c2a2c74b58c%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/15880dcf-6fb8-495d-a12b-b601ea5afa5f%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/p

[Puppet Users] Re: Puppet agent message: Could not retrieve local facts: Could not find fact 'define_fact'

2014-10-24 Thread Andreas Dvorak 
After downgrade facter to 1.7.1 the error is gone.
Then I did the update again and the error was back again.

I have many server that already have the version 2.1, without an update.

I don't understand why the update does not 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/e6383291-1fee-4fe1-abf0-73f9e627e737%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] apache::vhost add prefix to logfiles

2014-10-24 Thread Denny 
thanks, but this would be far to much work for like 100 vhosts, which I 
want to sort into 2-3 groups of vhosts

in fact, it's probably easier to put them into different directories

Am Freitag, 24. Oktober 2014 14:27:47 UTC+2 schrieb cwebber:
>
> Ok,
>
> So when you call `access_log_file => “wordpress_${access_log_file}”` 
> puppet is pulling $access_log_file from the scope in which you called 
> apache::vhost what you probably want to do is something like:
>
> $vhost_name = ‘vhost.example.com'
> $vhost_type = ‘wordpress’
>
> apache::vhost {$vhost_name:
>   port=> 80,
>   docroot => "/var/www/html/${vhost_name}”,
>   serveradmin => ‘ihaz...@mail.com ’,
>   access_log_file => “${vhost_type}_${vhost_name}_access.log”,
>   error_log_file  => “${vhost_type}_${vhost_name}_error.log”
> }
>
> On Oct 24, 2014, at 5:17 AM, Denny > 
> wrote:
>
> puppetlabs-apache (v1.1.1)
>
> Am Freitag, 24. Oktober 2014 13:35:23 UTC+2 schrieb cwebber:
>>
>> Denny,
>>
>> Which apache module are you using?
>>
>> — cwebber
>>
>> On Oct 24, 2014, at 12:32 AM, Denny  wrote:
>>
>> Hi there,
>>
>> this is - for sure - pretty easy to solve but I'm a bit stuck right now...
>>
>> I want to add a prefix to my apache-vhost access and error logs depending 
>> on what kind of application is installed on this vhost
>>
>> Right now my config looks something like this:
>>
>> apache::vhost { 'vhost.example.com':
>>   port=> '80',
>>   docroot => '/var/www/html/someprettywebsite',
>>   serveradmin => 'dontc...@example.com',
>> }
>>
>> which produces two log files: 
>> /var/log/http/vhost.example.com_error.log 
>> /var/log/http/vhost.example.com_access.log
>>
>>
>> but what I want is something like:
>>
>> /var/log/http/wordpress_vhost.example.com_error.log 
>> /var/log/http/wordpress_vhost.example.com_access.log
>>
>> I've tried things like the example below, but didn't work :(
>>
>> apache::vhost { 'vhost.example.com':
>>   port=> '80',
>>   docroot => '/var/www/html/someprettywebsite',
>>   serveradmin => 'dontc...@example.com',
>>   access_log_file => "wordpress_${access_log_file}",
>> }
>>
>>
>> Any suggestions are welcome,
>>
>> Denny
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to puppet-users...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/0931-1ab3-462a-9441-2ded4a79a879%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...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/298497a4-6140-4c52-b544-9c2a2c74b58c%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/15880dcf-6fb8-495d-a12b-b601ea5afa5f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] apache::vhost add prefix to logfiles

2014-10-24 Thread Christopher Webber 
Ok,

So when you call `access_log_file => “wordpress_${access_log_file}”` puppet is 
pulling $access_log_file from the scope in which you called apache::vhost what 
you probably want to do is something like:

$vhost_name = ‘vhost.example.com'
$vhost_type = ‘wordpress’

apache::vhost {$vhost_name:
  port=> 80,
  docroot => "/var/www/html/${vhost_name}”,
  serveradmin => ‘ihazem...@mail.com’,
  access_log_file => “${vhost_type}_${vhost_name}_access.log”,
  error_log_file  => “${vhost_type}_${vhost_name}_error.log”
}

> On Oct 24, 2014, at 5:17 AM, Denny  wrote:
> 
> puppetlabs-apache (v1.1.1)
> 
> Am Freitag, 24. Oktober 2014 13:35:23 UTC+2 schrieb cwebber:
> Denny,
> 
> Which apache module are you using?
> 
> — cwebber
> 
>> On Oct 24, 2014, at 12:32 AM, Denny > 
>> wrote:
>> 
>> Hi there,
>> 
>> this is - for sure - pretty easy to solve but I'm a bit stuck right now...
>> 
>> I want to add a prefix to my apache-vhost access and error logs depending on 
>> what kind of application is installed on this vhost
>> 
>> Right now my config looks something like this:
>> 
>> apache::vhost { 'vhost.example.com ':
>>   port=> '80',
>>   docroot => '/var/www/html/someprettywebsite',
>>   serveradmin => 'dontc...@example.com ',
>> }
>> 
>> which produces two log files: 
>> /var/log/http/vhost.example.com _error.log 
>> /var/log/http/vhost.example.com _access.log
>> 
>> 
>> but what I want is something like:
>> 
>> /var/log/http/wordpress_vhost.example.com_error.log 
>> /var/log/http/wordpress_vhost.example.com 
>> _access.log
>> 
>> I've tried things like the example below, but didn't work :(
>> 
>> apache::vhost { 'vhost.example.com ':
>>   port=> '80',
>>   docroot => '/var/www/html/someprettywebsite',
>>   serveradmin => 'dontc...@example.com ',
>>   access_log_file => "wordpress_${access_log_file}",
>> }
>> 
>> 
>> Any suggestions are welcome,
>> 
>> Denny
>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to puppet-users...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/0931-1ab3-462a-9441-2ded4a79a879%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/298497a4-6140-4c52-b544-9c2a2c74b58c%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/2B21DE26-29DC-45A9-AEFF-A213970EFF48%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] apache::vhost add prefix to logfiles

2014-10-24 Thread Denny 
puppetlabs-apache (v1.1.1)

Am Freitag, 24. Oktober 2014 13:35:23 UTC+2 schrieb cwebber:
>
> Denny,
>
> Which apache module are you using?
>
> — cwebber
>
> On Oct 24, 2014, at 12:32 AM, Denny > 
> wrote:
>
> Hi there,
>
> this is - for sure - pretty easy to solve but I'm a bit stuck right now...
>
> I want to add a prefix to my apache-vhost access and error logs depending 
> on what kind of application is installed on this vhost
>
> Right now my config looks something like this:
>
> apache::vhost { 'vhost.example.com':
>   port=> '80',
>   docroot => '/var/www/html/someprettywebsite',
>   serveradmin => 'dontc...@example.com ',
> }
>
> which produces two log files: 
> /var/log/http/vhost.example.com_error.log 
> /var/log/http/vhost.example.com_access.log
>
>
> but what I want is something like:
>
> /var/log/http/wordpress_vhost.example.com_error.log 
> /var/log/http/wordpress_vhost.example.com_access.log
>
> I've tried things like the example below, but didn't work :(
>
> apache::vhost { 'vhost.example.com':
>   port=> '80',
>   docroot => '/var/www/html/someprettywebsite',
>   serveradmin => 'dontc...@example.com ',
>   access_log_file => "wordpress_${access_log_file}",
> }
>
>
> Any suggestions are welcome,
>
> Denny
>
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to puppet-users...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/0931-1ab3-462a-9441-2ded4a79a879%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/298497a4-6140-4c52-b544-9c2a2c74b58c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] apache::vhost add prefix to logfiles

2014-10-24 Thread Christopher Webber 
Denny,

Which apache module are you using?

— cwebber

> On Oct 24, 2014, at 12:32 AM, Denny  wrote:
> 
> Hi there,
> 
> this is - for sure - pretty easy to solve but I'm a bit stuck right now...
> 
> I want to add a prefix to my apache-vhost access and error logs depending on 
> what kind of application is installed on this vhost
> 
> Right now my config looks something like this:
> 
> apache::vhost { 'vhost.example.com':
>   port=> '80',
>   docroot => '/var/www/html/someprettywebsite',
>   serveradmin => 'dontcal...@example.com',
> }
> 
> which produces two log files: 
> /var/log/http/vhost.example.com_error.log 
> /var/log/http/vhost.example.com_access.log
> 
> 
> but what I want is something like:
> 
> /var/log/http/wordpress_vhost.example.com_error.log 
> /var/log/http/wordpress_vhost.example.com_access.log
> 
> I've tried things like the example below, but didn't work :(
> 
> apache::vhost { 'vhost.example.com':
>   port=> '80',
>   docroot => '/var/www/html/someprettywebsite',
>   serveradmin => 'dontcal...@example.com',
>   access_log_file => "wordpress_${access_log_file}",
> }
> 
> 
> Any suggestions are welcome,
> 
> Denny
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to puppet-users+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/0931-1ab3-462a-9441-2ded4a79a879%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/F2F5CF40-208B-4A8D-9F94-5FB6DF89B27E%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: Puppet development IDE (Geppetto) integrated within Eclipse using puppet & hiera - puppet module

2014-10-24 Thread soumen trivedi 
Apologies for the delay in response.

This module will install eclipse and install Geppetto, Ruby DLTK, etc. as 
features into Eclipse. Required in situations where you are building dev 
environments frequently and want to give dev the capability to start all 
over again if something goes wrong with the environment without having the 
worry to configure the eclipse environment for development. Hope this makes 
sense.

On Thursday, October 9, 2014 8:11:37 PM UTC+1, Juan Andres Ramirez wrote:
>
> THis module is for Eclipse??, install Eclipse and add this module?.
>
> On Thursday, October 9, 2014 3:51:44 PM UTC-3, soumen trivedi wrote:
>>
>> I have created a puppet module that will setup an eclipse platform and 
>> integrate eclipes features using Eclipes p2 director. I have a working 
>> eclipse platform with geppetto, dltk, egit & grep console features 
>> integrated within my development environment. 
>>
>> As eclipse is one of many defacto-standards for IDE based development, I 
>> believe it would be easy for rollout and acceptance within the dev 
>> community.
>>
>> https://github.com/soumentrivedi/puppet-eclipse_platform
>>
>> It would be helpful if you can share some feedback on this module (rspec 
>> & beaker test are in progress and will be updated in due course).
>>
>> This module is based on the 
>> https://forge.puppetlabs.com/runthebusiness/eclipse and re-uses some of 
>> its features and extends the plugin deployment through hiera rather than 
>> static parameter set.
>>
>

-- 
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/714f0961-4053-4c1d-9d6f-199c1ec1beb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] unable to establish connection between agent and master.

2014-10-24 Thread hunkeelin 
I know this question has been asked before in many different variant. I 
read all the post related to the problem but I cannot get agent and master 
talking to each other. I boot up 2 vm via vmwork station both running on 
linuxmint 17.

I'll start this thread by telling what's my /etc/hosts and /etc/hostname in 
client and puppetmaster looks like.

In my client's vm my host name in /etc/hostname looks like the following:

puppetclient

my client's vm hosts in /etc/hosts looks like the following:

127.0.0.1 localhost
127.0.1.1 puppetclient
192.168.75.143 puppetmaster

In my master's vm /etc/hostname looks like the following:

puppetmaster

My master's vm /etc/hosts looks like the following:

127.0.0.1 localhost
127.0.1.1 puppetmaster
192.168.75.144 puppetclient



My /etc/puppet/puppet.conf in my master looks like the following:

[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
rundir=/var/run/puppet
factpath=$vardir/lib/facter
templatedir=$confdir/templates
prerun_command=/etc/puppet/etckeeper-commit-pre
postrun_command=/etc/puppet/etckeeper-commit-post

[master]
# These are needed when the puppetmaster is run by passenger
# and can safely be removed if webrick is used.
ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY

my /etc/puppet/puppet.conf in my client looks like the following: 


[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
rundir=/var/run/puppet
factpath=$vardir/lib/facter
templatedir=$confdir/templates
prerun_command=/etc/puppet/etckeeper-commit-pre
postrun_command=/etc/puppet/etckeeper-commit-post

[master]
# These are needed when the puppetmaster is run by passenger
# and can safely be removed if webrick is used.
ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY

[agent]
server=puppetmaster


I have many variant of puppet.conf during my search and I don't feel like 
posting here. One of the variant is to have `server=puppetmaster`in [main] 
in both my client and master's vm. Anyways, for all the puppet.conf 
variants i tried, my first error when I run `sudo puppet agent --test` is 
always `warning: unable to fetch my node definitoin, but agent run will 
continue:`the error after that is different for each variant of puppet.conf 
I implement. Can anyone tell me the right configuration for my setup?

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/fee20e12-a57e-42f0-b5af-acc644dbdb12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] apache::vhost add prefix to logfiles

2014-10-24 Thread Denny 
Hi there,

this is - for sure - pretty easy to solve but I'm a bit stuck right now...

I want to add a prefix to my apache-vhost access and error logs depending 
on what kind of application is installed on this vhost

Right now my config looks something like this:

apache::vhost { 'vhost.example.com':
  port=> '80',
  docroot => '/var/www/html/someprettywebsite',
  serveradmin => 'dontcal...@example.com',
}

which produces two log files: 
/var/log/http/vhost.example.com_error.log 
/var/log/http/vhost.example.com_access.log


but what I want is something like:

/var/log/http/wordpress_vhost.example.com_error.log 
/var/log/http/wordpress_vhost.example.com_access.log

I've tried things like the example below, but didn't work :(

apache::vhost { 'vhost.example.com':
  port=> '80',
  docroot => '/var/www/html/someprettywebsite',
  serveradmin => 'dontcal...@example.com',
  access_log_file => "wordpress_${access_log_file}",
}


Any suggestions are welcome,

Denny

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/0931-1ab3-462a-9441-2ded4a79a879%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: pull defined type into puppet template?

2014-10-24 Thread james . eckersall 
 Hi Trey,

You could always use the concat module.
https://forge.puppetlabs.com/puppetlabs/concat
Create the global fragment in the class and then use a defined type to 
create a concat fragment for each entry that you want.  You can pass a 
template to each fragment.

-- 
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/54cbab50-bac9-4c53-9ea3-ea395edc26dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.