Excerpt |
---|
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: 120 hours~110 hours for Lulu, plus Michael's hours for networking, hardware configuration, consultation, etc.
Work descriptions | Effort | Elapse time | Est. date |
---|---|---|---|
Install and config CentOS on headnode | 3 days | 1 week |
|
Install and config Warewolf | 5 days | 1 week |
|
Install and config Torque | 2 days | .5 wk |
|
Install and config WebMO | 5 days | 1 week |
|
Install and config 2nd (new) node | 1 day | .2 week |
|
Jun et al. test | 2 days | 1 week | End of August |
Plan
See above work descriptions for detailed steps.
Overview plan:
- Pull an old CN and convert to CentOS HD ("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
Risks
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).
- If so, use another node (for example, 3).