Last modified 10 years ago Last modified on 01/19/11 18:10:25

[part of a series of meetings]


Patrick, Antje, Paul, Karsten, Tanja, Gerd, Gene, Dmitry.


[see box on the right-hand side]


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 :)

Patrick: managed to get a slot at CMS meeting in Barri. Organised prep. meeting for meeting in Goethingham. Paperwork. Dmitry: fixed bug in space-manager; continue to test scalable SRM -- using SRM as a proxy to database. Jon wants a separate JAR file to deploy in production. srmGet is not very impressive compared to ... getting linear scalability; looking at pin-manager patch. srmGet is limited by pinManager performance; disabling this provides 2.5 times improvement of performance. Gene: nothing Gerd: working on pin-manager patch: now ready for reviewing; plan to deploy it on Monday at NDGF. One change not yet there is for disk-only files we can skip most of the logic; planned as a follow-up patch. Tanja: Tickets, NFS, gPlazma. Karsten: submitted VO-map role .. just updated. Tigran: 1.9.5 release, fixing kernel packaging, fixing kerberos. Paul: review patches, tickets, delegation work for EMI & OGF, Antje: dCache book + being ill.

Plans for patch-releases

Should we make a new patch release?

Just released 1.9.5-24 (just before meeting). A couple of patches for 1.9.10 and 1.9.11.

Problem with gPlazma works incorrectly: before Dima unhappy, now Dima happy but Gerd unhappy. Tanja is working on this.


Suggest upgrading to 1.9.12 (from 1.9.5). Dmitry to have a chat with Neha.

Trunk activity

Progress with new features...

Planning for 1.9.12

What is the exact release schedule for 1.9.12?

On Monday 28th we branch trunk to make 1.9.12; two weeks of testing; release 1.9.12-1 on March 14th.

Discuss testing schedule with Christian tomorrow (Thursday) or later.

New instance

Running trunk.

Issues from yesterday's Tier-1 meeting


Suggest Doris should review settings for

Can we distinguish between GridFTP-1 and GridFTP-2? Difficult with LoginManager?, but maybe adjust load metric sent back to SRM.

We should distinguish between using proxy or not. .. currently difficult to do this.

This is a low priority task.


No news on their upgrade to 1.9.5. Seems to be working OK for them.

Issues from EMI

Bug track

Update states in RT add new states.

Can we template SVN message? Don't know.

ReviewBoard? and Commit.

Gerd would like a link from SVN-commit message to RT-Ticket.

Please everyone update RT-ticket with when code is committed and when it will be released.

Outstanding RT Tickets

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

RT 5847: Migration remarks(problems)

Review of RB requests

Pin manager

Pin-manager: test in NDGF

Dmitry has high-pressure testing environment. Once existing testing is complete, he can test the new pin-manager once

Bottleneck is now in pin-manager.

Gerd's disclaimer: there are more patches coming that improve the performance.

Tigran: suggest adding extra functionality ... an "always succeed" mode for Tier-2s.

We can make the decision on getting this into 1.9.12 based on test people's tests: Dmitry and NDGF.

Moving database towards a common approach

Can we use the same approach with other db-aware components? For example: SRM, space-manager, gPlazma, jobs persistency.

Use of an ORM depends on the use-case; Chimera may not move. Space-Manager and SRM

The transaction-management part all components could make use

There's a LOT of boilerplate code .. using Aspect for this.

Coupling the operations with the transaction scope. We can't make PnfsManager operations can have the a higher transactional scope.

Tackle this independently, component-by-component.

But, we need to agree on technology.


Same time, next week.