-
Notifications
You must be signed in to change notification settings - Fork 23
Open
Labels
actinia as a serviceactinia roadmapLarge Feature, coming soonLarge Feature, coming soonenhancementNew feature or requestNew feature or requestplugindoes not concern actinia-core but one of the pluginsdoes not concern actinia-core but one of the plugins
Description
When actinia is configured with job type other than local, the job will be processed by an actinia worker. Currently there is no mechanism inside actinia to start the worker automatically, as there are many different options, where the worker can run (e.g. VM, kubernetes, HPC, ...)
(For VM start see #401)
Input / Output data need to be stored on mounted storage.
Some ideas to keep it standardised, so that python API stays the same for actinia-job-receiver (here details for VM approach):
prepare_actinia: VM starts, VM is installed (via ansible?) -> Start actinia worker automatically on VM - VM start #401execute_actinia: job is passed to worker / worker is startedgoodbye_actinia: confirm that worker shut down correctly and that VM is shutdown as well and no data loss can occur
-> Start actinia worker automatically on VM - VM shutdown #402
Also mind monitoring #403
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
actinia as a serviceactinia roadmapLarge Feature, coming soonLarge Feature, coming soonenhancementNew feature or requestNew feature or requestplugindoes not concern actinia-core but one of the pluginsdoes not concern actinia-core but one of the plugins