search

oasis-open / tosca-community-contributions

OASIS TC Open Repository: Manages TOSCA profiles, tests, and templates that are maintained by the TOSCA community. They are intended to be used as examples to help developers get started with TOSCA and to test compliance of TOSCA implementations with the standard.
https://github.com/oasis-open/tosca-community-contributions
Apache License 2.0
39 stars 25 forks source link

Packaging profiles as ... CSARs? Would this affect the metadata? (e.g. should the CSAR metadata contain the canonical namespace for the profile?) #62

Open aszs opened 2 years ago

philippemerle commented 2 years ago

Why is this needed? any use case? any technical issue if CSAR metadata does not contain profile metadata?

tliron commented 2 years ago

We received feedback from ETSI that it's useful for a CSAR to not have a root "service template" or even any TOSCA YAML files, to use the format for packaging other kinds of artifacts (e.g. YANG files).

philippemerle commented 2 years ago

We received feedback from ETSI that it's useful for a CSAR to not have a root "service template" or even any TOSCA YAML files, to use the format for packaging other kinds of artifacts (e.g. YANG files).

CSAR is a TOSCA dedicated packaging format. Then a CSAR file without TOSCA YAML files is just a ZIP file. So ETSI could use ZIP files (or any other similar packaging formats) for packaging YANG files.

tliron commented 2 years ago

I imagine that they are also using the Metadata file part of CSAR in processing. We can ask ETSI for more information about this,