Upgrade to CentOS and add 2 nodes to existing

Time and labor estimates

Start-to-finish time (taking into account availability): ~5 weeks (start 7/31, Wed)

Est. labor: ~110 hours for Lulu, plus Michael's hours for networking, hardware configuration, consultation, etc.

Work descriptions	Effort in Hours or days	Elapse time (usually days or weeks)	Est. date
Install and config CentOS on headnode (Use Node 2)	3 days	1 week
Install and config Warewulf Includes attaching one (new) node	5 days	1 week
Install and config Torque / maui	2 days	.5 wk
Install and config WebMO	5 days	1 week
Install and config 2nd (new) node and 3rd (old) node.	1 day	.2 week
Copy Jun data for test	2 days	.5 wk
Jun (and group) test & tweak	2 days	1 week
Cleanup / additional	2 days	.5 wk
Move old cluster nodes to new Cluster Keep the old head node for 1 month?	1 day	.2 wk
Move old cluster user data to new cluster (Collum group down time)	2 - 3 days	.5 week
	Total	18 days	5.7 weeks

Plan

See above work descriptions for detailed steps.

Overview plan:

Pull an old Compute Node (CN) and convert to a new CentOS Head Node ("new HN")
Add new CNs to new HN
Add one old CN's to new HN
After testing, shift production to new HN.
Add the rest of the old CN's to new HN
Convert old HN to CN and add it to new HN
Later; see P41: Migrate to ChemIT Community Head Node
- Add all CN's to ChemIT Community HN
- Convert Collum HN to CN and add to ChemIT Community HN

And possible ways to address them.

Gaussian needs to be recompiled (under new OS).

If so, add A LOT of time and uncertainty. Spools up a whole new, large project, and crack open the PGI compiler.

WebMO needs to be upgraded from 2010 version. Perhaps a good idea to do anyway, if "good reasons" are identified.

If so, $1,000. And time/ process to order and get software, learn of differences, and apply it.

Node 2 turns out to be a dud (fails or is unstable).