On Thu, Sep 11, 2008 at 12:13 PM, Johnny Tan <[EMAIL PROTECTED]> wrote:
>
> I'm using 3 environments in puppet. Each environment points
> to different IPs and/or hostnames for things ranging from
> nfs mounts to mail servers, etc.
>
> Ideally, I'd like to use the exact same file in each
> environm
I worked up http://reductivelabs.com/trac/puppet/wiki/Recipes/HostgroupFact to
do a similar task. It may be useful to you.
--
Mike Renfro / R&D Engineer, Center for Manufacturing Research
931 372-3601 / Tennessee Technological University
-Original Message-
From: Kenton Brede <[EMAIL PR
I'm using 3 environments in puppet. Each environment points
to different IPs and/or hostnames for things ranging from
nfs mounts to mail servers, etc.
Ideally, I'd like to use the exact same file in each
environment, where the IPs/hostnames/etc get called via a
variable.
Is there a best prac
2008/9/11 josh <[EMAIL PROTECTED]>:
> On another note, I do know the IP addresses of the boxes, can I use
> IP's in the nodes, or does it have to be via host name? (since that's
> what's in the certificate?)
Has to be what's in the CN of the cert. I know its been suggested
already, but I'd take
I'm trying to create a custom fact. The following code works fine if puppetd
runs as a daemon but not from the command line. In other words if this runs
on server5 as a daemon, the return is correct, "confidential." But if
I run "puppetd -t"
from the command line "normal" is returned.
I don't
On another note, I do know the IP addresses of the boxes, can I use
IP's in the nodes, or does it have to be via host name? (since that's
what's in the certificate?)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"
You'll need to generate keys for distribution, automating this somehow by
calling out to ssh-keygen I presume.
Regards,
AJ
2008/9/12 Kenneth Holter <[EMAIL PROTECTED]>
>
> I've gotten Puppet to distribute server A's public SSH key on some of the
> nodes in the network. For password-less login to
I've gotten Puppet to distribute server A's public SSH key on some of the
nodes in the network. For password-less login to work, the nodes' host key
must be saved on server A.
Is there a security reason for not automating this process (if possible),
i.e. automating the process of retreiving the no
Kenneth Holter wrote:
> In what version was this resource type introduced? I'm running 0.24.4
> bur are getting "Could not find resouce type ssh_autorized_key..."
It got introduced in 0.24.5 but you can also install it on previous
versions using the pluginsync mechanism.
François
--~--~---
Kenneth Holter wrote:
> But does this resource type manage the distribution of SSH public keys
> for setup of password-less login? If so, could you please provide a
> sample code for distributing the SSH public key for a server A?
No, the sshkey type only manages host key (ie. /etc/ssh/ssh_known
In what version was this resource type introduced? I'm running 0.24.4 bur
are getting "Could not find resouce type ssh_autorized_key..."
On 8/27/08, AJ <[EMAIL PROTECTED]> wrote:
>
>
> You're using a version of puppet that doesn't have this type.
>
> Upgrade.
>
> Regards,
>
> AJ
>
> On 27/08/2008,
Thanks for the reply.
But does this resource type manage the distribution of SSH public keys for
setup of password-less login? If so, could you please provide a sample code
for distributing the SSH public key for a server A?
On 9/10/08, Peter Meier <[EMAIL PROTECTED]> wrote:
>
>
> Hi
>
> > I'd l
12 matches
Mail list logo
