WP3 WP3 at Budapest 2/9/2002 Steve Fisher / RAL

WP3 Steve Fisher/RAL - 2/9/2002WP3 at Budapest2 Summary News –EDG Retreat –EDG Tutorials –Quality –Release plan –ATLAS DAQ requirements –CMS requirements Plan for the rest of the week

WP3 Steve Fisher/RAL - 2/9/2002WP3 at Budapest3 EDG retreat One and a half days in a hotel near CERN with about 40 participants –Short session from IRST (Trento) on static analyis and on formal methods –Release procedures Talk from Cal Talk from LCG The new QAG A technical body was proposed but was transformed by the next day –Support of 1.2 Talks from WP8-10 Talk from Markus –Proposed release procedures from Bob and LCG

WP3 Steve Fisher/RAL - 2/9/2002WP3 at Budapest4 Retreat: some issues Deployed Software must be supported Acceptance criteria are not in place for most WPs Release procedures, though formally in place, were ignored. Interfaces are too low level for the user They want efforts in reliability –need defensive programming –need good diagnostics –avoid single points of failure. Documentation needs revision GRISs need a shorter cache time for benefit of RB Should separate VOs - each with their own II and RB

WP3 Steve Fisher/RAL - 2/9/2002WP3 at Budapest5 Retreat: Site Man (1) Installation –Need manual checks and on each node Running –No test procedures to locate faulty services –Tracing a problem is hard - log files in odd places with odd formats –Error messages useless Web is no good for new users –hard to find the information –poor level of introductory info Sys-admin needs defined tests and procedures.

WP3 Steve Fisher/RAL - 2/9/2002WP3 at Budapest6 Retreat: Site Man (2) Unit tests are not sufficient - software needs to be tested on a system with a well defined software base. Need goals for reliability. Must be more strict on accepting software to integrate Need to make more use of Bugzilla Need to be able to cover vacations and conferences Good things! –Value of a test suite –IRC good –Atlas collaboration has sparked things off –WPs finally take responsibility for their code

WP3 Steve Fisher/RAL - 2/9/2002WP3 at Budapest7 Tutorials Tutorials for end users wishing to gridify their applications Hands-on in the afternoon - need some Linux knowledge Dates: –Naples Sept - only the hands on part by EDG –CERN 3-4 October –NeSc - December The hands-on exercises provide a basic test-suite Material is on-line and will be published very soon. Will be revised quite a lot after “dry run” at CERN –We need to sharpen the R-GMA part

WP3 Steve Fisher/RAL - 2/9/2002WP3 at Budapest8 Quality There is a policy statement linked from the EDG top page which could be paraphrased as: –Making 1.2 work will be top priority –Then supporting production releases (bug fixes) will become top priority –For future development quality should have higher priority than functionality Quality (or the lack of it) was a recurrent theme at the retreat New QAG group formed –Will define procedures –WP rep will ensure that WP follows procedure –Currently me for WP3

WP3 Steve Fisher/RAL - 2/9/2002WP3 at Budapest9 ATLAS DAQ requirements Nothing specific as yet (they currently use ILU) but they are interested in: –Thousands of producers –Good performance

WP3 Steve Fisher/RAL - 2/9/2002WP3 at Budapest10 CMS (Boss) requirements Producer API should be able to specify that the ProducerServlet should not close down immediately but should stay around for an API specified period of time afterwards. –This is because their may be network or other problems and CMS does not want to lose information. –This appears easy to implement If the registry is not accessible to the ProducerServlet all requests should be queued for an API specified period in the ProducerServlet. If the registry becomes accessible the registration will proceed. If the registry does not become accessible within the specified period a failure is returned as the response to the next request from the Producer. This may therefore fail long after the Producer has gone away and so the Producer API cannot necessarily be informed. –Note that that if the Producer API cannot find a ProducerServlet to talk to this results in an immediate error being returned. CMS are also interested in the overwrite mode.

WP3 Steve Fisher/RAL - 2/9/2002WP3 at Budapest11 The rest of the week We only have 15 months left so this is probably our last chance to discuss together any significant changes Need to increase quality