Hi Miguel,

please check if HC sends required capabilities
https://github.com/opendaylight/groupbasedpolicy/blob/82637edd95d47c8fc594bf8fa3027d378183ca0d/renderers/vpp/src/main/java/org/opendaylight/groupbasedpolicy/renderer/vpp/manager/VppNodeManager.java
see initializeRequiredCapabilities() method

Have you registered HC as a mount point?

http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/HC_NODE
<node xmlns="urn:TBD:params:xml:ns:yang:network-topology">
   <node-id>HC_NODE</node-id>
   <host xmlns="urn:opendaylight:netconf-node-topology">IP</host>
   <port xmlns="urn:opendaylight:netconf-node-topology">NETCONF_PORT</port>
   <username xmlns="urn:opendaylight:netconf-node-topology">admin</username>
   <password xmlns="urn:opendaylight:netconf-node-topology">admin</password>
   <tcp-only xmlns="urn:opendaylight:netconf-node-topology">false</tcp-only>
   <keepalive-delay
xmlns="urn:opendaylight:netconf-node-topology">0</keepalive-delay>
</node>

If the remote node is recognized as vpp capable, it will be stored under
renderer-nodes Operational DS.
https://github.com/opendaylight/groupbasedpolicy/blob/88d2213d806ecb4712351676e1a4ef471f560ca8/groupbasedpolicy/src/main/yang/model/renderer.yang

Tomas

2016-11-21 13:02 GMT+01:00 Miguel Angel Muñoz Gonzalez <
miguel.angel.munoz.gonza...@ericsson.com>:

> 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 nodes registered with
> netconf capabalities? (honeycomb seems to be running and working).
>
> Thank you very much,
> Best Regards,
> MA.
>
>
> _______________________________________________
> groupbasedpolicy-dev mailing list
> groupbasedpolicy-...@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/groupbasedpolicy-dev
>
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Reply via email to