Forward to: [email protected] [email protected] [email protected]
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Yang, Yi Y Sent: Thursday, November 24, 2016 8:56 AM To: Miguel Angel Muñoz Gonzalez <[email protected]>; [email protected] Cc: Manuel Buil <[email protected]> Subject: Re: [honeycomb-dev] Vpp nodes not being netconf capable Hi, Miguel I tested ODL SFC master, vpp nodes have been mounted, but we didn't receive data store update event, this is the root cause, I know Manuel is also debugging this, I'm fixing it, I think ODL netconf changed something so that vpp renderder can't work normally, it is ok when I tested this two or three weeks ago. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Miguel Angel Muñoz Gonzalez Sent: Wednesday, November 23, 2016 7:07 PM To: [email protected] Subject: [honeycomb-dev] FW: Vpp nodes not being netconf capable Sorry, this message was not sent to honeycomb list due to a typo in the address. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Miguel Angel Muñoz Gonzalez Sent: lunes, 21 de noviembre de 2016 13:03 To: [email protected]; [email protected] Cc: [email protected]; [email protected] Subject: [vpp-dev] Vpp nodes not being netconf capable Hi everyone, While browsing the ODL SFC code I see that VppNodeListener requires vpp nodes to be netconf capable in order to be manageable and stored in the internal hashmaps. public void onDataTreeChanged(@Nonnull Collection<DataTreeModification<Node>> changes) { printTraceStart(LOG); for (DataTreeModification<Node> modification : changes) { DataObjectModification<Node> rootNode = modification.getRootNode(); switch (rootNode.getModificationType()) { case WRITE: case SUBTREE_MODIFIED: if (rootNode.getDataAfter() != null) { Node node = rootNode.getDataAfter(); if (nodeManager.isCapableNetconfDevice(node)) { nodeManager.updateNode(node); } break; However, after registering VPP nodes I can only see this in network topology: { "network-topology": { "topology": [ { "topology-id": "topology-netconf", "node": [ { "node-id": "controller", "netconf-node-topology:host": "192.168.255.100", "netconf-node-topology:port": 2831, "netconf-node-topology:username": "admin", "netconf-node-topology:password": "admin", "netconf-node-topology:tcp-only": false, "netconf-node-topology:keepalive-delay": 0 }, As you can see there are not netconf capabilities shown, thus when using vpp-renderer in sfc it cannot find any node and it fails. Do you know what is required in order to have vpp + honeycomb nodes registered with netconf capabalities? (honeycomb seems to be running and working). Thank you very much, Best Regards, MA. _______________________________________________ vpp-dev mailing list [email protected] https://lists.fd.io/mailman/listinfo/vpp-dev _______________________________________________ honeycomb-dev mailing list [email protected] https://lists.fd.io/mailman/listinfo/honeycomb-dev _______________________________________________ honeycomb-dev mailing list [email protected] https://lists.fd.io/mailman/listinfo/honeycomb-dev _______________________________________________ sfc-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/sfc-dev
