UCS Tools Registry#

This section explains 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 UCS Tools (CLI/Studio).

Microservice Contents#

A UCS Microservice contains these artifacts:

  • UCS Microservice Specification

  • Helm chart

  • Container Image/s

  • Any other artifacts like DeepLearning Models and Configurations

Local Repository#

The local repository is a file-based repository created on the host file system.

When you build a microservice, it gets 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 (see Generate Scaffolding), Helm Chart and Container Images may be built and stored locally or used from a remote location.

The microservice developer decides how/where to store and retrieve other artifacts like Models and Configurations 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 an 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 its various repositories where it stores containers, Helm charts, and the UCS Microservice Specification for various microservices.

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

Multiple 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.

Optional:

  • Container Images may be uploaded to the same private NGC repository.

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

The microservice developer decides how/where to store and retrieve Container Images and other artifacts like Models and Configurations during deployment.

Note

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