Description:
IMPORTANT: Please examine this entire event description for a handy list of resources, responsibilities, and more!
P H O N E, W E B C O N F E R E N C I N G, A N D C H A T R O O M
Due to prankster calls, please contact the co-chairs using your OASIS-registered email address to obtain this information (reference: https://www.oasis-open.org/apps/org/workgroup/tosca/email/archives/201307/msg00013.html)
*** This meeting will use the phone bridge and web conferencing tool (also the new chatroom URL) specified by the co-chairs privately to all TC members ***
R E C O R D Y O U R O W N A T T E N D A N C E
Participants are responsible to log their attendance on this Kavi calendar entry. When you join the meeting, use this page to record your attendance by clicking "Record My Attendance". If you are not on the internet, you can request the chair to record your attendance on your behalf.
Y O U R S C R I B E R E S P O N S I B I L I T Y
Every person in the TC is asked to take their turn at scribing a meeting. When your name is called by the co-chair, please take your turn. You will use the chat room for the initial scribing.
Scribing is easy:
1. Change your name using setting button in the chat room to "YOUR NAME (Scribe - CO).
2. Record motions/votes and some context in the chat room during the meeting (people will add details and help). You don't have to quote people.
3. Later, use this template document to produce draft minutes of the meeting as recorded in the chat room: http://www.oasis-open.org/apps/org/workgroup/tosca/download.php/45088/TOSCA%20Minutes%20Template.docx (Copy/append the raw chat room contents at the end of the doc (copy/paste works fine in most browsers).
4. Post draft file called "TOSCA TC Minutes 2012-MM-DD" to "Meeting Notes" folder here: http://www.oasis-open.org/apps/org/workgroup/tosca/documents.php
T R A C K Y O U R V O T I N G R I G H T S
Participants are responsible for the state of their voting rights. The co-chairs will endeavor to update the roster at http://www.oasis-open.org/apps/org/workgroup/tosca/members/roster.php before meetings. Except for leaves of absence, the general rule is that a Voting Member who is absent from two consecutive meetings loses his or her voting rights at the end of the second Meeting missed, and a TC Member who has lost his or her voting rights shall regain them by attending two consecutive meetings after the end of the second Meeting attended. (see the TC Process section 2.4.4 for more details).
O T H E R R E S O U R C E S
TOSCA TC PAGE:
http://www.oasis-open.org/apps/org/workgroup/tosca/index.php
TOSCA JIRA Project (all proposals and issues): http://tools.oasis-open.org/issues/browse/TOSCA
PROPOSALS AND ISSUES:
TC standing rules for JIRA mandate that all technical and deliverable proposals and issues be in the form of JIRA issues and will only be voted upon after 1 week. Issues can be discussed at any time. For details, see the approved proposal at: http://www.oasis-open.org/apps/org/workgroup/tosca/email/archives/201112/msg00030.html
P H O N E, W E B C O N F E R E N C I N G, A N D C H A T R O O M
Due to prankster calls, please contact the co-chairs using your OASIS-registered email address to obtain this information (reference: https://www.oasis-open.org/apps/org/workgroup/tosca/email/archives/201307/msg00013.html)
*** This meeting will use the phone bridge and web conferencing tool (also the new chatroom URL) specified by the co-chairs privately to all TC members ***
R E C O R D Y O U R O W N A T T E N D A N C E
Participants are responsible to log their attendance on this Kavi calendar entry. When you join the meeting, use this page to record your attendance by clicking "Record My Attendance". If you are not on the internet, you can request the chair to record your attendance on your behalf.
Y O U R S C R I B E R E S P O N S I B I L I T Y
Every person in the TC is asked to take their turn at scribing a meeting. When your name is called by the co-chair, please take your turn. You will use the chat room for the initial scribing.
Scribing is easy:
1. Change your name using setting button in the chat room to "YOUR NAME (Scribe - CO).
2. Record motions/votes and some context in the chat room during the meeting (people will add details and help). You don't have to quote people.
3. Later, use this template document to produce draft minutes of the meeting as recorded in the chat room: http://www.oasis-open.org/apps/org/workgroup/tosca/download.php/45088/TOSCA%20Minutes%20Template.docx (Copy/append the raw chat room contents at the end of the doc (copy/paste works fine in most browsers).
4. Post draft file called "TOSCA TC Minutes 2012-MM-DD" to "Meeting Notes" folder here: http://www.oasis-open.org/apps/org/workgroup/tosca/documents.php
T R A C K Y O U R V O T I N G R I G H T S
Participants are responsible for the state of their voting rights. The co-chairs will endeavor to update the roster at http://www.oasis-open.org/apps/org/workgroup/tosca/members/roster.php before meetings. Except for leaves of absence, the general rule is that a Voting Member who is absent from two consecutive meetings loses his or her voting rights at the end of the second Meeting missed, and a TC Member who has lost his or her voting rights shall regain them by attending two consecutive meetings after the end of the second Meeting attended. (see the TC Process section 2.4.4 for more details).
O T H E R R E S O U R C E S
TOSCA TC PAGE:
http://www.oasis-open.org/apps/org/workgroup/tosca/index.php
TOSCA JIRA Project (all proposals and issues): http://tools.oasis-open.org/issues/browse/TOSCA
PROPOSALS AND ISSUES:
TC standing rules for JIRA mandate that all technical and deliverable proposals and issues be in the form of JIRA issues and will only be voted upon after 1 week. Issues can be discussed at any time. For details, see the approved proposal at: http://www.oasis-open.org/apps/org/workgroup/tosca/email/archives/201112/msg00030.html
==========
Agenda:
Welcome / Roll
Co-chair appoints a scribe
Review/approve draft proposed agenda
Review/approve draft minutes
* July 3: https://www.oasis-open.org/committees/document.php?document_id=53413&wg_abbrev=tosca
** Thanks to Efraim Moscovich for scribing
* Informal co-chair remarks
** Also, please welcome Dmitri Krasnenko from Alcatel-Lucent, Dmitri Krasnenko from Alcatel-Lucent, and Kapil Thangavelu from Canonical
*** This is a new feature. Please pardon a delayed invitation, if you are a new member.
Interoperability Subcommittee Report
* Status and updates from co-chairs (Matt Rutkowski and Richard Probst)
** 2014-06-30 Minutes: https://www.oasis-open.org/committees/document.php?document_id=53478&wg_abbrev=tosca-interop
** 2014-06-23 Minutes: https://www.oasis-open.org/committees/document.php?document_id=53432&wg_abbrev=tosca-interop
** SC-approved short abstract for ODCA 2014 Forecast Conference
** SC-approved long abstract for ODCA 2014 Forecast Conference
** Suggested motion: The TC supports the SC-approved short abstract and long abstracts at www.oasis-open.org/committees/document.php?document_id=53479&wg_abbrev=tosca and www.oasis-open.org/committees/document.php?document_id=53430&wg_abbrev=tosca-interop, respectively, for use at the ODCA 2014 Forecast Conference and other TC-approved public activities.
Ad Hoc on Container Support, e.g., Docker, and TOSCA synergies (lead: Hemal Surti)
* TOSCA-174 - This issue related to group activities
Marketing and Education Ad Hoc (lead: Karsten Beins)
* TOSCA-131 - This issue related to all such activities
Ad Hoc to Specify 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. Use cases from Derek, Dale, others. Search in JIRA for other "network" related issues.
* TOSCA-175 (Support navigation within the service template)
TOSCA v1.1
NOTE: As always, only JIRA issues will be considered by the TC for v1.1 document changes (any TC member can create a JIRA issue. These issues at the discretion of the co-chairs and time permitting. Please contact the co-chairs if you have technical issues or questions)
* Resources
* Current "base" for proposed spec changes, see Candidate OASIS Standard (public)
* TOSCA-108: Catch-all for All Editorial Suggestions That Do NOT Change Semantics, e.g., spelling, grammar, readability, layout (use for all v1.1 documents)
* Editor's Report
* TOSCA-7 (Alternate encodings Service Templates, e.g., YAML/JSON
Newly-Introduced Issues -- Brief Overview for TC and Discussion
*** TOSCA-176 (Add connectivity ability to Compute)
*** TOSCA-177 (Cardinality for node template)
*** TOSCA-178 (Define how an operation can expose outputs)
*** TOSCA-179 (Add "timeout" and "retry" keynames to an operation)
*** TOSCA-180 (Support of secured repositories for artifacts)
WD02-related issues (The below was previously introduced to the TC. Any questions, suggestions, or requests to discuss further?)
Note: Review issues that are receiving most attention in the YAML ad hoc. Any decisions or challenges?
*** TOSCA-132 (Use "set_property" methods to "push" values from template inputs to nodes)
*** 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-135 (Define/reference a Regex language (or subset) we wish to support for constraints)
*** TOSCA-138 (Define a Network topology for L2 Networks, etc.)
*** TOSCA-139 (Compute node scalability should be specified with a Compute node capability)
*** TOSCA-140 (Constraining the capabilities of multiple node templates)
*** TOSCA-141 (Specifying Environment Constraints for Node Templates)
*** TOSCA-142 (Define normative Artifact Types
*** TOSCA-143 (Define normative tosca.nodes.Network Node Type)
*** TOSCA-144 (Update Ch 6, Example 5, "Template for deploying a two-tier application servers.on two")
*** TOSCA-145 (Update Ch 7, Example 6, "Template for deploying a two-tier application on two servers.")
*** TOSCA-146 (Define a grammar for each property function and provide examples)
*** TOSCA-147 (Define grammar for and examples of using Relationship templates)
*** TOSCA-148 (Need a means to express cardinality on relationships)
*** 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-151 (Resolve spec. behavior if name collisions occur on named Requirements )
*** TOSCA-152 (Extend Requirement grammar to support "Optional/Best Can" Capability Type matching)
*** TOSCA-153 (Define grammar and usage of Service Template keyname)
*** TOSCA-154 (Decide how security/access control work with Nodes, update grammar, etc.)
*** TOSCA-155 (How do we provide constraints on properties declared as simple YAML lists)
*** TOSCA-156 (Are there IPv6 considerations (e.g., new properties) for tosca.capabilities.Endpoint)
*** TOSCA-157 (Can/how do we make a property defn. "final" or "read-only")
*** TOSCA-158 (Provide prose describging how Feature matching is done by orchestrators)
*** 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-161 (Need examples of using the built-in feature (Capability) and dependency (Requirement) of tosca.nodes.Root)
*** 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-164 (Do we need a restart lifecycle operation for nodes?)
*** 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-169 (Resolve text and grammar for the "get_ref_property" function)
*** TOSCA-170 (Explicit textual mention, and grammar support, for adding (extending) node operations)
WD03-related issues (New or Ready to be Revisited -- Overview for TC and Discussion/Questions)
WD03-related issues (The below was previously introduced to the TC. Any questions, suggestions, or requests to discuss further?)
*** 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-126 (Specifying connectivity to endpoints hosted outside a Service Template)
** TOSCA-127 (Conventions for provisioning network connectivity for Service Templates)
** TOSCA-114 (Composite Capabilities and Requirements)
** TOSCA-12 (Basic Node Types) -- also related is TOSCA-11 (Lifecycle Operations) -- Simple Profile, essentially
TOSCA v1.0
* TOSCA-171 (Various v1.0 spec bugs)
* AOB
REMINDER: While a general approach can be decided by motion, specific proposals and contributions need to be JIRA issue
==========
Minutes:
==========
Attendance:
| Meeting Statistics |
| Quorum rule |
51% of voting members
|
| Achieved quorum |
yes |
| Individual Attendance |
Contributing Members: 17 of 104 (16%)
Voting Members: 17 of 25 (68%) (used for quorum calculation)
|
| Company Attendance |
Contributing Companies: 11 of 31 (35%)
Voting Companies: 11 of 14 (78%)
|