Re: [controller-dev] Migrating inventory/topology models

2019-09-05 Thread Robert Varga
[+ discuss, mdsal-dev] On 05/09/2019 19:24, Anil Vishnoi wrote: > As for the next steps, I think we need to migrate these models to > openflowplugin, where they can be maintained, as that world is the only > place that really uses them. > > As far as upstream OpenDaylight is concern

Re: [controller-dev] [OpenDaylight Discuss] Migrating inventory/topology models

2019-09-05 Thread Luis Gomez
I think in the case of OFP the work can be split in 2: - Update topology model to last RFC (same as other projects in ODL). To me the sooner we can do this the better. This also may have reduced impact in OFP apps because the topology model contains very few data (e.g. no specific OFP

[controller-dev] Migrating inventory/topology models

2019-09-05 Thread Robert Varga
Hello everyone, as it currently stands, then only projects which are using opendaylight-{inventory,topology}*.yang models are OpenFlow-specific projects (openflowplugin, genius, sfc (in sfc-genius-utils), netvirt), plus a soon-to-be-deprecated component in controller/netconf. These models have

Re: [controller-dev] Migrating inventory/topology models

2019-09-05 Thread Anil Vishnoi
On Thu, Sep 5, 2019 at 8:56 AM Robert Varga wrote: > Hello everyone, > > as it currently stands, then only projects which are using > opendaylight-{inventory,topology}*.yang models are OpenFlow-specific > projects (openflowplugin, genius, sfc (in sfc-genius-utils), netvirt), > plus a