Hey LinMeng, I will leave it to others to agree or disagree on items #1 and #4, but speaking for myself I don’t think we have agreement on items #2 and #3. If there were no objections expressed during your presentation it was perhaps (as it was in my case) in the interest of time given a 10 minute agenda timeslot, and knowing that there will be other presentations tomorrow that might express other possible approaches. I suspect that there were others, like myself, who did not realize you were considering your presentation a readout of agreements reached in working sessions and asking for final agreement. Gil
From: [email protected] <[email protected]> On Behalf Of LinMeng Sent: Monday, October 29, 2018 6:19 PM To: '[email protected]' <[email protected]>; [email protected] Cc: BULLARD, GIL <[email protected]>; WECHSLER, CHESLA C <[email protected]>; Cheung, Ben (Nokia - US/Murray Hill) <[email protected]>; Sarris, Emmanuel, Vodafone Group <[email protected]>; SCAGGS, KEVIN <[email protected]>; Zu Qiang <[email protected]> Subject: [onap-discuss] Agreements on Montreal offline discussion of Resource IM and Service IM Hi everyone, Thanks for joining this call. There will be a conclusion session for modeling part, for resource IM and service IM, we are going to report our next steps based on our discussion: 1. 1) VNF Instance Model a) Agree to have one unified model for run-time information, combining information from AAI implementation, ETSI spec and VFC inventory b) Analyze the information from the above 3 sources to optimize the representation, e.g., identify the overlapping/redundant attributes, decide which attributes should be included, etc. i. Suggest to make a spread sheet on the wiki to do the analysis c) Consider PNF instance model as well 2) Onboarding/Internal Model a) Agree to have one unified model for onboarding descriptors and run-time instance model, which are described as separate objects and mapping between them are showed b) Describe which model is used for onboarding, for internal output or for run-time use 2.Network slicing model (4 layer model: NetworkSlice->NetworkSliceSubnet->NetworkService->VNF/PNF) No objection. Agreement on to take it as a start of network slice modeling work and then to fulfill the details. Need to report to the next service IM call 3.To support both NSD and service descriptor in the design time. Also, to support both of NS instance and service instance in the run time. No objection. 4. CCVPN optimization: Support service node in Data model; Support List type of inputs in service template; Add an updating workflow of service. No objection. Slides are available at: https://wiki.onap.org/display/DW/Joint+meeting+between+architecture+and+modeling+subcommittee<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Joint-2Bmeeting-2Bbetween-2Barchitecture-2Band-2Bmodeling-2Bsubcommittee&d=DwQFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6llaOBbLWNSasQ9_ejgubw&m=_HsVzLrDq98ugsaqK00UdWJ32WBdZH5NQDcxsA5QMVY&s=0AKVykDfEKHZra5VNlag49CiJ1VTiPrj400Tg1rCj2w&e=> Best regards, Lin ------------------------------- Meng Lin Center of AI and Intelligent Operation R&D China Mobile Research Institute No.32 Xuanwumen west street, Xicheng District, Beijing 100053, China Mobile: +86 13810012241 Email: [email protected]<mailto:[email protected]> ------------------------- -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13363): https://lists.onap.org/g/onap-discuss/message/13363 Mute This Topic: https://lists.onap.org/mt/27786848/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
