Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @


From EGIWiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

General information

News from URT

Staged rollout updates

  • STORM 1.11.10
  • DCACHE 2.13.27

Next releases

  • UMD 4.1.0 RC ready, release by May
    • goal: add SL6 to UMD4 in order to allow dismission of UMD3
    • SL6 migrated from UMD3 to UMD4, non-supported products have been removed
    • CentOS7 --> only Frontier for now, a new release will be made including dCache and ARGUS server

Preview repository

On April 1st it was released Preview 2.0.0

The second major release of Preview was created for releasing the products available on CentOS 7 and Scientific Linux 6 platforms that are about to be included in UMD4.

The products available in this first release are only for CentOS 7 platform:

  • ARC
  • Argus
  • dcache
  • fts3
  • site-bdii
  • top-bdii

The Scientific Linux 6 products will be available in one of the next updates.

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.

Operational issues

Aligning Fedcloud sites to the A/R procedures

  • EGI Operations proposal to align Fedcloud sites to the A/R related procedures used for the grid sites
  • based on the availability reliability of monitored services in cloudmon, EGI Operations will start follow up with underperforming sites as we are doing for every grid sites
  • sites will NOT be suspended for a/r performance at least until end of May
  • in parallel EGI Operations will start PROC08 to include cloud probes in the EGI_CRITICAL and EGI profiles used for A/R computations (IN PROGRESS)

The proposed timeline is:

  • February 2016:
    • EGI Operations will check the status of the production cloud services in order to understand which issues (if any) the site has and provide help to NGIs and sites;
    • Start of the integration of cloud probes in EGI CRITICAL profile(current set+openstack): To be agreed with the ARGO team, PROC08 will be followed
  • June 2016:
    • Starting notification of sites eligible for suspension

Comparing the two profiles

see the FedCloud meeting slides for details

  • nagios probes
New profile Old profile
    • org.nagios.OCCI-TCP
    • eu.egi.OCCI-IGTF
  • org.openstack.nova
    • eu.egi.Keystone-IGTF
    • org.nagios.Keystone-TCP
    • org.nagios.OCCI-TCP
    • org.nagios.CDMI-TCP
  • How the sites figures are changed:
March April
improvements 2 6
unchanged 11 7
worsening 9 10
#SSLVerifyClient optional_no_ca

Correct setting:

SSLVerifyClient optional
  • CETA-GRID (-42%): failures seem due to the grid-part of the site
  • CYFRONET-CLOUD (-100%):
    • same for march, problem not solved yet: wrong endpoint URL on GOC-DB
  • IFCA-LCG2 (-24%): until April 6th the failures were due to eu.egi.OCCI-IGTF probe, then fixed
    • the other failures occurred in the month were due to the OpenStack upgrade to Liberty version
  • IN2p3-IRES (-6%) and NCG-INGRID-PT (-7%): failures due to the grid part of the site
  • TR-FC1-ULAKBIM (-6%): failures registered between April 7th and 11th in both the reports
  • HG-09-Okeanos-Cloud: (SOLVED)
    • the token the AA mechanism served was expired
    • failures with the CAs probe
      • there were some invalid CAs files
  • PRISMA-INFN-BARI: it must be closed


Decommissioning SL5

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:

  • If we can't contact them, the site needs to make sure that there is no firewall blocking from accessing the argus 'pap' port
  • If we are not authorized, the site needs to add the right ACE to their argus authorization

The current status of the infrastructure can be found:

  • In the secmon nagios (not sure you have access to this):

  • On the security dashboard:

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

  • "Ok" means ok
  • "Unknown" means that we can't contact them
  • "High" means that we are not authorized
  • "Critical" means that argus is not pull rules from

The parent ticket is

2016_05_09 UPDATE pending tickets:

Other 5 servers are failing again


Monthly Availability/Reliability

A/R report on ARGO:

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

EGI Operations Support activities stopped

  • EGI Operations Support activity stopped on April 30, 2016
  • Operations Support GGUS SU to be decommissioned
  • all corresponding tickets will be moved to EGI Operations (except resource allocation)

Next meeting