New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Service Desginer - YANG #42

IanKruger opened this Issue Jul 25, 2018 · 0 comments


1 participant

IanKruger commented Jul 25, 2018

Templating Engine
The Templating Engine is responsible for managing the templates. When templates are created, they are uploaded to the object store (Katalog).

Netrino makes use of YANG models to define Services. Although YANG was designed along side NETCONF, it can be used for any arbitrary modelling since it can be serialized into popular API notation formats such as JSON or XML.

This means not only does Netrino support your favourite vendor out of the box by loading its YANG models (if it already supports NETCONF), but you can even make provision for ones that don't by creating the YANG model and driver for it yourself.

The YANG models are stored in the object store, and a helper function is supplied that can map the module name to the namespace, to be stored for easy lookup.

@IanKruger IanKruger added this to the Netrino Beta milestone Jul 25, 2018

@IanKruger IanKruger added this to To Do in Orchestrator via automation Jul 25, 2018

Vuader pushed a commit to Vuader/netrino that referenced this issue Oct 9, 2018

Vuader added a commit that referenced this issue Oct 9, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment