https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/INTTEST-2 integration-test <p>LINC (<a href="https://github.com/FlowForwarding/LINC-Switch" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/FlowForwarding/LINC-Switch</a>) is an OpenFlow-1.3 capable switch. It also implements the OFCONFIG protocol, so it would be very beneficial if we could integrate it in the lab, such that we can test not only OF, but also OFCONFIG (which is based on NETCONF).</p> <p>Operating System: All<br/> Platform: All</p> INTTEST-2

Integrate testing with LINC in the regression suite

Improvement Resolved Done Madhusudhan Ananderi Robert Varga Fri, 28 Mar 2014 20:41:12 +0000 Thu, 19 Oct 2017 22:33:55 +0000 Sat, 19 Nov 2016 00:45:04 +0000 0 8 <p>Madhusudhan is already working in testing Netconf.</p> <p>Hi, I have tested Netconf using docker image mentioned at <a href="https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Examples:Netconf#Docker_image" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Examples:Netconf#Docker_image</a> and found to be working fine.</p> <p>I have started testing using LINC switch now and keep you posted if I need any help. Thanks</p> <p>Robert,</p> <p>Am able to create netconf session between libnetconf client at the controller and LINC switch(netconf server).</p> <p>However, when I retrieve inventory nodes, the response could not find yang related capabilities.</p> <p>GET <a href="http://localhost:8080/restconf/operational/opendaylight-inventory:nodes/" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8080/restconf/operational/opendaylight-inventory:nodes/</a></p> <p>&lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;<br/> &lt;nodes <br/> xmlns="urn:opendaylight:inventory"&gt;<br/> &lt;node&gt;<br/> &lt;initial-capability <br/> xmlns="urn:opendaylight:netconf-node-inventory"&gt;urn:ietf:params:netconf:capability:writable-running:1.0<br/> &lt;/initial-capability&gt;<br/> &lt;initial-capability <br/> xmlns="urn:opendaylight:netconf-node-inventory"&gt;urn:ietf:params:netconf:capability:startup:1.0<br/> &lt;/initial-capability&gt;<br/> &lt;initial-capability <br/> xmlns="urn:opendaylight:netconf-node-inventory"&gt;urn:ietf:params:netconf:base:1.1<br/> &lt;/initial-capability&gt;<br/> &lt;id&gt;libnetconfd&lt;/id&gt;<br/> &lt;connected <br/> xmlns="urn:opendaylight:netconf-node-inventory"&gt;true<br/> &lt;/connected&gt;<br/> &lt;/node&gt;<br/> &lt;/nodes&gt;</p> <p>When I use GET <a href="http://localhost:8080/restconf/operational/opendaylight-inventory:nodes/node/libnetconfd/yang-ext:mount" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8080/restconf/operational/opendaylight-inventory:nodes/node/libnetconfd/yang-ext:mount</a>, I get 400 BAD Request status code and the response is</p> <p>Mount point does not contain any schema with modules.</p> <p>1. I am able to create netconf session between client and server using LINC openflow switch. I got hello message from netconf server:</p> <p>ssh -v -p 1830 -l linc -s 10.125.136.44 netconf<br/> &lt;?xml version="1.0" encoding="UTF-8"?&gt;&lt;hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"&gt;&lt;capabilities&gt;&lt;capability&gt;urn:ietf:params:netconf:base:1.1&lt;/capability&gt;&lt;capability&gt;urn:ietf:params:netconf:capability:startup:1.0&lt;/capability&gt;&lt;capability&gt;urn:ietf:params:netconf:capability:writable-running:1.0&lt;/capability&gt;&lt;/capabilities&gt;&lt;session-id&gt;3&lt;/session-id&gt;&lt;/hello&gt;]]&gt;]]&gt;</p> <p>2. GET request</p> <p>GET <a href="http://localhost:8080/restconf/operational/opendaylight-inventory:nodes" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8080/restconf/operational/opendaylight-inventory:nodes</a></p> <p>&lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;<br/> &lt;nodes <br/> xmlns="urn:opendaylight:inventory"&gt;<br/> &lt;node&gt;<br/> &lt;initial-capability <br/> xmlns="urn:opendaylight:netconf-node-inventory"&gt;urn:ietf:params:netconf:capability:writable-running:1.0<br/> &lt;/initial-capability&gt;<br/> &lt;initial-capability <br/> xmlns="urn:opendaylight:netconf-node-inventory"&gt;urn:ietf:params:netconf:capability:startup:1.0<br/> &lt;/initial-capability&gt;<br/> &lt;initial-capability <br/> xmlns="urn:opendaylight:netconf-node-inventory"&gt;urn:ietf:params:netconf:base:1.1<br/> &lt;/initial-capability&gt;<br/> &lt;id&gt;libnetconfd&lt;/id&gt;<br/> &lt;connected <br/> xmlns="urn:opendaylight:netconf-node-inventory"&gt;true<br/> &lt;/connected&gt;<br/> &lt;/node&gt;<br/> &lt;/nodes&gt;</p> <p>I could see the difference at this response when using netopeer server. I suspect LINC switch doesn't have support on yang modules and that's the problem in not getting yang data in the response.</p> <p>3. I am currently in the process of LINC integration with Mininet, so I can get both the topology information as well as netconf configuration.</p> <p>4. I would like to do the following basic netconf operations: </p> <p>(a) get Netconf session details <br/> (b) retrieve running configuration and device state configuration<br/> (c) how to copy/delete the configuration<br/> (d) close and kill the netconf session</p> <p>I am not sure how to do it. Can someone shed some light on this?</p> <p>Regarding netopeer issue, I've filed <a href="https://jira.opendaylight.org/browse/CONTROLLER-306" title="Regression when connecting to netopeer netconf server" class="issue-link" data-issue-key="CONTROLLER-306"><del>CONTROLLER-306</del></a> - this is a regression as I was able to get the operational data using restconf before. <br/> Regarding LINC, I don't have it installed (if you could create a trusted docker image that would be great<img class="emoticon" src="https://jira.opendaylight.org/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/>) but if it does not advertise yang models via netconf-monitoring extension the data will not be available. This can be verified by increasing logging level on org.opendaylight.netconf,org.opendaylight.controller.sal.connect.netconf to TRACE and checking the hello message.<br/> There is an improvement tracked as <a href="https://jira.opendaylight.org/browse/CONTROLLER-256" title="Loading YANG files from local directory when netconf server does not support netconf monitoring" class="issue-link" data-issue-key="CONTROLLER-256"><del>CONTROLLER-256</del></a> that would overcome this issue by placing the yang models on local file system. AFAIK nobody is currently working on it.</p> <p>LINC switch doesn't support IETF netconf-monitoring. Hence it does not advertise yang models via netconf-monitoring extension and the the data will not be available.</p> <p>2014-04-10 17:46:41.769 PDT <span class="error">&#91;nettyThreadgroupModule$NioEventLoopGroupCloseable-6-6&#93;</span> DEBUG o.o.c.n.c.SimpleNetconfClientSessionListener - Client session ServerNetconfSession</p> {sessionId=1} <p> went up<br/> 2014-04-10 17:46:41.770 PDT <span class="error">&#91;pool-24-thread-1&#93;</span> DEBUG o.o.c.s.c.n.NetconfDevice#libnetconfd - Initial capabilities []<br/> 2014-04-10 17:46:41.771 PDT <span class="error">&#91;pool-24-thread-1&#93;</span> INFO o.o.c.s.c.n.NetconfDevice#libnetconfd - Netconf server 10.125.136.44/10.125.136.44:1830 does not support IETF Netconf Monitoring<br/> 2014-04-10 17:46:41.773 PDT <span class="error">&#91;pool-24-thread-1&#93;</span> DEBUG o.o.c.s.c.n.NetconfDevice#libnetconfd - Trying to create schema context from []<br/> 2014-04-10 17:46:41.778 PDT <span class="error">&#91;pool-24-thread-1&#93;</span> DEBUG o.o.c.s.c.n.NetconfDevice#libnetconfd - Client capabilities <span class="error">&#91;urn:ietf:params:netconf:capability:writable-running:1.0, urn:ietf:params:netconf:capability:startup:1.0, urn:ietf:params:netconf:base:1.1&#93;</span><br/> 2014-04-10 17:46:41.783 PDT <span class="error">&#91;pool-24-thread-1&#93;</span> DEBUG o.o.c.s.c.n.NetconfDevice#libnetconfd - Update device state transaction DOM-2 putting operational data started.<br/> 2014-04-10 17:46:41.784 PDT <span class="error">&#91;pool-24-thread-1&#93;</span> DEBUG o.o.c.s.c.n.NetconfDevice#libnetconfd - Update device state transaction DOM-2 putting operational data ended.<br/> 2014-04-10 17:46:41.787 PDT <span class="error">&#91;pool-24-thread-1&#93;</span> DEBUG o.o.c.s.c.n.NetconfDevice#libnetconfd - Update device state transaction DOM-2 SUCCESSFUL.</p> <p>LINC switch announced capabilities only for Netconf protocol, but did not announced OF-Config, nor IETF-Monitoring. In general, IETF-Monitoring is required for ODL to automatically download models from Netconf Server, otherwise YANG models are used from cache/schema</p> <p>OF Config announcement (and announcements of other YANG modules) provides an information that netconf server support OF-Config (it references OF-Config YANG module), this actually triggers Netconf Connector to look up the YANG model (be it from cache/schema or via IETF-Monitoring from Netconf Device)</p> <p>LINC does not support the "netconf monitoring" feature required for netconf plugin to import yang models and generate RESTConf API.</p> Development Rank 0|i01lb3: