ONAP Acceleration Management Interest Group Calls

This page hosts information about zoom meetings dedicated to acceleration management interest group.

General Information

Meeting bi-weekly Wed UTC 06:00 / China 14:00 / Eastern 02:00 / Pacific 23:00(Tue)
Meeting bridge: https://zoom.us/j/9117271979

The meeting focus on three points:

Participants

Lei Huang, Shane Wang, Bin Yang

Clarified the division of labor in the acceleration management group plan and discussed the idea of acceleration management architecture/framework.
Lei Huang recommends seperating group task into two parts, first part is to determine use case and call on volunteers , second is to identify the architecture of acceleration management in ONAP .
The due date of first task is December 2018 , we welcome the demand from vendors as volunteers, and we will complete the use case collection before the deadline.
The due date of second task is October 15th, 2018, we would like to propose an acceleration management architecture before the October architecture meeting and present it at the meeting.
On the basis of the existing technology, we have discussed the idea of the framework of acceleration management, and Bin Yang suggested adding modeling part to our task.
Concrete group task description and meeting contents can be found in the slide .
Next steps: We will work on the established plan step-by-step, and clear the framework as well as use cases.

Meeting Slide

Recording

Audio only

Video and audio

chat

This is the first meeting of our interest group, focus on three points:

Participants

Lei Huang, Chuyi Guo, Margaret Chiosi, Shane Wang, Haibin Huang, Bin Yang, Bin Sun, Tina Tsou, Xu Yang

Described the problem statement of the current acceleration management and discussed the team target and next work plan.
Lei Huang recommends that the group's goal is to build end-to-end hardware acceleration management use case in ONAP D release.
Shane Wang give a proposal that they want to enable the SR-IOV and also target at the vCPE use case to see any performance benefit they can get from the SR-IOV, but it's a rough proposal.
Bin Yang suggests pushing from two directions to the discussion:1. bottom-up: First throw aside the ONAP, see how a specific use case is implemented, what functions or resources are involved in those platforms, and see if these functional resources can be found, orchestrated, and controlled through the rest API. 2.Top-down: Consider which modules the above features and resources relate to from ONAP perspective, and how these features and resource should be described and implemented abstractly.
Margaret Chiosi suggests list supported acceleration techniques, before we go use case, we should list them. And we need to create a purpose of this BOF that is different from HPA.
Haibin Huang recommends using DPDK in vCPE.

Recording

Audio only

Video and audio

chat