General informations
| Package manager | Software repository | Latest release | Total downloads |
|---|---|---|---|
pip |
PyPI |  |
|
conda |
conda-forge |  |
 |
Code health
| Branch | Tests | Coverage | Links | Documentation | Deployment | Activity |
|---|---|---|---|---|---|---|
master |
 |
 |
 |
 |
 |
kedro-mlflow is a kedro-plugin for lightweight and portable integration of mlflow capabilities inside kedro projects. It enforces Kedro principles to make mlflow usage as production ready as possible. Its core functionalities are :
- versioning:
kedro-mlflowintends to enhance reproducibility for machine learning experimentation. Withkedro-mlflowinstalled, you can effortlessly register your parameters or your datasets with minimal configuration in a kedro run. Later, you will be able to browse your runs in the mlflow UI, and retrieve the runs you want. This is directly linked to Mlflow Tracking. - model packaging:
kedro-mlflowintends to be be an agnostic machine learning framework for people who want to write portable, production ready machine learning pipelines. It offers a convenient API to convert a Kedro pipeline to amodelin the mlflow sense. Consequently, you can API-fy or serve your Kedro pipeline with one line of code, or share a model with without worrying of the preprocessing to be made for further use. This is directly linked to Mlflow Models.
Important: kedro-mlflow is only compatible with kedro>=0.16.0 and mlflow>=1.0.0. If you have a project created with an older version of Kedro, see this migration guide.
kedro-mlflow is available on PyPI, so you can install it with pip:
pip install kedro-mlflowIf you want to use the most up to date version of the package which is under development and not released yet, you can install the package from github:
pip install --upgrade git+https://github.com/Galileo-Galilei/kedro-mlflow.gitI strongly recommend to use conda (a package manager) to create an environment and to read kedro installation guide.
The documentation contains:
- A "hello world" example which demonstrates how you to setup your project, version parameters and datasets, and browse your runs in the UI.
- A section for advanced machine learning versioning to show more advanced features (mlflow configuration through the plugin, package and serve a kedro
Pipeline...) - A section to demonstrate how to use
kedro-mlflowas a machine learning framework to deliver production ready pipelines and serve them. This section comes with an example repo you can clone and try out.
Some frequently asked questions on more advanced features:
- You want to log additional metrics to the run? -> Try
MlflowMetricsDataSet! - You want to log nice dataviz of your pipeline that you register with
MatplotlibWriter? -> TryMlflowArtifactDataSetto log any local files (.png, .pkl, .csv...) automagically! - You want to create easily an API to share your awesome model to anyone? -> See if
pipeline_ml_factorycan fit your needs - You want to do something that is not straigthforward with current implementation? Open an issue, and let's see what happens!
The release history centralizes packages improvements across time. The main features coming in next releases are listed on github milestones. Feel free to upvote/downvote and discuss prioritization in associated issues.
This package is still in active development. We use SemVer principles to version our releases. Until we reach 1.0.0 milestone, breaking changes will lead to <minor> version number increment, while releases which do not introduce breaking changes in the API will lead to <patch> version number increment.
The user must be aware that we will not reach 1.0.0 milestone before Kedro does (mlflow has already reached 1.0.0). That said, the API is considered as stable from 0.8.0 version and user can reliably consider that no consequent breaking change will happen unless necessary for Kedro compatibility (e.g. for minor or major Kedro version).
If you want to migrate from an older version of kedro-mlflow to most recent ones, see the migration guide.
We'd be happy to receive help to maintain and improve the package. Any PR will be considered (from typo in the docs to core features add-on) Please check the contributing guidelines.
The following people actively maintain, enhance and discuss design to make this package as good as possible:
Many thanks to Adrian Piotr Kruszewski for his past work on the repo.