WP 1 WMS release 2 issues Massimo Sgaravatto

  • Slides: 6
Download presentation
WP 1 WMS release 2 issues Massimo Sgaravatto INFN Padova

WP 1 WMS release 2 issues Massimo Sgaravatto INFN Padova

Disclaimer n n n The issues that I am going to raise come from

Disclaimer n n n The issues that I am going to raise come from tests I performed I didn’t tests yet all the functionalities and all the components Please let us know if there are other open issues

Open issues n Some “last minute” UI problems n n Problems with resubmission n

Open issues n Some “last minute” UI problems n n Problems with resubmission n n CEs already “used” are not considered Some open issues with Condor-G n n Trivial to fix In some cases when submission to Globus fails, job stays idle, and nothing is reported Nothing is reported when the proxy expires … going to be fixed soon Some problems affecting UI with JDLs logged to LB Debugging messages to be removed in UI/NS client

Missing pieces n n Dynamic quota management in NS Maradona n n Ready in

Missing pieces n n Dynamic quota management in NS Maradona n n Ready in LM, still missing in JA Integration with WP 2 Replica Manager n Integration with RLS (List. Replicas) n n Integration with Optor (getaccesscost as rank) n n To be done in release 2. 0 or later ? Gangmatching ? n n ~ done, but not tested yet (since RLS not populated with significant [for us] entries) Status ? ? LB n n Interlogger crashes(d) very often Hopefully all problems fixed

Missing pieces n Output Data Registration n n Management of expired proxies n n

Missing pieces n Output Data Registration n n Management of expired proxies n n n To be done in release 2. 0 or later ? We have to decide what to do Also need to understand how Condor-G is going to manage these scenarios To be done after release 2. 0, I suppose UI man pages Documentation n WMS user and administrator guide n n Admin guide ~ ready (apart from UI part) User guide update on going Build part missing Need to explain somewhere the new extended LB querying capabilities

Testing n These issues come from tests I performed only using the python UI

Testing n These issues come from tests I performed only using the python UI n n Tested “old” functionalities New functionalities n n I didn’t test yet GUI and APIs I didn’t test yet the other new functionalities n n Quickly tested MPI jobs both on LSF and PBS Patched gridftp server and gridftp API tested Proxy renewal, Interactive jobs, Quota management for sandbox files, Job Checkpointing, purger daemon, … No stress tests