During our TOSCA Language Ad-Hoc meeting on Wednesday Oct. 23 we discussed our next course of action to move TOSCA v2.0 forward. While there are a number of functional areas to be revisited, we decided to prioritize the development of more comprehensive and more sophisticated examples to help users get started with TOSCA and promote adoption of TOSCA v2.0. We proposed the following actions:
- Make sure all the examples in the specification are valid TOSCA.
- Extract the examples from the spec and organize them in an "examples" subdirectory (Paul).
- Introduce a github action to "validate" files in the "examples" subdirectory whenever they are modified (either using Puccini or Ubicity) (Tal, Chris, Oliver).
- Create tooling to "pull" examples into the spec (Tal).
- Separately, create a more comprehensive set of examples in github, perhaps for inclusion in the "Introduction to TOSCA v2.0" document over time?
- Decide whether to manage this in the tosca-specs repo or in the tosca-community-contributions repo (all).
- Tal suggested creating an example "mini" profile that can be included in the spec and used by all the examples. We need to come up with ideas for an application domain. Tal suggested (virtual networking)? (all)
- Chris to contribute his outline that "progresses" examples through increasingly more sophisticated functionality (Chris)
- We also discussed the development of "test cases" to check if a TOSCA implementation complies with the spec.
- Contribute any test cases that are used by team members for development (Chris, Tal, others?)
- Tal suggested creating tooling that can create test cases automatically.
- We also discussed the need for a mechanism for "negative" testing (i.e. verify that a TOSCA Validator correctly flags incorrect TOSCA).
-
Please let me know if I missed anything.
Thanks,
Chris