JupyterFlow
Run your workflow on JupyterHub!
What is JupyterFlow?
Run Argo Workflow on JupyterHub with single command.
- No Kubernetes knowledge (YAML) needed to run.
- No container image build & push or deploy.
- Just simply run your workflow with single command
jupyterflow.
jupyterflow is a single command that helps user utilize Argo workflow engine without making any YAML files or building containers on JupyterHub. The following jupyterflow command will make sequence workflow for you. That's it!
jupyterflow run -c "python hello.py >> python world.py"
To make parallel workflow, write your own workflow.yaml file.
Problem to solve
- I wanted to train multiple ML models efficiently.
- Using Kubernetes was a good idea, since
- it is easy to make distributed jobs.
- it is easy to schedule ML jobs on multiple training server.
- it has native resource management mechanism.
- it has good monitoring system.
- But there were some drawbacks.
- I needed to re-build & re-push image everytime I updated my model. This was painful.
- People who were not familiar with k8s had a hard time using this method.
JupyterFlow aims to solve this problem. Run your workflow on JupyterHub with single command without Kubernetes & container troublesome task.
Limitation
JupyterFlow only works on JupyterHub deployed on Kubernetes.
Therefore, although using JupyterFlow does not require Kubernetes knowledge, setting up JupyterFlow requires Kubernetes understandings(YAML, helm, Service). If you're familiar with Kubernetes, it will not be too hard.
Getting Started
To set up jupyterflow and start running your first workflow, follow the Getting Started guide.
How does it work
To learn how it works, go to How it works guide.
Examples
For examples how to use, please see Examples page.
Configuration
To find out more configuration, take a look at Configuration page.
CLI Reference
For more detail usage of jupyterflow command line interface, find out more at CLI Reference page.
Metadata
Release files for jupyterflow 0.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| jupyterflow-0.0.4.tar.gz | 9.3 kB | Without provenance | Details for jupyterflow-0.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jupyterflow-0.0.4-py3-none-any.whl | Python 3 | none | any | Details for jupyterflow-0.0.4-py3-none-any.whl |
Total release size: 32.9 kB
Release files / jupyterflow-0.0.4.tar.gz
| Download URL | jupyterflow-0.0.4.tar.gz |
|---|---|
| Size | 9.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
625393cbf151f8083c5bcf62e6390772e08dd5aaa414d059626011dc659a42e9
|
|
BLAKE2b-256 checksum How to use checksums |
beaa5e15ea1b9da92622624a1df4761a0daa732a438c55d501e8e1c699b8d3b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.23.0 setuptools/46.4.0.post20200518 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.8.3
|
Release files / jupyterflow-0.0.4-py3-none-any.whl
| Download URL | jupyterflow-0.0.4-py3-none-any.whl |
|---|---|
| Size | 23.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eb7fb64b717e95d550ee4d434a24426b8bc330c9462a5631102918d6a8f17f35
|
|
BLAKE2b-256 checksum How to use checksums |
d441e77361118ef172b0747b721340b8e1bea3136b84a6cd7580b4754c922940
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.23.0 setuptools/46.4.0.post20200518 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.8.3
|
Security for jupyterflow 0.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.