August 14, 2017

Owned by Alla.Goldner
Last updated: Aug 15, 2017
2 min read

 

  1. R1 use cases: Status and actions, required from Use case subcommittee (vCPE: Yoav Kluger, vVoLTE: Yang Xe). Yang and Yoav presented status of vVoLTE and Residential vCPE use cases. Both teams continue their meetings with a different projects. vCPE wiki page will be significantly updated this week, to align with all recent agreements with a different projects. vVoLTE team has continuous discussions with SDC and So teams. The new item added this week to vVoLTE urgent to-be-resolved topics – DCAE/Usecase UI interaction and the corresponding meeting is scheduled.   

 

  1. ONAP Platform missing capabilities : We agreed on the following:

 

  1.  

    • We will continue update the list of missing capabilities under https://lf-onap.atlassian.net/wiki/display/DW/Missing+Platform+capabilities. All – please work on including missing capabilities in this list, including descriptions of the functionality

    • In parallel, R2 Architecture requirements list will be worked on to eventually align use cases/missing capabilities proposals with the architecture requirements. It is located under   https://lf-onap.atlassian.net/wiki/display/DW/Architecture+Requirements+for+R2+use+cases . We ask Architecture subcommittee to work on this task.

    • Ramki will bring proposal on R2 document skeleton (e.g. to include use cases, missing capabilities, architecture requirements proposals etc.). We will then decide if we move to shared document mode of work or we continue using and updating wiki.

 

 

  1. R2 use cases proposals and task forces status

  1.  

    • Enterprise vCPE

    • 5G

    • ONAP Change management

    • SD-WAN

Enterprise vCPE, 5G progress and statuses were presented. SD-WAN use case was presented for the first time.

AI:

  1. ONAP Change management (Emmanouil was not attending the call) – please present status, if possible, by updating wiki/sending email

  2. SD-WAN

    1. Define requirements for R2, and other for future possible implementation

    2. Extend use case definition by describing ONAP flows

    3. Work jointly with Enterprise vCPE on potentially harmonizing requirements

    4. 4.       All task forces – when you schedule dedicated meetings, please publish it on wiki/by email

 

  1. General topics

  1.  

    • Criteria for use case selection (for your information, R1 use cases criteria for selection are here: https://lf-onap.atlassian.net/wiki/display/DW/Release+1+Use+Cases ), please add what we should put emphasize on when bringing use cases, in light of ONAP Platform missing capabilities discussion

    • Architecture/Usecase subcommittees joint meeting

AI:

  1. Please fill in answers for the use cases under https://lf-onap.atlassian.net/wiki/display/DW/Questions+and+answers

  2. Please add your questions related to architecture requirements for R2 under the same link

  • Meanwhile, in absence of TSC guidance (hopefully, it will be presented this Thursday to TSC), we need to know how we move forward. The proposal is:

  1. 1.       Concentrate on R1 missing (and needed) platform capabilities proposals https://lf-onap.atlassian.net/wiki/display/DW/Missing+Platform+capabilities and on architecture requirements for R2 https://lf-onap.atlassian.net/wiki/display/DW/Architecture+Requirements+for+R2+use+cases

  2. 2.       Concentrate on description what are missing platform capabilities per R2 brought use cases proposals

(We will then prioritize both lists above those for R2 implementation)

  1. 3.       Concentrate on harmonization, if possible, between R2 proposed use cases and on R1 with R2 use cases