-
Notifications
You must be signed in to change notification settings - Fork 1
/
README.md.old
115 lines (95 loc) · 3.06 KB
/
README.md.old
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
Complete Condor batch system on Mesos cluster
=========
How to deploy Condor within a Mesos cluster on Openstack via Heat
<pre>
> git clone https://github.com/Cloud-PG/mesos-condor-cluster.git
> cd mesos-condor-cluster
> vim env_heat_condor
> heat stack-create -f mesoscluster-condor.yaml -e env_heat_condor CLUSTER_NAME</pre>
In "env_heat" modify this parameters:
- `network` is the id of the Openstack network used in your project;
- `ssh_key_name` is the name of the ssh key to inject into your cluster machines;
- `master_flavor`, `loadbalancer_flavor` and `slave_flavor` are the names or ids of the flavors to be used to create the mesos master/slave/loadbalancer VMs;
- `number_of_slaves` and `number_of_masters` is the number of VMs to spawn;
- `server_image` is the name/id of the virtual image to be used to launch the VMs;
You now have an empty Mesos/Marathon cluster.
Run Condor dockers manually
--------------
<pre>
> docker run -d --name=master2 dscnaf/htcondor-debian -m</pre>
Using Marathon
--------------
Master json:
<pre>{
"id": "htcondor-master-debian",
"args": ["-m"],
"cpus": 1,
"mem": 512.0,
"container": {
"type": "DOCKER",
"docker": {
"image": "ciangom/htcondor-docker-debian",
"network": "BRIDGE",
"portMappings": [
{"containerPort": 9618, "servicePort": 9618}
]
}
}
}</pre>
Submitter json:
<pre>{
"id": "htcondor-submitter-debian",
"args": ["-s", "192.168.150.65"],
"cpus": 1,
"mem": 512.0,
"container": {
"type": "DOCKER",
"docker": {
"image": "ciangom/htcondor-docker-debian",
"network": "BRIDGE"
}
}
}</pre>
Executor json:
<pre>{
"id": "htcondor-executor-debian",
"args": ["-e", "192.168.150.65"],
"cpus": 1,
"mem": 512.0,
"instances": 3,
"container": {
"type": "DOCKER",
"docker": {
"image": "ciangom/htcondor-docker-debian",
"privileged": true,
"network": "BRIDGE"
}
}
}</pre>
Tests
==================
From the slave containing schedd-docker:
<pre>root@mesos-s1:~# docker exec -it "schedd-docker-id" bash
root@f329f012e05f:/# apt-get install vim -y
root@f329f012e05f:/# useradd -m -s /bin/bash asd
root@f329f012e05f:/# su - asd
asd@f329f012e05f:~$ vim sleep.sh
#!/bin/bash
/bin/sleep 20
asd@f329f012e05f:~$ vim sleep.sub
executable = sleep.sh
log = sleep.log
output = outfile.txt
error = errors.txt
should_transfer_files = Yes
when_to_transfer_output = ON_EXIT
queue
asd@f329f012e05f:~$ condor_status
asd@f329f012e05f:~$ condor_submit sleep.sub
asd@f329f012e05f:~$ condor_q
asd@f329f012e05f:~$ condor_status</pre>
Docker problems (mail Marica)
==================
In /etc/condor/condor_config wrong path for "libexec"; correct one is /usr/lib/condor/libexec, current is /usr/libexec
Update: Riesco a specificare le porte e gli indirizzi, ma lo schedd cerca di collegarsi all'indirizzo locale del master (172. ecc) mentre il master è in ascolto sull'indirizzo ip dell'host. Da risolvere
Update2: Risolto problema porte. Rimodificato il condor_config riguardo alle policy di ALLOW