Book Image

Engineering MLOps

By : Emmanuel Raj
Book Image

Engineering MLOps

By: Emmanuel Raj

Overview of this book

Engineering MLps presents comprehensive insights into MLOps coupled with real-world examples in Azure to help you to write programs, train robust and scalable ML models, and build ML pipelines to train and deploy models securely in production. The book begins by familiarizing you with the MLOps workflow so you can start writing programs to train ML models. Then you’ll then move on to explore options for serializing and packaging ML models post-training to deploy them to facilitate machine learning inference, model interoperability, and end-to-end model traceability. You’ll learn how to build ML pipelines, continuous integration and continuous delivery (CI/CD) pipelines, and monitor pipelines to systematically build, deploy, monitor, and govern ML solutions for businesses and industries. Finally, you’ll apply the knowledge you’ve gained to build real-world projects. By the end of this ML book, you'll have a 360-degree view of MLOps and be ready to implement MLOps in your organization.
Table of Contents (18 chapters)
1
Section 1: Framework for Building Machine Learning Models
7
Section 2: Deploying Machine Learning Models at Scale
13
Section 3: Monitoring Machine Learning Models in Production

Configuring pipeline triggers for automation

In this section, we will configure three triggers based on artifacts that we have already connected to the pipeline. The triggers we will set up are as follows:

  • Git trigger: For making code changes to the master branch.
  • Artifactory trigger: For when a new model or artifact is created or trained.
  • Schedule trigger: A weekly periodic trigger.

Let's look at each of these pipeline triggers in detail.

Setting up a Git trigger

In teams, it is common to set a trigger for deployment when code changes are made to a certain branch in the repository. For example, when code changes are made to the master branch or the develop branch, CI/CD pipelines are triggered to deploy the application to the PROD or DEV TEST environments, respectively. When a pull request is made to merge code in the master or develop branch, the QA expert or product manager accepts the pull request in order to merge with the respective branch...