I had the same problem and just fixed with Patrick solution. I just wanted
to say thanks everybody.
--
Att,
Cesar Avalos
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To
Cesar Avalos ha scritto:
I had the same problem and just fixed with Patrick solution. I just
wanted to say thanks everybody.
Hello
Just as a round-up, You may want to add a [puppetca] section to your
puppet.conf, setting the same ssldir as you did in [puppetmasterd], so
that you don't have to
Hello
Thanks to the ones who replied.
Patrick Mohr ha scritto:
Basically, the puppet packages you are using (and I suspect most
others) assume that the client and the server on a given machine are
part of the same PKI. It also might be assuming a couple of other
things, but my experiments
On Wed, Jul 14, 2010 at 8:50 PM, Marco Marongiu brontoli...@gmail.comwrote:
Hello
I'm not sure if you're suggesting to use a single machine to host a CA
for the whole infrastructure. In case, would that scale?
It would scale, but it would be a single point of failure for adding new
puppet
Ohad Levy ha scritto:
On Wed, Jul 14, 2010 at 8:50 PM, Marco Marongiu brontoli...@gmail.com
mailto:brontoli...@gmail.com wrote:
Hello
I'm not sure if you're suggesting to use a single machine to host a CA
for the whole infrastructure. In case, would that scale?
It
Dear puppeteers
I am trying to build a tree hierarchy of puppetmasters. The architecture
is aimed to distribute the load among a number of datacenters, while
keeping the puppetmasters in sync by means of puppet itself.
The architecture I am trying to build is:
- one main puppetmaster;
- many
On Jul 13, 2010, at 6:54 AM, Marco Marongiu wrote:
Dear puppeteers
I am trying to build a tree hierarchy of puppetmasters. The architecture
is aimed to distribute the load among a number of datacenters, while
keeping the puppetmasters in sync by means of puppet itself.
The architecture
