Hi Nathan, The idea was to use a generic standards-based topology model when compared to opendaylight inventory model. This way individual southbound modules can use unified model.
There was a dichotomy in terms of which standard topology model to choose. Actually, there are two models to consider for this migration - [1] and [2]. Decision of which model to choose across the projects and still meet release schedules posed few challenges as discussed in [3] [1] https://tools.ietf.org/html/draft-clemm-netmod-yang-network-topo-01 [2] https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo-01 [3] https://lists.opendaylight.org/pipermail/tsc/2015-September/003837.html Regards Muthu -----Original Message----- From: controller-dev-boun...@lists.opendaylight.org [mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of Nathan Sowatskey Sent: Sunday, August 14, 2016 12:37 PM To: controller-dev Subject: [controller-dev] OpenDaylight inventory Yang model status Hi I am trying to explain a slice through the ODL stack based on the DLUX Nodes application and the opendaylight-inventory:nodes resource RESTCONF API. This is part of a training exercise that I am developing. I can see that the opendaylight-inventory:nodes RESTCONF API is used by the DLUX Nodes application, so I am guessing that the API is current and relevant. The Nodes code that uses the opendaylight-inventory:nodes is: dlux/modules/node-resources/src/main/resources/node/nodes.services.js node.factory('NodeInventorySvc', function(NodeRestangular) { var svc = { base: function() { return NodeRestangular.one('restconf').one('operational').one('opendaylight-inventory:nodes'); }, data : null }; When I am looking at the Yang models for opendaylight-inventory and netconf-node-inventory, though, I see “status deprecated” everywhere. That makes me suspect that this model, and so the APIs based on it, are not current and relevant, or are planned to become not so. The Yang file I am looking at is: controller/opendaylight/model/model-inventory/src/main/yang/opendaylight-inventory.yang typedef support-type { status deprecated; typedef node-id { status deprecated; and so on. I know that this is all in flux and so on, but could anyone shed any light on the actual and proposed status here please? Many thanks Nathan — Nathan John Sowatskey Consulting Engineer - Programmable Infrastructure, DevOps, IoT and SDN nat...@nathan.to www.linkedin.com/in/nathandevops XMPP: nathando...@im.koderoot.net Google: nathanjohnsowats...@gmail.com Skype: nathan_sowatskey Twitter: NathanDotTo GitHub: https://github.com/DevOps4Networks http://www.kipling.org.uk/poems_if.htm _______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev _______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
