...
Some features of the HTCondor in EWC:
Maintenance | Centrally Managed Tenancy, easy 'one click' deployment |
Deployment | Multi tenancy |
Resource | Join automatically the main HTCondor Pool, no need for password or any configuration, only choose the plan for the machine your want to add |
Usage | Easy 'one click' deployment, simple examples for running a job with docker universe |
Network | VPN, which allows processing nodes in a tenancy to communicate with the scheduler / master nodes |
Scheduling | Single schedulers in each tenancy, no possibility to erase other tenancies jobs |
Execute nodes
- No access to execute host for containers
- No access to other containers running on execute node
- Isolated environment for containers
- No autoscaling
- No NFS
...
htcondor security group with the following rules:
Rule name | Direction | Rule Type | Protocol | Port Range | Source Type | Source | Destination Type |
|---|---|---|---|---|---|---|---|
egress | Custom Rule | TCP | All | Instance | |||
egress | Custom Rule | UDP | All | Instance | |||
9618-tcp | ingress | Custom Rule | TCP | 9618 | Network | 100.64.0.0/10 | Instance |
Deploy execute or submit node
...
| Code Block |
|---|
# dockertest.sub -- example docker job universe = docker docker_image = debian executable = /bin/cat arguments = /etc/hosts should_transfer_files = YES when_to_transfer_output = ON_EXIT log = log/job_$(Process)_sleep.log output = output/job_$(Process)_output.txt error = error/job_$(Process)_errors.txt request_cpus = 1 request_memory = 1024M request_disk = 10240K queue 10010 |
- use condor_submit <job_name>
- verify jobs are running, using condor_q command
...