Versions Compared

Key

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

...

  • Short Description:  CNTT reference implementation and verification in OPNFV

  • Detailed Description:
    • We will use this session to drive the detailed discussion of CNTT activities in OPNFV. Major topics can include as follows (you are also welcome to add more topics)
      • CNTT progress updates, especially focusing on OPNFV related activities
      • High level discussion on OPNFV planning to engage in CNTT effort and reveal CNTT requirements
      • OPNFV feature projects planning for support of CNTT reference models and architecture
      • OPNFV installer projects gap analysis (whether the current projects will support the reference architecture in a good way?)
      • OPNFV testing project gap analysis (whether the current test cases and framework will support the verification requirement from CNTT?)
      • Next step
  • Topic Leader: Fu Qiao, 
  • Estimated Audience Size (15-30):
  • Interested In Attending:


--------------------------------------------------------------------------------

  • Short Description:  OPNFV Closed Loop Automation Working Group

  • Detailed Description:
    • This sessions would help members from OPNFV closed loop automation working group to collaborate on following:
      • What's working good so far
      • Topics and areas of interest that could be included as part of WG
      • Intersection with other projects like ONAP, etc.
      • On going demos and future demos of interest
      • TBA
  • Topic Leader: Sunku Ranganath, ... 
  • Estimated Audience Size : 5-10
  • Interested In Attending: please add your names (& emails) to help build the schedule

--------------------------------------------------------------------------------

  • Short Description:  Test frameworks and tools for CNTT

  • Detailed Description: This is continuation of discussion started in CNTT F2F meeting in Paris on OPNFV test framework strategy for CNTT reference implementations and compliance program.
    • See related thread and this point made by Georg Kunz... we need a structured way of integrating, maintaining and running specific test cases across test tools. It must be simple to call specific test cases across all OPNFV test tools. This means that ideally the OPNFV test tools agree on a common way to do this. Potential ways:
      1. All tools integrate in Xtesting
      2. All tools agree on a common API callable from some other tool
      3. Something else?
  • Topic Leader: Trevor Cooper
  • Estimated Audience Size: 5-10
  • Interested In Attending:

--------------------------------------------------------------------------------

...

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

  • Short Description:  CNI Round Table

  • Detailed Description:
    • Round Table discussion about CNI (mainly for networking plumbing).
    • Mainly focus on telco/NFV-ish area, but other areas also welcome.
    • For example:
      • Sharing experiments with CNI (e.g. multus or CNI reference plugins) and discuss missing requirements
      • What are the needs of Cloud Native VNF-s from networking?
      • Which CNI-s are fulfilling these requirements?
      • What is different and what is similar about the different CNI-s for telco workloads?
  • Topic Leader: Tomofumi Hayashi (tohayash@redhat.com), Levente Kale, Gergely Csatari 
  • Estimated Audience Size: 1-15
  • Interested In Attending:

--------------------------------------------------------------------------------

...

  • Short Description:  CNTT and CNCF TUG Common API Framework

  • Detailed Description: In this session, I would like to invite people from the CNTT group and CNCF TUG group to come together to work on a Common API Framework so that we can have a common North and southbound APIs for both VNF/CNF vendors/users and NFVI vendors/users. The intent of this session will be have an open discussion to drive a consensus so that we can align on the API framework that would work for both VNFs as well CNFs (cloud native) so that we can implement the reference architecture as specified by CNTT group. This should allow the transition of VNFs to CNFs smooth. Additionally, this will help build validation framework that works for all types of workloads.
  • Topic LeaderSukhdev Kapur(sukhdev@juniper.net)
  • Estimated Audience Size (15-50):
  • Interested In Attending: If you are interested in this discussion and would like to participate in it, please add your name and email here (one name/email per line please). We'll use this information when building the schedule so that we minimize overbooking people where possible.

--------------------------------------------------------------------------------

...

  • Short Description:  Improving ONAP interoperability & Adoption with API Fabric

  • Detailed Description: This sessions will present a solution to simplify the consumption of APIs in ONAP and to expose operational APIs while improving interoperability with 3rd party systems. We will present how the API Fabric provides a simplified abstraction layer, exposing standard APIs, which improves the usability for end users and speeds up the productization of ONAP.

    The API fabric provides capabilities for onboarding new APIs, with plugins to convert to standard APIs, and provides complete API lifecycle management including subscription and transaction control & monitoring. The exposed manageable façade layer simplifies ONAP’s consumable interface for operations, application development or business level monitoring, avoiding deep integration with individual ONAP components.

  • Topic Leader: Davide Cherubini , Manoj Nair  
  • Estimated Audience Size : 10-15
  • Interested In Attending: please add your names (& emails) to help build the schedule
  • David Perez Caparros
  • Shiby Parayil

--------------------------------------------------------------------------------

...

  • Short Description:  Blockchain based Telecom Solutions (Hyperledger Telecom SIG)

  • Detailed Description:
    • The Hyperledger Telecom Special Interest Group is focused on technical and business-level conversations about appropriate use cases for blockchain technology in the Telecom industry. In this session we  will show a new approach for Inter-Carrier Settlement and Service Level Agreement use cases on Hyperledger technology to make the process more efficient and cost effective for Telecom Operators.
  • Topic Leader: Vipin Rathi Sunay Zelawat
  • Estimated Audience Size : (10-20)
  • Interested In Attending: please add your names (& emails) to help build the schedule
  • Shiby Parayil

----------------------------------------------------------------------------------

...

  • Short Description:  A step towards validating ONAP Control Loops

  • Detailed Description: This is continuation of discussion started in DDF meeting in Sweden on ONAP Control loop validation.
    • As ONAP is currently implementing and improving the control loop framework (model driven control loops), we would like to propose a consistent validation of control loops by reusing existing mechanism, we would like to discuss the following topics :
    • try and validate control loops flow
      in an automated fashion, with the intention to serve multiple goals :
      - decouple control loop flows from instantiation flows in order to speed up validation.
      - lower the learning curve for people to understand control loops
      - identify quickly breaking changes that would hurt the control loop as a whole
      - create a framework to allow for proving control loop behavior
    • This session is an open discussion session 
  • Estimated Audience Size: 5-10
  • Interested In Attending:

---------------------------------------------------------------------------------

...

  • Short DescriptionVNF Testing standardiztion under TMF API

  • Detailed Description: TMF test API team and ONAP VNF Test Platfrom (VTP) team has found synergy between their API specification and investigated the mapping between these API. This would help in bringing the standardization in VNF testing in ONAP. As part of this discussion, following topics will be covered:

    • Need for the VNF testing standarization
    • Mapping between VTP API and TMF test API specs
    • Future of this TMF API alignment
  • Topic LeaderKanagaraj Manickam

  • Estimated Audience Size: 5-10
  • Interested In Attending:
  • Shiby Parayil


---------------------------------------------------------------------------------

...

  • Short Description: ONAP as a unified MEC-in-NFV Orchestrator

  • Detailed Description: In the latest ETSI MEC architecture specification, there is a generic reference architecture and a MEC-in-NFV variant. We would like to discuss the MEC-in-NFV variant and the possibility of ONAP serving as the combined orchestrator (NFVO MEAO). Also, given the rich functionality of various ONAP controllers, we would like to discuss how ONAP could possibly interface with both external MEPM-V components or alternatively subsume this functionality within ONAP. This is quite similar to how ONAP deals with VNFMs — they can be external or internal. There is no pre-planned agenda, and we would like to have an open discussion on this topic.

  • Topic LeaderSriram Rupanagunta

  • Estimated Audience Size: 5-10
  • Interested In Attending: Thoralf Czichy
  • Shiby Parayil

---------------------------------------------------------------------------------

...