Meeting Minutes
Membership
Alla Goldner alla.goldner@amdocs.com
Anatoly Andrianov anatoly.andrianov@nokia.com
Andrei Kojukhov andreik@amdocs.com
Avi Chapnick avich@amdocs.com
Brian Freeman bf1936@att.com
Chengli Wang wangchengli@chinamobile.com
Damon Li damonl@vmware.com
Eric Debeau eric.debeau@orange.com
Ethan Lynn ethanlynnl@vmware.com
Yuangxing Feng feng.yuanxing@zte.com.cn
George Lapiotis george.lapiotis@ericsson.com
Gil BULLARD wb5674@att.com
Helen Chen helen.chen@huawei.com
Hui Deng denghui12@huawei.com
Jianguo Zeng zengjianguo@huawei.com
Jimmy Forsyth James Forsyth
Jinhua Fu fu.jinhua@zte.com.cn
Joe Zhang zhang.zhou1@zte.com.cn
Jon Taylor jon.taylor@amdocs.com
John Zannos jaazannos@gmail.com
Kang Xi kang.xi@huawei.com
Lingli Deng denglingli@chinamobile.com
Liron Shtraichman lironsh@amdocs.com
Li zi li.zi30@zte.com.cn
Lv Bo lv.bo163@zte.com.cn
Maopeng Zhang zhang.maopeng1@zte.com.cn
Mark Pond mpond@amdocs.com
Mazin Gilbert mazin@research.att.com
Nagesha Subramanya nagesha.subramanya@nokia.com
Nir Rapaport Nir.Rapaport@amdocs.com
Oleg Kaplan oleg.kaplan@amdocs.com
Marc Volovic Marc.Volovic@amdocs.com
Avi Ziv Avi.Ziv@amdocs.com
Gautam Shah GAUTAMS@amdocs.com
Steven Blimkie Steven.Blimkie@amdocs.com
Tian Lee <TianL@amdocs.com>
Oliver Spatscheck spatsch@research.att.com
Sumit Verdi sverdi@vmware.com
Timo Perala timo.perala@nokia.com
Tomer Oster tomer.oster@amdocs.com
Vimal Begwani Begwani@att.com
Vivien Yang vivien.yang@intel.com
Xinhui Li lxinhui@vmware.com
Yoav Kluger yoav.kluger@amdocs.com
Yang Xu yang.xu3@huawei.com
Yan Yang yangyanyj@chinamobile.com
Yunlong Ying ying.yunlong@zte.com.cn
Yosi Ben-Tsur yosi.bentsur@amdocs.com
Zhaoxing Meng meng.zhaoxing1@zte.com.cn
Wenyao Guan guanwenyao@chinamobile.com
Yuan Liu liuyuanyjy@chinamobile.com
Tao Shen shentao@chinamobile.com
Victor Gao victor.gao@huawei.com
Xin Jin saw.jin@huawei.com
Seshu Kumar seshu.kumar.m@huawei.com
Guirong Wang wangguirong@boco.com.cn
Xiaodong Ning ningxiaodong2017@boco.com.cn
Hu Dong donghu@raisecom.com
Yannan Han hanyanan@raisecom.com
jamil chawki jamil.chawki@orange.com
Michal Pawlowski michal.pawlowski1@orange.com
Jacopo Pianigiani jpianigiani@juniper.net
Luman Wang wanglm.bri@chinatelecom.cn
Sujing Zhang zhang.sujing@zte.com.cn
Catherine Lefevre cl664y@att.com
Christophe Closset ChrisC
Gervais-Martial Ngueko Gervais-Martial Ngueko
Pamela Dragosh Pamela Dragosh
Randa Maher rx196w@att.com
Dan Timoney dtimoney@att.com
Amir Levy amir@gigaspaces.com
DeWayne Filppi DeWayne@gigaspaces.com
Arthur Berezin arthur@gigaspaces.com
Nati Shalom natis@gigaspaces.com
Huabing Zhao zhao.huabing@zte.com.cn
Heliu Zhong zhognheliu@boco.com.cn
Yuanwei Yang yangyuanwei@boco.com.cn
Jingbo Liu liujingbo@boco.com.cn
zhangxiong Zhou zhouzhangxiong@boco.com.cn
Michael O'Brien frank.obrien@amdocs.com
Anbing Zhang zhanganbing@chinamobile.com
Ying LI liying@chinamobile.com
Shasha Guo guoshasha@chinamobile.com
Evgeniy Zhukov evgeniy.zhukov@netcracker.com
Meeting logistics:
Kickoff meeting: Monday, June 19, 1500 UTC
Meeting Information:
Every Monday - 7:00am PDT, 10:00am EDT, 10:00pm China Time
IRC:
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/655429955
Or iPhone one-tap (US Toll): +16465588656,655429955# or +14086380968,655429955#
Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
Meeting ID: 655 429 955
International numbers available: https://zoom.us/zoomconference?m=CqsAwHx4CSyRanCfPHKBvf6Vslgcsn86
Use case subcommittee mailing list
onap-usecasesub@lists.onap.org
Participating in UC meetings
Use case subcommittee is contribution-driven
People can sign up for slots on the agenda
We will request people to develop proposals/presentations to discuss during meetings and via email
Use case subcommittee purpose:
Requirements Subcommittee Members
The use case subcommittee is responsible for developing use cases required for ONAP releases. This includes basic flows, VNFs and requirements, including alignment with use cases focused on VNF Requirements, along with a set of required guidelines for ONAP. It will be used as an input for developing functional architecture and detailed software architecture per release.
...
The use case subcommittee will not make decisions regarding Release’s functional architecture or internal functioning of projects. It is a support group for the TSC Chair and the TSC
...
. The use case subcommittee is advisory by nature, and not authoritative. It may provide advice to projects and to the TSC and TSC’s Architecture subcommittee.
...
The use case subcommittee operates on a rough consensus basis. If the subcommittee is unable to reach consensus on what use case to offer, the subcommittee will refer the matter to the TSC.
...
Participation
The use case subcommittee is open to all interested participants, and all meetings are open. Use case subcommittee is contribution-driven.
- People can sign up for slots on the agenda
We will request people to develop proposals/presentations to discuss during meetings and via email
Deliverables
The use case subcommittee will develop and maintain use case descriptions and any related explanatory material for ONAP releases.
Midway through a release, the use case subcommittee will provide its proposal for the use cases to be supported for the next release.
...
TSC subcommittee starting participants:
The use case subcommittee is open to all interested participants, and meetings are open.
Use case subcommittee flow:
1. Use case subcommittee discuses new use cases
2. Use case subcommittee produces use case flow diagrams, provides its view on the foreseen modules introductions/modifications and suggests potential PNFs / VNFs
3. Use case subcommittee gets feedback from the potentially effected projects including integration team on feasibility
4. Iterate back to 2
5. TSC approves the use case
6. In case a new modules or a new functionality to existing modules or a new APIs introduction is foreseen, architecture subcommittee defines the new/modified ONAP flows and the interfaces principles, based on the approved use cases (1)
7. Projects define their extended functionality and their external APIs, following those principles.
8. Detailed per-component flows are defined by the projects and projects write their user stories / implement them; Integration team continuously works with Use case subcommittee to accompany the use case development, review epics/user stories, answer questions, etc. Use case subcommittee behaves as system engineers for the use case through test start date
9. Integration team defines the gating use case based on step 8 and finalizes the PNFs / VNFs selection, with the help of use case subcommittee, architecture subcommittee, PTLs of a different ONAP projects
10. TSC approves the gating use case
11. Integration project leads (coordinates) effort to get the gating use case tested, repaired, and verified, and the results are documented.
...
Definition
Functional requirement - ONAP platform functional enrichment, enabling to build a different e2e use cases.
e2e use case - a new e2e functionality enriching ONAP platform, comprising of a different functional requirements. It can be tested e2e.
Process
Meeting logistics
Mailing List
onap-usecasesub@lists.onap.org
Meeting Information
Every Monday - 7:00am PDT, 10:00am EDT, 10:00pm China Time
Topics for discussion:
- M[x]-GATES, Score Cards, PJM, Status on Milestones
- Architecture , Requirements – TSC Bridging
- Steering Key Topics for discussion & investigation
- Testing – Evolution – Integration/Regression Dev-Test
- PTL cameos
- Release Content & Next Release Content
- Conferences Preparation, Reports, Review & Discussion
- Use Case Reports & Status
- Cross-U/C Interactions Steering topics
This would be done under assumption that different use cases/functional requirements tracks for covering their detailed work continue.
While:
- M-GATES – Discussion about the M1-2-3-4 gates. Where we are on Score Cards, PJM type discussion and topics, Status on Milestones. Bringing people together related to Use Case and where we are on the Use Cases.
- BRIDGING – tie together Architecture , Requirements, and TSC calls. Identifying those key things that come from those other calls back to what is relevant for Use Cases.
- STEERING –Steering Key Topics for discussion & investigation. Identifying what we need to be investigating.
- TESTING - Testing and Integration/Regression Dev-Test are key topics that span U/Cs. Tying in integration status, and discussion about where testing and integration needs to evolve. For example a discussion of regression testing and how that will be done, or what developments in automation of integration team means to the U/Cs.
- PTL CAMEOS – have a “schedule” of PTLs to make cameo appearances at the U/C (Monday) call and then reach out to the U/C owners to ask what they need to discuss w/ the PTLs and reserve 30min (or the whole meeting) to meet with that PTL discussion U/C topics.
- RELEASE CONTENT – the Release and Next Release Content, USE CASES/FUNCTIONAL REQUIREMENTS WISE. What potential new U/Cs are we thinking about for R5 El Alto for example.
- CONFERENCES – Discussion about Preparation and review of topics and presentations and logistics. Then after the conference discussion of Reports, Readouts, Review, and Retrospectives.
- U/C STATUS – Use Case Reports & Status
- Cross U/C INTERACTIONS and INTERDEPENDENCIES – share the Cross-U/C Interactions finding, and create Steering topics for further investigation by the U/C teams or U/C realization calls.
Use Case Subcommittee Meeting Minutes
IRC
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/655429955
Or iPhone one-tap (US Toll): +16465588656,655429955# or +14086380968,655429955#
Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
Meeting ID: 655 429 955
International Numbers
https://zoom.us/zoomconference?m=CqsAwHx4CSyRanCfPHKBvf6Vslgcsn86