-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> we´ve upgraded puppet from 0.24.8 to 0.25.5 last week, since then we
> ´re experiencing load/memory (and then swapping) problems. Our setup
> is based on nginx (0.8.20, four worker processes) balancing to five
> puppetmaster instances (servertype mon
On 1 June 2010 14:17, James Turnbull wrote:
> John Warburton wrote:
> >
> > This is nice. Can we go the whole hog and provide all configuration
> > options as facts? Could have a unique name space of something like
> > CONF_variable --> CONF_certname
>
> I though I logged a feature request for t
John Warburton wrote:
>
> This is nice. Can we go the whole hog and provide all configuration
> options as facts? Could have a unique name space of something like
> CONF_variable --> CONF_certname
I though I logged a feature request for this a while ago but damned if I
can find it now - so feel
On 29 May 2010 09:33, Nigel Kersten wrote:
>
> On Fri, May 28, 2010 at 4:19 PM, James Turnbull
> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Nigel Kersten wrote:
>> > I mentioned we had a custom fact for the client certname in IRC the
>> > other day and someone poked fun a
Julian Simpson wrote:
> +1 to any well-formed data about modules. FWIW, there was a discussion
> last year about storing metadata in JSON or YAML format.
And there in fact was a metdata.json file added to modules after Puppet
Camp. The proposed format was pretty much:
{
"license": "GPL2",
Hi,
I am running puppetmaster with storeconfigs. I am also using the
activemq queuing method.
However what i have found from configuring activemq and puppetqd, is
that now in my mysql database the hosts table only has the
puppetmasters ip address listed for all nodes, instead of having each
indiv
These servers only exist in RAM, so when they shutdown, all data is
lost. Julien also said that there's over a hundred of them. If you are
manually signing every time they reboot, you probably won't be diligent
enough to catch an impostor that can use the PXE server. At that point,
you might
On May 31, 2010, at 1:20 PM, Matt Juszczak wrote:
>> You should just be able to get the certificate signed on one of them and
>> then put the whole /var/lib/puppet directory in the image. Remember that
>> with this method, any computer that can access the PXE server can pretend to
>> be one o
You should just be able to get the certificate signed on one of them and
then put the whole /var/lib/puppet directory in the image. Remember
that with this method, any computer that can access the PXE server can
pretend to be one of those servers to the puppetmaster.
It'll also be annoying to
On May 31, 2010, at 6:41 AM, julien wrote:
> The problem is quite simple : if I install puppetd on the image, I
> will end up using the same certificate for 100 different servers with
> different names (the hostname is setup at boot time from dhcp) and I
> guess the puppetmaster won't allow that.
On Mon, May 31, 2010 at 6:41 AM, julien wrote:
> Hi list,
>
> In our platform we have a lot of machines in which the system is a
> single disk image loaded on RAM from PXE.
>
> The problem is quite simple : if I install puppetd on the image, I
> will end up using the same certificate for 100 diff
Hi list,
In our platform we have a lot of machines in which the system is a
single disk image loaded on RAM from PXE.
The problem is quite simple : if I install puppetd on the image, I
will end up using the same certificate for 100 different servers with
different names (the hostname is setup at
+1 to any well-formed data about modules. FWIW, there was a discussion last
year about storing metadata in JSON or YAML format.
J.
On 31 May 2010 03:10, Daniel Pittman wrote:
> "Gabriel - IP Guys" writes:
>
> > Just a idea to float out here among puppet forge users,
> >
> > Can we have a read
You might want to wait for another day or so, as a new major release is just
around the corner :) or you can test the release candidate (which seems to
be quite stable at the moment).
Ohad
On Mon, May 31, 2010 at 10:29 PM, CraftyTech wrote:
> Thanks for the feedback. I'll look it into it immed
Thanks for the feedback. I'll look it into it immediately.
Cheers,
Henry
On May 31, 10:16 am, Ohad Levy wrote:
> Hi,
>
> The Foreman supports inventory and many other features -
> seehttp://theforeman.org/projects/foreman/wiki/Features
>
> Ohad
>
> On Mon, May 31, 2010 at 10:14 PM, CraftyTech
Hi,
The Foreman supports inventory and many other features - see
http://theforeman.org/projects/foreman/wiki/Features
Ohad
On Mon, May 31, 2010 at 10:14 PM, CraftyTech wrote:
> It can be either Dashboard or any other web interface for Puppet. I'd
> be great for reporting on current inventory.
It can be either Dashboard or any other web interface for Puppet. I'd
be great for reporting on current inventory. Has any has gotten this
piece to work? Is it an intended feature, or wishful thinking on my
part?
--
You received this message because you are subscribed to the Google Groups
"Pup
Hey,
I'm exploring puppet-dashboard right now and I want to get the live
aggregation running.
But somehow I'm already failing at the puppet.conf entries ;)
The Dashboard readme says:
### Live report aggregation
To enable report aggregation in Puppet Dashboard, the file `lib/puppet/
puppet_dashboa
Hello,
When I try to revoke certificates from my puppet installation, I get
the following error :
/etc/puppet/ssl# puppetca --revoke all
all
notice: Revoked certificate with serial # Inventory of signed
certificates
err: Could not call revoke: Cannot convert into OpenSSL::BN
And nothing gets del
we´ve upgraded puppet from 0.24.8 to 0.25.5 last week, since then we
´re experiencing load/memory (and then swapping) problems. Our setup
is based on nginx (0.8.20, four worker processes) balancing to five
puppetmaster instances (servertype mongrel, package:rubygem-
mongrel-1.0.1-6.el5), hardware i
20 matches
Mail list logo
