Overview

The Open Networking Summit - EU 2019 event offers two "un-conference" 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.

Availability of the Unconference sessions will be limited.  While some topics may be hand selected (like a TAC meeting, if proposed for example), most 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. 

This wiki should be 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.

Schedule

The current Un-conference Schedule can be found here: TBA
If you wish to add a topic to the schedule, please post it below.
Unconference Rooms are located at Flanders Convention Center: Gorilla 4 + Gorilla 5

List of Proposed Topics

• Short Description:  CNTT reference implementation and verification in OPNFV

• Detailed Description:
  • We will use this session to drive the detailed discussion of CNTT activities in OPNFV. Major topics can include as follows (you are also welcome to add more topics)
    • CNTT progress updates, especially focusing on OPNFV related activities
    • High level discussion on OPNFV planning to engage in CNTT effort and reveal CNTT requirements
    • OPNFV feature projects planning for support of CNTT reference models and architecture
    • OPNFV installer projects gap analysis (whether the current projects will support the reference architecture in a good way?)
    • OPNFV testing project gap analysis (whether the current test cases and framework will support the verification requirement from CNTT?)
    • Next step
• Topic Leader: Fu Qiao, 
• Estimated Audience Size (15-30):
• Interested In Attending:

--------------------------------------------------------------------------------

• Short Description:  OPNFV Closed Loop Automation Working Group

• Detailed Description:
  • This sessions would help members from OPNFV closed loop automation working group to collaborate on following:
    
    • What's working good so far
    • Topics and areas of interest that could be included as part of WG
    • Intersection with other projects like ONAP, etc.
    • On going demos and future demos of interest
    • TBA
• Topic Leader: Sunku Ranganath, ... 
• Estimated Audience Size : 5-10
• Interested In Attending: please add your names (& emails) to help build the schedule
  • Sunku Ranganath, sunku.ranganath@intel.com, tohayash@redhat.com, tomi.juvonen@nokia.com

--------------------------------------------------------------------------------

• Short Description:  Test frameworks and tools for CNTT

• Detailed Description: This is continuation of discussion started in CNTT F2F meeting in Paris on OPNFV test framework strategy for CNTT reference implementations and compliance program.
  • See related thread and this point made by Georg Kunz... we need a structured way of integrating, maintaining and running specific test cases across test tools. It must be simple to call specific test cases across all OPNFV test tools. This means that ideally the OPNFV test tools agree on a common way to do this. Potential ways:
    1. All tools integrate in Xtesting
    2. All tools agree on a common API callable from some other tool
    3. Something else?
• Topic Leader: Trevor Cooper, Sridhar Rao?
• Estimated Audience Size: 5-10
• Interested In Attending: If you are interested in this discussion
  • Trevor Cooper

--------------------------------------------------------------------------------

• Short Description:   Discuss automation requirements for MEC during the whole life cycle of MEC application. 

• Detailed Description:  In this session ,i will introduce the whole MEC system with 5G Core.  Typically there will be a lot of facilities around MEC system. For instance,  local DNS system, hardware  or software firewall(if traffic from internet into MEC system , FW is needed).  When application is on boarding in MEC system, openstack or kubernetes will allocate virtual machine and container for applicaiton automatically. But the application can't supply the service right now.
  Automation requirements for MEC  to speed up the service provision procedure:
  1.  Set UPF rule automatically(traffic steering) 
  2.  Set FW  rule automatically(traffic rule)
  3.  Set DNS record automatically (DNS resolving)
  4.  others...
• Topic Leader: Jia Xuan (jiaxuan@chinamobile.com)
• Estimated Audience Size (5-10):
• Interested In Attending: If you are interested in this discussion
  • Xuan

--------------------------------------------------------------------------------

• Short Description:  One line description of topic

• Detailed Description: Detailed description of topic
• Topic Leader: name 1, name 2, ...
• Estimated Audience Size (1-15 / 15-30 / 30-50 / >50):
• 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.