Greetings, Adding some thoughts on information model: Orchestration need to interoperate among different interfaces, which in turn need to deal with very different payloads in form of YAML, YANG, JSON etc. There will be lots of data processing among these models to process complete service. Handling these templates in orchestrator will impose limitations on capability and performance of orchestrator. So, there should have standardized data model for smooth processing among orchestration steps.
Probably first time, orchestration is composing 3 different worlds of Network, Infra, IT, with different tunes of YANG, YAML, JSON/XML. Is there a play to develop standardized data models for orchestration, which will meet needs of each area? Is TOSCA sufficient? Or need some extended JSON data models? -Brijesh From: onap-tsc-bounces at lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of GILBERT, MAZIN E (MAZIN E) Sent: Thursday, April 20, 2017 8:30 AM To: denghui (L); JANA, RITTWIK (RITTWIK) Cc: onap-discuss at lists.onap.org; onap-tsc at lists.onap.org Subject: Re: [onap-tsc] Modelling discussion on Friday May 5th Rittwik, Deng, This is great. Thank you for taking the lead. I realize the focus is on TOSCA and parsers. Wonderful! I want to take you one level higher to start by discussing what the framework look like for the information model. Perhaps invite folks who have operational experience. Then start describing the differernt data models and how TOSCA plays a role in driving service chaining and micro services (like analytics, data collections, etc). It would be great if the outcome of this mini session to be a recommendation position/paper or a proposal for a project. Mazin On Apr 20, 2017, at 4:34 AM, denghui (L) <denghui12 at huawei.com<mailto:denghui12 at huawei.com>> wrote: 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-TSC mailing list ONAP-TSC at lists.onap.org<mailto:ONAP-TSC at lists.onap.org> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y&m=HRoKLiOZCWLzl3Z-00DLQIUCwCAWqQL50mUFHtfYXYA&s=731fuCUnXbuPSOGHEcVf4U29cHpOGPKmwevRHGAoeiY&e= ============================================================================================================================ 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-discuss/attachments/20170422/49eca0e4/attachment.html>