Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
*Started testing auto-submit
+
*CyberShake technical readiness review
*Verified BBP install on Stampede
+
*John upgraded Condor on shock to 8.2.8; fixed configuration problems
*Modified Titan pilot daemon to query for new Pegasus parameter
+
*Titan pilot jobs stopped being able to communicated; could be firewall issue
*Learned Blue Waters is upgrading GT on Thursday
+
*Tested job submission to h2ologin4 test system, not working; could be issue with h2ologin4 configuration, emailed NCSA
 +
*Found bug in pegasus-rc-client, emailed ISI, pushed out fix
 +
*Tested file transfer between ie06 test system and hpc-scec, worked
  
 
== Today ==
 
== Today ==
*Finish testing auto-submit
+
*Update science and technical reviews
*Test Titan pilot daemon
+
*Test h2ologin4 once Tim has pushed through fix
*Test current shock GT install on BW test system
+
*Check shock firewall issue
*Get materials together for technical readiness review - invite Blue Waters, OLCF?
+
*Communicate with NCSA, OLCF, and USC HPC about planned run
*Update science review with new source material and conclusions
 
  
 
== Blocked ==
 
== Blocked ==

Revision as of 19:27, 9 April 2015

Yesterday

  • CyberShake technical readiness review
  • John upgraded Condor on shock to 8.2.8; fixed configuration problems
  • Titan pilot jobs stopped being able to communicated; could be firewall issue
  • Tested job submission to h2ologin4 test system, not working; could be issue with h2ologin4 configuration, emailed NCSA
  • Found bug in pegasus-rc-client, emailed ISI, pushed out fix
  • Tested file transfer between ie06 test system and hpc-scec, worked

Today

  • Update science and technical reviews
  • Test h2ologin4 once Tim has pushed through fix
  • Check shock firewall issue
  • Communicate with NCSA, OLCF, and USC HPC about planned run

Blocked

  • No

Follow-ups

  • No

Areas of Responsibilities

  • CyberShake
  • Broadband CyberShake
  • Code migration