| commit | 102b89592db01d8361a754c11a85699e5d2e965c | [log] [tgz] |
|---|---|---|
| author | Tommy Carpenter <tc677g@att.com> | Fri Mar 20 10:02:46 2020 -0400 |
| committer | Tommy Carpenter <tc677g@att.com> | Fri Mar 20 12:27:06 2020 -0400 |
| tree | 34a70a8625fd6a98fae5e4f06292203f63ebb1d1 | |
| parent | 4014a85d3cc546bf39ffa64c5cfe6e21944d2afb [diff] |
Updates:
* Switch to python3.8
* Switch to SI95 from NNG (rmr v3 vs rmr v1)
* The switch to SI95 led to a rabbit hole in which we eventually discovered that rmr_send may sometimes block for an arbitrary period of time. Because of this issue, a1's sends are now threaded. Please see the longer comment about this in a1rmr.
* Bump version of py xapp frame (SDL used only) in A1
* Bump version of go xapp frame (0.0.24 -> 0.4.2) in integration tests
* Add some additional logging in A1
Issue-ID: RIC-156
Change-Id: I8ed5356bea60a3ccea6fa2d03981ad634b98bab1
Signed-off-by: Tommy Carpenter <tc677g@att.com>
The xApp A1 mediator exposes a generic REST API by which xApps can receive and send northbound messages. The A1 mediator will take the payload from such generic REST messages, validate the payload, and then communicate the payload to the xApp via RMR messaging.
Please see documentation in the docs/ subdirectory.