Welcome / Roll
Co-chair appoints a scribe
Review/approve draft proposed agenda
Review/approve draft minutes
* Oct.29: https://www.oasis-open.org/committees/document.php?document_id=56917&wg_abbrev=tosca
** Thanks to Hemal Surti for scribing
* Nov. 12: https://www.oasis-open.org/committees/document.php?document_id=56920&wg_abbrev=tosca
** Thanks to Juergen Meynert for scribing
* Informal co-chair remarks and notables
** Also, please welcome new TC members: Mr. Uri Elzur from Intel Corporation, Mr. Xavier Degenne of Fastconnect SAS, Mr. Xavier Degenne of Fastconnect SAS, and Sridhar Ramaswamy from Brocade Communications Systems
*** New members: expect a delay, but you will be added to this list within a couple weeks of joining of the TC
TOSCA Simple Profile in YAML v1.0 Public Review 01 Comment Resolution
* See latest iteration of the Comment Resolution Log
* Note: 30 Day Public Review ended Oct. 20 (announcment here).
Newly-Introduced Issues -- Brief Introduction by Issue Reporter, Q&A, and Identifying any Interested Parties To Help, etc.
* TOSCA-200 (Query based on capability) - Sivan (can somebody from Gigaspaces speak to this?)
* TOSCA-272 (Need to define "Relationship States" relative to Relationship lifecycle) - Matt (20 Aug)
* TOSCA-273 (D.3 Non-normative Node Types lack property descriptions) - Matt (20 Aug)
* TOSCA-274 (get_property syntax is not valid) - Luc (27 Aug)
* TOSCA-275 (Main Instance Model Ad Hoc Issue (Use for Suggestions/Contributions/etc)) - Luca (8 Sept)
Interoperability Subcommittee Report (Chair: Luc Boutier)
* TC Members are still invited to self-nominate for the role of Co-Chair or Vice Chair
* In response to growing TOSCA traction and maturity, this SC will reboot on November 25th with a shift in focus from public demonstration to conformance/testing and a different day/time
Instance Model Ad Hoc Group (Co-leaders: Sivan Barzilay and Alessandro Rossini)
* TOSCA-275 - This issue related to group activities, questions and suggestions from TC members, etc.
Ad Hoc on Container Support, e.g., Docker (lead: Hemal Surti)
* TOSCA-174 - This issue related to group activities, questions and suggestions from TC members, etc.
Ad Hoc on NFV - Network Function Virtualization (lead: Shitao Li)
* TOSCA-221 - Questions or suggestions for the group, general discussion, etc.
* NOTE: Latest TC-approved milestone (CSD02) published on 1 Oct 2015! See spec here.
Technical Marketing & Education Ad Hoc (lead: Karsten Beins)
IMPORTANT: Call for Co-Leader nominations!
* TOSCA-131 - This issue related to all such activities, questions and suggestions from TC members, etc.
** All current TC approved videos at the OASIS TOSCA YouTube Playlist
Ad Hoc on Monitoring (co-leaders: Luca Gioppo and Saji Thoppil)
* TOSCA-216 - This issue related to general group activities, questions and suggestions from TC members, etc.
ON HOLD: Ad Hoc on Network Features ()
* TOSCA-173 - This issue related to general group activities, questions and suggestions from TC members, etc.
TOSCA Ad Hoc on TOSCA Simple Profile v1.1 (leader: Matt Rutkowski)
This group aggragrates and acts upon the technical outputs and recommendations from the other ad hoc groups, as well
See explanation of OASIS document types and typical cadence
* TOSCA-7 (General suggestions/Questions -- Alternate encodings Service Templates, e.g., YAML/JSON and Simple Profile)
* v1.0 OASIS Standard documents
NOTE: ADDITIONAL TIME CAN BE ALLOCATED TO INTER-AD HOC WORKGROUP DISCUSSION AND COORDINATION, TIME PERMITTING
Cross-cutting Concerns, Issues, Suggestions, Questions for ALL v1.1 Documents and Deliverables
NOTE: All the below issues at the discretion of the co-chairs and time permitting. As always, technical issues must be posted in JIRA issues at least 48 hours to be considered by the TC. Naturally, any TC member can create or comment on a JIRA issue. Upload related documents to the OASIS website (please add links to the uploaded document in the JIRA issue). Please contact the co-chairs if you have any questions or problems.
* TOSCA-108: Catch-all for All Editorial Suggestions That Do NOT Change Semantics, e.g., spelling, grammar, readability
REMINDER: While a general approach can be decided by motion, specific proposals and contributions need to be JIRA issue |