| commit | 3db0eef3c1b3aedd8fdc6e09a662b5c9e188febc | [log] [tgz] |
|---|---|---|
| author | Scott Baker <smbaker@gmail.com> | Tue Jan 15 11:56:41 2019 -0800 |
| committer | Scott Baker <smbaker@gmail.com> | Tue Jan 15 11:56:41 2019 -0800 |
| tree | f70f0b5bbd0ab835fb043db21b10d5048d333682 | |
| parent | e35bec4bf553e8eca45ddd87f56bc24384d07eb8 [diff] |
SEBA-381 Expose ONU reason in XOS modeling Change-Id: I921a53df6ef5a083b137c5529ecce8143863ea95
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.