Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Who is responsible?

Level

Older cluster
set-ups

Contemporary cluster
set-ups
"latest versions" refers to versions available at the date of set-up.

Notes

Research group

Applications: running within a user's directory

 

 

What will run on contemporary OS?

Research group

Applications: Research software, residing in research group's shared directory

 

xtaloopt, phonop

xtaloopt, phonop  

What will run on contemporary OS?

ChemIT

Research applications: Select software, residing in ChemIT-designated directory

Guassian Gaussian, ADF
Guassian

Gaussian, ADF

Q: Are these the correct applications?
Remove or add any in which there is an economy for ChemIT to be responsible?

ChemIT

Compiler applications: Select software, residing in ChemIT-designated directory

Intel compiler, using ChemIT-managed license server.

Intel compiler, using ChemIT-managed license server.

What will run on contemporary OS?

ChemIT

System applications: Provisioning web interface to cluster services

WebMO (old version)

WebMO (latest version)

Collum's only,

ChemIT

System applications: Job queuing and scheduling systems

Maui/ Torque
(old version)

Maui/ Torque
(latest version)


ChemIT

Compute node provisioning

Perceus

Warewulf


ChemIT

Monitoring tools

RAID controller card monitoring (hard disk monitoring)

RAID controller card monitoring (hard disk monitoring)

 

ChemIT

Versioning tools

Back In Time

Back In Time

Optional

ChemIT

Backup software (not just versioning!)

EZ-Backup (off-site)

EZ-Backup (off-site)

Optional?

ChemIT

Operating System (OS)

Fedora 13

CentOS 6

 

 

 

Scheraga
Hoffmann (helios; migrating)
Lancaster (planning to upgrade)
Loring
Abruna

Collum
Hoffmann (sol; new)
Widom? (via Chemistry Community Computer Cluster (C-4) head node)

Migration in progress:
Hoffmann.
On deck for upgrading to contemporary set-ups:
Lancaster

Define "responsible"

Group which selects, installs, debugs, maintains, updates, and otherwise keeps software functional. Finds alternatives. Secures resources to make work, and otherwise "owns" the problem.

Others can assist and consult and provide "best effort" services. For example, ChemIT will require research groups to confirm the operation of new installations. And research groups may benefit from having ChemIT look over problems the research group is having with their software.

Issues

  • Version neglect makes support harder over time, for any of these layers.
  • Impact on research when software (1) updates, or (2) upgrades.