Difference between revisions of "Track User Support Requirements"
Line 157: | Line 157: | ||
| [https://rt.egi.eu/guest/Ticket/Display.html?id=928 #928 Scientific data flows] | | [https://rt.egi.eu/guest/Ticket/Display.html?id=928 #928 Scientific data flows] | ||
| | | | ||
2011, December 8: An "official API table" it promised to be delivered by EMI in December.<br> | |||
- EGI.eu will organize joint workshops on workflows with the SHIWA project on the 9-10th of February: http://go.egi.eu/workflowworkshops<br> | |||
The EGI workshop aims to:<br> | |||
* Report about EGI services for workflow and workflow engine developers (including middleware APIs)<br> | |||
* Introduce workflow engines, workflows and related services that are available for EGI user communities<br> | |||
* Capture requirements from EGI communities concerning the further development of services for workflow service and workflow developers, providers and users<br> | |||
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> | 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> | ||
Line 185: | Line 191: | ||
| [https://rt.egi.eu/guest/Ticket/Display.html?id=2561 #2561 EGI bubble help on EGI web sites] | | [https://rt.egi.eu/guest/Ticket/Display.html?id=2561 #2561 EGI bubble help on EGI web sites] | ||
| | | | ||
2011, December 9: The RT system has a web gadget that can be customised for user communities' websites and can provide a simple interface to submit new requirements: http://egi.eu/user-support/gadgets/rt/<br> | |||
User communities are encouraged to use this gadget instead of the standard interface of RT. The gadget interface is extremely simple, does not need any help. <br> | |||
2011, X: work in progress by UCST<br> 2011, July 14: New requirement entered into RT<br> | 2011, X: work in progress by UCST<br> 2011, July 14: New requirement entered into RT<br> | ||
Line 190: | Line 198: | ||
| [https://rt.egi.eu/guest/Ticket/Display.html?id=925 #925 Service certificates] | | [https://rt.egi.eu/guest/Ticket/Display.html?id=925 #925 Service certificates] | ||
| | | | ||
2011, December 9: Robot certificate has been introduced in Germany. Discussions are ongoing in Spain and France about the introducing robot certs. The following wiki page includes the list: https://wiki.egi.eu/wiki/Robot_certificates<br> | |||
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> | 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> | ||
Line 206: | Line 215: | ||
| [https://rt.egi.eu/guest/Ticket/Display.html?id=918 #918 Middleware support for pilot jobs] | | [https://rt.egi.eu/guest/Ticket/Display.html?id=918 #918 Middleware support for pilot jobs] | ||
| | | | ||
2011, December 9: UCST is working on a survey to collect information from site admins, application developers and user communities about their preferences, views on better/different support for pilot job frameworks in EGI.<br> | |||
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> | 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> | ||
Line 221: | Line 231: | ||
| [https://rt.egi.eu/guest/Ticket/Display.html?id=2985 #2985 VO registration without certificates] | | [https://rt.egi.eu/guest/Ticket/Display.html?id=2985 #2985 VO registration without certificates] | ||
| | | | ||
2011, December 9: UCST is working on a reporting system to capture the number of robot users from the different communities. The reporting will be done through the wiki page at https://wiki.egi.eu/wiki/EGI_robot_certificate_users.<br> | |||
2011, October 31: requirement was discussed at UCB meeting ([https://www.egi.eu/indico/conferenceDisplay.py?confId=681 minutes]) and requester agreed for an alternative solution: UCST collects user statistics from robot certificate owners<br> 2011, October 21: UCST investigates the policy documents and other related issues with user/robot certificates.<br> 2011, October 14: requirement is at GGUS. REF [https://ggus.eu/ws/ticket_info.php?ticket=75304 #75304]<br> 2011, October 13: New requirement entered into RT. | 2011, October 31: requirement was discussed at UCB meeting ([https://www.egi.eu/indico/conferenceDisplay.py?confId=681 minutes]) and requester agreed for an alternative solution: UCST collects user statistics from robot certificate owners<br> 2011, October 21: UCST investigates the policy documents and other related issues with user/robot certificates.<br> 2011, October 14: requirement is at GGUS. REF [https://ggus.eu/ws/ticket_info.php?ticket=75304 #75304]<br> 2011, October 13: New requirement entered into RT. | ||
Revision as of 12:42, 8 December 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.
Open requirements
Color & meaning |
---|
Orange indicates that technology providers involved through the TCB follow up the requirement. |
Green indicates that technology providers involved through the EGI Helpdesk follow up the requirement. |
Blue indicates that UCST with the NGIs follow up the requirement. |
Yellow indicates that the requirement needs input/decision from UCB. |
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 | |||
#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, November 29: UCST asked requestors to provide version and type of the product they are using | |
#919 Management of avalanches of job submission | |||
#916 DMS workload management | |||
(Subtopic 6.3) Content synchronisation | #924 File updates |
2011, December 7: feature request is submitted #89637 | |
(Subtopic 6.4) 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, December 1: UCST provided additional details to GGUS StoRM SU about what is expected by user community. | ||
Other | #910 Disk space management |
2011, November 29: UCST rephrases the requirement by adding an examples to improve the life of the users by preventing the storage to become full and return failures related to this to users and their jobs. How this is achieved is up to the technology provider to decide. Example possibilities: | |
#2491 Redundancy of SE using lcg-cr command |
2011, December 2: UCST asked to create a feature request for a lcg_Utils in GGUS | ||
#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, December 6: UCST proposed to a requester either adjust his requirement (because it was rejected by GGUS) or provide more details for submitting it to TCB | ||
#909 Improved replica selection |
2011, April 20: Bug was created in savannah tracker REF: #66197 | ||
#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, December 8: An "official API table" it promised to be delivered by EMI in December.
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, December 9: The RT system has a web gadget that can be customised for user communities' websites and can provide a simple interface to submit new requirements: http://egi.eu/user-support/gadgets/rt/ | |
#925 Service certificates |
2011, December 9: Robot certificate has been introduced in Germany. Discussions are ongoing in Spain and France about the introducing robot certs. The following wiki page includes the list: https://wiki.egi.eu/wiki/Robot_certificates | ||
#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, November 22: operations team are working on a wide NGI-VO SLA document | ||
#918 Middleware support for pilot jobs |
2011, December 9: UCST is working on a survey to collect information from site admins, application developers and user communities about their preferences, views on better/different support for pilot job frameworks in EGI. | ||
#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, December 9: UCST is working on a reporting system to capture the number of robot users from the different communities. The reporting will be done through the wiki page at https://wiki.egi.eu/wiki/EGI_robot_certificate_users. | ||
#3070 NGIs publishing user-level accounting data to the authorised VO Resource Managers |
2011, November 22: operations team are working on a wide NGI-VO SLA document | ||
#2947 EMI/UMD grid elements available as virtual machine images |
2011, October 3: requirement already has savannah Task. REF: #22854 |
Solved requirements
Please click on -> Solved_user_requirements