19 December 2006

Agenda for this weeks meeting can be found here:

http://indico.cern.ch/conferenceDisplay.py?confId=10067

18 December 2006

A new version of dcache-server was released on Wednesday, v1.7.0-23. I've
installed it and so far things seem to be running fine. One problem that I
came across was when trying to restart the processes following the
upgrade. SRM was complaining that there was no tomcat startup script:

/opt/d-cache/bin/dcache-srm: line 22:
/opt/d-cache/libexec/apache-tomcat-5.5.20/bin/startup.sh: No such file or
directory

This isn't that surprising since we all have jakarta-tomcat-4.1.31
installed. I just changed the line in the dcache-srm script to point to
the correct location for the tomcat start script and then ran ./dcache-srm
start. Everything seems to be OK now.

I'll follow up with the dCache people to find out what's going on.

12 December 2006

Agenda for this weeks meeting can be found here:

http://indico.cern.ch/conferenceDisplay.py?confId=9766

06 December 2006

Minutes of today's meeting are available.
Agenda for this week's meeting can be found here.

29 November 2006

Minutes now uploaded for today's meeting.

27 November 2006

Storage meeting: Wed 29th Nov 2006

Agenda: http://indico.cern.ch/conferenceDisplay.py?confId=9245

23 November 2006

A new version of dCache was released on 20th November 2006. dcache-server-1.7.0-20 can be obtained from the dcache.org repository. If using apt, then add this to a file in sources.list.d .

rpm http://www.dcache.org/apt/ sl stable

Some notes on upgrading to the 1.7.0 release can be found in the wiki.
There will be a WLCG workshop at CERN from the 22nd to 26th January 2007. GridPP will fund one person from eash Tier-2 site along with additional personnel. Contact Jeremy Coles if you would like to attend.
There will be a dCache workshop at DESY on the 18th and 19th January 2007. Tied in with this, there will be a virtualistion workshop on the 16th and 17th January. Those interested in attending should contact Jeremy Coles regarding funding.

22 November 2006

Hi everyone. Now, don't get mad, I know that you're saying "What are they doing, not another !@^&*$ blog!" but hold on, let me explain...

Over the past couple of years, the GRIDPP-STORAGE mailing list has grown such that we now have a fairly respectable number of subscribers (about 50 at last count). However, I have found from speaking to people that while most (if not all) of the postings are useful on a technical level, some subscribers feel that they cannot read through everything due to the volume of other email traffic that they have to parse. As a result, emails get filtered to a 'not often read' folder in your mail client. Of course, this means that important announcements like meeting agendas, new software releases and workshop dates can be missed, resulting in sites not knowing what software is available as well as when/how they should be upgrading.

The idea behind this blog is to rectify the situation. The blog will **NOT** become a forum for discussion of storage related issues; that will remain the purpose of the GRIDPP-STORAGE list/weekly meetings. What the blog **WILL** be used for is for making important announcements that (I believe) every site should be made aware of, thereby shielding them from the day-to-day technical discussions while still providing access to important information.

From this point of view, the real benefit of using blogger.com is that you can subscribe to the RSS or ATOM feed of the blog, meaning that you don't even have to check if a new posting has been made. As an example, I'm using the Sage plugin for Firefox, but there are loads of others available. A click of a button forces the RSS reader to check the blog feed and if something new has been posted the reader should let you know; otherwise nothing will change and you can go about your business as normal. Hopefully some people will find the news feed useful if used like this.

Of course, if you think this is all just a gimmick and will quickly become lost among your other RSS/ATOM feeds then you can ignore it completely and continue to read/filter the mailing list traffic. The decision is yours.

Thanks,
Greig