1. Proposal for GOCDB workload management
GOCDB Advisory Group, 18/06/2008
Gilles Mathieu

2. Outline Current situation Technical proposal Proposed procedures
Put requests on GOC-DB
Follow-up requests and ongoing developments
Technical proposal
Public wish list, development list and bug tracking
Proposed procedures
GAG role and interactions with OAT
“Fast track” for certain requests
Summary and proposed workflow

3. Current situation (1) Development work stopped in Dec. 07
Lack of manpower
Urgent maintenance only
Long list of requirements
It is spread
It needs updating
Follow up
Not easy to track what has been asked

4. Current situation (2) Development resumes with EGEE-III
Current work and priorities
Sort accumulated requirements
Publish them
Implement them
Solve already known bugs
Move forward…

5. GOC-DB Development list (1)
Current situation
How to submit requests and report bugs?
Submit a ticket in GGUS
Submit a bug in Savannah
Send a mail to UKI ROC
How to track what has been asked?
Browse GGUS tickets assigned to GOCDB
Browse GOCDB Savannah project
Public list on UKI ROC web site (outdated)
… Other repositories are not publicly available

6. GOC-DB Development list (2)
Ideas
Have a central repository for bug reports
Have a public wish list
Have a clear, official, public development list
Proposal
Use Savannah
To be agreed today

7. GOC-DB Development list (3)
Known bugs and bug reports
Savannah bug tracker
Wish list
Savannah Support Manager
Official list of ongoing developments
Savannah Task Manager

8. GAG role Agree on developments Follow up development items
Browse wish list and accept/refuse items
If needed, forward to appropriate bodies
Validate development plans
Follow up development items
Define priorities
Set deadlines
Agree on release plans

9. Other tracks OAT “Fast track”
For high level agreements or general issues
Will give general orientation (architecture, model)
“Fast track”
Not every request needs discussion
We can’t wait for 10 persons to meet every 3 months to decide everything
Use common sense to decide what needs discussion and what can be done quickly

10. Proposed ways Discussion on GAG mailing list Phone meetings
Face to face meetings
Browse wish list and accept/refuse items
If needed, forward to appropriate bodies
Validate development plans
Follow up development items
Define priorities
Set deadlines
Agree on release plans

11. Proposed workflow USER no GGUS UKI Helpdesk Mail/ other yes GOCDB AG
Does the request need discussion? no
GGUS
UKI Helpdesk
Mail/ other
Request
yes
GOCDB AG
Discuss request
GOCDB Admin
Savannah
Wish List
Request
Status=new
Does it need further validation? no
yes
OAT
Discuss request
Official Development List
Is the request acceptable?
Request
Status=accepted
Request
Status=refused
yes no