Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

  • Pull an old Compute Node (CN) and convert to a new CentOS Head Node ("new HN"“new HN”)
  • Add new CNs to new HN
  • Add one old CN's CN’s to new HN
  • After testing, shift production to new HN.
  • Add the rest of the old CN's 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 CN’s to ChemIT Community HN
    • Convert Collum HN to CN and add to ChemIT Community HN

...

  • If so, use another node (for example, 3).

Time and labor estimates

View Project timeline: Collum Cluster timeline.pdf

Est. labor: ~286 hours

Duration - Start-to-finish time (taking into account availability): ~5 weeks 30 work days (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

25 days

6.4 weeks