Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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: 
          • N/A  (Not working on any formal stories at this point)
        • Stories to be formally verified before closure:
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-404
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-779
             (Waiting on a few bugs to close)
        • Stories closed since last meeting:
          • N/A
        • 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
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-1024
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-1022
        • Bugs in progress:
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-1018
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-1021
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-1017
        • Bugs to be verified:
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-712
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-658
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-1013
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-987
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-803
             (Verify in OOM fails, assigned back to design)
          • Jira Legacy
            serverSystem Jira
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-808
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-988
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-975
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-976
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-798
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-967
        • Bugs closed off since last meeting:
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-850
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-849
          • Jira Legacy
            serverSystem Jira
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-1001
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-1014
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-700


  • 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
    • 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
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-1026
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-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.
  • 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.
  • 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 itThree already supported, two added and in testing. Trying to get Kabana one. A couple (validation, data router), may prove to be challenging
      • Does A&AI have something for datarouter we can support?  Maybe.
  • 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.