Sent: Thursday, September 5, 2019 11:49 PM
To: Anil Vishnoi
Cc: disc...@lists.opendaylight.org; controller-dev@lists.opendaylight.org;
mdsal-...@lists.opendaylight.org; openflowplugin-...@lists.opendaylight.org;
rele...@lists.opendaylight.org
Subject: Re: [release] [controller-dev] Migrating
[+ 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
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
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
