Hi, When mounting a netconf device initially there is an option to have a custom distinct schema cache for that node that is separate from the default cache/schema. You can also have multiple nodes using your distinct cache if they use the same yang modules so you may allocate them accordingly. When doing your initial put request for your netconf mount you can add the following option: <schema-cache-directory xmlns="urn:opendaylight:netconf-node-topology">custom_cache_name_here</schema-cache-directory> This should create a separate schema cache that can be found under /cache/custom_cache_name Hope this helps!
Yup. If you have a network of devices which have inconsistent models, this is the only way forward -- i.e. configure devices sharing the same view of a model to share a particular schema directory.
At the end of the day, you can go as far as having each device have its own cache directory (although I would not call that kind of setup efficient).
When mounting a netconf device initially there is an option to have a custom distinct schema cache for that node that is separate from the default cache/schema. You can also have multiple nodes using your distinct cache if they use the same yang modules so you may allocate them accordingly.
When doing your initial put request for your netconf mount you can add the following option: <schema-cache-directory xmlns="urn:opendaylight:netconf-node-topology">custom_cache_name_here</schema-cache-directory>
This should create a separate schema cache that can be found under /cache/custom_cache_name
I have a problem with the Netconf mount points. Our netconf devices use the same yang modules with the same revisions but with different contents. Most differences are in feature-list but not only. Also, appeared that it is impossible to enforce any discipline in this area, especially in the development time.
When we try to mount such devices we get unresolved capabilities. If we mount only one device, everything is fine. So, each device has a consistent data schema. They simply cannot work together.
Apparently, ODL uses the shared data schema for all mount points.
The question is if it is possible to have a separate data schema for each mount point isolated from other mount points. Obviously, the solution should include the split of the cache of yang files also.
