Date: Tue, 23 Nov 2004 13:13:21 +1100 (EST) From: "Peter Ross" <Peter.Ross@alumni.tu-berlin.de> To: <matt@offmyserver.com> Cc: freebsd-cluster@freebsd.org Subject: Re: Clustering options Message-ID: <41102.211.26.240.17.1101176001.squirrel@mailbox.TU-Berlin.DE> In-Reply-To: <20041122163244.M31380@knight.ixsystems.net> References: <1101168686.3370.210.camel@work.gusalmighty.com> <20041122160912.L31380@knight.ixsystems.net> <1101170559.3370.223.camel@work.gusalmighty.com> <20041122163244.M31380@knight.ixsystems.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Matt Olander wrote: > The system detects that a new blade is in slot3 and deploys the > webserver image, as per your rule. If I do a first installation I write a script documenting everything I change after deploying a base system (e.g. changes in /etc, installing of packages, creation of directories or symlinks etc.) Later I do a network boot, installing the base system, running the script and restore data. Advantages: The script documents my machine and I always know what a machine does. A new installation is always clean and does not contain traces of former try and error procedures, reconfigurations etc. I can use it with newer OS and software versions. (OK, I have to check it once). It is easy to convert a machine from running service A (e.g. FTP) to a machine serving B (e.g. a mail server). If I am in need of faster recovery I have a bunch of harddisks or even blades ready to go. Imaging is a tool created by whimps to copy Windows systems (where installation does black magic and usually needs interaction;-). And imaging is a source of wealth for manufacturers. See the license fee for the IBM Director Remote Deployment Module. As A UNIX admin familiar with a routine described above I do not see many advantages. Regards Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41102.211.26.240.17.1101176001.squirrel>