On Wed, 7 Mar 2007, Jeffrey Law wrote:
Ah. Does the headnode ever need to do anything to control the stateless
nodes without human intervention (ie, does the head node ever fire off
commands to the clients via SSH?)
Yes.
As an admin, do you ever remotely log into the clients via SSH? If so, then
you probably need a persistent SSH private key for the clients.
Due to the way it works there's not really any need to have different keys on
the slaves, so in the past I've just used the same keys for all slaves
If that's the only persistent bit you need, then puppet may be overkill.
The only other bit I have at the moment is X related. Due to hardware
failures I've got two different types of motherboards which require different
X configs. Currently this is simply detected at runtime, which works out as a
better solution than using something like puppet.
But as I said, partly I wanted to see how far StatelessLinux had got since the
last time I looked at it. It's nice to know what it can do, so that when I
find myself in a situation that suits it later down the line, I notice.
jh
--
"Computers are useless. They can only give you answers."
-- Pablo Picasso
_______________________________________________
Stateless-list mailing list
[email protected]
http://www.redhat.com/mailman/listinfo/stateless-list
