arc-ce: Export arc-ce feature from aquilon at RAL #232
Conversation
This prevents the named user accounts performing actions at the HTCondor level.
Specify lists of central service nodes, submitters, users and worker nodes.
These groups are then used for priorities, fairshares and limits.
"Without the condor_shared_port daemon, approximately 2.1 ephemeral ports per running job are required, and possibly more, depending on the rate of job completion."
For compatibility with monitoring scripts and tooling that parses output directly
It is very improtant to clean these up automatically, otherwise disk space will disappear very quickly.
Very large output files are known to cause problems with grid frameworks, so we knobble them.
…g use Add base of arc-ce feature - number of running & idle jobs by VO Add arc-ce jobs config Clean up jobs.pan Add condorjobs.sh
* scaling_factors_plugin.py * job_logs_to_s3.py * default_rte_plugin.py
This contains an empty mapping for all DNs to nobody as we only want ARGUS providing these mappings.
* Map queue name to the operating system version, we provide two images the jobs will run in - EL6 and EL7. * Specify the tags (versions) of the containers to allow us to control testing and rollout of updated images. * Make use of external data scraped for DockerHub by and hourly cron to validate that specified tags do actually exist.
Clean up service.pan Add queues.conf Add arc.conf
Clean up atlas-site-lcg.pan Clean up biomed.pan Clean up enmr.pan Clean up glite.pan Clean up proxy.pan Clean up t2k.pan Cleanup runtime-environments config
Move condor related file to subdirectory and update references - condor/limits
Move condor related file to subdirectory and update references - resourcelimits
|
HI, |
|
Probably not, there is definitely a large number of things to be improved with these templates. |
|
@jrha I completely forgot about this PR... What do you want to do? I think having some templates, even not perfect, for the ARC CE is a great addition. We just need to resolve the issue mentioned by @sartiran: there is already a set of templates to configure HTCondor. Does it makes sense to provide ARC CE templates relying on them? I guess it is not so simple... In this case may be we should rename the namespace used for the HTCondor templates provided here into something highliting the link with the ARC CE templates. Something like |
|
I think this is probably worth revisiting in the next release, our templates have almost certainly moved on quite a bit now. |
As the title suggests, this is a lightly sanitised copy of the (ARC 5) CE feature used at RAL, which is itself a hurriedly transcribed copy of the configuration from our old SCDB instance.
Nevertheless it is provided here in the hope it may be of use to someone.
May resolve #221.