Hello.
We have multiple RTX Workstations that we would like to connect to a single shared nucleus. Initially we designated one of the Workstation as a shared nucleus within our LAN and could collaboratively work. Now we would like to have the same set up without being in a single LAN.
We followed the instructions provided in this link to set up a VM in Azure: Nucleus on Microsoft Azure — Omniverse Nucleus
The installation displayed no errors and we were able to connect to the Enterprise Nucleus from all the RTX workstations.
If a scene was created with assets purely from the Nvidia library, the saving of the USD works in the shared Enterprise Nucleus. We are UNABLE to save any of our custom assets/scenes as a USD in the shared Enterprise Nucleus (with or without Flattening).
Did any of you face a similar situation ? Any help in this regard would be appreciated.
@deepa.kasinathan as someone who doesn’t have enterprise nucleus setup, i’ll defer to the mods/devs on this. that said, i am curious whether there were any error/warning messages from the console/nucleus log when attempting to save custom assets? given you can save asset from NVIDIA library, it doesn’t sound like a permission issue, but i could be wrong.
This is pretty advanced for Nucleus. Let me get our Nucleus expert to try to help. So you can READ files from there and connect fine, but you cannot WRITE files?
@Richard3D@dlindsey Thank you both for the prompt replies.
If this a proxy issue - then should it not allow ANY FORM of WRITE ? We can WRITE files that only references the assets in the Nvidia Library path.
We did not change the gateway’s supplied in the Nucleus containers.
We do have Enterprise license. How do I contact the support team ? I used the link on this page: Enterprise Customer Support | NVIDIA
This just routes me back to the AppHub UI
I an unable to create a case. Can you provide further guidance on this. Thanks.
When you click on that link, it should direct you to login to create a case. Once you login, does it work?
So going back to the issue, you were saying that you are in fact, using our supplied gateway with nucleus? Then, in that case, it’s more question of making sure you’re not configuring any proxies on top.
@Richard3D - Regarding the Enterprise support ticket : Doing the login is what kept me routing in a loop through the above mentioned two sites. I found a workaround. I was able to get a ticket-template if I clicked the “create a case without a login”. I have submitted a ticket now and uploaded our entitlement certificate.
Back to the issue: We did not change any gateways or configure any proxies.
The odd thing is that, when we try to save something, the folder structure from the end workstation is created in the shared nucleus. But no USD files get saved.
Hi @dlindsey. You were correct. The LFT port was not added to the list of inbound ports. This information is not directly listed on here: Nucleus on Microsoft Azure — Omniverse Nucleus but separately in a different link and we unfortunately overlooked it.
Now, the saving is working and we can move our localhost from Workstation to the cloud.
