Base Nucleus Stack
The Base Nucleus Stack stands up all of its components with their basic and default configuration.
It’s the primary foundation of your installation - with extra features added on top of it. This stack is also sufficient for basic Omniverse evaluation.
Please review the installation methodology prior to proceeding with installation.
Stack Notes
Scaling LFT
Large File Transfer (LFT) service can be scaled beyond default one instance to support increased throughput demands. We recommend one LFT instance per 10 concurrent up/downloads.
Scaling is achieved by spinning up more instances of nucleus-lft container
of the Base Stack, using docker-compose .... up --scale nucleus-lft=<#_of_instances> command.
Errors on Startup
If you see errors during the startup of the stack, please allow time for the stack to settle.
Errors may occur because Docker launches everything at the same time, and some services in a stack depend on other services.
For example, if the Authentication Service happens to come up before its dependency - Discovery Service - it will post an error, then be restarted by Docker.
Verifying Nucleus is operational
When all services “settle in” and are running stable (containers not restarting), first thing you should do is access Nucleus Navigator via your web browser using the IP Address or Hostname (depending on your configuration.)
Additionally, you can do the following checks in Nucleus Navigator:
Upload a file greater than 256KB, then download it - this validates the LFT Service
Upload an image and make sure that a thumbnail got created - this validates the Thumbnail service
Search for a file that you’ve uploaded - this validates the Search Service (Please note that building the index takes some time after service start up.)
Tag a file and see if that was successful and if the tag is properly read - this validates the Tagging service
Ports
Most ports used by Omniverse are customizable. Reference Networking and TCP/IP Ports for a comprehensive list of Omniverse ports.