| tag | 95090852ea1d3aa0be48e75d863972a151243dea | |
|---|---|---|
| tagger | Jenkins <do-not-reply@opencord.org> | Mon Feb 04 16:24:35 2019 +0000 |
| object | 47b4730f755aee8ce313aca62d12539c849b3149 |
Tagged by CORD Jenkins version-tag job: 1085, for Gerrit patchset: 12668
| commit | 47b4730f755aee8ce313aca62d12539c849b3149 | [log] [tgz] |
|---|---|---|
| author | Scott Baker <smbaker@gmail.com> | Wed Jan 30 16:55:07 2019 -0800 |
| committer | Scott Baker <smbaker@gmail.com> | Fri Feb 01 15:39:46 2019 -0800 |
| tree | 9ad11b778ccf6e4435a205521647b74e885a6beb | |
| parent | ae33e1674d0b3fd2a327cb6740414e19536768cd [diff] |
SEBA-405 Update VOLT Service to use synchronizer library Change-Id: I8292e0e7d1b7c76b1e53d9bd944abf95d9b38333
This repositoritory contains the XOS service that is responsible for the integration with VOLTHA.
At the moment the RCORDService assume that this service (or a service exposing the same APIs) is sitting after it in the service chain.
This service will listen for events on the kafka bus, in the topic onu.events
The events this service will react to are:
We assume that:
vOLTService service is a subscriber of MyOssService via ServiceDependencyMyOssService has type = ossMyOssService expose and API named validate_onuvalidate_onu API will be responsible to create a subscriber in XOSIf no OSS Service is found in between the providers of vOLTService no action is taken as a consequence of an event.