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.

(the helpdesk GGUS is not yet in the EGI Jira project; related changes are considered as Standard; for the moment we use the release notes as baseline)

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. 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
GGUS	Release version					Normal/Standard	EGI CAB
	Service operators (individuals)				Registered on GOCDB: GRIDOPS-GGUS	Standard	provider
	Service endpoint(s)				Registered on GOCDB: GRIDOPS-GGUS	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	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
GGUS	ticket fields				OMB/Operations Registered in GGUS	EGi Operations
	SUs categories				OMB/Operations Registered in GGUS	EGI Operations
	SUs decommission				ISRM5 Verify Helpdesk SUs are working and perform a periodic review of them	EGI Operations
	SUs creation				service request	provider

Old information

History of changes

All release notes: https://ggus.eu/index.php?mode=release_notes

29 Mar 2018 13938, 14149

11 Jan 2018 https://rt.egi.eu/rt/Ticket/Display.html?id=13971 (installation of security patches)

29 Nov 2017 applied the following changes:

• https://rt.egi.eu/rt/Ticket/Display.html?id=13848 (installation of security patches)
• https://rt.egi.eu/rt/Ticket/Display.html?id=13859 (renew certificate of GGUS Remedy server)

28 Sep 2017 applied the following changes

• https://rt.egi.eu/rt/Ticket/Display.html?id=13631 (Regular GGUS maintenance for installing security patches)
• https://rt.egi.eu/rt/Ticket/Display.html?id=13592 (new SU for the EGI Marketplace)

26 Jul 2017 applied the following changes:

• https://rt.egi.eu/rt/Ticket/Display.html?id=13210 (GGUS: installation of security patches)
• https://rt.egi.eu/rt/Ticket/Display.html?id=13211 (GGUS: enable IPv6 on GGUS servers)