External Integration Guide

How to integrate with ZenML

This is an older version of the ZenML documentation. To read and view the latest version please visit this up-to-date URL.

External Integration Guide

ZenML integrates with a bunch of tools from the MLOps landscape

One of the main goals of ZenML is to find some semblance of order in the ever-growing MLOps landscape. ZenML already provides numerous integrations into many popular tools, and allows you to extend ZenML in order to fill in any gaps that are remaining.

However, what if you want to make your extension of ZenML part of the main codebase, to share it with others? If you are such a person, e.g., a tooling provider in the ML/MLOps space, or just want to contribute a tooling integration to ZenML, this guide is intended for you.

Step 1: Categorize your integration

In Extending ZenML, we already looked at the categories and abstractions that core ZenML defines. In order to create a new integration into ZenML, you would need to first find the categories that your integration belongs to. The list of categories can be found on this page.

Note that one integration may belong to different categories: For example, the cloud integrations (AWS/GCP/Azure) contain container registries, artifact stores, secrets managers etc.

Step 2: Create individual stack component flavors

Each category selected above would correspond to a stack component flavor. You can now start developing these individual stack component flavors by following the detailed instructions on each stack component page.

Before you package your new components into an integration, you may want to first register them with the zenml <STACK_COMPONENT> flavor register command and use/test them as a regular custom flavor. E.g., when developing an orchestrator you can use:

zenml orchestrator flavor register <path.to.MyOrchestratorFlavor>

For example, if your flavor class MyOrchestratorFlavor is defined in flavors/my_flavor.py, you'd register it by doing:

zenml orchestrator flavor register flavors.my_flavor.MyOrchestratorFlavor

ZenML resolves the flavor class by taking the path where you initialized zenml (via zenml init) as the starting point of resolution. Therefore, please ensure you follow the best practice of initializing zenml at the root of your repository.

If ZenML does not find an initialized ZenML repository in any parent directory, it will default to the current working directory, but usually its better to not have to rely on this mechanism, and initialize zenml at the root.

Afterwards, you should see the new flavor in the list of available flavors:

zenml orchestrator flavor list

See the docs on extensibility of the different components here or get inspired by the many integrations that are already implemented, for example the mlflow experiment tracker.

Step 3: Integrate into the ZenML repo

You can now start the process of including your integration into the base ZenML package. Follow this checklist to prepare everything:

Clone Repo

Once your stack components work as a custom flavor, you can now clone the main zenml repository and follow the contributing guide to set up your local environment for develop.

Create the integration directory

All integrations live within src/zenml/integrations/ in their own sub-folder. You should create a new folder in this directory with the name of your integration.

Example integration directory structure

/src/zenml/integrations/                        <- ZenML integration directory
    <example-integration>                       <- Root integration directory
        |
        ├── artifact-stores                     <- Separated directory for  
        |      ├── __init_.py                      every type
        |      └── <example-artifact-store>     <- Implementation class for the  
        ├── secrets-managers                       artifact store flavor
        |      ├── __init_.py
        |      └── <example-secrets-manager>    <- Implementation class for the  
        |                                          flavor secrets manager
        ├── flavors 
        |      ├── __init_.py 
        |      ├── <example-artifact-store-flavor>  <- Config class and flavor
        |      └── <example-secrets-manager-flavor> <- Config class and flavor
        |
        └── __init_.py                          <- Integration class 

Define the name of your integration in constants

In zenml/integrations/constants.py, add:

EXAMPLE_INTEGRATION = "<name-of-integration>"

This will be the name of the integration when you run:

 zenml integration install <name-of-integration>

Create the integration class __init__.py

In src/zenml/integrations/<YOUR_INTEGRATION>/init__.py you must now create an new class, which is a subclass of the Integration class, set some important attributes (NAME and REQUIREMENTS), and overwrite the flavors class method.

from zenml.integrations.constants import <EXAMPLE_INTEGRATION>
from zenml.integrations.integration import Integration
from zenml.stack import Flavor

# This is the flavor that will be used when registering this stack component
#  `zenml <type-of-stack-component> register ... -f example-orchestrator-flavor`
EXAMPLE_ORCHESTRATOR_FLAVOR = <"example-orchestrator-flavor">

# Create a Subclass of the Integration Class
class ExampleIntegration(Integration):
    """Definition of Example Integration for ZenML."""

    NAME = <EXAMPLE_INTEGRATION>
    REQUIREMENTS = ["<INSERT PYTHON REQUIREMENTS HERE>"]

    @classmethod
    def flavors(cls) -> List[Type[Flavor]]:
        """Declare the stack component flavors for the <EXAMPLE> integration."""
        from zenml.integrations.<example_flavor> import <ExampleFlavor>
        
        return [<ExampleFlavor>]
        
ExampleIntegration.check_installation() # this checks if the requirements are installed

Have a look at the MLflow Integration as an example for how it is done.

Import in all the right places

The Integration itself must be imported within src/zenml/integrations/__init__.py.

Step 4: Create a PR and celebrate 🎉

You can now create a PR to ZenML and wait for the core maintainers to take a look. Thank you so much for your contribution to the code-base, rock on!