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...
Marcin
|