Marcin Radecki wrote:
> Hi Alessandro,
>
>> in the case of replication tests done through CE submission, the TOP
>> BDII used in the farm is *known* and the SAM test itself could do a
>> query to that particular Core Service SAM results:
>> - if CS test was FAILED: try anyway and if Rep fails write CSFAIL
>> - if CS test was GOOD proceed as usual (OK or FAIL)
>> - if CS test Not Available, shout it very loud, because CS *must* be
>> controlled, registered in GOCDB, etc...
>
> Your approach of using SAM results could be generalized into: SAM tests
> should check all their dependencies in order to detect CS failure. Let's
> stay with RM example which would need to check results for:
> - top level BDII
> - VO LFC (used to register an LFN)
> - central SE (SAM submission checks status of the SE beforehand = should
> be OK, but in the meantime might got bad)
>
> Then if any of dependencies is in ERROR state return CSFAIL. Of course
> if not possible to query SAM - don't care about it and do as usual. I
> wonder if that would scale in terms of SAM DB...
I'm not 100% sure, but I think that LAST SAM results are summary data
very quickly available, and not to be deeply digged from the DB history.
In this case, maybe it can scale...
Alessandro
>
> Marcin
--
Alessandro Cavalli
INFN - CNAF
Viale Berti Pichat 6/2
40127 Bologna
Italy
tel: +39 051 6092849
fax: +39 051 6092746
ICQ: 12771368
MSN: [log in to unmask]
Skype name: alessandro.cavalli
|