Hi
I want to manage CA certs on Centos boxes and also in JVM's
I found
https://forge.puppet.com/camptocamp/openssl ... not realy what i want
and
https://forge.puppet.com/pcfens/ca_cert
looks better.
If I was to extend to manage java certs.
this is my script
/usr/java/jdk1.6.0_30/bin/keytoo
Hello,
Can we pass parameters like build numbers taken from jenkins to manifest
through mco command.
Thanks,
Megha
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For canaries, we have some 'dev' versions of services, i.e. 'wiki' and
'wikidev'. Because of that, we can both leave the 'dev' versions on a
feature branch if we need to (or disable puppet entirely when we're down in
the nitty gritty and don't want puppet to undo development efforts) AND
have a tie
Another potential management approach I'm exploring...
Because of the complexity of my current situation, where we have multiple
independent internal apps and each one of these has a more-or-less unique
set of operational environments, AND we have common Puppet code that
applies across everything,
I've managed a lot of configs for apps our developers build. At times when
config changes were not backwards compatible I built in the equivalent of
feature flags. I added a Boolean param that controlled if it was on or off,
and built logic into the ERB/EPP template that used it. Then I could
contr
Passing noop => true to a class does not work as you expected.
This is one of that moments where you treat a class like a resource,
but it is not, unfortunately.
Take a look at this noop() function:
https://github.com/nrvale0/deploy-to-noop-part-1/tree/master/puppet/environments/production/modul
It depends on what you mean by slowly rolling out the change. Do you
control the openssh version globally (all machines get same version)? Or is
the version set per *operational* environment (dev machines have newer
version than prod machines, etc)?
If you set the version globally, and you want to
Last time I bump this email :/
Anyone has any idea?
Thanks
Julio
On Tuesday, August 16, 2016 at 6:29:22 PM UTC-5, Julio Guevara wrote:
>
> All puppet agent have on puppet.conf
> noop = true
>
> I need to make sure that some classes (like the class that configure the
> puppet-agents or mcollectiv
I think there are so many ways to do A/B deployments that it's probably not
wise to codify that into your Puppet environments layout. Here's a few
examples of how:
* Use DNS/Load Balancer rules/etc to control which puppet masters different
agents connect to. Some of the masters have a different de
basemodulepath helps here:
https://docs.puppet.com/puppet/latest/reference/configuration.html#basemodulepath
In puppet.conf:
basemodulepath = /etc/puppetlabs/code/environments/common/modules
If there's something that environments don't need to track specially (ntp and
mcollective modules come
Hi everyone.
I just put in production a new server with puppet 4.5 from puppetlabs
repository and the puppetdb (also from puppetlabs).
Almost all my linux server run with vserver (a virtualisation system)
All my client run puppet 3.x (from the OS) and when I trying to upgrade them to
puppet-agen
11 matches
Mail list logo
