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 components	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
WMS, DMS, Web Portal, Rest server	Service endpoints				registered in GRIDOPS-DIRAC4EGI	Normal	EGI CAB
	Release version:  Apply one or more patches Apply a new release Upgrade to a new version					Normal/Standard	EGI CAB
	Changes to underlying infrastructure with an impact to the service: Update VM OS (service migration) Adding/Deleting a VM Adding/Deleting a Database					Normal/Standard	EGI CAB
	Host certificates				Released through Sectigo	Normal/Standard	EGI Operations

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...	...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
WMS, DMS, Web Portal, Rest server	Service operators (individuals)				Registered on GOCDB: GRIDOPS-DIRAC4EGI	Supplier
	Add/delete a VO				upon a service request through a GGUS ticket	Supplier
	Add/Delete/Modify essential service. e.g. File Catalog				upon a service request through a GGUS ticket	Supplier
	Add/delete a users group / tag / priorities				upon a service request through a GGUS ticket	Supplier
	Modify user registration (e.g., Add/delete/ban a user to a VO)				upon a service request through a GGUS ticket	Supplier
	Add/Delete/Modify VO specific services				upon a service request through a GGUS ticket	Supplier
	Add/delete a site				upon a service request through a GGUS ticket	Supplier
	Temporary ban a site / Modify site parameters (VO supported, computing elements, storage elements, queues, tags,...)				upon a service request through a GGUS ticket	Supplier