Difference between revisions of "Track User Support Requirements"
Line 79: | Line 79: | ||
|-style="background:#E5ECF9;" | |-style="background:#E5ECF9;" | ||
|rowspan=" | |rowspan="15"|(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=" | |rowspan="7"|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;" | |-style="background:#E5ECF9;" |
Revision as of 13:02, 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 | |
#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. | |
#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. | |
#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.
| ||
(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. |
#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. | ||
(Subtopic 6.2) Stability and scalability of Data Management Services | #922 Management of many small files |
2011, July 1: Submitted to TCB | |
#919 Management of avalanches of job submission |
2011, July 1: Submitted to TCB | ||
#916 DMS workload management |
2011, July 1: Submitted to TCB | ||
(Subtopic 6.3) Content synchronisation | #924 File updates |
2011, November 7: requirement is at GGUS for clarification. REF #76058 | |
Data lifetime management | #2024 data lifetime management |
2011, October 10: GGUS StoRM SU provided the short guide using "volatile" feature. | |
#2877 storage element and lifetime of data |
2011, October 10: GGUS StoRM SU provided the short guide using "volatile" feature. | ||
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 | |
#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. | ||
#1742 lcg-cp - background replication to other SEs |
2011, September 6: Bug was created by GGUS in savannah tracker REF: #86446 | ||
#926 Distributed relational data management |
2011, November 1: UCST asked requestor to provide more details | ||
#909 Improved replica selection |
2011, April 20: Bug was created in savannah tracker REF: #66197 | ||
#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 | ||
#1626 Request for WebDav interface to LFC |
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 | ||
Workflows | #928 Scientific data flows |
2011, August 25: UCST provided the list of APIs table. REF Service_APIs | |
MPI | #1391 Support for parallel jobs in JDL |
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.
| |
#920 Parallel jobs submission | |||
#727 Proper MPI support | |||
#3087 mpi-start should publish the version inside information system |
2011, November 2: bug was created. REF: #52 | ||
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. | ||
Other | #2561 EGI bubble help on EGI web sites |
2011, X: work in progress by UCST | |
#925 Service certificates |
2011, October 14: EGI should proceed in two ways: | ||
#923 Single sign-on |
2011, October 14: EMI is developing STS service. Task: Simplified management of credentials #21798. Expected to be released in EMI-2. | ||
#921 Short jobs efficiency |
2011, October 31: another document for a requester was provided: VO and Resource Provider SLA Template. Waiting for a comments. | ||
#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 | ||
#722 Proper gLite services support and improvements and development at EMI |
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 | ||
#2968 JDL does not offer GLUE attribute for available disk space on worker node |
2011, October 14: savannah bug was created. REF #87799 | ||
#2985 VO registration without certificates |
2011, October 21: UCST investigates the policy documents and other related issues with user/robot certificates. | ||
#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 |
Solved requirements
Please click on -> Solved_user_requirements