[Puppet Users] Re: Providing hiera with module data
Hi, I have this problem: Hiera only looks inside "data/common.yaml"-file, which is in my module-directory. When i put other data into another yaml file "data/example.yaml", then Puppet doesn't find that data. What's the cause for this problem? -- 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/b3e1b520-f883-4bac-a887-c6bdd6dc5cac%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: puppet module search using an HTTP proxy
Maybe something as simple as using httpS? The puppet module face requires https when downloading I believe. Try 'export https_proxy=my.proxy.com' I hope this helps. Stephen -- 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/d08c7b5f-fb55-4d62-ab50-43557be24169%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] install puppet modules behind a proxy
Hi I installed puppet on centos for the first time yesterday. the default installation via YUM didnt install any modules i am using apache and mysql for the webserver and database. my question is there no way to install the modules if i am behind a proxy? [root@puppet ~]# puppet --version 3.3.2 [root@puppet conf.d]# cat /etc/*release* CentOS release 6.4 (Final) CentOS release 6.4 (Final) CentOS release 6.4 (Final) cpe:/o:centos:linux:6:GA [root@puppet conf.d]# At a number of places (forums) I find that it is not supported. I also installed and configured puppet dashboard which is running on port 3000. I am curious to know what runs on port 8140? The document root specified on the file puppetmaster.conf [root@puppet conf.d]# ll /usr/share/puppet/rack/puppetmasterd/public/ total 0 is empty. If I use *dashboard* do I still need the default puppet web page? [root@puppet ~]# cd /etc/httpd/conf.d/ [root@puppet conf.d]# ll total 36 -rw-r--r--. 1 root root 4129 Nov 29 15:18 dashboard-vhost.conf -rw-r--r--. 1 root root 1932 Nov 29 20:36 puppetmaster.conf -rw-r--r--. 1 root root 392 Aug 13 23:00 README -rw-r--r--. 1 root root 21 Nov 29 15:01 sample.html -rw-r--r--. 1 root root 9473 Aug 2 17:29 ssl.conf -rw-r--r--. 1 root root 299 Aug 2 17:29 welcome.conf -- 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/0b0703ca-7fa3-4862-9e66-dd2fa19d5a7e%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Unable to specify hierarchy for data-in-modules
Hi MM, Can you tell me how you succeeded in using hiera-data, which is stored in the individual module-directories? 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/65b8bae1-f0e6-429b-a7d7-e6ae8d5ee468%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Providing hiera with module data
Hiera-2? I can't find any information on the puppet-website about Hiera-2? What do you mean with Hiera-2? -- 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/e046b0d0-df25-413d-9dac-1c6eb253de48%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Providing hiera with module data
That doesn't help me :(. The page says: Can I set top level scope parameters using data in modules? No. Not yet at least. Isn't there a simple way to solve this problem? -- 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/3bf47459-699c-4ddf-987b-dd06b72d21a9%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Providing hiera with module data
Start here: http://docs.puppetlabs.com/puppet/3/reference/release_notes.html#data-in-modules Which leads you here: https://github.com/puppetlabs/armatures/blob/master/arm-9.data_in_modules/index.md On Nov 30, 2013, at 9:42 AM, Steven Jonthen wrote: > Hi guys, > > I don't know how to solve this: > I want ".yaml"-files in each module's "/data"-directory. These .yaml-files > should contain data, which Hiera sould pass to the module's manifests. > How can I do that? I'm using Puppet 3.3.1 > > 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/1ad11ee0-3e8c-4473-871a-c6bb0cc8bf02%40googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- 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/E46C8F86-1BDA-4EC5-B51B-2E2021D6C105%40comcast.net. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Providing hiera with module data
Hi guys, I don't know how to solve this: I want ".yaml"-files in each module's "/data"-directory. These .yaml-files should contain data, which Hiera sould pass to the module's manifests. How can I do that? I'm using Puppet 3.3.1 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/1ad11ee0-3e8c-4473-871a-c6bb0cc8bf02%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] puppetlabs-firewall scope
Hi Louis,
Did you ever find a workaround for this problem? I'm experiencing the same
thing, where the existing rules are not all purged at once so it causes the
other resources to time out. This can last for up to 10 minutes so it can
cause some problems.
Jeff
On Sunday, December 9, 2012 7:22:58 AM UTC+11, Lofic wrote:
>
> Thanks a lot. Indeed, in that way it leaves my untargeted nodes alone.
> And I feel it's cleaner than putting things in the site.pp.
>
> However I still have one little problem : at first application on some fw
> rules on a node with puppet, the purge of preexisting rules is slow,
> blocking the network temporarily.
>
> Hopefully it comes back after a while.
>
> I don't have this annoyance if I 'iptables -F' first.
>
> See an example below.
>
> I can work with that but if you have a workaround you're welcome.
>
> Louis Coilliot
>
> Info: Applying configuration version '1354997226'
> /Firewall[ fe701ab7ca74bd49f13b9f0ab39f3254]/ensure: removed
> /Firewall[ a627067f779aaa7406fa9062efa4550e]/ensure: removed
> /Firewall[ 49bcd611c61bdd18b235cea46ef04fae]/ensure: removed
> Error: /File[nagios.vim]: Could not evaluate: Connection timed out -
> connect(2) Could not retrieve file metadata for
> puppet:///modules/nagios/nagios.vim: Connection timed out - connect(2)
> Error: /File[nagiosvim-install.sh]: Could not evaluate: Connection timed
> out - connect(2) Could not retrieve file metadata for
> puppet:///modules/nagios/nagiosvim-install.sh: Connection timed out -
> connect(2)
> Error: /File[/etc/vimrc]: Could not evaluate: Connection timed out -
> connect(2) Could not retrieve file metadata for
> puppet:///modules/vim/vimrc: Connection timed out - connect(2)
> /Firewall[ b205c9394b2980936dac53f8b62e38e7]/ensure: removed
> /Firewall[000 accept all icmp]/ensure: created
> Info: /Firewall[000 accept all icmp]: Scheduling refresh of
> Exec[persist-firewall]
> /Firewall[ d53829245128968bfa101d5214694702]/ensure: removed
> /Firewall[001 accept all to lo interface]/ensure: created
> Info: /Firewall[001 accept all to lo interface]: Scheduling refresh of
> Exec[persist-firewall]
> /Firewall[002 accept related established rules]/ensure: created
> Info: /Firewall[002 accept related established rules]: Scheduling refresh
> of Exec[persist-firewall]
> /Firewall[003 accept SSH]/ensure: created
> Info: /Firewall[003 accept SSH]: Scheduling refresh of
> Exec[persist-firewall]
> /Firewall[999 drop all on INPUT eventually]/ensure: created
> Info: /Firewall[999 drop all on INPUT eventually]: Scheduling refresh of
> Exec[persist-firewall]
> /Firewall[999 drop all on FORWARD eventually]/ensure: created
> Info: /Firewall[999 drop all on FORWARD eventually]: Scheduling refresh of
> Exec[persist-firewall]
> /Stage[main]/Firewall/Exec[persist-firewall]: Triggered 'refresh' from 6
> events
> Finished catalog run in 196.45 seconds
>
>
> Le 07/12/2012 20:34, Shawn Foley a écrit :
>
> I created a firewall module. In firewall/manifests/init.pp i have the
> following.
>
> class firewall {
>
>## Always persist firewall rules
> exec { 'persist-firewall':
> command => '/sbin/iptables-save > /etc/sysconfig/iptables',
> refreshonly => true,
> }
>
>## These defaults ensure that the persistence command is executed after
> ## every change to the firewall, and that pre & post classes are run in
> the
> ## right order to avoid potentially locking you out of your box during
> the
> ## first puppet run.
> Firewall {
> notify => Exec['persist-firewall'],
> before => Class['firewall::post'],
> require => Class['firewall::pre'],
> }
> Firewallchain {
> notify => Exec['persist-firewall'],
> }
>
>## Purge unmanaged firewall resources
> ##
> ## This will clear any existing rules, and make sure that only rules
> ## defined in puppet exist on the machine
> resources { 'firewall': purge => true }
>
>## include the pre and post modules
> include firewall::pre
> include firewall::post
> }
>
> Then you just "include firewall"
>
>
> Shawn Foley
> 425.281.0182
>
>
> On Tue, Dec 4, 2012 at 12:36 PM, Louis Coilliot
>
> > wrote:
>
>> Hello,
>>
>> I can't figure out how I can use the module puppetlabs-firewall only
>> for some targeted nodes.
>>
>> If I put :
>>
>> resources { "firewall": purge => true }
>>
>> in top scope (i.e. site.pp),
>>
>> then all the firewall rules on all my nodes are purged. Even for nodes
>> for which I don't apply any module containing specific firewall { ...
>> } resources.
>>
>> If I put it in a module (i.e. myfw ), then for all nodes where I
>> apply a module containing firewall resources, I got a mix of the
>> previous rules (defined locally with the OS) and the new ones provided
>> with puppet.
>>
>> Did I miss something or is it the expected behaviour ?
>>
>> If this is expected, is there a workaround to apply the purge of the
>> rules only for some nodes where I want to apply specific fir
