OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Modified NEW! TOSCA TC Regular Meeting


Submitter's message
Adding suggested motion (some Kavi problems, too)
--
Event Title: NEW! TOSCA TC Regular Meeting

Date: Thursday, 14 August 2014, 12:00pm to 01:30pm EDT
Location: See private email to TC members. Please contact co-chairs using the email address you used to register with OASIS for this information, if you do not have it.
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, 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. Instructions will be provided in advance to any volunteer. 

 

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


This meeting counts towards voter eligibility.

Agenda

Welcome / Roll
Co-chair appoints a scribe
Review/approve draft proposed agenda
Review/approve draft minutes
* August 7: https://www.oasis-open.org/committees/document.php?document_id=53778&wg_abbrev=tosca
** Thanks to David Edery for scribing 
* July 24: https://www.oasis-open.org/committees/document.php?document_id=53680&wg_abbrev=tosca
** Thanks to Richard Probst for scribing
* Informal co-chair remarks
Suggested motion: The TC approves two LOA requests that were made within the same 12 month period from Peter Gibbels (July 31 through August 22) and Thomas Spatzier (August 16 through August 31).
** ODCA Forecast 2014 free passes (see here)
** Also, please welcome new TC members Jim Hunter from CA Technologies, Vasile Radoaca from Alcatel-Lucent, Noa Koffman from Alcatel-LucentLarry Lamers from VMWare, Kurt Spence from CA Technologies, and Wayne Witzel III from Canonical  
*** 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--8-11: https://www.oasis-open.org/apps/org/workgroup/tosca-interop/email/archives/201408/msg00010.html
** Minutes of 2014-08-04: https://www.oasis-open.org/apps/org/workgroup/tosca-interop/email/archives/201408/msg00002.html
*** IMPORTANT: You only need 1 slide to participate in the video the TC is preparing for ODCA Forecast (specify your 1 sentence voiceover (see email))
** ODCA Forecast Conference Video Slides (8/11): https://www.oasis-open.org/committees/document.php?document_id=53785&wg_abbrev=tosca
** TC-approved short abstract and long abstract  for ODCA Forecast Conference

 

Technical Marketing & Education Ad Hoc (lead: Karsten Beins)  
TOSCA-131 - This issue related to all such activities 

 

Ad Hoc on Container Support, e.g., Docker (lead: Hemal Surti) 
TOSCA-174 - This issue related to group activities

 

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.  
TOSCA-175 (Support navigation within the service template)

 

TOSCA V1.0 Errata 
TOSCA-124: Errata - Reference Correction
** Note: changes from approved CSD01 consist of addition of schema file and spelling corrections.
** Suggested motion: the TC to approves the Errata found at https://www.oasis-open.org/apps/org/workgroup/tosca/download.php/53678/TOSCA-v1.0-errata01-csd02.zip, and instructs the co-chairs to submit this to OASIS staff as Committee Spec Draft 02. Further, the TC instructs the co-chairs to request a public review for this document, once approved as CSD02.

 

TOSCA v1.1
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)
*** Suggested motion: The TC approves the document found at https://www.oasis-open.org/committees/document.php?document_id=53805&wg_abbrev=tosca as a general milestone and instructs the editors to accept all changes in that document, post a copy of that clean version to Kavi, and then create from the clean version the first rev of WD03. 

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)

 

Newly-Introduced Issues -- Brief Overview for TC and Discussion

*** TOSCA-176 (Add connectivity ability to Compute) 
*** TOSCA-180 (Support of secured repositories for artifacts)

 

These issues have been recently introduced to the TC
NOTE: These should be associated with a CSD, e.g., CSD02 or CSD03
*** TOSCA-178 (Define how an operation can expose outputs)
*** TOSCA-177 (Cardinality for node template)
*** TOSCA-179 (Add "timeout" and "retry" keynames to an operation)

 

CSD02-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) 

CSD03-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)

REMINDER: While a general approach can be decided by motion, specific proposals and contributions need to be JIRA issue



Owner: Mr. Paul Lipton
Group: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
Sharing: This event is shared with the OASIS Open (General Membership), and General Public groups. Public Event Link

Microsoft Outlook users: You will see event notifications requiring further action in your Outlook mail application.
Non-Outlook users: We still recommend subscribing to a Group or organization-wide calendar to keep your calendar updated.

  • Learn more about subscribing here.
  • View the updated Group web calendar here.

Attachment: ical_35873.ics
Description: application/ics

BEGIN:VCALENDAR
CALSCALE:GREGORIAN
METHOD:REQUEST
VERSION:2.0
PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:STANDARD
DTSTART:20001029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T060000Z
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:STANDARD
DTSTART:20071104T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000402T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T070000Z
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T020000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
STATUS:CONFIRMED
TRANSP:OPAQUE
DTSTAMP:20140813T041010Z
DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20140814T120000
DTEND;VALUE=DATE-TIME;TZID=America/New_York:20140814T133000
SEQUENCE:7883
SUMMARY:NEW! TOSCA TC Regular Meeting
LOCATION:See private email to TC members. Please contact co-chairs using the email address you used to register with OASIS for this information, if you do not have it.
LAST-MODIFIED:20140813T041010Z
ORGANIZER:tc_admin@oasis-open.org
DESCRIPTION:IMPORTANT: Please examine this entire event description for 
 a handy list of resources\, responsibilities\, and more!\n\n
  \n\nP 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\nDue to prankster calls\, this meeting will u
 se the phone bridge and web conferencing tool (also the new 
 chatroom URL) specified by the co-chairs privately to all TC
  members.\n\n \n\n  \n\nR E C O R D   Y O U R   O W N   A T 
 T E N D A N C E\nParticipants are responsible to log their a
 ttendance on this Kavi calendar entry. When you join the mee
 ting\, use this page to record your attendance by clicking &
 quot\;Record My Attendance&quot\;. If you are not on the int
 ernet\, you can request the chair to record your attendance 
 on your behalf.\n\n \n\n  \n\nY O U R   S C R I B E   R E S 
 P O N S I B I L I T Y\nEvery person in the TC is asked to ta
 ke their turn at scribing a meeting. When your name is calle
 d by the co-chair\, please take your turn. You will use the 
 chat room for the initial scribing. Scribing is easy. Instru
 ctions will be provided in advance to any volunteer. \n\n \n
 \nT R A C K   Y O U R   V O T I N G   R I G H T S\nParticipa
 nts are responsible for the state of their voting rights. Th
 e 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 consecut
 ive meetings loses his or her voting rights at the end of th
 e second Meeting missed\, and a TC Member who has lost his o
 r her voting rights shall regain them by attending two conse
 cutive meetings after the end of the second Meeting attended
 . (see the TC Process section 2.4.4 for more details).\n\n \
 n\n \n\nO T H E R   R E S O U R C E S \n\nTOSCA TC PAGE:\n\n
 http://www.oasis-open.org/apps/org/workgroup/tosca/index.php
 \n\n \n\nTOSCA JIRA Project (all proposals and issues): http
 ://tools.oasis-open.org/issues/browse/TOSCA\n\n \n\nPROPOSAL
 S AND ISSUES:\n\nTC standing rules for JIRA mandate that all
  technical and deliverable proposals and issues be in the fo
 rm of JIRA issues and will only be voted upon after 1 week. 
 Issues can be discussed at any time. For details\, see the a
 pproved proposal at: http://www.oasis-open.org/apps/org/work
 group/tosca/email/archives/201112/msg00030.html\n\n \n\n \n\
 nP 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\n\nDue 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)\n\
 n \n\n*** This meeting will use the phone bridge and web con
 ferencing tool (also the new chatroom URL) specified by the 
 co-chairs privately to all TC members ***\n\n \n\n  \n\nR E 
 C O R D   Y O U R   O W N   A T T E N D A N C E\n\nParticipa
 nts are responsible to log their attendance on this Kavi cal
 endar entry. When you join the meeting\, use this page to re
 cord your attendance by clicking &quot\;Record My Attendance
 &quot\;. If you are not on the internet\, you can request th
 e chair to record your attendance on your behalf.\n\n \n\n  
 \n\nY O U R   S C R I B E   R E S P O N S I B I L I T Y\n\nE
 very person in the TC is asked to take their turn at scribin
 g a meeting. When your name is called by the co-chair\, plea
 se take your turn. You will use the chat room for the initia
 l scribing.\n\n \n\nScribing is easy:\n\n1. Change your name
  using setting button in the chat room to &quot\;YOUR NAME (
 Scribe - CO). \n\n2. Record motions/votes and some context i
 n the chat room during the meeting (people will add details 
 and help). You don&#39\;t have to quote people.\n\n3. 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%20Min
 utes%20Template.docx (Copy/append the raw chat room contents
  at the end of the doc (copy/paste works fine in most browse
 rs).\n\n4. Post draft file called &quot\;TOSCA TC Minutes 20
 12-MM-DD&quot\; to &quot\;Meeting Notes&quot\; folder here: 
 http://www.oasis-open.org/apps/org/workgroup/tosca/documents
 .php\n\n \n\n  \n\nT R A C K   Y O U R   V O T I N G   R I G
  H T S\n\nParticipants are responsible for the state of thei
 r voting rights. The co-chairs will endeavor to update the r
 oster at http://www.oasis-open.org/apps/org/workgroup/tosca/
 members/roster.php before meetings. Except for leaves of abs
 ence\, the general rule is that a Voting Member who is absen
 t from two consecutive meetings loses his or her voting righ
 ts 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 seco
 nd Meeting attended. (see the TC Process section 2.4.4 for m
 ore details).\n\n \n\n \n\nO T H E R   R E S O U R C E S \n\
 nTOSCA TC PAGE:\n\nhttp://www.oasis-open.org/apps/org/workgr
 oup/tosca/index.php\n\n \n\nTOSCA JIRA Project (all proposal
 s and issues): http://tools.oasis-open.org/issues/browse/TOS
 CA\n\n \n\nPROPOSALS AND ISSUES:\n\nTC standing rules for JI
 RA 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-ope
 n.org/apps/org/workgroup/tosca/email/archives/201112/msg0003
 0.html\n\nAgenda: Welcome / Roll\nCo-chair appoints a scribe
 \nReview/approve draft proposed agenda\nReview/approve draft
  minutes\n* August 7: https://www.oasis-open.org/committees/
 document.php?document_id=53778&wg_abbrev=tosca\n** Thanks to
  David Edery for scribing \n* July 24: https://www.oasis-ope
 n.org/committees/document.php?document_id=53680&wg_abbrev=to
 sca\n** Thanks to Richard Probst for scribing\n* Informal co
 -chair remarks\nSuggested motion: The TC approves two LOA re
 quests that were made within the same 12 month period from P
 eter Gibbels (July 31 through August 22) and Thomas Spatzier
  (August 16 through August 31).\n** ODCA Forecast 2014 free 
 passes (see https://www.oasis-open.org/apps/org/workgroup/to
 sca/email/archives/201407/msg00041.html)\n** Also\, please w
 elcome new TC members Jim Hunter from CA Technologies\, Vasi
 le Radoaca from Alcatel-Lucent\, Noa Koffman from Alcatel-Lu
 cent\, Larry Lamers from VMWare\, Kurt Spence from CA Techno
 logies\, and Wayne Witzel III from Canonical  \n*** New memb
 ers: expect a delay\, but you will be added to this list wit
 hin a couple weeks of joining of the TC\n\nInteroperability 
 Subcommittee Report\n* Status and updates from co-chairs (Ma
 tt Rutkowski and Richard Probst) \n** Minutes of 2014--8-11:
  https://www.oasis-open.org/apps/org/workgroup/tosca-interop
 /email/archives/201408/msg00010.html\n** Minutes of 2014-08-
 04: https://www.oasis-open.org/apps/org/workgroup/tosca-inte
 rop/email/archives/201408/msg00002.html\n*** IMPORTANT: You 
 only need 1 slide to participate in the video the TC is prep
 aring for ODCA Forecast (specify your 1 sentence voiceover (
 see https://www.oasis-open.org/apps/org/workgroup/tosca/emai
 l/archives/201408/msg00020.html))\n** ODCA Forecast Conferen
 ce Video Slides (8/11): https://www.oasis-open.org/committee
 s/document.php?document_id=53785&wg_abbrev=tosca\n** TC-appr
 oved https://www.oasis-open.org/committees/document.php?docu
 ment_id=53479&wg_abbrev=tosca and https://www.oasis-open.org
 /committees/document.php?document_id=53430&wg_abbrev=tosca-i
 nterop  for ODCA Forecast Conference\n\n \n\nTechnical Marke
 ting & Education Ad Hoc (lead: Karsten Beins)  \n* https://t
 ools.oasis-open.org/issues/browse/TOSCA-131 - This issue rel
 ated to all such activities \n\n \n\nAd Hoc on Container Sup
 port\, e.g.\, Docker (lead: Hemal Surti) \n* https://tools.o
 asis-open.org/issues/browse/TOSCA-174 - This issue related t
 o group activities\n\n \n\nAd Hoc on Network Features (lead:
  Avi Vachnis)\n\n* https://www.oasis-open.org/apps/org/workg
 roup/tosca/email/archives/201407/msg00000.html (open to all 
 TC members\, of course) \n* https://tools.oasis-open.org/iss
 ues/browse/TOSCA-173 - This issue related to general group a
 ctivities.  \n* https://tools.oasis-open.org/issues/browse/T
 OSCA-175 (Support navigation within the service template)\n\
 n \n\nTOSCA V1.0 Errata \n* https://issues.oasis-open.org/br
 owse/TOSCA-124: Errata - Reference Correction\n** Note: chan
 ges from approved CSD01 consist of addition of schema file a
 nd spelling corrections.\n** Suggested motion: the TC to app
 roves the Errata found at https://www.oasis-open.org/apps/or
 g/workgroup/tosca/download.php/53678/TOSCA-v1.0-errata01-csd
 02.zip\, and instructs the co-chairs to submit this to OASIS
  staff as Committee Spec Draft 02. Further\, the TC instruct
 s the co-chairs to request a public review for this document
 \, once approved as CSD02.\n\n \n\nTOSCA v1.1\nNOTE: As alwa
 ys\, only JIRA issues will be considered by the TC for v1.1 
 for validation and approval. Note that any TC member can cre
 ate or comment on a JIRA issue\, upload related documents to
  Kavi (the OASIS website)\, etc. Please contact the co-chair
 s if you have any questions. The below issues at the discret
 ion of the co-chairs and time permitting. \n*** See https://
 tools.oasis-open.org/issues/browse/TOSCA-7 (Alternate encodi
 ngs Service Templates\, e.g.\, YAML/JSON)\n*** Suggested mot
 ion: The TC approves the document found at https://www.oasis
 -open.org/committees/document.php?document_id=53805&wg_abbre
 v=tosca as a general milestone and instructs the editors to 
 accept all changes in that document\, post a copy of that cl
 ean version to Kavi\, and then create from the clean version
  the first rev of WD03. \n\n* Resources\n** See https://www.
 oasis-open.org/apps/org/workgroup/tosca/email/archives/20140
 7/msg00007.html\n** Current &quot\;base&quot\; for v1.1 XML 
 Spec and Simple Profile is the http://docs.oasis-open.org/to
 sca/TOSCA/v1.0/os/ (public)\n** Note however that much work 
 for v1.1 is being done first on the YAML rendering and Simpl
 e Profile Document (last TC approved CSD is http://docs.oasi
 s-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.0/posted March
  27\, 2014) \n** https://tools.oasis-open.org/issues/browse/
 TOSCA-108: Catch-all for All Editorial Suggestions That Do N
 OT Change Semantics\, e.g.\, spelling\, grammar\, readabilit
 y (use for all v1.1 documents)\n\n \n\nNewly-Introduced Issu
 es -- Brief Overview for TC and Discussion\n\n*** https://is
 sues.oasis-open.org/browse/TOSCA-176 (Add connectivity abili
 ty to Compute) \n*** https://issues.oasis-open.org/browse/TO
 SCA-180 (Support of secured repositories for artifacts)\n\n 
 \n\nThese issues have been recently introduced to the TC\nNO
 TE: These should be associated with a CSD\, e.g.\, CSD02 or 
 CSD03\n*** https://issues.oasis-open.org/browse/TOSCA-178 (D
 efine how an operation can expose outputs)\n*** https://issu
 es.oasis-open.org/browse/TOSCA-177 (Cardinality for node tem
 plate)\n*** https://issues.oasis-open.org/browse/TOSCA-179 (
 Add &quot\;timeout&quot\; and &quot\;retry&quot\; keynames t
 o an operation)\n\n \n\nCSD02-related issues (The below was 
 previously introduced to the TC. Any questions\, suggestions
 \, or requests to discuss further?)\nNote: Review issues tha
 t are receiving most attention in the YAML ad hoc. Any decis
 ions or challenges? \n*** https://tools.oasis-open.org/issue
 s/browse/TOSCA-132(Use &quot\;set_property&quot\; methods to
  &quot\;push&quot\; values from template inputs to nodes) \n
 *** https://tools.oasis-open.org/issues/browse/TOSCA-133 (ad
 d material for defining a nested template that implements a 
 node type)\n*** https://tools.oasis-open.org/issues/browse/T
 OSCA-134 (Define TOSCA version type based upon Apache Maven 
 versioning)\n*** https://tools.oasis-open.org/issues/browse/
 TOSCA-135 (Define/reference a Regex language (or subset) we 
 wish to support for constraints)\n*** https://tools.oasis-op
 en.org/issues/browse/TOSCA-138 (Define a Network topology fo
 r L2 Networks\, etc.)\n*** https://tools.oasis-open.org/issu
 es/browse/TOSCA-139 (Compute node scalability should be spec
 ified with a Compute node capability)\n*** https://tools.oas
 is-open.org/issues/browse/TOSCA-140 (Constraining the capabi
 lities of multiple node templates)\n*** https://tools.oasis-
 open.org/issues/browse/TOSCA-141 (Specifying Environment Con
 straints for Node Templates) \n*** https://tools.oasis-open.
 org/issues/browse/TOSCA-142 (Define normative Artifact Types
  \n*** https://tools.oasis-open.org/issues/browse/TOSCA-143 
 (Define normative tosca.nodes.Network Node Type)\n*** https:
 //tools.oasis-open.org/issues/browse/TOSCA-144(Update Ch 6\,
  Example 5\, &quot\;Template for deploying a two-tier applic
 ation servers.on two&quot\;)\n*** https://tools.oasis-open.o
 rg/issues/browse/TOSCA-145 (Update Ch 7\, Example 6\, &quot\
 ;Template for deploying a two-tier application on two server
 s.&quot\;)\n*** https://tools.oasis-open.org/issues/browse/T
 OSCA-146 (Define a grammar for each property function and pr
 ovide examples)\n\n*** https://tools.oasis-open.org/issues/b
 rowse/TOSCA-147 (Define grammar for and examples of using Re
 lationship templates)\n*** https://tools.oasis-open.org/issu
 es/browse/TOSCA-148 (Need a means to express cardinality on 
 relationships)\n*** https://tools.oasis-open.org/issues/brow
 se/TOSCA-149 (Create an independent section to describe a si
 ngle requirement definition&#39\;s grammar)\n*** https://too
 ls.oasis-open.org/issues/browse/TOSCA-150 (Work towards a co
 mmon syntax for Requirement definitions)\n*** https://tools.
 oasis-open.org/issues/browse/TOSCA-151 (Resolve spec. behavi
 or if name collisions occur on named Requirements )\n*** htt
 ps://tools.oasis-open.org/issues/browse/TOSCA-152 (Extend Re
 quirement grammar to support &quot\;Optional/Best Can&quot\;
  Capability Type matching)\n*** https://tools.oasis-open.org
 /issues/browse/TOSCA-153 (Define grammar and usage of Servic
 e Template keyname)\n*** https://tools.oasis-open.org/issues
 /browse/TOSCA-154(Decide how security/access control work wi
 th Nodes\, update grammar\, etc.)\n*** https://tools.oasis-o
 pen.org/issues/browse/TOSCA-155 (How do we provide constrain
 ts on properties declared as simple YAML lists)\n*** https:/
 /tools.oasis-open.org/issues/browse/TOSCA-156 (Are there IPv
 6 considerations (e.g.\, new properties) for tosca.capabilit
 ies.Endpoint)\n*** https://tools.oasis-open.org/issues/brows
 e/TOSCA-157 (Can/how do we make a property defn. &quot\;fina
 l&quot\; or &quot\;read-only&quot\;)\n*** https://tools.oasi
 s-open.org/issues/browse/TOSCA-158 (Provide prose describgin
 g how Feature matching is done by orchestrators)\n*** https:
 //tools.oasis-open.org/issues/browse/TOSCA-159 (Describe how
  not all interfaces need to supply scripts (artifacts)\, it 
 is a no-op behavior)\n*** https://tools.oasis-open.org/issue
 s/browse/TOSCA-160 (Need examples of using the &quot\;tosca.
 interfaces.relationship.Configure&quot\; interface)\n*** htt
 ps://tools.oasis-open.org/issues/browse/TOSCA-161 (Need exam
 ples of using the built-in feature (Capability) and dependen
 cy (Requirement) of tosca.nodes.Root)\n*** https://tools.oas
 is-open.org/issues/browse/TOSCA-162 (Provide recognized valu
 es fo tosca.nodes.compute properties: os_arch)\n*** https://
 tools.oasis-open.org/issues/browse/TOSCA-163(Provide recogni
 zed values fo tosca.nodes.BlockStorage: store_fs_type)\n*** 
 https://tools.oasis-open.org/issues/browse/TOSCA-164 (Do we 
 need a restart lifecycle operation for nodes?)\n*** https://
 tools.oasis-open.org/issues/browse/TOSCA-165https://tools.oa
 sis-open.org/issues/browse/TOSCA-165 (New use case / example
 : Selection/Replacement of web server type)\n*** https://too
 ls.oasis-open.org/issues/browse/TOSCA-166 (New use case / ex
 ample: Web Server with (one or more) runtimes environments)\
 n*** https://tools.oasis-open.org/issues/browse/TOSCA-169 (R
 esolve text and grammar for the &quot\;get_ref_property&quot
 \; function)\n*** https://tools.oasis-open.org/issues/browse
 /TOSCA-170 (Explicit textual mention\, and grammar support\,
  for adding (extending) node operations) \n\nCSD03-related i
 ssues (The below was previously introduced to the TC. Any qu
 estions\, suggestions\, or requests to discuss further?)\n\n
 *** https://tools.oasis-open.org/issues/browse/TOSCA-167 (Ne
 w use case / example: Show abstract substitution of Compute 
 node OS...) \n*** https://tools.oasis-open.org/issues/browse
 /TOSCA-168 (New use case / example: Show how substitution of
  IaaS can be accomplished) \n\n** https://tools.oasis-open.o
 rg/issues/browse/TOSCA-126 (Specifying connectivity to endpo
 ints hosted outside a Service Template)\n** https://tools.oa
 sis-open.org/issues/browse/TOSCA-127 (Conventions for provis
 ioning network connectivity for Service Templates)\n** https
 ://tools.oasis-open.org/issues/browse/TOSCA-114(Composite Ca
 pabilities and Requirements)\n\n** https://tools.oasis-open.
 org/issues/browse/TOSCA-12 (Basic Node Types) -- also relate
 d is https://tools.oasis-open.org/issues/browse/TOSCA-11 (Li
 fecycle Operations)  -- Simple Profile\, essentially\n\nTOSC
 A v1.0 \n* https://tools.oasis-open.org/issues/browse/TOSCA-
 171 (Various v1.0 spec bugs)\n\nREMINDER: While a general ap
 proach can be decided by motion\, specific proposals and con
 tributions need to be JIRA issue\nGroup: OASIS Topology and 
 Orchestration Specification for Cloud Applications (TOSCA) T
 C\nCreator: Mr. Paul Lipton
URL:https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=35873
UID:https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=35873
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT00H15M00S
END:VALARM
END:VEVENT
END:VCALENDAR


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]