From Earlham Cluster Department

Revision as of 09:50, 7 December 2011 (view source) Fitz (Talk | contribs) (→New Hopper) ← Older edit		Revision as of 15:45, 1 February 2014 (view source) Charliep (Talk | contribs) Newer edit →
Line 3:		Line 3:
	Most of this information pertains to Al-Salam specifically (unless otherwise stated) since that's our primary cluster.		Most of this information pertains to Al-Salam specifically (unless otherwise stated) since that's our primary cluster.
		+
		+	= Cluster Pages =
		+	* http://cluster.earlham.edu/wiki/index.php/Al-salam
	= Installing Software =		= Installing Software =
	* Download the source tarball into /root/install		* Download the source tarball into /root/install

---

Revision as of 15:45, 1 February 2014

Information for the administrators of the Earlham CCG clusters.

Most of this information pertains to Al-Salam specifically (unless otherwise stated) since that's our primary cluster.

Contents 1 Cluster Pages 2 Installing Software 2.1 Enabling a package within Modules 3 Users and Groups 4 Monitoring 5 New Hopper

Cluster Pages

• http://cluster.earlham.edu/wiki/index.php/Al-salam

Installing Software

• Download the source tarball into /root/install
• Unpack
• Make a <package>-<version>.config.sh script that runs ./configure with all your options (so that it's kept around in case we need to reinstall).
• To configure, give --prefix=/mounts/al-salam/software/<package>-<version>
• Run your config.sh and continue building/installing as normal
• Create a soft link from /mounts/al-salam/software/<package> to /mounts/al-salam/software/<package>-<version>

Enabling a package within Modules

• sudo su -
• cd /mounts/al-salam/software/Modules/3.2.7/modulefiles
• ls and look for another package that has a similar usage model as the package you're installing (e.g., Python module, C/C++ library, utility, library+utilities)
• Copy that to your new package, e.g., cp -r openmpi <software>
• cd <software>; ls Note the filename that appears.
• Move that file to your package's <version>
• Edit <version>
• Change references to the package you copied to the new one you're installing, including the version number, path, variable names, etc.
• Check modulefile(4) for keywords, etc., within the module file.
• Usually, that's all you need to do. Verify that it shows up in module avail and that module load <software> doesn't throw any errors and allows your package to work.

If you think your new package is important enough to be loaded by default, then add it to the list in /mounts/al-salam/software/Modules/3.2.7/init/al-salam.{sh,csh}

Users and Groups

Users are authenticated based on an LDAP server running on Hopper. cpu is installed on Hopper as an LDAP-user management tool. You should use it to view/edit/create users unless you're super comfortable with ldapmodify and LDIF. Passwords can be changed easily with the ldpasswd command on Hopper. It can be used both by users to change their own password and root to change another user's password.

Groups are also in LDAP. Check the tail end of the result of cpu cat for group info.

man cpu-ldap will tell you all about using cpu for user/group management. For the most part, its format is pretty similar to pw, but there are some minor differences. Read the man page.

Monitoring

• Ganglia - http://cluster.earlham.edu/ganglia/?r=month&s=descending&c=
• Machine room environment -

New Hopper

• Currently known as Megamind