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

  • General Status

    • Dublin
      
      • Stories in progress: 

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

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

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

      • Stories to be formally verified before closure:

        • 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-957

        • 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-766

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

        • 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 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 SDNC-637

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

      • 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 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-1014

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

      • Bugs in progress:
        

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

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

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

      • Bugs to be verified:

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

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

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

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

      • Bugs closed off since last meeting:
        

        • 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-999

        • 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-998

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

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

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

• 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 We shall 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.
        • 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 is out of date.has been updated
      • common model mapping: https://wiki.onap.org/display/DW/Dublin+Common+Model+Mapping
        • Reflects what has been implemented after some updates
  • Not all containers have health check enabled
    • The gaps should be tracked. Action J.Ram.
      • Updated.  Only 3 microservices currently have healthcheck on them.  Updated on 

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

  • 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.
    • Status: Closed
• 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.

    • The plan of record in Dublin has the key of the PNF object changing from pnf-name to pnf-id.  This means a migration in systems that use the PNF object.

    • There are still discussions underway to reduce impact to clients, and we don’t have the official path forward on how this works (and there are also discussions about NOT introducing a breaking change in the API).  I think we’ll have a path forward next week, I’ll loop you in when I know which direction it’s going.

    • This would impact POMBA if we do get by id, this will impact us. If we are using a query string, we would be fine.
    • Action J.Ram to confirm which we use.
• 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 Legacy
      server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-2090

    • Closed
  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
    • 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
      • details of what people have contributed, Jira, etc
      • Action Sharon: Send information. .
        
        • https://onap.biterg.io/app/kibana#/dashboard/Overview?_g=h@44136fa&_a=h@3c6f7fd
      • Action Yong : follow up to get information
    • (+) 20190228: manifest confusion being addressed in TSC 2019-02-28 for 

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

      • This is related to integration testing using predictable environments
      • No resolution yet, but it is being discussed.
  • Should look at milestones and ensure we are in good shape.
    
    • API freeze is March 14th (or has this slipped?)
      • Michael is starting to put together M3 checklist.
      • POMBA is ok for M3, according to Michael O.