I have questions about Puppet's scalability.
I am looking for info about how one might have multiple cooperating
PuppetMasters on a network.
I have found old links that talk about merging Puppet and Func, but they all
seem out of date.
My questions go more toward delegated puppet-mastering rath
[ CC'ed to augeas-devel, more on-topic for ruby-augeas build errors ]
On 18/01/12 04:45, LawrieC wrote:
> Thanks for the tip Aaron.
>
> I have stuck with the platform RPMs as indicated earlier in the
> thread. I could not find a ruby-augeas SLED platform RPM.
I'm not familiar with the SUSE commu
- Original Message -
>
>
> On Jan 19, 11:01 am, "R.I.Pienaar" wrote:
> > - Original Message -
> > > Defined() doesn't suck! It's a 100% reliable way to check what
> > > classes and defined types are available to the autoloader. I
> > > challenge anyone
> > > to find me an examp
I use defined every so often so I would be sad if it was removed, it's
handy for certain things of things:
common/foreman_proxy/manifests/params.pp: if
defined(Class['puppet::server::ca']) {
common/foreman_proxy/manifests/params.pp: } elsif
defined(Class['puppet::server']) {
common/foreman_proxy
On Jan 19, 11:01 am, "R.I.Pienaar" wrote:
> - Original Message -
> > Defined() doesn't suck! It's a 100% reliable way to check what
> > classes and defined types are available to the autoloader. I challenge
> > anyone
> > to find me an example of this usage that fails.
>
> can you give
- Original Message -
> Defined() doesn't suck! It's a 100% reliable way to check what
> classes and defined types are available to the autoloader. I challenge anyone
> to find me an example of this usage that fails.
can you give an example of this use case pls?
--
You received this mes
Defined() doesn't suck! It's a 100% reliable way to check what classes
and defined types are available to the autoloader. I challenge anyone
to find me an example of this usage that fails.
But trying to use it to see whether a specific resource instance has
been declared is pure madness and must b
+1 to ditch it. As the other thread said well: use of defined() is
only done in badly designed code. Getting rid of it will force people
to use better designs.
cheers,
Walter Heck
On Thu, Jan 19, 2012 at 19:19, R.I.Pienaar wrote:
>
>
> - Original Message -
>> I'm looking for strong opin
- Original Message -
> I'm looking for strong opinions on whether we should or shouldn't
> deprecate the defined() function for Telly, the next major Puppet
> release this year.
First choice would be to make it reliable, that seems unlikely though
+1, I'd also make the scope.classes var
I'm looking for strong opinions on whether we should or shouldn't deprecate
the defined() function for Telly, the next major Puppet release this year.
jcbollinger put it quite well in another thread:
"Use of the "defined" function introduces a parse-order dependency, and the
additional work you n
On Wed, Jan 18, 2012 at 3:52 AM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:
>
> Is there a good reason that this function is even retained in recent
> versions of puppet? I have yet to encounter an instance where it can be
> used cleanly.
>
I'll start another thread about this, but I'd
So recently I deployed some new puppet code in our environment and
noticed CPU utilization on our puppetmasters went up a bit. This lead
me to wonder what exactly did I add to cause catalog compiling to
utilize more CPU? I was wondering if there is a way to check how long
different parts in a rec
If you omit the macaddress in the ifcfg-eth0 file, it should work properly
if there are no persistent network configs.
On Redhat, the 70-persistent-net.rules assigns a specific ethx device to a
specific nic. Your 'ignoring' messages strongly point in the direction of
such a mechanism.
So if yo
On Jan 18, 5:52 am, Felix Frank
wrote:
> Hi,
>
> On 01/17/2012 04:11 PM, jcbollinger wrote:
>
> > The first is simpler only if you get lucky, and you don't intend to
> > modify your manifests ever again.
>
> basically correct, but you can even play it safe: You must make sure
> each and every in
On Jan 19, 2:33 am, Antidot SAS wrote:
> Thx you very much this helps a lot.
>
> Just have a last point unclear from your example 4. As you said for example
> 1: "Puppet will ensure that class_B's definition is evaluated before
> anything following the "include" line inside class_A's definition"
Thx you very much this helps a lot.
Just have a last point unclear from your example 4. As you said for example
1: "Puppet will ensure that class_B's definition is evaluated before
anything following the "include" line inside class_A's definition" so
what's the use of declaring: Class['class_B'] -
16 matches
Mail list logo
