Hi folks.
I'm curious what approaches you take towards making sure the puppet tree is
consistent across distributed compile masters? In PE this would be code
manager's job, I believe. What do the FOSS folks use?
I was contemplating using zookeeper for this.
-G
--
Geoff Galitz, Systems Eng
I've seen a few ways of doing this:
- Running lsyncd to watch for changes to code on the MoM
- Rsync task on demand when the master is updated, maybe with something
like incrond or just with scripting or Jenkins tasks
- The R10K mco task from acidprime/r10k
https://github.com/acidprime/r10k#mcol
Cool.. I'm specifically interested in knowing how people deal with compile
servers that do not update their local version of the puppet tree properly
and how to prevent them serving stale or broken catalogs.
-G
On Tue, Jun 14, 2016 at 1:42 PM, Peter M Souter wrote:
> I've seen a few ways of
Most implementations make use of config_version setting in environment.conf (or
globally in puppet.conf) to identify systems with outdated puppet code
On 14 Jun 2016, at 13:50, Geoff Galitz wrote:
>
>
> Cool.. I'm specifically interested in knowing how people deal with compile
> servers tha
We push r10k runs via consul execs from Jenkins, and after and only after a
successful update, invalidate the environment cache(for the given
environment), so even if a deploy fails , the master(s) will keep serving
the "old" version as opposed to an incomplete deploy.
On Tue, Jun 14, 2016 at 7:52
On Monday, June 13, 2016 at 7:45:12 AM UTC-5, Matt Larson wrote:
>
> Eric et al,
>
> Thanks again for your help with this! I realize how crazy it may seem to
> want to rebuild from source. My company has become so paranoid of open
> source software due to recent events,
>
At the risk of tak
So I'm trying to use Ansible to automate the process of re-enrolling all my
systems after the upgrade from 3.8.6 to 4.3, and many (though not all) of
my clients are reporting thusly:
# *rpm -rf /var/lib/puppet/ssl /etc/puppet/ssl /etc/puppetlabs/puppet/ssl*
# *ssh puppet puppet cert list host.in
To your specific issue, it looks like your agent's CA cert doesn't match the
issuer of the new puppetmaster's CA cert ("unable to get local issuer
certificate"). If I recall correctly, an agent without a CA cert will download
one from the puppetmaster the first time and thereafter check it. You
I did the following (which I'd done before) and it seems to have helped:
# puppet resource service upppetserver ensure=stopped
# rm -rf /etc/puppetlabs/puppet/ssl
# puppet cert list -a
# puppet master --no-daemonize --verbose
^C
# puppet resource servcie puppetserver ensure=running
#
On Tuesday
Well, I _thought_ it helped. Many systems are connecting fine, others are
still getting a different ca.pem file. I suspect for some reason the server
is getting its copy overwritten somehow. I'm going to keep an eye on it now.
On Tuesday, June 14, 2016 at 10:07:13 AM UTC-4, Bret Wortman wrote:
>
Hi,
Is there a way to access a puppet node's facts in a report processor?
We have nodes which are part of auto scaling groups in AWS, so there are,
several nodes which are all the same 'type'. We expose this type as a fact
on the nodes themselves, and I would like to use the type in a report
p
You're very welcome Brian!
I plan on publishing an update to the ibm_installation_manager module in
the next few days to address an idempotency issue. As for the websphere
module, we are hoping to receive some valuable feedback on the 0.2.0
release we just published to the
Forge(https://forge.
I have successfully built the AIO package using the puppetlabs/puppet-agent
[1] repository from source. I did this because I needed ppc64le packages
which puppetlabs does not provide. This isn't the easiest process, but not
terribly difficult if you are comfortable building software.
I wanted t
Puppet Agent 1.5.2 is now available. This is a bugfix release that includes
and updated Puppet version with a handful of fixes; no other components are
update from the Puppet Agent 1.5.1 release a couple of weeks ago.
Check out the full release notes here:
https://docs.puppet.com/puppet/latest/ref
On Tue, 17 May 2016, Eric Sorenson wrote:
Hi Dan, this is a good and timely post.
I apologize for the lack of response. Health issues have taken a front
seat for a while.
I'm working on some related issues regarding Puppet's CA that may help
you out. Your thinking on this is roughly corre
15 matches
Mail list logo
