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: 
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-959
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-766
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-767
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-551
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-665
        • Stories to be formally verified before closure:
          • Jira
            serverONAP JIRA
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-778
          • Jira
            serverONAP JIRA
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keySDNC-475
            : For network resource only and should be split into Network Discovery and ND context builder.
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-779
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-957
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keySDNC-637
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-958
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-404
        • Stories closed since last meeting:
          • Jira
            serverONAP JIRA
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-763
        • 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
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-996
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-995
            • Team focusing effort here. Will follow up with A&AI team for help
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-994
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-993
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-988
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-987
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-986
        • Bugs in progress:
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-852
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-975
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-976
          • Jira
            serverONAP JIRA
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-967
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-916
        • Bugs to be verified:
          • Jira
            showSummarytrue
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-807
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-803
             (Verify in OOM fails, assigned back to design)
          • Jira
            serverONAP JIRA
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-808
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-981
        • Bugs closed off since last meeting:
          • Jira
            serverONAP JIRA
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-965
          • Jira
            serverONAP JIRA
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-966


  • 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
          • Or do Tuesday at 11 in logging meeting to get more people?
            • send email to advertise
            • Sharon to follow up with Michael O.
            • Note Logging meeting only happens every two weeks, although the zoom is available.
    • 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.
    • Not all containers have health check enabled
      • The gaps should be tracked. Action J.Ram.
    • Validation Service and adding rules
      • Action Yong to improve page or create a new one with better steps.
      • Work has been done and Brian has seen
      • Still looking for feedback from various folks and will update as appropriate.
      • Step by step now available.Status: Closed
    • Issues raised in integration environment, we don't know how they have deployed. Need to figure out how to better work with integration team.
      • This relates to the POD issues, where it was a problem with their manifest.
      • We have no visibility of their current setup.
      • PTLs will discuss with integration team to decide best path.
  • 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.
  • 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.
          • J. Ram will confirm we did an audit.
            • Updated on 
              Jira
              serverONAP JIRA
              serverId425b2b0a-557c-3c0c-b515-579789cceedb
              keyAAI-2090
    • Dublin
      • 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
      • (+) 20190228: manifest confusion being addressed in TSC 2019-02-28 for 
        Jira
        serverONAP JIRA
        serverId425b2b0a-557c-3c0c-b515-579789cceedb
        keyLOG-966
      • Should look at milestones and ensure we are in good shape.