Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Record the Meeting!! (issue with Zoom recording)
  • Introductions
  • Contribution Manoj Nair (Netcracker)
    • Casablanca Proposal, see: link
    • Extend ExtAPI scope to include "southbound APIs" to External SDN Controller, Edge Orchestrators, Domain Orchestrators, Domain Controllers (also Legacy OSS)
    • Need to explore relationship with MEF Presto NRP based on ONF TAPI
    • Continue discussion next week
  • Contribution Jack Pugaczewski (CenturyLink)
    • Casablanca Proposal: see: <link>
    • API Logging possibly using a Log Processor like Apache Nifi
    • Allows temporal flow analysis of API calls
    • Looking for interest in contributing to this activity
  • Next week: ONF TAPI discussion see: <link>
  • Update on code contribution Ludovic Robert
    • working Docker, performance, security, license info, risk management
    • Documentation: Updated release notes on Readthedocs
    • Amdocs bugs fixed
    • Need Pair-wise testing (in contact with Helen)
    • in two weeks TM Forum Two Demos on External API in Nice (including Sonata and Legato)
    • Need to push out OOM Healthcheck until May.
  • Interlude Update (Mehmet Toy)
    • Example Modify CIR for E-Access Service instantiated in a Partner Domain
    • Flows showing how Interlude works for the Elastic E-Access service
    • Potential Casablanca definition
  • Next Time: Discussion on relationship to MSB "External Gateway"; External API code to do mediation / translations
    • Cover registration, "visual range" of service as external 
  • Next Time: Continue Casablanca planning:
    • HOMEWORK: Which APIs have business impact; Put together PPT on proposed Casablanca API functionality.
    • Use Cases for Interlude; End to end flows 
    • Code to parse YAML from Service Catalog. Work with SDC on TOSCA toolset. Parse YAML within SDC once and create inputs once Service Definition is finalized.
    • Service Qualification / Servicability (pre-order) (is capacity and topology available supporting the specific set of service parameters; do policies permit instantiation, mapping of Service requirements to capabilities provided by the platform; checking against of service constraints and characteristics from Service catalog (or via catalog exposure to BSS), Service compatibility with other services instantiated within the customer's service group )
    • License Accounting
    • A&AI Customer (Possible removal of customer info from ONAP)
    • Enhancements for complex input types (transition from name-value pair to JSON structures-blob ) (e.g., MEF Bandwidth Profiles, L2 Connectivity as a Use Case)
  • Next Time:

...