Track User Support Requirements

Main

Submit

Track

UMD (TCB)

Operations (OMB)

User Support (UCB)

Status at UCB

Name of the topic	Related requirement tickets	Status of tickets	Date of flagging the topic as priotiry by the UBC	Summary & Actions
1.Increased stability and scalability for gLite WMS		Waiting for technical details from ticket submitters. Deadline to answer: 21/04/2011 Full details received for 1 ticket: #704 from VO hone	30 Nov 2010	Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced. Feb 2011: UCST invited the providers of reusable tools to comment on the requirements. Neither negative, nor positive evidences emerged. 1st of April 2011: UCST sent 2nd reminder to ticket submitters to provide technical details.
2.Better (more verbose and informative) error messages		Waiting for technical details from ticket submitters. Deadline to answer: 21/04/2011 Partial details received for 2 tickets: #712 from NGI_IL #1147 from Life Sciences Grid Community	30 Nov 2010	Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced. Feb 2011: UCST invited the providers of reusable tools to comment on the requirements. Neither negative, nor positive evidences emerged. 1st of April 2011: UCST sent 2nd reminder to ticket submitters to provide technical details.
3.Fixing the known bugs before adding new features		Waiting for technical details from ticket submitters. Deadline to answer: 21/04/2011	30 Nov 2010	Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced. Feb 2011: UCST invited the providers of reusable tools to comment on the requirements. Neither negative, nor positive evidences emerged. 1st of April 2011: UCST sent 2nd reminder to ticket submitters to provide technical details.
4.Coherency of command line commands, parameters and APIs	Resolved #665	Waiting for technical details from ticket submitters. Deadline to answer: 21/04/2011 Partial details received for 1 ticket: #1148 from Life Sciences Grid Community	30 Nov 2010	Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced. Feb 2011: UCST invited the providers of reusable tools to comment on the requirements. Neither negative, nor positive evidences emerged. 1st of April 2011: UCST sent 2nd reminder to ticket submitters to provide technical details.
5.Better feedback about jobs, automated resubmission of jobs that are stuck on sites	Resolved #660	Waiting for technical details from ticket submitters. Deadline to answer: 21/04/2011 Partial details received for 1 ticket: #657 from HealthGrid	30 Nov 2010	Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced. Feb 2011: UCST invited the providers of reusable tools to comment on the requirements. Neither negative, nor positive evidences emerged. 1st of April 2011: UCST sent 2nd reminder to ticket submitters to provide technical details.

UCB Requirements Dashboard

This is a TEST and information should NOT be used as valid.

UCB Requirements dashboard is a dynamic table of the requirements and it should help maintain and track the UCB process.

Open - requirement is open for discussions, consistency check & technical details gathering is in progress
Accepted - requirement has full technical details
Expired - tickets having status 'Open' had no response for 20days

RT Tags: UCB is using 'Custom Tag' field to group tickets into Topics e.g. 'Custom Tag = ucb1' means Topic 1 and so on.

All GGUS Tickets Note: because GGUS keyword search doesnt accept more than one keyword, we can use Ctrl+F browser based search.

				UCB Tagged Requirement Status
Date of the Topic	Name of the Topic	GGUS related tickets	Summary & Actions	Open	Accepted	Expired (no response for 20days)
30 Nov 2010	1. Increased stability and scalability for gLite WMS	All tickets at GGUS gLite WMS Support Unit workload manager crashes Comment: all the tickets for WMS are related to the separate components of WMS. Proxy related or job submission related issues are critical because these services which WMS provides within it's components are critical for the users.	Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced. Feb 2011: UCST invited the providers of reusable tools to comment on the requirements. Neither negative, nor positive evidences emerged. 1st of April 2011: UCST sent 2nd reminder to ticket submitters to provide technical details.
30 Nov 2010	2. Better (more verbose and informative) error messages	dpm-register error messages uninformative WMS logging says failure when there is none wms logging insufficient WMSUI: Very unhelpful message when a wrong type of proxy was used to submit a job Comment: all GGUS tickets related to errors have expressions used by submitters and supporters: "looks like error is about...", "seems that error is about..." - it means that nor user nor supporter finds the errors being meaningful and informative. There's a clear need of EGI software database of errors provided by Middleware developers. Existing Middleware Components Errors Database	Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced. Feb 2011: UCST invited the providers of reusable tools to comment on the requirements. Neither negative, nor positive evidences emerged. 1st of April 2011: UCST sent 2nd reminder to ticket submitters to provide technical details.
30 Nov 2010	3. Fixing the known bugs before adding new features	Comment: at the moment there are no known tickets at GGUS related to that topic, but this issue is known to all users and should be used as a rule in any software (middleware)development.	Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced. Feb 2011: UCST invited the providers of reusable tools to comment on the requirements. Neither negative, nor positive evidences emerged. 1st of April 2011: UCST sent 2nd reminder to ticket submitters to provide technical details.
30 Nov 2010	4. Coherency of command line commands, parameters and APIs	Comment: at the moment there are no known tickets at GGUS related to that topic, but this issue is known to applications or web portals developers and should be used as a rule in any software (middleware) development.	Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced. Feb 2011: UCST invited the providers of reusable tools to comment on the requirements. Neither negative, nor positive evidences emerged. 1st of April 2011: UCST sent 2nd reminder to ticket submitters to provide technical details.
30 Nov 2010	5. Better feedback about jobs, automated resubmission of jobs that are stuck on sites	Comment: in all cases if there's a problem with jobs - user is asked to provide detailed information e.g. which WNs were used, or information which is not provided by middleware tools. e.g. Jobs failed at CSCS-LCG2 Middleware or it's components (WMS) should be developed pragmatic enough that use cases when jobs a stuck at sites on any reason the meaningful information should be given back to the user if jobs resubmission without users intervention is not possible. At the moment in most cases user has to find administrator of the site to understand what he is doing wrong or if the site is not working as expected.	Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced. Feb 2011: UCST invited the providers of reusable tools to comment on the requirements. Neither negative, nor positive evidences emerged. 1st of April 2011: UCST sent 2nd reminder to ticket submitters to provide technical details.

Requirements are discussed, prioritized, accepted & grouped into the topics at UCB

User Support Status

Requirements in process by User Support

	Requirement Status
User Support	New	Open	Accepted	Stalled	Expired (no response for 20days)
Support Service
Applications Database
Training Services
VO Services
Web Site
Other
Support Action
Consultancy
Documentation
Training
Other
User Tools and Applications
Domain specific applications
Generic Tools
Other