Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Description

Overview

The Open Networking Summit - Europe 2018 event offers two "unconference" areas for topic discussions, small-team breakouts etc.  We call this an "Unconference" because it's less about pre-conceived and pre-arranged formal presentations and instead allows for discussion topics of interest to "spring up" either closer to the event or at the event itself.

Approximately 50% of the Unconference sessions will be selected from the proposed topics below.  The other half will be scheduled at the event on first-come, first-serve basis  If you have a topic you'd like to discuss at ONS and don't already see it below, please consider adding it.  If you do see a topic below that you would like to participate in, then please add your name to the list of potential attendees.  We will use those lists to determine which topics get scheduled prior to the event. 

The Unconference areas is in the Emerald Lounge. Each "stage" area has seating for about 40 people.

This wiki is now freely available to edit.  Please feel free to add your session.  However, please do not delete or move someone else's session without their permission.


Unconference Schedule

DayTimeStageTopicPresenter(s)
Tuesday 9/2515:301OPNFV TSC New Member Welcome and Discussion of Challenges and Opportunities in the Year AheadDavid McBride, and Tim Irnich
15:302

16:101

16:102Edge Computing Group at ONS EuropeChris Price
Wednesday 9/2611:001OVP Evolution & StrategyM.Richomme, C.Donley, G.Kunz
2

13:501Doc-athonSofia Wallin & Thanh Ha
2

16:101

2ONAP TSC Introductions and Operational ImprovementsKenny Paul
Thursday 9/2711:151The collaboration between OPNFV C-RAN and O-RAN alliance for 5G whitebox  BBU program for indoor distributionRongwei Ren
2

Edge Stack Discussion for Cloud Edge and IoT

Wenjing Chu
13:501Lab as a Service Next StepsFrank Brockners
2Network Service MeshFrederick Kautz
16:051

2


List of Proposed Topics

LFN Doc-athon

  • Name:  Doc-athon: A Cross-Community Working Session Focused on Documentation

  • Description: Come and join a working session to contribute to and/or get help with LFN cross-community documentation. At the beginning of this session, we plan to briefly introduce the newly organized cross-community documentation working group (OPNFV, ODL, ONAP, FDio, etc), recap the differences between documentation created by the Linux Foundation vs. open source projects, and review recent improvements in Linux Foundation Doc toolchain capabilities. After that, we plan to spend the bulk of the time doing “hands-on” cross-community documentation. This would include reviewing & prioritizing the list of common Jira’s to be worked, and developing and testing new content with participants. This will also be an opportunity for sharing recommended practices (and those to avoid) as well as proposing new ideas for additional tool chain automation.
  • Topic Leader: Thanh Ha, and Sofia Wallin
  • 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 TSC New Member Welcome and Discussion of Challenges and Opportunities in the Year Ahead

  • NameOPNFV TSC New Member Welcome and Discussion of Challenges and Opportunities in the Year Ahead
  • Description: Following the TSC election, this is an opportunity to gather both former and new TSC members, as well as interested community  members, to have an informal discussion about the state of OPNFV and the road ahead.  Note that this is NOT a formal TSC meeting and there will be no votes or decisions made.
  • Topic LeaderTim IrnichDavid McBride
  • 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 TSC Introductions and Operational Improvements

  • Name: ONAP TSC Introductions and Operational Improvements
  • Description: As recommended at the Sept. 6th TSC Meeting, meet new members and an informal review the operational improvement recommendations from the Casablanca Developer Forum which were deferred until the new TSC was elected. Note that this is NOT a formal TSC meeting and there will be no votes or decisions made.
  • Topic Leader: Kenny Paul
  • 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.


Lab-as-a-Service - Next steps


PRouter - disaggregating big routers to enable “All IP CloudCO”

  • Name: PRouter - disaggregating big routers to enable “All IP CloudCO”
  • Description: Edge computing and NFV will play a major role in the evolution of the telcom operators and new concepts like CORD and CloudCO are being developed to best serve these use cases.  But while today common architectures are inspired by the big DC architectures which is L2, with an overlay network, CloudCO traffic patterns may require a different approach.

    Since CloudCO traffic pattern will be based on chains of VNFs, an “All IP” architecture may greatly simplify the CloudCO operation to greatly reduce the OPEX.

    In this session we will introduce PRouter architecture, a novel approach that disaggregate big routers and how it enable the “All IP CloudCO” use case

Edge Stack Discussion for Cloud Edge and IoT

OVP Evolution and Strategy

 The collaboration between OPNFV C-RAN and O-RAN alliance for 5G whitebox  BBU program for indoor distribution

  • Name: 5G whitebox  BBU program for indoor distribution
  • Description: OPNFV C-RAN project will cooperate with O-RAN alliance for evolving radio acccess networks— making them more open and smarter than previous generations.  Additional virtualized network elements with open, standardized interfaces will be key aspects of the reference designs. Technologies from open source and open whitebox network elements will be important software and hardware components of these reference designs.

    In OPNFV C-RAN project, we will focus on the virtualized network element and standardized interface. we will introduce the architecture of 5G whitebox BBU, including the description for each function component and the specific development plan in  C-RAN project.

Network Service Mesh

  • Name: Network Service Mesh
  • Description: NSM is a new project aiming to provide for L2/L3 networks what existing service mesh's such as Isito and Linkerd provide for L4/L7. NSM is a new project, having just begun in late April of 2018. We are making progress towards an initial early release before the end of 2018. This session will be for folks who are interested in learning more about NSM and how to contribute.
  • Topic Leader: Kyle Mestery (Kyle Mestery ) and Frederick Kautz
  • 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.
  • Date: This Unconference session will ideally be held on Thursday. Wednesday the topic leaders are presenting on NSM at the main conference, so Thursday is a good day to explore NSM in more detail.

Sample Design Forum Discussion Topic

  • Name: Sample Name (eg Improving Boron Documentation)
  • Description: Description of the topic and the objective/outcome desired at the end of the discussion.
  • Topic Leader: The person that is knowledgeable enough to lead and moderate this discussion.
  • 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.
    • First Last
    • First Last


Table of Contents