All of ONAP's mailing lists will be migrated from mailman to groups.io from 09:20 to 11:00 AM Pacific time on June 20th. This is a brief overview of what to expect with the new system

must be Monday

Istio service mesh provides an infrastructure layer to connect, manage and secure microservices, meanwhile, CNCF project Jaeger and Prometheus can provide service visibilities with distributed tracing and metrics. This session will talk about how MSB project plan to integrate them with ONAP and leverage their capabilities to support ONAP microservice architecture.

Discussion and agreement on improvement proposals

Community Feedback

showcase the DCAE-DC as the monitoring designer in SDC.

a demo of the capabilities will be presented with a Q&A session.

a presentation of the features planned for Casablanca.

showcase the VID as the operations portal of ONAP.

a demo of the capabilities will be presented with a Q&A session.

a presentation of the features planned for Casablanca.

Looking at ONAP production deployment top-down from operator’s point of view
1) Business drivers
2) Production deployment use cases
3) Typical challenges
4) Capabilities required in ONAP to address the challenges
5) Role of standards and how we see the overall standard eco system can enable the scenarios
6) Our Proposal

Edge Automation through ONAP

1) Casablanca M1 Planning

2) Topics for upcoming releases

We would like to present 3 different approaches to accelerate the ONAP release cadence

Review the feedback on how Platform Maturity (S3P) worked in Beijing. Suggested changes to requirements, levels, and supporting tools/projects.

(NOTE: may require an agenda item on the TSC meeting for voting also)

Review the experience of starting with a functional VNF and getting it deployable using ONAP.  What was easy vs hard when preparing a VNF package, installing ONAP, and using ONAP to onboard and deploy the VNF.  Experience with multiple releases of ONAP will be covered (ideally).  Conclude with recommendations for assisting the VNF developer to integrate with ONAP.

Workshop to identify ONAP security risks. The purpose is to produce a prioritized list of security improvements.

The main focus in this WS is to identify risks (assets - threats - vulnerabilities - existing controls) with a creative, brainstorming WoW.

Scope as decided in ONAP Security Sub-Committee: VID, External API, Controllers, DCAE, SO, UI componts: SDC and Use-Case UI, Portal.

1st WS: Tuesday

2nd WS: Thursday

Mornings preferred

SDNC and Generic L4-7 NF Controller

For the ONAP Beijing release, the APPC project delivered the CDT design tool to support the APPC model driven design approach.
For the next ONAP releases, we are proposing to develop a common design tool to support both SDNC and Generic L4-7 NFs (APPC, VFC) Controller integrated with SDC.

This common design tool, also called “Controller Design Studio”, will be built with associated data dictionary and an Ingredient Resource Resolution Micro service
The common design tool models shall be backwards compatible to the current use cases supported in Amsterdam and  Beijing release by Generic L4-7 NF (APP-C specific). 

Change Management for life-cycle support from hybrid PNF and VNF management perspective

Presentation of change management requirements and thoughts on 5G hybrid PNF and VNF management

Wednesday or Thursday

KDDI presents our anticipation for ONAP from the perspectives as follows;

      ?3 Main functions of eTOM

????Japanese Operator’s policy and issues

????Anticipation for ONAP