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 108: Line 108:
|- style="background:#E5ECF9;"
|- style="background:#E5ECF9;"
| rowspan="6" | Other  
| rowspan="6" | Other  
| style="background-color:orange" rowspan="1" |[https://rt.egi.eu/guest/Ticket/Display.html?id=910 #910 Disk space management]<br>
| style="background-color:orange" rowspan="1" |<rt ticketid="910" field="Subject"/><br>  
|
| <rt ticketid="910" field="CF.{Status and History}"/>
2012, January 16: TCB recognized the topic and related tickets as the need for EGI community and Endorses it.<br>
2011, November 29: UCST rephrases the requirement by adding an examples and service versions: 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:<br>
- introducing storage quotas on storages (per user and/or per job), supporting users and jobs with tools to watch their quotas<br>
- monitors that check SE status and alarm site admins to free up space by removing or moving files elsewhere when the storage starts to fill up. Providing tools for the admins to perform these tasks<br>
- monitors that can automatically remove or move files in case of fill up<br>
2011, November 23: 9th TCB F2F meeting [https://www.egi.eu/indico/conferenceDisplay.py?confId=672 (minutes)]. UCST submitted formally the [https://www.egi.eu/indico/getFile.py/access?sessionId=17&resId=0&materialId=0&confId=672 Catalog of Requirements] containing the details and descriptions of the requirements.<br>
- The requirement was returned for clarification to rephrase what is actually requested from technology providers<br>
2011, November 9: requester asked to provide solution for a long-term:<br> 1. consider a semi-automatic file migration tool, used by VO managers to migrate user files (e.g. Globus online)<br> 2. provide storage "advices" based on the status of the current resources (e.g. "you should store this file there")<br> 3. propose a storage model (e.g. advised number of replicas and placement) based on available resources and file types<br> 2011, November 8: VO Services team produced the instructions based on LFCBrowser tool for use in migrating the files from SE/LFC by VO managers if SE should be decommissioned. REF: [https://wiki.egi.eu/wiki/VO_Services/Services_and_Tools_Portfolio#SE_intervention:_LFCBrowseSE SE intervention, LFCBrowseSE ]<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;"
|- style="background:#E5ECF9;"

Revision as of 15:09, 1 February 2012

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


TOPIC 2


TOPIC 4


(Topic 6) Data management SUB-TOPIC 6.1


SUB-TOPIC 6.2



FEATURE / Scheduled for ?
SUB-TOPIC 6.4


Other
#2491 Redundancy of SE using lcg-cr command
BUG / Scheduled for ?

2011, December 15: Bug was created in savannah #89914.
2011, December 2: UCST asked to create a feature request for a lcg_Utils in GGUS
2011, November 23: suggestion from GGUS to start using ARC middleware resources, those do solve many problems, including this one as well
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, 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
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 (REJECTED):
"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 / Scheduled for EMI-2 (April 30, 2012)

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 / Scheduled for EMI-2 (April 30, 2012)

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, December 8: An "official API table" it promised to be delivered by EMI-2 release in April of 2012.
- EGI.eu will organize joint workshops on workflows with the SHIWA project on the 9-10th of February: http://go.egi.eu/workflowworkshops
The EGI workshop aims to:

  • Report about EGI services for workflow and workflow engine developers (including middleware APIs)
  • Introduce workflow engines, workflows and related services that are available for EGI user communities
  • Capture requirements from EGI communities concerning the further development of services for workflow service and workflow developers, providers and users

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 / UMD-1.4.0 Released (19 Deccember, 2011)

2012, January 17: Owners of MPI requirements were invited to try latest MPI package using UMD-1.4.0 production release and provide comments and feedback.
2011, December 19: UMD-1.4.0 is out including MPI packages. Note: WMS is still not in UMD, it is planned to be included in UMD 1.5.0 release. It means that MPI features are not working using WMS, but only direct submission for CREAM-CE
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 / UMD-1.4.0 Released (19 Deccember, 2011)
#727 Proper MPI support
BUG / UMD-1.4.0 Released (19 Deccember, 2011)
#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 #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
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, November 22: operations team are working on a wide NGI-VO SLA document
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, 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.
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, 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.
2011, October 31: requirement was discussed at UCB meeting (minutes) and requester agreed for an alternative solution: UCST collects user statistics from robot certificate owners
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 22: operations team are working on a wide NGI-VO SLA document
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

#2947 EMI/UMD grid elements available as virtual machine images
TASK / ?

2011, October 3: requirement already has savannah Task. REF: #22854
2011, October 3: New requirement entered into RT.

Solved requirements

Please click on -> Solved_user_requirements

Useful links