Welcome / Roll
Co-chair appoints a scribe
Review/approve draft proposed agenda
Review/approve draft minutes
* May 28: https://www.oasis-open.org/committees/document.php?document_id=55754&wg_abbrev=tosca
** Thanks to Chris Lauwers for scribing
* Informal co-chair remarks and notables
** Also, please welcome new TC members: Mr. Shay Naeh from GigaSpaces Technologies, Pamela Dragosh from AT&T and Mr. Uri Cohen 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)
** 2015-06-01 Minutes: https://www.oasis-open.org/apps/org/workgroup/tosca-interop/email/archives/201506/msg00000.html
** Revised Draft of CSAR file posted on 13 May: https://www.oasis-open.org/committees/document.php?document_id=55661&wg_abbrev=tosca
** Interop Demo at OSCON 2015 (current committed companies: Fujitsu, Gigaspaces, Huawei, IBM, Vnomic)
Technical Marketing & Education Ad Hoc (lead: Karsten Beins)
* TOSCA-131 - This issue related to all such activities, questions and suggestions from TC members, etc.
* INVITATION TO ALL TC MEMBERS: Submit organization/company videos for OASIS YouTube Channel!
** Upload candidate videos for TC review to the OASIS TOSCA TC Documents section (Working Drafts folder)
** All current TC approved videos at the OASIS TOSCA YouTube Playlist
Ad Hoc on NFV - Network Function Virtualization (lead: Shitao Li)
* TOSCA-221 - Questions or suggestions for the group, general discussion, etc.
Note: TOSCA Simple Profile for NFV candidate for CSD01 was approved by the TC on May 28th and can be downloaded here (OASIS is still processing official version)
Ad Hoc on Monitoring (co-leaders: Chip Holden 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: Avi Vachnis)
* TOSCA-173 - This issue related to general 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.
TOSCA Simple Profile in YAML v1.0 Ad Hoc Editorial Group
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
* TOSCA-202 (Cardinalities for capabilities and requirements) - Luc (23 Apr)
* TOSCA-205 (Add interface type) - Luc (23 Apr)
* TOSCA-208 (Add Conditional Capabilities) - Luc (23 Apr)
* TOSCA-220 (get_artifact function) - Luc (23 Apr)
* TOSCA-225 (Adding a (untyped) dependency relationship between Node Templates) - Derek
* TOSCA-226 (Proposal (incomplete) to change Requirement Def. from Ordered List to a Map) - Matt
* TOSCA-229 (Requirements / target filters and subsituable / selectable are too confusing) - Luc (23 Apr)
* TOSCA-232 (Adding metadata section in Service template) - Shitao
* TOSCA-233 (How to handle VM image in terms of software component) - Shitao
* TOSCA-234 (Discuss removing "github_url" property from non-normative Nodejs Node Type) - Matt
* TOSCA-235 (Endpoint capability needs support for Fixed IPs) - Matt (30 Apr)
* TOSCA-238 (Task: Author Section A.1.1 "A.1.1 Rules to avoid namespace collisions") - Matt (May 6)
NOTE: TOSCA-239 through TOSCA-251 already introduced in TC meeting of May 7th (see minutes)
* TOSCA-252 (node_filters should be available on requirement definition in addition to requirement assignment) - Luc (2 Jun)
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 |