1. GOCDB current status and plans
COD-16, 16/06/2008
Gilles Mathieu

2. Outline Current situation About GOCDB development list…
Wish list, development list and bug tracking
Agreement on developments and priorities
Provisional development plan

3. Current situation (1) Development work stopped in Dec. 07
Lack of manpower
Urgent maintenance only
Long list of requirements
It is spread (GGUS, Savannah, UKI helpdesk…)
It needs updating
Lack of documentation

4. Current situation (2) Development resumes with EGEE-III Priorities
More manpower 
Priorities
Sort accumulated requirements
Implement them
Solve bugs
Move forward…

5. GOC-DB Development list (1)
Current situation is a bit messy
How to submit requests and report bugs?
Submit a ticket in GGUS
Submit a bug in Savannah
Send a mail to UKI ROC
Post on a mailing list, hoping for an answer
How to track what has been asked?
Browse GGUS tickets assigned to GOCDB
Browse GOCDB Savannah project
Public list on UKI ROC web site (completely outdated)
Ask your crystal gazer (if you don’t have any, your local butcher will do)

6. GOC-DB Development list (2)
Ideas
Have a unique entry point for bug reports
Have a wish list
Have a clear official development list
Proposal
Use Savannah
To be agreed by GOCDB Advisory Group

7. Agreeing on tasks and priorities
GOCDB Advisory Group (GAG)
No, it’s not a gag
Representatives from ROCs, CODs, sites, Operations tools
Will validate and prioritize requests put on GOCDB
OAT
For high level agreements or general issues
Will give general orientation (architecture, model)

8. Agreeing on tasks and priorities
Short 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

9. GOC-DB interactions with CODs
CODs have requests for GOC-DB
Stored information
Way to handle sites
General concerns, best practices, failover…
How to address them?
Within COD meetings 
Through the wish list in Savannah
Phone, mail, send an owl… I’ll centralize and update requirements list accordingly

10. Provisional dev plans Short term (2-3 months) Medium term (6 months)
Bring back GOCDB to a maintainable state
Start concrete work for GOCDB failover
Medium term (6 months)
Achieve failover work
Start working on model evolution and APIs
Longer term (1 year)
“Think different, think service” © - Coordination with other tools
Build modules, package and distribute
Commercialize and make a lot of money (or not)