GOCDB
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Tools menu: | • Main page | • Instructions for developers | • AAI Proxy | • Accounting Portal | • Accounting Repository | • AppDB | • ARGO | • GGUS | • GOCDB |
• Message brokers | • Licenses | • OTAGs | • Operations Portal | • Perun | • EGI Collaboration tools | • LToS | • EGI Workload Manager |
Grid Configuration Database (GOCDB) contains general information about the sites participating to the production Grid. Accessed by all the project actors (end-users, sitemanagers, NGI mangers, support teams, VO managers), by other tools and by third party middleware in order to get Grid topology. The portal has a single central installation but interested NGIs can download and install their own instance.
GOC DB is one of EGI core services and part of EGI Federated Operations service.
Tool name | Grid Configuration Database (GOCDB) |
Tool Category and description | EGI Core service
(GOCDB) is a central registry to record information about different entities such as the Operations Centres, the Resource Centres, service endpoints and the contact information and roles of people responsible for operations at different levels. |
Tool url | http://gocdb.egi.eu/ (primary instance) http://goc.dl.ac.uk (failover) |
gocdb-admins@mailman.egi.eu | |
GGUS Support unit | GOCDB |
GOC DB entry | https://goc.egi.eu/portal/index.php?Page_Type=Site&id=335 |
Requirements tracking - EGI tracker | https://rt.egi.eu/rt/Dashboards/5541/GOCDB-Requirements |
Issue tracking - Developers tracker | https://github.com/GOCDB/gocdb/issues |
Release schedule | GOCDB/Release Schedule |
Release notes | Release notes |
Roadmap | GOCDB/Roadmap |
Related OLA | https://documents.egi.eu/public/ShowDocument?docid=2170 |
Test instance url | https://gocdb-test.esc.rl.ac.uk |
Documentation | GOCDB/Documentation Index |
License | gLite/Apache 2 |
Provider | STFC |
Notifications | GOCDB/notifications |
Source code | https://github.com/GOCDB/gocdb |
Change, Release and Deployment
This sections are providing detailed agreement in terms of requirements gathering, release and deployment of GOC DB which extend Instructions for Operations Tools teams
- All requirements are gathered in EGI Request Tracker
- Prioritization and testing is done by development team, in case of need separated OTAG team will be introduced
- EGI RT statuses of requests are as follow
- New - newly recorded in system
- Accepted - accepted by OTAG team
- Rejected - rejected by OTAG team
- Open - (In progress) development team is implementing change
- Resolved - released
- Stalled - on hold
- Priority of requests are as follow
- None - 0
- Low - 1
- Normal - 2
- High - 3
- Immediate (i.e. emergency) - 4
- Standard changes (routine actions, no need for approval)
- changes related to database information update
- bug fixing - restoring service to expected functionality
- Emergency changes (implemented without approval but subject of post-review)
- Security incidents
- Releases
- Frequency: every 2-3 months
Documentation
Enter GOCDB Documentation Index Here
Extract information from GOCDB
Information is extracted by means of the GOCDB Programmatic Interface
Service end-points
- Find GOCDB service endpoints by service type
- Find all service-end points that are NOT monitored
Resource Centres
Find sites in GOCDB by status:
- Find all Certified Resource Centres
- Find all Certified sites in a given NGI/EIRO. Example: NGI_DE
- Find all Candidate Resource Centres
- Find all Suspended Resource Centres
- Find all Uncertified Resource Centres
- Find all Local Resource Centres (i.e. outside of the EGI scope)
- Find all Test/Certified Resource Centres
- Find all Test/Uncertified Resource Centres
- Get status transition of a site: example
- Find all Certified/Local Resource Centres
- Find all Uncertified/Local Resource Centres
- List of CANDIDATE/SUSPENDED sites waiting to be certified
Status transitions
Get status transition of a site: example