Table of Contents |
---|
High Level
The POMBA code and containers are an implementation of a model based audit where logging transaction tracing would assist this new audit code in determining the differences and causes of any discrepancy between the model intent and the reality of VNF orchestrations.
Actions
A new set of new microservices around orchestration model based auditing are being proposed as an addition to the logging prkject project and up sourced into ONAP for the Casablanca release.
A meeting with the architecture subcommittee is planned for the 15th May.29th of May.https://lists.onap.org/pipermail/onap-discuss/2018-May/009660.html
Jon Taylor and Geora Barsky (assisting) and Sharon Chisholm (assisting) will presenting the proposed architecture along with myself.
Team members
In addition to the current logging team members
...
The following additional team members - the majority of which currently work/have-worked on SDNC like the clustering and federation work in ONAP will also support the scope change work.
...
Geora Barsky (sniro)
Mohammadreza PasandidehNeha Jain
Phillip Leigh
Vitaly Lavrusevich
Stella StoykovaStela Stoykova
With additional ongoing support/work from the OOM project
Plan
Cover off all the items identified in the scope change epic, including overlap with other projects, what we require from other projects and what other projects may require from us in terms of API.
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
The POMBA microservices will require their own sub repo - ideally per/container as a sub-project of logging. See https://gerrit.onap.org/r/#/admin/projects/logging-analytics,branches - raising LF ticket