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.

• Notebooks

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	Attributes...	...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
JupyterHub Helm	Release version				Managed in the GitHub repo: https://github.com/EGI-Federation/notebooks-operations	Normal/Standard	EGI CAB
	Allowed VOs				Managed in the GitHub repo: https://github.com/EGI-Federation/notebooks-operations	Normal/Standard	EGI CAB
	Other JupyterHub configuration				Managed in the GitHub repo: https://github.com/EGI-Federation/notebooks-operations	n.a.	Provider
	Service endpoint(s)				Registered on GOCDB: EGI-NOTEBOOKS	Normal/Standard	EGI CAB
Jupyter images	Release version				Managed in the GitHub repo: https://github.com/EGI-Federation/notebooks-operations	Normal/Standard	EGI CAB
Hub image	Release version				Managed in the GitHub repo: https://github.com/EGI-Federation/notebooks-operations	Normal/Standard	EGI CAB
Kubernetes	Release version				Managed in the GitHub repo: https://github.com/EGI-Federation/notebooks-operations	n.a.	Provider

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	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
JupyterHub	Service operators (individuals)				Registered on GOCDB: EGI-NOTEBOOKS	Provider