Agenda
- 8:00am Eastern
- Status and Stucks
- Technical Discussion
- Making the PTL Happy
- 8:30am Eastern
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:
- LOG-778 - Getting issue details... STATUS
- SDNC-475 - Getting issue details... STATUS : For network resource only and should be split into Network Discovery and ND context builder.
- LOG-779 - Getting issue details... STATUS
- LOG-957 - Getting issue details... STATUS
- SDNC-637 - Getting issue details... STATUS
- LOG-958 - Getting issue details... STATUS
- LOG-404 - Getting issue details... STATUS
- Stories closed since last meeting:
- LOG-763 - Getting issue details... STATUS
- 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:
- Bugs closed off since last meeting:
- Dublin
- Technical Discussion
- Consider demo schedules
- J. Ram Balasubramanian will forecast demos as development progresses
Data Dictionary & Network Discovery- Dec 20Done
- L2 Network data (Today!)
- See slides
- Additional enhancement - March 21st
- additional resources and rules
- potentially other enhancements
- J. Ram Balasubramanian will forecast demos as development progresses
- 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.
- OOM submissions
- Steps to ensure PODS are healthy
- Before checkins should do a local Robot health check. If this is not clear, documentation needs to be updated.
- action Yong
- Before checkins should do a local Robot health check. If this is not clear, documentation needs to be updated.
- This was guidance from PTL and also good practice.
- Steps to ensure PODS are healthy
- Consider demo schedules
- Making the PTL Happy
- Casablanca
- Release notes being prepared.
- Still seems to be open.
- Data router version was upped. So, POMBA needed to update its version. This was integrated.
- There was a bug and the A&AI team fixed it. Integration team tested the fix, but perhaps did not test POMBA
- J. Ram will quickly test.
- Michael O. did test already that the POD comes up and passes health check.
- There was a bug and the A&AI team fixed it. Integration team tested the fix, but perhaps did not test POMBA
- Release notes being prepared.
- Dublin
- Should look at milestones and ensure we are in good shape.
- Feature commitment Jan 17 → pushed one week. Jan 24th. (M1)
- Prudence is supporting Michael for this activity.
https://wiki.onap.org/display/DW/Logging+Dublin+M1+Release+Planning
- Functionality freeze Feb 21
- Any new APIs are supposed have draft definition, but this doesn't really apply to us
- Michael has filled in the templates for POMBA. Should be good to go.
- API freeze is March 14th (or has this slipped?)
- Feature commitment Jan 17 → pushed one week. Jan 24th. (M1)
- Should look at milestones and ensure we are in good shape.
- Casablanca
- Demo
- Slides
- Dublin Test lab configuration
- POMBA audit is trigger
- Currently via service instance id, model id and model invariant id
- This enables some good validation
- This information can be hard to find in cases. An audit trigger based on information a more typical user has should be considered
- Both could be supported
- Brian thinks he previously raised something on this. If not, Sharon will add something to the backlog to track.
- LOG-983 - Getting issue details... STATUS
- Currently via service instance id, model id and model invariant id
- The demo data is roughly based on vfw, but modified to ensure we have violations to show
- Integration team can create their own rules. The steps are defined
- Validation Service
- Action Yong to improve page or create a new one with better steps.
- Openstack keystone needs to be version 3, or shortly no one will be able to use it
- Network Discovery is using v3, so we are ok
- Currently Openstack coordinates are part of the helm chart. There is a way the URL information can be discovered
- Action Sharon to add something to the backlog for this
- SDNC-663 - Getting issue details... STATUS
- Action Sharon to add something to the backlog for this
- Openstack passwords are obfuscated.
- Ideally, it would be good to network discover using meta-data
- This information gets associated to the VM
- Openstack does support filtering on field values. Depending on how the meta data is stored in openstack, this would be possible to implement.
- Currently network discovery is triggered out resource type and id.
- There is a heatstack to metdata association that is critical
- More analysis of this is required.