omni.services extensions and Omniverse Kit’s
--exec command-line option makes it easy to get started with services.
As the service evolves and grows, it might be worth turning the service itself into an Extension so that it is easy to ship and distribute.
Doing so will also give all the power of extensions to services, with the possibilities to set up dependencies on other extensions, install additional Python packages and take advantage of the settings framework.
Starting with a very simple “Hello World” Python example:
1from omni.services.core import main 2 3def hello_world(): 4 return "Hello World!" 5 6main.register_endpoint("get", "/hello-world", hello_world)
That is all there is needed to write a service. To run this with Omniverse Kit and an HTTP transport:
./kit \ --exec hello_world.py \ --enable omni.services.core \ --enable omni.services.transport.server.http \ --/exts/omni.kit.registry.nucleus/registries/0/name=kit/services \ --/exts/omni.kit.registry.nucleus/registries/0/url=https://dw290v42wisod.cloudfront.net/exts/kit/services
By default, an API documentation page is created to list the services exposed, and accessible at
It is possible to exercise the API from that webpage by using the
Try it out feature within the different endpoints.
omni.kit.registry.nucleus settings make sure that the Omniverse services extensions can be found and downloaded as by default they do not ship with the Kit SDK.
A more involved example is available at the following GitHub Repository: https://github.com/NVIDIA-Omniverse/deep-dive-into-microservices
Omniverse Kit ships with several more advanced services and more are available in the extension registry and Omniverse Farm is also fully built using the microservices stack within Omniverse and is made up several different services. Its code is available from the Omniverse Launcher after which its code can be explored.