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
Storage element	Host certificates				part of the daily operation of a RC is to keep the systems up-to-date following the management indications	not applicable	RCs Administrators
	Release version				The RCs install a new version when it is available in the UMD distribution	not applicable	RCs Administrators
	Service endpoint(s)				Registered on GOCDB: SRM, webdav, xrootd	not applicable	RCs Administrators
	STORM middleware				the product team releases a new version which is then included to UMD	not applicable	the product team
	dCache middleware				the product team releases a new version which is then included to UMD	not applicable	the product team
	EOS middleware				the product team releases a new version which is then included to UMD	not applicable	the product team
	xrootd middleware				the product team releases a new version which is then included to UMD	not applicable	the product team

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
Storage elements	Service operators (individuals)				Registered on GOCDB within each site: Sites list	RCs Administrators