Thanks for the summary Hema, this morning I could not attend the call but this
is useful info. Question: do we plan to put also in .cfg those knobs that are
only in yang today, like for example the idle-flow mode I have tested recently.
BR/Luis
> On Jan 19, 2017, at 8:31 PM, Hema Gopalkrishnan
According to our discussion yesterday, config knobs will be defined in .cfg
files and in yang (same names to be used in both places)
1. Values defined .cfg files will be the Day 0 configuration. These
values will be used initially.
2. If the admin wants to change it at run time, the
OpenFlow Plugin:
Functionality Freeze:
1. Final list of externally consumable APIs defined: Yes
** If you had any Tentative APIs, have they been moved to Provisional or
Dropped? Yes/No (link to release plan) N/A
** If any of your Tentative APIs were dropped, have you notified all
projects that
-
Browser Friendly format meeting minutes:
-
http://meetings.opendaylight.org/opendaylight-openflowplugin/2017/openflow_plugin_meeting_jan_19__2017/opendaylight-openflowplugin-openflow_p
I added the wait to avoid heisenbugs where the app expects the RPC impl to be
there on startup, i.e. it can't startup and will fail if the impl isn't
present. But if there are apps which don't require this, i.e. the impl is
registered dynamically based on some event, then we can add a flag to e
On 01/19/2017 01:37 PM, Tom Pantelis wrote:
> yes - it looks like RpcServiceMetadata can't find the DOMRpcService. All
> the DOM services are instantiated/registered
> in
> controller/opendaylight/md-sal/sal-dom-broker/src/main/resources/org/opendaylight/blueprint/dom-broker.xml
>
So this looks
