I assume the larger VOs are using glideinWMS to have a factory submit glideins through your CE on their behalf?Â In general, CEs are designed mainly to support pilot jobs coming through them, not payload jobs.Â Also, I assume there's a reason these smaller VOs can't use glideinWMS to send pilots to DESY?
Otherwise, it is possible to have a "glidein lite", where these VOs or maybe DESY itself sends pilot condor startds through the CE that are designed to augment these VO's home pool.
we are running CondorCEs, where so far larger VOs have been the only users. Now we got asked by a smaller group how they could use the CondorCEs to submit their grid jobs to us.
(I had a similar question before, but that has been more or less for internal monitoring of the job flow)
While in principle I as a user can submit a job directly to a CondorCE, the overall usage is more orientated to be used through a production system - which might be too much for a smallish group.
Thus, I am looking for a good way on how to make the CondorCEs accessible, so that the group can
Â* submit jobs
Â* query their and only their job states
Â* stage results back
from the command line and which is also GDPR compliant.
Is there already a suggested setup for such a use case?
Cheers and thanks,
_______________________________________________ HTCondor-users mailing list To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a subject: Unsubscribe You can also unsubscribe by visiting https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users The archives can be found at: https://lists.cs.wisc.edu/archive/htcondor-users/