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

Dear Colleagues,
please note, on

  Jan, 31st, 2017, 00:00h

we are decommissioning our CREAM-CEs

  grid-cr0.desy.de
  grid-cr1.desy.de

for the LHC VOs

  ATLAS
  CMS
  LHCb

The pledged computing resources at DESY-HH are available on

  grid-arcce0.desy.de
  grid-arcce1.desy.de

Best regards,
Andreas Gellrich
Can sites be careful when changing their accounting client settings that they do not inadvertently re-publish old data. This has an inordinate effect on the APEL service, much more than publishing the same number of new jobs.

If you observe that you have Sync test failures flagged in Nagios and wish to solve this, please open a GGUS ticket so that the APEL Team can advise on how and what to republish and on when to schedule such publishing, Don't just try gap publishing even though the sync test message suggests this

Thanks in anticipation, 

The APEL Team
Dear VO Managers and VO Users,

With regret, we wish to inform you that we are beginning the decommissioning
process (https://wiki.egi.eu/wiki/PROC11) for the Resource Centre INDIGO-CATANIA-STACK in
NGI_IT. The following VOs are affected at this Resource Centre:

fedcloud.egi.eu and vo.indigo-datacloud.eu

The aim is to change the status of the resource centre to "suspended" in
GOCDB by 1st February 2017. Below is a list of affected services and a
decommissioning timeline.

Kind regards,
Marco Fargetta

List of services decommissioned with the site:
- stack-server-02.ct.infn.it (org.openstack.nova)
- indigo-sb.ct.infn.it (eu.egi.cloud.vm-metadata.vmcatcher)
- stack-server-02.ct.infn.it (eu.egi.cloud.vm-management.occi)
- indigo-sb.ct.infn.it (eu.egi.cloud.accounting)
- indigo-sb.ct.infn.it (eu.egi.cloud.information.bdii)

Timeline:
- 10/01/2017: Ticket for decommissioning and broadcast to VO managers and users.
- 11/01/2017: Start downtime of the site
- 01/02/2017: Site marked as suspended. Services will become unavailable
- 01/06/2017: End of log retention period and site marked as closed
The wms marwms.in2p3.fr has been stopped. It will not be restarted.
FGI JYU decommisioning
  	
Detailed Description:
  	 
Old FGI is being replaced with FGCI. As a consequence the following services will be decommissioned:

electra-grid.chem.jyu.fi (ARC-CE) https://goc.egi.eu/portal/index.php?Page_Type=Service&id=2865
electra-grid.chem.jyu.fi (gLite-APEL) https://goc.egi.eu/portal/index.php?Page_Type=Service&id=6363

Grid queues will be drained and endpoints removed from GOCDB on 17.1.2017.
All services and data will be permanently deleted after 90 days counting from 17.1.2017.

Affected ROC/NGI: NGI_FI
Affected Site: FI_JYU 
GGUS ticket : https://ggus.eu/index.php?mode=ticket_info&ticket_id=125781
Dear VO Managers,
the site INFN-NAPOLI-CMS is under decommissioning.

The site will be put in downtime to prevent new activities.

>>> More news <<<

======= Content ========
1) UMD releases
2) Decommission of mon.egi.eu and cloudmon.egi.eu
======================

1) On Nov 23rd two revisions of UMD 3.14.6 (SL6) and UMD 4.3.1 (SL6/CentOS7) have been released:

a) UMD 3.14.6 includes lcmaps-plugins-vo-ca-ap, needed for supporting the IGTF IOTA profile of CAs

b) UMD 4.3.1 includes:

*** CentOS7

lcas-lcmaps-gt4-interface 0.3.0-0.3.1
lcmaps 1.6.6
lcas 1.3.19
glExec 1.2.3
glExec-WN 1.3.0
lcmaps-plugins 1.7.1

*** SL6

ARGUS 1.7 (regular 4.3.0 shipped only CentOS7 version)

2) Decommission of mon.egi.eu and cloudmon.egi.eu

a) on 29 November all the cloud probes were moved to the central servers, and cloudmon.egi.eu was dismissed on Dec 1st.
All the probes are executed using the following certificate subjects:

/DC=EU/DC=EGI/C=HR/O=Robots/O=SRCE/CN=Robot:argo-egi@cro-ngi.hr
/DC=EU/DC=EGI/C=GR/O=Robots/O=Greek Research and Technology Network/CN=Robot:argo-egi@grnet.gr

b) On Dec 6th 2016 the old SAM GridMon box mon.egi.eu, housing central ATP and POEM, was decommissioned. These services became obsolete when we switched to central monitoring instances in July.

- The VO SAM instances will not be affected as they are using local ATP and POEM.
- Remaining NGI SAM instances rely on central ATP and will no longer get topology updates, so this gives their administrators extra incentive to decommission them.
Dear VOs and users,

It was found by the CMS experiment that a WN at the GRIF/IRFU site was silently corrupting files (thanks, CMS).
After investigations, it appears that a CPU on the machine was silently corrupting files while they were beeing compressed on the machine, only if the compression task was beeing run on core #8 of the CPU socket #0, in addition to it's sibling hyperthreaded core #28.

Unfortunately, this hardware issue remained unnoticed because uncaught by the various hardware and software system checks - neither Dell nor Intel diagnostic tools could find and report it.
Unfortunately also, root files seem to be affected. Or at least files created by the CMS software which includes root and recompiled copies of various compression tools.
It was found also that files compressed with the "bzip2" system tool was also corrupted, but not files created with the system lzma or gzip tools for instance.

Final bad news : we have no way to identify which files -your files- were produced on that machine.

We would therefore like to warn you about this problem, giving you as much details as possible.

The machine name is : wn328.datagrid.cea.fr
The ethernet MAC address of the main ntework interface is : 00:8C:FA:F2:93:1E
The host IPs are : 192.54.205.14 (v4) and 2001:660:3031:110:10::328/64 (v6)
The host entered production on Sep. 21 @ 9H49.
The host is running an up to date SL 6.8

Off course, the host was finally taken out of production (thanks again to cms ;) ) on November 25 2016@10H01 CET time, and the bad cpu should be changed this week.

We would like to apologize for this unwelcome hardware failure, as we already know finding the affected files will be a hard work that you would all have prefered to avoïd.
Best regards

The GRIF/IRFU admins
Site egee.fesb.hr will be decommissioned on December 15th. Currently there is 69 GB of biomed data stored on SE se.fesb.egi.cro-ngi.hr. CE element is already disabled.

Parent GGUS ticket is here: https://ggus.eu/index.php?mode=ticket_info&ticket_id=125331&come_from=submit

Best regards
emir
Old FGI is being replaced with FGCI. As a consequence the following services will be decommissioned:

aesyle-grid.fgi.csc.fi (ARC-CE) - https://goc.egi.eu/portal/index.php?Page_Type=Service&id=2859
aesyle-grid.fgi.csc.fi (gLite-APEL) -https://goc.egi.eu/portal/index.php?Page_Type=Service&id=5545
usva.fgi.csc.fi (gLite-APEL) - https://goc.egi.eu/portal/index.php?Page_Type=Service&id=6356
usva.fgi.csc.fi (ARC-CE) - https://goc.egi.eu/portal/index.php?Page_Type=Service&id=2863
rocks.csc.fi (ngi.SAM) - https://goc.egi.eu/portal/index.php?Page_Type=Service&id=3557
ping.fgi.csc.fi (ngi.SAM) https://goc.egi.eu/portal/index.php?Page_Type=Service&id=3558
murska-arc.csc.fi (ARC-CE) https://goc.egi.eu/portal/index.php?Page_Type=Service&id=2862
vuori-arc.csc.fi (ARC-CE) https://goc.egi.eu/portal/index.php?Page_Type=Service&id=2861
gtpps.csc.fi (ARC-CE) https://goc.egi.eu/portal/index.php?Page_Type=Service&id=2861

Grid queues will be drained and endpoints removed from GOCDB on 15.12.2016.
All services and data will be permanently deleted after 90 days counting from 15.12.2016.
CSC grid site availability should have any impact as new resources and queues are running in parallel. 

Luís Alves 

Link to GGUS ticket: https://ggus.eu/index.php?mode=ticket_info&ticket_id=12528
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 2016.12.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.79          2016.11.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.79-1 with Classic, SLCS and MICS profiles, encoded in
meta-package "ca-policy-egi-core-1.79-1" (new installs) and "lcg-CA-1.79-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.78 to 1.79
-------------------------
(28 November 2016)

* Updated UNLPGrid CA with extended validity period (AR)
* Fix regular expressions in CILogon and NCSA CA namespaces files (US)
* Included rollover CA IRAN-GRID-CGC-G2 (IR)
* Corrected an incorrect line in selected info files for DigiCert (US)
* Discontinued expiring NECTEC CA (TH)

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.79-1
1) UMD 4.3.0 has been released today Nov 10th: http://repository.egi.eu/2016/11/10/release-umd-4-3-0/

It brings several new products and updates[*], included the following fixes:

- umd-release 3.14.3, fixing an issue with GPG keys, details here: https://gist.github.com/pkoro/cc2ce75a0867a835f15d2f4d3fe50f44
- gridsite 2.3.3, fixing an issue with proxy renewal on WMS https://ggus.eu/index.php?mode=ticket_info&ticket_id=124499
- VOMS 3.5.0, which makes RFC proxies the default for voms-proxy-init; an update of YAIM core handling RFC proxy as the new default

[*] Products included in this release:
- ARC, GFAL2, XROOT, Davix, dCache, ARGUS, Gridsite, edg-mkgrid, umd-release for CentOS7
- ARC, GFAL2, XROOT, Gridsite, edg-mkgrid, umd-release, GRAM5, DPM, Globus GridFTP, globus-default-security, MyProxy, Davix, dCache, VOMS, YAIM core, lcas-lcmaps for SL6

2) Please start using UMD4/SL6 or UMD4/CentOS7 instead of UMD3/SL6:
- Debian not used anymore, SL5 only security fixes, SL6 is available in UMD4 as well
- UMD4/SL6 contains products of UMD3/SL6 which give support for the next year at least, all the unsupported products are not in UMD4/SL6 (please let us know if we are missing specific products that we might have skipped!):
-- for some unsupported products, we are investigating how to replace them with equivalent products in UMD4/SL6 (see WMS)
-- list of all the products that are in UMD3 but not migrated to UMD4 is available, to be improved: https://wiki.egi.eu/wiki/UMD3_UMD4_products
[ Reminder ]

Dear WLCG site admins in EGI,

In the Grid Deployment Board meeting of May 2016 the afternoon was dedicated
to a session on what could be done to allow the operation of WLCG sites to
be made less heavy. A summary of the session and the conclusions so far are
available here:

    https://twiki.cern.ch/twiki/bin/view/LCG/LightweightSites

Now we would like to identify areas where it is worthwhile to spend effort
such that sizable numbers of sites may profit, while at the same time
avoiding that a lot of work is merely shifted to the experiments, CERN IT
or the T1 sites.

The aim is to get to a "matrix" of approaches that sites can choose from,
depending on criteria that we try to cover in this questionnaire:

    http://wlcg-survey.web.cern.ch/survey/lightweight-sites

Please take some time to fill it out, you may need just a few minutes.

Your help with the questionnaire is greatly appreciated, thanks!
1) Av./Rel. recomputation for not considering the downtimes due to the vulnerability CVE-2016-5195

All the resource centres that were affected by the vulnerability CVE-2016-5195 and that declared a downtime between 2016-10-20 16:00 UTC and 2016-10-31 18:00 UTC are invited to request a recomputation of A/R figures for the days in which the downtime was ongoing.

In according to the procedure https://wiki.egi.eu/wiki/PROC10_Recomputation_of_SAM_results_or_availability_reliability_statistics you need to fill this form:

http://argo.egi.eu/lavoisier/recomputation

and indicate:

- Your name and email
- the site(s) affected by the problem
- a description of the problem
- the profile affected
- the starting and ending time of the problem (including day and hour in UTC)

In case of problems with the web form, please submit a GGUS ticket to ARGO/SAM support unit providing the same information.

2)  UMD 3.14.5 released today, including:
- umd-release 3.14.3, fixing an issue with GPG keys; details here: https://gist.github.com/pkoro/cc2ce75a0867a835f15d2f4d3fe50f44 (it doesn't affect new installations) 
- gridsite 2.3.3, fixing an issue with proxy renewal on WMS https://ggus.eu/index.php?mode=ticket_info&ticket_id=124499
- VOMS 3.5.0, which makes RFC proxies the default for voms-proxy-init; an update of YAIM core handling RFC proxy as the new default 

3) please start using UMD4/SL6 or UMD4/CentOS7 instead of UMD3/SL6
- Debian not used anymore, SL5 only security fixes, SL6 is available in UMD4 as well
- UMD4/SL6 contains products of UMD3/SL6 which give support for the next year at least, all the unsupported products are not in UMD4/SL6 (please let us know if we are missing specific products that we might have skipped!)
-- for some unsupported products, we are investigating how to replace them with equivalent products in UMD4/SL6 (see WMS)
-- list of all the products that are in UMD3 but not migrated to UMD4 is available, to be improved: https://wiki.egi.eu/wiki/UMD3_UMD4_products 

4) new version of VAPOR (https://operations-portal.egi.eu/vapor/) will be released this month: it is an important tool for gathering and displaying the information published by the sites in the BDII, like for example the computing/storage capacities and many other things, and it replaced GSTAT.

Each NGI and Resource Centre should review the information provided by their sites and let us know any inconsistency: http://operations-portal.egi.eu/vapor/resources/GL2ResSummary . We need your feedback to improve the service.

- please test the version 2.2 by going on the dev instance http://operations-portal.egi.eu/vapor_dev
- report any comment, inconsistencies or suggestion for improvement into https://ggus.eu/index.php?mode=ticket_info&ticket_id=124872 where you can find details about how to test the version 2.2
Hello,

 This is a reminder for the DPM workshop 2016, which will
take place on the 23th and 24th of November 2016 at LPNHE(Paris),
with the kind support of the French DPM community.

https://indico.cern.ch/event/559673/

 You are invited to participate to the workshop and to the
discussions, where we cover news and updates on the status
of DPM: releases, distributions, development directions,
involvement of the DPM collaboration, new components, new
setup, old components revisited, performance evaluations
and experiences in general.

 The workshop will cover news and updates on experiences
and best practices, user reports, administration tools, federations,
data access and community talks.

 The agenda is complete and the registration is still open.
 All the speakers and participants are kindly invited to register.

 We hope to see you all there.

Cheers
Fabrizio