Great thought, Aayush. Agreed. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png at 01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/>
From: onap-tsc-bounces at lists.onap.org [mailto:onap-tsc-bounces at lists.onap.org] On Behalf Of aayush.bhatna...@ril.com Sent: Thursday, April 27, 2017 12:18 PM To: michael at gigaspaces.com; denglingli at chinamobile.com Cc: rjana at research.att.com; onap-discuss at lists.onap.org; onap-tsc at lists.onap.org Subject: Re: [onap-tsc] [onap-discuss] Modelling discussion on Friday May 5th Dear Michael, Ling Li I have a suggestion here to move forward - We should indeed have a broader workflow discussion, and consider the end to end aspects (which would be ?realized? by ECOMP and Open-O merged at ONAP). All workflows should have a reference to the TOSCA declarative model-driven orchestration, so that we arrive at ?ECOMP Templates? for each of the workflows. Some of the workflows that we can take up are listed below as a suggestion (largely aligned to the ETSI MANO requirements): 1. Lifecycle Management workflows for VNFs (Onboarding, Packaging, Instantiation, Auto scaling and Termination) 2. Lifecycle Management workflows for Network Services (NS) on the same lines 3. Workflows for service creation through VNF FGs. 4. Onboarding of NFVI resources fulfilment (underlying hardware and virtualization to add resources to the pool) leading to resource discovery processes from a NFVO perspective (ECOMP AAI may play a role here). 5. Workflows for fault management and VNF shifting/migration 6. Other aspects ? I believe our joint objective should be to define the scope of these workflows and arrive at an agreeable set of flows which can be implemented / realized using ECOMP. BPMN based workflow implementations can also co-exist with the TOSCA model-driven graphs. However, we may discuss in more detail on how to move forward in this aspect. There would always still remain specific workflows for users of the ECOMP platform, which can be then be designed using the ECOMP design time framework and perhaps the ?learnings? can be contributed back to the community This can help us formally develop as a workflow design library for ECOMP, enabling VNF providers to quickly adopt the platform by using its templates and also contributing the learnings back to make it better. If all agree in principle, we can discuss and move forward. Regards Aayush Bhatnagar Reliance Jio From: onap-tsc-bounces at lists.onap.org<mailto:onap-tsc-bounces at lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Michael Brenner Sent: 26 April 2017 22:00 To: Lingli Deng Cc: onap-discuss; JANA, RITTWIK (RITTWIK); onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org> Subject: Re: [onap-tsc] [onap-discuss] Modelling discussion on Friday May 5th Lingli, all: I though we are now discussing ONAP and how to improve it, and not Open-O? Furthermore, ONAP is indeed using BPEL/BPMN workflows, but that is as part of the MSO. MSO may decide to delegate certain portion of the orchestration to a TOSCA-based orchestration engine, and what is delegated to such engine may have to use its own internal/native workflows. The real question here is: are we trying to leverage the best of all we have available, or are we trying to keep replicating the status-quo forever. Regardless of the answer, I find it that it is a very narrow perspective if we only want to discuss workflows in the context of what was implemented initially in Open-O or ECOMP, instead of opening a broader discussion of what makes sense where in the overall architecture. Best regards, Michael On Wed, Apr 26, 2017 at 2:10 AM, Lingli Deng <denglingli at chinamobile.com<mailto:denglingli at chinamobile.com>> wrote: Hi Michael, You may consult your gigaspace's colleage, as my recollection, native workflow proposed by gigaspaces was turned down by the consensus of the OPENO community, we decided to use BPMN/BPEL type of workflow, you can also find out the workflow in MSO /APPC of OPENCOMP are also using BPMN/DG Thanks, Lingli From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at lists.onap.org> [mailto:onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>] On Behalf Of Michael Brenner Sent: 2017?4?26? 11:09 To: denghui (L) <denghui12 at huawei.com<mailto:denghui12 at huawei.com>> Cc: onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org>; JANA, RITTWIK (RITTWIK) <rjana at research.att.com<mailto:rjana at research.att.com>>; onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Subject: Re: [onap-discuss] Modelling discussion on Friday May 5th But no TOSCA native workflows ... why? Michael On Tue, Apr 25, 2017 at 8:03 PM, denghui (L) <denghui12 at huawei.com<mailto:denghui12 at huawei.com>> wrote: Hi Michael, Thanks for your suggestion, workflow is already covered in the Shitao?s session, they will discuss 1) OPENCOMP Workflow 2) OPEN-O Workflow. Best regards, DENG Hui From: Michael Brenner [mailto:michael at gigaspaces.com<mailto:mich...@gigaspaces.com>] Sent: Friday, April 21, 2017 7:14 AM To: Amir Levy Cc: JANA, RITTWIK (RITTWIK); Nguyenphu, Thinh (Nokia - US/Irving); denghui (L); onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>; Nati Shalom; onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org> Subject: Re: [onap-discuss] Modelling discussion on Friday May 5th I'll be happy to attend and take part in the discussion and would like to suggest to add workflows to the agenda ...a topic which I offer to moderate. Best regards, Michael On Apr 20, 2017 4:51 PM, "Amir Levy" <amir at gigaspaces.com<mailto:amir at gigaspaces.com>> wrote: Thanks DENG for leading this initiative. I would love to share few quick links to prepare for this meeting: We have a two parts video that provides TOSCA in practice training : Part 1: https://www.youtube.com/watch?v=aMkqLI6o-58 and https://www.youtube.com/watch?v=6xGmpi--7-A And Michael Brenner for ETSI/NFV and TOSCA has recently drafted a in-depth comparison between model-driven and task-driven workflows: http://getcloudify.org/brochures/tosca-workflows-Apr-2017.pdf ? amir amir at gigaspaces.com<mailto:amir at gigaspaces.com> +1 408 916 8572<tel:(408)%20916-8572> On Apr 20, 2017, at 10:29 AM, Nguyenphu, Thinh (Nokia - US/Irving) <thinh.nguyenphu at nokia.com<mailto:thinh.nguyenphu at nokia.com>> wrote: Hi Rittwik and DENG, Is modeling discussion covering network service and VNF descriptors? Or it is broader to cover all of the ONAP functions? Yes, I am planning to attend. Thinh From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of denghui (L) Sent: Thursday, April 20, 2017 3:35 AM To: denghui (L) <denghui12 at huawei.com<mailto:denghui12 at huawei.com>>; onap-tsc at lists.onap.org<mailto:onap-tsc at lists.onap.org>; onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Cc: JANA, RITTWIK (RITTWIK) <rjana at research.att.com<mailto:rjana at research.att.com>> Subject: [onap-discuss] Modelling discussion on Friday May 5th Hello all We are happy to let you know that we are hosting a modeling session on Friday, May 5th, AT&T Lab. 9:00-10:30 Shitao moderate: TOSCA NFV Profile 10:30-12:00 Rittwik moderate: AT&T Parser 13:30-16:00 DengHui moderate: Modelling & Opendeployment Please kindly help to let us know if you are interested in joining us, so that we can book a proper meeting room for our discussion Best regards, Rittwik & DENG Hui _______________________________________________ onap-discuss mailing list onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> https://lists.onap.org/mailman/listinfo/onap-discuss -- Michael Brenner, Chief Architect NFV [https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/-27020792c3e94269b883d9a828be029f56c08986b2ab208a46143b169592c35a.png] ________________________________ M: +1-732-895-5772<tel:(732)%20895-5772> http://getcloudify.org<http://getcloudify.org?utm_source=signaturesatori&utm_medium=email&utm_campaign=Cloudify%204.0%20Webinar> @cloudifysource [https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/2fb5e7413e7dbeee3e88676333b65c05237ec13d3512e4a63ebc1b5f85bfb917.png]<https://twitter.com/CloudifySource> [https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/16b91ab7a91bb3a298f2a322640bebb3754357f93e9f20ff50d2c94bb82b1814.png] <https://www.linkedin.com/company-beta/17918192/> [https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/6f7421bc5b9a93a0649735bbc8589b200c678bf08af9d7e0cebf1b3cffcdac94.png] <https://github.com/cloudify-cosmo> [https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/4be4d1377f4c1afe70a25e78926b6aad4e0a4fb1d45a7727e31d5a807eb3aae7.png] <https://www.youtube.com/cloudifysource> [https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/-218433c43f71db1180fd27884e3650b01b94c578c594b32c6f49c3daa3151366.png]<http://getcloudify.org/webinars/the-new-cloudify-4.html?utm_source=signaturesatori&utm_medium=email&utm_campaign=Cloudify%204.0%20Webinar> -- Michael Brenner, Chief Architect NFV [https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/-27020792c3e94269b883d9a828be029f56c08986b2ab208a46143b169592c35a.png] ________________________________ M: +1-732-895-5772 http://getcloudify.org<http://getcloudify.org?utm_source=signaturesatori&utm_medium=email&utm_campaign=Cloudify%204.0%20Webinar> @cloudifysource [https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/2fb5e7413e7dbeee3e88676333b65c05237ec13d3512e4a63ebc1b5f85bfb917.png]<https://twitter.com/CloudifySource> [https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/16b91ab7a91bb3a298f2a322640bebb3754357f93e9f20ff50d2c94bb82b1814.png] <https://www.linkedin.com/company-beta/17918192/> [https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/6f7421bc5b9a93a0649735bbc8589b200c678bf08af9d7e0cebf1b3cffcdac94.png] <https://github.com/cloudify-cosmo> [https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/4be4d1377f4c1afe70a25e78926b6aad4e0a4fb1d45a7727e31d5a807eb3aae7.png] <https://www.youtube.com/cloudifysource> [https://storage.googleapis.com/signaturesatori/customer-C00h6qxzk/images/-218433c43f71db1180fd27884e3650b01b94c578c594b32c6f49c3daa3151366.png]<http://getcloudify.org/webinars/the-new-cloudify-4.html?utm_source=signaturesatori&utm_medium=email&utm_campaign=Cloudify%204.0%20Webinar> "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential and may be privileged. If you are not the intended recipient, you are hereby notified that any review, re-transmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment." ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html <http://www.techmahindra.com/Disclaimer.html> externally http://tim.techmahindra.com/tim/disclaimer.html <http://tim.techmahindra.com/tim/disclaimer.html> internally within TechMahindra. ============================================================================================================================ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170427/b99c21e8/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 4909 bytes Desc: image001.png URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170427/b99c21e8/attachment-0001.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 7337 bytes Desc: image002.jpg URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170427/b99c21e8/attachment-0001.jpg>
