- Combined list requests (Dmitry, Sasha), October 2012 ☑ done
- SSO for list request (Dmitry), October 2012☑ done
- Automatic task splitting (Dmitry), End October - November 2012
- Tasks cloning (Alexei, Valeri, Dmitry), October, 2012
- I/F part is ready. Nov 5, 2012. : http://pandamon.cern.ch/tasks/clonetask
- Task Request I/F parameters checking is in progress
- Running from nightlies (Andrej, Rod), October 2012
- Tag definition I/F. New implementation (Sasha, Dmitry), December 2012
- TR features for Group Production. Hiding unnecessary fields (Nurcan). Not assigned. More info is needed to implement it
- Pile up tasks start up before simulation is done. (Sasha), October 2012 ☑ done
- 1% issue. Implementation is postponed
- Scouts info usage for simulation tasks (Andrej, Rod, Wolfgang), Oct-Nov 2012 ☑ done
- FTK, file naming convention for merging step (Sasha, Graeme), October 2012☑ done
- CPU consumption information taken from TRF (Sasha, Graeme, 'Wuppertal group'), November 2012
- Meta-Language for Task Requests. ☑ done ( GraphML schema chosen - Maxim)
- CAPTCHA in TR I/F (Dmitry), October-November 2012☑ done
- it will be implemented as SSO and CAPTCHA option won't be needed anymore
- Requestor I/F . RIF. Wolfgang, Maxim, Valeri
- RIF specs (Wolfgang, Maxim)
- Twiki from Maxim : https://twiki.cern.ch/twiki/bin/viewauth/Atlas/ProdSys
- mid-Nov : Wolfgang will prepare an initial list of requirements
- Tаsk Request CLI
- postponed until ProdSys II
- Documentation, Savannah, Twiki (Maxim, Dmitry)
- AGIS/PanDA integration (Ale, Alden, AlexeyA)
- "Alden part " December 2012
- End-to-end test Jan 2013
- Production version, Feb 2013
- Task search options (Alexei), October 2012, ☑ done
- Monitoring.
- long running jobs/tasks
- Task progress based on task's submission info
- Failed jobs monitoring (by error type)
- 'Stuck' tasks
- Integration of existing group production monitoring tools with PanDA Classical and Dashboard monitoring (Nurcan, Jarka, Laura, Valeri)
- PanDA classical pages response time (Valeri)
Monday, October 29, 2012
ProdSys splinter meeting (October 2012) action items
Subscribe to:
Post Comments (Atom)
The doc reads,
ReplyDelete" . . .
19. Monitoring.
5. Integration of existing group production monitoring tools with PanDA
. . . "
Is it possible to provide some sort of URL to "existing group production monitoring tools" or /and list those tools explicitly?
Valeri, a customized monitoring page was set up by Rob Henderson to monitor the semi-automatic submission of the merging tasks in group production:
Deletehttp://lapb.lancs.ac.uk/atlas_validation/gmerge.php
We can choose an output type from this page. The displayed information is the run number (first column), a link to the input tasks (second column) and a link to the merging task (third column). The idea was to see the last run submitted and if the input tasks are done and the merging tasks are submitted w/o any delay.
As far as I followed from this ticket:
https://savannah.cern.ch/bugs/index.php?98935
You have set up a monitoring page to choose a particular output type for a given p-tag. Rob's page covers all p-tags used in the merging of a given output type. I'll discuss with Rob how much of the info in Rob's page we can monitor in Panda. I'll reply back here.
This comment has been removed by the author.
DeleteAlexei, I have a comment on the item "7. TR features for Group Production. Hiding unnecessary fields (Nurcan). Not assigned. More info is needed to implement it". This refers to the task request page:
ReplyDeletehttp://panda.cern.ch/server/pandamon/query?mode=reqtask1
where we only fill 3 fields to submit a task; Dataset, Configuration tag, userid. The other 3 fields can be hidden; Project, Transformation Type, Transformation Version.
Hi Nurcan,
ReplyDeleteplease give me default values to be used for hidden fields. Cheers, Alexei
As to Meta-Language for Task Requests: we are very close to the consensus (and probably arrived to the decision) that we'll use the graph model to describe Tasks. This is completely in line with what's done in industry and research. As such, the problem of picking the language becomes at least partially defined, as we need to look at representation of graphs and their state ("markings").
ReplyDeleteProgress report:
ReplyDelete4. Tasks cloning.
The application has been installed and available
https://pandamon.cern.ch/tasks/clonetask
The details are available via Savannah ticket https://savannah.cern.ch/bugs/?98392
4.1. 'https' protocol and CERN SSO are used to allow the restricted access and populating the "Task Request" fields like 'email' and "comment" from the user Grid certificate automatically
4.2. The clone task logic is present with hthttp://pandamon.atlascloud.org/static/doc/tasks/clonetask.html pending Sasha, Dmitri review.
4.3. The application API is
curl http://pandamon.cern.ch/clonetask?tid=[task Request Id]
It is available with New Monitor ‘?’ link.
4.4. The "action" parameter was added to the "List the Task Requests" application to allow using the well-known Web API to search and select the "Task Requests" and apply "action=cloneaction" for each selected request if needed.
https://pandamon.cern.ch/tasks/listtasks1?action=clonetask has been
4.5. Wolfgang is testing the application (see https://savannah.cern.ch/bugs/?98392 )
4.6. Main issue is the lack of the reliable up-to-date “sanity” function from prodsys group.
Progress report:
ReplyDelete15. Requestor I/F . RIF. Wolfgang, Maxim, Valeri
Neither clear requirement nor spec has been provided to be implemented yet.
Progress report.
ReplyDelete20. Monitoring
20.6 PanDA classical pages response time (Valeri)
The link http://panda.cern.ch/server/pandamon/query?mode=listtask is now connected with the new Panda Monitor Server providing 2-5 sec response time. The parameter “classic=true” can be used to access the old page if needed. This link is available from the new page as well.