Table of content


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 componentAttributes......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
Accounting PortalRelease version
(tick)

Normal/StandardEGI CAB
Service endpoint(s) 
(tick)
Registered on GOCDB: GRIDOPS-ACCPORTALNormalEGI CAB
Accounting RepositoryRelease version
(tick)

Normal/StandardEGI CAB
Service endpoint(s)
(tick)
Registered on GOCDB: GRIDOPS-APELNormalEGI CAB


List of 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 componentAttributesCIs under direct EGI F. controlCIs controlled by suppliers, whose changes need the EGI F. approvalCIs where EGI F. must have transparencyProcedure / How it is controlledApproving body
Accounting Portal






Service operators (individuals)

(tick)Registered on GOCDB: GRIDOPS-ACCPORTALProvider

Accounting Repository

Service operators (individuals)

(tick)Registered on GOCDB: GRIDOPS-APELProvider
List of accounting metrics(tick)

proposed to and discussed by the OMBOMB
endpoints sending accounting records

(tick)Registered on GOCDB: GRIDOPS-APEL

Sub-pages

Old content

History of changes

on  Update the APEL central repository, introducing long running VM support https://rt.egi.eu/rt/Ticket/Display.html?id=14187

on  applied on the Accounting Portal the following change: https://rt.egi.eu/rt/Ticket/Display.html?id=13512 (Request for change: Fourth Release of the Accounting Portal)

on  applied:

  • No labels