This page is locked and topics are under review - will be re-opened for editing following review on
Please add your suggestions for the OPNFV plugfest below. Timeline for topic selection is:
Initial proposals due for review
Review will be undertaken by the Plugfest Planning Meeting / Participants and feedback will be provided
Review proposals and select topics
Final review and selections will be made for the plugfest tracks.
Plugfest planners are requesting more of a focus on developer engagement and less on content presentation. Consequently, proposals that are development oriented are more likely to be selected for the Prague OPNFV Plugfest. We are expecting to select between 4 and 5 plugfest topics / tracks. These tracks will run throughout the week, with the goal to deliver the outcome described in the proposed. The event will wrap up, with each track providing a 10 minute update the event closing plenary on Thursday.
For Plugfest challenges, state the hacking challenge and include the technologies of interest so that developers can self-identify if they have the skills for the challenge.
Topics
<Sample Topic>
Short Description: One line description of topic
Detailed Description: Detailed description of topic
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.
CI/CD Evolution
Short Description: Collect requirements, discuss, and hopefully reach a consensus (to propose to the TSC) on which CI system OPNFV might (or not) transition to.
Detailed Description: The CI/CD landscape has change dramatically over the last few years and opened the door to new services that are easier to understand, quicker to setup, and provide greater insight into project CI/CD. The OPNFV community has taken some time to investigate these new tools and determine if our requirements (e.g. Connecting hardware) for CI can be met (or not) by them. We should discuss these finding and weight the cost of transitioning (time, effort, etc) vs. the benefits of staying where we're at. The goal of this track is to reach a consensus, coupled with a document explaining how that consensus was reached (research findings, costs, etc.), to present to the OPNFV TSC for approval. If the consensus is to move, then additionally a draft migration plan should be created to outline the decencies required in moving.
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.
<your name here>
priority:
time: 45
Pharos 2.0
Short Description: Discuss how the Pharos project can evolve with new OPNFV installer (Airship) and CIRV (CNTT) influences.
Detailed Description: Discussion topics include
Pharos Specification, POD Descriptor File (PDF), Scenario Descriptor File (SDF) and Community Labs
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.
Short Description: Provide a collaborative and safe environment for VNF vendors to try out ONAP/OPNFV interop via OVP and other tooling. VNF participants completing full passing runs will be able to submit the results to the OVP portal, to have their product listed with the VNF badge.
Detailed Description: Hands-on testing topics include the following. Get more information here.
As part of this track, labs are being organized to host existing instances of the ONAP El Alto release (first release with validation tests cases included) to support the testing efforts. We will have experts and test developers participating in the track, to assist with debugging issues and to answer questions about the requirements or test results. If time permits and resources are available, VNF participants will be able to try out more advanced cases on the ONAP infrastructure, such as VNF configuration, scale-out / scale-in, etc.
Note: even though the session is optimized for VNF vendors, PNF/CNF vendors are welcome
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.
Short Description: VSPERF's IRUYA Intern on Container deployment and performance measurement of networking alternatives.
Detailed Description: See OPNFV VSPERF Wiki Intern Project page This proposed work allows for some additional Hacking on the Intern Project, development of the presentation (and maybe a demo ) with the Mentors, and a slot for the presentation itself (not too early in the week, so that all the preceding can be accomplished).
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. >>> We usually try to schedule a slot where much of the OPNFV Community can attend. With one Intern this should be about 30 minutes. <<<
Time: 45
Release Plan Evolution
Short Description: Discuss and refine the current release plan proposal
Detailed Description: A new release plan was requested by the TSC nearly two years ago. A release plan proposal has slowly taken shape since the TSC request; however, it's yet to be implemented. This meeting will seek to further refine the plan, taking into account new projects, such as CNTT-RI and the new Airship installer.
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.
Time: 45
Manifest Validation
Short Description: create automated means to do a manifest validation / or audit of actual delivery and installation of the OpenStack deployment
Skills: Meta-Data file interpretation (PDF/SDF/IDF), knows way around a command-line, system admin for data comparison between systems
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.
Skills: OS system navigation, BIOS settings, low-level hardware configuration, etc
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.
Skills: IDE tools and capabilities, Interpret YAML files, VF design artifacts, translation of NFVI and VNF standard requirements
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.
Notes: proposed byTrevor Cooper to edit description → create a prototype ‘Golden VNF’ to demonstrate and baseline capabilities and services of NFVi for a VNF Family
Time: 45
OPNFV/OVP
Airship Installation
Short Description: create a tool to take a PDF/SDF/IDF and render as files consumable by Airship (aka Manifests)
Skills: YAML, Python et al, Meta-Data Translations
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.
Short Description: create the outlines of a Kubernetes Reference Implementation (based on RA2) using a pre-built RA1-compliant OpenStack Reference Implementation
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.
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.
priority: H
CNTT only
How/where AWS fit within CNTT
Short Description: discuss how AWS fit within CNTT K8s RA
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.
priority: H
CNTT only
Joint Exercise CNTT/OPNFV for Kubernetes
Short Description: Take OPNFV phase 2 to take the Kubernetes RA2 through RI into certification of a CNF on a Kubernetes platform conforming with RA2
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/CNTT - may be replaced by CNTT RI2/RA2 discussions
Testing NFVi compliance of CNTT requirements (performance testing)
Short Description: Demonstrate a prototype of automation tools to test if NFVi complies with CNTT requirements starting with data-path performance
Detailed Description: Proposed by Trevor Cooper . This hack challenge will use PoC work in "POD10" as a baseline and aims to engage developers interested in contributing to this category of CNTT work
Challenge Leader(s): Trevor Cooper, Luc Provoost, Petar Torre, Sridhar Rao, Al Morton, ...
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.
Functest Jerma, more than ever a collection of state-of-the-art virtual infrastructure test suites
Short Description: Functest is more than ever a collection of state-of-the-art virtual infrastructure test suites
Detailed Description: Functest Jerma conforms with the latest OpenStack and Kubernetes releases and expands once again the testing coverage (.i.e. Load Balancer testing). It's is more than ever a collection of state-of-the-art virtual infrastructure test suites, including automatic VNF testing. And Functest team is now focusing on the compliance expected by CNTT (Common NFVI Telco Task Force) https://lists.opnfv.org/g/opnfv-tsc/message/5636
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.
Time: 45
Cross-Open Source Roadmap
Short Description: Develop a Strategic Roadmap across LFN open source initiatives
Detailed Description: Gather any 2020 requirement from other open source communities (OPNFV, OVP, CNTT, CVC, Acumos, Akraino, etc) that should be considered as part of the ONAP Guilin Release and beyond
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.
Time: 1.5hr
OPNFV/ONAP/CNTT joint session
OVP automation augmentation to support both NFVI and VNF testing and certification
Short Description: Explore requirements, architecture design, show a demo and open discussion on collabioration
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.