Project

General

Profile

Dispatching containers to cloud VMs » History » Version 69

Tom Clegg, 06/18/2019 05:57 PM

1 1 Tom Clegg
h1. Dispatching containers to cloud VMs
2
3 6 Tom Clegg
(Draft)
4 1 Tom Clegg
5 11 Tom Clegg
{{>toc}}
6
7 7 Tom Clegg
h2. Component name / purpose
8 1 Tom Clegg
9 53 Tom Clegg
arvados-dispatch-cloud runs Arvados user containers on generic public cloud infrastructure by automatically creating and destroying VMs of various sizes according to demand, preparing the VMs' runtime environments, and running containers on them.
10 1 Tom Clegg
11 49 Tom Clegg
h2. Overview of operation
12
13
The dispatcher waits for containers to appear in the queue, and runs them on appropriately sized cloud VMs. When there are no idle cloud VMs with the desired size, the dispatcher brings up more VMs using the cloud provider's API. The dispatcher also shuts down idle VMs that exceed the configured idle timer -- and sooner if the provider starts refusing to create new VMs.
14
15
h2. Interaction with other components
16
17
Controller (backed by RailsAPI and PostgreSQL) supplies the container queue: which containers the system should be trying to execute (or cancel) at any given time.
18
19
The cloud provider's API supplies a list of VMs that exist (or are being created) at a given time and their network addresses, accepts orders to create new VMs, updates instance tags, and (optionally, depending on the driver) obtains the VMs' SSH server public keys.
20
21 57 Tom Clegg
The SSH server on each cloud VM allows the dispatcher to authenticate with a private key and execute shell commands as root (either directly or via sudo).
22 49 Tom Clegg
23
h2. Instance tags
24
25
The dispatcher relies on the cloud provider's tagging feature to persist state across server restarts.
26
* {"InstanceType": "foo"} indicates that the instance was created with the specs from the instance type named "foo" in the cluster configuration file.
27 50 Tom Clegg
* {"IdleBehavior": "hold"} indicates that the management API has been used to put the instance in "hold" state.
28 58 Tom Clegg
* {"InstanceSecret": "ad23b6a8912f2b75d8a5e6887fbcb82f8024daea"} is a random string used to verify the instance's SSH host key.
29 49 Tom Clegg
30
Provider-specific drivers (Amazon, Google, Azure) determine exactly how these tags are encoded in the cloud API, and can use tags to persist their own internal state as well. For example, a driver might save tags named "Arvados-DispatchCloud-InstanceType" rather than just "InstanceType".
31
32 23 Tom Clegg
h2. Deployment
33 24 Tom Clegg
34 53 Tom Clegg
*Where to install:* The arvados-dispatch-cloud process can run anywhere, as long as it has network access to the Arvados controller, the cloud provider's API, and the worker VMs. Each Arvados cluster should run only one arvados-dispatch-cloud process.
35 9 Tom Clegg
* Future versions will support multiple dispatchers.
36 1 Tom Clegg
37 9 Tom Clegg
*Dispatcher's SSH key:* The operator must generate an SSH key pair for the dispatcher to use when connecting to cloud VMs. The private key is stored (without a passphrase) in the cluster configuration file. It does not need to be saved in @~/.ssh/@.
38 1 Tom Clegg
39 56 Tom Clegg
*Cloud VM image:* The operator must provide a VM image with an SSH server on a port reachable by the dispatcher (default 22, configurable per cluster). The dispatcher's SSH public key must be listed in @/root/.ssh/authorized_keys@. The image should also include systemd-cat (part of systemd) and suitable versions of docker and crunch-run. The @/var/lock@ directory must be available for lockfiles with names matching "@crunch-run-*.*@".
40 1 Tom Clegg
* It is possible to install docker and crunch-run using a custom boot probe command, but pre-installing is more efficient.
41
* Future versions will automatically sync the crunch-run binary from the dispatcher host to each worker node.
42 56 Tom Clegg
* The Azure driver creates a new admin user account and installs the SSH public key by itself so @/root/.ssh/authorized_keys@ is not needed. The VM image must include @sudo@.
43 1 Tom Clegg
44 6 Tom Clegg
*Cloud provider account:* The dispatcher uses cloud provider credentials to create and delete VMs and other cloud resources. An Arvados user can create an arbitrary number of long-running containers, and the dispatcher will try to run all of them. Currently the dispatcher does not enforce any resource limits of its own, so the operator must ensure the cloud provider itself is enforcing a suitable quota.
45 53 Tom Clegg
46 52 Tom Clegg
*Migrating from nodemanager/SLURM:* When VM images, SSH keys, and configuration files are ready, disable nodemanager and crunch-dispatch-slurm. Install arvados-dispatch-cloud deb/rpm package. Confirm success with @systemctl status arvados-dispatch-cloud@ and @journalctl -fu arvados-dispatch-cloud@. See [[Migrating from arvados-node-manager to arvados-dispatch-cloud]].
47 1 Tom Clegg
48 6 Tom Clegg
h2. Configuration
49 1 Tom Clegg
50 42 Tom Clegg
Arvados [[Cluster configuration]] (currently a file in /etc) supplies cloud provider credentials, allowed node types, spending limits/policies, etc.
51 1 Tom Clegg
52 6 Tom Clegg
<pre><code class="yaml">
53
    CloudVMs:
54 1 Tom Clegg
      BootProbeCommand: "docker ps -q"
55 42 Tom Clegg
      SSHPort: 22
56 27 Tom Clegg
      SyncInterval: 1m    # how often to get list of active instances from cloud provider
57 8 Tom Clegg
      TimeoutIdle: 1m     # shutdown if idle longer than this
58
      TimeoutBooting: 10m # shutdown if exists longer than this without running BootProbeCommand successfully
59
      TimeoutProbe: 2m    # shutdown if (after booting) communication fails longer than this, even if ctrs are running
60
      TimeoutShutdown: 1m # shutdown again if node still exists this long after shutdown
61 6 Tom Clegg
      Driver: Amazon
62 8 Tom Clegg
      DriverParameters:   # following configs are driver dependent
63 6 Tom Clegg
        Region: us-east-1
64 59 Tom Clegg
        AccessKeyID: abcdef
65
        SecretAccessKey: abcdefghijklmnopqrstuvwxyz
66 39 Tom Clegg
        SubnetID: subnet-01234567
67 59 Tom Clegg
        SecurityGroupIDs: sg-01234567
68
        AdminUsername: ubuntu
69
        EBSVolumeType: gp2
70 8 Tom Clegg
    Dispatch:
71
      StaleLockTimeout: 1m     # after restart, time to wait for workers to come up before abandoning locks from previous run
72
      PollInterval: 1m         # how often to get latest queue from arvados controller
73
      ProbeInterval: 10s       # how often to probe each instance for current status/vital signs
74
      MaxProbesPerSecond: 1000 # limit total probe rate for dispatch process (across all instances)
75
      PrivateKey: |            # SSH key able to log in as root@ worker VMs
76
        -----BEGIN RSA PRIVATE KEY-----
77
        MIIEowIBAAKCAQEAqYm4XsQHm8sBSZFwUX5VeW1OkGsfoNzcGPG2nzzYRhNhClYZ
78
        0ABHhUk82HkaC/8l6d/jpYTf42HrK42nNQ0r0Yzs7qw8yZMQioK4Yk+kFyVLF78E
79
        GRG4pGAWXFs6pUchs/lm8fo9zcda4R3XeqgI+NO+nEERXmdRJa1FhI+Za3/S/+CV
80
        mg+6O00wZz2+vKmDPptGN4MCKmQOCKsMJts7wSZGyVcTtdNv7jjfr6yPAIOIL8X7
81
        LtarBCFaK/pD7uWll/Uj7h7D8K48nIZUrvBJJjXL8Sm4LxCNoz3Z83k8J5ZzuDRD
82
        gRiQe/C085mhO6VL+2fypDLwcKt1tOL8fI81MwIDAQABAoIBACR3tEnmHsDbNOav
83
        Oxq8cwRQh9K2yDHg8BMJgz/TZa4FIx2HEbxVIw0/iLADtJ+Z/XzGJQCIiWQuvtg6
84
        exoFQESt7JUWRWkSkj9JCQJUoTY9Vl7APtBpqG7rIEQzd3TvzQcagZNRQZQO6rR7
85
        p8sBdBSZ72lK8cJ9tM3G7Kor/VNK7KgRZFNhEWnmvEa3qMd4hzDcQ4faOn7C9NZK
86
        dwJAuJVVfwOLlOORYcyEkvksLaDOK2DsB/p0AaCpfSmThRbBKN5fPXYaKgUdfp3w
87
        70Hpp27WWymb1cgjyqSH3DY+V/kvid+5QxgxCBRq865jPLn3FFT9bWEVS/0wvJRj
88
        iMIRrjECgYEA4Ffv9rBJXqVXonNQbbstd2PaprJDXMUy9/UmfHL6pkq1xdBeuM7v
89
        yf2ocXheA8AahHtIOhtgKqwv/aRhVK0ErYtiSvIk+tXG+dAtj/1ZAKbKiFyxjkZV
90
        X72BH7cTlR6As5SRRfWM/HaBGEgED391gKsI5PyMdqWWdczT5KfxAksCgYEAwXYE
91
        ewPmV1GaR5fbh2RupoPnUJPMj36gJCnwls7sGaXDQIpdlq56zfKgrLocGXGgj+8f
92
        QH7FHTJQO15YCYebtsXWwB3++iG43gVlJlecPAydsap2CCshqNWC5JU5pan0QzsP
93
        exzNzWqfUPSbTkR2SRaN+MenZo2Y/WqScOAth7kCgYBgVoLujW9EXH5QfXJpXLq+
94
        jTvE38I7oVcs0bJwOLPYGzcJtlwmwn6IYAwohgbhV2pLv+EZSs42JPEK278MLKxY
95
        lgVkp60npgunFTWroqDIvdc1TZDVxvA8h9VeODEJlSqxczgbMcIUXBM9yRctTI+5
96
        7DiKlMUA4kTFW2sWwuOlFwKBgGXvrYS0FVbFJKm8lmvMu5D5x5RpjEu/yNnFT4Pn
97
        G/iXoz4Kqi2PWh3STl804UF24cd1k94D7hDoReZCW9kJnz67F+C67XMW+bXi2d1O
98
        JIBvlVfcHb1IHMA9YG7ZQjrMRmx2Xj3ce4RVPgUGHh8ra7gvLjd72/Tpf0doNClN
99
        ti/hAoGBAMW5D3LhU05LXWmOqpeT4VDgqk4MrTBcstVe7KdVjwzHrVHCAmI927vI
100 1 Tom Clegg
        pjpphWzpC9m3x4OsTNf8m+g6H7f3IiQS0aiFNtduXYlcuT5FHS2fSATTzg5PBon9
101
        1E6BudOve+WyFyBs7hFWAqWFBdWujAl4Qk5Ek09U2ilFEPE7RTgJ
102
        -----END RSA PRIVATE KEY-----
103 9 Tom Clegg
    InstanceTypes:
104
    - Name: m4.large
105
      VCPUs: 2
106
      RAM: 7782000000
107 66 Tom Clegg
      Scratch: 32000000000
108 59 Tom Clegg
      IncludedScratch: 32000000000
109 9 Tom Clegg
      Price: 0.1
110
    - Name: m4.large.spot
111
      Preemptible: true
112
      VCPUs: 2
113
      RAM: 7782000000
114 66 Tom Clegg
      Scratch: 32000000000
115 59 Tom Clegg
      IncludedScratch: 32000000000
116 9 Tom Clegg
      Price: 0.1
117
    - Name: m4.xlarge
118
      VCPUs: 4
119
      RAM: 15564000000
120 66 Tom Clegg
      Scratch: 80000000000
121 59 Tom Clegg
      IncludedScratch: 80000000000
122 9 Tom Clegg
      Price: 0.2
123
    - Name: m4.xlarge.spot
124
      Preemptible: true
125
      VCPUs: 4
126
      RAM: 15564000000
127 66 Tom Clegg
      Scratch: 80000000000
128 59 Tom Clegg
      IncludedScratch: 80000000000
129 9 Tom Clegg
      Price: 0.2
130
    - Name: m4.2xlarge
131
      VCPUs: 8
132
      RAM: 31129000000
133 66 Tom Clegg
      Scratch: 160000000000
134 59 Tom Clegg
      IncludedScratch: 160000000000
135 9 Tom Clegg
      Price: 0.4
136
    - Name: m4.2xlarge.spot
137
      Preemptible: true
138
      VCPUs: 8
139
      RAM: 31129000000
140 66 Tom Clegg
      Scratch: 160000000000
141 59 Tom Clegg
      IncludedScratch: 160000000000
142 9 Tom Clegg
      Price: 0.4
143 6 Tom Clegg
</code></pre>
144 1 Tom Clegg
145 10 Tom Clegg
h2. Management API
146 1 Tom Clegg
147 10 Tom Clegg
APIs for monitoring/diagnostics/control are available via HTTP on a configurable address/port. Request headers must include "Authorization: Bearer {management token}".
148
149
Responses are JSON-encoded and resemble other Arvados APIs:
150
<pre><code class="json">
151
{
152 43 Tom Clegg
  "items": [
153 10 Tom Clegg
    {
154 43 Tom Clegg
      "name": "...",
155 10 Tom Clegg
      ...
156
    },
157
    ...
158
  ]
159
}
160
</code></pre>
161
162
@GET /arvados/v1/dispatch/containers@ lists queued/locked/running containers. Each returned item includes:
163
* container UUID
164
* container state (Queued/Locked/Running/Complete/Cancelled)
165
* desired instance type
166 1 Tom Clegg
* time appeared in queue
167
* time started (if started)
168
* if you're switching from slurm, this is roughly *equivalent to squeue*
169
170 69 Tom Clegg
&dagger;@POST /arvados/v1/dispatch/containers/kill?container_uuid=X@ terminates a container immediately.
171
* a single attempt is made to send SIGTERM to the container's supervisor (crunch-run) process
172 1 Tom Clegg
* container state/priority fields are not affected
173
* assuming SIGTERM works, the container record will end up with state "Cancelled"
174 10 Tom Clegg
* if you're switching from slurm, this is roughly *equivalent to scancel*
175 68 Tom Clegg
176
@GET /arvados/v1/dispatch/instances@ lists cloud VMs. Each returned item includes:
177
* provider's instance ID
178
* hourly price (from configuration file)
179
* instance type (from configuration file)
180
* instance type (from provider's menu)
181
* UUID of the current / most recent container attempted (if known)
182
* time last container finished (or boot time, if nothing run yet)
183
* if you're switching from slurm, this is roughly *equivalent to sinfo*
184 10 Tom Clegg
185 54 Tom Clegg
@POST /arvados/v1/dispatch/instances/hold?instance_id=X@ puts an instance in "hold" state.
186 34 Tom Clegg
* if the instance is currently running a container, it is allowed to continue
187
* no further containers will be scheduled on the instance
188
* the instance will not be shut down automatically
189
190 54 Tom Clegg
@POST /arvados/v1/dispatch/instances/drain?instance_id=X@ puts an instance in "drain" state.
191 1 Tom Clegg
* if the instance is currently running a container, it is allowed to continue
192
* no further containers will be scheduled on the instance
193 34 Tom Clegg
* the instance will be shut down automatically when all containers finish
194 1 Tom Clegg
195 55 Tom Clegg
@POST /arvados/v1/dispatch/instances/run?instance_id=X@ puts an instance in the default "run" state.
196
* if the instance is currently running a container, it is allowed to continue
197
* more containers will be scheduled on the instance when it becomes available
198
* the instance will be shut down automatically when it exceeds the configured idle timeout
199
200 61 Tom Clegg
@POST /arvados/v1/dispatch/instances/kill?instance_id=X@ shuts down an instance immediately.
201 1 Tom Clegg
* the instance is terminated immediately via cloud API
202 34 Tom Clegg
* SIGTERM is sent to the container if one is running, but no effort is made to give it time to end gracefully before terminating the instance
203 54 Tom Clegg
204
&dagger;@POST /arvados/v1/dispatch/loglevel?level=debug@ sets the logging threshold to "debug" or "info".
205
* @.../loglevel?level=debug@ enables debug logs
206
* @.../loglevel?level=info@ disables debug logs
207 47 Tom Clegg
208 10 Tom Clegg
h2. Metrics
209 13 Tom Clegg
210 63 Tom Clegg
Metrics are available via HTTP on a configurable address/port (conventionally :9006). Request headers must include "Authorization: Bearer {management token}".
211 10 Tom Clegg
212 13 Tom Clegg
Metrics include:
213 1 Tom Clegg
* (gauge) number of existing VMs
214 35 Tom Clegg
* (gauge) total hourly price of all existing VMs
215 46 Tom Clegg
* (gauge) total VCPUs and memory in all existing VMs
216 1 Tom Clegg
* (gauge) total VCPUs and memory allocated to containers
217
* (gauge) number of containers running
218 46 Tom Clegg
* &dagger;(gauge) number of containers allocated to VMs but not started yet (because VMs are pending/booting)
219
* &dagger;(gauge) number of containers not allocated to VMs (because provider quota is reached)
220 62 Tom Clegg
* (gauge) total hourly price of VMs, partitioned by allocation state (booting, running, idle, shutdown)
221 46 Tom Clegg
* &dagger;(summary) time elapsed between VM creation and first successful SSH connection to that VM
222
* &dagger;(summary) time elapsed between first successful SSH connection on a VM and ready to run a container on that VM
223
* &dagger;(summary) time elapsed between first shutdown attempt on a VM and its disappearance from the provider listing
224 60 Tom Clegg
* &dagger;(summary) wait times (between seeing a container in the queue or requeueing, and starting its crunch-run process on a worker) across previous starts
225
* &dagger;(gauge) longest wait time of any unstarted container
226 46 Tom Clegg
227
&dagger; not yet implemented
228
229 14 Tom Clegg
h2. Logs
230 20 Tom Clegg
231 16 Tom Clegg
For purposes of troubleshooting, a JSON-formatted log entry is printed on stderr when...
232 20 Tom Clegg
233 44 Tom Clegg
|                                                              |... if loglevel &ge; ...|...including timestamp and...|
234
|a new instance is created/ordered                             |info                    |instance type name|
235
|an instance appears on the provider's list of instances       |info                    |instance ID|
236
|an instance's boot probe succeeds                             |info                    |instance ID|
237
|an instance is shut down after boot timeout                   |warn                    |instance ID, &dagger;stdout/stderr/error from last boot probe attempt|
238
|an instance shutdown is requested                             |info                    |instance ID|
239
|an instance disappears from the provider's list of instances  |info                    |instance ID and previous state (booting/idle/shutdown)|
240
|a cloud provider API or driver error occurs                   |error                   |provider/driver's error message|
241 64 Tom Clegg
|a new container appears in the Arvados queue                  |info                    |container UUID, desired instance type name|
242 45 Tom Clegg
|a container is locked by the dispatcher                       |debug                   |container UUID|
243 44 Tom Clegg
|a crunch-run process is started on an instance                |info                    |container UUID, instance ID, crunch-run PID|
244
|a crunch-run process fails to start on an instance            |info                    |container UUID, instance ID, stdout/stderr/exitcode|
245
|a crunch-run process ends                                     |info                    |container UUID, instance ID|
246
|an active container's state changes to Complete or Cancelled  |info                    |container UUID, new state|
247
|an active container is requeued after being locked            |info                    |container UUID|  
248
|an Arvados API error occurs                                   |warn                    |error message|
249 16 Tom Clegg
250 44 Tom Clegg
&dagger; not yet implemented
251 1 Tom Clegg
252 51 Tom Clegg
Example log entries from test suite (note test suite uses text formatting, production logging uses JSON formatting):
253
<pre>
254
INFO[0000] creating new instance                         ContainerUUID=zzzzz-dz642-000000000000160 InstanceType=type8
255
INFO[0000] instance appeared in cloud                    IdleBehavior=run Instance=stub-providertype8-6ec34c367674cb74 InstanceType=type8 State=booting
256
INFO[0000] boot probe succeeded                          Command=true Instance=stub-providertype8-6ec34c367674cb74 InstanceType=type8 stderr= stdout=
257
INFO[0000] instance booted; will try probeRunning        Instance=stub-providertype8-6ec34c367674cb74 InstanceType=type8 ProbeStart="2019-02-05 15:49:49.183431341 -0500 EST m=+0.126074285"
258
INFO[0000] probes succeeded, instance is in service      Instance=stub-providertype8-6ec34c367674cb74 InstanceType=type8 ProbeStart="2019-02-05 15:49:49.183431341 -0500 EST m=+0.126074285" RunningContainers=0 State=idle
259
INFO[0000] crunch-run process started                    ContainerUUID=zzzzz-dz642-000000000000160 Instance=stub-providertype8-6ec34c367674cb74 InstanceType=type8 Priority=20
260
INFO[0000] container finished                            ContainerUUID=zzzzz-dz642-000000000000160 State=Complete
261
...
262
INFO[0002] shutdown idle worker                          Age=151.615512ms IdleBehavior=run Instance=stub-providertype8-6ec34c367674cb74 InstanceType=type8 State=idle
263
INFO[0002] instance disappeared in cloud                 Instance=stub-providertype8-6ec34c367674cb74 WorkerState=shutdown
264
</pre>
265 14 Tom Clegg
266 10 Tom Clegg
If the dispatcher starts with a non-empty ARVADOS_DEBUG environment variable, it also prints more detailed logs about other internal state changes, using level=debug.
267
268
h2. Internal details
269
270 38 Tom Clegg
h3. Worker lifecycle
271
272
<pre>
273 41 Tom Clegg
274
  ┌────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
275
  │                                                                                                                                                    │
276
  │                  create() returns ID                                                                                                               │         want=drain
277
  │    ┌───────────────────────────────────────────────────────────────────────────┐                                      ┌────────────────────────────┼─────────────────────────────────────────┐
278
  │    │                                                                           ∨                                      │                            │                                         ∨
279
  │  ┌─────────────┐  appears in cloud list   ┌─────────┐  create() returns ID   ┌─────────┐  boot+run probes succeed   ┌──────┐  container starts   ┌─────────┐  container ends, want=drain   ┌──────────┐  instance disappears from cloud   ┌──────┐
280
  │  │ Nonexistent │ ───────────────────────> │ Unknown │ ─────────────────────> │ Booting │ ─────────────────────────> │      │ ──────────────────> │ Running │ ────────────────────────────> │          │ ────────────────────────────────> │ Gone │
281
  │  └─────────────┘                          └─────────┘                        └─────────┘                            │      │                     └─────────┘                               │          │                                   └──────┘
282
  │                                             │                                                                       │      │                                 idle timeout                  │          │
283
  │                                             │                                                                       │ Idle │ ────────────────────────────────────────────────────────────> │ Shutdown │
284
  │                                             │                                                                       │      │                                                               │          │
285
  │                                             │                                                                       │      │                                 probe timeout                 │          │
286
  │                                             │                                                                       │      │ ────────────────────────────────────────────────────────────> │          │
287
  │                                             │                                                                       └──────┘                                                               └──────────┘
288
  │                                             │                                                                         ∧      boot timeout                                                    ∧
289
  │                                             └─────────────────────────────────────────────────────────────────────────┼──────────────────────────────────────────────────────────────────────┘
290
  │                                                                                                                       │
291
  │   container ends                                                                                                      │
292
  └───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘</pre>
293 38 Tom Clegg
294 10 Tom Clegg
h3. Scheduling policy
295 6 Tom Clegg
296
The container priority field determines the order in which resources are allocated.
297
* If container C1 has priority P1,
298
* ...and C2 has higher priority P2,
299
* ...and there is no pending/booting/idle VM suitable for running C2,
300
* ...then C1 will not be started.
301
302 1 Tom Clegg
However, containers that run on different VM types don't necessarily start in priority order.
303
* If container C1 has priority P1,
304 5 Peter Amstutz
* ...and C2 has higher priority P2,
305 6 Tom Clegg
* ...and there is no idle VM suitable for running C2,
306
* ...and there is a pending/booting VM that will be suitable for running C2 when it comes up,
307 1 Tom Clegg
* ...and there is an idle VM suitable for running C1,
308 6 Tom Clegg
* ...then C1 will start before C2.
309 10 Tom Clegg
310 1 Tom Clegg
h3. Special cases / synchronizing state
311 6 Tom Clegg
312
When first starting up, dispatcher inspects API server’s container queue and the cloud provider’s list of dispatcher-tagged cloud nodes, and restores internal state accordingly.
313 10 Tom Clegg
314 36 Tom Clegg
At startup, some containers might have state=Locked. The dispatcher can't be sure these have no corresponding crunch-run process anywhere until it establishes communication with all running instances. To avoid breaking priority order by guessing wrong, the dispatcher avoids scheduling any new containers until all such "stale-locked" containers are matched up with crunch-run processes on existing VMs (typically preparing a docker image) or all of the existing VMs have been probed successfully (meaning the locked containers aren't running anywhere and need to be rescheduled).
315
316 37 Tom Clegg
At startup, some instances might still be running containers that were started by a prior invocation, even though the (new) boot probe command fails. Such instances are left alive at least until the containers finish. After that, the usual rules apply: if boot probe succeeds before boot timeout, start scheduling containers; otherwise, shut down. This allows the operator to configure a new image along with a new boot probe command that only works on the new image, without disrupting users' work.
317 1 Tom Clegg
318 4 Peter Amstutz
When a user cancels a container request with state=Locked or Running, the container priority changes to 0. On its next poll, the dispatcher notices this and kills any corresponding crunch-run processes (or, if there is no such process, just unlocks the container).
319 6 Tom Clegg
320
When a crunch-run process ends without finalizing its container's state, the dispatcher notices this and sets state to Cancelled.
321 4 Peter Amstutz
322 5 Peter Amstutz
h3. Probes
323
324
Sometimes (on the happy path) the dispatcher knows the state of each worker, whether it's idle, and which container it's running. In general, it's necessary to probe the worker node itself.
325
326
Probe:
327
* Check whether the SSH connection is alive; reopen if needed.
328
* Run the configured "ready?" command (e.g., "grep /encrypted-tmp /etc/mtab"); if this fails, conclude the node is still booting.
329
* Run "crunch-run --list" to get a list of crunch-run supervisors (pid + container UUID)
330 6 Tom Clegg
331 5 Peter Amstutz
h3. Detecting dead/lame nodes
332 10 Tom Clegg
333 65 Tom Clegg
If a node has been up for N seconds without a successful probe, it is shut down, even if it was running a container last time it was contacted successfully.
334 28 Tom Clegg
335
h1. Future plans / features
336
337
Per-instance-type VM images: It can be useful to run differently configured/tuned kernels/systems on different instance types, use different ops/monitoring systems on preemptible instances, etc. In addition to a system-wide default, each instance type could optionally specify an image.
338
339 1 Tom Clegg
Selectable VM images: When upgrading a production system, it can be useful to run a few trial containers on a new VM image before making it the default.