Table of Contents
[part of a series of meetings]
Participants
Antje, Tanja, Jan, Paul, Tigran, Karsten, Christian, Al
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 :)
Christian: ETICS building, creating RfC, releasing 1.9.12-13 to EMI.
Al: posted patches to review board. Rewriting XACML client to use independent principals. Extended GlobusPrincipal? and modified the FqanPrincipal? to add the extra information that we need. Trying to making the rest of the code independent of gPlazma1. Looking at annotation-base unit-tests.
Tanja: mostly web-admin work; GSS and tickets.
Jan: fixing a lot of small bugs web-admin (thanks Tanja!), providing error messages that let people know what went wrong.
Paul: password ...
Tigran: 2.1 release (whah!) fighting agist infrastructure to work for us. The download page does a redirect to a dCache instance (run by DESY), which serves release binaries. Now we do clean "mvn release".
Karsten: fix some patches on RB. Committing some of them. Building a IPv6 testing environment work-in-progress.
Antje: changes on web-pages. Committing the SRM chapter. Translating dCache white-paper to HTML, etc.
Patrick: CERN. Initiated collaboration gLite data-management on LFC-redirection. Possible new global redirector using HTTP (instead of other protocol) trying to hire a new student to go over to CERN to work on this (for dCache).
Plans for patch-releases
Should we make a new patch release?
Releasing 1.9.12 next week.
Need to release next 2.0 (2.0.3?). DESY will update Hera instance (oldest dCache) instance to 2.1 (+new web-admin patches). Originally decided 2.1 will be only /usr layout package. After talking to Birgit, better to allow slowly migrating over to usr-layout over the course of 2.1; initial upgrade will be to opt-layout.
You can't mix opt-layout and usr-layout.
usr-layout package checks for existence of /opt/d-cache directory. If present, the package refuses to install. This is a hard protection against accidental upgrade.
Need to allow (force?) people to migrate in 1.9.12 from opt- to FHS- layout or we provide opt- and FHS- layout in 2.2 (i.e., for next golden release). Unclear which is best approach.
Trunk activity
Progress with new features...
How to organise big patches
Al
Copy of classes from gPlazma1 to gPlazma2 (+changing of usage to reflect this)
Modifying FqanPrincipal? + VOMS change.
Modifying X509 plugin to create ExtendedGlobusPrincpal?
XACML stuff adding to gPlazma.
VOMS unit-testing
Al
Q: what to do about the setup for the tests?
The kind of tests needs the PKI Verifier class. If it doesn't find the OpenSSL-style certs directory then it complains.
What are you testing? Can we mock it? Can we write a replacement?
There's a class we access to obtain the attributes: mostly testing this external code.
Start of by writing mock-code (or similar) or just not putting unit-test just now. Look at testing this later on.
Took a while to mock the XACML client.
VOMS principals
Discussion taken offline (mailing list)
Issues from yesterday's Tier-1 meeting
We could open a ticket against DavFS about lack of redirect support.
Patrick has suggested they use NFS/4.1 instead.
Perhaps the student could work on this ... but this would require further investigation.
Patrick: ask Gerd for contact within Swegrid about fixing WebDAV clients.
Lots of (commercial) webdav based storage services available now but they all redirect on DNS level, never at HTTP level.
Maybe they do a trick: TSM trick call GET with zero-length first. At that point, if you do redirect, they would work. Before creating the file they do GET with zero-length. This might be to discover a redirect; the client would follow the redirect before doing a PUT.
Issues from EMI
Regression tests
Requests for Change (RfC) and regression tests are desired by EMI. My personal opinion is that a test driven development could be beneficial to our software quality.
RfCs? created: http://rt.dcache.org/Dashboards/6786/EMI%20RfCs
UnitTests?: making them available online: http://www.avajava.com/tutorials/lessons/how-do-i-generate-a-unit-test-report-for-a-site.html?page=2
No new release without all packages being produced
https://savannah.cern.ch/task/?24851
There are RfCs? for EMI-2. These are in the tracker. Need to identify whether we have any tests for these (unit-test or functional test).
Update to our RT to allow recording which tests are available. This allows Christian to keep track of this information and provide it for EMI.
Unit-tests available via HTTP URL link pointing to an HTML page that describes the result PASS/FAIL of running the tests. Christian: look at output from Hudson to see if this is sufficient.
There's also a plugin in Maven that also provides this kind of information.
Documentation Issues
https://savannah.cern.ch/task/index.php?25302
Patrick: we got agreement on current format.
Antje: to look at adding funding statement.
Making SRM-client Debian/EPEL compliant
Description of how to layout files so a package is Debian/FHS compliant:
This file describes what files should go where: http://www.pathname.com/fhs/pub/fhs-2.3.pdf
Outstanding RT Tickets
[This is an auto-generated item. Don't add items here directly]
Review of RB requests
httpd script: alias for billing pointing to the old billing cell. Is this still being used?
Tanja to look into this.
DTNM
Proposed: same time, next week.
