Welcome / Roll
Co-chair appoints a scribe
Review/approve draft proposed agenda
Review/approve draft minutes
* Sept 3: https://www.oasis-open.org/committees/document.php?document_id=56407&wg_abbrev=tosca
** Thanks to Chris Lauwers for scribing
* Informal co-chair remarks and notables
** Also, please welcome new TC members: Bruno Volckaert from iMinds-IBCN, and Mr. Sandeep Lugani from WIPRO Limited
*** 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 (lead for continuity: Richard Probst)
* NOMINATIONS FOR CO-LEADERS NOW BEING ACCEPTED
* Will reboot, with more of a conformance/testing focus 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 (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 (lead for continuity: Ifat Afek)
NOMINATIONS FOR CO-LEADER NOW BEING ACCEPTED
* 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
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 CSD04! This has also been approved for 30 Day Public Review ending 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) - 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)
* TOSCA-268 (Useless DB_port in tosca.nodes.Database) - Luca (30 Jun)
* TOSCA-269 (tosca.nodes.Database should have some more optional properties) - Luca (Jun 30)
* TOSCA-270 (Reverse ordering of presentation in YAML document) - Luca (June 30)
* TOSCA-271 (Change "description" from a defintion to a TOSCA type to be consistent) - Matt (7 Jul)
* 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)
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 |