Huabing I'm curious on what basis are you making the following assumptions:
"Condition 2: Neither declarative nor internal imperative workflow is capable of the process model of general Telecom cloud NFV process model. which I have already elaborated in my previous mails. and you also agreed. Condition 3: BPMN/BPEL can do this job. " Is there a specific POC or test that you've ran to validate those assumptions? What are the specific use cases that can't be implemented with option 2? The reason i'm asking is that i want to verify those statements is that its important to separate the conceptual/architecture limitation from specific implementation limitation and without knowing those details its too early to make this kind of arguments. I would like to point out that many use web-scale use cases (mostly) outside of the telco industry use a declarative model (Amazon cloud formation is a good example, Terraform could be another good example) to deal with large scale and complex deployment that span across zones, sites etc. This is even more true with the containers and cloud native services. I could also point out just as equally to how you can deliver VCPE, SD-WAN and many other Telco use cases that spans across multi-site in either option hence my point above. So while were making this sort of discussions i think that it would important that we will more specific on the use-case and user-story first, than explore which options first that use case best and drive the decision from there. It sounds like you've gone through this process youself hence my original question for sharing the details from that experience before we jump into conclusion and build an entire strategy around them. Nati S. On Fri, Apr 28, 2017 at 9:45 AM <zhao.huab...@zte.com.cn> wrote: > The reasoning is obvious and simple: > > Condition 1: TOSCA intend to have both the topology model and process > model to facilitate the cloud and NFV orchestration. > > Condition 2: Neither declarative nor internal imperative workflow is > capable of the process model of general Telecom cloud NFV process model. > which I have already elaborated in my previous mails. and you also agreed. > > Condition 3: BPMN/BPEL can do this job. > > reasoning result: BPMN/BPEL should be included in TOSCA for process > modelling, along with declarative workflow. > > What if we not: TOSCA workflow solution is uncompleted due to the lack of > NFV process modelling capability. > > I just don't understand the logic why you keep pushing back what is > obviously good for the expansion of TOSCA adaption and healthy of TOSCA > ecosystem._______________________________________________ > onap-discuss mailing list > onap-disc...@lists.onap.org > https://lists.onap.org/mailman/listinfo/onap-discuss >
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
