sounds great, is it part of the release? or latest repo?
Actually we just added venv support as well, the reasoning is/was inside a docker it is easier to separate the running processes, with venv we had to support multiple venv running at the same time and reusing of those venv (just a bit more logic) anyhow this is now supported :)
is there a fundamental reason why is this only enabled in --docker mode?
is there a way to assign a job to a specific worker? or is it only working on queue level
Only on a queue level, but you can have as many as you like and spin the agent on it (notice you can have multiple queues on the same agent, pulling based on priority/order).
one more question, is there a way to assign a job to a specific worker? or is it only working on queue level
directly from the UI from the services queue?
Spin the agent with --service-mode it will keep pulling jobs from the queue and spinning them (BTW, it will only start the next job after the first one finished the env setup, and you must be running with --docker mode 🙂
some arbitrary job.. can be executed in parallel to a running job on the same agent.
directly from the UI from the services queue?
doing some extra "services"
what do you mean by "services" ? (from the system perspective any Task that is executed by an agent that is running in "services-mode" is a service, there are no actual limitation on what it can do 🙂 )
just making sure, the services queue is available from the clearml-server UI
great! so the agent can be executing some "regular" job while doing some extra "services"
Hi RipeGoose2
Yes, the "services-mode" of an agent will take multiple Tasks, that said, these are "service" i.e. light CPU tasks, think pipeline controllers etc.