Versions Compared

Key

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

...

...

Cross-Carrier 5G Slicing Roaming Use Case

...

  • Short Description:  Review & discuss changes to platform maturity (S3P) requirements for Guilin release
  • Detailed Description: The ONAP Platform Maturity level definitions and required levels have remained static for the past few releases.  In this session we will review feedback from the project teams (to be gathered prior to the session) & discuss what changes can be made to the requirements so that ONAP can improve its maturity posture in a way that projects can easily achieve.  Please join to have your voice heard.
  • Topic Leader: Jason Hunt
  • Estimated Audience Size (1-15 / 15-30 / 30-50 / >50): 30-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.

...

O-RAN / OSC rel A / ONAP joint PoC/PlugFest results and next steps 

...

  • Short Description:  The presentation will outline VNFC level reconfiguration problem and how it is mitigated today what makes ONAP not so ready for carrier-grade deployments
  • Detailed Description: Today in many of existing use cases there are performed anonymous reconfiguration and LCM actions on VNFC level by configuration on VNF level. This happens in example in vLB/vDNS ScaleOut or vFW Traffic Distribution use cases where specifically adapted VNF reconfiguration pattern is applied. This approach cannot be repeated on carrier-grade scale, with services instances having many vf-modules or many VNFC types or many LCM actions . In consequence, ONAP is not ready for carrier grade reconfiguration today as long as VNF does not have its internal LCM controller. This problem is a consequence of lack of support for VNFC level reconfigurations in the controllers and in SO. In this presentation on examples we will show how VNFC level configuration is hacked today and what are the potential solutions for that. The topic will be shown on examples and code from use cases realized in ONAP.
  • Topic Leader: Lukasz Rajewski Scott Blandford Marco Platania Ajay Mahimkar
  • Estimated Audience Size (15-30):
  • Interested In Attending:

...

ONAP and JIRA - Discussion of Best Practices and a Proposal for Improvement

...

  • Short Description:  Control Loop sub committee working session

  • Detailed Description: This working meeting will include Control Loop Roadmap, Frankfurt status updates as well as for the team to start vetting out requirements for the Guilin Release: https://wiki.onap.org/display/DW/Control+Loop+Sub+Committee+Guilin+Release+Planning
  • Topic Leader: Pamela Dragosh TBD
  • Estimated Audience Size (1-15 / 15-30 / 30-50 / >50): 1-15
  • 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.

...

HPA Pluggable in Multicloud

...

  • Short Description: Explain and demonstrate the improvements in the ONAP policy Framework being developed in Frankfurt
  • Detailed Description:  A number of improvements and enhancements such as better handling of PDPs, better TOSCA support, support for Self Service Control loops, and better monitoring and observability are being developed in the ONAP Policy Framework in Frankfurt. In this  session, we will describe the improvements and demonstrate early versions of enhanced functionality.
  • Topic Leader: Pamela Dragosh Liam Fallon Other Policy Framework project members.
  • Estimated Audience Size (1-15 / 15-30 / 30-50 / >50): 15-30
  • 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.

...

Modeling subcommittee

  • Short Description: Model of ONAP will be finalized before M3, many models need to be finalized
  • Detailed Description:  There are many models proposed for Frankfurt which need to be finalized. Slicing model et al.
  • Topic Leader: Andy Mayer Hui Deng
  • Estimated Audience Size (1-15 / 15-30 / 30-50 / >50): 15-30
  • 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: Open discussion on performance and robustness tests
  • Detailed Description: For the moment, most of the tests are functional tests. There is no real stress or performance test. There is 1 72h long duration test (stability test executed by integration team consistsing in runningvFW use case during 72h). These tests are usually complex to setup and requires resources. This session will question the sense of such tests within ONAP context and evaluate some scenarios. 
  • Topic Leader: Morgan Richomme
  • Estimated Audience Size (1-15 / 15-30 / 30-50 / >50): 1-15
  • 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.

...

Integration - Discussion on the test strategy evolution in ONAP

  1. Short Description: Discussion on the test strategy evolution in ONAP based on Integration team experience.
  2. Detailed Description: Very ambitious test had been announced in the past (S3P, chaos monkey). However health check still does not guarantee a good integration, verified end to end use cases are sometimes very big and hard to automate and/or to reproduce in different environments.  It is today not trivial to know which components are really used/covered through existing use cases. Basic Integration tests in the target environment are missing to guarantee a good quality of the solution.

    More basic tests should be provided by the components to offer a better coverage of their APIs, interfaces and features. CSIT tests are not enough as they are run on non representative target environment and robot healthcheck tests are sometimes to high level to re

  3. ally indicate the health of a component. This session will address the question of the test strategy in ONAP.

  4. Topic Leader: Morgan Richomme Krzysztof Kuzmicki Marcin Przybysz
  5. Estimated Audience Size (1-15 / 15-30 / 30-50 / >50): 1-15
  6. 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.

...

ONAP Usability - Current status and Frankfurt objectives

...