Navigating multiple development environments.
Note: This page is a work in progress (WIP) and is currently under development. If you have any questions or need assistance, please join our Slack community.
ZenML deployments often involve multiple environments. This guide helps you manage dependencies and configurations across these environments.
Here is a visual overview of the different environments:
Left box is the client environment, middle is the zenml server environment, and the right most contains the build environments
The client environment is where the ZenML pipelines are started, i.e., where you call the pipeline function (typically in a
run.pyscript). There are different types of client environments:
- A local development environment
runnerimage orchestrated by the ZenML server to start pipelines.
In all the environments, you should use your preferred package manager (e.g.,
poetry) to manage dependencies. Ensure you install the ZenML package and any required integrations.
The client environment typically follows these key steps when starting a pipeline:
- 1.Generating an intermediate pipeline representation.
The ZenML server environment is a FastAPI application managing pipelines and metadata. It includes the ZenML Dashboard and is accessed when you deploy ZenML. To manage dependencies, install them during ZenML deployment, but only if you have custom integrations, as most are built-in.
When running locally, there is no real concept of a
executionenvironment as the client, server, and execution environment are all the same. However, when running a pipeline remotely, ZenML needs to transfer your code and environment over to the remote orchestrator. In order to achieve this, ZenML builds docker images known as
ZenML handles the Docker image configuration, creation, and pushing, starting with a base image containing ZenML and Python, then adding pipeline dependencies. To manage the Docker image configuration, follow the steps in the containerize your pipeline guide, including specifying additional pip dependencies, using a custom parent image, and customizing the build process.
The execution environments do not need to be built each time a pipeline is run - you can reuse builds from previous runs to save time.
By default, execution environments are created locally in the client environment using the local Docker client. However, this requires Docker installation and permissions. ZenML offers image builders, a special stack component, allowing users to build and push docker images in a different specialized image builder environment.
Note that even if you don't configure an image builder in your stack, ZenML still uses the local image builder to retain consistency across all builds. In this case, the image builder environment is the same as the client environment.