tosca-community-contributions

tosca-community-contributions copied to clipboard

The case sensitivity issue with scalar-unit.bitrate

4

aszs

Should relationship type be mandatory in requirement definitions?

3

lauwers

Harmonize condition syntax across workflows and policies

13

Condition clauses are used in policy definitions as well as in workflow definitions. While the condition syntax is well thought-out and supports arbitrary boolean expressions, in practice it is very...

lauwers

Use condition syntax in node filters and capability filters

2

I have a need to define more complex requirement fulfillment logic than what can be expressed using node and capability filters. I believe the existing condition syntax could be used...

lauwers

Add support for capability filters in requirement definitions (and requirement assignments)

1

Requirement definitions and assignments support a node_filter keyword to narrow down the set of target nodes that can be used to fulfill a requirement. This keyword presumes that the node...

lauwers

CSAR: tarball (streaming) formats

2

aszs

What to do with the "schema" constraint?

2

aszs

https://docs.oasis-open.org/tosca/TOSCA/v2.0/csd05/TOSCA-v2.0-csd05.html#_Toc125468802 documents function definition syntax, but the syntax suggested for `function refinement` needs further clarification/exploration, since refinements in function definitions does not follow the same pattern as refinement in type...

lauwers

https://docs.oasis-open.org/tosca/TOSCA/v2.0/csd05/TOSCA-v2.0-csd05.html#_Toc125468800 is somewhat wishy-washy about where function values are allowed. That section must include a complete list of all syntax elements that allow function values.

lauwers

Tosca 1.3 override requirements in node_type

2

Why are requirements is list? So I can't override requirements via derived from mechanism. Can you explain why requirements is list? I think, that requirements should be dict and capability,...

DYDKA4