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/TSC-124 tsc <p>OpenDaylight uses ietf-topology as one of the central models. This model has finally been standardized as ietf-network and ietf-network-topology.</p> <p>We need to drive adoption of this model in four key areas:</p> <ul> <li>NETCONF, <a href="https://git.opendaylight.org/gerrit/73661" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/73661</a></li> <li>OVSDB, which should mirror NETCONF by my estimate</li> <li>BGPCEP, which needs to find suitable replacements for draft isis/ospf topology</li> <li>OpenFlow world, which is using ietf-topology through opendaylight-topology</li> </ul> <p>This obviously impacts our NBI, but the differences are largely mechanic.</p> TSC-124

RFC8345 defines ietf-network(-topology), which we should adopt

Epic Medium Open Unresolved Unassigned Robert Varga Mon, 2 Jul 2018 20:28:10 +0000 Tue, 30 Apr 2019 01:38:56 +0000 General 0 3 <p>Impact analysis of ietf-network, showing the scope of work which is being done on top of these models:</p> <p><a href="https://www.yangcatalog.org/yang-search/impact_analysis.php?modules[]=ietf-network-topology&amp;recurse=3&amp;rfcs=1&amp;show_subm=0&amp;show_dir=dependents" class="external-link" target="_blank" rel="nofollow noopener">https://www.yangcatalog.org/yang-search/impact_analysis.php?modules[]=ietf-network-topology&amp;recurse=3&amp;rfcs=1&amp;show_subm=0&amp;show_dir=dependents</a></p> <p>Some concerns were risen today around the user impact and amount of work for this change. Would it be possible to know:</p> <ul class="alternate" type="square"> <li>Summary of API changes introduced by this model update.</li> <li>Estimated work to migrate key projects listed above.</li> </ul> <p>The model changes very few things in real terms:</p> <ul> <li>there are two models, ietf-network (i.e. inventory equivalent) and ietf-network-topology</li> <li>a change in namespace, hence a change in imports</li> <li>NetworkTopology, Topology, TopologyId, TopologyKey -&gt; Networks, Network, NetworkId, NetworkKey</li> <li>Structural comparison can easily be draw from comparing these sections: <ul> <li>Old: <a href="https://tools.ietf.org/html/draft-clemm-netmod-yang-network-topo-01#section-3.2" class="external-link" target="_blank" rel="nofollow noopener">https://tools.ietf.org/html/draft-clemm-netmod-yang-network-topo-01#section-3.2</a></li> <li>New: <a href="https://tools.ietf.org/html/rfc8345#section-4" class="external-link" target="_blank" rel="nofollow noopener">https://tools.ietf.org/html/rfc8345#section-4</a></li> </ul> </li> </ul> <p>In terms on time – NETCONF took ~8 hours to migrate, including UTs and adjustment of SFC to cope and an update to the model (which broke the patch again).</p> Relates TRNSPRTPCE-29 NETCONF-550 Development Epic Color ghx-label-9 Epic Name Adopt ietf-network Epic Status Rank 0|i03gb3: