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 @ egi.eu.

Agenda-10-02-2014

From EGIWiki
Jump to navigation Jump to search
Audio conference link Conference system is Adobe Connect, no password required.
Audio conference details Indico page



1. Middleware releases and staged rollout

1.1 News from URT

EMI released updates for EMI-3 and EMI-2:

Other updates from PTs:

  • DPM/LFC inclusion of STAR accounting to be used off of the shelf
  • FTS3 release in EPEL
  • WMS update by the end of February

1.2 UMD release

  • UMD 3.4.0 was released 29/01/2014 and contained the following components:
  • CREAM TORQUE v. 2.1.2: This release fixes the wrong total cpu count from PBS infoprovider together with a dependency issue with lcg-info-dynamic-scheduler
  • ARC-CE v. 4.0.0: This is a major release of ARC-CE and include updates for both server and client tools. Among several new features now ARC client tools use by default the new client-side BDB job storage if available this leads to an backwards incompatible since jobs stored in xml file will not be accessed.
  • QCG COMP v. 3.2.0 : This release provides and optimization of the GetFactoryAttributes method together with an extension element in SLURM module and some bug fixes.
  • BDII-CORE v. 1.5.5: On this release there a new version of glite-yaim-bdii that sets the top BDII cache validity to 4 days by default. Also this release also contains a new version of glue-validator-cron that logs only the results for full EGI profile GLUE 2 validation.
  • BDII-TOP v. 1.1.4: This release decommissions the FCR (Freedom of Choice of Resources) mechanism that is no longer needed in the top BDII.

Messaging:

  • QCG NOTIFICATION v. 3.2.0 : This release provides server improvements like the option for disabling Current Messages and several bugfixes.
  • GridSite v. 2.2.0 : This is a minor release of GridSite addressing the issue of key lengths being hard-coded at 512 bits. It increases the default key length to 1024 bits, and exposes new functions in the API to accepts custom key lengths.
  • UMD-2 (UMD 2.80 RC):
    • proxyrenewal 1.3.35
    • gridsit v. 1.7.29
    • Globus-proxy-utils v. 5.0.6
    • cream v. 1.14.6
  • UMD-2 is considered under security support, but update Gridsite, glite-px and globus-proxy-utils in order to make them compatible with the latest openssl updates. Since UMD-2 will start the decommissioning process soon, only a verification will be performed.

1.3 Staged rollout updates

  • Currently in staged rollout:

1.3.1 WMS issues

  • At the moment there are 5 major open issues with WMS:
    • There are two problems regarding with the proxies that in some cases can still generate 512 bits proxies:
      • The WMS Purger still uses 512 bits which is hard-coded and can update wms's proxy with the wrong 512 bits (NOTES).
      • The glite-wms-create-proxy.sh uses an undefined GLOBUS_LOCATION env var which avoids the invocation of grid-proxy-init, which by default produces 1024bit proxies. The missing variable its solved by the WMS purger which then generates 512 bits proxies. (NOTES).
    • Issues introduced only in 3.6.2 (UMD not affected):
    • WMProxy still uses the low-level symlink call which doesn't support heading dash ("-") in the file names (NOTES).
    • Bad exception handling in ICE prevents the user from getting a readable error message (NOTES).
    • Problem on glite-wms-wmproxy-api-java with TERENA certificate (NOTE)

1.3.2 CREAM_SLURM

  • Cream-slurm v. 1.0.1 as some problem with accounting that many records not being published even if jobs successfully finished. This is under investigation so if you are planning to deploy cream-slurm I would delay it until putting into production.

1.4 Next releases

  • UMD-2 this week
  • UMD-3 next week

2. Operational issues

2.1 Report from DMSU

Nothing to report

2.1 EMI-2 decommision calendar

According to the EGI decommissioning policy, the decommissioning deadline expires one month after the end of security updates and support of the software. For EMI 2 the end of security support is: 30-04-2014. And unsupported services must be either decommissioned, upgraded or in downtime after 31 May 2014.

A broadcast has been sent to sites and NGIs.

List of affected products

  • ARC v2.*
  • ARGUS v1.5.*
  • BDII Site older than v1.2.0
  • BDII Top older than v1.1.0
  • CREAM v1.14.*
  • dCache v2.2.*
  • DPM older than v1.8.6
  • EMI-UI v2.*
  • EMI-WN v2.*
  • FTS v.2.2.8
  • StoRM older than v.1.11.0
  • VOMS v.2.*

2.2 NGI Argus status

The following table has been prepared by Sven Gabriel and shows the status of GGUS tickets opened to track the deployment of Argus services at NGI level.

Resp. Unit Status Hostname DN Central Instance Connect Nagios (Updated Ban Info)
NGI_MARGI assigned NONE
ROC_Russia solved b4ng.jinr.ru /C=RU/O=RDIG/OU=hosts/OU=jinr.ru/CN=b4ng.jinr.ru
ROC_LA in progress argus.hpc.utfsm.cl /C=CL/O=REUNACA/O=REUNA/OU=UTFSM/CN=argus.hpc.utfsm.cl
ROC_Canada closed roc-policy.triumf.ca /C=CA/O=Grid/OU=triumf.ca/CN=roc-policy.triumf.ca
ROC_Asia/Pacific in progress argus02.grid.sinica.edu.tw /C=TW/O=AS/OU=GRID/CN=argus02.grid.sinica.edu.tw
NGI_ZA closed NONE
NGI_UK in progress argusngi.gridpp.rl.ac.uk /C=UK/O=eScience/OU=CLRC/L=RAL/CN=argusngi.gridpp.rl.ac.uk
NGI_UA closed argus.grid.org.ua /DC=org/DC=ugrid/O=hosts/O=KNU/CN=argus.grid.org.ua NiP
NGI_TR closed nagios.ulakbim.gov.tr /C=TR/O=TRGrid/OU=TUBITAK-ULAKBIM/CN=nagios.ulakbim.gov.tr
NGI_SK closed argus.slovakgrid.sk /C=SK/O=SlovakGrid/O=IISAS/CN=argus.slovakgrid.sk
NGI_SI closed argus.sling.si /C=SI/O=SiGNET/O=SLING/CN=argus.sling.si
NGI_RO in progress TO BE FOLLOWED UP, NO NGI-ARGUS in GOC-DB
NGI_PL on hold TO BE FOLLOWED UP, NO NGI-ARGUS in GOC-DB
NGI_NL closed argus.grid.sara.nl /O=dutchgrid/O=hosts/OU=sara.nl/CN=argus.grid.sara.nl
NGI_NDGF closed liuske.csc.fi NO DN REGISTERED IN GOC-DB
NGI_ME solved TO BE FOLLOWED UP, NO NGI-ARGUS in GOC-DB
NGI_MD closed node01-02.imi.renam.md NO DN REGISTERED IN GOC-DB N2
NGI_IT solved argus-it.cnaf.infn.it NO DN REGISTERED IN GOC-DB
NGI_IL in progress TO BE FOLLOWED UP, NO NGI-ARGUS in GOC-DB N3
NGI_IBERGRID closed rargus.ifca.es /DC=es/DC=irisgrid/O=ifca/CN=host/rargus.ifca.es
NGI_HU closed grid146.kfki.hu NO DN REGISTERED IN GOC-DB
NGI_HR in progress TO BE FOLLOWED UP, NO NGI-ARGUS in GOC-DB
NGI_GRNET closed argus-ngi.core.hellasgrid.gr /C=GR/O=HellasGrid/OU=athena.hellasgrid.gr/CN=argus-ngi.core.hellasgrid.gr
NGI_GE closed argus.sg.grena.ge /DC=ORG/DC=SEE-GRID/O=Hosts/O=Georgian Research ..../CN=argus.sg.grena.ge
NGI_FRANCE in progress TO BE FOLLOWED UP, NO NGI-ARGUS in GOC-DB
NGI_FI closed liuske.csc.fi SEE NGI_NDGF
NGI_DE solved TO BE FOLLOWED UP, NO NGI-ARGUS in GOC-DB N3
NGI_CZ closed ngiargus.grid.cesnet.cz /DC=org/DC=terena/DC=tcs/OU=Domain Control Validated/CN=argus.grid.cesnet.cz
NGI_CYGRID closed argus.grid.ucy.ac.cy ? /C=CY/O=CyGrid/O=HPCL/CN=argus.grid.ucy.ac.cy ? N3
NGI_CH in progress TO BE FOLLOWED UP, NO NGI-ARGUS in GOC-DB,
NGI_BY in progress TO BE FOLLOWED UP, NO NGI-ARGUS in GOC-DB
NGI_BG solved argus.ipp.acad.bg ? /DC=bg/DC=acad/O=hosts/O=IICT-BAS/OU=GTA/CN=argus.ipp.acad.bg ? N3
NGI_BA closed TO BE FOLLOWED UP, NO NGI-ARGUS in GOC-DB
NGI_ARMGRID solved argus.grid.am /C=AM/O=ArmeSFo/O=IIAP NAS RA/OU=HPC Laboratory/CN=argus.grid.am
NGI_AL closed ONE SITE IN THAT NGI, THIS ONE IS CLOSED
NGI_AEGIS closed argus.ipb.ac.rs /C=RS/O=AEGIS/OU=Institute of Physics Belgrade/CN=host/argus.ipb.ac.rs

2.3 GLUE2 validation

No improvements in the last weeks, please follow up with your sites:

3. AOB

3.1 Next meeting

4. Minutes