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.

Difference between revisions of "URT:Agenda-2020-11-16"

From EGIWiki
Jump to navigation Jump to search
Line 84: Line 84:


== ARC  ==
== ARC  ==
6.8.1 is out in the Nordugrid repo. Not yet in EPEL stable.
ARC 6.9 is planned for end of November. Will contain REST interface reworked technical preview.
http://www.nordugrid.org/arc/releases/6.8.1/release_notes_6.8.1.html
 
ARC 6.8.0 and 6.8.1 is built with xrootd5. If xrootd5 is not yet in epel-stable, then if you have nordugrid-arc-plugins-xrootd installed, you must enable the epel-testing repo.


== CREAM  ==
== CREAM  ==

Revision as of 15:16, 16 November 2020

News

  • EGI repositories handover in January 2021: provider moving from IASA to IBERGRID.
    • The handover will be a complex operation due to the complexity of the repository workflows and technologies adopted. Handover preparation started with a regular meeting between IASA and IBERGRID and agreement said handover will occur in the first half of December 2020 in order to avoid the problematic end of year holiday.
    • Last released planned for November 2020.
    • During 2021 repositories will undergo a series of improvements, frontend and backend and a complete review of the procedures and workflows following a CI/CD approach.

UMD

  • UMD4 release in preparation
    • StoRM, VOMS, BDII update, dCache
    • VERY URGENT
  • feedback on software automation from the EGI Conference
  • UMD 5 dry run planned for, get the process ready for end of October
  • dedicated update for VOMS on UMD4/CentOS7 as soon as it's released
  • dedicated update for StoRM+BDII on UMD4/C7+SL6 before repo migration

CMD

Status

UMD

In Verification

  • cream-blah 1.23.0 (failed SR)
  • cvmfs 2.7.5, cvmfs-config-egi-2.5, and egi-cvmfs-2-7
  • arc6 6.8.1 (requires Xroot 5.0)
  • xroot 5.0.2
  • glite-info-update-endpoints 3.0.2
  • apel-ssm 3.0.0
  • ams-library 0.5.8
  • storm 1.11.19 (centos6, centos7)
  • bdii 5.2.26
  • lcg-info 1.12.5
  • glite-info-update-endpoints 3.0.2
  • voms-admin-server 3.8.0 (centos7)
  • voms-clients 2.0.15
  • htcondor-ce 3.4.0 (UMD-5)
  • htcondor 8.8.11 (UMD-5)

Under Staged Rollout

N/A

Ready to be Released

  • davix 0.7.6

CMD-OS

In Verification

In Staged Rollout

Ready to be released

Technical Providers - Round table

APEL

Frontier

Indigo-DataCloud

dCache

DPM/Dynafed/LFC

New version of DPM (1.13.2) available in EPEL

http://lcgdm.web.cern.ch/dmlitedpm-1132-released-epel

Data management clients

gfal2 2.17.0 pushed to EPEL

http://dmc.web.cern.ch/release/gfal2-2.17.0

FTS

New Major version of SOCI in EPEL7-testing (4.0.0). FTS rebuild needed, we are discussing with the maintainer about issues that we found.

We would need to release a new FTS build for C7 when SOCI 4 will be pushed to EPEL stable.

ARC

ARC 6.9 is planned for end of November. Will contain REST interface reworked technical preview.

CREAM

QCG

Globus

xrootd

The xrootd 5.0.2 update is available in EPEL stable since 2020-10-30.

Updates for all packages in EPEL depending on xrootd built against xrootd 5 are also available in EPEL stable. Thanks to Michal Simon and Oliver Keeble for taking part in this coordinated effort.

Major changes:

  • The old client library libXrdClient has been dropped (replacement: libXrdCl).

Minor changes:

  • The XrdSysDNS class is removed (replacement: XrdNetAddr)
  • XrdPosixXrootd::setDebug() and some other deprecated methods in that class have been dropped.

For EPEL 7 there is an xrootd-compat package providing the old xrootd 4 libraries. It is parallel installable since the sonames have changed. The compat package does not provide any devel subpackages.

Main xrootd update:

GFAL2 built against xrootd 5:

dmlite built against xrootd 5:

No update to xrootd 5 is planned for EPEL 6.

The xrootd 4.12.5 update for EPEL 6 (and the corresponding update of xrootd-compat for EPEL 7) is in EPEL stable since 2020-10-31:

The xrootd 5.0.3 update for EPEL 7 and EPEL 8 is in EPEL testing:

caNl

BDII

WN/UI

Argus

v1.7.3 will be released after StoRM and VOMS releases.

Started investigation on https://ggus.eu/index.php?mode=ticket_info&ticket_id=147877

StoRM

StoRM v1.11.18 released. http://italiangrid.github.io/storm/2020/08/07/storm-v1.11.18-released.html

StoRM v1.11.19 released. http://italiangrid.github.io/storm/2020/10/29/storm-v1.11.19-released.html

StoRM 1.11.20 not planned. We started working on Frontend's code optimization in order to avoid memory leaks. If there's no urgency on fixing some bug we'll start building and testing on CentOS 8.

VOMS

Release v3.8.0 NOT yet released.

Tests in progress. Got positive feedback from CERN. Expected release: by 25th of September.

Packages will be released also for CentOS 7.

voms-api-java-3.3.2-1 and voms-clients-java-3.3.2-1 are available in EPEL stable since 2020-10-28.

The VOMS 2.0.15 release is available in EPEL 6 stable and EPEL 7 stable since 2020-11-12.

The VOMS package in EPEL 8 is using the 2.1 series and is not affected by this update.

Preview

  • released on 2020-10-09
    • Preview 1.29.0 AppDB info (sl6): ARC 6.8.0 and 6.8.1, BDII 5.5.26, CVMFS 2.7.4, dCache 5.2.31, DMLite/DPM 1.14.0, frontier-squid 4.13.1, glite-info-update-endpoints 3.0.2, lcg-info 1.12.5, STORM 1.11.18
    • Preview 2.29.0 AppDB info (CentOS 7): ARC 6.8.0 and 6.8.1, BDII 5.5.26, CVMFS 2.7.4, dCache 5.2.31, DMLite/DPM 1.14.0, frontier-squid 4.13.1, glite-info-update-endpoints 3.0.2, lcg-info 1.12.5, STORM 1.11.18

UMD on CentOS 8

  • Plan to be defined with
    • Technical Providers
    • WLCG
    • NGIs/sites (there was 1 request so far)
    • UMD team (innovation in the process must be taken into consideration)

Wiki: https://wiki.egi.eu/wiki/Next_middleware_release

AOB

ARC finds it problematic that the ARC released in UMD is always so far behind the current newest release. We are considering to stop providing ARC for UMD.

The verification procedure for ARC - does it involve running ARC together with other relevant packages in the release to make sure compatibility is met?