Page Comparison

...

Status and Stucks
- Current POMBA Dublin Stories (Logging Project) -
  - Dublin Pomba Stories
- Current Code Inspections
  - https://gerrit.onap.org/r/#/q/status:open+pomba
- POMBA 6 hour healthcheck (full 200G CD deployment) - http://kibana.onap.info:5601/app/kibana#/dashboard/AWAtvpS63NTXK5mX2kuS
- General Status
  - Dublin
    - Stories in progress:
      - N/A (Not working on any formal stories at this point)
    - Stories to be formally verified before closure:
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-779
        (Waiting on a few bugs to close)
    - Stories closed since last meeting:
      - N/A
    - New content
      - Added 6 new health checks for POMBA, and 1 more in progress
    - 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:
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-1034
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-1030
    - Bugs in progress:
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-1017
    - Bugs to be verified:
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-1024
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-1021
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-1018
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-1030
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-1015
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-967
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-975
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-712
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-976
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-658
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-823
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-969
    - Bugs closed off since last meeting:
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-798
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-988
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-808
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-1013
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-916
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-688
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-657
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-656
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-803
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-1014
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-849
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-1022
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-1025
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
      - additional resources and rules
      - potentially other enhancements
      - We shall do in Logging Timeslot (11am eastern), Tuesday March 26th
        https://zoom.us/j/519971638
- 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://wiki.onap.org/display/DW/POMBA+Common+Model
      - This has been updated
    - common model mapping: https://wiki.onap.org/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
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-1026
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-1027
    - May also want to add a story to backlog for a story that uses data from SDC and validates other data against it, but treating SDC as a model
      - Also note that some of those could be written just as simple attribute comparisons, others are meta data.
      - Sharon to raise story.
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-1028
- - - All demos are complete. Thanks everyone!
Let Prudence know when we are ready to create artifacts for POMBA release (target end of month)
- Do we need a task?
- Norm is in the process of releasing the common model itself. Then will look at manifest update.
- Process
  - Request done by PTL
  - If there is order (model, other stuff, etc)
  - move from snapshot to .version
  - Then ask Linux foundation to formally release it
- Include Prudence in any emails.
- What timeline?
  - We will be code freeze end of day.
  - Modelleing changes are done.
  - Not sure exact process on how to release Pomba, or release later as part of Dublin
  - If team ready, do release now. Not expecting too much work after Friday, so makes sense to do now.
  - Note health check work does not impact this based on where it lives.
- When ready to release, send email to Linux foundation.
How are our health checks?
- We have added health checks
- Missing from certain components (only on three containers now, and standard deployment runs 12 containers)
  - SDC CB
  - SDNC CM
  - Kabana
  - etc
- Three already supported, two added and in testing. Trying to get Kabana one. A couple (validation, data router), may prove to be challengingDoes A&AI have something for datarouter we can support? Maybeto most items
- Additional to track in backlog?
- Just have one more to add - validation.
- If it goes in, it will go in today.
- Test goes in first, then OOM. (ordering of check ins)
  - Small window when integration team may trip over the partial checkin.
  - less than a day.
Need to do a serious bug scrub and ensure we are not doing any last minute submissions.
- If we choose to not remaining bugs to next release now, that is OK.
- Unassigned the resources to bugs we are no working on.
Validation upgrade investigation
- Have determined this update is too risky/breaks Pomba/too much work
  - Schema versions at startup from A&AI
  - Jira Legacy
    server System Jira
    serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
    key AAI-2295
  - Too many changes
- We will still use Casablanca version of validation engine.
- Means extra work from when someone wants to take the data dictionary POC and productize it.
- Chesla, Yong, Tanya and ~~Anthony~~ to talk more offline to unsure problem is understood.
- Also need to ensure that no one accidentally picks up a new version and tries to use it with POMBA without doing the extra work.
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
  - Should look at milestones and ensure we are in good shape.
    - API freeze is March 14th
      - Michael is starting to put together M3 checklist.
      - POMBA is ok for M3, according to Michael O.
      - M3 happened and we passed.
- Note once we are complete the current set of work, it might make sense to roll the Pomba meeting back into the Logging meeting.
  - Today will be the last meeting in this timeslot.
  - Future discussions will be every seconds Tuesday at 11am Eastern in the Logging meeting

Versions Compared

Old Version 4

New Version Current

Key