...

• 8:00am Eastern
  
  • Status and Stucks
  • Technical Discussion
  • Making the PTL Happy
• 8:30am Eastern
  
  • Demo 2
    • POMBA Demo_onap_dublin_2.pptx

Notes

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

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

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

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

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

      • Stories closed 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-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 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-995

          • Team focusing effort here. Will follow up with A&AI team for help

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

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

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

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

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

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

        • 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
          key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution server System Jira columns 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-966807

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

           (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-965

        Bugs to be verified:
        

        • 808

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

          981

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

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

        Bugs closed off since last meeting:

        • 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 (Today!Feb 21)
        • See slidesvideo available
      •  Additional enhancement - March 21st
        • additional resources and rules
        • potentially other enhancements
  • 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.
  • OOM submissions
    
    • Steps to ensure PODS are healthy
      • Before checkins should do a local Robot health check. If this is not clear, documentation needs to be updated.
        • action Yong
    • This was guidance from PTL and also good practiceBugs raised; Issues fixed.
    • Chesla to review mapping and provide feedback
      
      • common model: https://lf-onap.atlassian.net/wiki/display/DW/POMBA+Common+Model
        • This is out of date.
      • common model mapping: https://lf-onap.atlassian.net/wiki/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.
  • 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.
  • 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 Legacy
            server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-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 Legacy
      server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-966

    • Should look at milestones and ensure we are in good shape.
      
  • Slides
  • Dublin Test lab configuration
  • POMBA audit is trigger
    • Currently via service instance id, model id and model invariant id
      • This enables some good validation
    • This information can be hard to find in cases.  An audit trigger based on information a more typical user has should be considered
      • Both could be supported
      • Brian thinks he previously raised something on this. If not, Sharon will add something to the backlog to track.

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

  • The demo data is roughly based on vfw, but modified to ensure we have violations to show
  • Integration team can create their own rules. The steps are defined
    
    • Validation Service
    • Action Yong to improve page or create a new one with better steps.
  • Openstack keystone needs to be version 3, or shortly no one will be able to use it
    
    • Network Discovery is using v3, so we are ok
  • Currently Openstack coordinates are part of the helm chart. There is a way the URL information can be discovered
    • Action Sharon to add something to the backlog for this

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

  • Openstack passwords are obfuscated.
  • Ideally, it would be good to network discover using meta-data
    • This information gets associated to the VM
    • Openstack does support filtering on field values. Depending on how the meta data is stored in openstack, this would be possible to implement.
      • Currently network discovery is triggered out resource type and id.
    • There is a heatstack to metdata association that is critical
    • More analysis of this is required
      • Feature commitment Jan 17 → pushed one week. Jan 24th. (M1)
        
        • Prudence is supporting Michael for this activity.
        • we are at M2 not M1
        • Logging Dublin M2 Deliverables for Functionality Freeze Milestone Checklist

        • https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Logging+Dublin+Deliverables+for+Planning+Milestone+Checklist+Template

        • https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Logging+Dublin+M1+Release+Planning

      • Functionality freeze Feb 21/28
        • Any new APIs are supposed have draft definition, but this doesn't really apply to us
        • Michael has filled in the templates for POMBA. Should be good to go.
      • API freeze is March 14th (or has this slipped?)
    Demo
    • • • • Michael is starting to put together M3 checklist.