I have a question regarding what kind of OV subscription architecture to have for our use case.
We use Isaac Sim in the company (Company A) for the development of robotic applications and RL. The current setup consists of a single good development PC, which has an Omniverse launcher installed along with its local Nucleus server (Individual license). However, rather than using the native Isaac Sim app, we use the docker container version of the Isaac Sim and run multiple instances of the Isaac Sim containers simultaneously (it is much easier for us to use docker due to development reasons). Each Isaac Sim container can see the local Nucleus server running, which is useful for sharing data between the Isaac Sim containers.
Now, we would like to change this architecture a bit as we want the following features:
an option to store/backup our USD assets on the cloud
a proper version control on USD assets (e.g., checkpoints) and two-way synchronization of the files between local PCs and the servers.
collaborate on the USD assets with other companies (e.g., company B). Assume that Company B has the exact setup with us.
Based on our investigation, setting up an AWS/Azure server running a (containerized) Nucleus server and connecting the local OV Launchers (running on development PCs) to this server would be a solution. The attached picture demonstrates this architecture. My questions are:
Would this architecture really be a solution for us?
How many Enterprise subscriptions do we need for this? a) Only one for running a Nucleus container in the server, b) one for each company (running the OV Launcher + local Nucleus), or c) one for each Isaac sim container? d) something else. We are trying to understand the cost of having these features we want.
How is an Isaac Sim within a container associated with a user and the Nucleus server? E.g., are all Isaac Sim containers within a PC registered as the same user?
What are the pros/cons of using Isaac Sim containers in relation to OV Enterprise features? Are there any features unsupported from OV Enterprise just because we do not use the native app? E.g., two-way synchronization not being automatic, container users not being differentiable, etc.
Can we easily scale the proposed architecture (attached picture)? E.g., adding a second server by adding an additional Enterprise account on a new server (maybe one server for each company).
In general, I would be grateful if you could help me understand how OV Enterprise solutions work in the presence of dockerized Isaac Sims.
Based on your description above, this should work for what you’re trying to do. You would just have to make sure that both companies can access the Nucleus URL securely.
Hi @dlindsey , thank you for your answer. It is still not clear what counts as a user when we ue docker containers. E.g., if each container requires a separate user or only the one that is associated with the nucleus or if I need a separate user for the server within a cloud system. Would you be possible for you to have a look at my five questions once more?
@ozhanozen, a user is a principal that logs into the Nucleus server, let me get some more information about how Isaac is licensed.
Also, I’m a bit unclear on your questions 4 and 5.
It seems there may be some confusion about Nucleus itself. It is not a single user service, you can have multiple users log in and store data on the server. So, based on your diagram, you should have a single instance of Nucleus running (maybe two: one for each company - though there is no automated syncing between Nuclei). Then you would have users and your simulations all run against that single instance of Nucleus.
@dlindsey , while having an enterprise subscription for every individual user might work, we are trying to minimize the costs as much as possible, potentially mixing individual licenses with enterprise licenses. Our primary needs are the three features I wrote on top of what individual licenses provide; the other features of enterprise subscriptions are not crucial.
The question is: what is the minimum required number of enterprise subscriptions we need to set up the proposed architecture?
For example, to run a nucleus on the cloud, we need access to nucleus docker images, which is only available for an enterprise subscription, as far as I read. This is one subscription already. Do we need more enterprise subscriptions? Can we not simply use individual subscriptions within the development PCs that connect to the nucleus server in the cloud? Are there limitations to this?
Questions 3 and 4 are related to containerized versions of Isaac Sim and how they are associated with a license. I am confused there. It seems like Isaac Sims within containers are either free from a user account, or multiple containers within a PC are recognized as the same user.
Question 5 asks about the cost increase (in terms of the number of enterprise subscriptions) of adding a cloud that runs a nucleus server. For example, when Company B says: we would like to have our own independent server.
There is no special licensing for Isaac Sim. You do not need to buy all licenses upfront you can grow as needed. Based on your diagram there is not a way to tell you the number of licenses. Please refer to our license page to determine how many you need.
@ozhanozen If you would like I can connect you with Enterprise Sales. They can answer your questions specifically.
Based on my understanding you will need at least 2 enterprise licenses for at least one user at each company and to access an Enterprise Nucleus server. Each additional user can download Issac Sim and the ov launcher for free, but it would be better if they were Enterprise as well. Let me know if you want to talk to someone about it.
