Versions Compared

Key

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

...

Agenda set Sept. 18

...

TOPIC RECOMMENDATIONS


Anchor
TH3
TH3


Amsterdam M4 Code Freeze Milestone Review  

  • Description: M4 Code Freeze Review of all Amsterdam Projects. TSC will vote on the projects and depending on the findings, TSC will need to decide on:

...

  • Targeted Audience: anyone but PTLs and TSC voting members attendance is expected. In case a PTL cannot physically attend, please delegate one committer who can answer questions.
  • Date: ThursdayWednesday, Sept 28 27 for 8 am 1 pm to 12 5 pm
  • Topic Leader: Gildas Lanilis gildas.lanilis@huawei.com
  • Volunteer Note Taker: 
  • Estimated Duration: 4 hours
  • Link to data Source (if applicable): Gildas will publish the M4 findings on WednesdayTuesdsay, Sept 2726
  • Interested to attend:

Training: On the Importance of adopting Scrum and Estimating

  • Description: Discussion on the benefits of applying Scrum techniques and Poker Planning for Estimating.
    1. Why is Scrum important for the Team. How to apply Scrum for distributed Team
    2. You can't swallow more that you can shew: Estimating with Poker Planning will make the team more realistic.
  • Date: TBD
  • Topic Leader: Gildas Lanilis gildas.lanilis@huawei.com
  • Volunteer Note Taker: 
  • Estimated Duration: 2 hours
  • Link to data Source (if applicable): Gildas will publish deck prior to training.
  • Interested to attend:
    • Gildas Lanilis

Beijing Release Calendar Proposal

Enforcing an "Upstream first" approach to ONAP

  • 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.
  • Volunteer Note Taker: First Last  email
  • Estimated Duration:
  • Link to data Source (if applicable)
  • Interested to attend:

External Open Source collaboration (OPNFV, ODL, etc.) and required actions 

Anchor
M6
M6


Training: On the Importance of adopting Scrum and Estimating 

  • Description: Discussion on the benefits of applying Scrum techniques and Poker Planning for Estimating.
    1. Why is Scrum important for the Team. How to apply Scrum for distributed Team
    2. You can't swallow more that you can shew: Estimating with Poker Planning will make the team more realistic.
  • Date: TBD
  • Topic Leader: Gildas Lanilis gildas.lanilis@huawei.com
  • Volunteer Note Taker: 
  • Estimated Duration: 2 hours
  • 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. (Jamil Chawki for OPNFV)
  • Volunteer Note Taker: First Last  email
  • Estimated Duration:
  • Link to data Source (if applicable): Gildas will publish deck prior to training.
  • Interested to attend:

External Standards Coordination and required actions with a different SDO 

Beijing Release Calendar Proposal

Joint Architecture/Usecase subcommittees' meeting 

  • Description: Jointly identify key features and requirements exposed by the R2 use case and/or by the release 
  • Topic Leader: Alla Goldner/Chris Donley
  • Volunteer Note Taker: First Last  email
  • Estimated Duration:
  • Link to data Source (if applicable)
  • Interested to attend:
    • Vimal Begwani
    • Margaret Chiosi
    • Andrei Kojukhov
    • Gil Hellmann
    • Alex Vul
    • Chuanyu Chen

Joint Architecture/Usecase/Modeling subcommittees' meeting 

Enforcing an "Upstream first" approach to ONAP

  • 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.
  • Volunteer Note Taker: 
  • Description: First synchronization on Release plans
  • Topic Leader: Alla Goldner/Chris Donley/Hui Deng
  • Volunteer Note Taker: First Last  email
  • Estimated Duration:
  • Link to data Source (if applicable)
  • Interested to attend:
  • Zhuoyao Huang
  • Seshu Kumar Mudiganti
  • Vimal Begwani
  • Margaret Chiosi
  • Andrei Kojukhov
  • Gil Hellmann
  • Alex Vul
  • Hui Deng
  • Thinh Nguyenphu
  • Chuanyu Chen
  • HuabingZhao

ONAP security subcommittees' meeting 

...

Anchor
TH11
TH11


External Open Source collaboration (OPNFV, ODL, etc.) and required actions  

  • 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. (Jamil Chawki for OPNFV)
  • Volunteer Note Taker: First Last  email
  • Estimated Duration:

...

  • Link to data Source (if applicable)
  • Interested to attend:

...

R2 (Beijing) Architecture

  • Description: A discussion to firm-up open issues in the R2 architecture and status.
    • Get alignment on Orchestration (Resource / Service Orchestration)
    • Get a better alignment between App-c and VF-C controllers
    • Agree on high level objectives and guidelines for introducing new controller
  • Topic Leader: Vimal Begwani & Jamil Chawki
  • Volunteer Note Taker: First Last  email
  • Estimated Duration: 1 hour presentation for information of current state, but also a more indeep parallel workshop.
  • Link to data Source (if applicable)
  • Interested to attend:

R2 (Beijing) use cases/platform capabilities first presentation to the TSC 

Anchor
TH6
TH6


External Standards Coordination and required actions with a different SDO   

Usecase subcommittee meeting 

  • Description: R2 desired ONAP Platform capabilities and use cases to show those capabilities 
  • Topic Leader: Alla Goldner
  • Volunteer Note Taker: First Last  email
  • Estimated Duration: 2 hours
  • Link to data Source (if applicable)
  • Interested to attend:
    • Vimal Begwani
    • Margaret Chiosi
    • Andrei Kojukhov

Installation hands-on

  • Description: Sharing on ONAP installation
  • Topic Leader: The person that is knowledgeable enough to lead and moderate this discussion.
  • Volunteer Note Taker: First Last  email
  • Estimated Duration: 2h
  • Link to data Source (if applicable)
  • Interested to attend:

Kubernetes ONAP deployment overview and hands-on

Modeling

Residential vCPE Use-Case deep dive

VoLTE Use-Case deep dive

Microservice Bus Tutorial

Anchor
W3
W3


Joint Architecture/Usecase subcommittees' meeting 

Anchor
W4
W4


Joint Architecture/Usecase/Modeling subcommittees' meeting 

  • Description: First synchronization on Release plans
  • Topic Leader: Alla Goldner/Chris Donley/Hui Deng
  • Volunteer Note Taker: First Last  email
  • Estimated Duration: 2 hours

...

  • Link to data Source (if applicable)
  • Interested to attend:

...

Anchor
TH10
TH10


ONAP security subcommittees' meeting   

  • Description: A discussion and feedback on ONAP security topics:  Static Code Scanning; CII Badiging program certification feedback (CLAMP team); Credential Management
  • Topic Leader: Stephen Terrill; (together with a CLAMP team memember)
  • Volunteer Note Taker: Pawel Pawlak pawel.pawlak3@orange.com 
  • Estimated Duration: 1 hour

Introducing CLI Model engine &  Tutorial

  • Description: As part of this session, audience will learn about the CLI model engine capabilities and how to develop ONAP commands using it just by writing YAML file with zero line of code, CLI model engine produce Commands directly from YAML.
  • Topic Leader: user-67d6f
  • Volunteer Note Taker: user-67d6f
  • Estimated Duration: 1h 
  • Link to data Source (if applicable)
  • Interested to attend:

Integration / Testing

How to use ONAP Developer Lab

R2: Non-functional requirements proposals 

  • Description: Presenting and further gathering of R2 non-functional requirements as candidates for R2
  • Topic Leader: Alla Goldner, Chris Donley
  • Volunteer Note Taker: eric.debeau@orange.com
  • Estimated Duration: 1h 
  • Link to data Source (if applicable)
  • Interested to attend:
    • Vimal Begwani
    • Margaret Chiosi
    • Jing Wang
    • Alex Vul

ONAP Development Tutorial

  • Description: Development environment setup, testing, ONAP development flow, Vagrant, etc. will be introduced in this session.
  • Topic Leader: The person that is knowledgeable enough to lead and moderate this discussion.
  • Volunteer Note Taker: First Last  email
  • Estimated Duration: 2h 
  • Link to data Source (if applicable)
  • Interested to attend:

    Control Loop - E2E

    • Description: Let's close the gaps from design to runtime for supporting current and future control loops.
    • Topic Leader: Pam Dragosh
    • Volunteer Note Taker: First Last  email
    • Estimated Duration: 2h 
    • Interested to attend:

    LF Productivity and Process Town Hall Session

    • Description:  Everyone has their favorite tool they want to use to work and communicate more efficiently.   The LF IT Department gets requests to add new tools or functiuonaluty on an almost daily basis, but accomodating all of these isn't feasable.  We need a more complete strategy for supporting your needs and this Monday session is intended to gather community input and share ideas on what is working well and can be improved upon in the area of tools and processes.  NOTE: This is not a technical "how-to" session.
    • Topic Leader:Kenny Paul  Tech. Program Manager, The Linux Foundation
    • Volunteer Note Taker: First Last email
    • Estimated Duration: 1hr
    • Interested to attend:

    Documentation: how to describe detailed call flows 

    • Description: To undestrand the various ONAP component inteactio, call flows description are very impôrtant. They are currenly used in various projects  and use-cases. Various tools are used to describe call flows with various levels of details. This session will present a way to describe some detailed call flows with API calls between various components using PlantUML.
    • Date: TBD
    • Topic Leader: eric.debeau@orange.com
    • Volunteer Note Taker: 
    • Estimated Duration: 30'
    • Interested to attend:
      • Gildas Lanilis
      • Vimal Begwani

    Future Plan for the Development of Holmes

    • Description:  The basic analysis capability of Holmes will be available by R1. We want to discuss how to enhance the functionalities to make Holmes be able to support more use cases and scenarios. Besides, we want to have a brief introduction on the vision of a smarter and more general analysis application based on the big data components provided by the ONAP community. 
    • Topic Leader: Guangrong Fu
    • Volunteer Note Taker: First Last email
    • Estimated Duration: 1hr
    • Interested to attend:

    End-to-End Model Driven VNF Lifecycle Management/Modeling

    ...

    Anchor
    W5
    W5


    Operator Perspectives on R2 (Beijing) Architecture 

    Anchor
    W7
    W7


    R2 (Beijing) use cases/platform capabilities first presentation to the TSC 

    Anchor
    TH15
    TH15


    Usecase subcommittee meeting  


    Installation hands-on

    Anchor
    M8
    M8


    Kubernetes ONAP deployment overview and hands-on  

    Anchor
    TH2
    TH2


    Modeling 

    Anchor
    T2
    T2


    Residential vCPE Use-Case deep dive 


    VoLTE Use-Case deep dive 

    Anchor
    M2
    M2


    Microservice Bus Tutorial 

    Anchor
    M3
    M3


    Introducing CLI Model engine &  Tutorial 

    • Description: As part of this session, audience will learn about the CLI model engine capabilities and how to develop ONAP commands using it just by writing YAML file with zero line of code, CLI model engine produce Commands directly from YAML.
    • Topic Leader: user-67d6f
    • Volunteer Note Taker: user-67d6f
    • Estimated Duration: 1h 
    • Link to data Source (if applicable)
    • Interested to attend:

    Anchor
    T1
    T1


    Integration / Testing 

    • Description: This session will give an overview of ONAP status from Integrtaion / Testing point of view:
      1. ntegration testing process and its status:
        1. UT
        2. CSIT
        3. Integration lab, this includes pair testing rules for each project, this includes a brief on how to use the lab in general, Stephen and Yang will give details later
        4. End to End lab status overview for vCPE, VoLTE  (deep dive will be covered in another two sessions) and vFW / vDNS
        5. Integration deployment strategy for Amsterdam: assets requirement and deployment topology, quick review of how to use heat template to deploy ONAP in Integration lab
      2. Integration testing practice and results from Orange open lab

    Anchor
    M4
    M4


    How to use ONAP Community Lab 

    Anchor
    W2
    W2


    R2: Non-functional requirements proposals  

    Anchor
    M1
    M1


    ONAP Development Tutorial 

    Anchor
    T8
    T8


    Control Loop - E2E 

    Anchor
    M5
    M5


    LF Productivity and Process Town Hall Session  

    • Description:  Everyone has their favorite tool they want to use to work and communicate more efficiently.   The LF IT Department gets requests to add new tools or functiuonaluty on an almost daily basis, but accomodating all of these isn't feasable.  We need a more complete strategy for supporting your needs and this Monday session is intended to gather community input and share ideas on what is working well and can be improved upon in the area of tools and processes.  NOTE: This is not a technical "how-to" session.
    • Topic Leader:Kenny Paul  Tech. Program Manager, The Linux Foundation
    • Volunteer Note Taker: First Last email
    • Estimated Duration: 1hr
    • Interested to attend:

    Anchor
    M7
    M7


    Documentation: how to describe detailed call flows 

    • Description: To undestrand the various ONAP component inteactio, call flows description are very impôrtant. They are currenly used in various projects  and use-cases. Various tools are used to describe call flows with various levels of details. This session will present a way to describe some detailed call flows with API calls between various components using PlantUML.
    • Date: TBD
    • Topic Leader: Eric Debeau - Orange
    • Volunteer Note Taker: 
    • Estimated Duration: 30'
    • Interested to attend:

    Anchor
    TH12
    TH12


    Future Plan for the Development of Holmes 

    • Description:  The basic analysis capability of Holmes will be available by R1. We want to discuss how to enhance the functionalities to make Holmes be able to support more use cases and scenarios. Besides, we want to have a brief introduction on the vision of a smarter and more general analysis application based on the big data components provided by the ONAP community. 
    • Topic Leader: Guangrong Fu
    • Volunteer Note Taker: First Last email
    • Estimated Duration: 1hr
    • Interested to attend:

    VoLTE E2E Service Design Demo

    • Description:  David Shadmi from SDC team gave a small group people a demo of VoLTE E2E service design by using early version of SDC, it was very helpful. We would like to see the same demo with the latest SDC code and bigger audience to get the feedback.  
    • Topic Leader: David Shadmi
    • Volunteer Note Taker: Yang Xu
    • Estimated Duration: 1hr
    • Interested to attend:

    Anchor
    TH1
    TH1


    End-to-End Model Driven VNF Lifecycle Management/Modeling 

    • Description: As part of the VNF SDK project, VNF modeling subproject has been focusing on establishing a consistent end-to-end approach for VNF and VNF package modeling in R2. We have identified several starting point for standardization of these models. What we need to do next is to agree on what models and/or standards are going to be applicable at what stages of the VNF lifecycle.

      We will start with the VNF model, as it is seen by VNF developers, inclusive of compute/storage/network hardware requirements, telemetry and policy specification, and identified how this information is ingested and trasformed into other models as part as part of VNF on-boarding (SDC), instantiation (SO/VF-C/Optimization/Policy) and operation (APPC/VFC/Optimization/Policy).

      We will also need to understand how policies and telemetry apply across the VNF management lifecycle, at what point they are defined, who gets to define them and how they are blended/federated with policies already provided during VNF on-boarding.

    Anchor
    T9
    T9


    Enhancing ONAP to orchestrate container VNFs using container orchestration as VIMs 

    • Description: Release 1 ONAP instantiates VNFs as VMs in compute farm using VIMs such as Openstack which manages VM. Increasing VNF density on each node, need for multiple networks/slices, Services using SFC and reduced bringup & network latency requirements in market such as 5G and vCPE  are driving container based VNFs.  This project proposal is to enhance ONAP to support VNFs as containers in addition to VNFs as VMs by container orchestration as VIM instead of VM manager like openstack.
      • Objective/Outcome desired:
        • Get consensus on crawl/walk/run direction.
        • Get agreement on K8S as container VIM in R2
        • Get feedback on proposed architecture and changes to various ONAP projects.
        • Get an understanding that VNFs as container is needed for ONAP R-2 use cases(5G-RAN and vCPE)

    Anchor
    TH9
    TH9


    DCAE New Features and Enhancements for Beijing and Future Releases 

    Anchor
    TH13
    TH13


    SDC: R2 Backlog Discussion 

    Anchor
    TH8
    TH8


    VID: R2 Backlog Discussion  

    • Description: Presenting and further gathering of R2 candidate requirements
    • Topic Leader: David Shadmi 
    • Volunteer Note Taker: 
    • Estimated Duration: 1 hours
    • Link to data Source (if applicable)
    • Interested to attend:

    Anchor
    TH44
    TH44

    AAI: R2 Backlog Discussion  

    • Description: Presenting and further gathering of R2 candidate requirements
    • Topic Leader:Colin Burns
    • Volunteer Note Taker: 
    • Estimated Duration: 1 hours
    • Link to data Source (if applicable)
    • Interested to attend:

    Anchor
    TH14
    TH14

    AAI: Graph DB Evolution 

    • Description: Discuss Beijing plans to move to JanusGraph, migration strategies, etc.
    • Topic Leader: Jimmy Forsyth
    • Volunteer Note Taker: 
    • Estimated Duration: 1 hours
    • Link to data Source (if applicable)
    • Interested to attend:
           

    Anchor
    TH7
    TH7


    Service Orchestration Workflow Development and Testing  

    Anchor
    T10
    T10


    TOSCA Native Service Orchestration Design 

    Anchor
    TH5
    TH5


    ONAP Modeling: long-term strategy vs short-term tactics  


    • Description: Discuss goals, challenges and approaches to define an ONAP modeling long-term strategy (R2 and beyond), with the emphasis on E2E service automation, in sync with long-term architecture and driven by ONAP Service Provider requirements, and the short-term tactics (R2) in support of the long-term strategy; consider requirements, architecture, info models, data models, and DSLs in this order, and discuss the landscape of standards and open source communities contributing to them. Make specific long-term strategic, as well as specific short-term tactical recommendations for ONAP and other SDOs/open source communities.
    • Topic Leader: Michael Brenner, Cloudify, michael@cloudify.co
    • Volunteer Note Taker: First Last  email
    • Estimated Duration: 1.5 hrs
    • Link to data Source (if applicable)
    • Interested to attend:

    Workshop Title: ONAP Multi Cloud Architectural vision for R2 and beyond

    Goal:                               Advance Multi Cloud beyond the current proxy implementation to address ONAP platform level issues across all use cases

    Workshop Lead:            VMware

    Primary Contact:           Ramki Krishnan, VMware, ramkik@vmware.com

    Estimated Duration:      3 hrs.

    Desired Scheduling:     Before Architecture and TSC meetings. After lunch scheduling is desired since some folks are connecting from US and may not be able to attend in person. 

    Interested in Attending:

    Slides: ONAP-mc-workshop-agenda.pdf

    Minutes on Multi-Cloud follow up and R2 scope discussion (09/28/2017): Multi-Cloud follow up and R2 discussion.pdf

    Anchor
    T4
    T4

    Subtopic 1:   Multi-Cloud Architectural Vision Introduction 

    Description:   This session will focus on discussion of the evolution of the Multi-Cloud framework for R2 and beyond, to address some of the platform gaps and move towards a more extensible and consistent cloud mediation layer. We would like to introduce a few key focus areas for this evolution, both in term of the use cases, architectural design principles, and integrations.

    Architectural focus: Model Driven API for cloud infrastructure, Standardized cloud telemetry management, and policy driven cloud agnostic deployment.

    Deep-dive subtopics (2, 3 and 4) towards achieving this vision are listed below for convenience

    • Performance & Isolation - "Towards a performance-aware and portable cloud-agnostic Infrastructure"
    • SDN - "Architectural options for Multi-vendor SDN Controller and Multi Cloud Deployments in a DC"
    • FCAPS Telemetry - "Standardized Infrastructure class statistics Model" 

    Suggested Audience:      ONAP-OF, OOM, SDN-C, SO, VF-C, APP-C, DMaaP

    Estimated Duration:        1.5 hrs

    Subtopic Lead:                 VMware

    Presenters:                       AT&T, VMware, Wind River, Intel

    Slides:                               ONAP-mc-intro.pdf

    Anchor
    T5
    T5


    Subtopic 2: Performance & Isolation - "Towards a performance-aware and portable cloud-agnostic Infrastructure" 

    Description:                    Multi-vendor cloud portability and interoperability while delivering performance is a mandatory feature of distributed DC deployments. The practical challenge in achieving this goal is the lack of standardization of Platform-aware and QoS features, for example extra specs in OpenStack, which results in a vertically integrated solution. This session will focus on how Multi Cloud can offer policy standardization and translation as a microservice for platform-aware and QoS features (hard-guarantee, min-guarantee, best effort etc.) for addressing this challenge and how NFV application classes such as IMS/EPC Control/Data Plane can benefit from this framework.

    Suggested Audience:     VNF Requirements/Modelling, A&AI, Policy, SO, VF-C, APP-C, SDC

    Estimated Duration:       .5 hrs.

    Subtopic Lead:                Bin Yang, Wind River, bin.yang@windriver.com 

    Presenters:                      Wind River, Intel

    Slides:                              ONAP-mc-performance-isolation.pdf

    Anchor
    T6
    T6

    Subtopic 3:  SDN - "Architectural options for Multi-vendor SDN Controller and Multi Cloud Deployments in a DC" 

    Description:                    Multi-vendor components in a DC including underlay, overlay, gateway and SDN Controllers for the same pose various architectural challenges in terms interoperability, security etc. This session will focus on an in depth analysis of the architectural options including related efforts such as OpenStack Gluon. This proposal also addresses communication latency-bound multi-side physical DCs which can be treated as a single virtual DC for management purposes.

    Suggested Audience:    SDN-C, SO, VF-C, APP-C, SDC, OOM

    Estimated Duration:       .5 hrs.

    Subtopic Lead:               AT&T

    Presenters:                     AT&T, Intel, Huawei, VMware

    Slides:                             ONAP-mc-sdn.pdf

    Anchor
    T7
    T7

    Subtopic 4:   FCAPS Telemetry - "Standardized Infrastructure Class statistics Model" 

    Description:                   This session will focus on a hierarchical cloud-platform-aware architectural framework with separation of collection, storage, processing functions and real-time vs historical analytics components. In this framework, Multi Cloud will deliver a standardized infrastructure class statistics model for driving ONAP component/VNF placement/change management across distributed DC multi cloud instances through ONAP-OF, DCAE and other components. The benefit to ONAP platform, across all use cases, will be delivering the best performance and security while minimizing cost.

    Suggested Audience:      ONAP-OF, DCAE, A&AI, Policy, OOM, SDN-C, DMaaP

    Estimated Duration:        .5 hrs.

    Subtopic Lead:                 AT&T

    Presenters:                       VMware, Wind River, AT&T, Intel

    Slides: ONAP-mc-fcaps.pdf

    Anchor
    TH4
    TH4

    Kubernetes vs Dockers Swarm supporting ONAP-OOM on multi-cloud multi-stack environment 

    Description:  ONAP was set originally to support multiple container platform and cloud through TOSCA. In R1 ONAP and OOM is dependent completely on Kubernetes. As there are other container platforms such as Docker Swarm that are gaining more wider adoption as a simple alternative to Kubernetes. In addition operator may need the flexibility to choose their own container platform and be open for future platform. We need to weight the alternatives and avoid using package managers as Helm that makes K8s mandatory.

    The use of TOSCA in conjunction with Kubernetes provides that "happy medium" where on one hand we can leverage Kubernetes to a full extent while at the same time be open to other alternative. In this workshop, we will compare Kubernetes with Docker Swarm and walk through an example of how ONAP can be set to support both platforms using TOSCA.

                

    Suggested Audience:    SDN-C, SO, VF-C, APP-C, SDC, OOM

    Estimated Duration:       1 hrs.

    Desired Scheduling:      Before Architecture and TSC meetings.

    Topic Lead               :      Cloudify

    Presenters               :      Cloudify, AT&T (to confirm)

    Interested in Attending:

    SLIDES 

    Amsterdam Release Lesson Learned

    Description:  The purpose of this topic is to share preliminary Amsterdam Release Lesson Learned, to reflect together on how everything went and then to decide what changes we want to make in the next ONAP release (i.e. Beijing), answering the following questions:

    • What worked well?
    • What did not work well?
    • What actions can we take to improve our process going forward?

    Suggested Audience:    Anyone but ONAP Release Manager and PTLs are expected

    Estimated Duration:       1 hrs.

    Desired Scheduling:      No preference

    Topic Leader:     Catherine Lefèvre (AT&T)

    Volunteer Note Taker: Gervais-Martial Ngueko (AT&T)

    Interested in Attending:



    VID: R2 Backlog Discussion  

    • Description: Presenting and further gathering of R2 candidate requirements
    • Topic Leader: David Shadmi 
    • Volunteer Note Taker: 
    • Estimated Duration: 1 hours
    • Link to data Source (if applicable)
    • Interested to attend:

    Enhancing ONAP to orchestrate container VNFs using container orchestration as VIMs

    • Description: Release 1 ONAP instantiates VNFs as VMs in compute farm using VIMs such as Openstack which manages VM. Increasing VNF density on each node, need for multiple networks/slices, Services using SFC and reduced bringup & network latency requirements in market such as 5G and vCPE  are driving container based VNFs.  This project proposal is to enhance ONAP to support VNFs as containers in addition to VNFs as VMs by container orchestration as VIM instead of VM manager like openstack.
      • Objective/Outcome desired:
        • Get consensus on crawl/walk/run direction.
        • Get agreement on K8S as container VIM in R2
        • Get feedback on proposed architecture and changes to various ONAP projects.
        • Get an understanding that VNFs as container is needed for ONAP R-2 use cases(5G-RAN and vCPE)

    DCAE New Features and Enhancements for Beijing and Future Releases

    • Description: Discussion for new/enhancing features and priorities for Beijing and future releases.  
    • Topic Leader:  Lusheng Ji
    • Volunteer Note Taker: First Last  email
    • Estimated Duration: 2 Hours
    • Link to data Source (if applicable)
    • Interested to attend:

    SDC: R2 Backlog Discussion

    • Description: Presenting and further gathering of R2 candidate requirements
    • Topic Leader: David Shadmi / Michael Lando
    • Volunteer Note Taker: 
    • Estimated Duration: 2 hours
    • Link to data Source (if applicable)
    • Interested to attend:

    VID: R2 Backlog Discussion

    • Description: Presenting and further gathering of R2 candidate requirements
    • Topic Leader: David Shadmi 
    • Volunteer Note Taker: 
    • Estimated Duration: 1 hours
    • Link to data Source (if applicable)
    • Interested to attend:

    AAI: Graph DB Evolution

    • Description: Discuss Beijing plans to move to JanusGraph, migration strategies, etc.
    • Topic Leader: Jimmy Forsyth
    • Volunteer Note Taker: 
    • Estimated Duration: 1 hours
    • Link to data Source (if applicable)
    • Interested to attend:

    Service Orchestration Workflow Development and Testing

    • Description: Review of workflow development methods and tools for SO
    • Topic Leader: Rob Daugherty (rd472p@att.com) / Seshu Kumar (seshu.kumar.m@huawei.com)
    • Volunteer Note Taker:
    • Estimated Duration: 1 hour
    • Link to data Source (if applicable)
    • Interested to attend:

    Workshop Title: ONAP Multi Cloud Architectural vision for R2 and beyond

    Goal:                               Advance Multi Cloud beyond the current proxy implementation to address ONAP platform level issues across all use cases

    Moderator(s):                 VMware, Wind River

    Primary Contact:           Ramki Krishnan, VMware, ramkik@vmware.com

    Desired Scheduling:     After lunch scheduling is desired since some folks may not be able to attend in person. 

    Interested in Attending:

    • Vimal Begwani - AT&T
    • Margaret Chiosi - Huawei
    • Sastry Isukapalli - AT&T
    • Ankitkumar Patel - AT&T
    • Danny Lin - VMware
    • Sumit Verdi - VMware
    • Xihui Li - VMware
    • Bin Hu - AT&T
    • Gil Hellmann - Wind River
    • Sarat Puthenputa - AT&T
    • Shankar Narayanan - AT&T
    • Jing Wang - Huawei
    • Isaku Yamahata - Intel
    • Alex Vul - Intel
    • Rajesh Gadiyar - Intel
    • Srinivasa Addepalli - Intel
    • Bin Yang - Wind River
    • Chuanyu Chen - Huawei

    Topic 1:   Multi-Cloud Architectural Vision Introduction

    Description:   This session will focus on discussion of evolution of the Multi Cloud framework for R2 and beyond, to address some of the platform gaps and move towards a more extensible and consistent cloud mediation layer. We would like to introduce a few key focus areas for this evolution, both in term of the use cases, architectural design principles, and integrations.

    Architectural focus: Model Driven API for cloud infrastructure, Standardized cloud telemetry management, and policy driven cloud agnostic deployment.

    Deep-dive topics (2, 3 and 4) towards achieving this vision are listed below for convenience

    • Standardized Infrastructure class statistics Model
    • Towards a performance-aware and portable cloud-agnostic infrastructure
    • Architectural options for Multi-vendor SDN Controller and Multi Cloud Deployments in a DC

    Suggested Audience:     ONAP-OF, OOM, SDN-C, SO, VF-C, APP-C, DMaaP

    Estimated Duration:        2 hrs.

    Desired Scheduling:       Before topics 2, 3, 4, Architecture and TSC meetings.

    Topic Lead               :       VMware

    Interested in Attending:

    Topic 2:   Standardized Infrastructure Class statistics Model

    Description:                   This session will focus on a hierarchical cloud-platform-aware architectural framework with separation of collection, storage, processing functions and real-time vs historical analytics components. In this framework, Multi Cloud will deliver a standardized infrastructure class statistics model for driving ONAP component/VNF placement/change management across distributed DC multi cloud instances through ONAP-OF, DCAE and other components. The benefit to ONAP platform, across all use cases, will be delivering the best performance and security while minimizing cost.

    Suggested Audience:     ONAP-OF, DCAE, A&AI, Policy, OOM, SDN-C, DMaaP

    Estimated Duration:        1 hrs.

    Desired Scheduling:       After Topic 1 and Before Architecture and TSC meetings.

    Topic Lead               :       AT&T

    Presenters               :       VMware, Wind River, AT&T, Intel

    Interested in Attending:

    Topic 3:  Towards a performance-aware and portable cloud-agnostic infrastructure

    Description:                    Multi-vendor cloud portability and interoperability while delivering performance is a mandatory feature of distributed DC deployments. The practical challenge in achieving this goal is the lack of standardization of Platform-aware and QoS features, for example extra specs in OpenStack, which results in a vertically integrated solution. This session will focus on how Multi Cloud can offer policy standardization and translation as a microservice for platform-aware and QoS features (hard-guarantee, min-guarantee, best effort etc.) for addressing this challenge and how NFV application classes such as IMS/EPC Control/Data Plane can benefit from this framework.

    Suggested Audience:    VNF Requirements/Modelling, A&AI, Policy, SO, VF-C, APP-C, SDC

    Estimated Duration:       1 hrs.

    Desired Scheduling:      After Topic 1 and Before Architecture and TSC meetings.

    Topic Lead               :      Bin Yang, Wind River, bin.yang@windriver.com 

    Presenters               :      Wind River, Intel, VMware (to confirm)

    Interested in Attending:

    • Gil Hellmann - Wind River

    Topic 4:   Architectural options for Multi-vendor SDN Controller and Multi Cloud Deployments in a DC

    Description:                    Multi-vendor components in a DC including underlay, overlay, gateway and SDN Controllers for the same pose various architectural challenges in terms interoperability, security etc. This session will focus on an in depth analysis of the architectural options including related efforts such as OpenStack Gluon. This proposal also addresses communication latency-bound multi-side physical DCs which can be treated as a single virtual DC for management purposes.

    Suggested Audience:    SDN-C, SO, VF-C, APP-C, SDC

    Estimated Duration:       1 hrs.

    Desired Scheduling:      After Topic 1 and Before Architecture and TSC meetings.

    Topic Lead               :      VMware

    ...