Home

Awesome

Batch Scoring Deep Learning Models With Kubernetes

Overview

In this repository, we use the scenario of applying style transfer onto a video (collection of images). This architecture can be generalized for any batch scoring with deep learning scenario. For an alternative solution using Azure Machine Learning service, we suggest seeing the solution available here which is also described on the Azure Reference Architecture center.

Design

Reference Architecture Diagram

The above architecture works as follows:

  1. Upload a video file to storage.
  2. The video file will trigger Logic App to send a request to the flask endpoint hosted on one of the nodes of the AKS cluster.
  3. That node will first preprocess the video file by splitting the video into individual images and extracting the audio file.
  4. That node will then add all images to the Service Bus queue.
  5. The other nodes in the AKS cluster are continuously polling the Service Bus queue - as soon as any images are in the queue, it will pull it off the queue and apply style transfer to the image.
  6. When all frames have been processed, the images will be stitched back together into a video with the audio file.

What is Neural Style Transfer

Style image:Input/content video:Output video:
<img src="https://happypathspublic.blob.core.windows.net/assets/batch_scoring_for_dl/style_image.jpg" width="300"><img src="https://happypathspublic.blob.core.windows.net/assets/batch_scoring_for_dl/input_video_image_0.jpg" width="300" height="300"> click to view video<img src="https://happypathspublic.blob.core.windows.net/assets/batch_scoring_for_dl/output_video_image_0.jpg" width="300" height="300"> click to view

Prerequsites

Local/Working Machine:

Accounts:

While it is not required, it is also useful to use the Azure Storage Explorer to inspect your storage account.e az cli installed and logged into

Setup

  1. Clone the repo git clone https://github.com/Azure/Batch-Scoring-Deep-Learning-Models-With-AKS
  2. cd into the repo
  3. Setup your conda env using the environment.yml file conda env create -f environment.yml - this will create a conda environment called batchscoringdl
  4. Activate your environment source activate batchscoringdl
  5. Log in to Azure using the az cli az login
  6. Log in to Docker using the docker cli docker login

Steps

Run throught the following notebooks:

  1. Test the Style Transfer Script
  2. Setup Azure - Resource group, Storage, Service Bus.
  3. Test the model locally
  4. Create the AKS cluster
  5. Run style transfer on the cluster
  6. Deploy Logic Apps
  7. Clean up

Clean up

To clean up your working directory, you can run the clean_up.sh script that comes with this repo. This will remove all temporary directories that were generated as well as any configuration (such as Dockerfiles) that were created during the tutorials. This script will not remove the .env file.

To clean up your Azure resources, you can simply delete the resource group that all your resources were deployed into. This can be done in the az cli using the command az group delete --name <name-of-your-resource-group>, or in the portal. If you want to keep certain resources, you can also use the az cli or the Azure portal to cherry pick the ones you want to deprovision. Finally, you should also delete the service principle using the az ad sp delete command.

All the step above are covered in the final notebook.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.