Difference between revisions of "Upgrading sword"

From CUC3
Jump to navigation Jump to search
import>Cen1001
import>Cen1001
Line 1: Line 1:
Sword needs an upgrade. I'd like to move it to SuSE 9.3. At the moment I'm waiting to see how the [[Upgrading_destiny|destiny upgrade]] goes before making any firm decisions, but here are my current plans for sword:
+
Sword needs an upgrade. I'd like to move it to SuSE 9.3. The [[Upgrading_destiny|destiny upgrade]] went OK, which was effectively a trial run for upgrading sword. Here are my current plans for sword:
   
 
* Remove the MPI queues. MPI should be done on [http://www-theor.ch.cam.ac.uk/IT/servers/athens/ Athens] or the group servers
 
* Remove the MPI queues. MPI should be done on [http://www-theor.ch.cam.ac.uk/IT/servers/athens/ Athens] or the group servers

Revision as of 16:24, 27 April 2006

Sword needs an upgrade. I'd like to move it to SuSE 9.3. The destiny upgrade went OK, which was effectively a trial run for upgrading sword. Here are my current plans for sword:

  • Remove the MPI queues. MPI should be done on Athens or the group servers
  • Use rsh internally (ssh will still work though)
  • I have a list of suse packages for sword .
  • Make modules compulsory
  • Do network installs for the compute nodes
  • Software to be removed:
    • GAMESS-US
    • PGI 4.0
    • gcc 3.2
    • BLACS
    • ScaLAPACK
    • Most of the MPI libraries (may need to keep some for compiling purposes)

If anyone has things they'd like to see on sword this would be the place to ask for them.--Catherine 15:08, 28 March 2006 (BST)