Welcome / Roll
Co-chair appoints a scribe
Review/approve draft proposed agenda
Review/approve draft minutes
* October 30: https://www.oasis-open.org/committees/document.php?document_id=54444&wg_abbrev=tosca
** Thanks to Lowell Higley for scribing
* Informal co-chair remarks and notables
** Very successful half-day November 13th ad hoc meeting. Minutes can be found here.
** TOSCA v1.0 CSD02 Errata published
** Also, please welcome new TC members Mr. Ran Ziv from GigaSpaces Technologies, Mr. Li Xu of Neusoft, Mr. Nati Shalom from GigaSpaces Technologies, Ms. chunxiu jia from Huawei, Nikunj Nemani from VMware, Wan Anfeng from Huawei, and Radek Pospisil from Hewlett-Packard
*** 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
* Status and updates from co-chairs (Matt Rutkowski and Richard Probst)
** Minutes of 2014-11-10: https://www.oasis-open.org/apps/org/workgroup/tosca-interop/email/archives/201411/msg00000.html
Technical Marketing & Education Ad Hoc (lead: Karsten Beins)
* TOSCA-131 - This issue related to all such activities
** INVITATION TO ALL TC MEMBERS: Submit organization/company videos by uploading them to the OASIS TOSCA TC Documents section (Working Drafts folder)
** All TC approved videos at: OASIS TOSCA YouTube Playlist
Ad Hoc on Network Features (lead: Avi Vachnis)
* Meeting invitation and logistics (open to all TC members, of course)
* TOSCA-173 - This issue related to general group activities.
Ad Hoc on Container Support, e.g., Docker (lead: Hemal Surti)
* Hemal is leading work on container white paper
* TOSCA-174 - This issue related to group activities
Ad Hoc on Monitoring (formation)
* Call for candidates (current self-nominations: Chip Holden & Tomer Shtilman)
* Statements (if more than 2 candidates)
* Motion to approve
Review and Consideration of Issues Nominated for Closure by Nov. 13th Ad Hoc Meeting (can optionally be conducted in conjunction with review of latest WD of Simple Profile / YAML doc)
1. Each issue will be briefly described along with an equally brief description of the resolution.
2. The Co-Chair will ask if any TC member would oppose closure and note such
3. At the end of the review, non-contested issues will be motioned for closure.
4. Contested issues will be discussed, time permitting.
* TOSCA-133 (add material for defining a nested template that implements a node type)
* TOSCA-134 (Define TOSCA version type based upon Apache Maven versioning)
* TOSCA-139 (Compute node scalability should be specified with a Compute node capability)
* TOSCA-147 (Define grammar for and examples of using Relationship templates)
* TOSCA-149 (Create an independent section to describe a single requirement definition's grammar)
* TOSCA-150 (Work towards a common syntax for Requirement definitions)
* TOSCA-157 (Can/how do we make a property defn. "final" or "read-only")* TOSCA-157 (Can/how do we make a property defn. "final" or "read-only")
* TOSCA-159 (Describe how not all interfaces need to supply scripts (artifacts), it is a no-op behavior)
* TOSCA-160 (Need examples of using the "tosca.interfaces.relationship.Configure" interface)
* TOSCA-164 (Do we need a restart lifecycle operation for nodes?)
* TOSCA-177 (Cardinality for node template)
* TOSCA-190 (Fix grammar for "Constraints" on a Target node of a requirement)
* TOSCA-203 (Properties defined with type number (should be integer or float based on the valid types)
TOSCA v1.1 Simple Profile and YAML Language Rendering (can optionally be conducted in conjunction with review of candidate issues for closure)
NOTE: As always, only JIRA issues will be considered by the TC for v1.1 for validation and approval. Note that any TC member can create or comment on a JIRA issue, upload related documents to Kavi (the OASIS website), etc. Please contact the co-chairs if you have any questions. The below issues at the discretion of the co-chairs and time permitting.
*** See TOSCA-7 (Alternate encodings Service Templates, e.g., YAML/JSON and Simple Profile)
* Resources
** See explanation of OASIS document types and typical cadence
** Current "base" for v1.1 XML Spec and Simple Profile is the v1.0 OASIS Standard documents (public)
** Note however that much work for v1.1 is being done first on the YAML rendering and Simple Profile Document (last TC approved CSD is CSD01 posted March 27, 2014)
** TOSCA-108: Catch-all for All Editorial Suggestions That Do NOT Change Semantics, e.g., spelling, grammar, readability (use for all v1.1 documents)
Review and Consideration of Issues Nominated for Deferal by Nov. 13th Ad Hoc Meeting (can optionally be conducted in conjunction with review of latest WD of Simple Profile / YAML doc)
1. Each issue will be briefly described along with an equally brief description of the resolution.
2. The Co-Chair will ask if any TC member would oppose deferal and note such
3. At the end of the review, non-contested issues will be motioned for deferal
4. Contested issues will be discussed, time permitting.
* TOSCA-154 (Decide how security/access control work with Nodes, update grammar, etc.)
* TOSCA-156 (Are there IPv6 considerations (e.g., new properties) for tosca.capabilities.Endpoint)
* TOSCA-158 (Provide prose describging how Feature matching is done by orchestrators)
* TOSCA-161 (Need examples of using the built-in feature (Capability) and dependency (Requirement) of tosca.nodes.Root - see TOSCA-181)
* TOSCA-162 (Provide recognized values fo tosca.nodes.compute properties: os_arch)
* TOSCA-163 (Provide recognized values fo tosca.nodes.BlockStorage: store_fs_type)
* TOSCA-165 (New use case / example: Selection/Replacement of web server type)
* TOSCA-166 (New use case / example: Web Server with (one or more) runtimes environments)
* TOSCA-167 (New use case / example: Show abstract substitution of Compute node OS...)
* TOSCA-168 (New use case / example: Show how substitution of IaaS can be accomplished)
* TOSCA-176 (Add connectivity ability to Compute)
* TOSCA-179 (Add "timeout" and "retry" keynames to an operation)
* TOSCA-201 (Harmonize Properties and Capabilities in Node Types)
Newly-Introduced Issues -- Brief Overview for TC and Discussion
* TOSCA-193 (Need to support "implements" keyword and add to grammar)
* TOSCA-194 (Nested Service Templates should be able to define additional operations)
* TOSCA-195 (Add new normative Runtime capability in the TOSCA spec)
REMINDER: While a general approach can be decided by motion, specific proposals and contributions need to be JIRA issue |