RFC: Classes list for FAI/Lenny
The Etch installation scheme with our FAI server used one class for each type of node (NODE_COMPUTE, STORAGE, ...) but this is somehow inflexible when a mixture of classes is needed and also quite error-prone in terms of duplicated package lists. Thus, I propose to move to a modular FAI class concept, where in the end a larger number of dedicated classes compose the final class.
This is a sample list of possible class names:
| Class name
|| purpose / packages in this class (example)
|| perform any necessary actions for creating a 4 disk RAID6 array with 750 GB disks on a ARECA controller
|| master node for Condor
|| Condor compute node
|| submission only head nodes (remote submission) - if needed
|| set-up this machine as a forward only mail client
|| everything about mail server in the Atlas framework
|| set-up for Atlas NIS clients
|| set-up for our Atlas NIS server
|| bare minimum list needed everywhere (vim, emacs, apt-file, htop, sysstat, iostat, ...)
|| install development packages (man pages, compilers, debugging tool, ...)
|| this host is exposed and needs, iptables, apticron, security.debian.org,...
|| remember that the class hostname is always available
|| install LDG related things (ldg-server/client)?
|| lscsoft related stuff
|| install only matalb stuff for compute nodes
|| install interactive matlab environment
|| install mysql server
|| install postgresql server
|| install and configure basic apache
I guess many more classes are possible, but you get the idea.
Unless FAI has its own way of creating dependency between classes, we probably need to write a wrapper script which maps a host class to service classes, e.g.
| Host Class
|| Service classes
|| DEFAULT ATLAS_MAIL_CLIENT ATLAS_NIS_CLIENT ATLAS_CONDOR_NODE LSC MATLAB_BATCH ...
- 06 Feb 2009
| Title || Description of FAI classes for Lenny |
| Description || This page proposes a new modular scheme for FAI classes on Lenny Servers. |
| Tags || FAI class Lenny |
| Category || Admin |