The LFN Technical Meetings for CNTT/OPNFV and ONAP are being held concurrently over three days, April 21 - 23. This virtual event takes the place of the in-person meetings originally planned after ONES North America in Los Angeles (which is being rescheduled for the fall). Registration is required and registrants can attend any of the LFN Technical Meeting sessions as desired. This is the first fully virtual event of this type for LF Networking. We thank you for your patience and also welcome your feedback and suggestions. Attendees will be asked to complete a short survey post-event. Survey participants will receive a code to redeem an event gift from LF Networking.
CNTT: The Common NFVI Telecom Taskforce (CNTT) is a collaborative effort from GSMA and the Linux Foundation launched in June, 2019. Its mission is to define a common NFV infrastructure to simplify the development and deployment of virtualized networking applications for the telecom industry. This gathering will be an opportunity to advance work on the Reference Architecture and Reference Model and address implementation considerations for OPNFV and the OPNFV Verification Program (OVP).
ONAP: The ONAP community will be hosting meetings for alignment of architecture, modeling, security and other aspects of system design as we look toward future releases of the platform.
This helps the LFN staff better to anticipate attendance, allocate resources, and measure community engagement. Thank you for taking this important step.
Links to the event schedule will be posted to this page when ready. On the schedule, attendees will find the Zoom bridge information for their desired sessions. Please create your own calendar appointments with this information to ensure you don't miss your sessions.
Appuyez sur la touche Entrée pour effectuer la recherche
Écrire un commentaire…
search
recentlyviewed
attachments
weblink
advanced
image-effects
image-attributes
Connexion en cours....
Short Description: One line description of topic
Short Description: One line description of topic
Short Description: Review of the Communication matrix status for an external communication in DCAE context
Short Description: Review of the Package upgrade strategy and progress made
Short Description: Continuation of VNF secirity requirements updates
Short Description: From security perspective this topic is very important and unfortunately not progressing in ONAP
Draft recommendation idea:
Short Description: One line description of topic
Short Description: Sharing between both projects progress in the security domains
Short Description: Review of best practices implemented in Akraino taht could be used for ONAP
Short Description: Full view of ONAP security
Short Description: Review of priorities for Guilin release from Security Subcommittee perspective with split into priorities.
Updates of the languages (java from v8 -> v11 and Python 2.7 -> to 3.x) – Interns from LFN could be gained
Updates of directly dependent software components (Here we are thinking about benefiting from LFN Interns that could support projects in their packages upgrades, in addition the new version of Nexus-IQ is able to display components with direct and indirect dependencies, we should define priorities, release manager should help in coordination between projects)
Automated security testing – containers not running as root – SDNC good example
Increase the number of CIS Docker Benchmark checks in the Integration healthchecks.
Secrets management
No root access to the DB from main application container. Currently we have some pods (i.e. OOF) that require root access to their mariadb-galera instance for main application to work. This is obviously a security issue. Each application should have its own DB account that allows to access only its own DB.
All config files inside the main container should be ReadOnly There are some weird design like in APPC where main container modifies properties provided by the user at runtime. I believe that application configuration should be read only.
Increase of code coverage (to be honest in Frankfurt release it seems that not that much happened) – each project was supposed to propose a % feasible for them and follow the actions to achieve it.
CII badging
SECCOM initiative: OJSIs to be solved
SECCOM initiative: https communication
SECCOM initiative:: ONAP MVP
SECCOM initiative: Flow management
SECCOM initiative: Logs management
Short Description: ONAP historically mostly documented the VM modeling, and now it moves into the cloudnative solution, so container modeling need to be documented as well, related documentation 1) Introduction of K8S module in MultiVIM project and 2) Invite K8S PoC could be found here: https://wiki.onap.org/display/DW/Modeling+2020-04-07
Short Description: Show test automation demo with ONAP components and discuss how to leverage Devops and CI/CD to achieve test automation and continuous testing
Short Description: A demo of HDV implementation based on redfish interface.
Short Description: Control Loop subcommittee open discussion on Guilin Requirements
Short Description: Presentation of requirements proposed for Guilin
Short Description: Presentation of 5G Use Cases and PNF Use Cases proposed for Guilin
Short Description: Presentation on platform telemetry insights & demos of closed loop automation use cases.
Short Description: Discussion of details and agreements leading up to a new release process.
Short Description: Review OPNFV's overall process to respond to CNTT Requirements pre-Baldy Release
Short Description: Discussion, Decisions, and all topics of importance to OPNFV.
Short Description: Introduce the change that will introduce for OPNFV 2.0.
Short Description: Provide a short and sweet overview on several OPNFV projects, including the most recent achievements and status
Short Description: Collect and Discuss some enhancements to Test API and Testdb
Short Description: Discussion of Cloud Native OVP (OVP 2.0) and cross-community action items
Short Description: ArchCom updates and plans for the rest of 2020
Short Description: Demos of the Policy Framework Platform
Short Description: Demos of deploying ONAP over StarlingX 3.0 (kubernetes 1.16.2), and orchestrating CNF (cloud native Firewall) to StarlingX 3.0.
Short Description: Hardware Acceleration Solution and gap analysis with CNTT. Discuss and gather hardware acceleration requirements for OPNFV and CNTT.
Short Description: Update on technical community coordination
Short Description: Show the OOM Guilin release plan
Short Description: Discuss the main priorities for Guilin (use cases, CI, test cases, x-projects support, ...)
Short Description: Share visions and explore collaboration
Community: CNTT, OPNFV, and ONAP
Short Description: E2E Network Slicing Planning for G release and discussion on some key tracks
This session will include the follow 4 sub topics:
Design Time validation: When Operator on-board CNF as VSP in SDC, Operator wants to check the given CNF is confromance to their Operator Specific compliance such as security policies
Run time validation: Once CNF is provisioned in ONAP, it needs to be validated for sanity check and required functioanlity check.
Support LFN OVP 2.0 to support CNF conformance and CNF on-boarding vadlidations. (pre-on-boarding time)
Short Description: discuss NFVI features for edge computing
Short Description: discuss SDN solution in data center and gap analysis with CNTT
Short Description: discuss vSwitch offloading requirements analysis and standard
Short Description: Discuss the steps being taken on on-boarding and designing aspects of the ETSI based package mgmt through ONAP
Short Description: Discuss on the efforts being taken by the ONAP CNF task force for the ONAP - CNTT alignment.
Short Description: Planned enhancements around CMPv2 support in Guilin release including DCAE integration and