Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Track User Support Requirements"

From EGIWiki
Jump to navigation Jump to search
Line 79: Line 79:


|-style="background:#E5ECF9;"
|-style="background:#E5ECF9;"
|rowspan="15"|(Topic 6) Data management
|rowspan="14"|(Topic 6) Data management
|rowspan="2" style="background-color:orange"|(Subtopic 6.1) Access rights synchronization  
|rowspan="2" style="background-color:orange"|(Subtopic 6.1) Access rights synchronization  
|[https://rt.egi.eu/guest/Ticket/Display.html?id=2022 #2022 enforcement of access control between file catalogue and physical files]
|[https://rt.egi.eu/guest/Ticket/Display.html?id=2022 #2022 enforcement of access control between file catalogue and physical files]
Line 156: Line 156:


|-style="background:#E5ECF9;"
|-style="background:#E5ECF9;"
|rowspan="7"|Other
|rowspan="6"|Other
|[https://rt.egi.eu/guest/Ticket/Display.html?id=910 #910 Disk space management]<br>
|[https://rt.egi.eu/guest/Ticket/Display.html?id=910 #910 Disk space management]<br>
|
|
Line 204: Line 204:
2011, March 31: UCST and UCB evaluates the requirement.<br>
2011, March 31: UCST and UCB evaluates the requirement.<br>
2011, January 6: New requirement entered into RT<br>
2011, January 6: New requirement entered into RT<br>
|-style="background:#E5ECF9;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=2969 #2969 LFC reliability is currently not acceptable]
|
2011, November 1: requestor was noticed that if he doesnt reply within 1 week, his requirement will be closed<br>
2011, October 14: GGUS asked more details with an example. Requestor was asked to provide more details.<br>
2011, October 14: requirement is at GGUS. REF: [https://ggus.eu/ws/ticket_info.php?ticket=75299 #75299]<br>
2011, February 7: New requirement entered into RT<br>


|-style="background:#E5ECF9;"
|-style="background:#E5ECF9;"

Revision as of 13:13, 8 November 2011

Main Submit Track


UMD (TCB) Operations (OMB) User Support (UCB)


This page displays the details of requirements that have been submitted to EGI by its user communities through the Requirement Tracking system. The requirements are investigates by the User Community Support Team of EGI, solutions are offered to them by the team, by NGIs and by external technology providers of EGI. The process is described at https://wiki.egi.eu/wiki/Requirements_gathering_details. If you wish to submit a requirement to EGI, please use the Requirement Tracking system.

The requirements of the operational community of EGI (administrators of grid sites) are listed on another page: ...

Open requirements

Color & meaning
Orange indicates that TCB OR Technology providers has something to do with it through TCB.
Green indicates that Technology provider has something to do with it.
Blue indicates UCST has something to do with it.
Yellow indicates UCB has something to do with it.


Subject Status & History
(Topic 1) Increased stability and scalability for gLite WMS #2966 Enhanced WMS throughput

2011, October 26: EMI confirmed that "WMS performance report" document will be provided by Marco Checchi in December
2011, May 20: at TCB 6th meeting discussion was closed and EMI promised to provide documentation on installation scenarions for WMS (Action 02/07 closed: minutes)
2011, April 7: requirements were discussed at 5th TCB meeting (Action 02/07 open: minutes)
2011, February 8: requirements were evaluated by UCST
2010, December 7: New requirements entered into RT

#2970 The WMS is unstable and slow
#2972 WMS high workload
#1133 Increased stability and scalability for gLite WMS
#704 Demand for WMS , stability of CREAMCE, gLite reliability at EMI
#698 WMS stability and performance
(Topic 2) Better (more verbose and informative) error messages #2965 Enhanced information feedback by middleware error messages

2011, October 26: EMI confirmed that they will prepare a list of error message documentations. It will be ready before EMI-2 release, in December.
2011, August 9: at TCB 7th meeting discussion was closed because EMI's requirements process already has that embeded and documented which components have documentation on error messages (Action 05/02 closed: minutes)
2011, May 20: requirements were discussed at 6th TCB meeting (Action 05/02 open: minutes)
2011, February 8: requirements were evaluated by UCST
2010, December 7: New requirements entered into RT

#2971 Error messages and Error status
(Topic 4) Coherency of command line commands, parameters #2560 man pages for grid commands

2011, October 10: Ales from GGUS triggered the discussion in SA2 for updating the GENERIC_DOC_4 to include proper "--help" messages.
2011, August 5: Requirement is at GGUS. GGUS REF: #73214
2011, July 14: New requirement entered into RT

#723 no coherent set of option flags in command line tools

2011, October 26: EMI confirmed that they will provide table of cli parameters the same time as EMI-2 release will go out (April 30, 2012) and after EGI should provide feedback about which parameters should be changed.
2011, April 21: EMI promised to provide a table of cli parameters, an inventory of all the cli parameters per commands as it is Today and ask the community to mark which parameters they want to change (REF: https://rt.egi.eu/guest/Ticket/Display.html?id=1780)
2011, April 7: requirement was discussed at 5th TCB meeting (no action recorded minutes)
2011, February 8: requirement was evaluated by UCST
2010, December 8: New requirement entered into RT


(Topic 6) Data management (Subtopic 6.1) Access rights synchronization #2022 enforcement of access control between file catalogue and physical files

2011, October 28: UCST got a confirmation from EmiJra1Syncat activity that SYNCAT will give tools and methods to synchronize metadata and then it's up to the storage technology providers to decide to use them or not.
2011, September 27: It was accepted and already (partially) covered by EMI development plans (REF: https://rt.egi.eu/guest/Ticket/Display.html?id=2731)
2011, September 20: The EMI presentations at the EGI Technical Forum showed that development of SE-LFC synchronisation is ongoing.
Link to the "catalogue synchronisation working group" of EMI: https://twiki.cern.ch/twiki/bin/view/EMI/EmiJra1Syncat
Link to the developers' tracker: https://savannah.cern.ch/task/?21787
2011, May 11: requirements were discussed at UCB (no action recorded minutes)
2011, May 10: requirements were evaluated by UCST
2011, April 27: New requirements entered into RT

#917 Coherent control access policies for all replica of a file

2011, October 28: UCST got a confirmation from EmiJra1Syncat activity that SYNCAT will give tools and methods to synchronize metadata and then it's up to the storage technology providers to decide to use them or not.
2011, September 27: This request is accepted and already (partially) covered by EMI development plans (REF: https://rt.egi.eu/guest/Ticket/Display.html?id=2731)
2011, September 20: The EMI presentations at the EGI Technical Forum showed that development of SE-LFC synchronisation is ongoing.
Link to the "catalogue synchronisation working group" of EMI: https://twiki.cern.ch/twiki/bin/view/EMI/EmiJra1Syncat
Link to the developers' tracker: https://savannah.cern.ch/task/?21787
2011, March 30: requirement was evaluated by UCST
2011, January 7: New requirement entered into RT

(Subtopic 6.2) Stability and scalability of Data Management Services #922 Management of many small files

2011, July 1: Submitted to TCB
2011, March 31: requirement was evaluated by UCST
2011, January 7: New requirement entered into RT

#919 Management of avalanches of job submission

2011, July 1: Submitted to TCB
2011, March 31: requirement was evaluated by UCST
2011, January 7: New requirement entered into RT

#916 DMS workload management

2011, July 1: Submitted to TCB
2011, March 31: requirement was evaluated by UCST
2011, January 7: New requirement entered into RT

(Subtopic 6.3) Content synchronisation #924 File updates

2011, November 7: requirement is at GGUS for clarification. REF #76058
2011, October 28: UCST got a confirmation from EmiJra1Syncat activity that SYNCAT will NOT cover this requirement as they deal only with metadata and not real data.
2011, September 27: It was accepted and already (partially) covered by EMI development plans (REF: https://rt.egi.eu/guest/Ticket/Display.html?id=2731)
2011, September 20: The EMI presentations at the EGI Technical Forum showed that development of SE-LFC synchronisation is ongoing.
Link to the "catalogue synchronisation working group" of EMI: https://twiki.cern.ch/twiki/bin/view/EMI/EmiJra1Syncat
Link to the developers' tracker: https://savannah.cern.ch/task/?21787
2011, March 30: requirement was evaluated by UCST
2011, January 7: New requirement entered into RT

Data lifetime management #2024 data lifetime management

2011, October 10: GGUS StoRM SU provided the short guide using "volatile" feature.
2011, September 28: UCST requested at GGUS to provide a StoRM-SRM-Client User Guide for a "volatile" feature usage.
2011, August 22: StoRM (STOrage Resource Manager) is part of UMD and could be used as a solution.
2011, July 28: Requirement is at GGUS. GGUS REF: #72997
2011, May 24: New requirement entered into RT

#2877 storage element and lifetime of data

2011, October 10: GGUS StoRM SU provided the short guide using "volatile" feature.
2011, September 28: Similar requirement #2024 is already in GGUS (REF: #72997). UCST requested at GGUS (REF: #72997) to provide a StoRM-SRM-Client User Guide for a "volatile" feature usage.
2011, September 26: New requirement entered into RT

Other #910 Disk space management

2011, October 21: VO Services team is working on a study about VO and Storage Element decommissioning which may provide valuable input to solve this requirement. The decommissioning of an SE also requires tools to mass-migrate files to other storage.REF: #2394
2011, October 14: Reqeustor confirmed that for a short-term the partial solution might help them to solve that issue, but it would not solve for a long term depending on how this short-term solution will be applied.
2011, October 14: Asked requestors if they would be happy with the partial solution to be implemented
2011, October 5: Partial solution depends on operations requirements #2766. But in order to fulfill the complete requirement it should be discussed at TCB only.
2011, September 28: Requirement is at GGUS for a confirmation.GGUS REF: 74741
2011, March 31: UCST evaluates the requirement
2011, January 6: New requirement entered into RT

#2491 Redundancy of SE using lcg-cr command

2011, October 24: UCST asked GGUS DMSU again with a few questions providing the use cases and asked for a best practice information.
2011, September 6: GGUS proposed temporary solution to create an FAQ. We are waiting for a confirmation when it will be done. Also we did ask to forward the request to a product teams for further comments.
2011, July 25: Requirement is at GGUS (REF: #73806)
2011, June 30: New requirement entered into RT

#1742 lcg-cp - background replication to other SEs
BUG / No EMI release defined

2011, September 6: Bug was created by GGUS in savannah tracker REF: #86446
2011, June 17: Requirement is at GGUS (REF: #71646)
2011, April 13: New requirement entered into RT

#926 Distributed relational data management

2011, November 1: UCST asked requestor to provide more details
2011, October 21: UCST is investigating the use of RDBMS in Grid
2011, October 26: Answer from GGUS:
"Within EMI data there is no such activity.
The access control to the multiple databases should also be aligned.
That is far beyond our scope. You may contact the PTB through our technical director in case you would like this to be included in EMI-3."
2011, October 10: Requirement is at GGUS for a confirmation (REF: #75165)
2011, March 31: UCST evaluates the requirement.
2011, January 7: New requirement entered into RT

#909 Improved replica selection
BUG / No EMI release defined

2011, April 20: Bug was created in savannah tracker REF: #66197
2011, March 31: Requirement is at GGUS (REF: #56928).
2011, March 31: UCST and UCB evaluates the requirement.
2011, January 6: New requirement entered into RT

#1626 Request for WebDav interface to LFC
FEATURE / No EMI release defined

2011, August 2: EMI task - "D2: Http/webdav for LFC" created. REF: #21779. Currently task is defined as "problemtatic" and is being investigated, no release planned yet. EMI Document REF: Technical Development Plan 1.3.2
2011, July 25: Requirement is at GGUS. REF: #72918
2011, March 28: New requirements entered into RT

Workflows #928 Scientific data flows

2011, August 25: UCST provided the list of APIs table. REF Service_APIs
2011, June 14: requirement was discussed at UCB meeting: (Action open 04/03 minutes)
2011, March 31: requirement was evaluated by UCST
2011, January 7: New requirement entered into RT

MPI #1391 Support for parallel jobs in JDL
BUG / Scheduled for UMD-1.4.0 (30 January, 2012)

2011, November 7: UMD-1.0 release does not include EMI gLite MPI released package which doesn't pass the UMD quality criteria. EMI gLite MPI is planned to be included in 1.4.0 release scheduled in 2012 January.
2011, June 7: UCST prepared MPI User Guide
2011, May 12: EMI-1 Kebnekaise release including fixed MPI related bugs: #77096, #76971, #58878.
2010, December 8: New requirement entered into RT

#920 Parallel jobs submission
BUG / Scheduled for UMD-1.4.0 (30 January, 2012)
#727 Proper MPI support
BUG / Scheduled for UMD-1.4.0 (30 January, 2012)
#3087 mpi-start should publish the version inside information system
BUG / Scheduled for release ? (Date ?)

2011, November 2: bug was created. REF: #52
2011, November 2: requirement is at GGUS. REF: #75847
2011, November 2: New requirement entered into RT

Client API
#2769 Homogenous APIs for a middleware

2011, September 29: 8th TCB meeting has some updates on SAGA API. Deployment of SAGA and inclusion into UMD is expected in Q1/2012.
2011, August 25: New requirement entered into RT

Other #2561 EGI bubble help on EGI web sites

2011, X: work in progress by UCST
2011, July 14: New requirement entered into RT

#925 Service certificates

2011, October 14: EGI should proceed in two ways:
1. Introducing robot certificates at national CAs: tasks - contacting the local CAs by the NGIs, requesting the introducing of certificates, reporting back to project members about success and lessons learnt.
2. EGI.eu establish a CA that issues robot certificates: tasks - Discuss the feasibility of establishing such a CA with IGTF; depending on the policy regulations establish the CA or request changes in policies.
2011, September 20: Requestor would like to see robot certificates supported by all EGI CAs - grid-wide.
2011, June 8: UCST provided the list of CAs supporting the robot certificates.
2011, March 31: UCST evaluated the requirement.
2011, January 7: New requirement entered into RT

#923 Single sign-on
TASK / Scheduled for EMI-2 (April 30, 2012)

2011, October 14: EMI is developing STS service. Task: Simplified management of credentials #21798. Expected to be released in EMI-2.
2011, October 10: Waiting for confirmation from GGUS when requirement could be implemented REF: #75175
2011, June 28: Requirement is at GGUS (REF:#73008). Work is planned but not for EMI-2.
2011, March 31: UCST evaluated the requirement.
2011, January 7: New requirement entered into RT

#921 Short jobs efficiency

2011, October 31: another document for a requester was provided: VO and Resource Provider SLA Template. Waiting for a comments.
2011, October 10: requester says that current OLA document cant be used between user community and site/VO SLA
2011, September 13: Waiting for a comments from requestor
2011, June 16: UCST with help of Operations provided the RC OLA document which can be re-used for VO OLA, REF: Resource infrastructure Provider Operational Level Agreement
2011, March 31: UCST evaluated the requirement.
2011, January 7: New requirement entered into RT

#918 Middleware support for pilot jobs

2011, July 2: UCST will collect the current use cases, requirements and opinions about pilot jobs from the community
2011, July 1: Was discussed at UCB meeting on 2011, June 14 (meeting minutes)
2011, May 30: UCST evaluated the requirement.
2011, January 7: New requirement entered into RT

#722 Proper gLite services support and improvements and development at EMI
TASK / Scheduled for EMI-2 (April 30, 2012)

2011, October 28: GGUS confirmed and provided the list of committed tasks for EMI-ES service. REF: click here. The service and committed tasks should be implemented and available for EMI-2 release
2011, October 10: UCST submitted GGUS ticket (REF: #75181) to get a confirmation about the timeline of implementation.
2011, July 12: EMI-2 release have work planned towards the unified user interface REF: see attachments
2011, March 30: UCST evaluated the requirement.
2010, December 8: New requirement entered into RT

#2968 JDL does not offer GLUE attribute for available disk space on worker node
BUG / Scheduled for EMI-2 (April 30, 2012)

2011, October 14: savannah bug was created. REF #87799
2011, October 14: requirement is at GGUS. REF: #75297.
2011, February 7: New requirement entered into RT

#2985 VO registration without certificates

2011, October 21: UCST investigates the policy documents and other related issues with user/robot certificates.
2011, October 14: requirement is at GGUS. REF #75304
2011, October 13: New requirement entered into RT.

#3070 NGIs publishing user-level accounting data to the authorised VO Resource Managers

2011, November 2: operations team will investigate the requirement in the next upcoming operations meeting
2011, October 31: requestor was asked to provide more details.
2011, October 31: requirement is under evaluation by UCST.
2011, October 27: New requirement entered into RT.
2011, October 26: requirement is at GGUS. REF: #75762

Solved requirements

Please click on -> Solved_user_requirements

Useful links

Retrieved from "https://wiki.egi.eu/w/index.php?title=Track_User_Support_Requirements&oldid=27221"