Hi Steve,
That's not a bad idea but I'd probably need to do some reinstalling
which will take more effort than I was hoping to expend! Let's see what
the discussions from tomorrow yield...
Thanks!
Mark
On 11/03/2018 09:37, sjones wrote:
> Perhaps the simplest thing is to leave CREAM on, with one node, only
> to make BDII output (incl. VAC capacity) and run tests. Until these
> other arrangements kick in, anyway.
>
> Cheers,
>
> Ste
>
>
> On 2018-03-09 14:03, Andrew McNab wrote:
>> 1) How to run the LHC experiment SAM (ETF) tests.
>>
>> LHCb already runs the ETF tests inside the VMs too (as part of the
>> pilot) so that’s done. I’ve started an email thread about the
>> possibility of submitting the ATLAS ETF test jobs to the HTCondor
>> pools that the VMs get the ATLAS pilots from. That should work for
>> ALICE too.
>> 2) How to run the EGI ops SAM tests
>>
>> Do we need to do this at Vac/Vcycle-only sites? UCL stopped running
>> them when they turned off CREAM years ago. It’s really a political
>> question (related to the question of why we still care about them at
>> all.)
>>
>> 3) How to get capacity included in REBUS
>>
>> We discussed this late last year, and there is a route to do it by
>> putting the capacity information into GOCDB (which is on the WLCG
>> InfoSys TF roadmap) and then getting it into REBUS from there (via
>> CRIC maybe.) This needs to happen somehow when WLCG drops the
>> requirement for sites to run BDII. In the meantime, maybe we could run
>> a BDII server with just this information, maintained manually for the
>> relevant sites?
>
|