The TOSCA TC meetings are used to discuss topics that are relevant to the entire TOSCA community, to approve work products, and to promote drafts to official Oasis specifications. Attendance of the TC meetings is required to maintain voter status. Note that TC meetings are held monthly.
Please log in to the chatroom to facilitate recording of meeting notes: The chatroom URL is http://webconf.soaphub.org/conf/room/TOSCA_main
To participate, please Join the following Zoom meeting:
https://us02web.zoom.us/j/87122464085?pwd=TUJweHRtTHdTdktTanJHVS8xM1VHdz09
Meeting ID: 871 2246 4085
Passcode: 746323
One tap mobile
+16699009128,,87122464085#,,,,*746323# US (San Jose)
+13462487799,,87122464085#,,,,*746323# US (Houston)
Agenda
Approval of Agenda / Approval of Minutes
Review/approve draft proposed agenda
Review/approve draft minutes.
* June 26, 2025: https://groups.oasis-open.org/discussion/mom-26-06-2025
Status of TOSCA v2.0
* TOSCA v2.0 was officially released on July 22, 2025
- https://docs.oasis-open.org/tosca/TOSCA/v2.0/TOSCA-v2.0.html
* Press release planned for September 2025
- Draft available at https://docs.google.com/document/d/1HLzv1R1Kf89EElbZhotBzE-h481-3MsgKPzrYsPHWsY/edit?tab=t.0
- Working with Peter at HPE on a supporting quote from a sponsor company.
TOSCA 2.0 Test Framework
* Creating tests in https://github.com/oasis-open/tosca-community-contributions/tree/master/tests/tosca_2_0
* Trying to use GitHub Copilot to create test cases automatically.
- Requires valid tests in each of the subdirectories
TOSCA 2.1 Next Steps
* Template in https://github.com/oasis-tcs/tosca-specs/tree/working/tosca_2_1
- Should examples use tosca_2_1 definitions version?
* Scope of TOSCA v2.1
- Address issues in https://github.com/oasis-tcs/tosca-specs/issues and discussions in https://github.com/oasis-tcs/tosca-specs/discussions
- Leveraging state machines to support declarative workflows
TOSCA Adoption
* Focus on creating community profiles
- https://github.com/lauwers/tosca-community-contributions/blob/master/profiles/community/README.md
* Focus on best practices
- How to support abstraction?
- How to decouple deployment technologies from models with the goal of supporting multiple alternatives?