Welcome / Roll
Co-chair appoints a scribe
Review/approve draft proposed agenda
Review/approve draft minutes
* Aug 20: https://www.oasis-open.org/committees/document.php?document_id=56359&wg_abbrev=tosca
** Thanks to Jacques Durand for scribing
* Informal co-chair remarks and notables
** Also, please welcome new TC members: Mr. Sandeep Lugani from WIPRO Limited and Mr. Jeremy Hess from GigaSpaces Technologies
*** New members: expect a delay, but you will be added to this list within a couple weeks of joining of the TC
Interoperability Subcommittee Report (co-leaders: Matt Rutkowski and Richard Probst)
* Aug 24: NO MEETING
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 (CSD01) published on 19 June 2015! See message with links here.
Technical Marketing & Education Ad Hoc (lead: Karsten Beins)
* 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: Roger Dev and Ifat Afek)
* TOSCA-216 - This issue related to general group activities, questions and suggestions from TC members, etc.
TABLED: Ad Hoc on Network Features (lead: ???)
* TOSCA-173 - This issue related to general group activities, questions and suggestions from TC members, etc.
Presentation on TOSCA Models@run-time
A continuous of Q&A / Discussion led by Alessandro Rossini from the TC meeting of August 13th
* TOSCA-274 (get_property syntax is not valid) - Luc Boutier (Aug 26)
Note: since Luc indicated this is a blocking/critical problem, providing him an opportunity to introduce the issue prior to Simple Profile in YAML candidate review
TOSCA Ad Hoc on TOSCA Simple Profile in YAML v1.0
* Discussion of conformance section (Jacques/Editors)
* Response and actions to suggestions from OASIS staff (on CSD03) - Editors
* Walkthrough / Q&A / Discussion - Editors/all
* IMPORTANT: As discussed at the TC meeting of August 20th, it is likely that the TC will entertain a motion to approve the latest spec as CSD04, and possibly progression to public review, as well.
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: Latest TC-approved milestone (CSD03) published on 19 May 2015! See message with links 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) - Yaron (can somebody from Gigaspaces speak to this?)
* TOSCA-262 (Specify if the artifact has to be "elaborated" on orchestrator or on node) - Luca (17 Jun)
* TOSCA-263 (Define an C.8.5.5 tosca.artifact.implementation.exec) - Luca (17 Jun)
* TOSCA-264 (XSD validation) - Luca (17 Jun)
* TOSCA-265 (Different flavours of the same Service) - Luca (18 Jun)
* TOSCA-266 (Creating an abstract or phantom node) - Luca (19 Jun)
NOTE: TOSCA-267 through TOSCA-270 to be added shortly
* TOSCA-271 (Change "description" from a defintion to a TOSCA type to be consistent) - Matt (7 Jul)
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 |