google-cloud-automlops 1.0.2

AutoMLOps is a service that generates a production-style MLOps pipeline from Jupyter Notebooks.

AutoMLOps

AutoMLOps is a service that generates a production ready MLOps pipeline from Jupyter Notebooks, bridging the gap between Data Science and DevOps and accelerating the adoption and use of Vertex AI. The service generates an MLOps codebase for users to customize, and provides a way to build and manage a CI/CD integrated MLOps pipeline from the notebook. AutoMLOps automatically builds a source repo for versioning, cloudbuild configs and triggers, an artifact registry for storing custom components, gs buckets, service accounts and updated IAM privs for running pipelines, enables APIs (cloud Run, Cloud Build, Artifact Registry, etc.), creates a runner service API in Cloud Run for submitting PipelineJobs to Vertex AI, and a Cloud Scheduler job for submitting PipelineJobs on a recurring basis. These automatic integrations empower data scientists to take their experiments to production more quickly, allowing them to focus on what they do best: providing actionable insights through data.

Prerequisites

In order to use AutoMLOps, the following are required:

• Jupyter (or Jupyter-compatible) notebook environment
• Notebooks API enabled
• Python 3.0 - 3.10
• Google Cloud SDK 407.0.0
• beta 2022.10.21
• git installed
• git logged-in:

  git config --global user.email "[e-mail]"
  git config --global user.name "Your Name"

• Application Default Credentials (ADC) are setup. This can be done through the following commands:

gcloud auth application-default login
gcloud config set account <[e-mail]>

Install

Clone the repo and install either via setup.py or wheel (wheel requires less processing):

• setup.py: pip install .
• wheel: pip install dist/AutoMLOps-1.0.2-py2.py3-none-any.whl

Dependencies

• autoflake==2.0.0,
• docopt==0.6.2,
• ipython==7.34.0,
• pipreqs==0.4.11,
• pyflakes==3.0.1,
• PyYAML==5.4.1,
• yarg==0.1.9

GCP Services

AutoMLOps makes use of the following products by default:

• Vertex AI Pipelines
• Artifact Registry
• Google Cloud Storage
• Cloud Build
• Cloud Build Triggers
• Cloud Run
• Cloud Scheduler
• Cloud Tasks

APIs & IAM

AutoMLOps will enable the following APIs:

• cloudresourcemanager.googleapis.com
• aiplatform.googleapis.com
• artifactregistry.googleapis.com
• cloudbuild.googleapis.com
• cloudscheduler.googleapis.com
• cloudtasks.googleapis.com
• compute.googleapis.com
• iam.googleapis.com
• iamcredentials.googleapis.com
• ml.googleapis.com
• run.googleapis.com
• storage.googleapis.com
• sourcerepo.googleapis.com

AutoMLOps will update IAM privileges for the following accounts:

1. Pipeline Runner Service Account (one is created if it does exist, defaults to: vertex-pipelines@PROJECT_ID.iam.gserviceaccount.com). Roles added:

• roles/aiplatform.user
• roles/artifactregistry.reader
• roles/bigquery.user
• roles/bigquery.dataEditor
• roles/iam.serviceAccountUser
• roles/storage.admin
• roles/run.admin

2. Cloudbuild Default Service Account ([e-mail]). Roles added:

• roles/run.admin
• roles/iam.serviceAccountUser
• roles/cloudtasks.enqueuer
• roles/cloudscheduler.admin

User Guide

For a user-guide, please view these slides.

Options

AutoMLOps currently supports 4 different configurations based on the following flags:

1. use_kfp_spec: (Optional) Bool that specifies whether to use Kubeflow definitions or Python custom definitions. Defaults to False. See user guide.
   • if True:
     • The pipeline uses Kubeflow objects and syntax, and will generate all the necessary files in the backend to compile and run the pipeline.
   • if False:
     • The pipeline uses a custom defined syntax (through a series of python dictionaries and lists) that effectively removes the need to know Kubeflow syntax to compile and run the pipeline.
2. run_local: (Optional) Bool that specifies whether to use generate files resources locally or use cloud CI/CD workflow (see below). Defaults to True. See CI/CD Workflow

Required parameters:

1. project_id: str
2. pipeline_params: dict

Optional parameters (defaults shown):

1. af_registry_location: str = 'us-central1'
2. af_registry_name: str = 'vertex-mlops-af'
3. cb_trigger_location: str = 'us-central1'
4. cb_trigger_name: str = 'automlops-trigger'
5. cloud_run_location: str = 'us-central1'
6. cloud_run_name: str = 'run-pipeline'
7. cloud_tasks_queue_location: str = 'us-central1'
8. cloud_tasks_queue_name: str = 'queueing-svc'
9. csr_branch_name: str = 'automlops'
10. csr_name: str = 'AutoMLOps-repo'
11. custom_training_job_specs: list[dict] = None
12. gs_bucket_location: str = 'us-central1'
13. gs_bucket_name: str = None
14. pipeline_runner_sa: str = None
15. run_local: bool = True
16. schedule_location: str = 'us-central1'
17. schedule_name: str = 'AutoMLOps-schedule'
18. schedule_pattern: str = 'No Schedule Specified'
19. use_kfp_spec: bool = False
20. vpc_connector: str = None

AutoMLOps will generate the resources specified by these parameters (e.g. Artifact Registry, Cloud Source Repo, etc.). If run_local is set to False, the AutoMLOps will turn the current working directory of the notebook into a Git repo and use it for the CSR. Additionally, if a cron formatted str is given as an arg for schedule_pattern then it will set up a Cloud Schedule to run accordingly.

Customizations

Set scheduled run:

Use the schedule_pattern parameter to specify a cron job schedule to run the pipeline job on a recurring basis.

schedule_pattern = '0 */12 * * *'

Set pipeline compute resources:

Use the custom_training_job_specs parameter to specify resources for any custom component in the pipeline.

custom_training_job_specs = [{
    'component_spec': 'train_model',
    'display_name': 'train-model-accelerated',
    'machine_type': 'a2-highgpu-1g',
    'accelerator_type': 'NVIDIA_TESLA_A100',
    'accelerator_count': '1'
}]

Use a VPC connector:

Use the vpc_connector parameter to specify a vpc connector.

vpc_connector = 'example-vpc'

Layout

Included in the repository is an example notebook that demonstrates the usage of AutoMLOps. Upon running AutoMLOps.go(project_id='automlops-sandbox',pipeline_params=pipeline_params), a series of directories will be generated automatically, and a pipelineJob will be submitted using the setup below:

.
├── cloud_run                                      : Cloud Runner service for submitting PipelineJobs.
    ├──run_pipeline                                : Contains main.py file, Dockerfile and requirements.txt
    ├──queueing_svc                                : Contains files for scheduling and queueing jobs to runner service
├── components                                     : Custom vertex pipeline components.
    ├──component_base                              : Contains all the python files, Dockerfile and requirements.txt
    ├──create_dataset                              : Pull data from a BQ table and writes it as a csv to GS.
    ├──train_model                                 : Trains a basic decision tree classifier.
    ├──deploy_model                                : Deploys model to endpoint.
├── images                                         : Custom container images for training models.
├── pipelines                                      : Vertex ai pipeline definitions.
    ├── pipeline.py                                : Full pipeline definition.
    ├── pipeline_runner.py                         : Sends a PipelineJob to Vertex AI.
    ├── runtime_parameters                         : Variables to be used in a PipelineJob.
        ├── pipeline_parameter_values.json         : Json containing pipeline parameters.    
├── configs                                        : Configurations for defining vertex ai pipeline.
    ├── defaults.yaml                              : PipelineJob configuration variables.
├── scripts                                        : Scripts for manually triggering the cloud run service.
    ├── build_components.sh                        : Submits a Cloud Build job that builds and deploys the components.
    ├── build_pipeline_spec.sh                     : Builds the pipeline specs
    ├── create_resources.sh                        : Creates an artifact registry and gs bucket if they do not already exist.
    ├── run_pipeline.sh                            : Submit the PipelineJob to Vertex AI.
    ├── run_all.sh                                 : Builds components, pipeline specs, and submits the PipelineJob.
└── cloudbuild.yaml                                : Cloudbuild configuration file for building custom components.

Cloud Continuous Integration and Continuous Deployment Workflow

If run_local=False, AutoMLOps will generate and use a fully featured CI/CD environment for the pipeline. Otherwise, it will use the local scripts to build and run the pipeline.

Pipeline Components

The example notebook comes with 3 components as part of the pipeline. Additional sample code for commonly used services can be found below:

• Feature Store
• BigQuery ML
• Model Registry
• Experiments
• ExplainableAI
• Vertex AI Pipelines
• Google Cloud Pipeline Components

Next Steps / Backlog

• PyPI
• Refine unit tests
• Use terraform for the creation of resources.
• Allow multiple AutoMLOps pipelines within the same directory
• Adding model monitoring part
• Alternatives to Pipreqs

Contributors

Sean Rastatter: Technical Lead

Tony DiLoreto: Project Manager

Allegra Noto: Engineer

Disclaimer

This is not an officially supported Google product.

Copyright 2023 Google LLC. All Rights Reserved.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.