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. In the following tables there is a summary on how the attributes are controlled. 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. 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.).Baseline
Level of control
List of Software/Hardware attributes
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 Virtual Appliance Catalogue (Application DB) Release version Normal/Standard EGI CAB Service endpoint(s) Registered on GOCDB: GRIDOPS-APPDB Normal EGI CAB Dynamic DNS Service endpoint(s) Registered on GOCDB: EGI-DDNS Normal EGI CAB Release version Managed manually Normal EGI CAB VM Management (Fedcloud sites) Host certificates part of the daily operation of a RC is to keep the systems up-to-date following the management indications not applicable RCs Administrators Release version The RCs install a new version when it is available in the UMD distribution not applicable RCs Administrators Service endpoint(s) Registered on GOCDB: org.openstack.nova, org.openstack.horizon, eu.egi.cloud.accounting not applicable RCs Administrators List of attributes not related to software or hardware
Service component Attributes... ...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 Virtual Appliance Catalogue (Application DB) Service operators (individuals) Registered on GOCDB: GRIDOPS-APPDB Provider Dynamic DNS Service operators (individuals) Registered on GOCDB: EGI-DDNS Provider VM Management (Fedcloud sites) Service operators (individuals) Registered on GOCDB: FedCloud sites Provider
Overview
Content Tools