Difference between revisions of "GOCDB"
m |
|||
Line 5: | Line 5: | ||
<br> | <br> | ||
GOC DB is one of [[Core EGI Activities|EGI core services and]] part of [http://www.egi.eu/services/catalogue/fed-ops.html EGI Federated Operations service]. | GOC DB is one of [[Core EGI Activities|EGI core services and]] part of [http://www.egi.eu/services/catalogue/fed-ops.html EGI Federated Operations service]. | ||
<br> | |||
{| class="wikitable" | {| class="wikitable" | ||
Line 16: | Line 16: | ||
| '''Tool Category and description''' | | '''Tool Category and description''' | ||
| ''EGI Core service'' | | ''EGI Core service'' | ||
GOCDB is a central registry to record information about the topology of an e-Infrastructure. This includes entities such as Operations Centres, Resource Centres, service endpoints and their downtimes, contact information and roles of users responsible for operations at different levels. The service enforces a number of business rules and defines different grouping mechanisms and object-tagging for the purposes of fine-grained resource filtering. | GOCDB is a central registry to record information about the topology of an e-Infrastructure. This includes entities such as Operations Centres, Resource Centres, service endpoints and their downtimes, contact information and roles of users responsible for operations at different levels. The service enforces a number of business rules and defines different grouping mechanisms and object-tagging for the purposes of fine-grained resource filtering. | ||
|- | |- | ||
Line 38: | Line 38: | ||
|- | |- | ||
| '''Release schedule''' | | '''Release schedule''' | ||
| [[GOCDB/Release Schedule]] | | [[GOCDB/Release Schedule]] | ||
[[https://wiki.egi.eu/wiki/PROC23 EGI Release Procedure]] | [[https://wiki.egi.eu/wiki/PROC23 EGI Release Procedure]] | ||
|- | |- | ||
| '''Release notes''' | | '''Release notes''' | ||
Line 48: | Line 49: | ||
|- | |- | ||
| '''Related OLA''' | | '''Related OLA''' | ||
| ''https://documents.egi.eu/public/ShowDocument?docid=2170'' | | ''https://documents.egi.eu/public/ShowDocument?docid=2170'' (May-2014-April2015) <br> ''https://documents.egi.eu/public/ShowDocument?docid=2456'' (May2015-April2016) <br>'' https://documents.egi.eu/public/ShowDocument?docid=2770'' (May2016-April2017)<br>QoS Reports: ''https://documents.egi.eu/public/ShowDocument?docid=2284''<br> Availability/Reliability Reports: ''https://documents.egi.eu/public/ShowDocument?docid=2324'' | ||
|- | |- | ||
| '''Test instance url''' | | '''Test instance url''' | ||
Line 55: | Line 56: | ||
| '''Documentation''' | | '''Documentation''' | ||
| [[GOCDB/Documentation Index]] | | [[GOCDB/Documentation Index]] | ||
[https://wiki.egi.eu/w/images/d/d3/GOCDB5_Grid_Topology_Information_System.pdf Executive Summary] | [https://wiki.egi.eu/w/images/d/d3/GOCDB5_Grid_Topology_Information_System.pdf Executive Summary] | ||
|- | |- | ||
| '''License''' | | '''License''' | ||
Line 69: | Line 71: | ||
| https://github.com/GOCDB | | https://github.com/GOCDB | ||
|- | |- | ||
| '''Data Privacy / Code of Conduct''' | | '''Data Privacy / Code of Conduct''' | ||
| [[GOCDB/ | | [[GOCDB/data privacy]] | ||
| | | <br> | ||
|} | |} | ||
Line 103: | Line 105: | ||
#*Frequency: every 2-3 months | #*Frequency: every 2-3 months | ||
= Documentation = | = Documentation = | ||
[[GOCDB/Documentation Index|Enter GOCDB Documentation Index Here]] | [[GOCDB/Documentation Index|Enter GOCDB Documentation Index Here]] |
Revision as of 10:23, 27 April 2016
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 the topology of an e-Infrastructure. This includes entities such as Operations Centres, Resource Centres, service endpoints and their downtimes, contact information and roles of users responsible for operations at different levels. The service enforces a number of business rules and defines different grouping mechanisms and object-tagging for the purposes of fine-grained resource filtering. | |
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 (May-2014-April2015) https://documents.egi.eu/public/ShowDocument?docid=2456 (May2015-April2016) https://documents.egi.eu/public/ShowDocument?docid=2770 (May2016-April2017) QoS Reports: https://documents.egi.eu/public/ShowDocument?docid=2284 Availability/Reliability Reports: https://documents.egi.eu/public/ShowDocument?docid=2324 | |
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 | |
Data Privacy / Code of Conduct | GOCDB/data privacy |
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