From EGIWiki
Jump to: navigation, search


General information


Staged rollout updates

Preview repository

on 2016-05-17 released:

Generic information about Preview repository:

Note: EGI provides the preview repository without any additional quality assurance process, but the products are released as they are provided by the product team. EGI recommends the use of the UMD repositories, which contain software verified through the quality assurance process of UMD.


Central monitoring

RFC proxy will be default

EGI Operations Support activities stopped

missed to update any documents.

Monthly Availability/Reliability

A/R report on ARGO:

List of the underperforming RCs for (at least) 3 consecutive months:

Decommissioning SL5

Status and actions

NGIs argus server not properly configured

Some time ago (more than a year I think), EGI ran a campaign to have NGIs run a "NGI Argus" service. This campaign resulted in new services being added to goc-db for each NGI.

Unfortunately, as explained in the OMB in February, our monitoring is currently unable to check the deployment of these services: - For 6 services, our monitoring cannot contact the NGI Argus - For 18 services, our monitoring is not authorized to get the right information from the NGI Argus - For 1 service, our monitoring indicates that the NGI Argus is not properly configured and does not pull the rules from

In the end, only 5 services are properly configured and monitored!

The changes are rather easy:


The current status of the infrastructure can be found:

On the security dashboard, each NGI should have a "argus-ban" result:

The parent ticket is

2016_06_13 UPDATE pending tickets:

FedCloud status

A/R Profile March April May
improvements 2 6 5
unchanged 11 7 5
worsening 9 10 12


Next meeting

Personal tools