Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

  • List of Epics

  • New tickets

  • Consider new functionality / items

  • Detailed discussion of important topics

  • Site report activity

...

Item

Presenter

Notes

5.4.3 releases in Centos 7 / EL8;

  • Problems observed: (pgRead / pgWrites)

AllThomas, Jyothish (STFC,RAL,SC)

Jira Legacy
serverSystem JIRA
serverId929eceee-34b0-3928-beeb-a1a37de31a8b
keyXRD-14
,
Jira Legacy
serverSystem JIRA
serverId929eceee-34b0-3928-beeb-a1a37de31a8b
keyXRD-10

defaults to 64kiB (in async).
bufferedIO appears to improve situation for writes; reads appears to be broken.

custom core XrootD version (5.4.3) with downgraded internal protocol version to switch off pgreads/writes.

Outstanding items for 5.4.X XrdCeph version

Master:

Jira Legacy
serverSystem JIRA
serverId929eceee-34b0-3928-beeb-a1a37de31a8b
keyXRD-22
included;

BufferedIO: PR to merge current Master needed;

Jira Legacy
serverSystem JIRA
serverId929eceee-34b0-3928-beeb-a1a37de31a8b
keyXRD-9
Code prepared; PR needed

Non Epic ticket review

All

Jira Legacy
serverSystem JIRA
serverId929eceee-34b0-3928-beeb-a1a37de31a8b
keyXRD-24

Add xrd.report monitoring to all xrootd instances; collate and ingest into ES.
Initial version: https://github.com/snafus/xrdreport

Should time derivative data be calculated and exported to ES?

Tom - mentioned whether influxDB is a better option (via telegraph); to discuss further offline

Jira Legacy
serverSystem JIRA
serverId929eceee-34b0-3928-beeb-a1a37de31a8b
keyXRD-23

Possibility to specify a set of “Features” that XrdCeph support; can we make use of this?

Jira Legacy
serverSystem JIRA
serverId929eceee-34b0-3928-beeb-a1a37de31a8b
keyXRD-13

Did not that some difference in the reported timestamps; stalled.

Jira Legacy
serverSystem JIRA
serverId929eceee-34b0-3928-beeb-a1a37de31a8b
keyXRD-21

Not yet started

Jira Legacy
serverSystem JIRA
serverId929eceee-34b0-3928-beeb-a1a37de31a8b
keyXRD-20

Timeline to get a working dev instance? Another hackathon required?

Lancaster / Glasgow also looking at this

Jira Legacy
serverSystem JIRA
serverId929eceee-34b0-3928-beeb-a1a37de31a8b
keyXRD-26

ceph-dev-gw2: aim to pass current compliance tests (XrootD 5.5. will be needed for all components).
Demonstrate that Echo can satisfy proposed ATLAS strategy with mixed x509 / tokens workload.

Site reports

Lancaster

Discussion of dropped packets in CEPH - some clues given.

xrootd tpc still continues to be broken. Rollback to 5.4.2 and removing the cksum option has led to a failure that looks like the auth proxy isn’t being passed to the source.

Glasgow

Exploring xrootd redirector for (internal) gateway. 

✅ Action items

  •  

⤴ Decisions

...