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 hourly healthcheck (CD deployment) - http://kibana.onap.info:5601/app/kibana#/dashboard/AWAtvpS63NTXK5mX2kuS
    

  • General Status

    • Dublin
      
      • Tasks to be closed off (just a technicality):
      • Stories in progress: All 3 of them will be delivered by Feb-08.
      • Stories to be formally verified before closure:

        • Jira Legacy
          server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-778

        • Jira Legacy
          server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-763

        • Jira Legacy
          server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key SDNC-475

          : For network resource only and should be split into Network Discovery and ND context builder.

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-779

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-404

      • Stories closed since last meeting:

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-768

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-765

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-762

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-938

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-937

        • Jira Legacy
          server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-764

      • 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 columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-967

        • Jira Legacy
          server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-966

        • Jira Legacy
          server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-965

      • Bugs in progress:
        

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-852

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-916

      • Bugs to be verified:
        

        • Jira Legacy
          showSummary true server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-807

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-803

           (Verify in OOM fails, assigned back to design)

        • Jira Legacy
          server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-808

        • Jira Legacy
          server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-917

      • Bugs closed off since last meeting:
        
        
• Technical Discussion
  
  • Cross context builder dependencies, documented
    • POMBA Cross Data Source Dependencies
  • Note we need to be careful about breaking POMBA when in the middle of incremental updates, where OOM isn't yet done.
    • Pulling OOM back into the project will fix this. This is currently not planned, and requires resources from OOM project to do this, so defer.
    • both master and any MR

    • Jira Legacy
      server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-950

    • Sharon to create task for this for El Alto backlog.

    • Jira Legacy
      server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-971

  • Organizing Models and Swaggers between releases
    • Summary table
      • POMBA Releases
        • Note technically there was Swagger for the network discovery API in Casablanca, but it could not be used out of the box and has changed so much, we decided to remove it.
    • Basic navigation should take us to current. Need to verify this
  • Consider demo schedules
    • J. Ram Balasubramanian will forecast demos as development progresses
      • Data Dictionary & Network Discovery-  Dec 20
        
        • Done
      • L2 Network data
        
        • Let's demo with some rules.
        • If we want validation run on new data, then Feb 21st makes more sense
      •  Additional enhancement - March 21st
  • Should ping the automation team on POMBA usage
    • Chesla to ping Brian.
• Making the PTL Happy
  
  • Dublin
    • Should look at milestones and ensure we are in good shape.
      
      • Feature commitment Jan 17 → pushed one week. Jan 24th. (M1)
        
        • Prudence is supporting Michael for this activity.

        • https://wiki.onap.org/display/DW/Logging+Dublin+Deliverables+for+Planning+Milestone+Checklist+Template

        • https://wiki.onap.org/display/DW/Logging+Dublin+M1+Release+Planning

      • Functionality freeze Feb 14
        • Not sure if this was impacted by M1 slip - nope - still the 14th
      • API freeze is March 14th.