Thread: [SSI] RFC: SSI Installation and Administration Requirements
Brought to you by:
brucewalker,
rogertsang
From: Brian J. W. <Bri...@co...> - 2001-12-18 01:50:25
|
SSI Installation and Administration Requirements ------------------------------------------------ I. General requirements A. Simple, yet flexible interfaces B. Interfaces similar to those found in base, where possible C. Interfaces are a superset of those used for CI D. Automatic operations, where possible E. Sanity checks and safeguards for user input F. No need to take down or reboot cluster, except when installing first node or building a new kernel G. Support interconnect technologies other than TCP/IP H. Support multiple interconnects for scalability and availability I. Support external networking interfaces on all nodes J. Support multiple filesystems served by different nodes (using CFS) II. Installing the first node A. Support different distributions B. Support different architectures, including UML C. Support an aggregation of technologies 1. CI 2. SSI 3. CFS 4. GFS 5. LVS 6. Mosix Load Leveler 7. DRBD 8. DLM 9. etc. D. Install from binaries or source E. CI and SSI packages can be verified with MD5 sums and GPG signatures III. Adding a node A. Use netboot to install new node B. Internal disk can be blank -- installing Linux is _not_ required C. Option to clean/reformat internal disk D. Support different swap device(s) on each node E. Node can always netboot, or optionally use internal boot disk F. Support different interconnect device(s) on each node G. Zero to minimal cluster configuration changes H. Automatic node number selection (optional) I. Automatic interconnect address selection (optional) J. Fully automatic node addition (optional) K. Option to make node a potential CLMS master (requires internal boot disk) IV. Adding a device A. Automatically added to device database during boot B. Automatically assigned a clusterwide unique name that is persistent across reboots V. Building a new kernel and ramdisk A. Almost the same as on a base system B. Not necessary for all nodes with internal boot disks to be up at the time, but it is recommended C. Currently using LILO; will switch to GRUB in the future VI. Changing a node's configuration A. Changes include: 1. node number 2. interconnect address 3. CLMS master flag 4. internal swap device 5. internal boot device 6. interconnect device B. Can be applied when a node is up C. Node may need to be rebooted for changes to take effect D. Safeguards against changing to an existing node number or interconnect address VII. Replacing a node A. Similar to adding a node B. Select existing node number, and confirm that it should be replaced C. Effectively deletes node and configures from scratch D. Use old node's configuration by default E. Safeguards against replacing a node that is up VIII. Replacing an interconnect interface A. Netboot with new interface B. Select existing node number to update interconnect hardware address information C. Safeguards against selecting a node that is up IX. Replacing an internal disk A. Clear internal disk information for node B. Netboot after installing new disk C. Format disk and reconfigure information X. Reformatting an internal disk A. Similar to replacing an internal disk B. Can clear disk information while node is up XI. Deleting a node A. Deletes appropriate device database entries B. Deletes node configuration C. Safeguards against deleting a node that is up XII. Deleting a device A. Deletes appropriate device database entry B. Safeguards against deleting a device in use -- Brian Watson | "Now I don't know, but I been told it's Linux Kernel Developer | hard to run with the weight of gold, Open SSI Clustering Project | Other hand I heard it said, it's Compaq Computer Corp | just as hard with the weight of lead." Los Angeles, CA | -Robert Hunter, 1970 mailto:Bri...@co... http://opensource.compaq.com/ |