chaen
chaen
Can you remind me why we did not do it for the LHCb DB ?
I know pretty much nothing in all that aspect of DIRAC, but from the little I know, this seems pretty well crafted ! :-)
Part of it is in https://github.com/DIRACGrid/DIRAC/pull/7077/commits/f6f0e37504c97e6a38549c40397ddbf15addebe2 For `remove-catalog-replicas`, why not just using `dirac-dms-remove-replicas` ? it will tell you if you are trying to delete the last replicas. Also, this behavior...
That has been observed today in production in LHCb. Edit: to be precise, I did not have 2 tabs opened. I had a single web app open, but when talking...
These are nice ideas, and we welcome PR ! The input data resolution being based on plugins, it should not be too difficult for you to extend. You should find...
why ? I'd keep that one opened. Indeed it's not planned, but it would still be nice to have :-/
I believe this was the original idea behind https://github.com/DIRACGrid/DIRAC/issues/4077 and https://github.com/DIRACGrid/DIRAC/pull/4230 Now before doing any more move, I am waiting for the doc.
yes, this method also will need to be updated, depending on how/what one wants to check
Thanks for the RFC, it is well described. I will comment here, as I don't think I can comment on the RFC directly. I do appreciate this idea of replicating...
it's actually much worse than this ! The Agent will create (buggy) removal request at every loop, because it creates the removal requests before attempting to delete the job. https://github.com/DIRACGrid/DIRAC/pull/5414