This page hosts information about discussion calls dedicated to service modeling.
Upcoming call
Logistics
Start Time: 1 pm US western Sunday, March 25
Length: 4 hours
Meeting room: https://zoom.us/j/882442618
Part of the ONAP Sunday afternoon modeling session in ONS 2018
Proposed Agenda
- ONAP R2+ service IM Discussion Review and Proposal
Service IM layering framework (Lingli Deng)
- SDO Persptive
MEF (Jack Pugaczewski)
TMF (John Wilmes)
ONF (Nigel Davis)
- ONAP R3 Service IM Proposals
Service Order (Andy/Kevin)
Service Component: Network Service Descriptor (Maopeng Zhang)
Service Component: WAN Service Descriptor (Zhuoyao Huang)
- Priority and Planning Discussion
The current status of service IM and my observations (Xu Yang)
Discussion
Past calls
20180325
Agenda
- ONAP R2+ service IM Discussion Review and Proposal
Service IM layering framework (Lingli Deng)
- SDO Persptive
MEF (Jack Pugaczewski)
TMF (John Wilmes)
ONF (Nigel Davis)
- ONAP R3 Service IM Proposals
Service Order (Andy/Kevin) (Skipped as Andy is not online)
Service Component: WAN Service Descriptor (Zhuoyao Huang & Nigel Davis)
Service Component: Network Service Descriptor (Maopeng Zhang & Thinh)
- Priority and Planning Discussion
The current status of service IM and my observations (Xu Yang) (Skipped for time limitation)
Discussion (Partially covered during the flow of discussion)
Minutes
TBA
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)
Minutes
- 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
Minutes
- Agenda bashing
Added a time slot for Network service VL Discussion. WAN service IM/DM Proposal (Zhuoyao)
WAN (Service Component) IM
Need clarifications on relationship with ONF CIM and/or TAPI model.WAN (Service Component) DM
Need clarificationson relationship with parallel TOSCA Data Modeling practice at ONF and avoid collision if possible (e.g. in terms of naming conventions)
- Network Service Discussion
- NetworkService Model Diagram (Maopeng)
Add reference to IFA 014 2.4.1 when appropriate. Need sync with SDC/VF-C for implementation plan in R2. - Network service VL Discussion (Nagesha)
Very briefly done due to time limit. Will provide wiki page contribution and kick off further discussion.
- NetworkService Model Diagram (Maopeng)
- Wrap up
Recordings
20180307
Agenda
- Agenda bashing
- Service DM proposal (Chuanyu/Maopeng)
- WAN service modeling proposal (Zhuoyao)
- Wrap up
Minutes
- Agenda bashing (Lingli)
No comments received and proceeded with the proposed agenda. Service IM recap and update(Kevin)
No update made to the clean version as agreed back in December F2F. (Kevin)
Concerns raised about potential alignment conflicts with MEF service models, which would be discussed further in March F2F. (Mehmet and others)- Service DM proposal (Maopeng)
It is clarified that both network service and wan service are derived from service component. The network service as it currently represented is a simplified subset of Network Service as define by ETSI NFV, without VNFFG or Deployment Flavour etc. (Maopeng)
UML class diagram for corresponding IM design was requested to be added. (Andy)
More sophisticated design for virtual link might need to be considered for some service provider scenario, contribution to be expected in later discussion. (Thinh) - WAN service modeling proposal (Zhuoyao)
It is recognized as a good approach to proceed, suggest to add consideration for covering both intra-DC connectivity and inter-DC connectivity for underlay. (Gil & Andy) - Wrap up
All participants are encouraged to leave their comments to the wiki discussion pages for further discussion and better tracking.
Recording