Ask is moving to Stack Overflow and Serverfault.com! Please use the "opendaylight" tag on either of these sites. This site is now in Read-Only mode

Revision history [back]

click to hide/show revision 1
initial version

I have just tested this approach using Helium-SR2 release of ODL with a simulated netconf device (using netconf testtool). Everything worked fine for me. What I did:

1 Started slightly modified netconf testtool (it did not support monitoring and did not provide any schemas, also the get-config operation was hardcoded to return some testing data):

<cont xmlns="urn:opendaylight:test">
    <l>Content</l>
</cont>

2 Put testing yang file in cache/schemas folder (the name of the file has to be test@2014-10-17.yang in this case):

    module test {
    yang-version 1;
    namespace "urn:opendaylight:test";
    prefix "tt";

    revision "2014-10-17";

    container cont {
      leaf l {
        type string;
     }
    }
    }

3 Started ODL 4 Spawned netconf connector that connects to simulated device over restconf. The configuration cotnained this piece of xml:

<yang-module-capabilities xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">
    <capability xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">
urn:opendaylight:test?module=test&amp;revision=2014-10-17
    </capability> 
</yang-module-capabilities>

5 Executed over RESTCONF get operation on: http://localhost:8181/restconf/config/opendaylight-inventory:nodes/node/newDevice/yang-ext:mount
The data I want was returned.

So could you try with SR2 releae ? and also check that your yang schema is correct and the data presented by the device is valid according to that schema ?

If it still does not work for you, I could have a look at your schema and data returned (if possible) or just take a look at the detailed log (with TRACE level set for netconf).

I have just tested this approach using Helium-SR2 release of ODL with a simulated netconf device (using netconf testtool). Everything worked fine for me. What I did:

1 Started slightly modified netconf testtool (it did not support monitoring and did not provide any schemas, also the get-config operation was hardcoded to return some testing data):

<cont xmlns="urn:opendaylight:test">
    <l>Content</l>
</cont>

2 Put testing yang file in cache/schemas folder (the name of the file has to be test@2014-10-17.yang in this case):

    module test {
    yang-version 1;
    namespace "urn:opendaylight:test";
    prefix "tt";

    revision "2014-10-17";

    container cont {
      leaf l {
        type string;
     }
    }
    }

3 Started ODL 4 Spawned netconf connector that connects to simulated device over restconf. The configuration cotnained this piece of xml:

<yang-module-capabilities xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">
    <capability xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">
urn:opendaylight:test?module=test&amp;revision=2014-10-17
    </capability> 
</yang-module-capabilities>

5 Executed over RESTCONF get operation on: http://localhost:8181/restconf/config/opendaylight-inventory:nodes/node/newDevice/yang-ext:mount
The data I want was were returned.

So could you try with SR2 releae release ? and also check that your yang schema is correct and the data presented by the device is valid according to that schema ?

If it still does not work for you, I could have a look at your schema and data returned (if possible) or just take a look at the detailed log (with TRACE level set for netconf).