[Beowulf] Re: number of admins (Mike & Chris & Sean)
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Ed Karns edkarns at firewirestuff.comThu Jun 9 07:38:40 PDT 2005
- Previous message: [Beowulf] [gregory.brittelle@kirtland.af.mil: Re: Intel?]
- Next message: [Beowulf] [rjdyer@vcu.edu: Re: Intel?]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Excellent suggestions & checklist (below) and should probably be the preface to or appended to all large systems tech support documentation. FYI: The night shift of the entire Australian telecom / datacom system (support, control, oversight and service) is operated this way ... from here in the old USA! ... although the "unattended" part is not really unattended but constantly monitored "virtually". Ed Karns FireWireStuff.com On Wednesday, June 8, 2005, at 04:41 PM, beowulf-request at beowulf.org wrote: > Chris Dagdigian wrote: > >> My $.02 >> >> The number of sysadmins required is a function of how much >> infrastructure you have in place to reduce operational burden: >> >> - remote power control over all nodes >> >> - remote access to BIOS on all nodes via serial console >> >> - remote access to system console via serial port on all nodes >> >> - unattended/automatic OS installation onto bare metal (autoYast, >> kickstart, systemimger etc.) >> >> - unattended/automatic OS incremental updates to running nodes >> >> - documented plan for handling node hardware failures
- Previous message: [Beowulf] [gregory.brittelle@kirtland.af.mil: Re: Intel?]
- Next message: [Beowulf] [rjdyer@vcu.edu: Re: Intel?]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
