Agenda

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

        • LOG-958: Attribute comparison rule: PNFClosed

        • LOG-957: Attribute comparison rule: networkClosed

        • SDNC-637: Netork Discovery - portsClosed

      • Stories to be formally verified before closure:

        • LOG-778: POMBA: SDNC Context Builder: pnfClosed

        • LOG-763: POMBA: A&AI Context Builder: networkClosed

        • SDNC-475: Netork Discovery - networkClosed: For network resource only and should be split into Network Discovery and ND context builder.

        • LOG-779: Rules Update for Attribute Comparison (SDNC)Closed

        • LOG-404: Post Orchestration Audit – Data Dictionary InterfaceClosed

      • Stories closed since last meeting:

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

        • LOG-976: POMBA Model and Mapping Inconsistencies: PNFClosed

        • LOG-975: POMBA Model and Mapping Inconsistencies: NetworkClosed

      • Bugs in progress:
        
        

        • LOG-852: POMBA: Some pods do not ship with filebeat Closed

        • LOG-967: POMBA: Do not consider model names to be instance names in auditClosed

        • LOG-966: dublin pomba-validation-service crashes on start - with staging integration manifest overrideClosed

        • LOG-916: POMBA: Validation service should not throw violation errors when a builder returns nullClosed

        • LOG-965: pomba-networkdiscovery crashes on startClosed

      • Bugs to be verified:
        
        

        • https://lf-onap.atlassian.net/browse/LOG-807

        • https://lf-onap.atlassian.net/browse/LOG-803 (Verify in OOM fails, assigned back to design)

        • https://lf-onap.atlassian.net/browse/LOG-808

        • https://lf-onap.atlassian.net/browse/LOG-981
          
          
          

      • Bugs closed off since last meeting:

        • https://lf-onap.atlassian.net/browse/LOG-933

        • https://lf-onap.atlassian.net/browse/LOG-893

        • https://lf-onap.atlassian.net/browse/LOG-881

        • https://lf-onap.atlassian.net/browse/LOG-917

        • https://lf-onap.atlassian.net/browse/LOG-931

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

        • See slides

      •  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 practice.

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

  • 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://lf-onap.atlassian.net/wiki/display/DW/Logging+Dublin+Deliverables+for+Planning+Milestone+Checklist+Template

        • https://lf-onap.atlassian.net/wiki/display/DW/Logging+Dublin+M1+Release+Planning

      • Functionality freeze Feb 21

        • 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

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

        • https://lf-onap.atlassian.net/browse/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

      • https://lf-onap.atlassian.net/browse/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.