I think that the remaining bit here is to get this working on windows images. At the moment, I think "windows images" means OCC and generic-worker repo, but not monopacker. I'll ignore OCC since that's going out of style anyway /cc grenade. Then we can start getting this deployed. Once it's deployed more-or-less everywhere, we can remove the now-redundant support for clouds from generic-worker (but of course keep the ability to run independently). Then, we can start adding more detailed support, first to catch up to docker-worker: - support for monitoring for instance termination and then on to more exciting across-the-board stuff - error reporting for startup errors - automatic self-termination in cases where worker startup fails - registration updates ("hey w-m, I'm still here and running") - etc.
Bug 1558532 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I think that the remaining bit here is to get this working on windows images. At the moment, I think "windows images" means OCC and generic-worker repo, but not monopacker. I'll ignore OCC since that's going out of style anyway /cc grenade. Then we can start getting this deployed. Once it's deployed more-or-less everywhere, we can remove the now-redundant support for clouds from generic-worker (but of course keep the ability to run independently). Then, we can start adding more detailed support, first to catch up to docker-worker: - support for monitoring for instance termination and then on to more exciting across-the-board stuff - error reporting for startup errors - automatic self-termination in cases where worker startup fails - registration updates ("hey w-m, I'm still here and running") - etc.