Rocks Cluster Distribution: Users Guide: 
| ||
|---|---|---|
| Prev | Appendix B. Kickstart Nodes Reference | Next |
The packages and other common elements of the 411 Secure Information Service.
Parent Nodes:
Sets up the 411 Secure Information Service for clients. The 411 service will automatically configure itself when a file is published. Also puts all current 411 files from the frontend into the kickstart file for services that cannot tolerate a single 411 failure. Note that 411 can never guarentee full absolute success at any single time. It only offers consistancy over the long term.
Parent Nodes:
Sets up the 411 Secure Information Service for Master nodes. Creates the RSA public and private keys for the cluster, and configures Apache for 411.
Parent Nodes:
AutoFS for automounting home directories over NFS or the loopback device.
Parent Nodes:
Base class for all Rocks nodes. This should include compute nodes, frontend nodes, standalone laptops, computer labs, graphics nodes, nfs servers To achieve this level of flexibility this base class should have edges only to those classes that implement the core of Rocks.
Parent Nodes:
Children Nodes:
Minimalist C development support. This is everything you need to compile the kernel.
Parent Nodes:
A Rocks Cluster Central server. Can kickstart other servers over the network.
Parent Nodes:
The 'client node' in the graph. This file is used as a connection point for other XML configuration nodes.
Children Nodes:
Cluster Database SQL table structure. This used to be generated from a dump of the structure on Meteor. Now we just edit this directly.
Parent Nodes:
The 'devel node' in the graph. This file is used as a connection point for other XML configuration nodes.
Parent Nodes:
Children Nodes:
Take a root partition, and make it ours! This is the key to determining, on reinstalls, if we should save partitions (because the stamp is there) or blow away all the paritions on the disk (because the stamp isn't there).
Parent Nodes:
Configures a DNS nameserver for the cluster on the frontend. Both forward and reversed zones are defined using the database.
Parent Nodes:
Examine the disks on the box we're installing and see if there are existing, non-root partitions which we should preserve.
Parent Nodes:
Do everything needed to kickstart compute nodes or, generally speaking, everything needed to kickstart any node from this machine.
Parent Nodes:
The base installclass files. This graph node must preceed any other installclass graph nodes.
Parent Nodes:
A node is a machine in the cluster. Node's are on a private network and get DHCP/NIS state from the frontend.
Parent Nodes:
Turn off a bunch of packages we think we can live without. They take up too much room on the CD. For DVD based systems this is not required Be the ugly american. the only reason why we do this is because we want to be able to fit a rocks-enabled solution onto a single cdrom and the packages below don't directly help people to run parallel applications
Parent Nodes:
The 'server node' in the graph. This file is used as a connection point for other XML configuration nodes.
Parent Nodes:
Children Nodes:
A Rocks Cluster machine that has been kickstarted over the wide area network. Used by the central server to construct a minimal kickstart file.
Children Nodes:
SSH Config for compute nodes and other non-frontend appliances. We are using one key pair among all SSH servers in the cluster. This implies we do not care about Man-in-the-Middle attacks. We have subverted the protection for these attacks for several releases (broadcastSSH). This logic should not be in the ssh.xml node so the frontend will generate its own keypair.
Parent Nodes:
Setup Syslog for client machine to forward messages
Parent Nodes:
Children Nodes:
Setup Syslog for server to accept forwarded messages
Parent Nodes:
Children Nodes:
Trimmed down version of X11 for when we don't need sound all all that other GUI nonsense. I just want to run netscape man.
Parent Nodes:
Children Nodes: