The July Virtual 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.
...
Description: VF-C have identified some gaps between the objects VF-C need to store and the models that A&AI already exists. Need to discuss with A&AI team on how to map these gaps.
- Topic Leader: Yan Yang(yangyanyj@chinamobile.com), Weitao Gao(victor.gao@huawei.com)
- Volunteer Note Taker: First Last email
- Estimated Duration: 2 hour
- Link to data Source (if applicable)
- Interested In Attending: We would like to invite A&AI,VF-C and other related projects to join in this topic
- First Last email
- Lingli Deng (denglingli@chinamobile.com)
- Tao Shen (shentao@chinamobile.com)
- Kanagaraj M kanagaraj.manickam@huawei.com
- Subhash Kumar Singh (subhash.kumar.singh@huawei.com)
- Chuanyu Chen (chenchuanyu@huawei.com)
- James Forsyth
- Eric Multanen eric.w.multanen@intel.com
- Murat Parlakisik
- Nagesha Subramanya nagesha.subramanya@nokia.com
- Amy Zwarico az9121@att.com
- Moshe Hoadley moshehoa@amdocs.com
- t
OOM & MSB Interaction
- Description:
According to the conclusion of service registry discussion between MSB and OOM, OOM and MSB manage the process and service separately at different levels and these two projects need to cooperate to use the Consul as the service registry to provide the service endpoints info for MSB. So MSB can leverage this info for service routing/load balancing, etc. https://lists.onap.org/pipermail/onap-discuss/2017-June/001241.html
Need to understand the current OOM process level registration info and how to combine process and service level registration info and save it to Consul catalog.
- Topic Leader: Former user (Deleted)
- Volunteer Note Taker: First Last email
- Estimated Duration:
- Link to data Source (if applicable) MSB Release Planning
- Interested In Attending:
- First Last email
- Stephen terrill
- Dan Timoney
- Michael O'Brien frank.obrien@amdocs.com (as OOM)
- Rich Bennett
- James Forsyth
- Xin Miao
- Vijay Kumar
- Zhaoxing Meng
...
- Description: Discussion on common issues related labs, Plan to setup physical lab, etc.
- Topic Leader: Chengli Wang
- Volunteer Note Taker: First Last email
- Estimated Duration:
- Link to data Source (if applicable)
- Interested In Attending:
- Kang Xi
- Wenyao Guan guanwenyao@chinamobile.com
- Helen Chen
- Yang Xu yang.xu3@huawei.com
- Gildas Lanilis Gmail
- Prabhu Somasundaram (ps7551@att.com)
- Rich Bennett
- Zhaoxing Meng
VoLTE Use Case Control Loop Automation (Day 2- Main Conf. Bridge)
- Description: In the Amsterdam release, VoLTE use case has a requirement on fault correlation and auto-healing, which is closely related to Control loop, including but not limited to CLAMP, DCAE, Policy, Holmes, Multi-Cloud and VF-C projects. During the previously discussion in the weekly meeting, the workflow of control loop has been introduced, but some actual example files are not provided. It is time to design the control loop for VoLTE use case to ensure deliver on time. Here are the gaps need to discuss.
- Examples of DCAE template, CLAMP/Cloudify Blueprint, Config Policy, Operational Policy and related files needed to be designed and used in the control loop. If a series of practical examples can be provided, like all related examples of the vFW demo, which is better for us to understand.
- Developer guidelines to design the control loop to achieve the requirement of VoLTE. Demo of the entire process, e.g. create, deploy, etc., which is a better way help us to learn, if it can be provided.
- The solution of Holmes deployment, integrated with DCAE or others, e.g. workflow, DCAE Template, API, etc.
- The solution of design, creating and distributing Holmes rules, e.g. refer to Policy, or other solutions, etc.
- The requirement of Policy to invoke the API of VF-C.
- The API document of VES collector in DCAE is used by VF-C to report VNF FCAPS data.
- Topic Leader: Yuan Liu
- Volunteer Note Taker: First Last email
- Estimated Duration: 2 hours
- Link to data Source (if applicable)
- Interested In Attending: We would like to invite CLAMP, DCAE, Policy, Holmes, Multi-Cloud, VF-C and other related projects to join in this topic.
- Lingli Deng - denglingli@chinamobile.com
- Yan Yang - yangyanyj@chinamobile.com
- Guangrong Fu - fu.guangrong@zte.com.cn
- Former user (Deleted) - lxinhui@vmware.com
- Kang Xi
- cl664y@att.com
- Wenyao Guan guanwenyao@chinamobile.com
- Gervais-Martial Ngueko
- Pamela Dragosh
- Marco Platania platania@research.att.com
- Stephen terrill
- Alla Goldner
- Ranny Haiby
- Eric Multanen eric.w.multanen@intel.com
- Yang Xu yang.xu3@huawei.com
- Brian Freeman
- Ron Shacham rshacham@research.att.com
- Ritu Sood ritu.sood@intel.com
- Shashank Kumar Shankar shashank.kumar.shankar@intel.com
- simer.singh@us.fujitsu.com
- Murat Parlakisik
- Prabhu Somasundaram (ps7551@att.com)
- Chengli Wang
- Michał Pawłowski
- t
- Kanagaraj M kanagaraj.manickam@huawei.com
- Qidi Lv lvqidi@chinamobile.com
- Subhash Kumar Singh (subhash.kumar.singh@huawei.com)
- Margaret.chiosi1@huawei.com
- James Forsyth
- Jing Wang
- Xin Miao
- Nagesha Subramanya nagesha.subramanya@nokia.com
- Vijay Kumar
- Cheng (Ian) Liu Cheng Ian Liu
- Zhaoxing Meng
...
VoLTE Service Design and Instantiation (Day 2 - Main Conf. Bridge)
- Description: Discuss the details of service design and instantiation for VoLTE use case:
- VNF template format (TOSCA/HEAT)
- vEPC and vIMS VNFs onboarding
- Network service design for data center interconnect network (underlay and overlay), and network between 2 VNFs
- SDC output artifacts (content and format)
- VoLTE service instantiation
- Topic Leader:Yang Xu
- Volunteer Note Taker: First Last email
- Estimated Duration: 2 hrs
- Link to data Source -
- Interested In Attending: If you are interested in this discussion and would like to participate in it, please add your name and email here (one name/email per line please). We'll use this information when building the schedule so that we minimize overbooking people where possible.
- Yang Xuyang.xu3@huawei.com
- Gil Bullard gil.bullard@att.com
- John Choma jchoma@att.com
- Eric Multanen eric.w.multanen@intel.com
- Brian Freeman
- Ron Shacham rshacham@research.att.com
- Prabhu Somasundaram (ps7551@att.com)
- Chengli Wang
- Yan Yang yangyanyj@chinamobile.com
- Yuan Liu liuyuanyjy@chinamobile.com
- Michał Pawłowski
- Murali Mohan Murthy Potham
- Lingli Deng denglingli@chinamobile.com
- Qidi Lv lvqidi@chinamobile.com
- Wenyao Guan guanwenyao@chinamobile.com
- Tao Shen shentao@chinamobile.com
- Murat Parlakisik
- Nagesha Subramanya nagesha.subramanya@nokia.com
- cl664y@att.com
- Zhaoxing Meng
- kspviswa kspviswa.github@gmail.com ( Verizon )
...