Please add your suggestions for the ONAP DDF below. Timeline for topic selection is:
...
Short Description: introduce the implementation of automatic service continuity and life-cycle management of 5G network slices of devices roaming across Operators.
- Detailed Description:
- This session will present options for 5G slice continuity when devices roam across International borders (e.g., standard slices vs. slice blueprint export vs. Virtual home slice) and then identify and implement the necessary logic, APIs and models in ONAP for Guilin release.
- Topic Leader: Davide Cherubini
- Estimated Audience Size (1-15 / 15-30 / 30-50 / >50): 15-30
- Interested In Attending:
- If you are interested in 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 TSC Member Roundtable
...
Integration - Discussion on the test strategy evolution in ONAP
- Short Description: Discussion on the test strategy evolution in ONAP based on Integration team experience.
- 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
ally indicate the health of a component. This session will address the question of the test strategy in ONAP.
- Topic Leader: Morgan Richomme Krzysztof Kuzmicki Marcin Przybysz
- 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.
...
ONAP Usability - Current status and Frankfurt objectives
...
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.
...
Transport Slicing: How to evolve CCVPN to a multi-layer slicing and abstraction solution
Short Description: Share and discuss design ideas on how to add to CCVPN the multi-layer slicing and network abstraction capability, which can enable 5G transport slicing
- Detailed Description: This topic discusses (1) how to evolve/extend the current CCVPN use case into a multi-layer/technology slicing architecture which provides abstraction management across layers; (2) how to carry out a transport network slicing solution based on the new architecture; (3) how the solution can be integrated with other ONAP components/solutions to support the overall E2E 5G slicing use case; and (4) how ONAP can work together with standards organizations (ETSI, IETF, MEF, etc.) on coordinating aspects of standards relevant to multi-layer/technology transport slicing functionality and operations in 5G contexts.
- Topic Leader: LIN MENG Henry Yu
- 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: Update and deep dive for the PM Control function being added in Frankfurt
- Detailed Description: As a further evolution of the 5G Bulk PM use case, a control plane is being added supporting definition of network-wide subscriptions with flexible lifecycle. This session will look closer at how the use case is realized using the different ONAP components such as AAI, DCAE, Policy and SDNC/CCSDK/CDS.
- Topic Leader: Oskar Malm
- 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.
...
Ingress controller status update
Short Description: Update and deep dive for the Ingress controller work
- Detailed Description: The session will look closer at how our support for ingress controller is moving forward as a first step towards service mesh. The talk will focus on current state and challenges to move forward.
- Topic Leader: Krzysztof Opasiak
- 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.
...
Password removal status update and examples
Short Description: Update on password removal from Helm charts
- Detailed Description: The session will focus on the status of password removal effort. We will focus on current blockers and present some good and bad examples from project that we discovered while working on this topic.
- Topic Leader: Krzysztof Opasiak
- 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.