wiki:developers-meeting-20141217
Last modified 3 years ago Last modified on 12/17/14 16:23:05

[part of a series of meetings]

Participants

Al, Gerd, Paul, Christian, Karsten,

Agenda

[see box on the right-hand side]

Postcards

Up to two minutes (uninterrupted) per person where they can answer two questions:

  • What I did last week (since the last meeting),
  • What I plan to do in the next week.

No questions until we get through everyone :)

Karsten: dcwww

Christian:

  • pcells release process, except for some last Jenkins issues (one artifact does not created) for now, will build locally and release
  • now support PAM style key loggin
  • tickets

Paul:

  • SRM/FTS: Lightning meeting: Clarified some issues, successfully.
  • Stabilize Jenkins, some issues remaining
  • new computer!
  • Prometheus

Gerd:

  • Supporting KIT
  • Found dcap/nfs leak, was disposed by unlimited allowed connections -> fixed
  • IPv4/IPv6 issues reproducing -> confusing success caused by many lucky
  • some work left for other protocols with proxy mode
  • ATLAS: Milton issue, sometimes it changes "File not found" to "Not authorized" replies. (Probably for Office 2010 compatibility) -> affects workaround is to use srm for deletion

Dmitry:

  • Build and tested 2.2 private branch for CMS -> successfully deployed
  • Meetings, archival project (allow people to store their data in dCache)
  • Reviews

Al:

  • Made some changes to better support integrated alarm server
  • updated a couple of patches
  • looked at Wicket 6 upgrade issues

Special topics

Trunk activity

Progress with new features...

Prometheus

Paul: Prometheus is a test server to run daily master to find if we break clients

  • Currently dteam, atlas and
  • Asked FTS people to do tests
  • Currently IPv4 only, will be IPv6 at some point
  • LDAP service with a website, allowing people to sign up (e.g., davix developer)
  • Will mention this on meeting in January.

Christian: Will SSL3 be enabled?

Paul: No, it's disabled in master

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

Thursday:

FERMI: Internal restructuring, new service group, new people joining

  • Asked, why FERMI reports 1.9.5 as version -> they have their own system, want to turn off BDII How this is supposed to work with WLCG, is unclear

Tuesday:

PIC: Upgraded to 2.10. NDGF: 401/405 issue (see Gerd's postcard)

  • Logging for Webdav is bad -> might be caused by using the wrong instance...

KIT: - Upgrade for CMS was fine, would like to have an RPM -> send link to download

  • Atlas upgrade some issues with xrootd plugin
  • LHCb: Very smooth
  • one instance left for upgrade to 2.11
  • asked about NFS not notifying about deleted files -> Tigran is working on it
  • ghost movers, statistics (Gerd plans to improve performance)

Dmitry: BDII@Fermi: How does information get published? Paul: In EGI a hierarchy of BDII servers publishes data on a regular bases... Dmitry: Published information seems not to be updates.

Plans for patch-releases

xrootd4j

Karsten: CMS@Desy requested RPM, so I created one and put it on www.dcache.org Paul: Should we merge plugins in dcache codebase? Patrick: Can we take the plugins and do some basic tests? Gerd: We could, but this might encourage plugin developers to not maintain the plugins as well Dmitry: Plugins should not cause dCache to fail loading, only plugin related functionality should not be available. Gerd: For authorization plugins this could create a security problem

Gerd: Suggest not to get involved into externaly maintained plugins. Tigran: We need a way to communicate possible problems. Paul: We could periodically check the plugins.

-> Make plugin developers aware and trigger them to fix their plugins

-> We create CMS RPM -> Keep them in loop, but

Karsten: API version number? Gerd: Won't help for many issues, because they are caused by non API related bugs.

-> We already had some voluntarily looks into the plugins code

Karsten: API version might help for the transition to 2.12

-> Should we publish dCache to Maven? -> Developer's workshop

FTS

Delayed passive -> now default IPv6 -> multiple patches Bulk staging requests, limit at 2k -> multiple suggestions

Regular

Should we make a new patch release?

no releases last week, will probably do a full round this week.

Outstanding RT Tickets

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

Review of RB requests

New, noteworthy and other business

Merry X-Mas!

DTNM

Proposed: same time, next week.