[ale] ssh for automated management

[James P. Kinney III]

On Fri, 2004-12-17 at 16:57, David Corbin wrote:

> 
> What I failed to mention, is this is really about managing software upgrades 
> automatically.  It's not something that will happen on an every day basis.  
> Short of serious problems, it would probably be once a moneth at most.  Even 
> then, it would likely be staged: 1 site for 2 days.  10 sites.  25 sites.  
> 100, 250   the rest.

rsync is the most eficient way. Each master node server polls the root
server for updates and then is ready for slave nodes to update from it. 

ssh keys need to be installed for best security. A single distributed
master key and a single distributed slave key, turn off host checking
and make key authentication the only method. chroot the rsync servers.

There is a multiple-shell ssh extension that allows same command to
execute on multiple remote ssh logins simultaneously. I don't recall the
tool name. That is good for getting keys setup.
-- 
James P. Kinney III          \Changing the mobile computing world/
CEO & Director of Engineering \          one Linux user         /
Local Net Solutions,LLC        \           at a time.          /
770-493-8244                    \.___________________________./
http://www.localnetsolutions.com

GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics)
<jkinney at localnetsolutions.com>
Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part