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 CIs/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...	...under direct EGI Foundation control	...controlled by suppliers, whose changes need the EGI F. approval	...where EGI F. must have transparency	Procedure / How it is controlled	Type of EGI CHM change	Approving body
ARGO, SAM	Host certificates				Released through Sectigo	Normal/Standard	EGI Operations
	Release version					Normal/Standard	EGI CAB
	Service endpoint(s)				Registered on GOCDB: GRIDOPS-SAM, GRIDOPS-MON	Normal	EGI CAB
Messaging	Host certificates					Normal/Standard	EGI Operations
	Release version					Normal/Standard	EGI CAB
	Service endpoint(s)				Registered on GOCDB: GRIDOPS-MSG	Normal	EGI CAB

List of attributes not related to software or hardware

The associated 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...	...under direct EGI F. control	...controlled by suppliers, whose changes need the EGI F. approval	...where EGI F. must have transparency	Procedure / How it is controlled	Approving body
ARGO, SAM	Service operators (individuals)				Registered on GOCDB: GRIDOPS-SAM, GRIDOPS-MON	ARGO, SAM
	List of endpoints to be monitored and attributes				Registration on GOCDB	n.a.
	Service types and Metrics associations				PROC07 Adding new probes to ARGO Registered in Poem	OMB
	Monitoring profiles (which probes are critical, which are for alarms, which are for testing)				PROC06 Setting Nagios test status to operations PROC08 Management of the EGI OPS Availability and Reliability Profile Registered in Poem	OMB
	the monitoring probes					technology providers
Messaging	Service operators (individuals)				Registered on GOCDB: GRIDOPS-SAM, GRIDOPS-MON	Messaging