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
    • General Status
      • Casablanca (Maintenance)
        • Nothing
      • Dublin
        • Tasks to be closed off (just a technicality):
        • Stories in progress: All 3 of them will be delivered by Feb-08.
          • Jira Legacy
            serverSystem Jira
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-778
          • Jira Legacy
            serverSystem Jira
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-763
          • Jira Legacy
            serverSystem Jira
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keySDNC-475
            : For network resource only and should be split into Network Discovery and ND context builder.

        • Stories to be formally verified before closure:
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-768
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-765
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-762
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-938
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-937
          • Jira Legacy
            serverSystem Jira
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-764
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-779
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-404
        • 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:
          • none
        • Bugs in progress:
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-852
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-803
             (Verify in OOM fails, assigned back to design)
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-916
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-917
             (high)
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-935
             (high)
        • Bugs to be verified:
          • Jira Legacy
            showSummarytrue
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-807
          • 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-875
        • Bugs closed off since last meeting:
          • Jira Legacy
            serverSystem Jira
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-821
          • Jira Legacy
            serverSystem Jira
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-804
          • Jira Legacy
            serverSystem Jira
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-713
          • Jira Legacy
            serverSystem Jira
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-714
          • Jira Legacy
            serverSystem Jira
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-809


  • Technical Discussion
    • Note OOM changes should be done when manifest changes are done. Should not wait for integration team to do this work for us.
      • We will have to do this for Dublin in two months.
        • Create task to track J. Ram Balasubramanian
          • Done.
        • Docker version update
        • Moving from snapshot to proper release is part of workflow.
          • If POMBA thinks they will have no more changes, they can do this earlier
        • This is covered. We can stop tracking this here.
    • Organizing Models and Swaggers between releases
      • Basic navigation should take us to current
      • It should also be possible to get Casablanca information
      • Wiki needs some reorganization
    • Consider demo schedules
      • J. Ram Balasubramanian will forecast demos as development progresses
        • Data Dictionary & Network Discovery-  Dec 20
          • Done
        • L2 Network data - beginning of Feb?
          • Set a more specific date in January
          • Let's demo with some rules. So probably Feb 14th or 21st.
        •  Additional enhancement - March 21st
    • Should ping the automation team on POMBA usage
      • Chesla to ping Brian.
  • Making the PTL Happy