Area leaders should use this page to enter their key findings/impressions/concerns regarding the event
Monday, January 13
Track | Key Points | Challenges | Next Steps / AIs |
---|---|---|---|
Testing | Have 3 participants providing VNFs for testing
Working on two infrastructures, with 3rd being setup
VNF Images have uploaded to infrastructure |
|
|
CNTT | Community alignment |
|
|
Containers verification |
|
| |
OPNFV | CIRV is approved project in OPNFV - this is the delivery of RI and RC for CNTT. |
| |
CI/CD Evolution to solve today's problems |
|
| |
OPNFV PDF to Airship Manifest transformation |
|
| |
VMware Integrated OpenStack Reference Implementation |
| This is a Project proposal! VCF Installer | |
Green Bay Packers won their playoff round | Go Pack Go! https://www.google.com/search?client=firefox-b-1-e&q=NFL+playoffs | ||
ONAP | ONAP Usability |
|
|
Platform Maturity for Guilin | Are we making progress on platform maturity?
|
| |
SO Enhancement | Next steps support:
|
| |
SECCOM | Main requirements for Frankfurt
| How to get all OSJI solved by PTL ? => Need help from TSC to progress Proposals to remove all Root privileges to containers and to automatically check in Gating User management is also a key topic to be addressed. Some experience from ODL could be used. | |
OOM: What's new | Main objectives for Frankfurt
Creation of template for Helm charts | Discussions on database: do we still need so many DB types ? Impacts on operations (backup/restore) Discussions on password managementto contuniue with dedicated sessions tomorrow | |
Closed Loop | TOSCA based closed Loop Extend closed loop from DACE/Policy to other appalications CLAMP extension
|
Tuesday, January 14
Track | Key Points | Challenges | Next Steps / AIs |
---|---|---|---|
LF Staff | Be respectful of everyone's time |
|
|
Testing | Have starting running static testing |
|
|
CNTT | Targeted 2020 Release Discussions: (Alpha, Beta, General Availability Launch) |
|
|
OVP 2.0 Launched RI & RC |
| ||
OPNFV |
| Marching towards reference! | |
RI + RC WS Update:
|
|
| |
Hardware Delivery Validation
|
|
| |
OPNFV Release Process Evolution
|
|
| |
OVP 2.0
|
|
| |
ETSI NFV Mano and VNF Testing
|
|
| |
Manifest Validation
|
|
| |
ONAP | Change Management support | Presented what is done in Frankfurt and what is planned in Guilin | Build and Replace worklfow should allow to modify existing instances of the VNFs on the fly. Lack of VNFC level reconfiguration is one if the missing features on SO/Controller side which is not suppoirted today. We want to solve this issue in the Guilin release PNF support by ONAP Change Management is the key challenge, planned to extend in Guilin Schema/VSP Update is a chalange in the Upgrade process in ONAP. We want to addres this issue and to enable update of the schema with adequate modification of the existing instnces of services - for PNFs, VNFs and CNFs Integration with CDS and K8s workloads as one of the key drivers for improvements of change management porocess in ONAP as K8s provides scaling, upgrades and traffic distribution capabilities by itself. For Frankfurt integration with CDS for CNFs creation is introduces. IN further releases K8s scaling and upgrade capabilities should be introduced. |
Transport slicing support by ONAP | This presentation focused on:
|
| |
Network slicing (core network) ongoing support by ONAP CSMF and NSMF part of ONAP. External NSSMF to be used. Demo for Frankfurt:
ONAP components Impacts
| Challenges on whether this is the only possible implementation or there may be more Alignment on models and API with 3GPP and ORAN A1 | Next step for G Release: include transport and mronitoring Discussion on communication-service-profile introduced in ONAP Warning on templates that are deprecated within 3GPP | |
SECCOM: Password removal | All passwords should be stored only in Kubernetes secrets, users should be allowed to provide their own secrets for the deployment and allow to generate passwords at the deployment time. | Further exchanges with ONAP community on best practice approval and implementation - sessions at the PTLs and TSCs calls. | |
SECCOM: Ingress controller Ingress Controller introduced for Frankfurt as an option deployment | Effort on passing knowledge to ONAP teams on ingress controller and service mesh | Sessions at the PTLs calls. | |
ONAP SECCOM ISTIO opportunity for common continuation discussion | Coexistance of AAF and Service Mesh in a long term security solution | AAF and ISTIO to be treated as two separate tracks | |
Use Case Cross-Carrier 5G | Get the Community Aligned on Network Slicing - AP for Architecture/Requirements subcommittee + Magnus (ONAP TCC) What are the "baby steps" to build a "Slicing" roadmap Promote ONAP through #1 use cases that does not require changes in ONAP; #2 POC so Innovation can continue while focus on ONAP Core. | ||
Use Case Subcommittee
|
| ||
Modeling Subcommittee
| Align Information Model with external SDO | Alignment with Documentation to include glossary from Modeling team and to improve API Documentation. Communication to PTL to explain the API Swagger reco |
Wednesday, January 15
Track | Key Points | Challenges | Next Steps / AIs |
---|---|---|---|
Testing | |||
CNTT | |||
OPNFV | |||
ONAP | Collaboration between 3GPP (and other SDOs) and ONAP -
| How to provide links to ONAP implementations from 3GPP (eg Github, RTD link) ? | 3GPP/SA5 collaboration to Establish more communication wit TMF to get more feedback on ONAP (via catalyst experience) Catalyst projects can be seen as use-case incubation |
O-RAN / OSC rel A / ONAP joint PoC/PlugFest results and next steps | |||
ONAP Integration Gating retrospective ~2h to deploy ONAP Dashboard: <add link> Recap of KaaS (Kubernetes as a Service) POC to support Gating activities - deployment on Ms Azure | Avoid merge code when OOM gating is failing Need to identify how we can pursue footprint reduction effort | Sync-up with SO, OOM team to identify additional 'build' improvement | |
Thursday, January 16
Track | Key Points | Challenges | Next Steps / AIs |
---|---|---|---|
Testing | |||
CNTT | |||
OPNFV | |||
ONAP |