OOF 2018-02-19 Meeting Notes

Date

19 Feb 2018 using alternative temporary zoom ID: https://zoom.us/j/245712981 (expires after the meeting)

Clean up the TODO's from last week – most are still pending (will update status there)
Next job to run merge job will upload to nexus (for optf-osdf; same for optf-has)
- Dileep to expand
Group to review functional tests this meeting
Sonar jobs for oof/osdf and oof/has
- These are still pending for Python
- osdf runs coverage by default, but has does not

Item	Who	Notes

Unit tests	Dileep	Whoever is working on the tests should communicate through JIRA to prevent duplication. Should invite Ikram into these calls. Offline call for deep dive.
Functional tests	Yoram to provide feedback	Flows that should be successful and those that should fail. We want to return invalid request type cases. Need to have performance measures. We want optimizer to ignore failure and still continue without losing its state: continuous input data, optimizer should function in the presence of noisy data – this maybe beyond scope of R2 (for usecases such as SON)? break it down into validation checks (e.g. incomplete data) versus noise in timeseries data (large anamolies to be ignored): first case is in scope for R2, second one is not in scope for R2
Platform maturity	Ramki	Sonar provides static code analysis – we can wait to see the outcome from sonar job results and plan accordingly. We need the ONAP system to spin up the whole system in one hour (with readiness check). Having a clean separation between being ready and announcing it. Should we do roll this up into functional tests?
HPA	Dileep	How will A&AI schema relates to HPA.

@Split tests into sunny day and rainy day cases... Ramki and Shankar to work on the JIRAs. Yoram can expand on this after three weeks.

Contributor	What did you do last week?	Are there any impediments in your way?

Dileep	Worked on unit/functional testing with OOF-HAS	Had some trouble with Mocking MUSIC. See notes below.