If this is a new node being created through some sort of automation
procedure (kickstart, etc..) I'd look into generating your certs. You
can then, as part of the procedure, simply copy them to your puppet
client & server. This is how we do it within kickstart, which was
actually pretty easy to s
You're right. Should have spent some more minutes thinking about it.
It's been a long day...
On Wed, Feb 3, 2010 at 8:26 PM, Scott Smith wrote:
> Daniel wrote:
>>
>> Why not create a class or define containing your keys and run puppetd
>> only with the related tag? This would only install your ce
Daniel wrote:
Why not create a class or define containing your keys and run puppetd
only with the related tag? This would only install your certificates
but it requires you pre-generate the keys and certs on the
puppetmaster.
Without the private key, a certificate is useless. :( Also, how will
Why not create a class or define containing your keys and run puppetd
only with the related tag? This would only install your certificates
but it requires you pre-generate the keys and certs on the
puppetmaster.
On Wed, Feb 3, 2010 at 9:11 AM, Neil Prockter wrote:
> Hello
>
> I often configure a
On 2/3/10 12:11 AM, Neil Prockter wrote:
Hello
I often configure a new node that I want to be the same as an existing one.
However I'd like to run puppetd with --noop just the once to double
check the changes (I'm still responsible for them after all)
Trouble is on a new node the keys etc aren
Hello
I often configure a new node that I want to be the same as an existing one.
However I'd like to run puppetd with --noop just the once to double
check the changes (I'm still responsible for them after all)
Trouble is on a new node the keys etc aren't there and running as noop
they don't get
