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 hourly healthcheck (CD deployment) - http://kibana.onap.info:5601/app/kibana#/dashboard/AWAtvpS63NTXK5mX2kuS
      • Status: RED Michael O'Brien will need to address what looks like some outages in the tool
      • Something broken? Not giving update updates. Still broken as of last night.
    • General Status
      • Casablanca
        • Bugs
        • in progress
        • to be verified/closed:
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-
        • 857
          • OOM work – this will get merged into master – Dublin. We'll have to flag this to cherry pick into Casablanca Maintenance. (Added 
            Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-896
            )
        • Let's move fix to just Dublin and get rid of 896.
          • Changed to Dublin during meeting.
          • 805

            • Pinged Brian (again) for closure
      • Dublin
        • Stories in progress (to be delivered this week)
        • Bugs to be verified
        • :
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-
        • 805
          • Pinged Brian for closure
        • Bugs closed off:
        Dublin
          • 404
          Stories in progress:
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-404517
        • 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-426
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-779
        • Bugs in progress:
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-
        • 807
          • 852
          • Jira
            serverONAP JIRA
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-
        • 808
          • 879
            • Waiting for OOM merge
        • Bugs to be verified:
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-
        • 852
          • 803
          • Jira
            serverONAP JIRA
        • columns
        • key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
          • serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-
        • 879Bugs to be verified:
          • 807
          • Jira
            serverONAP JIRA
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-
        • 891
          • 808
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-
        • 803
          • 814
          • Jira
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            keyLOG-
        • 814
          • 857
  • Technical Discussion
    • Integration Team discussion
      • When we know the Openstack/network discovery info will work in ONAP, we shall reach out to Brian and the Integration team again.
        • The logs are broken, which makes it harder to debug and test.
      • How to test L2 Fabric
        • Some of that information may be not be available in ONAP
        • But the resources will be, even if for other reason.
    • Consider demo schedules
      • David Stangl has identified some timeframes where demos would probably make sense based on current forecast
        • Data Dictionary - end of Dec?
          • Technically that would be Dec 20.
          • Also demo network discovery of VM info using native code as part of end to end flow.
        • L2 Network AVPs - beginning of Feb?
          • Set a more specific date in January
        • Network Audit - end of Feb?
  • Making the PTL Happy
    • ONAP Casablanca Maintenance?
      • Consider porting bugs into maintenance (add label for candidates)
        • Only high and highest ones. Ones that impact other components, prevent POMBA from launching or the audit to even start.
    • Dublin
      • Should look at milestones and ensure we are in good shape.
        • Feature commitment Jan 17
        • Functionality freeze Feb 14
        • API freeze is March 14th.