This page hosts information about discussion calls dedicated to service modeling.
Upcoming call
Logistics
Start Time: 8 am US western Friday, March 30
- TBA
Proposed Agenda
- TBA
Past calls
20180330
Logistics
Intercontinental Los Angeles Downtown, sponsored by Linux Foundation Network Echo Park Meeting Room 5th floor
Time: 8am-1pmLength: 5 hours
Meeting room: https://zoom.us/j/882442618
Part of the ONAP Friday morning modeling session in ONS 2018 (30 March 2018)
Agenda
Proposed Agenda
- TBA
Past calls
0 Agenda bashing
Service session
1 Yangxu - Service IM Status and Observations
2 John - MEF MCM Proposal
3 Jianguo - ONAP R3 Service IM Proposal
4 Lingli - Service IM Usecase Proposal (Skipped for time limitation)
5 Discussion on next steps
Resource DM session
6 Michael - ONAP R3 Resource DM Proposal Feedback
7 Alex - Kicking off ONAP R2 Resrouce DM Open Issues (Skipped for time limitation)
Onsite Participants
Hui DENG , Xinhui Li, Lingli Deng , Seshu Kumar, Parviz Yegani, Alex Vul , John Strassner , Xu YANG
Anh Le , Thinh Nguyenphu , Michael Lando , Pawel Pawlak , Jianguo Zeng , Stephen Terrill , Seshu Kumar
Tal Liron, Yoav Kluger, Catherine Lefevre
Meeting minutes
1) R2 service modeling will be the same as R1 servcie modeling which is confirmed by SDC/SO/HPA/VNFSDK/AAI/VFC
2) R2 resource modeling will be based on clean version of wiki page, but will only implment part of the request from the use case
3) R3 DT resource DM have critical issue whether we are going to improve R2+ model or redesign a new DM for R3+
4) ONAP service model is broder than ETSI Network Service
5) Product/Offer is out of the scope of ONAP service model
6) The workshop made the following concensused suggestion:
- Cardiality correction by John
- Suggest to move to composite pattern instead of recursive aggregation
- Decoration pattern is FFS
- Terminology need to be defined (e.g. clarifications on service component as with the one in MEF)
20180325
Agenda
- ONAP R2+ service IM Discussion Review and Proposal
...
- The current status of service IM and my observations (Xu Yang) - delayed due to time limitation
- Discussion for follow-ups
- Lingli provides customer-facing business scenarios as input for service model discussion and comparison by Tuesday;
- For Friday workshop, each presenter (including SDOs/individuals) is expected to provide their respective proposal models and with the context of customer facing business scenario;
- Based on which, the team is expected to develop a more clearly scoped target and collaborative pattern for R3+.
20180321
Agenda
- Agenda bashing
R2 Status summary and priority
ONS workshop agenda
- R2 VNFD DM clean up discussion (added for R2 priority)
- Network Service Descriptor R2 Implemenation Discussion
- Service Order Model (added to the agenda, but deferred to next meeting due to time limit)
...
- Agenda bashing
Andy suggested to add service order model to the agenda.
Hui suggested to add VNFD DM discussion for finalizing R2 spec. R2 Status summary and priority
Agreed to continue work on nsd for R2 implemenation, and defer WAN descriptor discussion for R3 discussion starting next call.
And service order proposal to R3 discussion.ONS workshop agenda
Deng Hui suggest to- Add project PTL to explain how they implement service today SDC, SO, A&AI
- YANGXU is presenting the relationship between SERVICE and network service
- Multi SDO presentation about service IM , tmf/mef/onap
- Offline to build tiger team to design service IM
Andy suggest to
- Add service order model
- Further Discuss NS
- Network Service Descriptor R2 Implemenation Discussion
NS model as service component added in the R2.
Maopeng and Anatoly need to discuss more tosca grammar details related to NS model and update the NS model. - Wrap up
20180313
Agenda
- Agenda bashing
WAN service IM/DM Proposal (Zhuoyao)
- Network Service Discussion
- Wrap up
...
Recordings
20180307
Agenda
- Agenda bashing
- Service DM proposal (Chuanyu/Maopeng)
- WAN service modeling proposal (Zhuoyao)
- Wrap up
...