A proposal about single management platform for edge cloud
presentation & discussion
Share some conclusion about test on edge virtualization layer (plan selection included) and discuss about an edge management platform and its necessary functions.
Key research and technology related to C-RAN/O-RAN network
discussion
Discuss about the relative research and technology on C-RAN/O-RAN network including virtualized RAN with white box pico-station, potential MEC scenario with virtualized RAN, Radio Intelligent Controller with virtualized RAN.
Kubernetes based cloud region support to deploy all kinds of deployments - VNFs, CNFs, IT application micro-services
Presentation and Discussion
Present the work done as part of ONAP R4 & OPNFV OVN4NFV project and propose new features in ONAP R6 and OPNFV such as : Multi-Cluster scheduler to schedule applications across multiple sites, Matching engine to identify sites with edge labeling and K8s operator support etc... Also, will present some use cases and expectations on how they need to get deployed and how ONAP R6 work takes care of these deployments
Present current Samsung experiences with CNF infrastructure (outside of ONAP) and discuss how it applies to and can be leveraged in ONAP solution.
View file
name
LFN ONAP CNF.pptx
height
150
View file
name
ONAP_service_on_Openstack_and_Kubernetes.pptx
height
150
View file
name
zoom_Container_infrastructure_for_CNFs.mp4
height
250
ONAP & OPNFV
@ Yi Yang
Opendaylight scalability issues in super scale data center
Presentation + Discussion
In industries, many commercial SDN products have been rolled out based on Opendaylight, but Opendaylight community release is not ready to enter super scale data center which has 1000+ servers, reliability, horizontal scalability and performance are fundamental requirements, this presentation will point out current scalability issues and possible solutions and propose some effort directions in the future ODL development, also encourage PTLs can participate in discussion and elaborate scalability issues in every project and propose some good solutions. Cloud data center is a critical area Opendaylight must take care of if we want to keep Opendaylight successful continuously.
Experience Sharing of Hardware acceleraion in China Mobile
Presentation + Discussion
Present the work done about hardware acceleration In China Mobile, such as the the OVS offloading test, Also will present some focus about future research.
Present the desigh thought of common API for hardware acceleration in dataplane. Discuss about th GTP offloading requirement and procedure of VNF, the common API may be use in this prcedure.
All you need to know about the building block workflows in Service Orchestrator.
Presentation + Discussion
This discussion / presentation will give insights to understand the concepts and implementation details behid the SO building blocks, the idea is to make it as simple as possible for someone new to ONAP able to appreciate and use the existing building blocks and futher build / enhance their own on the top.
Short term and long term improvements. Followup on ongoing activities. El Alto planning.
API DocumentationEric Debeau : lessons learnt from existing Documentation. Proposal to verify API compliancy and to use another visualistaion tool for API documentation
Security and DocumentationEric Debeau , Natacha Mach , Pawel Pawlak : How to better document the various ONAP components and their open ports.
Archi and DocumentationStephen Terrill : how to join efforts for a better documentation. Architecture project started to describe functional view of various ONAP components. How can we ruse it for official documentation ?
The architecture and the implementation of the ONAP Policy Framework was substantially upgraded in the ONAP Dublin release. In this talk, we present the evolved ONAP Policy Framework discussing the most important improvements, and describing the evolved architecture of the Policy Framework. We highlight the power of TOSCA Policy Types and how they can be used to build translation applications.
This session will introduce Sweetcomb project and cover key elements:
1) Provides gNMI interface and OpenConfig Yang models for Cloud.
2) Provides NETCONF & RESTCONF interfaces and IETF Yang models for Telecom.
3) Can Support different Data Planes, such as VPP, DPDK, Linux Kernel and OVS.
4) Can integrate with SDN Controllers and Orchestration, such as ONAP, K8s, ODL and ONOS, etc.
5) Supports High Availability and real-time streaming telemetry in Containers.
The architecture and the implementation of the ONAP Policy Framework was substantially upgraded in the ONAP Dublin release. In this talk, we present the evolved ONAP Policy Framework discussing the most important improvements, and describing the evolved architecture of the Policy Framework. We highlight the power of TOSCA Policy Types and how they can be used to build translation applications.
View file
name
zoom_0.mp4
height
250
ONAP Anyone who uses or may use the Policy Framework
Experience Sharing of Trustworthiness Improvement In ONAP Development
Presentation + discussion
Introduction Huawei open source team's effort in assuring code and docker security by apdoting open source tools in development, such as coverity and anchore.
View file
name
Experience Sharing of Trustworthiness Improvement In ONAP Development.pdf
How ONAP is going to handle VNF Application Configuration? As ONAP is already introducing SOL003 and SOL005, it is worth introducing SOL002 as well. I will present work that Samsung has done as part of the internal demo + discussion about the future of Application LCM interfaces in ONAP.
What should be the ONAP TSC Priorities for the next 6 months?
Discussion
This session is dedicated to identify what would be the top 3 priorities of the TSC in order to support the ONAP Community, to improve any process/toolchain gaps and to build an execution plan accordingly.
Feel free to create new TSC tasks in JIRA under "ONAP TSC" project
Virtual Radio Area Network (vRAN) is a critical piece for upcoming 5G networks. In this demo, we will show you how to build the FlexRAN (an open source vRAN approximation VNF from Intel), onboard it onto ONAP and then deploy it onto OpenStack. Once the service is deployed, the FlexRAN service performs basic operations in a simulated environment.
This session gives developers an opportunity to discuss the strengths, weaknesses, areas that can be improved, and areas that threaten project failures. The focus here is on developer issues such as but not limited to languages, coding, processes, tools, methods, project structures. The result of this session could be a report for the steering committee of projects.
One suggestion would be to run this session using a technique such as SWOT analysis but that's only one suggestion. The format of the session and the reporting done from the session is at the discretion of the participants on the day.
AAI Data Model / Visualization Tools / Graph Traversals
Presentation and demo
We will look at the AAI data model and some of the visualization tooling that is being developed around it. We'll look at AAI custom queries that allow for easy traversals of the graph database, and touch on new features for even more flexible traversals slated for future releases.
Experiences in switching to Alpine Linux and upgrading to Java 11
Presentation + discussion
This session would cover two experiences sharing topics, that is gathered in working at Policy Framework but can be applied anywhere:
Switching docker base image from ubuntu to apline, that would reduce footprint signicantly .
Investigation result about upgrade Java 11 from Java 8, that is tricker than most upgrades. We have to face some challenges, like: some modules were removed or deprecated, we need to find the replacements; IDEs, plugins and tools also need to be updated; some new features are introduced, etc.
Meanwhile it would be also great to listen to your opinions.
ONAP Platform with network security as an application
Presentation + discussion
Looking into security of the managed environment, this could be represented as a 3rd party application using ONAP. The questions to explore are: how does a 3rd party application use ONAP? What are the options and approaches?
Demonstrate use of the SO multicloud plugin adapter to instantantiate workloads via Multicloud – showing how HPA policies can be utilized and also deployment to Kubernetes cloud regions. Discuss API, feature/functionality work items, integration, etc.
1. Lab update - invite lab owner to introduce the lab latest status
2. Disscuss how to better utilize lab resources and oversight lab utilization
3. OpenLab E/F work planing
View file
name
ONAP-OpenLab_DDF.pdf
height
250
View file
name
LFN-DDF OWL.pdf
height
250
WIN LAB update 1. Have some quesitons about ONAP deployment automation, next plan: OpenLab will have a cooperation meeting do discuss this details OpenLab E/F planning 1. Open Lab repo proposal Team think this is a good idea, next step is to apply this gerrit repo and plan the dirctory under the repo 2. Add lab requirements to ONAP milestone Team think we should consider whether the proposal is practical. Because it proposal mainly for usecase and functional requirements, so next plan is to propose this to usecase subcommittee and collect feedback
2.The VF-C commercial application from different vendor
3. The VF-C Requirements collection and discussion in E/F
View file
name
VF-C Dublin Highlights and EF planning-final.pdf
height
250
Sharing the experiences in developing CMCC NFV Orchestrator with ONAP, some concerns/improvements/requirements about projects of ONAP
Demonstrate CMCC NFV Orchestrator, including package management, life cycle management. etc.
View file
name
NFV Orchestrator Practice in CMCC based on ONAP.pdf
height
250
1. In order to deal with the problem that the SDC output is inconsistent with the VFC input, now have manual step in SDC. Ericsson suggest we can leverage the PNF onboard process to less the manual step. next plan is to verify this function in SDC. 2. The VF-C workflow is the same with workflow in SO The current VF-C workflow integrated with different workflow ,such as wso2, activity and can provide unitfy API as microservice 3. The requirements collected for F release will be discuss one by one in VF-C following weekly meeting.
Present the work done about PNF software upgrade using Ansible, and propose the enhancement roadmap for El Alto, such as: 1. SO workflow 2. Query and update A&AI 3. Northbound API 4. Ansible management API 5. etc.
Vimal shares the closed-loop vision of intelligent network architecture. It is recommended to build a big data platform and model training platform around Datalake to complete the loop with Acumos, DCAE and Datalake.
Stephen shares the work related to 3GPP SA2 NWDAF and SA5 MDAF, and proposes to coordinate the relevant functional architecture to achieve consistency with the community.
Srini shares the progress of the AAAS use-case. It is recommended to cooperate with the demonstration application of China Mobile's core network element intelligent expansion and expansion, and collaborative development for specific intelligent scenarios. An open source reference implementation that integrates edge orchestration and intelligent network architecture.
There is a discussion of working procedure, it is recommended to set up a virtual working group and follow the existing workflow of the community (use-case, architecture, modeling, etc.).
This is a discussion session intended to host a dedicated discussion on implementation options on how to enable end-to-end 5G slicing as part of ONAP automated service provisioning/operation. Gaps in contexts of different options will be discussed for corresponding planning.
3GPP SA5 defines the reference architecture and workflow for 5G Slicing Management but with no standard interfaces between the three layering architecture.
A new two-layering implementation architecture of the 3GPP functional architecture leveraging TMF openAPI is reflected in commercial solutioning and external ONAP PoCs.
Call for a common approach to converge different options and work complementary manner to accelerate 5G slicing management use-case realization.
Improve ONAP tests and remove specific use-cases artifacts from ONAP components code
Presentation+discussion
Improve ONAP tests and verify that every pod is using in one or more end-to-end use-case or test cases.
Improve use-case documentation to explain the list of components used per use-case (by use-case owner)
Detail for each use-case the list of pods involved for every use-case (by PTL)
Remove use-case code/artifcats from the ONAP components code and create dedicated repos for the use-case gathering all the artifacts to be used for a use-case
Finalize the integration and work plan on the CVC (compliance and verification community) minimum viable product (MVP) for VNF Validation (life-cycle) program. This program will award a badge to VNF products (HEAT or TOSCA) meeting the programs test case / success requirements. Form this meeting, there needs to be secure commitments for resources, firm understand the timeline and milestones. Engage ONAP TestSuite/integration, VVP, and VNFSDK teams in this process.
No Kubernetes cluster should stay vulnerable. Easiest way of ensuring that is to use an automated assessment tool. Session will cover current approaches for this task as well as gather ONAP requirements for such utility.
Not all ONAP container images keep the binary content idempotent. In several cases additional runtime dependencies are downloaded after container starts. Consequences and possible solutions will be discussed during this session.
The goal of this session is to present ONAP SECCOM Scope of Work proposal and discuss with stakeholders feasibility, time line and responsibilities for:
Using dockherhub's public registry for CI/CD builds - An ONAP use-case
Presentation +
Discussion
A new proposal to use dockerhub's own docker registry for storing the Ci/CD/daily docker images builds as opposed to other implementations. Discussions around reliability, outreach of the registry, speed of new feature adoptions (like multi-architecture support) and daily performance.
The presentation will have three parts:
A brief introduction to dockerhub.
How dockerhub is used on LF projects CI/CD pipelines
ONAP use-case. How dockerhub public registry can benefit ONAP CI/CD build pipeline, what are the challenges, what are the tech teams requirements, proposed migration plan, and stakeholders, expressed and addressed concerns so far
After the presentation we would like to initiate Q/A and expression of other concerns not addressed so far, to be addressed or to be made known to us so we can addressed them in subsequent refinements of this proposal.
View file
name
Using Docker Hub's public registry for CI_CD builds - An ONAP use-case.pdf
height
150
1. Using Docker Hub is a must in order to support platform independent images
2. We want to extend the Jenkins build pipeline to build in parallel docker images for multiple architectures; this has little impact on the team's effort as it doesn't impact the artefacts (Java or Python services) build process at all
3. Migrating from Nexus3 to Dockerhub in ONAP requires a team effort between tech teams in ONAP (PTLs), LinuxFoundation (Releng) and the Multiarch team but among us we have the experience to deliver this in a smooth way
We will have a short presentation on what Lab as a Service is, where we are today, and how we plan to proceed. We want to have time to discuss the LaaS project proposal with the community and answer any questions.
The LaaS team is not able to attend, so this will have to be a remote session.
Certificate management and Secure Storage discussion
Discussion + Presentation
With the introduction of mTLS for the Dublin release, there have been troubles with proper certificate handling with external CA support and secure key storage. As a result, some ONAP projects ended up using manually configured certificates. A centralized solution for certificate handling, secure storage and KMS that ONAP projects easily can integrate with is important for future release. Focus will be on external interfaces.
It would be good for the community to get clear guidelines from SECCOM which solution we will target in long term and for Frankfurt. In this session there will be multiple presenters. First topic will be regarding background from Dublin and the need to introduce CMPv2 with welcomed discussion regarding how this might be done.
Second presentation will be held by AAF PTL related to the current plans and solution in AAF regarding certicate handling and secure key storage. Third presentation will be held by Intel regarding their investigation and PoC for ISTIO CA private key secure storage using softhsmv2.
Three new requirements for PKI in ONAP Frankfurt were proposed. Alternative 1 from how to use CMPv2 was said to be the initial target for the community, further discussion might be needed. This target would modify two previous Dublin requirements to not go for a true "RA" but for a CMPv2 client.
Status update and demo from AAF and latest progress regarding certificate handling. Demo for auto certificate renewal and other. See zoom meeting for demo.
Community sync and alignment between the current two tracks (AAFvsISTIO) to be further discussed and analyzed. Possibility to reuse SoftHSMv2 solution from ISTIO/Intel PoC also for AAF as they both target PKCS#11.
Many ONAP components have developed their own data models independently to fill their own needs. As the complexity of ONAP increases, there is a need not only to document these data models, but also to compare them, find commonalities, create abstractions, and define common principles. One path to this is through reverse-engineering.
This session will present different considerations and techniques when reverse-engineering data models to a common notation, looking at specific examples. The intention is to start a discussion around the needs in the community and how to best fulfil them.
Hello World Closed Loop (CDS and Policy aka APEX integration)
demo + presentation/discussion
A PoC has been progressed to explore CDS integration with APEX for a PNF closed loop.
This activity has brought up interesting questions, possible requirements and next step proposals for further architectural exploration in the area of policy framework and CLAMP. We are happy to share it in the comunity to open a discussion.
A top-down approach for xNF license management and ONAP: proposal with a few license management principles, and some existing use cases with license management aspects included.
View file
name
xNF License Management and ONAP 20190613 clean.pptx
Continuing on from the presentation / discussion in San Jose in April, taking Policy Framework as an example for defining model-driven ONAP architecture
Review status of ONAP architecture task forces and next steps
presentation/discussion
Walkthrough the ONAP architecture taskforces to identify which should remain open and what is the intent in the next few months, and update on the current status.
Three best practices that will improve your container development experience
Presentation & discussion
ONAP uses a number of different container base images and different versions of the same base images: 5 different versions of node, 9 different versions of openjdk and 13 different versions of Python across ONAP projects. This approach has led to duplication of efforts and inefficiencies, such as resource consumption, large footprint and long build times. Also, teams experience unnecessary pain when unexpected changes occur in upstream projects.
What if we adopted three best practices to tackle these issues together and increase re-usability, stability and security.
First, to exploit cross-project commonalities and increase re-usability, adopt a set of common base images, (onap/base-xxx) with a well-defined life cycle controlled by PTLs.
Second, to guarantee stability, setup a mirror of the Alpine Linux distribution that's locked during development cycles. Base images and libraries will remain stable during each development cycle and will only be updated in-between development cycles.
Third, let the security sub-committee proactively participate in the vetting of the OS distribution and base image in order to address any security concern before a development cycle starts.
Related to the API GW Proposal being discussed in the Architecture committee - Discussion on the problems, functional capability, project alignment and technology (Service Mesh, API GW Solution, K8S API Aggregation etc) . Seek guidance from ArchComm on next steps
CDAP - current state ; History with respect to ONAP ; Future Roadmap ; Google's managed version of CDAP on google cloud - Cloud Data Fusion - https://cdap.io/
Introduction to OVP. This session will set up the business drivers and high level expectations of OVP. For those that have not been involved in OVP work to date, this will be a good set up for working sessions later in the week.