UCS Tools Registry#

In this section, we explain how UCS Tools Registry (aka UCS Registry) and repositories in the registry are organized. Repositories can be local or remote on NGC. Developers can interact with the repositories using the UCS Tools (CLI/Studio).

Microservice Contents#

A UCS Microservice contains the following artifacts:

  • UCS Microservice Specification

  • Helm chart

  • Container Image/s

  • Any other artifacts like DeepLearning Models and Configurations

Local Repository#

Local repository is basically a file based repository created on the host file system.

When a microservice is built it is added to the local repository. The generated UCS Microservice Specification gets stored in this local repository. Based on the mode of microservice creation and build (Refer to Generate scaffolding), Helm Chart and Container Images maybe built and stored locally or maybe used from a remote location.

It is up to the microservice developer on how/where the other artifacts like Models and Configurations are stored and retrieved during deployment.

Note

Users can use the local (default) repository to store microservices.

NGC Repository#

Currently, UCS Tools supports NGC as the remote repository. NGC is a NVIDIA provided catalog service for containers, pre-trained models, Helm charts for Kubernetes deployments and industry specific AI toolkits with software development kits (SDKs).

UCS Tools uses NGC as a platform for it’s various repositories where it stores the containers, helm charts and the UCS Microservice Specification for the various microservices.

A UCS Tools NGC repository is basically a Private NGC Registry with a specified org and team.

Multiple such use case/product-specific repositories have been created. Each UCS Tools NGC repository contains artifacts specific to the use case/product. It contains:

  • UCS Microservice Specification for the various microservices used in the use case/product.

  • Helm Chart for the microservices.

  • Container Images may be uploaded to the same private NGC repository. However this is OPTIONAL.

  • Other artifacts like Models and Configurations may be uploaded to the same private NGC repository. However this is OPTIONAL.

It is up to the microservice developer on how/where the Container Images and other artifacts like Models and Configurations are stored and retrieved during deployment.

Note

Users cannot create new NGC based repositories and hence they can use the local (default) repository to store microservices.

On this page