Hi Chris,
SOL-003 is the interface and data-model of or-vnmf reference point which means between NFVO and VNFM. If SO provides SO-003 in southbound, does this imply SO is providing NFVO function in Casablanca no matter for POC purpose or as an stable delivery? It is clear VFC has provided the NFVO functionality then what is the relationship of the NFVO in SO and the NFVO in VFC? If these two NFVOs in ONAP are same functionality and different implementation? I am not objecting the idea that we have two NFVOs in ONAP. I just want to make it clear. I am neutral on having different approaches for one same component in open source practice. If this is accepted as a principle of ONAP, I am OK with that. Yuan Yue Senior Strategy Planner Technology Planning Dept./Technology Planning Dept./System Product ZTE Corporation No.50, Software Ave, Nanjing, 210012, P. R. China T: +86 25 88013621 M: +86 13851446442 E: yuan....@zte.com.cn www.zte.com.cn 原始邮件 发件人：ChristopherDonley <christopher.don...@huawei.com> 收件人：John Quilty <john.qui...@ericsson.com>Zengjianguo (OSS Design) <zengjian...@huawei.com>张茂鹏10030173; 抄送人：ONAP-TSC@lists.onap.org <ONAP-TSC@lists.onap.org>Stephen Terrill <stephen.terr...@ericsson.com>anatoly.andria...@nokia.com <anatoly.andria...@nokia.com>gil.bull...@att.com <gil.bull...@att.com> 日 期 ：2018年07月24日 05:10 主 题 ：Re: [onap-tsc] Casablanca Architecture presentation question My understanding is that SO will include a Proof of Concept to support SOL-003 in the Casablanca release. This does not change any support for VNFMs in VF-C. It only demonstrates support for SVNFMs in operator environments that are not using VFC, supporting the Casablanca theme of "Deployability". Because the SOL-003 support was described as a POC for Casablanca, and the team wanted to make sure it didn't affect S3P before merging it with the main branch, SOL-003 was listed as a recommendation on slide 8, but not included in the SO section on pages 10-11 so as not to confuse external audiences regarding the availability of the interface. Let's discuss on tomorrow's call to make sure the deck is accurate and clear. Chris From: John Quilty <john.qui...@ericsson.com> Date: Monday, July 23, 2018 at 2:27 AM To: "Zengjianguo (OSS Design)" <zengjian...@huawei.com>, maopeng <zhang.maope...@zte.com.cn> Cc: "ONAP-TSC@lists.onap.org" <ONAP-TSC@lists.onap.org>, Chris Donley <christopher.don...@huawei.com>, Stephen Terrill <stephen.terr...@ericsson.com>, "anatoly.andria...@nokia.com" <anatoly.andria...@nokia.com>, "gil.bull...@att.com" <gil.bull...@att.com> Subject: RE: [onap-tsc] Casablanca Architecture presentation question Hi Zeng Yes we agree that the VFC has a role to play in the ETSI-ONAP alignment, however the following was also presented in the architecture F2F (https://wiki.onap.org/download/attachments/8225716/Proposed%20ETSI%20ONAP%20Alignment%20Regarding%20Scaling%20-%20Vancouver%20v6.pptx?api=v2), and various steps had being presented before to the architecture team. To my understanding this was agreed and rolled up into the architecture requirements. The wording of the architectural requirements (https://wiki.onap.org/display/DW/Casablanca+Release+Requirements). Please note, that as this was approved under architectural alignment, it doesn’t need an approved use case. Chris, Anatoly, Gil, does this align with your understanding? Regards John From: Zengjianguo (OSS Design) <zengjian...@huawei.com> Sent: 21 July 2018 10:03 To: maopeng <zhang.maope...@zte.com.cn>; John Quilty <john.qui...@ericsson.com> Cc: ONAP-TSC@lists.onap.org; Christopher Donley (Chris) <christopher.don...@huawei.com> Subject: 答复: [onap-tsc] Casablanca Architecture presentation question Hi +1 on maopeng’s comments. We already do a lot in ONAP R1 & R2, and plan continue work on ETSI NFV alignment in VFC during ONAP R3. So why and in which usecase to try to do it in another way? I agree ONAP as platform , should be flexible and there may be more than one choice to one same/similar feature, but may I suggest to try PoC in R3, and show what the difference/advantage firstly, then do the following steps.. Zeng JianGuo 发件人:ONAP-TSC@lists.onap.org [mailto:ONAP-TSC@lists.onap.org] 代表 maopeng 发送时间: 2018年7月20日 9:41 收件人:john.qui...@ericsson.com 抄送:ONAP-TSC@lists.onap.org; Christopher Donley (Chris) <christopher.don...@huawei.com> 主题:答复: [onap-tsc] Casablanca Architecture presentation question Hi John Very interested in the ETSI SOL related discussion: Some backgrounds from my experiences in VFC project and SO project: In ONAP R1&R2, There is SOL005 interface between the SO and VFC, and SOL003 between the VFC and VNFM(vendor or GVNFM). In ONAP R2, VFC has started the work to align the latest SOL interface. please see the JIRA: https://jira.onap.org/browse/VFC-635 and commit some codes. In ONAP R3, VFC will continue to do the work. In the VFC there already extists the vendor VNFM driver and do the implication enhancement. If interested the ETSI SOL interfaces and avoid creating a new wheels, suggest working together in the VFC team and collaborating with each other. Does it make sense? thanks BR Maopeng 原始邮件 发件人：JohnQ <john.qui...@ericsson.com> 收件人：ONAP-TSC@lists.onap.org <ONAP-TSC@lists.onap.org>christopher.don...@huawei.com <christopher.don...@huawei.com> 日 期 ：2018年07月19日22:02 主 题 ：[onap-tsc] Casablanca Architecture presentation question Hi Chris Thanks for pulling this together. Two quick observation/questions The work on the standards alignment could be clearer on where it is impacting on Casablanca. On Slide 8 it is easy to miss the targeted SOL003 VNFM plugin for SO. I just have a quick question should the slide from 9 onwards reflect the proposed changes in Casablanca? If so the VNFM plug-in to SO could be better reflected in 10 and 11. I would suggest reflecting that the VNF LCM interface that SO consumes is SOL003 on slide 10 and 11. Regards John -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#3494): https://lists.onap.org/g/ONAP-TSC/message/3494 Mute This Topic: https://lists.onap.org/mt/23791374/21656 Group Owner: onap-tsc+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
