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) CMD-OS 1.1.0, 1.1.1, 1.1.2 released
2) CREAM 1.16.5 for CentOS7 available in Preview

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

1) CMD-OS 1.1.0, 1.1.1, 1.1.2 (C7/Xenial) released:

- CentOS7: bdii-infoprovider 0.7.0, rOCCI client 4.3.8, APEL SSM 2.1.7, Infrastructure Manager 1.5.1, Site BDII 1.2.1, ooi 1.1.1, keystone-VOMS 9.0.4, cASO 1.1.0
- Ubuntu Xenial: bdii-infoprovider 0.7.0, rOCCI client 4.3.8, Infrastructure Manager 1.5.1, ooi 1.1.1, keystone-VOMS 9.0.4, cASO 1.1.0

more details at the following links:
http://repository.egi.eu/2017/06/13/release-cmd-os-1-1-0/
http://repository.egi.eu/2017/06/13/release-cmd-os-1-1-1/
http://repository.egi.eu/2017/06/21/release-cmd-os-1-1-2/

2) The first release of CREAM (1.16.5) for CentOS7 is available in Preview. In the coming months it will be released in UMD as well, after the conclusion of the verification and staged rollout processes.
Please contact EGI Operations through a GGUS ticket in case you are interested in joining the staged rollout process.

For the installation and configuration, have a look at the following information:

- Link to the release notes: https://wiki.egi.eu/wiki/Preview_2.13.0#CREAM_1.16.5
- For configuring the Preview repository: https://wiki.egi.eu/wiki/Preview_Repository#Repository_configuration
Please be informed that wms.grid.icm.edu.pl service will be in decommissioning downtime starting 1 August 2017.

best regards, 
Marcin Stolarek 
ICM Site Operations Manager
IN2P3-CC will not support any more Biomed VO as production site (storage and computing). 

The decommissioning procedure for the CEs and SE hosted at IN2P3-CC has reached its end.
Biomed VO will be removed from the following CEs and SE on August 1st:
- CEs: cccreamceli09.in2p3.fr and cccreamceli10.in2p3.fr
- SE: ccsrm02.in2p3.fr

Regards,
David Bouvet for IN2P3-CC
Dear All, 

This is to inform you that the following hosts (services) at TOKYO-LCG2 will be decommissioned. 

lcg-ce02.icepp.jp (CREAM-CE)
lcg-ce03.icepp.jp (CREAM-CE)
lcg-wms01.icepp.jp (WMS)
lcg-lb01.icepp.jp (LB)

The downtime will start on 25/07/2017 00:00 (UTC). The services will be disabled and removed directory after the downtime.

Best regards, 
Tomoe
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.07.04 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.84          2017.06.26

------------------------------------------------------------------------------
   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.84-1 with Classic, SLCS and MICS profiles, encoded in
meta-package "ca-policy-egi-core-1.84-1" (new installs) and "lcg-CA-1.84-1"
(for sites upgrading from EGEE/JSPG releases).

IMPORTANT NOTICE:
  Sites that need compliance with the WLCG policy should install BOTH packages,
  or you will miss out the CERN WLCG IOTA CA specific exception. Details, see:
    https://documents.egi.eu/document/2745

  The next release 1.84 will add support for differentiated assurance in the
  EGI trust fabric infrastructure in the form of an additional trust anchor
  meta-package, which replaces the specific policy mechanism described above.
  Please review the documentation for the new software that will be needed
  to support differentiated assurance and the Collaborative Assurance Model.
  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, in as far as pertinent to
this release. Details are found in the newsletter https://www.eugridpma.org/


Changes from 1.83 to 1.84
-------------------------
(26 June 2017)

* Updated ROSA root certificate with extended 20yr valitity (RO)
* Updated contact details for CyGrid CA following transition to CYNET (CY)
* Removed obsoleted KISTI-2007 trust anchor - replaced by KISTIv3 (KR)
* Removed expiring LACGrid trust anchor a9082267 (BR)


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.84-1
Dear VO managers,
The following services, hosted by wms01.begrid.be, will be put in downtime on the 3rd of July :
- WMS
- LB
These services will be removed directly after the downtime.
Regards, St.

>>> More news <<<

Dear EGI users,

the gLite WMS service has been in best effort support since more than one year, and only for security fixes. As a consequence of the limited support effort available, together with the WMS developers, EGI Operations is proposing the following decommissioning plan:

•	WMS will be decommissioned by the end of 2017
•	After the end of the year all WMS instances will be removed from production.

As  alternative workload management system, EGI can provide support for migrating to the DIRAC service, a tool that provides features very similar to the WMS ones.

 If you are still using the WMS for your daily activities, please contact your VO managers in order to get in contact with EGI Operations: together the DIRAC supporters, we can set-up a server for your VO to start testing the new tool and provide support for the migration.

 We would encourage the VOs using WMS to coordinate with their users and contact EGI Operations as soon as possible, to plan the transition to other workload management system such as DIRAC, and not be unprepared when the WMS server are switched off. So please contact us per time in order to agree the transition to the new solutions.

Best reagrds,
EGI Operations
Dear site administrators, NGIs, ROCs, 

Cristina has announced yesterday on the EMI mailing lists [*]that the EMI repositories will be shut down on the 15th of June 2017. 

As previously advised by EGI Operations through different channels (broadcasts, EGI Operations meetings, OMB), EGI RCs are asked to switch to an alternative, as the EMI software is highly outdated or unsupported. 

Whatever still maintained or still used by EGI sites from EMI3 has been migrated already long time ago on the Preview repository https://wiki.egi.eu/wiki/Preview_Repository and properly updated by EGI Operations so far. Also a "third party repository" https://appdb.egi.eu/store/software/third.party.distribution has been set, containing a selection of software not distributed through UMD and managed by third party providers.  

The UMD distribution (versions 3 and 4) contains software that goes through a quality verification process performed by the UMD team for each product of each release, hence representing in general a better alternative than Preview and advised by EGI Operations.

RCs still using EMI are invited to switch to supported repositories to benefit from security and feature updates for their installed middleware. 

Please refer to http://repository.egi.eu/ for further information, or contact directly operations@egi.eu to get direct support. 

Thanks
 Vincenzo - EGI Operations

[*]<quote>
Dear EMI fans,

as you already know the EMI project finished on April 2013 and the last update pushed to its repositories happened on Nov. 2015.
Since then the effort concentrated in providing support to EGI Operations & Release teams to setup an equivalent repository where updates received from PTs could be pushed before their Staged-Rollout and release in official UMD repositories.

This EGI Community repository, UMD-preview [1], was announced on 23.02.2016 [2] as a mirror of EMI3 repository and since then was constantly updated with newer version of all the components part of UMD.

Therefore it is now the time to completly close any access to EMI repositories, and also to EMI documentation, since long time obsoleted. All repositories (packages and documentation) will be closed starting 15th of June 2017.

All sites are warmly adviced, if not done until now, to point your nodes to UMD repositories [3], production, testing or untested ones, or to UMD-preview mentioned above.

All the Best,
Cristina
</quote>
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.06.05 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.83          2017.05.29

------------------------------------------------------------------------------
   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.83-1 with Classic, SLCS and MICS profiles, encoded in
meta-package "ca-policy-egi-core-1.83-1" (new installs) and "lcg-CA-1.83-1"
(for sites upgrading from EGEE/JSPG releases).

IMPORTANT NOTICE:
  Sites that need compliance with the WLCG policy should install BOTH packages,
  or you will miss out the CERN WLCG IOTA CA specific exception. Details, see:
    https://documents.egi.eu/document/2745

  The next release 1.84 will add support for differentiated assurance in the
  EGI trust fabric infrastructure in the form of an additional trust anchor
  meta-package, which replaces the specific policy mechanism described above.
  Please review the documentation for the new software that will be needed
  to support differentiated assurance and the Collaborative Assurance Model.
  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.82 to 1.83
-------------------------
(29 May 2017)

* Added new trust anchor for accredited KISTI CA v3 (KR)
* Removed obsolete GEANT TCS G1 and G2 (old Comodo-backed) trust anchors:
  UTN-USERFirst-Hardware TERENA-eScience-SSL-CA AAACertificateServices
  UTNAAAClient TERENAeSciencePersonalCA UTN-USERTrust-RSA-CA
  TERENA-eScience-SSL-CA-2 TERENAeSciencePersonalCA2 (EU)

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.83-1
=============== 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".