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
 
(106 intermediate revisions by 3 users not shown)
Line 3: Line 3:
{{TOC_right}}
{{TOC_right}}


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 [https://wiki.egi.eu/wiki/New_Requirement_Manual Requirement Tracking system].  
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 [[Requirements_gathering_details]]. If you wish to submit a requirement to EGI, please use the [[New_Requirement_Manual| Requirement Tracking system]].  


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


== Open requirements ==
== Open requirements ==


{|style="background: #BCCDF0;"
{| style="background: #BCCDF0;"
!style="background:#BCCDF0;"|Color & meaning
|-
|-
|style="background-color:orange"|Orange indicates that TCB OR Technology providers has something to do with it through TCB.
! style="background:#BCCDF0;" | Explanation of colour codes used below
|-
|-
|style="background-color:yellowgreen"|Green indicates that Technology provider has something to do with it.  
| style="background-color:orange" | Orange indicates that the Technology Coordination Board, or technology providers in the board follow up the requirement.
|-
|-
|style="background-color:#E5ECF9"|Blue indicates UCST has something to do with it.  
| style="background-color:yellowgreen" | Green indicates that technology providers follow up the requirement through the EGI Helpdesk.
|-
|-
|style="background-color:yellow"|Yellow indicates UCB has something to do with it.  
| style="background-color:#E5ECF9" | Blue indicates that EGI.eu with the NGI support teams follow up the requirement.
|-
|-
| style="background-color:yellow" | Yellow indicates that the requirement needs input/decision from the User Community Board.
|-
| style="background-color:pink" | Pink indicates that the requirement needs input/decision from the Operations Management Board.
|}
|}


<br>


{|style="background: #BCCDF0;"
{| style="background: #BCCDF0;"
!style="background:white" colspan="2"|
|-
!style="background:#E5ECF9;"|Subject
! colspan="2" style="background:white" |  
!style="background:#E5ECF9;"|Status & History
! style="background:#FFFFFF;" | Subject
|-style="background:#E5ECF9;"
! style="background:#FFFFFF;" | Status &amp; History
|rowspan="6" colspan="2" style="background-color:orange"|(Topic 1) Increased stability and scalability for gLite WMS
|[https://rt.egi.eu/guest/Ticket/Display.html?id=2966 #2966 Enhanced WMS throughput]
|rowspan="6"|
2011, October 26: EMI confirmed that "WMS performance report" document will be provided by Marco Checchi in December<br>
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: [https://www.egi.eu/indico/conferenceDisplay.py?confId=464 minutes])<br>
2011, April 7: requirements were discussed at 5th TCB meeting (Action 02/07 open: [https://www.egi.eu/indico/conferenceDisplay.py?confId=410 minutes])<br>
2011, February 8: requirements were evaluated by UCST<br>
2010, December 7: New requirements entered into RT<br>
 
|-style="background:#E5ECF9;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=2970 #2970 The WMS is unstable and slow]
|-style="background:#E5ECF9;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=2972 #2972 WMS high workload]
|-style="background:#E5ECF9;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=1133 #1133 Increased stability and scalability for gLite WMS]
|-style="background:#E5ECF9;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=704 #704 Demand for WMS , stability of CREAMCE, gLite reliability at EMI]
|-style="background:#E5ECF9;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=698 #698 WMS stability and performance]
 
|-style="background:#E5ECF9;"
|rowspan="2" colspan="2" style="background-color:orange" |(Topic 2) Better (more verbose and informative) error messages
|[https://rt.egi.eu/guest/Ticket/Display.html?id=2965 #2965 Enhanced information feedback by middleware error messages]
|rowspan="2"|
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.<br>
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: [https://www.egi.eu/indico/conferenceDisplay.py?confId=501 minutes])<br>
2011, May 20: requirements were discussed at 6th TCB meeting (Action 05/02 open: [https://www.egi.eu/indico/conferenceDisplay.py?confId=464 minutes]) <br>
2011, February 8: requirements were evaluated by UCST<br>
2010, December 7: New requirements entered into RT<br>
 
|-style="background:#E5ECF9;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=2971 #2971 Error messages and Error status]
|-style="background:#E5ECF9;"
|rowspan="2" colspan="2" style="background-color:orange"| (Topic 4) Coherency of command line commands, parameters
|[https://rt.egi.eu/guest/Ticket/Display.html?id=2560 #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.<br>
2011, August 5: Requirement is at GGUS. GGUS REF: [https://ggus.eu/ws/ticket_info.php?ticket=73214 #73214]<br>
2011, July 14: New requirement entered into RT<br>
 
|-style="background:#E5ECF9;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=723 #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.<br>
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)<br>
2011, April 7: requirement was discussed at 5th TCB meeting (no action recorded [https://www.egi.eu/indico/conferenceDisplay.py?confId=410 minutes])<br>
2011, February 8: requirement was evaluated by UCST<br>
2010, December 8: New requirement entered into RT<br>
 
 
|-style="background:#E5ECF9;"
|rowspan="16"|(Topic 6) Data management
|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]
|
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.<br>
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)<br>
2011, September 20: The EMI presentations at the EGI Technical Forum showed that development of SE-LFC synchronisation is ongoing.<br>
Link to the "catalogue synchronisation working group" of EMI: https://twiki.cern.ch/twiki/bin/view/EMI/EmiJra1Syncat<br>
Link to the developers' tracker: https://savannah.cern.ch/task/?21787<br>
2011, May 11: requirements were discussed at UCB (no action recorded [https://www.egi.eu/indico/conferenceDisplay.py?confId=473 minutes])<br>
2011, May 10: requirements were evaluated by UCST<br>
2011, April 27: New requirements entered into RT<br>
 
|-style="background:#E5ECF9;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=917 #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.<br>
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)<br>
2011, September 20: The EMI presentations at the EGI Technical Forum showed that development of SE-LFC synchronisation is ongoing.<br>
Link to the "catalogue synchronisation working group" of EMI: https://twiki.cern.ch/twiki/bin/view/EMI/EmiJra1Syncat<br>
Link to the developers' tracker: https://savannah.cern.ch/task/?21787<br>
2011, March 30: requirement was evaluated by UCST<br>
2011, January 7: New requirement entered into RT<br>
 
|-style="background:#E5ECF9;"
|rowspan="3" style="background-color:orange"| (Subtopic 6.2) Stability and scalability of Data Management Services
|[https://rt.egi.eu/guest/Ticket/Display.html?id=922 #922 Management of many small files]
|
2011, July 1: Submitted to TCB<br>
2011, March 31: requirement was evaluated by UCST<br>
2011, January 7: New requirement entered into RT<br>
 
|-style="background:#E5ECF9;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=919 #919 Management of avalanches of job submission]
|
2011, July 1: Submitted to TCB<br>
2011, March 31: requirement was evaluated by UCST<br>
2011, January 7: New requirement entered into RT<br>
 
|-style="background:#E5ECF9;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=916 #916 DMS workload management]
|
2011, July 1: Submitted to TCB<br>
2011, March 31: requirement was evaluated by UCST<br>
2011, January 7: New requirement entered into RT<br>
 
|-style="background:#E5ECF9;"
|(Subtopic 6.3) Content synchronisation
|[https://rt.egi.eu/guest/Ticket/Display.html?id=924 #924 File updates]<br>
|
2011, November 7: requirement is at GGUS for clarification. REF [https://ggus.eu/ws/ticket_info.php?ticket=76058 #76058]<br>
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.<br>
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)<br>
2011, September 20: The EMI presentations at the EGI Technical Forum showed that development of SE-LFC synchronisation is ongoing.<br>
Link to the "catalogue synchronisation working group" of EMI: https://twiki.cern.ch/twiki/bin/view/EMI/EmiJra1Syncat<br>
Link to the developers' tracker: https://savannah.cern.ch/task/?21787<br>
2011, March 30: requirement was evaluated by UCST<br>
2011, January 7: New requirement entered into RT<br>
 
|-style="background:#E5ECF9;"
|rowspan="2"|Data lifetime management
|[https://rt.egi.eu/guest/Ticket/Display.html?id=2024 #2024 data lifetime management]
|
2011, October 10: GGUS StoRM SU provided the short guide using "volatile" feature.<br>
2011, September 28: UCST requested at GGUS to provide a StoRM-SRM-Client User Guide for a "volatile" feature usage.<br>
2011, August 22: StoRM (STOrage Resource Manager) is part of UMD and could be used as a solution.<br>
2011, July 28: Requirement is at GGUS. GGUS REF: [https://ggus.eu/ws/ticket_info.php?ticket=72997 #72997]<br>
2011, May 24: New requirement entered into RT<br>
 
|-style="background:#E5ECF9;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=2877 #2877 storage element and lifetime of data]
|
2011, October 10: GGUS StoRM SU provided the short guide using "volatile" feature.<br>
2011, September 28: Similar requirement [https://rt.egi.eu/guest/Ticket/Display.html?id=2024 #2024] is already in GGUS (REF: [https://ggus.eu/ws/ticket_info.php?ticket=#72997 #72997]). UCST requested at GGUS (REF: [https://ggus.eu/ws/ticket_info.php?ticket=72997 #72997]) to provide a StoRM-SRM-Client User Guide for a "volatile" feature usage.<br>
2011, September 26: New requirement entered into RT<br>
 
|-style="background:#E5ECF9;"
|rowspan="8"|Other
|[https://rt.egi.eu/guest/Ticket/Display.html?id=910 #910 Disk space management]<br>
|
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: [https://rt.egi.eu/rt/Ticket/Display.html?id=2394 #2394]<br>
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.<br>
2011, October 14: Asked requestors if they would be happy with the partial solution to be implemented<br>
2011, October 5: Partial solution depends on operations requirements [https://rt.egi.eu/guest/Ticket/Display.html?id=2766 #2766]. But in order to fulfill the complete requirement it should be discussed at TCB only.<br>
2011, September 28: Requirement is at GGUS for a confirmation.GGUS REF: [https://ggus.eu/ws/ticket_info.php?ticket=74741 74741]<br>
2011, March 31: UCST evaluates the requirement<br>
2011, January 6: New requirement entered into RT<br>
 
|-style="background:#E5ECF9;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=2491 #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.<br>
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.<br>
2011, July 25: Requirement is at GGUS (REF: [https://ggus.eu/tech/ticket_show.php?ticket=73806 #73806])<br>
2011, June 30: New requirement entered into RT<br>
 
|-style="background:#E5ECF9;"
|style="background-color:yellowgreen"|[https://rt.egi.eu/guest/Ticket/Display.html?id=1742 #1742 lcg-cp - background replication to other SEs]<br>
<center><b>BUG / No EMI release defined</b></center>
|
2011, September 6: Bug was created by GGUS in savannah tracker REF: [https://savannah.cern.ch/bugs/index.php?86446 #86446]<br>
2011, June 17: Requirement is at GGUS (REF: [https://ggus.org/tech/ticket_show.php?ticket=71646 #71646])<br>
2011, April 13: New requirement entered into RT<br>
 
|-style="background:#E5ECF9;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=926 #926 Distributed relational data management]
|
2011, November 1: UCST asked requestor to provide more details<br>
2011, October 21: UCST is investigating the use of RDBMS in Grid<br>
2011, October 26: Answer from GGUS:<br>
"Within EMI data there is no such activity.<br>
The access control to the multiple databases should also be aligned.<br>
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."<br>
2011, October 10: Requirement is at GGUS for a confirmation (REF: [https://ggus.eu/ws/ticket_info.php?ticket=75165 #75165])<br>
2011, March 31: UCST evaluates the requirement.<br>
2011, January 7: New requirement entered into RT<br>


|-style="background:#E5ECF9;"
|- style="background:#FFFFFF;"
|style="background-color:yellowgreen"|[https://rt.egi.eu/guest/Ticket/Display.html?id=909 #909 Improved replica selection]<br>
| rowspan="2" | (Topic 6) Data management
<center><b>BUG / No EMI release defined</b></center>
|
2011, April 20: Bug was created in savannah tracker REF: [https://savannah.cern.ch/bugs/index.php?66197 #66197]<br>
2011, March 31: Requirement is at GGUS (REF: [https://ggus.eu/ws/ticket_info.php?ticket=56928 #56928]).<br>
2011, March 31: UCST and UCB evaluates the requirement.<br>
2011, January 6: New requirement entered into RT<br>


|-style="background:#E5ECF9;"
|- style="background:#FFFFFF;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=2967 #2967 Enhanced SRM performance]
| style="background-color:orange" | <b>SUB-TOPIC 6.4</b> <rt ticketid="3230" field="Subject" />
|
|style="background-color:orange"| <rt ticketid="2024" field="Subject"/>  
2011, October 21: requestor was noticed that if he doesnt reply within 1 week, his requirement will be closed<br>
| <rt ticketid="2024" field="CF.{Status and History}"/>
2011, October 14: requestor is asked to provide more details<br>
2011, February 7: 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]
|- style="background:#FFFFFF;"
|
| rowspan="3" | Other
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:#FFFFFF;"
|style="background-color:yellowgreen"|[https://rt.egi.eu/guest/Ticket/Display.html?id=1626 #1626 Request for WebDav interface to LFC]<br>
| style="background-color:yellowgreen"|<rt ticketid="2491" field="Subject"/><br><center>'''BUG / Scheduled for ?'''</center>
<center><b>FEATURE / No EMI release defined</b></center>
| <rt ticketid="2491" field="CF.{Status and History}"/>  
|
2011, August 2: EMI task - "D2: Http/webdav for LFC" created. REF: [https://savannah.cern.ch/task/?21779 #21779]. Currently task is defined as "problemtatic" and is being investigated, no release planned yet. EMI Document REF: [https://twiki.cern.ch/twiki/pub/EMI/DeliverableDNA132/EMI-DNA1.3.2-1277543-Technical_Development_Plan-v1.0.pdf Technical Development Plan 1.3.2]<br>
2011, July 25: Requirement is at GGUS. REF: [https://ggus.eu/tech/ticket_show.php?ticket=72918 #72918]<br>
2011, March 28: New requirements entered into RT<br>


|-style="background:#E5ECF9;"
|- style="background:#FFFFFF;"
|rowspan="1" colspan="2"|Workflows
| style="background-color:yellowgreen" | <rt ticketid="1742" field="Subject"/><br> <center>'''BUG / No EMI release defined'''</center>  
|[https://rt.egi.eu/guest/Ticket/Display.html?id=928 #928 Scientific data flows]
| <rt ticketid="1742" field="CF.{Status and History}"/>
|
--->
2011, August 25: UCST provided the list of APIs table. REF [https://wiki.egi.eu/wiki/Service_APIs Service_APIs]<br>
2011, June 14: requirement was discussed at UCB meeting: (Action open 04/03 [https://www.egi.eu/indico/conferenceDisplay.py?confId=500 minutes])<br>
2011, March 31: requirement was evaluated by UCST<br>
2011, January 7: New requirement entered into RT<br>


|-style="background:#E5ECF9;"
|rowspan="4" colspan="2"|MPI
|style="background-color:yellowgreen"|[https://rt.egi.eu/guest/Ticket/Display.html?id=1391 #1391 Support for parallel jobs in JDL]<br>
<center><b>BUG / Scheduled for UMD-1.4.0 (30 January, 2012)</b></center>
|rowspan="3"|
2011, November 7: [http://repository.egi.eu/category/umd_releases/distribution/umd_1/ UMD-1.0] release does not include [http://www.eu-emi.eu/products/-/asset_publisher/z2MT/content/glite-mpi EMI gLite MPI] released package which doesn't pass the UMD quality criteria. EMI gLite MPI is planned to be included in [https://wiki.egi.eu/wiki/UMD_1.4.0_ContentsUMD 1.4.0] release scheduled in 2012 January.
<br>
2011, June 7: UCST prepared [https://wiki.egi.eu/wiki/MPI_User_Guide MPI User Guide]<br>
2011, May 12: EMI-1 Kebnekaise release including fixed MPI related bugs: [https://savannah.cern.ch/bugs/?77096 #77096], [https://savannah.cern.ch/bugs/?76971 #76971], [https://savannah.cern.ch/bugs/?58878 #58878].<br>
2010, December 8: New requirement entered into RT<br>


|-style="background:#E5ECF9;"
|style="background-color:yellowgreen"|[https://rt.egi.eu/guest/Ticket/Display.html?id=920 #920 Parallel jobs submission]<br>
<center><b>BUG / Scheduled for UMD-1.4.0 (30 January, 2012)</b></center>


|-style="background:#E5ECF9;"
|style="background-color:yellowgreen"|[https://rt.egi.eu/guest/Ticket/Display.html?id=727 #727 Proper MPI support]<br>
<center><b>BUG / Scheduled for UMD-1.4.0 (30 January, 2012)</b></center>


|-style="background:#E5ECF9;"
|- style="background:#FFFFFF;"
|style="background-color:yellowgreen"|[https://rt.egi.eu/guest/Ticket/Modify.html?id=3087 #3087 mpi-start should publish the version inside information system]<br>
| colspan="2" rowspan="2" | Client API
<center><b>BUG / Scheduled for release ? (Date ?)</b></center>
|- style="background:#FFFFFF;"
|
| style="background-color:orange" |<rt ticketid="2769" field="Subject"/>  
2011, November 2: bug was created. REF: [https://devel.ifca.es/mpi-start/ticket/52 #52]<br>
| <rt ticketid="2769" field="CF.{Status and History}"/>
2011, November 2: requirement is at GGUS. REF: [https://ggus.eu/tech/ticket_show.php?ticket=75847 #75847]<br>
2011, November 2: New requirement entered into RT<br>


|-style="background:#E5ECF9;"
|rowspan="2" colspan="2"|Client API
|-style="background:#E5ECF9;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=2769 #2769 Homogenous APIs for a middleware]
|
2011, September 29: [https://www.egi.eu/indico/conferenceDisplay.py?confId=613 8th TCB meeting] has some updates on SAGA API. [https://www.egi.eu/indico/getFile.py/access?sessionId=3&resId=0&materialId=0&confId=613 Deployment of SAGA] and inclusion into UMD is expected in Q1/2012.<br>
2011, August 25: New requirement entered into RT<br>


|-style="background:#E5ECF9;"
|rowspan="10" colspan="2"|Other
|[https://rt.egi.eu/guest/Ticket/Display.html?id=2561 #2561 EGI bubble help on EGI web sites]
|
2011, X: work in progress by UCST<br>
2011, July 14: New requirement entered into RT<br>


|-style="background:#E5ECF9;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=925 #925 Service certificates]
|
2011, October 14: EGI should proceed in two ways:<br>
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.  <br>
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. <br>
2011, September 20: Requestor would like to see robot certificates supported by all EGI CAs - grid-wide.<br>
2011, June 8: UCST provided the list of CAs supporting the robot certificates.<br>
2011, March 31: UCST evaluated the requirement.<br>
2011, January 7: New requirement entered into RT<br>
|-style="background:#E5ECF9;"
|style="background-color:yellowgreen"|[https://rt.egi.eu/guest/Ticket/Display.html?id=923 #923 Single sign-on]<br>
<center><b>TASK / Scheduled for EMI-2 (April 30, 2012)</b></center>
|
2011, October 14: EMI is developing STS service. Task: Simplified management of credentials [https://savannah.cern.ch/task/?21798 #21798]. Expected to be released in EMI-2.<br>
2011, October 10: Waiting for confirmation from GGUS when requirement could be implemented REF: [https://ggus.eu/ws/ticket_info.php?ticket=75175 #75175]<br>
2011, June 28: Requirement is at GGUS (REF:[https://ggus.eu/tech/ticket_show.php?ticket=73008 #73008]). Work is planned but not for EMI-2.<br>
2011, March 31: UCST evaluated the requirement.<br>
2011, January 7: New requirement entered into RT<br>
|-style="background:#E5ECF9;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=921 #921 Short jobs efficiency]
|
2011, October 31: another document for a requester was provided: [https://documents.egi.eu/document/725 VO and Resource Provider SLA Template]. Waiting for a comments.<br>
2011, October 10: requester says that current OLA document cant be used between user community and site/VO SLA<br>
2011, September 13: Waiting for a comments from requestor<br>
2011, June 16: UCST with help of Operations provided the RC OLA document which can be re-used for VO OLA, REF: [https://documents.egi.eu/public/ShowDocument?docid=463 Resource infrastructure Provider Operational Level Agreement]<br>
2011, March 31: UCST evaluated the requirement.<br>
2011, January 7: New requirement entered into RT<br>
|-style="background:#E5ECF9;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=918 #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<br>
2011, July 1: Was discussed at UCB meeting on [https://www.egi.eu/indico/conferenceDisplay.py?confId=500 2011, June 14 (meeting minutes)]<br>
2011, May 30: UCST evaluated the requirement.<br>
2011, January 7: New requirement entered into RT<br>
|-style="background:#E5ECF9;"
|style="background-color:yellowgreen"|[https://rt.egi.eu/guest/Ticket/Display.html?id=722 #722 Proper gLite services support and improvements and development at EMI]<br>
<center><b>TASK / Scheduled for EMI-2 (April 30, 2012)</b></center>
|
2011, October 28: GGUS confirmed and provided the list of committed tasks for EMI-ES service. REF: [https://savannah.cern.ch/search/?words=EMI-ES&type_of_search=task&Search=Search&exact=1#options click here]. The service and committed tasks should be implemented and available for EMI-2 release<br>
2011, October 10: UCST submitted GGUS ticket (REF: [https://ggus.eu/ws/ticket_info.php?ticket=75181 #75181]) to get a confirmation about the timeline of implementation.<br>
2011, July 12: EMI-2 release have work planned towards the unified user interface REF: [https://twiki.cern.ch/twiki/bin/view/EMI/DeliverableDNA132 see attachments]<br>
2011, March 30: UCST evaluated the requirement.<br>
2010, December 8: New requirement entered into RT<br>


|-style="background:#E5ECF9;"
|style="background-color:yellowgreen"|[https://rt.egi.eu/guest/Ticket/Display.html?id=2968 #2968 JDL does not offer GLUE attribute for available disk space on worker node]<br>
<center><b>BUG / Scheduled for EMI-2 (April 30, 2012)</b></center>
|
2011, October 14: savannah bug was created. REF [https://savannah.cern.ch/bugs/index.php?87799 #87799]<br>
2011, October 14: requirement is at GGUS. REF: [https://ggus.eu/ws/ticket_info.php?ticket=75297 #75297].<br>
2011, February 7: New requirement entered into RT<br>


|-style="background:#E5ECF9;"
|- style="background:#FFFFFF;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=2985 #2985 VO registration without certificates]
| colspan="2" rowspan="10" | Other
|
2011, October 21: UCST investigates the policy documents and other related issues with user/robot certificates.<br>
|- style="background:#FFFFFF;"
2011, October 14: requirement is at GGUS. REF [https://ggus.eu/ws/ticket_info.php?ticket=75304 #75304]<br>
| style="background-color:yellowgreen" | <rt ticketid="2947" field="Subject"/><br> <center>'''TASK / Should be finished on 2013-05-27'''</center>
2011, October 13: New requirement entered into RT.
| <rt ticketid="2947" field="CF.{Status and History}"/>


|-style="background:#E5ECF9;"
|[https://rt.egi.eu/guest/Ticket/Display.html?id=3070 #3070 NGIs publishing user-level accounting data to the authorised VO Resource Managers]<br>
|
2011, November 2: operations team will investigate the requirement in the next upcoming operations meeting<br>
2011, October 31: requestor was asked to provide more details.<br>
2011, October 31: requirement is under evaluation by UCST.<br>
2011, October 27: New requirement entered into RT.<br>
2011, October 26: requirement is at GGUS. REF: [https://ggus.eu/ws/ticket_info.php?ticket=75762 #75762]<br>
|}
|}


Line 355: Line 80:
== Useful links ==
== Useful links ==


*https://wiki.egi.eu/wiki/PDT:Policies_and_Procedures
*[[PDT:Policies_and_Procedures]]

Latest revision as of 11:11, 1 May 2013

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 Requirements_gathering_details. If you wish to submit a requirement to EGI, please use the Requirement Tracking system.


Open requirements

Explanation of colour codes used below
Orange indicates that the Technology Coordination Board, or technology providers in the board follow up the requirement.
Green indicates that technology providers follow up the requirement through the EGI Helpdesk.
Blue indicates that EGI.eu with the NGI support teams follow up the requirement.
Yellow indicates that the requirement needs input/decision from the User Community Board.
Pink indicates that the requirement needs input/decision from the Operations Management Board.


Subject Status & History
(Topic 6) Data management
SUB-TOPIC 6.4



Client API



Other

TASK / Should be finished on 2013-05-27

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=54625"