General information

Middleware


UMD

About the new Linux distribution

About UMD (see also the presentation in March OMB meeting)

  • collecting the products available on EL9 to prepare the first UMD5 release

  • New repository structure implemented in the testing infrastructure and operational:

    • Main repository: umd/5/release

    • Testing repository:  umd/5/testing

    • Contrib repository:  umd/5/contrib

  • New public key already available in the repository: https://nexusrepoegi.a.incd.pt/repository/umd/UMD-5-RPM-PGP-KEY

  • All tests with priority were made and working as expected (new bdii in there for testing)

    • Small changes were made at the level of the workflow. This was required to improve the automation process. 

    • A lot of work made at the level of the back-end and jenkins workflows close to finish. Running manual scripts already possible and the new json structure being finalized (json will replace the current xml for releases)

  • What needs to be done:

    • Implement an High Availability proxy based on NGINX in order to filter the traffic to umd4 and umd5 repos. 

      • Using the HA proxy will provide a certain degree of freedom and in security terms will be an improvement since for example it will allow us to block most of the bots that keep scanning the repositories.

    • move the testing infrastructure to production. 

    • finalize the umd-5 rpm and upload it to the repositories so people can test it.

Operations

ARGO/SAM

  • notifications enabled for the metrics included in the profile ARGO_MON_OPERATORS (instead of ARGO_MON_CRITICAL)  
  • changing the warning period of the host certificate validity metric
    • https://ggus.eu/index.php?mode=ticket_info&ticket_id=161019
    • currently is 1 month before the certificate expiration
      • most of the sites cannot fix the situation immediately
    • proposing to have the WARNING status 2 weeks before the certificate expiration
      • with notifications sent 14 days, 10 days, 5,4,3,2,1 days before the expiration
  • Monitoring of xrootd endpoints
    • some endpoints are exposed outside the site in read-only mode
    • need to modify the xrootd probe to execute only "read" tests
    • the new service type "eu.egi.readonly.xrootd" was created for this purpose (see GGUS 160848)

FedCloud

Feedback from DMSU


New Known Error Database (KEDB)

The KEDB has been moved to Jira+Confluence: https://confluence.egi.eu/display/EGIKEDB/EGI+Federation+KEDB+Home

  • problems are tracked with Jira tickets to better follow-up their evolution
  • problems can be registered by DMSU staff and EGI Operations team


Monthly Availability/Reliability

Under-performed sites in the past A/R reports with issues not yet fixed:


Under-performed sites after 3 consecutive months, under-performed NGIs, QoS violations: (Mar 2023):


sites suspended: 

Documentation

IPv6 readiness plans

Transition from X509 to federated identities (AARC profile token)

  • In Feb 2022 OSG fully moved to token-based AAI, abandoning X509 certificates
  • HTCondorCE: replacement of Grid Community Toolkit
    • The long-term support series (9.0.x) from the CHTC repositories will support X509/VOMS authentication until May 2023
    • Starting in 9.3.0 (released in October 2021), the HTCondor feature releases does NOT contain this support
    • EGI sites are recommended to stay with the long-term support series for the time being

Migration of the VOs from VOMS to Check-in

  • transition period where both X509 and tokens can be used
    • delays in updating the GRID elements to the latest version compliant with tokens
    • not all of the middleware products can be compliant with tokens at the same time
    • the same VO has to interact with element supporting different authentications

Testing HTCondorCE and AARC Profile token

  • INFN-T1 did some tests with the AARC Profile token using its HTCondorCE endpoints
  • dteam VO registered in Check-in/Comanage:
    • Entitlements:
      • urn:mace:egi.eu:group:dteam:role=member#aai.egi.eu
      • urn:mace:egi.eu:group:dteam:role=vm_operator#aai.egi.eu
  • The HTCondorCE expects to find in the token the scope claim to authorise the jobs submission
    • in that moment Check-in didn't release this claim: it does since the migration to Keykloak technology replacing MitreID

WLCG Campaign

Hackathon events

  • 15th - 16th September ARC/HTCondor CE Hackathon, organised by WLCG, with HTCondorCE and ARC-CE to mostly investigating data staging issues (see GDB introduction)
    • agreed to enable the support of the several token profiles through plugins
      • same plugin for the several CEs 
      • plugins provided by the "creators" of the token profiles
    • CE teams to provide specifics to the AAI teams and to release a new CE version supporting the plugins

Plans for the coming months:

  • ARC-CE and HTCondorCE implemented a new API interface
  • The Check-in team is working on a plugin for the Check-in/AARC token profile allowing the authz on the CE side
    • according to the AARC guidelines, the claim to authorise the job submission is provided through a different attributes than the one used by the WLCG token
    • the plugin will translate the attribute to be understandable to the CEs
  • The plugin is currently under testing before its release in UMD
    • involved DESY-HH, FZK-LCG2, INFN-BARI, INFN-T1, RECAS-NAPOLI
    • the plugin is tested with HTCondor Feature Release which introduced the support to Check-in tokens 
  • Then we can start the decommission procedure for the HTCondorCE long-term support series (9.0.x)
    • we might agree to postpone this decommission deadline considering the (relatively ) low likelihood of security issues
    • this will make the transition to tokens less painful for VOs that are not ready yet
  • At the same time the VOs using voms will be cloned to Check-in in order to be ready to use the tokens when the first HTCondor (Feature Channel version) endpoints are in productions.

DPM Decommission and migration

  • DPM supported until June 2023
  • Sites are encouraged to start the migration to a different storage element since the process will take time
    • choosing the new storage solution depends on the expertise/experience of the sites and on the needs of the supported VOs 
  • See the slides presented by Petr Vokac at the EGI Conference 2022 about the migration tools to dCache
  • DPM provides a migration script to dCache (migration guide)
    • Transparent migration
      • Migrate just catalog (database) and keep files untouched
      • both SE store files on posix filesystem
  • Migration in three steps
    • verify the DPM data consistency
      • no downtime needed
      • the operation can last several days or some weeks
    • DPM dump and dCache import
      • downtime lasting about 1 day
  • In September opened tickets to the sites to plan the migration and decommission:
    • tickets list (20 out of 56 were solved)
    • Please let us know your plans for DPM EOL and in case you decide to use dCache migration tools the tickets will be used to support you on this storage migration method.
    • dCache migration should be done by June 2023.
    • Last week we requested info from undefined and planned until Feb.2023

Planned completion date

Beginning of 2023

1

By Feb 2023

1

By March 2023

2

By Q1 2023

3

By April

3

By Q2 2023

12

undefined

9

Chosen technology

Migration to dCache

26

Migration to EOS

8

Migration to xroot/ceph

3

Migration to XrootD

1

Migration to Xcache

1

Migration to Dynafed

2

Not yet decided/no clear plan

7

Decommissioning SE or site

6

New benchmark replacing HEP-SPEC06

The benchmark HEPSCORE is going to replace the old Hep-Spec06

Main points agreed:

  • Existing resources at the sites will not be re-benchmarked with HEPscore (unless the site has modern resources and would like to re-benchmark them in order to get higher consumption in the accounting reports)
  • New resources purchased by the site will be benchmarked with HEPscore
  • HEPscore23 will be normalized with HS06 with factor 1
  • The switch to HEPscore23 in the accounting reports will happen on the 1st of April 2023 (when WLCG switch yearly pledges)
  • This implies that two benchmarks will co-exist on the infrastructure for quite some time
  • We would like to follow the progress regarding amount of the resources benchmarked with HEPscore23
  • No need for reporting of measurements for two benchmarks in parallel for the same set of resources
    • This implies that accounting record should contain one metric for a single benchmark and benchmark name has to be properly defined in the accounting record.

Plans for the coming months:

  • Change of units: last week of March 2023 in the Accounting Portal all of the references to HepSpec06 were replaced with HEPscore23
  • A new APEL version compliant with the new benchmark will be released within a few weeks
  • Some tests in particular with sites sending normalised reports are ongoing.
  • Need to distinguish between the resources benchmarked with one benchmark or the other to monitor the move to the new benchmark over the time
    • The accounting records will be tagged with the name of the benchmark used for normalisation
    • A new APEL version is going to introduce this feature
    • The Accounting Portal will allow to see the split of the resources by benchmark
    • This change will be introduced by the end of May

HEPSCORE application:

April GDB:

Monitoring of webdav and xrootd protocols/endpoints

AOB


Next meeting

March

  • No labels