Roadmap
The conda-store roadmap for the remaining part of 2024 into 2025 will revolve around several key areas of iterative improvement:
- Performance
- Backup and restore
- User experience improvements
| Mark | Description |
|---|---|
| 📪 | work not started |
| ✅ | work completed |
| ⬆️ | upstream |
| 🏃 | in progress |
| 💪 | stretch goal |
Performance
- ✅ Identify the parts of conda-store responsible for slowing down new environment builds.
- 🏃 ~40% of environment build time comes from a slow call to conda-lock, which solves each environment twice (once for conda packages and again to support pip packages with a vendored version of poetry). The dependency on conda-lock will be eliminated by implementing official conda support for lockfile generation:
- ⬆️🏃 Teach conda create how to handle environment.yml files (#14113)
- ⬆️🏃 Add support for conda [env] hooks (#13833).
- ⬆️📪 Implement the hooks mentioned above in conda-pypi.
- ⬆️📪 Define and standardize a conda lockfile schema.
- ⬆️📪 Replace conda-lock with an officially supported conda plugin for lockfile generation.
- 🏃 ~40% of environment build time is due to package download and extraction, which is carried out serially to avoid collisions when multiple concurrent requests for the same package are made. Implement a locking mechanism to allow concurrent downloads, reducing this to just the bare network time required to download the required assets.
- 🏃 Currently, simultaneous calls to conda create result in corrupted packages and cached repo data (#13037). Support for locking the repodata cache was added by the community recently (#12996), but full locking support must be added to prevent conflicts/data corruption from other concurrent conda operations.
- ⬆️📪 Add native conda support for locking to allow parallel conda commands on a single machine (#13055).
- 🏃 Currently, simultaneous calls to conda create result in corrupted packages and cached repo data (#13037). Support for locking the repodata cache was added by the community recently (#12996), but full locking support must be added to prevent conflicts/data corruption from other concurrent conda operations.
- 🏃 ~40% of environment build time comes from a slow call to conda-lock, which solves each environment twice (once for conda packages and again to support pip packages with a vendored version of poetry). The dependency on conda-lock will be eliminated by implementing official conda support for lockfile generation:
- 🏃 Implement a plugin system for critical conda-store functions including locking, solving, and package managment, paving the way for slow code paths to be replaced with faster alternatives. (#929)
Storage / Backup and Restore
- 📪 A major concern for existing conda-store deployments is that old, unused builds still take up space on shared volumes. Old builds eventually fill up disk space for deployments with many users, requiring manual intervention to delete them. Implementing a backup mechanism will require reaching consensus on an approach to archiving and recreation old builds (#889).
- 📪 Implement archiving of old builds: the yaml spec and the lockfile are kept, but the environments on disk are deleted (#947).
- 📪 Implement recreation of old builds. Combined with planned performance improvements, users can expect to wait only as long as it takes to download and reinstall the packages for the recreated environment (#948).
- 📪 Transferring or copying a full conda-store deployment is currently not possible. Implement full backup and restore, including creating the active environments on disk. (#949)
- 📪 Currently, conda environments created by conda-store do not share packages. In deployments containing many builds, this can lead to many duplicate packages, which uses much more storage than necessary. Refactor the logic around creating new environments so that packages are shared across environments (#950).
- 📪 Design a serialization format upstream for conda environments that captures both the environment specification and the resulting lockfile, paving the path for allowing environments to be transferred reproducibly. (#952)
- 📪 In conda-store, implement the ability to transfer environments along with their histories using the new serialization format (#952).
User experience improvements
- 🏃 Currently there are three ways to interact with the conda-store-server: the CLI, the REST API, and the Python API. However, these interfaces do not provide the same functionality, leading to maintenance issues. Addressing this will require refactoring the existing CLI, in addition to potential modifications to the REST and Python APIs.
- 📪 The current conda-store-ui has proven difficult to extend, improve, and maintain. A refactor to simplify and standardize its codebase, while following industry best-practices is currently being proposed which includes updates to the UI to match the new workflows mentioned above (#439)
- 🏃 Additional documentation for developers is critical for helping potential contributors, but our current developer documentation does not cover all parts of the code.
- 🏃 Existing architectural diagrams give an overview of what microservices comprise a complete conda-store deployment. Additional documentation would be useful, particularly to help newcomers understand what conda-store is doing when the user takes various actions.
- 📪 Additional documentation about authorization and authentication remains a goal for after the implementation of the workflow improvements discussed above; these will likely impact on permissioning and authorization.
- 📪 Refactor
jupyterlab-conda-storeto make it a simple iframe of the existing UI, with cross-iframe messages + URL query parameters for communication and customization (#68). - 📪 Instead of requiring the user to set an environment variable to build GPU-enabled environments, explicitly add this option to conda-store to make this process smoother (#955).
- 📪 Deprecation of conda-store admin app (#956).
- 📪 Implement UX improvements based on recently-completed usability study, and practical issues encountered from dogfooding.
- 📪 Document the ideal way that
conda-storeshould be deployed - volumes, instance sizes for various use cases, etc (#957).