There has been no blog post for almost half a year. It does not mean that nothing has happened since than. We devoted enormous effort to some background works (automated test bed, nightly builds and test runs, change to EMI era from EGEE, etc.). We will test the tools and the procedures in the first months of 2011, analyze if they have added value and how they could be improved. As for the visible part, we released GFAL/LCG_Util 1.11.16 (finally) in November - see the release notes. Better later than never!
Showing posts with label release. Show all posts
Showing posts with label release. Show all posts
Tuesday, December 21, 2010
GFAL / LCG_Util 1.11.16 release
There has been no blog post for almost half a year. It does not mean that nothing has happened since than. We devoted enormous effort to some background works (automated test bed, nightly builds and test runs, change to EMI era from EGEE, etc.). We will test the tools and the procedures in the first months of 2011, analyze if they have added value and how they could be improved. As for the visible part, we released GFAL/LCG_Util 1.11.16 (finally) in November - see the release notes. Better later than never!
Friday, December 18, 2009
As wrapping up the year we have a GFAL/lcg_util v1.11.13, FTS 2.2.4 and DPM/LFC v1.7.4.
Details are in the data management relese notes.
This FTS snapshot already has a secure preview of the administrative web interface:
Details are in the data management relese notes.
This FTS snapshot already has a secure preview of the administrative web interface:
Wednesday, November 25, 2009
FTS releases
The current, 'WLCG approved' version of FTS is FTS 2.1.
gLite has already released FTS 2.2 (i.e. FTS 2.2.0), however Atlas has
discovered some shortcomings with the checksum suppport in the
Pilot service, which were fixed in the upcoming FTS 2.2.1 and
FTS 2.2.2 releases.
FTS 2.2.2 has been certified by gLite and installed on the CERN FTS
Pilot service and will be running until the beginning of December
to reach the 'WLCG approved' status.
Currently we are working on FTS 2.2.3 to address a few more issues.
Have a look at the FTS patch status page for more details on older releases!
gLite has already released FTS 2.2 (i.e. FTS 2.2.0), however Atlas has
discovered some shortcomings with the checksum suppport in the
Pilot service, which were fixed in the upcoming FTS 2.2.1 and
FTS 2.2.2 releases.
FTS 2.2.2 has been certified by gLite and installed on the CERN FTS
Pilot service and will be running until the beginning of December
to reach the 'WLCG approved' status.
Currently we are working on FTS 2.2.3 to address a few more issues.
Have a look at the FTS patch status page for more details on older releases!
releases
My magic URL for upcoming data management releases points into Savannah.
We usually create a 'patch' (i.e. release) when we have a draft idea of what should
go into a release. For example FTS 2.2.3 and GFAL 1.11.13 are created with all the
bugs attached that we intend to implement by the release date.
The first noteworthy state is 'Ready for certification', when the developers have
finished their work and there are already RPMs created. At this point we usually
upload the packages into our Release Candidate repository for the convenience of
early testers.
The next noteworthy state is 'Certified', when the release has passed all regression
tests and the new features seem to be working.
After this state there is a few weeks of testing (i.e. waiting if there is any unexpected
behaviour) in the pre-production testbed (PPS) and then comes the gLite release.
We usually create a 'patch' (i.e. release) when we have a draft idea of what should
go into a release. For example FTS 2.2.3 and GFAL 1.11.13 are created with all the
bugs attached that we intend to implement by the release date.
The first noteworthy state is 'Ready for certification', when the developers have
finished their work and there are already RPMs created. At this point we usually
upload the packages into our Release Candidate repository for the convenience of
early testers.
The next noteworthy state is 'Certified', when the release has passed all regression
tests and the new features seem to be working.
After this state there is a few weeks of testing (i.e. waiting if there is any unexpected
behaviour) in the pre-production testbed (PPS) and then comes the gLite release.
Friday, October 16, 2009
Chrome for ETICS
I have tried Chrome with the ETICS web interface and the speed improvement of the JavaScript engine is impressive.
The only catch is the authentication, which you have to solve by command line tools, as Google expects that the OS provides the GUI for certificate handling.
To solve the bootstrapping problem here are some useful commands, given that you have libnss3-tools and ca-policy-igtf-classic installed:
cd ~/.globus
openssl pkcs12 -export -inkey userkey.pem -in usercert.pem -out usercert.p12
certutil -d sql:$HOME/.pki/nssdb -i ~/.globus/usercert.p12
certutil -d sql:$HOME/.pki/nssdb -A -t "C,," -n cern-root -i /etc/grid-security/certificates/d254cc30.0
certutil -d sql:$HOME/.pki/nssdb -A -t "C,," -n cern-online -i /etc/grid-security/certificates/1d879c6c.0
Friday, August 7, 2009
transfer-url-copy version 3.2.1-rel2 released
The affected module is: org.glite.data.transfer-url-copy.
The changes are:
glite-data-transfer-url-copy_R_3_2_1_2
The functionality and the behaviour have not been changed.
See the component in the CVS.
The changes are:
- Warning removal
- The result of the code review implemented partially: descriptive enum-s to signal the actual checksum checking use case.
glite-data-transfer-url-copy_R_3_2_1_2
The functionality and the behaviour have not been changed.
See the component in the CVS.
Subscribe to:
Posts (Atom)