Based on the community feedback from ONS North America, ONS events are now including project-based submissions in the regular ONS programing and can be submitted as part of the CFP process. There will be tracks that will be set up to focus on data plane, control plane, orchestration, analytics, and more. There will be no longer be separate Developer Summits at ONS. In order to accommodate the extra sessions, ONS Europe is being expanded to 3 days and ONS North America will be 4 days. On the ONS CFP Page, there has been additional information added with a new tab called tips for "How We Pick Submissions" (also listed below). Please bear these tips in mind when preparing your submission. Please send any questions to firstname.lastname@example.org.
How the Program Committee Picks Submissions
- Coverage of all layers of architecture and all 6 tracks is important. Abstracts should be clear and relevant to the track submitted (eg Tech or business)
- Similar topics (including opposing views) could also be grouped into a joint presentation/panel to make it interesting.
- Product Pitches are not well received and get lower ratings/scores.
- Open Source + Open Networking usage/reference including deployment examples are rated higher.
- Speaker qualification is important to tailor to the audience based on the track (eg no marketing speakers in a tech track).
- End Users get a higher priority – all things being equal.
- Future/forward-looking topics get a slight advantage along with actual deployment examples based on projects. (Note to project submissions: Any submission that simply re-iterates project content is not rated highly. Eg what is ONAP or ONAP Beijing Architecture or OPNFV Upcoming Release or Container Networking etc. This information can be obtained through TSC calls and Wiki. The goal is to show usage OR forward-looking ideas of how projects impact adjacent areas. Also, very specific open source tools for debugging or use in single vendor/user network are rated lower.
- The diversity of speakers & organizations is important.
- In a case of “conflict” (eg company submission, personal submission etc.) reviewers are asked to please use professional judgment and refrain from rating their submissions or their own company’s submissions.
- All scheduled content is confidential until the schedule comes out.
OPNFV CFP Submissions Workspace
If you a planning to submit an OPNFV-related proposal to the ONS CFP, please add it here to help ensure we are covering the OPNFV key areas and putting our best foot forward and allow LFN staff to help coordinate submissions accordingly. Please consider submissions in the following OPNFV core areas: Release process based on CD, OVP strategic Evolution, Edge, Cloud Native/K8s, Collaboration/Integration with other LFN Projects. Submissions are due Sunday, June 24!
|Submission Name||Core Area(s)||Submitter Names||Draft Abstract||Session Type (session, panel, demo, etc)||Technical Level (Beginner, Intermediate, Advanced)||Notes|
|OPNFV Hands-on||Ryota Mibu||Learn overview, installation, quick test tools of OPNFV Fraser release||Tutorial (2hours) OR Workshop (1/2 day)||Intermediate||https://etherpad.opnfv.org/p/ons_2018_eu_opnfv_handson|
Evolving CI/CD in Open Source Networking
|This session will talk about the importance of collaboration across open source communities both within developers and among decision makers and provide updates regarding OPNFV XCI and OpenCI Initiatives.||Session||Any||N/A|
|This session will talk about realizing CI/CD pipelines that span across multiple communities and give details about multi-repo patch verification using Zuul and CI/CD System Integration using events, possibly accompanied by a demo.||Session||Any||N/A|
|Evolving the OPNFV test ecosystem for future use cases|
Networking Latest Trends
The OPNFV community has developed a comprehensive set of open source test tools and test methodologies for NFVIs and VM-based cloud platforms. With the proliferation of cloud native and edge computing, we need to think about how to evolve these tools to meet the requirements of emerging and future use cases. In this talk, we will give an outlook on how the OPNFV test tool ecosystem can address new use cases and challenges, bring forward ideas and create a discussion with the community on requirements and solutions.
|Are you insured against Noisy Neighbors|
Networking Latest Trends
|The presentation will cover how OPNFV-VSPERF, OPNFV- Barometer-Collectd, RMD Client and Stress-NG are used for (a) creation and analysis of last-level-cache LLC profiles of all workloads and (b) policy-driven management of LLC resource to improve the performance and manage the noisy neighbors.||Session||Any||N/A|
OPNFV Demo Ideas Submission Workspace
There will be room for demos again in the LFN Booth at ONS Europe. Our goal again is to show compelling uses of LFN networking project technology to solve real world industry challenges. Demos that show cross-project elements (e.g. between ODL, ONAP, OPNFV, FD.io and other projects), that map to a specific industry use case, and that are endorsed by a service provider are preferred. That said, we have some room for demos that highlight the good work and value-add from projects that don't necessarily meet these criteria. Please consider submissions in the following OPNFV core areas: Release process based on CD, OVP strategic Evolution, Edge, Cloud Native/K8s, Collaboration/Integration with other LFN Projects. Submissions are due Sunday, July 8!
|Demo Name||Core Area(s)||Submitter Names||Draft Abstract||Notes|
|Lab as a Service||Collaboration/Integration||Lincoln Lavoie||Provide hands on demo of LaaS, showing how resources can be scheduled, access, modified, etc. Goal is for this to be the first public demo (maybe even the launch) of the LaaS 2.0 system.||Demo would require working internet connection and presentation screen (preferable larger than a laptop screen).|
|LFN Orange Openlab: a neutral open source catalyst & playground||Collaboration/Integration|
Orange officially launched an openlab beginning 2018. This openlab is used to support several LFN projects: OPNFV, ONAP and Acumos. It was already used to support OPNFV CI in Danube, has been used by VNF actors (tuning of vEPC testcase by rebecca for OPNFV Fraser) and used for OPNFV plugfests.
It has been built using OPNFV best practices reusing infrastructure automation (XCI on bare metal), scenario installation, test framework reuse (Functest and Yardstick).
It also provides an ONAP solution for community members. Since February about 80 accounts have been created. More than 50% corresponds to external users including vendors, telcos and academics.
Next step consists in integrating acumos CI pipelines.
The demo deals with user management, supervizion, CI/CD pipelines (to deploy and test the infrastructure and the orchestration solution)