--------------------------------------------------------------------------------------------------------------- EGI BROADCAST TOOL : https://operations-portal.egi.eu/broadcast

--------------------------------------------------------------------------------------------------------------- Publication from : Alessandro Paolini alessandro.paolini@egi.eu Targets : VO managers/vlemed vlemed-vo-managers@biggrid.nl ----------------------------------------------------------------------------------------------------------------

1) New configuration for DTEAM VO

The HellasGrid Certification Authority changed its DN from "/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2006" to "/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2016"

Since it is also changed the certificate of the 2 voms servers hosting dteam VO, the settings of this VO need to be updated accordingly on *ALL THE (grid and cloud) SERVICES*

- New yaim settings (for the ../vo.d/dteam file):

VOMS_SERVERS='vomss://voms.hellasgrid.gr:8443/voms/dteam?/dteam/' VOMSES="'dteam voms.hellasgrid.gr 15004 /C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr dteam 24' 'dteam voms2.hellasgrid.gr 15004 /C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms2.hellasgrid.gr dteam 24'" VOMS_CA_DN="'/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2016' '/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2016'"

- .lsc files:

# cat /etc/grid-security/vomsdir/dteam/voms.hellasgrid.gr.lsc /C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr /C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2016

# cat /etc/grid-security/vomsdir/dteam/voms2.hellasgrid.gr.lsc /C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms2.hellasgrid.gr /C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2016

- configuration information:

https://voms.hellasgrid.gr:8443/voms/dteam/configuration/configuration.actio... https://voms2.hellasgrid.gr:8443/voms/dteam/configuration/configuration.acti...

2) EGI central monitoring instance (ARGO)

Since July 1st, the EGI infrastructure is being monitored by two monitoring instances that can be found on these addresses:

https://argo-mon.egi.eu/nagios https://argo-mon2.egi.eu/nagios

Both instances are running the same set of tests and results provided are equivalent.

Starting from the same date, the central ARGO Web UI (http://argo.egi.eu/lavoisier ) provides information from these two instances and the Operations Portal was reconfigured to raise alarms based on information from ARGO central instances.

Results coming from NGI SAM instances are no longer consumed by the central ARGO or Operations Portal so NGIs can eventually decommission them following the standard decommissioning procedures (https://wiki.egi.eu/wiki/PROC12 ).

3) New set of CREAM probes

A new set of probes is being used for monitoring the CREAM CEs and the A/R computation: https://wiki.italiangrid.it/twiki/bin/view/CREAM/DjsCreamProbeNew This set of probe doesn't make use of the BDII, WMS and the messaging infrastructure like instead did the old WN monitoring framework.

---------------------------------------------------------------------------------------------------------------- link to this broadcast : https://operations-portal.egi.eu/broadcast/archive/id/1422 ----------------------------------------------------------------------------------------------------------------