Modified: NEW! TOSCA TC Regular Meeting

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:20141030T025634Z
DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20141030T120000
DTEND;VALUE=DATE-TIME;TZID=America/New_York:20141030T133000
SEQUENCE:7887
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:20141030T025634Z
ORGANIZER:
DESCRIPTION:IMPORTANT: Please examine this entire event description for 
 a handy list of resources\, responsibilities\, and more!\n\n
 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\nDue to prankster calls\, this meeting will use th
 e phone bridge and web conferencing tool (also the new chatr
 oom URL) specified by the co-chairs privately to all TC memb
 ers. Please contact the co-chairs from your OASIS registered
  email address if you have a problem. \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 responsi
 ble to log their attendance on this Kavi calendar entry. Whe
 n you join the meeting\, use this page to record your attend
 ance by clicking &quot\;Record My Attendance&quot\;. If you 
 are not on the internet\, you can request the chair to recor
 d your attendance on your behalf.\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 aske
 d to take their turn at scribing a meeting. You are encourag
 ed to volunteer\, and the co-chairs make this easy by provid
 ing a &quot\;cheatsheet&quot\; to make the task easy. Otherw
 ise\, when your name is called by the co-chair\, please take
  your turn. You will use the chat room for the initial scrib
 ing.\n\nT R A C K   Y O U R   V O T I N G   R I G H T S\nPar
 ticipants are responsible for the state of their voting righ
 ts. The co-chairs will endeavor to update the roster at http
 ://www.oasis-open.org/apps/org/workgroup/tosca/members/roste
 r.php before meetings. Except for leaves of absence\, the ge
 neral rule is that a Voting Member who is absent from two co
 nsecutive 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 at
 tended. (see the TC Process section 2.4.4 for more details).
 \n\n \n\nO T H E R   R E S O U R C E S \n\nTOSCA TC PAGE: ht
 tp://www.oasis-open.org/apps/org/workgroup/tosca/index.php\n
 \nTOSCA JIRA Project (all proposals and issues): http://tool
 s.oasis-open.org/issues/browse/TOSCA\n\nOASIS Youtube TOSCA 
 Playlist: https://www.youtube.com/playlist?list=PLaYKtNo_Bit
 ZXdvyNDwBi290IHxdi459v\n\nPROPOSALS AND ISSUES:\nTC standing
  rules for JIRA mandate that all technical and deliverable p
 roposals and issues be in the form of JIRA issues and will o
 nly be voted upon after 1 week. Issues can be discussed at a
 ny time. For details\, see the approved proposal at: http://
 www.oasis-open.org/apps/org/workgroup/tosca/email/archives/2
 01112/msg00030.html\n\nAgenda: Welcome / Roll\nCo-chair appo
 ints a scribe\nReview/approve draft proposed agenda\nReview/
 approve draft minutes\n* October 23: https://www.oasis-open.
 org/committees/document.php?document_id=54369&wg_abbrev=tosc
 a\n** Thanks to Luc Boutier for scribing \n* Informal co-cha
 ir remarks\n** November 13th: Half day ad hoc meeting to res
 olve issues for CSD02 candidate for TC review and considerat
 ion (see event https://www.oasis-open.org/apps/org/workgroup
 /tosca/event.php?event_id=38562) \nTOSCA v1.0 CSD02 Errata h
 ttps://www.oasis-open.org/apps/org/workgroup/tosca/email/arc
 hives/201410/msg00074.html\n** 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\, W
 an Anfeng from Huawei\, and Radek Pospisil from Hewlett-Pack
 ard \n*** New members: expect a delay\, but you will be adde
 d to this list within a couple weeks of joining of the TC\n\
 nInteroperability Subcommittee Report\n* Status and updates 
 from co-chairs (Matt Rutkowski and Richard Probst) \n** Minu
 tes of 2014-10-27: https://www.oasis-open.org/apps/org/workg
 roup/tosca-interop/email/archives/201410/msg00004.html\n \n\
 nTechnical Marketing & Education Ad Hoc (lead: Karsten Beins
 )\n* https://tools.oasis-open.org/issues/browse/TOSCA-131 - 
 This issue related to all such activities \n** INVITATION TO
  ALL TC MEMBERS: Submit organization/company videos by uploa
 ding them to the OASIS TOSCA TC Documents section (Working D
 rafts folder) \n** All TC approved videos at: https://www.yo
 utube.com/playlist?list=PLaYKtNo_BitZXdvyNDwBi290IHxdi459v\n
 \nAd Hoc on Network Features (lead: Avi Vachnis)\n* https://
 www.oasis-open.org/apps/org/workgroup/tosca/email/archives/2
 01407/msg00000.html (open to all TC members\, of course) \n*
  https://tools.oasis-open.org/issues/browse/TOSCA-173 - This
  issue related to general group activities.  \n\nAd Hoc on C
 ontainer Support\, e.g.\, Docker (lead: Hemal Surti) \n* htt
 ps://tools.oasis-open.org/issues/browse/TOSCA-174 - This iss
 ue related to group activities\n\nTOSCA v1.1\nNOTE: As alway
 s\, only JIRA issues will be considered by the TC for v1.1 f
 or validation and approval. Note that any TC member can crea
 te 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 discreti
 on of the co-chairs and time permitting. \n*** See https://t
 ools.oasis-open.org/issues/browse/TOSCA-7 (Alternate encodin
 gs Service Templates\, e.g.\, YAML/JSON and Simple Profile)\
 n* Resources\n** See https://www.oasis-open.org/apps/org/wor
 kgroup/tosca/email/archives/201407/msg00007.html\n** Current
  &quot\;base&quot\; for v1.1 XML Spec and Simple Profile is 
 the http://docs.oasis-open.org/tosca/TOSCA/v1.0/os/ (public)
 \n** Note however that much work for v1.1 is being done firs
 t on the YAML rendering and Simple Profile Document (last TC
  approved CSD is http://docs.oasis-open.org/tosca/TOSCA-Simp
 le-Profile-YAML/v1.0/posted March 27\, 2014) \n** https://to
 ols.oasis-open.org/issues/browse/TOSCA-108: Catch-all for Al
 l Editorial Suggestions That Do NOT Change Semantics\, e.g.\
 , spelling\, grammar\, readability (use for all v1.1 documen
 ts)\n\nNewly-Introduced Issues -- Brief Overview for TC and 
 Discussion\n* https://issues.oasis-open.org/browse/TOSCA-193
  (Need to support &quot\;implements&quot\; keyword and add t
 o grammar) \n* https://issues.oasis-open.org/browse/TOSCA-19
 4 (Nested Service Templates should be able to define additio
 nal operations)\n* https://issues.oasis-open.org/browse/TOSC
 A-195 (Add new normative Runtime capability in the TOSCA spe
 c)\n\n \n\nThe below was previously introduced to the TC. An
 y questions\, suggestions\, or requests to discuss further?\
 nSuggested activity (time permitting): The TC (with input fr
 om the Simple Profile Ad Hoc members) is asked to briefly co
 nsider scan the list to see if it is possible to close any o
 f the below issues.  \n* https://tools.oasis-open.org/issues
 /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 (add m
 aterial for defining a nested template that implements a nod
 e type)\n* https://tools.oasis-open.org/issues/browse/TOSCA-
 134 (Define TOSCA version type based upon Apache Maven versi
 oning)\n* https://tools.oasis-open.org/issues/browse/TOSCA-1
 35 (Define/reference a Regex language (or subset) we wish to
  support for constraints)\n* https://tools.oasis-open.org/is
 sues/browse/TOSCA-136 (Rules to Ensure Uniqueness of Require
 ment and Capability Names)  \n* https://tools.oasis-open.org
 /issues/browse/TOSCA-137 (Need to address &quot\;optional&qu
 ot\; and &quot\;best can&quot\; on node requirements)  \n* h
 ttps://tools.oasis-open.org/issues/browse/TOSCA-138 (Define 
 a Network topology for L2 Networks\, etc.)\n* https://tools.
 oasis-open.org/issues/browse/TOSCA-139 (Compute node scalabi
 lity should be specified with a Compute node capability)\n* 
 https://tools.oasis-open.org/issues/browse/TOSCA-140 (Constr
 aining the capabilities of multiple node templates)\n* https
 ://tools.oasis-open.org/issues/browse/TOSCA-141 (Specifying 
 Environment Constraints for Node Templates) \n* https://tool
 s.oasis-open.org/issues/browse/TOSCA-142 (Define normative A
 rtifact 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(Upda
 te Ch 6\, Example 5\, &quot\;Template for deploying a two-ti
 er application servers.on two&quot\;)\n* https://tools.oasis
 -open.org/issues/browse/TOSCA-145 (Update Ch 7\, Example 6\,
  &quot\;Template for deploying a two-tier application on two
  servers.&quot\;)\n* https://tools.oasis-open.org/issues/bro
 wse/TOSCA-146 (Define a grammar for each property function a
 nd provide examples)\n* https://tools.oasis-open.org/issues/
 browse/TOSCA-147 (Define grammar for and examples of using R
 elationship templates)\n* https://tools.oasis-open.org/issue
 s/browse/TOSCA-148 (Need a means to express cardinality on r
 elationships)\n* https://tools.oasis-open.org/issues/browse/
 TOSCA-149 (Create an independent section to describe a singl
 e requirement definition&#39\;s grammar)\n* https://tools.oa
 sis-open.org/issues/browse/TOSCA-150 (Work towards a common 
 syntax for Requirement definitions)\n* https://tools.oasis-o
 pen.org/issues/browse/TOSCA-151 (Resolve spec. behavior if n
 ame collisions occur on named Requirements )\n* https://tool
 s.oasis-open.org/issues/browse/TOSCA-152 (Extend Requirement
  grammar to support &quot\;Optional/Best Can&quot\; Capabili
 ty Type matching)\n* https://tools.oasis-open.org/issues/bro
 wse/TOSCA-153 (Define grammar and usage of Service Template 
 keyname)\n* https://tools.oasis-open.org/issues/browse/TOSCA
 -154(Decide how security/access control work with Nodes\, up
 date grammar\, etc.)\n* https://tools.oasis-open.org/issues/
 browse/TOSCA-155 (How do we provide constraints on propertie
 s declared as simple YAML lists)\n* https://tools.oasis-open
 .org/issues/browse/TOSCA-156 (Are there IPv6 considerations 
 (e.g.\, new properties) for tosca.capabilities.Endpoint)\n* 
 https://tools.oasis-open.org/issues/browse/TOSCA-157 (Can/ho
 w do we make a property defn. &quot\;final&quot\; or &quot\;
 read-only&quot\;)\n* https://tools.oasis-open.org/issues/bro
 wse/TOSCA-158 (Provide prose describging how Feature matchin
 g is done by orchestrators)\n* https://tools.oasis-open.org/
 issues/browse/TOSCA-159 (Describe how not all interfaces nee
 d to supply scripts (artifacts)\, it is a no-op behavior)\n*
  https://tools.oasis-open.org/issues/browse/TOSCA-160 (Need 
 examples of using the &quot\;tosca.interfaces.relationship.C
 onfigure&quot\; interface)\n* https://tools.oasis-open.org/i
 ssues/browse/TOSCA-161 (Need examples of using the built-in 
 feature (Capability) and dependency (Requirement) of tosca.n
 odes.Root - see TOSCA-181)\n* https://tools.oasis-open.org/i
 ssues/browse/TOSCA-162 (Provide recognized values fo tosca.n
 odes.compute properties: os_arch)\n* https://tools.oasis-ope
 n.org/issues/browse/TOSCA-163(Provide recognized values fo t
 osca.nodes.BlockStorage: store_fs_type)\n* https://tools.oas
 is-open.org/issues/browse/TOSCA-164 (Do we need a restart li
 fecycle operation for nodes?)\n* https://tools.oasis-open.or
 g/issues/browse/TOSCA-165https://tools.oasis-open.org/issues
 /browse/TOSCA-165 (New use case / example: Selection/Replace
 ment of web server type)\n* https://tools.oasis-open.org/iss
 ues/browse/TOSCA-166 (New use case / example: Web Server wit
 h (one or more) runtimes environments)\n* https://tools.oasi
 s-open.org/issues/browse/TOSCA-169 (Resolve text and grammar
  for the &quot\;get_ref_property&quot\; function)\n* https:/
 /tools.oasis-open.org/issues/browse/TOSCA-170 (Explicit text
 ual mention\, and grammar support\, for adding (extending) n
 ode operations) \n* https://issues.oasis-open.org/browse/TOS
 CA-176 (Add connectivity ability to Compute) \n* https://iss
 ues.oasis-open.org/browse/TOSCA-177 (Cardinality for node te
 mplate) \n* https://issues.oasis-open.org/browse/TOSCA-178 (
 Define how an operation can expose outputs)\n* https://issue
 s.oasis-open.org/browse/TOSCA-179 (Add &quot\;timeout&quot\;
  and &quot\;retry&quot\; keynames to an operation)\n* https:
 //issues.oasis-open.org/browse/TOSCA-180 (Support of secured
  repositories for artifacts)\n* https://issues.oasis-open.or
 g/browse/TOSCA-181 (Dependency requirement type should match
  any target node - see TOSCA-161)\n* https://issues.oasis-op
 en.org/browse/TOSCA-186 (Model Composition) - Oct. 9th\n* ht
 tps://issues.oasis-open.org/browse/TOSCA-187 (Using TOSCA mo
 dels to describe NFV forward graph) - Oct. 9th\n* https://is
 sues.oasis-open.org/browse/TOSCA-188 (Requirements section s
 hould be turned to a map instead of list)\n* https://issues.
 oasis-open.org/browse/TOSCA-189 (Application Monitoring - Pr
 oposal)\n* https://issues.oasis-open.org/browse/TOSCA-190 (F
 ix grammar for &quot\;Constraints&quot\; on a Target node of
  a requirement)\n* https://issues.oasis-open.org/browse/TOSC
 A-191 (&ldquo\;augmentation&rdquo\; behavior after relations
 hip is selected in a requirement)\n* https://issues.oasis-op
 en.org/browse/TOSCA-192 (how to differentiate get_propertiy 
 and get_attribute)\n\n** Root issues for all Simple Profile 
 work\, essentially: https://tools.oasis-open.org/issues/brow
 se/TOSCA-12 (Basic Node Types) -- also related is https://to
 ols.oasis-open.org/issues/browse/TOSCA-11 (Lifecycle Operati
 ons)  \n\nREMINDER: While a general approach can be decided 
 by motion\, specific proposals and contributions need to be 
 JIRA issue\nGroup: OASIS Topology and Orchestration Specific
 ation for Cloud Applications (TOSCA) TC\nCreator: Mr. Paul L
 ipton
URL:https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=35884
UID:https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=35884
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT00H15M00S
END:VALARM
END:VEVENT
END:VCALENDAR