8989bd0e8e
runservice: pass arch to driver
...
k8s driver: use the provided arch and set the related nodeselector label
(`kubernetes.io/arch`) when not empty.
2019-04-25 13:42:34 +02:00
6f88bd3d53
runservice: handle multiple executor archs
...
An executor can handle multiple archs (an executor that talks with a k8s cluster
with multi arch nodes). Don't use a label for archs but a custom executor
field.
2019-04-25 13:30:46 +02:00
e0d37b08f2
runservice: add k8s driver
2019-04-22 17:54:24 +02:00
a0d69f4bc3
runservice executor: update for executor groups
...
* Add the concept of executor groups and siblings executors
* Add the concept of dynamic executor: an executor in an executor group that
doesn't need to be manually deleted from the scheduler since the other sibling
executors will take care of cleaning up its pods.
* Remove external labels visibility from pod.
* Add functions to return the sibling executors and the executor group
* Delete pods of disappeared sibling executors
2019-04-24 12:37:55 +02:00
7e9abbf529
runservice executor: add driver Setup method
...
Remote custom `copytoolbox` hack and use a generic `Setup` function in the
driver interface
2019-04-22 18:17:55 +02:00
7ebc436854
runservice executor: generate pod id outside driver
2019-04-22 17:53:34 +02:00
dfeba334f6
runservice: update docker registry auth
2019-04-22 14:38:25 +02:00
4dd89646af
runservice executor: report ActiveTasksLimit
...
Add a config option to set the active tasks limit and report it.
2019-04-17 15:51:20 +02:00
455623e58a
runservice executor: report running tasks
2019-04-17 15:47:58 +02:00
a511fbf10c
runservice: executor: provide architecture information
2019-04-17 15:22:26 +02:00
06374e14fd
runservice: resolve ~ in working_dir
2019-04-15 11:12:07 +02:00
8bde2f2bc0
runservice: implement caching
...
Add `save_cache` and `restore_cache steps`
2019-04-13 14:58:56 +02:00
991fcc59de
runservice: stop all running executor tasks when run is marked to stop
2019-04-11 23:44:55 +02:00
634a8a543c
runservice: implement docker registry auth
...
By now just support default username/password login
In future also support additional container registries with their own credential
helpers
2019-04-10 17:13:51 +02:00
8f4a5b29b9
*: implement setup step
2019-03-13 15:48:35 +01:00
b05b377d31
runservice: add option to define custom container entrypoint
2019-03-13 12:12:32 +01:00
16ac6ada66
runservice: add privileged containers options
2019-03-13 12:11:46 +01:00
36fc79dfc6
runservice: initial commit
2019-02-21 15:54:50 +01:00
Simone Gotti