wiki:developers-meeting-20180213
Last modified 9 months ago Last modified on 02/13/18 17:31:18

[part of a series of meetings]

Participants

Al, Tigran, Marina, Paul, Dmitry

Postcards

Al: Work on Resilience, debugging of various issues. Finished and committed some dCacheView components

Tigran: Mostly prepared tasks for the HTW students of this year's course. Diagnosis of problems with the DESYCloud instance: Long file retention time combined with a user creating massive amounts of files caused an infinite file listing loop.

Marina: Continuing Kafka work, releasing

Paul: Added new logfile for Zookeeper curator events. XDC WP 4 project work in the areas of caching, QoS and DLC.

Dmitry: Internal operational procedure work

Jürgen: Jenkins update, XDC project work, fixes to S2, and the robot tests, bug reports to some grid middleware in preparation

Special topics

Al: Pool configurations using Resilience

Al asks about possibilities to configure pools in a Stage- / RW configuration. We discuss implementation details for this.

Release news

Keeping with the weekly release cycle.

Jürgen is doing a major update to the Jenkins infrastructure, removing the remaining SL5 components and dependencies.

1st of March is the date for dCache 4.1, and we'll prepare that release (VM, Jenkins infrastructure, branching etc.)

Trunk activity

Progress with new features...

Issues from [FIXME: Add link to yesterday's Tier-1 meeting]

Outstanding RT Tickets

[This is an auto-generated item. Don't add items here directly]

Review of RB requests

We note that there are several outstanding review requests for 4.1. After a long discussion about whether or not to prioritize exact timeboxed releases over inclusion of outstanding patches, we decide to accept a short delay of a week or two but will release even without outstanding features when the delay would be longer.

New, noteworthy and other business

Jürgen asks who might take a look at proposed changes to an RPM specfile.

DTNM

We'll have to talk to the meeting service team about the stability of Cisco Meeting, but we'll not change back to Hangouts due to the user limit.

Attachments