Date: | Thu, 03 Sep 2015 16:58:09 +0100 |
---|---|
From: | Matthew Hinton <matth@xxxxxxxxxxxxxx> |
Subject: | Re: [HTCondor-devel] Inclusion of additional arguments to docker run |
Hi, Thanks for getting back to me so quickly. That is indeed our use case. More specifically, we have a /shared/ volume on each of the hosts (hence why it's fine for now) which holds data to be processed as input by the programs running in the containers and then new files are passed out (usually to a /shared/scratch directory). We're dealing with TB of data in total (though each job only deals with ~GB) so file copies of the input / output are not an option (using transfer_files). I'm not sure I understand your solution. Are you saying that each node will advertise which volumes it has available (i.e. something like ÂHasVolumes = /shared/...), which the administrator can set in the condor_config.local file or similar. Then, when submitting jobs, if the docker_volume argument is passed then it will only run on machines which HasVolumes contains the required volume? That would be ideal really. Thanks for getting back to me, Matt On 3 September 2015 at 16:40, Greg Thain <gthain@xxxxxxxxxxx> wrote: On 09/03/2015 03:42 AM, Matthew Hinton wrote: |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | Re: [HTCondor-devel] Inclusion of additional arguments to docker run, Greg Thain |
---|---|
Next by Date: | , (nil) |
Previous by Thread: | Re: [HTCondor-devel] Inclusion of additional arguments to docker run, Greg Thain |
Next by Thread: | , (nil) |
Indexes: | [Date] [Thread] |