How microsoft/nvidia-omniverse-azure-operations-twin works
Main components
• Infrastructure Provisioning and Networking:
– Bicep templates for creating Azure resource groups, virtual networks, subnets and NAT/NSG rule sets.
– DNS and certificate configuration (both self-signed and Let’s Encrypt options).
• Cloud Services and Edge Components:
– Azure IoT Services, Event Hubs, and Azure Data Explorer feeding telemetry.
– API Management service deployed in a dedicated subnet.
– Application Gateway with Web Application Firewall that fronts the API management and streaming endpoints.
• Kubernetes Cluster (AKS) and associated node pools:
– General purpose/compute nodes in the main “agentpool” (for base services including Flux, ingress controllers, and standard applications).
– Memory-optimized nodes (“cachepool”) running memcached (to improve shader caching and streaming session performance).
– NVIDIA GPU nodes (“gpupool”) dedicated to the Omniverse Kit Streaming pods.
• Helm-Managed Services on AKS:
– Kit App Streaming Manager, Kit App Streaming Applications, and RMCP (Resource Management Control Plane) deployed via Helm charts.
– Supplementary services such as Flux (for GitOps) and External DNS (for dynamic DNS updates).
• ISV Custom Omniverse Kit Application:
– The kit-app-source directory contains sample modules (USD viewer, messaging, and setup) for customizing the Kit application.
– Instructions in the README describe how to containerize a kit app (with premake scripts and custom configuration).
• Web-based Front End:
– The web-app folder contains a complete React application that integrates several partitions:
• A 3D Viewport component which receives and displays the lower-latency Omniverse streaming session (with USD content).
• Components for embedding and interacting with a Power BI report (using Redux to synchronize state between the dashboard and 3D viewport).
• Additional debug and state management tools.
– The web app deployment also includes configuration for Azure Static Web Apps and integration with authentication (as seen in the authConfig template).
Relationships and interactions
• IoT devices send real-time telemetry data into Azure IoT Operations. That data streams via Event Hubs and Azure Data Explorer to update Power BI reports.
• Power BI is integrated into the web-app. In the UI, selection in the report (or events coming from Event Hub) update a Redux global state, which then synchronizes with the 3D Omniverse streaming viewport.
• The Omniverse Kit streaming service is deployed on the AKS cluster. It automates cloud rendering by dynamically provisioning kit app streaming sessions with GPU nodes.
• API Management (APIM) and Application Gateway sit in front of the internal services. They provide a secure, managed access layer (with custom domains and certificates) to both the streaming services and the web APIs.
• The control flow for deployments is managed by Helm charts and GitOps through Flux, using detailed Kubernetes manifests (found under the k8s/templates directories).
• Scripts and bicep modules automate Azure resource provisioning and configuration (and certificate generation) ensuring that the infrastructure is aligned with the network and security requirements.
Architectural patterns and design principles
• Microservices/Modular design: Each service—from the Omniverse Kit Application streaming components to Power BI integration—is developed, containerized, and deployed as an independent module.
• Infrastructure-as-Code: Bicep scripts, Helm charts, and Kubernetes manifests ensure repeatable deployments.
• Cloud-Native/Container Orchestration: AKS is used with multiple node pools (segregated by workload types) to isolate GPU-intensive workloads from others.
• GitOps and Declarative Configuration: Flux is deployed to maintain configuration state in Git and push out changes automatically.
• Secure and Scalable Networking: Azure’s API Management, Application Gateway with WAF, and DNS configuration (internal and external) provide secure exposure of the services.
• State Synchronization and Event-Driven Updates: The React web client, through Redux and event hubs, forms a bi-directional communication channel between the 3D viewport and Power BI.
Relevant technologies and frameworks
• Azure Cloud Services (AKS, API Management, Application Gateway, Azure DNS, Azure Container Registry)
• NVIDIA Omniverse Kit App Streaming technology, using container images sourced via NVIDIA NGC.
• Kubernetes as an orchestration layer with Helm for deployments.
• Infrastructure-as-Code tools (Bicep) for resource provisioning.
• GitOps using Flux.
• React (with Typescript), Redux, and associated tooling (Vite/Webpack) for the web client.
• Integration with external services such as Power BI and Event Hubs.
• Clear labels on all major components:
– “Azure Infrastructure” (highlighting Resource Group, Virtual Network and Subnets)
– “AKS Cluster” with subcomponents: Agent Pool (Compute), Cache Pool (Memcached), GPU Pool (Omniverse Streaming)
– “Helm/Flux Managed Services” showing Kit App Streaming Manager, Applications, RMCP, GPU Operator, Memcached, and Ingress Controllers
– “API Exposure Layer” showing API Management and Application Gateway with custom domains and certificates
– “Web Front End” with React App integrating Power BI and a 3D Viewport
– “External Services” – Azure IoT Edge, Event Hubs, Power BI, etc.
• Annotations to explain special patterns, such as “GitOps – Flux Controller,” “Infrastructure as Code – Bicep templates,” and “Service Segregation – Multiple Node Pools.”
Importance of detail
• Be meticulous by labeling sub-components such as “Ingress Controller (Nginx – internal)” within the AKS layer.
• Presence of automated pipelines (via Helm charts and Flux) and the security layers (NSGs, certificates, API management configuration).