Make job-local work with docker labels #71
Conversation
|
Thank you! |
|
@maietta Sorry to highjack this thread but there is no issue tracker :) I noticed that there is no image on the Docker Hub with the latest version (v1.0.8). Is this project (chadburn) still maintained? I am trying to set up ofelia and saw a comment regarding this project. |
|
I recently lost my business partner to a heart attack, and I have been in the middle of forming a new business. This project is now under PremoWeb LLC, and a new version will be made available sometime soon, but there is no timeline I can pin down just yet. There were some issues with deploying fresh images, and I haven't been able to look into it yet. Because this project is not funded, it was placed on a back burner. I'm working on setting myself up to getting donations and sponsors so I can focus on open source, but I'm not there yet. It's been rather hectic. Also, Docker placed limitations on downloads, which caused issues for people. It was preferred to use Github Container Registry instead. |
|
Thanks for the swift response! I am very sorry for your loss. I hope it did not come across as putting pressure, it was not meant that way. I mainly wanted to see if it makes sense for us to adopt chadburn. I do appreciate the work you put into this project to keep it going forward. I will give it a try tomorrow (interested in the Teams feature). All the best for your new business. |
|
It's okay, I understand and thanks for reaching out.
Someone declared this project dead on a very public website with lots of traffic, which to be frank, pissed me off. They did not bother to talk with me first. Chadburn is STABLE and incorporates the fixes people had with project it was forked from, Ofelia. (Those issues have been fixed, I think). I forked it to provide a stable version people can depend on but was not yet in a position to go full time on development with it.
After this project was declared dead, I briefly took it offline, but reinstated it and disabled discussions and issues while I attempted to reorganize everything to better move forward.
There's some key changes that are coming in 2.x release including removing dependencies, offering an API and even an optional UI. One of the issues with the project is the inherent design flaw of using labels. People don't understand how to manage container labels and this has lead to the bulk of the issues people have, so this is something I feel needs to be addressed.
…On Tuesday, June 11, 2024 20:57 UTC, Matthias Schoettle ***@***.***> wrote:
Thanks for the swift response!
I am very sorry for your loss.
I hope it did not come across as putting pressure, it was not meant that way. I mainly wanted to see if it makes sense for us to adopt chadburn. I do appreciate the work you put into this project to keep it going forward.
I will give it a try tomorrow (interested in the Teams feature).
All the best for your new business.
--
Reply to this email directly or view it on GitHub:
#71 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
|
I've re-enabled issues and discussions. I've not personally tested the teams feature, but after reviewing the API and code, I felt confident the PR for it was good. I believe I now have Teams on my new Office 365 plan, so I can probably tested or adjust as needed. |
|
@mschoettle in case it is handy, I've been working on Alfred, a scheduler very similar to Chadburn and Ofelia, which is a rewrite from scratch. The repo is at https://gitlab.com/invisionai-public/alfred For the moment we suppport only |
job-localjobs did not work before this pull request, because onlyjob-execones are honored from the docker labels.I'm not very happy with the copy-paste of code I did in this PR, but since the repo uses an old version of go it's not easy to use generics, and updating to 1.18 seems to cause many dependency issues.