Hello oscar friends, There is a feature in oscar that is slightly disturbing, or may be it's just my lack of understanding of oscar capabilities. Here is the problem:
Every time you reinstall the clients because of an update to the image on the server (e.g. updated RPM), you need to let your clients reboot from the network (PXE) or from a floppy. Now once your clients have reinstalled themselves, you want them of course to reboot from their own system on their local disks. To do that, you need either to remove the floppy from the drive or to change the boot sequence in the BIOS, which means a human intervention on all worker nodes after every system update. This is clearly unacceptable for a cluster containing a large number of machines. Given that I am working on building a system which will contain up to 1000 worker nodes and which is likely to experience ver frequent software updates, I need to find a solution to this problem. How are people managing big clusters dealing with this issue? Thank you, Vuko -- ===========================================================| Vuko Brigljevic, EP Research Fellow | CERN - European Laboratory for Particle Physics | --------------------------------------------------------- | Mail Address: CERN, Div. EP, 1211 Geneve 23 (Switzerland) | Office : B40-2B08 | Phone : +41-22-767 1662 | www : http://cern.ch/vuko | ===========================================================| ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Oscar-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-users
