2019-03-14 (March 14)
- J. Ram Balasubramanian
- Sharon Chisholm
Agenda
8:00am Eastern
Status and Stucks
Technical Discussion
Making the PTL Happy
Notes
Status and Stucks
Current POMBA Dublin Stories (Logging Project) -
Current Code Inspections
POMBA 6 hour healthcheck (full 200G CD deployment) - http://kibana.onap.info:5601/app/kibana#/dashboard/AWAtvpS63NTXK5mX2kuS
General Status
Dublin
Stories in progress:
Stories to be formally verified before closure:
Stories closed since last meeting:
https://lf-onap.atlassian.net/browse/SDNC-475For network resource only and should be split into Network Discovery and ND context builder.
Bugs to enter:
Latest security scan results show ~9 medium issues that should be recorded (but aren't severe enough to merit immediate work).
Bugs entered in last week:
Bugs in progress:
Bugs to be verified:
https://lf-onap.atlassian.net/browse/LOG-803 (Verify in OOM fails, assigned back to design)
Bugs closed off since last meeting:
Technical Discussion
Consider demo schedules
@J. Ram Balasubramanian will forecast demos as development progresses
Data Dictionary & Network Discovery- Dec 20
Done
L2 Network data (Feb 21)
video available
Additional enhancement - March 21st
additional resources and rules
potentially other enhancements
We shall do in Logging Timeslot (11am eastern), Tuesday March 26th
Note we have discovered a number of discrepancies between the model definition in the wiki and the code. We are now raising bugs on specific issues found and will resolve as appropriate.
Bugs raised; Issues fixed. Found a few more issues yesterday, which are being worked.
Chesla to review mapping and provide feedback
common model: https://lf-onap.atlassian.net/wiki/display/DW/POMBA+Common+Model
This has been updated
common model mapping: https://lf-onap.atlassian.net/wiki/display/DW/Dublin+Common+Model+Mapping
Reflects what has been implemented after some updates
Chesla has reviewed SDC and we are tracking issues in Jira
She has not looked at the rest of it, and to provide extra validation beyond what has already been done requires getting real data, which she may have time for.
Some concerns over VNF type. If it not used correctly in practice, but so long as it is being used consistently
There might be a late change to the PNF model
We might get impacted
Will they be backwards compatible? Ie, versioned
Sharon to follow up Jimmy.
The plan of record in Dublin has the key of the PNF object changing from pnf-name to pnf-id. This means a migration in systems that use the PNF object.
There are still discussions underway to reduce impact to clients, and we don’t have the official path forward on how this works (and there are also discussions about NOT introducing a breaking change in the API). I think we’ll have a path forward next week, I’ll loop you in when I know which direction it’s going.
This would impact POMBA if we do get by id, this will impact us. If we are using a query string, we would be fine.
Action J.Ram to confirm which we use.
Given the way we were using this field field in the GET, we are fine.
we were using PNF ID as the index already, assuming PNF-name is the same as PNF-id
GET path/PNF/<pnf-name> but we pass in GET path/PNF/<pnf-id>
How are our health checks
Missing from certain components (only on three containers now, and standard deployment runs 12 containers)
SDC CB
SDNC CM
Kabana
etc
We may want to address this as part of our bug scrub. Perhaps after the 'high' priority bugs? Or during it.
Making the PTL Happy
Casablanca
Dublin
From PTL
If you have concerns bring them to the TSC or the PTL meet - as I have a hard time convincing the TSC about issues without more developer voices
Also for committer promotion - the template needs more data - 90/180/360 day commits, jira, discuss groups, wiki, reviewed commits, meeting attendance - as one of the committers for integration was rejected last week - any developer listed for committer promotion must attend the TSC 9-1030 to promote themselves and answer questions
details of what people have contributed, Jira, etc
Action Sharon: Send information.
Action Yong : follow up to get information
Will discuss further offline
(+) 20190228: manifest confusion being addressed in TSC 2019-02-28 for https://lf-onap.atlassian.net/browse/LOG-966
This is related to integration testing using predictable environments
No resolution yet, but it is being discussed.
Closed
Should look at milestones and ensure we are in good shape.
API freeze is March 14th (or has this slipped?)
Michael is starting to put together M3 checklist.
POMBA is ok for M3, according to Michael O.