EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI Requirements Status EGI.eu UCB

EGI-InSPIRE RI Overview UCB Topics (number of topics): 6 –EMI feedback was received for 5 topics –6 th topic is still New and not submitted to TCB yet (Title: Data management), full details are still gathered. –Total number of top priority requirements (distributed between 6 topics): 35 ( atus_at_UCB) atus_at_UCB Other (number of lower priority requirements): –9 are waiting feedback from EMI ( –4 (MPI related) are in process of implementation by EMI

EGI-InSPIRE RI Topic 1 (Ticket: #1777) Topic (1) - Increased stability and scalability for gLite WMS –Total requirements: 7 –All requestors are VO Manager(s). Full details received only from VO hone. –No response from VO(s): lsgrid, lofar, ilc, fusion, cdf, calice. –EMI feedback: EMI will provide a document detailing the scalability and stability capabilities of WMS under recommended typical deployment. The "WMS performance report" can then be used as a basis for further discussions. The WMS team thinks that the current performance numbers already meet the need of most of the user communities. At the same time, users are requested to submit bug reports directly to WMS via GGUS. RT Ticket: #1777

EGI-InSPIRE RI Topic 2 (Ticket: #1778) Topic (2) - Better (more verbose and informative) error messages –Total requirements: 6 –Requestors are: VO Manager(s), Communitie(s), NGI(s). Full details received only from LSGC and NGI_IL. –No response from VO(s): vlemed, lsgrid, lofar, ilc. –EMI feedback: EMI proposes the following strategy: - initially, we concentrate only on the client error messages - the user community is asked to submit the ten most annoying error messages per area (compute, data, security, information system/accounting) - EMI teams will fix and at the same time analyze the error messages RT Ticket: #1778

EGI-InSPIRE RI Topic 3 (Ticket: #1779) Topic (3) - Fixing the known bugs before adding new features –Total requirements: 1 –Requestor is: VO Manager(s) of desktopgrid.vo.edges-grid.eu. Still No response received. –EMI feedback: EMI commits itself to be focused on achieving service consolidation and stability. The handling of bugs is regulated by the EGI-EMI SLA. That SLA identifies very specific response and resolution deadlines for bug categories. Changes in the SLA have to be negotiated with EMI project office. RT Ticket: #1779

EGI-InSPIRE RI Topic 4 (Ticket: #1780) Topic (4) - Coherency of command line commands, parameters and APIs –Total requirements: 3 –Requestors are: VO Manager(s) and Communitie(s). –No response from VO(s): vlemed, pheno and Community: LSGC –EMI feedback: EMI proposes the following strategy for the command line parameters coherency challenge: - focus on user-side commands only, service administration commands should be excluded - EMI will provide a table of cli parameters, an inventory of all the cli parameters per commands as it is Today - EMI will ask the community to mark which parameters they want to change - EMI will also come with is own proposition concerning what kind of changes are feasibleRT Ticket: #1780

EGI-InSPIRE RI Topic 5 (Ticket: #1781) Topic (5) - Better feedback about jobs, automated resubmission of jobs that are stuck on sites –Total requirements: 4 –Requestors are: VO Manager(s) and Project(s). –No response from VO(s): lofar, fusion, cdf and Project: Healthgrid. –EMI feedback: According to the WMS product team the latest version of the WMS, that is released with EMI-1 should address most of the request. If there are still unresolved issues please open a GGUS ticket for the missing part(s). RT Ticket: #1781

EGI-InSPIRE RI Topic 6 (Ticket: #1808) NEW - Topic (6) – Data management –Total requirements: 14 –Requestors are: VO Manager(s), Project(s), Communitie(s). –Project’s DRIHMS requirements (4) were recorded, but no contact with project representatives was made yet. Are these requirements still valid ? –Community’s LSGC requirements (9) were processed and asked for more details. –VO vlemed didn’t responded yet. –EMI feedback: not available yet, because topic is not submitted to TCB. RT Ticket: #1808

EGI-InSPIRE RI Issues What is a requirement ? What is the state of your requirement ? UCST workflow

EGI-InSPIRE RI A requirement These parts must be clear and detailed –Use Case (based on experienced issue) –Configuration, Environment (where issue was experienced) –Expectation (what is expected) –Impact for user community (the impact of solved requirement)

EGI-InSPIRE RI State of the requirement UCST Ticket States: –Open - requirement is open for discussions, consistency check & technical details gathering is in progress –Accepted - requirement has full technical details and was accepted UCB Ticket States (highest priority requirements): –Open - requirement is open for discussions, consistency check & technical details gathering is in progress –Accepted - requirement has full technical details and was accepted –RT Tags - UCB is using 'Custom Tag' field to group tickets into Topics e.g. 'Custom Tag = ucb1' means Topic 1 and so on. TCB Ticket States: –RT Tags - TCB is using ‘TCB Status‘ field where values may be one of {Submitted|Committed|Endorsed|Stalled|Returned}.

EGI-InSPIRE RI UCST Workflow: EGI Requirements Process UCST Technology Providers UCB TCB Consistency check Formally accept the ticket Evaluate the technical completeness and correctness of the request Provide solution from the EGI-InSPIRE project or involve external solution providers Solution User Support Requirements Operational Tools Requirements Unified Middleware Distribution Requirements