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 componentAttribute......under direct EGI Foundation control...controlled by suppliers, whose changes need the EGI F. approval...where EGI F. must have transparencyProcedure / How it is controlledType of EGI CHM changeApproving body
Operations PortalHost certificates(tick)

Released through SectigoNormal/StandardEGI Operations?
Release version
(tick)

Normal/StandardEGI CAB
Service endpoint(s)
(tick)
Registered on GOCDB: EGI-OPSPORTALNormalEGI CAB








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

CIs under direct EGI F. control

CIs controlled by suppliers, whose changes need the EGI F. approval

CIs where EGI F. must have transparency

Procedure / How it is controlled

Approving body


Operations Portal






Service operators (individuals)

(tick)Registered on GOCDB: EGI-OPSPORTALProvider
List of Virtual Organisations (VOs)

(tick)



PROC14 VO Registration PROC13 VO Deregistration

Registered in the Operations Portal

EGI Operations

Old information

History of changes


  • No labels