Skip to content

Template repository for setting up MLOps components using AVH_FVP models and cmsis-toolbox in a Docker Container

License

Notifications You must be signed in to change notification settings

ARM-software/AVH-MLOps

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

222 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

License base_image_build licensed_image_build licensed_image_build_community

Foundation Components for MLOps Systems

Arm provides a set of foundation tools and software components to enable MLOps systems and the overall development flow for machine learning applications.

  • This repository contains workflows to create Docker containers with foundation tools for MLOps systems.

Container customization

Tools for the container can be selected by altering the vcpkg-configuration.json file. See vcpkg-tool-installation.

Directory Structure

Directory
Description
.github/workflows GitHub Action workflow definitions.
docker_base Docker base image with all tools (see Arm Tools Artifactory).
docker_licensed Import license file into the Docker base image.

Continuous Integration (CI)

Four workflows examplify how to create docker images and equip with licenses suitable for build and test typical MLOps applications.

CI Workflow files
Description
base_image_build.yml Build a docker image that has all ARM tools mentioned before installed and configured. It will be stored on the Github docker registry for fast access to the image.
licensed_image_build.yml By using the Base docker image, this workflow adds your own license supplied by Arm for the commercial tools. It is rebuilt every night and serves as the base image from which the actual container runtime environments are generated. It will also be stored on the Github docker registry.
licensed_image_test.yml Test the licensed docker image with the necessary tools and dependencies for an ML project.
licensed_image_build_community.yml By using the Base docker image, this workflow adds your own community license supplied by Arm for the commercial tools. It is rebuilt every night and serves as the base image from which the actual container runtime environments are generated. It will also be stored on the Github docker registry.

Customize this repository

First create a fork into a user account or organization of your own (or commit to a new private repository). On your fork you need to make a couple of modifications:

  1. Add own Activation Code (Arm UBL license) The activation code is passed to the docker build process in a Github Actions secret called ARM_UBL_LICENSE_IDENTIFIER. To set a secret called ARM_UBL_LICENSE_IDENTIFIER to a repository in Github, go to the repository's main page, click on "Settings", then "Secrets", and "New repository secret". Enter "ARM_UBL_LICENSE_IDENTIFIER" as the name and the activation code for the Arm UBL license as the value. Click on "Add secret".

  2. Customize Base Docker Image Additional installations for custom tools you can add those to docker_base/Dockerfile. If you are new to Docker find a good starting point in the Docker manual.

Check the Actions view to verify the execution of all 4 workflows.

Raise a bug report

Please report any issue you are facing while using these repository Issues tab on GitHub.

About

Template repository for setting up MLOps components using AVH_FVP models and cmsis-toolbox in a Docker Container

Resources

License

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors 6