* Created a config flag in RESTCONF protocol, to allow the protocol
to be dynamically configured to work with either YMS or Dynamic Config
during runtime.
* Note that this is an interim solution to help RESTCONF migrate from
YMS to Dynamic Config. The changes will be removed once the migration
is complete.
Change-Id: I36dc8537c88965034da6238df32dde7558ac5f5c
1. BUCK file fixes in RESTCONF
2. Changed tenbi/yangmodel bundle to feature. This is required for YMS
schema registration.
3. Added TE topology, TE tunnel, tenbi, restconf server, and TE provider to modules.defs.
Change-Id: I5bc3208c7fe823352500a63f87bfd990cb3037b4
1. Add skeleton code of LispMapReferral message type
2. Refactor LispLocatorRecord and LispMapRecord
Change-Id: Icbe6243e5892a0bfb784ba3c0daa22ab73c7e977
* Added a callback function mechanism to the RESTCONF notification
listener. Applications can register their callbacks to a listener.
This is to allow multiple SB providers share one generic listener.
while still being able to process app-specific events.
* Created a default RESTCONF notification listener implementation.
* Refactored TE provider code to allow TE-topology and TE-tunnel share one
RESTCONF event listener
Change-Id: I26dc4972683fcda3eefacde131353312809aa95e
This submission contains the restconf portion of the changes of the follwoing
submission:
https://gerrit.onosproject.org/#/c/12310/
Change-Id: I7534c8491633f0e9a6062b337a6fd79013202940
This commit integrates the REST proxy within the standard REST
protocol and provider, supporting multiple devices managed by
a single REST end point (e.g. a REST-based second level controller).
It introduces the concept of RestSBServer, that represents
the REST service exposed by a single or a set of devices.
Change-Id: I0b187151848c20bc1fd8c39a33d57a500f667533
- Added handler for idle OF channel
- Workaround for device not responding to meter feature request (ONOS-5834)
Change-Id: I72435c65fa427c3f7668a0042b9425eb726cd54e
For example, "id=of:0000000000000203, available=true, local-status=connected 18m7s ago, role=STANDBY, ..."
Also increasing the resolution of the TimeAgo utility.
Change-Id: Ie1b89bd193552e0edd38a9ca28c5ce99b1d27c19
There are a few places where Throwable.getMessage() is emitted directly
instead of utilizing a Throwable argument to the Logger output methods.
Using debug as an example, when dealing with exception reporting cases,
it is, generally better to rely upon:
http://www.slf4j.org/api/org/slf4j/Logger.html#debug(java.lang.String, java.lang.Throwable)
than:
http://www.slf4j.org/api/org/slf4j/Logger.html#debug(java.lang.String)
This commit also cleans up the language of another log message.
Change-Id: I53a77286069c112aafc83ad8157a439a4d50e52e
Signed-off-by: Ryan Goulding <ryandgoulding@gmail.com>
