Operating System: Windows
Platform: PC

Changed to enhancement, since this is new feature.

Thanks Tony for having a look at it.

Would it be right to load the yang files from local directory or should the yang files be written in a separate osgi bundle.

Also, if we put the yang files in local directory, there will be no java source code generated - so in that case how to manipulate the device data?

-Kanika

Hi Tony,

Is it possible to reference the yang files from OSGI bundle when netconf server doesn't support ietf monitoring.

Because now i have to keep two copies of yang files:

1) OSGI bundle
2) In /cache/schema for restconf

-Kanika

. I have a netconf server which does not support netconf monitoring and therefore no yang files are loaded from the device. So I wrote my own yang file that represent the device and below is what I hard coded.

With recent refactoring done in this area, you might not find NetconfDevice.xtend, please look for NetconfDevice.java.

1. Placed 03-neconf-devices.xml in initial directory, updated netconf server ip, port, password, name. Started the controller and was able to see the netconf servers in opendaylight inventory (http://localhost:8080/restconf/operational/opendaylight-inventory:nodes/)
2. Wrote yang file to represent netconf server (based on get-config information received from the node using netconf rpc) and placed it in /cache/schema. But netconf plugin was not reading this yang file and I filed the bug-628 for it. However, to proceed I hardcoded server capabilities in NetconfDevice.xtend as below:
o a) Declare following variables in NetconfDevice.xtend
Set<String> newServerCapabilities
Collection<String> newCapabilities
o Add following code in NetconfDevice.xtend
private def getNewServerCapabilities()

o Update getInitialCapabilities() method as below
def getInitialCapabilities() {
//val capabilities = client?.capabilities; //Notice this commented line
val capabilities = getNewServerCapabilities();
o From command prompt go to the location \\odl-controller\opendaylight\md-sal\sal-netconf-connector and "run mvn clean install"
o Copy sal-netconf-connector-1.1-SNAPSHOT.jar from .m2 repository to odl's plugin folder.
o Accessed device information using postman with below URL:
http://localhost:8080/restconf/config/opendaylight-inventory:nodes/opendaylight-inventory:node/node_0001/yang-ext:mount/

https://git.opendaylight.org/gerrit/#/c/9107/

https://git.opendaylight.org/gerrit/#/c/9107/

I have fixed the code to read the schema file from ODL local.

Hi I have fixed the ODL code and below mentioned gerrit code can be used for fixing the issue:

changes in MD-SAL: https://git.opendaylight.org/gerrit/#/c/9135

changes in yangtools: https://git.opendaylight.org/gerrit/#/c/9112/

(In reply to Ankit agarwal from comment #6)

Hi

Your commits do not solve the problem reported here. This problem says that if you put yang files into local folder for a device that does not report its modules, there is no way for netconf-connector to load them. There needs to be a mechanism to tell netconf-connector about schemas in /cache/schema folder.

You are possibly solving a problem with device reporting yang modules but without revision. Is that correct ? If so, please report a new bug and put your commits there.

Maros

Raised a new Bug - 1393 as suggested

https://git.opendaylight.org/gerrit/#/c/9490/

Hi Maros/Kanika,

I checked the above commit message https://git.opendaylight.org/gerrit/#/c/9490/ and it says "User can place yang files into cache/schema folder and set the capabilities for these modules into config attribute for netconf-connector."

I'm using the ODL's Service Provider Ubuntu VM in my testing. I've added my YANG file in controller-sp/opendaylight/cache/schema. But, I'm unable find the file where I've to add the capabilities.

Regards,
Rahul Swaminathan