Storage Services

Omniverse on DGX Cloud (OVC) Storage Services are a collection of advanced microservices. In the diagram below, the microservices colored in orange are directly accessible via the ingress path of AKS, while the microservices colored in black are accessed via the custom API Gateway. The auth service is responsible for providing authentication to all services, including the Streaming SaaS and Farm services.

When a workload such as a Kit-based application for either streaming (i.e., Kit pod) or batch rendering (i.e., Render pod) is spawned, this application presents a JWT (Javascript Web Token) to access the object storage services. This traffic exclusively travels through the Azure internal load balancer to locate the desired services.

Live Edit storage traffic additionally follows this route. Live Edit is an Omniverse on DGX Cloud service where multiple users engage in live collaboration of a scene with synchronization across all users in real time.

For storage content operations such as reading, writing, and updating (i.e., CRUD operations), scene contents can take multiple routes depending on the request type. For example, they can be directed to the NGINX content cache, which caches the data fetched from the Azure Blob Storage for the respective tenant. Similarly, requests that are directed to the Nucleus Large File Transfer (LFT) service can be routed to the API Gateway and then to the Nucleus LFT, which interacts with Azure Blob Storage to fulfill the request. Certain requests are fulfilled by the PubSub controller, which also goes through the API Gateway and then to the PubSub Controller. The controller utilizes a dedicated etcd store to store publisher/subscriber session metadata.