Hi Peter!
On Thursday, June 25, 2015 at 9:45:51 PM UTC-7, Peter Huene wrote:
>
> Hi Ken!
>
> On Thu, Jun 25, 2015 at 11:53 AM, Ken Bowley > wrote:
>
>> While testing puppet 4 to see if it was ready for production (still not),
>> I now get to deal with the new Fa
While testing puppet 4 to see if it was ready for production (still not), I
now get to deal with the new Facter 3.0.
Hopefully ruby based facter won't be totally abandoned, since the C++ based
version is going to be an annoyance on non-PL supported systems.
The first thing I noticed is that a c
le wrote:
> > On 6/22/15, 3:08 PM, "Vince Skahan" >
> wrote:
> >
> >> On Thursday, June 18, 2015 at 4:18:37 PM UTC-7, Ken Bowley wrote:
> >>> This is better than what is currently being used, but I'm strongly in
> the AIO
> >>&g
This is better than what is currently being used, but I'm strongly in the
AIO idea to be stupid. Split it into multiple packages and use proper
dependencies like every other sane packaging system has done for a long,
long time.
If all you do is bump the version of facter, then only have me dow
I managed to get it to work by editing tagmail.rb and hard coding any of
the areas where it tries to use Puppet[:*] config options that don't exist
and can not work with puppet 4.1.
On Thursday, June 11, 2015 at 1:30:52 PM UTC-7, Ken Bowley wrote:
>
> While I ignore puppet 4's b
While I ignore puppet 4's brain-dead stupid fact behaviour when using
puppetdb, I'm on to the issue of getting puppet to mail reports when
something changes on a node.
Since the built-in tagmail is no longer an option, I decided to look at the
tagmail module. As far as I can tell, the puppetla
I'm running puppet 4.1.0 in a test VM in preparation for an eventual
migration from 3.8.1. I've recently run into an issue that seems to be
mentioned in https://tickets.puppetlabs.com/browse/PDB-949
Here's a little back info; My VM is a copy of our production puppet
master, but with 4.1.0 an
een offline and have older versions of puppet that need to be
upgraded.
On Friday, April 17, 2015 at 4:25:59 PM UTC-7, Kylo Ginsberg wrote:
>
> On Fri, Apr 17, 2015 at 3:12 PM, Ken Bowley > wrote:
>
>> Puppet 4 needs a lot of new directories in order to even attempt to run.
&g
;t involve firing up a new puppet 4 server
to run alongside the puppet 3 server.
On Friday, April 17, 2015 at 3:04:51 PM UTC-7, Tim Skirvin wrote:
>
> Ken Bowley > writes:
>
> > We've been using Puppet since the 0.24 days, and it's always been fairly
> > sim
We've been using Puppet since the 0.24 days, and it's always been fairly
simple to add in a new system.
Do a base install (Linux or Mac OS X)
Install Ruby if Linux
gem install puppet
run puppet
sign the cert on the puppetmaster
let puppet take care of everything else.
This was easy, easy to docu
I've been testing puppet 0.25.x in a two system test environment for a
while now, just waiting for the day that I could deploy into
production (currently 0.24.8). Yesterday I applied your patch to
0.25.1 and finally had things working! Here is my setup:
System A:
Centos 5.4
httpd-2.2.3-31.e
I had an init script that was exhibiting the same behavior of only
creating the start links, but after adding a properly formated BEGIN
INIT INFO section to the header of the init script, the kill links
were also created when I ran "chkconfig on", so the lesson
here should be to format the header
12 matches
Mail list logo
