Hi John,
Basically I agree with you. It's just frustrating me no end that there
is such a simple way to address this but it isn't being done, at the
cost of dozens of site admins having to do more work themselves. It's
not just this one item which is probably easy to fix by hand. I would
like to establish the general principle that I stated at the end of my
last email and that I seem to keep banging on about at meetings. To get
a working site, it shoudl not be necessary to do anything beyond what is
written in the installation and (to be done) maintenance instructions.
The amount of hot air we have expended on this is far more effort than
it would have taken for someone to copy the new apel rpm into the lcg
updates dir and run the necessary yum and apt commands to make it visible.
Rant over, thanks to Jeremy for taking this up at the EGEE/LCG workshop.
Anyway, in practice I can assure you that at RHUL we are not sitting
back; we are really busy with other work, so the easier it is to have
the right software installed and correctly configured, the sooner (and
more often) we will be able to do it.
Cheers,
Simon
Gordon, JC (John) wrote:
> I agree that the problem is with LCG but LHCC has asked that they
> receive accounting for all LHC experiments so we need to work round the
> problems. APEL is a UK product so we also want to show it in the best
> light. Having all UK sites publishing is one thing we can do. We have
> all been told about it on this list. Pragmatically is it not better to
> make your site work that sit back and say 'I fail but it is not my
> fault'?
>
> I will get someone to raise the issue of patches at the Operations
> Workshop starting soon.
>
> John
>
>
>>-----Original Message-----
>>From: Testbed Support for GridPP member institutes
>>[mailto:[log in to unmask]] On Behalf Of Simon George
>>Sent: 24 May 2005 11:06
>>To: [log in to unmask]
>>Subject: Re: Sites not publishing accounting data
>>
>>Hi Jeremy,
>>
>>at the last tb-support meeting, as far as I recall, it was confirmed
>>that the accounting package in LCG 2.4.0 does not work, which was
>>thought likely to be the reason why some sites (e.g. RHUL)
>>had followed
>>the installation instructions but not got accounting working.
>>
>>I asked why fixes considered necessary (like this) are not
>>put in to the
>>apt/yum rpm respository for LCG software, so they can be upgraded
>>automatically or by site admins just running the standard update
>>command. We are already doing this to get o/s updates and CA
>>updates. It
>>has to be by far the easiest and most standard way to distribute both
>>important bug fixes and security fixes. I don't see why this
>>needs to be
>>any more complicated. Has there been any progress on this?
>>
>>I still maintain that I should not have to go beyond the 2.4.0
>>installation instructions (and maintenance instructions when they are
>>available) to get my site functioning as fully as LCG needs.
>>If that is
>>not true, the the problem is with LCG 2.4.0, not my site!
>>
>>Cheers,
>>Simon
>>
>>Coles, J (Jeremy) wrote:
>>
>>>Dear All
>>>
>>>At the last TB-SUPPORT meeting we reviewed sites not
>>
>>publishing accounting data but reiterated the need for this
>>to be collected so that we understand usage of the resources.
>>
>>>The following sites are still not producing any data.
>>
>>Please could the relevant Tier-2 coordinator follow up with
>>their sites to understand any problems:
>>
>>>hp-bristol
>>>csTCDie
>>>Cavendish-LCG2
>>>LivHEP-LCG2
>>>QMUL-eScience
>>>RHUL-LCG2
>>>UCL-HEP
>>>
>>>I understand that there are some special cases here. If
>>
>>there are problems with the site (publishing) we need to
>>understand how to improve the situation. Where everything is
>>set up correctly but jobs are just not arriving we need to
>>follow up with the VOs.
>>
>>>Many thanks,
>>>Jeremy
>>
|