/
2020 April Virtual Technical Event

2020 April Virtual Technical Event

Apr 25, 2020

Welcome to the April Virtual Technical Meetings!

Normally we'd post a photograph of the meeting city, so instead enjoy this image of a vintage switchboard!

REGISTER: https://events.linuxfoundation.org/lfn-technical-meetings-spring/

LFN Technical Meetings Spring 2020, April 21-23

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. 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.

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.

Logistics

The Schedule can be found here: https://lf-networking.atlassian.net/wiki/x/9Ofu

Registration to the event is required for all attendees. Register via CVENT Here.

Registration helps the LFN staff better to anticipate attendance, allocate resources, and measure community engagement. Thank you for taking this important step.

Materials

Presenters, please remember to link your topic materials are linked to your session in the schedule.

Meeting Participation

All sessions shown on schedule are accessible via the (experimental) Qiqo Chat: https://lfn.qiqochat.com/events OR via the zoom bridge shown in the track (column) header on the schedule above.

New to Qiqo?  You can find a Qiqo Chat Account Creation & Demo here: https://lf-networking.atlassian.net/wiki/x/8Obu

Please feel free to use the Hallway track rooms in Qiqo for ad hoc meeting discussions. If you'd like to announce a particular ad hoc discussion, please add it to the schedule in the appropriate Hallway column in the schedule above.

Please use the main Qiqo Chat for overall event questions/issues; please use the zoom chat capabilities for interactions within a particular session.

Finally, please join us for the post event Social Hour at the conclusion of the event. This will be a time to gather more informally with your colleagues and have some fun, more casual conversations and to celebrate the end of several days of intense collaborative progress. 



Feedback

Please provide ongoing real-time feedback for the event here: https://lf-networking.atlassian.net/wiki/x/gOfu

We will also be sending out a post-event attendee survey that we hope all of you will complete.





Qiqo Chat Account Creation & Demo

2020 April VF2F Combined Event Schedule

2020 April VF2F Combined Event Schedule

LFN 2020 April Virtual Event Review & Feedback





Topics

<Sample Topic>

  • Short Description:  One line description of topic

  • Community:  CNTT, OPNFV or ONAP

  • Detailed Description: Detailed description of topic

  • Topic Leader(s): name 1, name 2, ...

  • Scribe (Capture important commentary and record action items): name1, name2

  • Moderator (Monitor Chat, organize questions, manage time): name1

  • Host (Manage/Control Bridge functions):  You can appoint an alternate host, but we recommend that the Moderator and the Host be the same person.

  • 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: Password removal continued and no hardcoded passwords for a new code 

  • Short Description:  One line description of topic

  • Community:  ONAP

  • Detailed Description: Continuation of efforts in removing hardcoded passwords in ONAP

  • Topic Leader(s): @Krzysztof Opasiak 

  • Scribe (Capture important commentary and record action items): name1, name2

  • Moderator (Monitor Chat, organize questions, manage time): name1

  • Host (Manage/Control Bridge functions):  You can appoint an alternate host, but we recommend that the Moderator and the Host be the same person.

  • Expected duration: 30 mins

  • Interested In Attending: @Pawel Pawlak @Samuli Kuusela @Tony Hansen

ONAP: Communication matrix 

  • Short Description:  Review of the Communication matrix status for an external communication in DCAE context

  • Community:  ONAP

  • Detailed Description: Detailed description of topic

  • Topic Leader(s): @Natacha Mach 

  • Scribe (Capture important commentary and record action items): name1, name2

  • Moderator (Monitor Chat, organize questions, manage time): @Natacha Mach name1

  • Host (Manage/Control Bridge functions):  You can appoint an alternate host, but we recommend that the Moderator and the Host be the same person.

  • Expected duration: 30 mins

  • Interested In Attending: @Pawel Pawlak @Samuli Kuusela

ONAP: Package upgrade strategy - security aspects

  • Short Description:  Review of the Package upgrade strategy and progress made

  • Community:  ONAP

  • Detailed Description: Review of the new process and guidelines prepared for ONAP projects

  • Topic Leader(s): @Pawel Pawlak @Amy Zwarico 

  • Scribe (Capture important commentary and record action items): name1, name2

  • Moderator (Monitor Chat, organize questions, manage time): @Pawel Pawlak

  • Host (Manage/Control Bridge functions):  You can appoint an alternate host, but we recommend that the Moderator and the Host be the same person.

  • Expected duration: 30 mins

  • Interested In Attending: . 

ONAP: VNF security requirements

  • Short Description:  Continuation of VNF secirity requirements updates

  • Community:  ONAP

  • Detailed Description: Set of requirements under review

  • Topic Leader(s): @Amy Zwarico 

  • Scribe (Capture important commentary and record action items): name1, name2

  • Moderator (Monitor Chat, organize questions, manage time): @Amy Zwarico 

  • Host (Manage/Control Bridge functions):  You can appoint an alternate host, but we recommend that the Moderator and the Host be the same person.

  • Expected duration: 60 mins

  • Interested In Attending: @Pawel Pawlak  @Samuli Kuusela

ONAP: Logs management evolution

  • Short Description:  From security perspective this topic is very important and unfortunately not progressing in ONAP

  • Community:  ONAP

  • Detailed Description: 

    • Draft recommendation idea:

      1. common place for data - all applications should generate logs that can be collected by Kubernetes (rtarget for G release)

      2. common format for data - format of minimum data that we want that is usefull (target for H release)

  • Topic Leader(s): @Pawel Pawlak 

  • Scribe (Capture important commentary and record action items): name1, name2

  • Moderator (Monitor Chat, organize questions, manage time): @Pawel Pawlak 

  • Host (Manage/Control Bridge functions):  You can appoint an alternate host, but we recommend that the Moderator and the Host be the same person.

  • Expected duration: 30 mins

  • Interested In Attending:  @Samuli Kuusela @Srinivasa Addepalli  @Tony Hansen

ONAP: Service Mesh analysis as alternative for part of ONAP AAF (policy enforcement)

  • Short Description:  One line description of topic

  • Community:  ONAP

  • Detailed Description: Discussion on policy enforcement part and how Service MEsh could fulfill this gap

  • Topic Leader(s): @Krzysztof Opasiak 

  • Scribe (Capture important commentary and record action items): name1, name2

  • Moderator (Monitor Chat, organize questions, manage time): @Krzysztof Opasiak name1

  • Host (Manage/Control Bridge functions):  You can appoint an alternate host, but we recommend that the Moderator and the Host be the same person.

  • Expected duration: 30 mins

  • Interested In Attending: @Pawel Pawlak @Krzysztof Opasiak @Amy Zwarico @Samuli Kuusela @Gervais-Martial Ngueko @hampus.tjader @Srinivasa Addepalli @Tony Hansen

ONAP and CNTT Security alignment meeting

  • Short Description:  Sharing between both projects progress in the security domains

  • Community:  CNTT and ONAP

  • Detailed Description: 

  • Topic Leader(s): @Samuli Kuusela @Pawel Pawlak

  • Scribe (Capture important commentary and record action items): @Pawel Pawlak 

  • Moderator (Monitor Chat, organize questions, manage time): name1

  • Host (Manage/Control Bridge functions):  You can appoint an alternate host, but we recommend that the Moderator and the Host be the same person.

  • Expected duration: 30 mins

  • Interested In Attending:. @Pawel Pawlak @hampus.tjader

ONAP: Akraino reference for security documentation

  • Short Description:  Review of best practices implemented in Akraino taht could be used for ONAP

  • Community:  ONAP

  • Detailed Description: 

  • Topic Leader(s): @Amy Zwarico 

  • Scribe (Capture important commentary and record action items): 

  • Moderator (Monitor Chat, organize questions, manage time): @Amy Zwarico

  • Host (Manage/Control Bridge functions):  You can appoint an alternate host, but we recommend that the Moderator and the Host be the same person.

  • Expected duration: 30 mins

  • Interested In Attending: @Pawel Pawlak  @Samuli Kuusela @hampus.tjader

ONAP: Holistic view of ONAP security

  • Short Description:  Full view of ONAP security

  • Community:  ONAP

  • Detailed Description: 

    • Access control

    • Hardening

    • Logging

    • Gaps identified

  • Topic Leader(s): @Krzysztof Opasiak @Amy Zwarico 

  • Scribe (Capture important commentary and record action items): @Pawel Pawlak 

  • Moderator (Monitor Chat, organize questions, manage time): @Krzysztof Opasiak name1

  • Host (Manage/Control Bridge functions):  You can appoint an alternate host, but we recommend that the Moderator and the Host be the same person.

  • Expected duration: 60 mins

  • Interested In Attending: @Pawel Pawlak @Amy Zwarico @Krzysztof Opasiak @Samuli Kuusela  @Gervais-Martial Ngueko @hampus.tjader @Tony Hansen

ONAP: SECCOM Guilin security requirements update

  • Short Description:  Review of priorities for Guilin release from Security Subcommittee perspective with split into priorities.

  • Community:  ONAP

  • Detailed Description:

    • Priority1:

      • 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.

    • Priority2:

      • 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.

    • Priority3:

      • 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

    • High priority SECCOM initiative - service mesh recommendation

    • SECCOM initiative: OJSIs to be solved

    • SECCOM initiative: https communication

    • SECCOM initiative: User access management

    • SECCOM initiative:: ONAP MVP 

    • SECCOM initiative: Flow management 

    • SECCOM initiative: Logs management

  • Topic Leader(s): @Pawel Pawlak , @Amy Zwarico @Krzysztof Opasiak @Tony Hansen @Natacha Mach

  • Scribe (Capture important commentary and record action items): @Amy Zwarico

  • Moderator (Monitor Chat, organize questions, manage time): @Pawel Pawlak

  • Host (Manage/Control Bridge functions):  You can appoint an alternate host, but we recommend that the Moderator and the Host be the same person.

  • Expected duration: 60 mins

  • Interested In Attending: @Pawel Pawlak @Samuli Kuusela @hampus.tjader @Tony Hansen

ONAP: ETSI NFV modeling and API

  • Short Description:  The alignment of modeling between ONAP and ETSI NFV is important for the commercial deployment based on ONAP, this slot will summary what we have achieved and and identify the future cooperation work between modeling and API

  • Community: ONAP

  • Detailed Description: Agenda

    • Latest ETSI NFV modeling and API progress (@Thinh Nguyenphu )

    • ETSI NFV model impact on R7 (@Xu Yang )

  • Topic Leader(s):  Andy Mayer, DENG Hui

  • Scribe (Capture important commentary and record action items): Andy Mayer, DENG Hui

  • Moderator (Monitor Chat, organize questions, manage time): Andy Mayer, DENG Hui

  • Host (Manage/Control Bridge functions):  Andy Mayer, DENG Hui.

  • Expected duration: 30 mins

  • Interested In Attending: Andy Mayer, @Benjamin Cheung @Hui Deng @Xu Yang @lishitao @Kamel Idir

ONAP: Container Modeling

  • 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

  • Community: ONAP

  • Detailed Description: Agenda

  •  

    • CNCF TUG @Lei Wang

    • CNTT  @Tom Kivlin @Gergely Csatari

    • ETSI NFV container architecture @Ulrich Kleber

  • Topic Leader(s):  Andy Mayer, Hui Deng

  • Scribe (Capture important commentary and record action items): Andy Mayer, DENG Hui

  • Moderator (Monitor Chat, organize questions, manage time): Andy Mayer, DENG Hui

  • Host (Manage/Control Bridge functions):  Andy Mayer, DENG Hui

  • Expected duration: 45 mins

  • Interested In Attending: Andy Mayer, @Hui Deng @Xu Yang @lishitao @Amar Kapadia @Srinivasa Addepalli @Victor Morales @Manoj Kumar

ONAP: Test Automation DevOps and CI/CD

  • 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

  • Community: ONAP

  • Detailed Description: 

    • Demonstration:  leverage ONAP projects to build VNF end-to-end testing which will achieve automatic test topology design, automatic test environment deployment, automatic test execution and the test results collection

    • Open discussion 

      • How to apply test frameworks in CI / CD? the integrated options?

      • how to leverage DevOps and CI/CD techniques across the boundary from SW provider to service provider? how to build the joint pipeline between SW provider and service provider?

  • Topic Leader(s):  @Yan Yang

  • Scribe (Capture important commentary and record action items):TBD

  • Moderator (Monitor Chat, organize questions, manage time): @Yan Yang

  • Host (Manage/Control Bridge functions):  @Yan Yang

  • Expected duration: 45 mins

  • 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.



OPNFV: Hardware Delivery Validation tools demostration

  • Short Description:  A demo of HDV implementation based on redfish interface.

  • Community:  OPNFV

  • Detailed Description: 

    • The HDV tool is currently in CIRV project. It provide interface and status check for hardware for the preparation of infrastructure software deployment, following the requirement from CNTT RI chp5

    •  introduction of the hdv tools, (principle, configuration file instruciton, opnfv repos location)

    •  demo on a lab server, current tool usage, configuration extension. etc.

  • Topic Leader(s):  @Liang Chen

  • Scribe (Capture important commentary and record action items): name1, name2

  • Moderator (Monitor Chat, organize questions, manage time): @Qiao Fu

  • Host (Manage/Control Bridge functions):  @Qiao Fu

  • 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: Control Loop Sub Committee Guilin Requirements