A JupterLab Extension and client to interface with conda-store
Project description
Conda Store
End users think in terms of environments not packages. The core philosophy of conda-store is to serve identical conda environments in as many ways as possible. Conda Store controls the environment lifecycle: management, builds, and serving of environments.
It manages conda environments by:
- watching specific files or directories for changes in environment filename specifications
- provides a REST api for managing environments (which a jupyterlab plugin is being actively developed for)
- provides a command line utility for interacting with conda-store
conda-store env [create, list] - provides a web ui to take advantage of many of conda-stores advanced capabilities
It builds conda specifications in a scalable manner using N
workers communicating with a database to keep track of queued up
environment builds.
It serves conda environments via a filesystem, lockfiles,
tarballs, and soon a docker registry. Tarballs and docker images can
carry a lot of bandwidth which is why conda-store integrates
optionally with s3 to actually serve the blobs.
Terminology
-
An environment is a
nameassociated with an environmentspecification. -
A specification is a conda
yamldeclaration with fieldsname,channels, anddependenciesdetailed here -
For each specification conda-build attempts to build the specification. Upon failure conda-store reschedules the build
Ntimes with exponential backoff.
Philosophy
We mentioned above that conda-store was influenced by
nix. While conda is not as pure as nix (when it
comes to reproducible builds) we can achieve close to the same results
with many of the great benefits that nix users achieve. Motivation
from this work came from the following projects in no particular
order: lorri, nix layered docker
images,
https://nixos.org/, nixery. You will see
bits of each in this work.
- specifications are idempotent, created once, and never updated
(this means there is no
conda installorconda env update). In fact there is only one conda commandconda env create -f <specification>. - specifications are named
<sha256-hash-of-spec>-<environment-name>. Ensuring every conda environment is unique. - conda environments e.g.
<environment-name>is symlinked to a specific conda specification<sha256-hash-of-spec>-<environment-name>.
The benefits of this approach is versioning of environments, heavy caching, and rollbacks to previous environment states.
Development
docker-compose up --build
In order for logs and artifacts to be downloaded properly you will
need to set dns host minio -> localhost. The easiest way to do
this is via /etc/hosts
...
minio localhost
...
Extension Local Testing
This extension for jupyterlab providees kernel management from within the Jupyter intereface and ecosystem.
NOTE: In nixOS, use conda-shell and this method will work.
cd conda-store
conda env update -f environment.yaml
conda activate conda-store
pip install .
jupyter labextension develop . --overwrite
jlpm run build
jupyter lab
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
File details
Details for the file conda_store-0.2.4.tar.gz.
File metadata
- Download URL: conda_store-0.2.4.tar.gz
- Upload date:
- Size: 436.7 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.58.0 CPython/3.8.7
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | dbf0f1122ae0c8027bff9c1938f81e91fe29913ca64dd362e0480a26554132be |
|
| MD5 | 6d10911b636b1a4c0feb22f183cef388 |
|
| BLAKE2b-256 | 1f5251210008c0ef67b41283f9c8af921054388e48046917f65e5c98e4476368 |
