logo operations poral

logo egi


Operations Portal is an EGI service provided by CCIN2P3,
co-funded by EGI.eu and EGI-Engage



Release Version : 4.1 - September 13th

For any contact, use this section: Contact Us



The Operations Portal is a central portal for the EGI operations management that offers a different capabilities, such as the broadcast tool, VO management facilities and various of dashboards (Security, VO and Operations) to facilitate infrastructure oversight.

Latest news

=============== Contents: ==================

1) Failures with CREAM-CE JobCancel probe: 
2) Decommissioning of dCache 2.10

============================================

1) Failures with CREAM-CE JobCancel probe:

Since the update of the CREAM probes on May 4th, several sites (about 13% of the total CREAM instances) were failing the emi.cream.CREAMCE-JobCancel probe: firstly it looked like a problem of job slots reservation, then it seems due to an unusual delay with which the blah blparser detects a job is cancelled.

See as reference the ticket https://ggus.eu/index.php?mode=ticket_info&ticket_id=128151

The delay is much higher than the timeout set in the probe (15 minutes), so a critical status is returned; in the previous version of the probes the returned status was UNKNOWN, and the problem wasn't noticed because the presence of other issues producing an UNKNOWN status as well.

If the bug will be confirmed, it will take some time to release and deploy a proper fix, so in order not to penalise further the sites, it was decided to exclude (temporary) the emi.cream.CREAMCE-JobCancel metric from the ARGO_MON_CRITICAL profile.
At the end of the month it will be performed a recomputation of the A/R statistics, so the failures of the past weeks won't be taken into account.

2) Decommissioning of dCache 2.13

All sites are invited to plan an upgrade of their 2.13 endpoints to a newer golden release, which can be 2.16 or 3.0.
The deadline is end of July 2017. Tests will get CRITICAL from June 1st on. 

Please have a look at PROC16 for further details: https://wiki.egi.eu/wiki/PROC16_Decommissioning_of_unsupported_software
Dear EGI AAI “CheckIn” user,

We would like to let you know that on Tuesday, 23 May, at 7:00 AM CEST, there will be scheduled down time for approximately 6 hours. We will be using this time to perform a major software upgrade of the ~okeanos infrastructure.

During this maintenance window, the EGI AAI “CheckIn” platform will be inaccessible. All operations around the platform, including federated authentication & authorisation, user registration and account management will resume immediately after the maintenance window.

We appreciate your patience and understanding,
The EGI AAI team
Dear all,
INFN-T1 site is decommissioning cream ce ce01-lcg.cr.cnaf.infn.it.
The timeline for the decommission is as follows:

- 12 may 2017 job submission will be disabled
- 19 may 2017 cream ce will be shutdown
- 19 may 2017 GOCDB will be updated

Andrea
Dear all,

The WMS ipngrid05.in2p3.fr will be removed on May 15, 2017. The WMS ipngrid28.in2p3.fr will remain available for your VO. So please, from now on, use the WMS ipngrid28.in2p3.fr.

Best regards,

Christophe DIARRA, a GRIF site admin.
Dear All, 

I would like to announce that UNICAN site has started the decommission procedure. 

Timeline
====
4th of April 2017
- Broadcast of timeline to VO managers and users.
- The all of its grid services will begin scheduled downtime until
19th of April , during which time VO managers and users can retrieve
data.

19th of April
- Start of scheduled Downtime until  4th of June

4th of June 2017
- *** HARD DEADLINE for VO Managers to retrieve all data from storage
elements. ***
- The resource centre status will be marked "suspended".
- Resource centre hardware and services may become inaccessible
without further notice to VO managers, users, etc. from this date.

5th of August 2017
- End of log retention period.
- Resource centre will be marked "closed".

Best regards

Antonio S. Cofiño
We wish to inform you that we are beginning the decommissioning process (https://wiki.egi.eu/wiki/PROC12) for the eubrazilcc VOMS service at UPV-GRyCAP in NGI_IBERGRID.

The VO affected is eubrazilcc VO
Below is a list of affected services and a decommissioning timeline.

Services affected
====
eubrazilcc-voms.i3m.upv.es (VOMS)

Timeline
====
3st April 2017
- GGUS Ticket opened

18th April 2017
- The service will begin scheduled downtime until 1st June 2017 

1st June 2017 
- Service may become inaccessible without further notice to VO managers, users, etc. from this date.
The service is set to "production=N" "monitored=N" in the GOCDB

1st July 2017 
- End of log retention period.
- VOMS Service will be marked "closed".

>>> More news <<<

Dear all,

EUGridPMA have announced a new set of CA rpms. Based on this IGTF release a new set of CA RPMs have been packaged for EGI. 

Please upgrade until 2017.04.03 at your earliest convenience. When this timeout is over, SAM will throw critical errors on CA tests if old CAs are still detected.

Please check https://wiki.egi.eu/wiki/EGI_IGTF_Release for more details 
 
EGI UMD software provisioning Team

The following release notes accompany this release:

European Grid Infrastructure EGI Trust Anchor release 1.82          2017.03.27

------------------------------------------------------------------------------
   For release DOCUMENTATION available on this EGI Trust Anchor release see   
               https://wiki.egi.eu/wiki/EGI_IGTF_Release                      
------------------------------------------------------------------------------

This is the EGI Trust Anchor release, based on the updated IGTF Accredited CA
distribution version 1.82-1 with Classic, SLCS and MICS profiles, encoded in
meta-package "ca-policy-egi-core-1.82-1" (new installs) and "lcg-CA-1.82-1"
(for sites upgrading from EGEE/JSPG releases).

IMPORTANT NOTICE:
  Your may install BOTH "egi-core" AND "lcg" meta-packages, according to your 
  policies. Note that your organisation or NGI may have a specific policy and
  may have added or removed CAs compared to the EGI core policy.
  Sites that need compliance with the WLCG policy should install BOTH packages,
  or you will miss out the CERN WLCG IOTA CA specific exception see 
  https://documents.egi.eu/document/2745 for details and the WLCG statement
  http://lcg-ca.web.cern.ch/lcg-ca/doc/WLCG-CERN-IOTA-statement-MB.pdf

  In the first quarter of 2017, full support for differentiated assurance
  profiles will be introduced in the EGI trust fabric infrastructure. This
  will take the form of an additional trust anchor meta-package, and replaces
  the specific policy mechanism described above. Such full support also
  required new software and configuration at each resource centre.
  We ask for your support in implementing the requisite changes, and deploy
  new trust anchor meta-packages and the new local policies only in unison.


The following notices are republished from the IGTF, inasfar as pertinent to
this release. Details are found in the newsletter https://www.eugridpma.org/


Changes from 1.81 to 1.82
-------------------------
(27 March 2017)

* Added new G2 UGrid trust anchor (UA)
* Extended validity for AEGIS CA (RS)
* Withdrawn discontinued FNAL KCA (US)
* Extended valitity for REUNA CA (CL)

The CA modifications encoded in both "requires" and "obsoletes" clauses (RPM)
and Conflicts/Replaced clauses (Debian)  have been incorporated in the above-
mentioned meta-packages.  This release is best enjoyed with  fetch-crl v3  or 
better, available from GNU/Linux OS add-on repositories Fedora, EPEL, Debian,
and from the IGTF at https://www.igtf.net/fetch-crl

Version information: ca-policy-egi-core = 1.82-1
=============== Contents: ==================

1) Monitoring of uncertified sites
2) Release of VAPOR 2.2
3) Decommissioning of dCache 2.10
4) UMD 4.4.0 released
5) UMD 3.14.8 released

============================================

1) Monitoring of uncertified sites

As discussed during the last Operations Meeting (https://indico.egi.eu/indico/event/3141/ ), it is finally available the monitoring of the uncertified sites.

The feature has been enabled on the test nagios server: https://argo-mon-uncert.cro-ngi.hr/nagios/
A report of the uncertified sites has been created on the ARGO development instance: http://web-egi-devel.argo.grnet.gr/lavoisier/status_report-site?report=CriticalUncert&accept=html

In order to being correctly monitored, the uncertified sites need to fill in the service endpoint information (queues for CREAM-CE and service URLs for SEs and other products in general) into GOC-DB.
It was also written an HOWTO for adding this piece of information into GOC-DB: https://wiki.egi.eu/wiki/HOWTO21

The Resource Centre registration and certification procedure has been updated accordingly (certification part, step 6): https://wiki.egi.eu/wiki/PROC09_Resource_Centre_Registration_and_Certification

If in your NGI there is any site undergoing the certification process, please use this new feature and, as usual, report any issue to us through a GGUS ticket.

2) Release of VAPOR 2.2

The VAPOR application v2.2 have been released : https://operations-portal.egi.eu/vapor

There are several improvements and new features: the computation of values of CPU and storages have been deeply reviewed, nevertheless some values are still not in line with the reality.
Next version will be focused on these computations to be able to provide better figures.
Check the release notes for more details : http://operations-portal.egi.eu/vapor/releases?name=VAPOR+2.2

Please have a look at the information displayed by the tool and report us any inconsistency you should spot.

3) Decommissioning of dCache 2.10

Just as a reminder, support for the dCache 2.10 ended at December 2016. All sites are invited to plan an upgrade their 2.10 endpoints to a newer golden release, which can be 2.13, 2.16 or even 3.0.
The deadline is end of April. The decommissioning campaign is ongoing: at the moment 12 instances of dCache 2.10 are still published on BDII. 

More information here: https://www.dcache.org/downloads/1.9/index.shtml https://wiki.egi.eu/wiki/Agenda-13-03-2017#Decommissioning_of_dCache_2.10

4) UMD 4.4.0 released

UMD 4.4.0 (regular release) has been released: http://repository.egi.eu/2017/03/23/release-umd-4-4-0/
It contains products for:

- CentOS7: Davix 0.6.4, GFAL 2.12.2, GFAL Utils 1.4.0, CGSI gSOAP 1.3.10, gfalFS 1.5.1, srm-ifce 1.24.1, yaim core 5.1.4, MyProxy 6.1.25, globus-default-security 6.4.0, dCache SRM client 3.0.9, ARC 15.03.12, canL 2.2.8, FTS3 3.5.8, dpm-dsi 1.9.0, GridFTP 11.8.1, GRAM5 13.16.0

- SL6: GFAL 2.12.2, GFAL Utils 1.4.0, CGSI gSOAP 1.3.10, gfalFS 1.5.1, FTS3 3.5.8, yaim core 5.1.4, Davix 0.6.4, canL 2.2.8, dCache SRM client 3.0.9

5) UMD 3.14.8 released

UMD 3.14.8 (emergency release) has been released: http://repository.egi.eu/2017/03/16/release-umd-3-14-8/ 
It contains a fix for canL.
We are  going to decommission the vo-nagios service provided by vo-nagios.physics.ox.ac.uk on 30th of March 2017. vo-nagios is managed for the GridPP project at Oxford and it is monitoring the following VOs
gridpp
lsst
pheno
t2k.org
snoplus.snolab.ca
vo.southgrid.ac.uk

vo-nagios is using sam-nagios software which is no longer maintained . The replacement for sam-nagios is the Argo service, which is currently not available for site installation. We are actively looking for a replacement for vo-nagios but there is no suitable alternative available yet. 
If you have been using vo-nagios.physics.ox.ac.uk and found it useful then please let us know at  lcg_manager@physics.ox.ac.uk to help us understand the level of importance of this service.

Thanks
VO-Nagios Admin
Dear all,

This is to inform you that the following services will be decommissioned by 12/04/2017.

LCG_KNU:
cluster3.knu.ac.kr(WMS)
cluster132.knu.ac.kr(LFC)

The downtime will start on 30/03/2017.

Best regards,
Han
There will be a downtime with the next GGUS maintenance on March 29th 2017.
This downtime is announced in GOCDB: https://goc.egi.eu/portal/index.php?Page_Type=Downtime&id=22456

We are moving GGUS system to a new database. Hence all interfaces to other systems like national ticketing systems, operations portal etc. will be down
Dear all,

EUGridPMA have announced a new set of CA rpms. Based on this IGTF release a new set of CA RPMs have been packaged for EGI. 

Please upgrade until 2017.03.06 at your earliest convenience. When this timeout is over, SAM will throw critical errors on CA tests if old CAs are still detected.

Please check https://wiki.egi.eu/wiki/EGI_IGTF_Release for more details 
 
EGI UMD software provisioning Team

The following release notes accompany this release:

European Grid Infrastructure EGI Trust Anchor release 1.81          2017.02.28

------------------------------------------------------------------------------
   For release DOCUMENTATION available on this EGI Trust Anchor release see   https://wiki.egi.eu/wiki/EGI_IGTF_Release                      
------------------------------------------------------------------------------

This is the EGI Trust Anchor release, based on the updated IGTF Accredited CA distribution version 1.81-1 with Classic, SLCS and MICS profiles, encoded in
meta-package "ca-policy-egi-core-1.81-1" (new installs) and "lcg-CA-1.81-1" (for sites upgrading from EGEE/JSPG releases).

IMPORTANT NOTICE:
Your may install BOTH "egi-core" AND "lcg" meta-packages, according to your  policies. Note that your organisation or NGI may have a specific policy and may have added or removed CAs compared to the EGI core policy. Sites that need compliance with the WLCG policy should install BOTH packages, or you will miss out the CERN WLCG IOTA CA specific exception see https://documents.egi.eu/document/2745 for details and the WLCG statement http://lcg-ca.web.cern.ch/lcg-ca/doc/WLCG-CERN-IOTA-statement-MB.pdf

In the first quarter of 2017, full support for differentiated assurance profiles will be introduced in the EGI trust fabric infrastructure. This will take the form of an additional trust anchor meta-package, and replaces the specific policy mechanism described above. Such full support also required new software and configuration t each resource centre.  We ask for your support in implementing the requisite changes, and deploy new trust anchor meta-packages and the new local policies only in unison.
 
The following notices are republished from the IGTF, inasfar as pertinent to this release. Details are found in the newsletter https://www.eugridpma.org/

Changes from 1.80 to 1.81
-------------------------
(28 February 2017)

* Added accredited DarkMatter classic QV-intermediate ICAs (AE)
  including QuoVadis Root CA 2 G3 and Root CA 3 G3 higher level CAs (BM)
* Updated contact information for EUN EG-GRID CA (EG)
* Withdrawn classic UKeScienceCA-2A in advance of repurposing (UK)

The CA modifications encoded in both "requires" and "obsoletes" clauses (RPM) and Conflicts/Replaced clauses (Debian)  have been incorporated in the above-
mentioned meta-packages.  This release is best enjoyed with  fetch-crl v3  or better, available from GNU/Linux OS add-on repositories Fedora, EPEL, Debian,
and from the IGTF at https://www.igtf.net/fetch-crl

Version information: ca-policy-egi-core = 1.81-1
The APEL Accounting Repository is being updated today, so there may be a delay in accounting data reaching the Portal. This will mostly affect cloud accounting which requires extra processing during the update.

The APEL Team.
CREAM CE at SiGNET site creamce.ijs.si will be decommissioned. Ticket tracking the process is
https://ggus.eu/index.php?mode=ticket_info&ticket_id=126333

CE will be in downtime from 20 Jan 12:00 UTC and will be removed on 6 Mar 12:00 UTC.
=============== Contents: ==================

1) Decommissioning dCache 2.10
2) CMD-OS 1.0.0 for OpenStack released
3) UMD 3.14.7 and UMD 4.3.2
4) Recommendation for reporting security incidents
5) GSTAT decommissioned

==========================================

1) Decommissioning dCache 2.10

Support for the dCache 2.10 ended at December 2016. As a consequence, according to EGI policies, dCache 2.10 must be decommissioned. All sites are invited to plan an upgrade their 2.10 endpoints to a newer golden release, that can be 2.13 (whose support ends on July 2017) or 2.16 (whose support ends on May 2018).
A decommissioning campaign will be started in the next days by EGI Operations to monitor the upgrade of the dCache 2.10 instances and follow up with the NGIs/sites.
Please consider that 2.13 gets out of support in only 6 months, and that the dCache team does not support the upgrade from 2.10 directly to 2.16.
More information here: https://www.dcache.org/downloads/1.9/index.shtml

2) CMD-OS 1.0.0 for OpenStack released

The very first version of CMD-OS, the Cloud Middleware Distribution for OpenStack Mitaka, have been released. It includes Keystone-VOMS 9.0.3, ooi 0.3.2, gridsite 2.3.3, Cloud BDII Information provider 0.6.12. For more details, please visit: http://repository.egi.eu/category/os-distribution/cmd-os-1/

3) UMD 3.14.7 and UMD 4.3.2 have been released on December 5th (fix releases), with an update for umd-release, fixing an issue with GPG keys.

4) Recommendation for reporting security incidents

In according to the EGI CSIRT Security Incident Handling Procedure (https://wiki.egi.eu/wiki/SEC01), please report any security incident to your local security team, your NGI Security Officer and the EGI CSIRT via abuse@egi.eu

5) GSTAT decommissioned

As announced in the past months, GSTAT has been decommissioned and replaced by VAPOR: https://operations-portal.egi.eu/vapor/
We would like to thank a lot ROC_AsiaPacific for having provided and managed such a powerful tool over severla years and projects.