wiki:developers-meeting-20100331
Last modified 11 years ago Last modified on 03/31/10 17:24:28

[part of a series of meetings]

Participants

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

Vijay: enstore PNFS upgrade hardware upgrade D0 dCache.. Preparing all the tests; PNFS/PostgreSQL upgrade. Taking dumps etc. Tuesday is the big day. CDF is 15 days from D0. Am the dCache expert for the week;

Jan: on web-admin .. patches in RB: developing SSL / login process.

Paul: ..

Owen: Released dcap. Fixed gsidcap bug (artefact of linking to libssl). Another bug reported in dcap that needs investigating. ETICS looks closer to getting a release of the server (1.9.5-17): claiming it needs an ETICS-specific OpenLDAP server instead of using the system-supplied version. dcap: ready to release to CERN (before bug-report came it).

Patrick: filling out electronic EU forms to get 1.5 people for 3 years.

Tanya: managing tickets, bothering developers; working on pool.

Plans for patch-releases

Should we make a new patch release?

Nothing pending for 1.9.5 and 1.9.6. 1.9.7 is to be release today.

Someone should make sure that when a release is made, then an email is sent to tell people.

Another idea: advertise when a release is going to be made so people can rush to get their patch in. Or always release on a particular day-of-week.

Trunk activity

Progress with new features...

Enstore

Patch submitted to enstore team, but delayed on people looking into it. This patch is to add Chimera support add a new file namespace.py: able to handle PNFS, Chimera and Lustre. Enstore (core) is using some methods from some of the files that have been changed, but most of the changes are to encp.

Can sites upgrade just encp? Basic functionality should be fine; but, PIC have agreed to upgrade enstore so this shouldn't be a problem.

How do you store the enstore specific information in Chimera? Storing this information in level-4 using the dot-commands. Is this the final design? This is the final design.

Use tables instead of using level-4?

Wrapper server (kind of PnfsManager) is likely to be needed in the future. encp (and other) clients will talk to this service rather than mounting a namespace. A switch to using database tables rather than level-4 might happen as part of this change.

Enstore fixed to support >15,000 requests in the queue. Is this deployed at PIC already? Don't know: ask Dmitry.

Issues from 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

Testing of SRM?

Jean-Phillippe would like to test the new SRM / FTP-client code.

DTNM

Proposed: same time, next week.