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
