On Friday, 15 February 2019 21:45:00 UTC, Michelle Fredette wrote:
>
> We regret any disruption that this change causes, and if you’re having
> trouble finding something you need, please email d...@puppet.com
> and we will help you find it.
>
Except that when I DID email to d...@puppet.com i
On Thursday, 31 January 2019 12:48:30 UTC, Henrik Lindberg wrote:
>
>
> If you really must keep the CSV format, you can write your own function
> that you use with hiera 5. It is quite simple. I show examples and
> explain how hiera 5 works in this video:
>
> https://www.slideshare.net/PuppetL
On Wednesday, 30 January 2019 00:17:07 UTC, Ben Ford wrote:
>
> Your simplest and most straightforward upgrade path would be to port the
> CSV file to a common.yaml file and then switch to using lookup() with
> hieradata.
>
Thanks, Ben. That worked, and wasn't too painful.
Now all I have to
I'm looking at the possibility of moving our Puppet manifests from 3.8 to
Something More Recent (i.e. 6.1)
We have one big CSV file for (mostly) encrypted passwords and the like.
And our existing manifests use extlookup to extract the relevant entries,
via calls like pw =
How should I replace
I'm using Puppet (3.8) to set up installations of a system for different
clients.
We have a number of servers running "live" installations,
and others running corresponding development installations.
There is a module for the system, and each node has a separate
instance for each client that th
On 22 June 2017 at 14:42, jcbollinger wrote:
>
>
> On Thursday, June 22, 2017 at 5:26:41 AM UTC-5, Robert Inder wrote:
>
> I don't understand why the behavior you describe occurs, but I also don't
> understand why you are trying to set the owner of the link in the
3 is EOL.
>
If the issue is with puppet itself, rather than perms, it's going to
> require an upgrade to fix.
>
Well, an upgrade MIGHT fix it
But I guess that upgrading is something I'm going to have to think about
some time...
Unlikely, but wanted to make sure
I'm hoping someone can help me diagnose a problem with
Puppet version 3.8.7 running on CentOS 6.4.
I have a couple of servers with a total of 43 web-accessed software
systems, each with its own unix user.
These installations are all created from scratch by Puppet, and then
the appropriate vers
On Saturday, 21 March 2015 22:08:34 UTC, Christopher Wood wrote:
>
> On Sat, Mar 21, 2015 at 12:08:07PM -0700, Robert Inder wrote:
>
:
:
> >This is not quite the behaviour I want.
> >
> >But how can I stop it?
>
> In your place I'd pro
On Friday, 20 March 2015 08:18:15 UTC, jamese wrote:
>
> Try running puppet with "--debug" and "--evaltrace" to see where it's
> taking the time.
>
Ah! As before, the evaltrace for the empty node definition lists a handful
of things
being evaluated in negligible times.
But that out put is b
We have about a dozen CentOS 6 servers being managed by puppet 3.7.4, using
puppet
apply with locally stored modules and node definition.
Recently, performance on one of them has collapsed to hopeless levels, and
I really don't know how to diagnose the problem.
Puppet used to take 5 - 10 min
I've taken over a puppet 2.7 setup that does not use a puppet master - we
just use puppet-apply on locally stored manifests. I'm trying to
re-organise our manifests, and want to avoid changing things
unintentionally.
Since manifests are compiled into a catalog before they are applied, I'm
h
12 matches
Mail list logo
