Bobsced Cluster
Jump to navigation
Jump to search
Contents
Bobsced
Todo
- 411 tools-- fix ganglia to recognize broadcasts & update
- Naming scheme bs* vs compute-*-* vs c*-*
- This is terrible it needs work
- Updating bobsced0's RPM repo:
- yum-- free
- up2date-- RHEL
- "Aborting the rocks-update tool while the tool is downloading RPMs might produce corrupted RPM packages (SDSC Toolkit)" from pr_troubleshooting.doc
- NIS map &
/etc/passwd & /etc/group
permissions - What broke
cluster-fork
?
Howtos
Updating nodes to be kickstarted & adding new packages
- bobsced0 can be updated by just installing rpms
- Check for an RPM in:
/state/partition1/home/install/rocks-dist/lan/x86_64/RedHat/RPMS/
- Edit
/home/install/site-profiles/4.1.1/nodes/extend-compute.xml
- Add a package i.e.
<package arch="x86_64">libgfortran</package>
- Add a package i.e.
- Update the files that get loaded on kickstart:
cd /home/install
rocks-dist dist
- Check the kickstart file
dbreport kickstart c0-0
- If there were no errors, kickstart the node. i.e.:
shoot-node c0-0
Adding post install scripts to kickstart
- Edit
/home/install/site-profiles/4.1.1/nodes/extend-compute.xml
- Add a
<post arch="x86_64">
entry i.e.:<post arch="x86_64">cp /cluster/ganglia/gmond.conf /etc/gmond.conf</post>
Using 411 tools
- make -C /var/411 on bobsced0
- Copies the files to /etc/411.d/ using 411put
- Notifies client nodes to run 411get using ganglia
- The files that are watched can be updated by changing the makefiles in /var/411/
cluster-fork /opt/rocks/bin/411get --all
cluster-fork
- Used to run commands on all cluster nodes like the c3tools
- Broken, see todo
- Temporary fix:
cluster-fork --nodes="compute-0-%d:0-14" <command>
General Info
- NIS Importing
/etc/cron.hourly/importNIS.sh
- http
/cluster/www/bobsced/
/cluster
- Mounted using
/etc/rc.local
- Mounted using
/cluster/bobsced/etc/
- What's in here? Things for client or bobsced0?
References
- Rocks user's guide
- Platform rocks
- pr_troubleshooting.doc
- 411tools
- RHEL & More RHEL