Agenda

  • Status and Stucks
  • Technical Discussion
  • Making the PTL Happy

Notes

  • Status and Stucks

    • Current POMBA Casablanca Stories (Logging Project) -

    • Current Code Inspections

    • POMBA hourly healthcheck (CD deployment) - http://kibana.onap.info:5601/app/kibana#/dashboard/AWAtvpS63NTXK5mX2kuS
    • General Status
      • Casablanca
        • Wiki updates completed
        • Resource limits/chart issue has been fixed.
        • Pairwise testing table has been updated
        • So, we are basically done.
      • Dublin
        • SDNC Context Builder w/ Generic API merged
          • OOM branch not available until ~November
          • Jobs enabled
        • SDNC Context Builder w/ selection + VNF API mostly complete (working on VNF API and need to do designer testing)
          • This is the 'mapper' plus able to support VNF API
        • SDNC Context builder has Dublin branch, others don't
        • OOM, etc won't have branches until November. Means we can't close stories.
          • Might be able to submit and have disabled in OOM. That would be in the Casablanca branch.
          • Everything non-OOM, we should be able to cut branches earlier as we have control.
            • OK, for everything but new microservices and rule updates.
        • Started offline discussion on model updates to support Dublin content.  Will review with team shortly.
    • Engage Integration Team now?
      • Sharon sent email to Brian and Helen.
      • Could have replied to Robot email chain as well. 
      • In addition, we ourselves can run POMBA audits based on data in integration lab, in our own instances.
        • Chesla and others will try this.
    • Sharon availability (start a 'working holiday' Oct 24-Nov 7). Someone may need to cover to cover this meeting.  David or Michael.
  • Technical Discussion
    • SDNC Mapping
      • Use two third party frameworks
        • Drools
          • Decide based on parameters from A&AI, subscription type will be used. Decide between the two ones
          • Implementations can customize this decision
          • Configuration file outside of core code image. Specify what parameters to use to decide what APIs to call
          • Generic resources API (vFW), VNF API otherwise.
        • Camel routing
          • Implement specific caller to make call and process results.
          • Two of these
          • Java beans
          • Specify in config file which java bean to call.
        • Need to define instructions on how to inject additional java beans into solution
          • Track as new story or existing? It is just documentation.
          • Needs to be possible. Doesn't need to be trivial.
        • Good to see details of mappings.
        • Longer term, could this information be driven off the model? Model invariant id?
          • Or are we just converging on a single API, so not necessary. This is a stop gap.
          • Also controllers themselves are evolving.
    • If model updates are ready to discuss next week, let's do that.
    • May also be interesting to get an ONAP common model update from Chesla
      • TOSCA task force. How to use end to end through lifecycle through project
        • May impact what sort of rules we can source from the model
        • Will take time.
      • Two internal data model
        • VFC
        • SO, SDNC, etc
        • Trying to bring it together.
  • Making the PTL Happy