Baseline

As baseline we use the Request for Change (Jira tickets) created any time the suppliers announce a new release of their services. In the tickets it is reported the date when a given change has been implemented and the version. The links in the table point to the Jira project where the tickets are collected by the "component" field.

Level of control

In the following tables there is a summary on how the several attributes are controlled.

List of Software/Hardware attributes

The changes affecting some of the attributes in the table below are not in the CHM scope because they are controlled in a federated way. For us transparency means either that the information is stored and maintained on GOCDB or that we are notified by email about any change.

Service component	Attribute...	Procedure / How it is controlled	Type of EGI CHM change	Approving body
GOCDB	Host certificates	Released through Sectigo	Normal/Standard	EGI Operations
	EGI scoped Service endpoints	registered in GRIDOPS-GOCDB	Normal	EGI CAB
	~~Release version that alter~~ API spec		Normal/Standard	EGI CAB
	GOCDB codebase version (https://semver.org/)		Normal/Standard	EGI CAB
	egi.eu domain for GOCDB		Normal/Standard	EGI CAB
	changes to Underlying STFC infrastructure with an impact to the service		Normal	EGI CAB

List of CIs/Attributes not related to software or hardware

The associated CIs/Attributes in the table below are not software-related and they are controlled by the EGI Federation in other ways (infrastructure procedures, management boards, etc.).

Service component	CI/Attribute...	Procedure / How it is controlled	Approving body
GOCDB	Information on service operators (individuals)	Registered on GOCDB	GOCDB
	NGIs/Operations Centres under the EGI Project	PROC02 Operations Centre creation PROC03 Operations Centre decommission Registered in GOCDB	n.a.
	RCs under EGI.eu	PROC09 Resource Centre Registration and Certification PROC11 Resource Centre Decommissioning Registered in GOCDB	EGI Operations
	people under EGI project	Registered in GOCDB
	people under EGI.eu	Registered in GOCDB
	Service Types	https://docs.egi.eu/internal/configuration-database/service-types/ Registered in GOCDB	OMB (and EGI Operations)
	GOCDB fields		OMB (and EGI Operations)
	Roles	https://docs.egi.eu/internal/configuration-database/users-roles/ Registered in GOCDB	OMB (and EGI Operations)
	RCs under each NGI	PROC09 Resource Centre Registration and Certification PROC11 Resource Centre Decommissioning Registered in GOCDB	The relevant NGI
	People under each NGI	Registered in GOCDB	The relevant NGI
	Service endpoints under each RC	PROC09 Resource Centre Registration and Certification PROC12 Production Service Decommissioning Registered in GOCDB	The relevant RC
	People under each RC	Registered in GOCDB	The relevant RC
	Downtimes	https://docs.egi.eu/providers/operations-manuals/man02_service_intervention_management/ https://docs.egi.eu/internal/configuration-database/downtimes/ Registered in GOCDB	The relevant RC
	Scope Tags	https://docs.egi.eu/internal/configuration-database/scopes/ Registered in GOCDB	GOCDB

Configuration items by type

The list of CIs for each type can be got either by browsing the GOCDB portal or by using its programmatic interface. In the following table there is an example of the available API calls

API Methods
Service types	Returns a list of valid service types and associated description
Operations Centres	Returns the list of OCs in the EGI scope
Resource Centres	Returns the list of production and certified RCs, in the EGI scope
Service Groups	Returns the list of service groups with the service endpoints under those groups.

Old information

History of changes

29 Apr 2019 Update GOCDB to version 5.7.3 - https://rt.egi.eu/rt/Ticket/Display.html?id=15445

21 Mar 2018 Change the CNAME DNS entry for goc.egi.eu to point to goc.stfc.ac.uk - https://rt.egi.eu/rt/Ticket/Display.html?id=14152

Page tree

Configuration database - GOCDB (CMDB)