tosca-community-contributions

tosca-community-contributions copied to clipboard

Fully specify substitution specification and mechanism (e.g. how to map multiple requirements with the same name, or how to map notifications?)

2

aszs

Should 'constraints' keyword be renamed?

9

In Tal's latest proposal, the 'constraints' keyword has been renamed to 'validation'. The meaning of the 'validation' keyword is less intuitive than the original 'constraints', but the 'constraints' keyword suggest...

lauwers

(At the request of Thinh Nguyenphu) Something like this: TOSCA includes basic support for [policies / workflows] to supplement its main goal of declaratively describing cloud topologies. This feature is...

tliron

Should a relationship definition be allowed to refer to properties of a target node type before the type of the node has been declared/resolved? If not then the Node clause should be documented as required in that case.

29

aszs

Allow distributing `service_template` among several TOSCA files

3

This tentative proposal is to allow a TOSCA file import tree to contain more than one file with a `service_template` keyname. The obvious implication is that the final collection of...

tliron

Rename `entry_schema` and `key_schema` to `entry_type` and `key_type`

1

The word "schema" is confusing here, as we are referring to a data type. Changing it to `_type` also aligns with my general preference that keynames include the name of...

tliron

Explain `$get_artifact`

1

It is currently unclear what exactly the `$get_artifact` function returns. Assuming it does return a URL or path to access the artifact (which I think is most logical), it does...

tliron

"about" keyname

5

Every TOSCA file (see #112) can have an `about` keyname with the following keys, all optional: - short_description (no newlines) - long_description (standardize on Markdown?) - version ([semver](https://semver.org/), for this...

tliron

About - day 2 identification of the definition of a node graph

3

Consider those use-cases, where the node graph created from a service template deployment is *persisted*. I am aware that not all orchestrators have such a model, but some do. In...

pmbruun

The problem is that the `targets` keyname accepts both node (types or templates) and group (types or actual), but each of these exist in their own per-type namespace and there...

tliron