Here is the code that we use to pull Auto Scaling messages off an SQS queue
and add/remove the respective nodes to autosign.conf and sign or clean up
their certificates.
https://gist.github.com/sigmaris/bda78c1857034031eb76
It's copied and pasted out of a larger application that handles various
On Tuesday, 27 May 2014 12:56:05 UTC+1, Jeremy wrote:
>
> This actually sounds like a useful tool. Is this something you're (or
> would) consider releasing as OSS for others to make use of?
>
> I've put my autosign script up on a GitHub gist and at least one other
> has considered it useful so
> Am I missing a configuration option in the manual to somehow disable SSL
> certificate validation? Does everybody add a cron job to their puppet
> master to stop the puppetmaster daemon and blow away its SSL directory then
> restart it at exactly 12:00AM every day, and the same on the instan
On Friday, May 3, 2013 4:50:38 PM UTC+1, Martijn wrote:
>
> Dear list,
>
> When I bootstrap a new EC2 instance from a base Ubuntu 12.04 LTS image I
> use cloud-init to install the puppet-agent via apt, write a minimal
> puppet.conf and start puppet. Ubuntu 12.04 comes with puppet 2.7.*, and I'd
On Monday, April 22, 2013 12:31:57 AM UTC+1, Shiva Narayanaswamy wrote:
>
> My setup has an EC2 autoscaling group of clustered glassfish application
> servers. Each glassfish instance will register itself with a DAS (Domain
> Administration Server) to become a member of the cluster, and deregiste
I've filed a bug report http://projects.puppetlabs.com/issues/19884 with
some info on the OpenJDK / Ruby / OpenSSL versions we're using.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails fr
On Friday, March 22, 2013 10:47:15 AM UTC, Russell Parsloe wrote:
> I'm running PuppetDB 1.1.1 with Puppet 3.1, both on the same server.
> Occasionally nodes report this error:
>
> err: Could not retrieve catalog from remote server: Error 400 on SERVER:
>> Could not retrieve resources from the P
Using puppet 3.0.1 I ran into an odd scoping problem - I've got a class
called 'lettuce' in a module named testtools, like this:
class testtools::lettuce {
require pip
Package {
provider => pip,
}
package {
"lettuce":
ensure => installed;
"let
On Tuesday, October 9, 2012 10:24:53 AM UTC+1, Fran RodrÃguez wrote:
> Yes, it does. This occurs when change apt module for the puppetlabs-apt.
> Maybe is a issue with environments, im trying to figure out what is
> happening, and like the log said the module stdlib which provide the anchor
> t
On Thursday, October 4, 2012 9:01:58 PM UTC+1, Jeff McCune wrote:
>
> On Wed, Oct 3, 2012 at 6:31 AM, Hugh Cole-Baker
> >
> wrote:
> > After upgrading to Puppet 3.0.0 it seems that puppet doc is no longer
> > producing documentation from my modules / manifests.
After upgrading to Puppet 3.0.0 it seems that puppet doc is no longer
producing documentation from my modules / manifests.
I have a setup with two environments in
/etc/puppet/environments/[production, testing], and I'm running the
following command to generate the docs:
puppet doc --all --mode
11 matches
Mail list logo
