On 10 Nov 2015, at 20:33, Arnau wrote:
> Hi,
>
> >
> > I see two possible entry points for your problem:
> >
> > 1. environment specific hiera data
> > according to your hiera.yaml file you have hieradata per environment.
> > can you please cross check that the
Hi Martin,
> The only env where it's defined is the one I'm using.
>
> Maybe that is the reason.
>
Sorry, but I don't see why this could be the reason. Could you please
explain it to me?
> Can you please have a look at the nagios::client code and check whether
> there is a default set for
Hi John,
2015-11-11 15:43 GMT+01:00 jcbollinger :
first of all, let me thanks for your answer,
[...]
First off, you talk about how you are using Hiera to set *variables* of
> class ::nagios::client, but that can be true only inasmuch as class
> *parameters* are a
On Wednesday, November 11, 2015 at 7:21:44 AM UTC-6, Arnau wrote:
>
> Change ::selinux to false (append selinux=0 in the kernel line) and
> everything works as expected.
>
>
> still (very) confused
>
>
It is plausible that disabling selinux on the machine would result in
selinux-related
Dear Puppet users,
for those of you using *Puppet *for configuration management on top of *IaaS
*the extension of the open source
multi-cloud modelling and an run-time tool *CloudML *may be of interest.
CloudML lets you define a *deployment model* for your applications
consisting of
-
Greetings,
I'm getting ready to spin up a puppet 3.7 environment (Debian Jessie)
and was reading about the top level $facts hash that holds the
client's facts. The puppet documentation states that it is off by
default in the open source version [1].
"Drawbacks: Only works with Puppet 3.5 or
On Tuesday, November 10, 2015 at 7:19:49 AM UTC-6, Arnau wrote:
> ** Hiera works and returns the expected values:*
>
> # hiera -c /etc/puppet/hiera.yaml -d classes environment=basic_conf
> clientcert=XX
> DEBUG: Tue Nov 10 14:14:39 +0100 2015: Hiera YAML backend starting
> DEBUG: Tue Nov 10
On Wed, Nov 11, 2015 at 9:42 AM, Matt Zagrabelny wrote:
> Greetings,
>
> I'm getting ready to spin up a puppet 3.7 environment (Debian Jessie)
> and was reading about the top level $facts hash that holds the
> client's facts. The puppet documentation states that it is off by
>
Hi Martin,
Thanks for that. It worked a treat.
I just did some simple validation in the end.
yaml_object = YAML.load(content)
expect(yaml_object.length).to be > 0
I validate the content elsewhere but this is just an a basic check that
it's able to parse it. I have been using regexp
Change ::selinux to false (append selinux=0 in the kernel line) and
everything works as expected.
still (very) confused
Arnau
2015-11-11 12:37 GMT+01:00 Arnau :
> Hi Martin,
>
>
> > The only env where it's defined is the one I'm using.
>>
>> Maybe that is the reason.
Omen Wild writes:
> Any idea what the timeframe for the 3.8.4 packages is? We have been using
> OpenCSW for a while, but we have a Puppet 4 migration planned for any day
> now. Having a 3.8.4 package would prevent me from having to move to GEM
> based Puppet for our Solaris(ish)
11 matches
Mail list logo