TODO


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

General:
_config files_
The domaine name is set in both files, this might cause weird problems if not set to identical values. This also means we're doing something incorrect ans out config file approach is flawed (duplication of information, things _will_ go wrong).

beowulf-head ebuild:

The beowulf-head ebild requires that the NFS bootable image exists in /tftproot/nfsroot/$ARCH prior to calling pkg_config. Currently, this folder is populated thanks to the following sequence:

 mkdir -p /tftproot/nfsroot/$ARCH
 tar -xjf /var/tmp/catalyst/builds/default/stage4-$ARCH-nfsroot.tar.bz2 \
 -C /tftproot/nfsroot/$ARCH

Where stage4-$ARCH-nfsroot.tar.bz2 is a stage4 package created using the NFSroot-HOWTO.

We need to find a way to either automate the image creation via an ebuild or provide such an image wthat could be downloadable and add it as a config parameter to cluster.conf (ie: NFS_ROOT_IMAGE=stage4-$ARCH-nfsroot.tar.bz2) and let pkg_config perform the above sequence.

Code:

cluster-setup

* Separate the functions so that the node part could be called upon multiple NFSROOTs. This would make it easyer to provide support for different ARCHs provided by the same master. Something in the lines of `setup-nfsroot $NFSROOOT` would be appropriate.

* Modify script so that it can be used under different ROOT environements (ie: USB environment where the ROOT is actually rw)
- This wasnt done since one can argue that a USBkey install is identical to an HDD install and most of the automation in the cluster-setup are meant for a livecd. HDD and USBkey install should just use the ebuilds and follow the instructions.

* Modularize so it is easy to add new features to auto-confgure, triggered by USE flags (ie: the torque auto-config is triggered bu the pbs USE flag)

System:

* Aufs mount the liveCD and provide the means by which one may save the config+environement to USB key (is it worth the effort or shouldn't someone just install directly to USB).