Service Orchestration Workflow Development and Testing~The September Developers Event is for ONAP developers, by ONAP developers. Your contributions and needs are what will drive the agenda for all of these sessions.  To build the agenda for the we are soliciting Topics for discussion from the community.  Ideally these are questions that you need a deeper understanding of in order to make progress or deep-dive information sharing in a particular area.

Topic/Question Name

  • 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)


INSTRUCTIONS:  

Please edit the section below and add any topics (using the template) that you would like to lead and/or attend. List the topic, and your name. If there is a topic that you would like discuss, but you do not feel that you can lead it, please list the topic below and indicate that you are "Interested in Attending", then indicate TBD as the "Topic Leader"

IMPORTANT DATES

Community Members provide Topic recommendations Aug. 3 - Sept. 10

Attendees self-select Topics of interest Sept. 11 - 15

Agenda set Sept. 18


TOPIC RECOMMENDATIONS



Amsterdam M4 Code Freeze Milestone Review  

        1. projects who pass M4
        2. projects that will need to be removed from Amsterdam
        3. projects that will need some adjustements


Training: On the Importance of adopting Scrum and Estimating 

Beijing Release Calendar Proposal

Enforcing an "Upstream first" approach to ONAP


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


External Standards Coordination and required actions with a different SDO   


Joint Architecture/Usecase subcommittees' meeting 


Joint Architecture/Usecase/Modeling subcommittees' meeting 


ONAP security subcommittees' meeting   


Operator Perspectives on R2 (Beijing) Architecture 


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


Usecase subcommittee meeting  


Installation hands-on


Kubernetes ONAP deployment overview and hands-on  


Modeling 


Residential vCPE Use-Case deep dive 


VoLTE Use-Case deep dive 


Microservice Bus Tutorial 


Introducing CLI Model engine &  Tutorial 


Integration / Testing 


How to use ONAP Community Lab 


R2: Non-functional requirements proposals  


ONAP Development Tutorial 


Control Loop - E2E 


LF Productivity and Process Town Hall Session  


Documentation: how to describe detailed call flows 


Future Plan for the Development of Holmes 

VoLTE E2E Service Design Demo


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


Enhancing ONAP to orchestrate container VNFs using container orchestration as VIMs 


DCAE New Features and Enhancements for Beijing and Future Releases 


SDC: R2 Backlog Discussion 


VID: R2 Backlog Discussion  

AAI: R2 Backlog Discussion  

AAI: Graph DB Evolution 


Service Orchestration Workflow Development and Testing  


TOSCA Native Service Orchestration Design 


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


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

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

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


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

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

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

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:

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