Hello everyone,
I haven't seen a Puppet module to create a windows service so I've hacked
something together as a Defined Type instead of a Parameterized Class
(mainly because I want to call it for multiple services) and I would
appreciate feedback and suggestions for improvements. I'm having
Hello everyone,
I hadn't noticed until recently but a large % of host reports are not
getting into PuppetDB and I looking for ways to determine what the cause
is. I could see an all or nothing but not this. I'm not worried about the
data for those hosts but I'm un-sure what steps to take. I
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
&
ns_in')
environment_timeout = 0
modulepath = /etc/puppet/environments/test/modules:
/etc/puppet/environments/test/site/modules
environment = test
environmentpath = /etc/puppet/environments
disable_per_environment_manifest = false
On Friday, May 8, 2015 at 2:23:27 PM UTC-5, Jim Miller wrote:
Still wrestling with this. Puppet is now seeing 'part' of the module paths
but not all of them, one thing I had to change was using an absolute path
and not '$confdir' and it's not using the correct site.pp file
"non-prod_site.pp"
[ ~ ]# puppet config print --environment test |grep env
environ
remote server: Error 400 on SERVER:
Could not find class mywebsite::profiles::web::site_web_dev for
. on node
Again,
Any suggestions would be _greatly_ appreciated.
Thanks,
Jim
On Friday, May 8, 2015 at 2:23:27 PM UTC-5, Jim Miller wrote:
>
> Hi all,
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
t "999 drop all OUTPUT" -j DROP
-A dns_out -p tcp -m comment --comment "024 dns_out" -j LOG --log-prefix
"dns_out"
-A dns_out -p tcp -m comment --comment "025 dns_out" -j ACCEPT
-A ssh_in -p tcp -m comment --comment "009 ssh_in" -j LOG --log-prefix
hain => 'OUTPUT', outiface => 'eth0',
> destination => '10.x8.x0.x5', proto => 'tcp', state => 'NEW', port => '53',
> action => 'accept', }
>
> Jeff
>
> On 12/11/2013 10:24 PM, Jim Mi
We're testing out the Puppetlabs-Firewall module. And it seems I'm either
missing something fundamental or Logging/Accpet works/doesn't work in an
irregular way. I would be most grateful for some input.
*COMMON:*
firewall { '002 accept related established rules INPUT': proto => 'all',
state
Hello all,
We are beginning to implement the Puppetlabs-firewall module and have not
been able to implement a final LOG, DROP rule (our standard policy is LOG
and DROP everything which isn't explicitly allowed IN or OUT) in post.pp.
Has anyone been able to implement a post.pp which does a LOG
I am using example42s squid module
https://github.com/example42/puppet-modules/tree/master/squid, and trying
to define certain user variable at the puppet/manifest/nodes.pp level
This is the first module of their's I've tried, I've read over their
documentation and FAQ and for the life of me
12 matches
Mail list logo
