Utilities for job scheduling of ewoks workflows.
Ewoksjob provides an ewoks interface for asynchronous and distributed scheduling of ewoks from python.
Note that ewoksjob distributes the execution of workflows while ewoksdask distributes the execution of tasks in a workflow. So in the context of workflows, job scheduling exists on two levels.
The primary clients that need to schedule workflows are
Install on the client side
pip install ewoksjob
Install on the worker side
pip install ewoksjob[worker]
Start a worker pool that can execute ewoks graphs
ewoksjob worker
Start a workflow on the client side
from ewoksjob.client import submit
workflow = {"graph": {"id": "mygraph"}}
future = submit(args=(workflow,))
result = future.get()
Note that both environments need to be able to import celeryconfig which
contains celery configuration (mainly the message broker and result backend URL's).
Clone the git repository and start a worker pool
scripts/worker.sh --sql
Submit workflows
scripts/runjobs.sh --sql
pytest --pyargs ewoksjob
To run the redis tests you need redis-server (e.g. conda install redis-server).
FAQs
Asynchronous and distributed scheduling of Ewoks workflows from python
We found that ewoksjob demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.