version 1.3 Public Review 01 Comments

[Priya T G <priya.g@netcracker.com>]

Chris,

 

As already discussed with you, I am sharing some comments on clause 3.8.7.1 and 7.3.8 related to support for custom workflow language:

 

From the workflow definition in clause 3.8.7.1 , it appears that external workflows and TOSCA service templates are not connected. The workflow definition and examples in clause 7.3.8 need to account for the following:

a.       Allow input assignments for workflows : Allow assignment of values to workflow inputs, this could be values of attributes/properties of a node template through the use of intrinsic functions such as get_input or get_property.

b.      Illustrate how outputs from external workflows are returned and assigned to attributes/properties of node template/service template.

 

Regards,

Priya

 

From: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org] On Behalf Of Paul Lipton
Sent: Monday, June 3, 2019 11:24 PM
To: tosca@lists.oasis-open.org
Cc: Chris Lauwers <lauwers@ubicity.com>
Subject: [tosca] Guidance for First CSD Public Review of v1.3

 

[External Email]

---

 

Hi TOSCA-teers (specifically, TC Members),

 

June 21^st concludes the first public review period for v1.3. As TC Members, you have all played a role to determine the scope and final features of v1.3. Thus, while not mandatory, it is recommended that v1.3 comments be focused on items such as non-normative corrections or editorial errors/typos, which will likely not require a 2^nd CSD Public Review, or comments that identify normative âfixesâ so compelling that they cannot wait for v2.0 and/or a v1.3 Errata.

 

TC Members may submit any v1.3-specific comments for TC consideration to the usual TC mailing list (tosca@lists.oasis-open.org). Please identify such emails with a subject starting with a string such as âv1.3 Public Review 01 Comment(s): xxxxâ where xxxx is a short title of some sort.

 

For TOSCA releases after v1.3, please continue to add your strategic proposals to our Strategy Spreadsheet. The latest version is currently at: https://www.oasis-open.org/apps/org/workgroup/tosca/download.php/64733/TOSCA%20TC%20Post%20v1.3%20Proposals%202019-02-01%20v3%20Calin%20PL%20.xlsx

 

Non-TC member comments should be submitted to the TC Comment Portal, which can be found at: https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=tosca. Feel free to share that link with appropriately interested outside parties.

 

Thanks,

Paul

 

 

 

 

---

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.  

--- Begin Message ---

• From: Priya T G <priya.g@netcracker.com>
• To: Chris Lauwers <lauwers@ubicity.com>, Arturo Martin De Nicolas <arturo.martin-de-nicolas@ericsson.com>, "claude.noshpitz@att.com" <claude.noshpitz@att.com>, "tosca@lists.oasis-open.org" <tosca@lists.oasis-open.org>
• Date: Thu, 7 Feb 2019 13:02:02 +0000

[External Email]

---

 

Chris,

 

Perhaps,  section 7.3.8 can be enriched with examples to clarify the interactions between TOSCA and external workflows for version 1.3.(i.e. address comment #2 in the email below) ?

We can further revisit this topic in version 1.4.

Please let me know.

 

Regards,

Priya

 

From: Chris Lauwers [mailto:lauwers@ubicity.com]
Sent: Thursday, February 7, 2019 12:31 AM
To: Priya T G <priya.g@netcracker.com>; Arturo Martin De Nicolas <arturo.martin-de-nicolas@ericsson.com>; claude.noshpitz@att.com; tosca@lists.oasis-open.org
Subject: RE: Minor errors in latest draft

 

[External Email]

---

 

Hi Priya, these are very good comments.

 

I made the change to Section 11.1.19 but your other comments are more involved. I agree that this discussion should be harmonized with the general discussion about Artifact Processing in Chapter 13. Any chance you might be able to provide a contribution that could be included in Version 1.3 of the spec? If not, we can plan to revisit this discussion and provide a more comprehensive introduction as part of Version 1.4.

 

Chris

 

From: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org] On Behalf Of Priya T G
Sent: Monday, January 28, 2019 12:37 AM
To: Chris Lauwers <lauwers@ubicity.com>; Arturo Martin De Nicolas <arturo.martin-de-nicolas@ericsson.com>; claude.noshpitz@att.com; tosca@lists.oasis-open.org
Subject: [tosca] RE: Minor errors in latest draft

 

Hi Chris,

 

Here are some comments on Section 7.3.8 Use a custom workflow language:

 

1.       The beginning of this section should capture our discussions on this topic, i.e. about the responsibilities of decomposition of tosca template, maintaining and exchanging instance model etc. so that the strategy and applicability of third party work flows is clear for the readers. Is it necessary to introduce and describe âexternal workflow enginesâ as it was done for artifact processors so that it is clear how TOSCA Orchestrators can interact with such engines? This would also align this section with clear statements already present in the specification about declarative and imperative workflows, state change, steps weaving etc.

2.       Section 3.8.7.1 talks about property definitions and attribute mappings. There should also be clear examples about interactions between TOSCA and external workflows , for e.g.

a.       How does an attribute from a node template/instance get assigned as input and passed to external workflow.

b.      Is it possible/not possible to invoke operations for a particular node template from external workflows? E.g. invoking interfaces->Standard->Configure , interfaces ->Standard -> Create etc.

c.       How are the outputs from external workflows returned and assigned to attributes in the node template?

 

3.       Section 11.1.19 - tosca.artifacts.nfv.SwImage to be changed to tosca.artifacts.Deployment.Image

 

 

Regards,

Priya

 

From: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org] On Behalf Of Chris Lauwers
Sent: Friday, January 25, 2019 10:34 AM
To: Chris Lauwers <lauwers@ubicity.com>; Arturo Martin De Nicolas <arturo.martin-de-nicolas@ericsson.com>; claude.noshpitz@att.com; tosca@lists.oasis-open.org
Subject: [tosca] RE: Minor errors in latest draft

 

[External Email]

---

 

Hi Arturo,

 

These have been fixed in rev15 (to be published early next week).

 

Thanks again for pointing these out.

 

Chris

 

From: tosca@lists.oasis-open.org <tosca@lists.oasis-open.org> On Behalf Of Chris Lauwers
Sent: Tuesday, January 15, 2019 1:00 PM
To: Arturo Martin De Nicolas <arturo.martin-de-nicolas@ericsson.com>; claude.noshpitz@att.com; tosca@lists.oasis-open.org
Subject: [tosca] RE: Minor errors in latest draft

 

Thanks Arturo, Iâll try to correct those in the next revision.

 

Chris

 

From: tosca@lists.oasis-open.org <tosca@lists.oasis-open.org> On Behalf Of Arturo Martin De Nicolas
Sent: Tuesday, January 15, 2019 4:44 AM
To: claude.noshpitz@att.com; Chris Lauwers <lauwers@ubicity.com>; tosca@lists.oasis-open.org
Subject: [tosca] Minor errors in latest draft

 

Hi Claude and Chris,

 

I spotted 3 small errors in the latest draft  (wd0.1-rev14) that I think could be fixed directly  before we finalize 1.3:

 

 

1) 3.3.5.1.1 Single-line grammar

 

The second line and 3rd line should be removed

 

 

2) 3.8.3 Node Template

 

The node_filter entry in the table still talks about the 'selectable' directive. This directive is not defined and we had removed some other text referring to it, but seems this part was missed.

 

 

3) Clause after 3.10.3.9.3, artifact types

This clause has no numbering. It should be 3.10.3.10. Then âkeynameâ should become 3.10.3.10.1, Grammar should become 3.10.3.10.2 and Example 3.10.3.10.3. Afterwards the L4 index for succeeding clauses must be stepped.

 

Thanks.

 

BR,

Arturo

 

 

---

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.  

--- End Message ---