[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [tosca] Question about use cases for instance-based Orchestration
Hi Anh,
Answers in line
Best,
Derek
From: <tosca@lists.oasis-open.org> on behalf of Anh Tuan Le <AnhLe@NetCracker.com>
Date: Wednesday, April 13, 2016 at 6:43 PM To: "tosca@lists.oasis-open.org" <tosca@lists.oasis-open.org> Subject: [tosca] Question about use cases for instance-based Orchestration Dear Derek and Sivan, Thank you for the document presentation today. Let me have some question to the TOSCA workgroup. If you create another mailing list just for our Instance ad-hoc group, please let me know. [Derek] I don’t think we have a doc which talks about use cases (Sivan would know better than I). If you have other use cases you are welcome to submit them. At the moment we are looking at the instance model from the perspective of generic application
automation requirements and only have explicitly covered cases where existing declarative orchestration has been insufficient (this is where the cluster use case came from). In parallel we are developing the imperative workflow feature but this is done in
the YAML profile working group. We are not looking at NFV or other domains yet.
- Is life cycle state changes in scope, and what other Standardization works we like to refer to? [Derek] The YAML profile spec draft has everything we have on this topic.
- About the notion of only one running instance of workflow at a time: is it suggestion from a practical implementation? Or there are other reasons for it? Thank you, Anh Anh Le, Senior Director, Telecom Research The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or
privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact
the sender and delete the material from any computer.
The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]