[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Modified NEW! TOSCA TC Regular Meeting
|
Event Title: NEW! TOSCA TC Regular Meeting Date: Thursday, 21 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
R E C O R D Y O U R O W N A T T E N D A N C E
Y O U R S C R I B E R E S P O N S I B I L I T Y
T R A C K Y O U R V O T I N G R I G H T S
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 Interoperability Subcommittee Report
Technical Marketing & Education Ad Hoc (lead: Karsten Beins)
Ad Hoc on Container Support, e.g., Docker (lead: Hemal Surti)
Ad Hoc on Network Features (lead: Avi Vachnis) TOSCA v1.1
Newly-Introduced Issues -- Brief Overview for TC and Discussion
These issues have been recently introduced to the TC
CSD02-related issues (The below was previously introduced to the TC. Any questions, suggestions, or requests to discuss further?) *** TOSCA-147 (Define grammar for and examples of using Relationship templates) 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-126 (Specifying connectivity to endpoints hosted outside a Service Template)
** TOSCA-12 (Basic Node Types) -- also related is TOSCA-11 (Lifecycle Operations) -- Simple Profile, essentially 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. |
Attachment:
ical_35874.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:20140821T033654Z DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20140821T120000 DTEND;VALUE=DATE-TIME;TZID=America/New_York:20140821T133000 SEQUENCE:7882 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:20140821T033654Z 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"\;. 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 "\;Record My Attendance "\;. 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 "\;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'\;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 "\;TOSCA TC Minutes 20 12-MM-DD"\; to "\;Meeting Notes"\; 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 14: https://www.oasis-open.org/committees /document.php?document_id=53913&wg_abbrev=tosca\n** Thanks t o Alessandro Rossini for scribing \n* Informal co-chair rema rks\n** ODCA Forecast 2014 free passes (see https://www.oasi s-open.org/apps/org/workgroup/tosca/email/archives/201407/ms g00041.html)\n** Also\, please welcome new TC members Ton Ng o from IBM. Jim Hunter from CA Technologies\, Vasile Radoaca from Alcatel-Lucent\, Larry Lamers from VMWare\, Kurt Spenc e from CA Technologies\n*** New members: expect a delay\, bu t you will be added to this list within a couple weeks of jo ining of the TC\n\nInteroperability Subcommittee Report\n* S tatus and updates from co-chairs (Matt Rutkowski and Richard Probst) \n** Minutes of 2014-08-11: not posted\n** TC-appro ved https://www.oasis-open.org/committees/document.php?docum ent_id=53479&wg_abbrev=tosca and https://www.oasis-open.org/ committees/document.php?document_id=53430&wg_abbrev=tosca-in terop for ODCA Forecast Conference\n\n \n\nTechnical Market ing & Education Ad Hoc (lead: Karsten Beins) \n* https://to ols.oasis-open.org/issues/browse/TOSCA-131 - This issue rela ted to all such activities \n\n \n\nAd Hoc on Container Supp ort\, e.g.\, Docker (lead: Hemal Surti) \n* https://tools.oa sis-open.org/issues/browse/TOSCA-174 - This issue related to group activities\n\n \n\nAd Hoc on Network Features (lead: Avi Vachnis)\n* https://www.oasis-open.org/apps/org/workgrou p/tosca/email/archives/201407/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 acti vities. \n\nTOSCA v1.1\nNOTE: As always\, only JIRA issues will be considered by the TC for v1.1 for validation and app roval. Note that any TC member can create or comment on a JI RA issue\, upload related documents to Kavi (the OASIS websi te)\, etc. Please contact the co-chairs if you have any ques tions. The below issues at the discretion of the co-chairs a nd time permitting. \n*** See https://tools.oasis-open.org/i ssues/browse/TOSCA-7 (Alternate encodings Service Templates\ , e.g.\, YAML/JSON)\n* Resources\n** See https://www.oasis-o pen.org/apps/org/workgroup/tosca/email/archives/201407/msg00 007.html\n** Current "\;base"\; for v1.1 XML Spec an d Simple Profile is the http://docs.oasis-open.org/tosca/TOS CA/v1.0/os/ (public)\n** Note however that much work for v1. 1 is being done first on the YAML rendering and Simple Profi le Document (last TC approved CSD is http://docs.oasis-open. org/tosca/TOSCA-Simple-Profile-YAML/v1.0/posted March 27\, 2 014) \n** https://tools.oasis-open.org/issues/browse/TOSCA-1 08: Catch-all for All Editorial Suggestions That Do NOT Chan ge Semantics\, e.g.\, spelling\, grammar\, readability (use for all v1.1 documents)\n\n \n\nNewly-Introduced Issues -- B rief Overview for TC and Discussion\n* https://tools.oasis-o pen.org/issues/browse/TOSCA-175 (Support navigation within t he service template) - or was this already discussed? \n* ht tps://issues.oasis-open.org/browse/TOSCA-176 (Add connectivi ty ability to Compute) \n* https://issues.oasis-open.org/bro wse/TOSCA-180 (Support of secured repositories for artifacts )\n* https://issues.oasis-open.org/browse/TOSCA-181 (Depende ncy requirement type should match any target node)\n* https: //issues.oasis-open.org/browse/TOSCA-182 (Document parsing c onventions) \n* https://issues.oasis-open.org/browse/TOSCA-1 83 (Composition across multiple yaml documents)\n* https://i ssues.oasis-open.org/browse/TOSCA-184 (Pushing (vs pulling) inputs to templates) \n* https://issues.oasis-open.org/brows e/TOSCA-185 (Instance model)\n\n \n\nThese issues have been recently introduced to the TC\nNOTE: These should be associa ted with a CSD\, e.g.\, CSD02 or CSD03\n*** https://issues.o asis-open.org/browse/TOSCA-178 (Define how an operation can expose outputs)\n*** https://issues.oasis-open.org/browse/TO SCA-177 (Cardinality for node template)\n*** https://issues. oasis-open.org/browse/TOSCA-179 (Add "\;timeout"\; a nd "\;retry"\; keynames to an operation)\n\n \n\nCSD 02-related issues (The below was previously introduced to th e TC. Any questions\, suggestions\, or requests to discuss f urther?)\nNote: Review issues that are receiving most attent ion in the YAML ad hoc. Any decisions or challenges? \n*** h ttps://tools.oasis-open.org/issues/browse/TOSCA-132(Use &quo t\;set_property"\; methods to "\;push"\; values from template inputs to nodes) \n*** https://tools.oasis-ope n.org/issues/browse/TOSCA-133 (add material for defining a n ested template that implements a node type)\n*** https://too ls.oasis-open.org/issues/browse/TOSCA-134 (Define TOSCA vers ion type based upon Apache Maven versioning)\n*** https://to ols.oasis-open.org/issues/browse/TOSCA-135 (Define/reference a Regex language (or subset) we wish to support for constra ints)\n*** https://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 (Comput e node scalability should be specified with a Compute node c apability)\n*** https://tools.oasis-open.org/issues/browse/T OSCA-140 (Constraining the capabilities of multiple node tem plates)\n*** https://tools.oasis-open.org/issues/browse/TOSC A-141 (Specifying Environment Constraints 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.nod es.Network Node Type)\n*** https://tools.oasis-open.org/issu es/browse/TOSCA-144(Update Ch 6\, Example 5\, "\;Templat e for deploying a two-tier application servers.on two"\; )\n*** https://tools.oasis-open.org/issues/browse/TOSCA-145 (Update Ch 7\, Example 6\, "\;Template for deploying a t wo-tier application on two servers."\;)\n*** https://too ls.oasis-open.org/issues/browse/TOSCA-146 (Define a grammar for each property function and provide examples)\n\n*** http s://tools.oasis-open.org/issues/browse/TOSCA-147 (Define gra mmar for and examples of using Relationship templates)\n*** https://tools.oasis-open.org/issues/browse/TOSCA-148 (Need a means to express cardinality on relationships)\n*** https:/ /tools.oasis-open.org/issues/browse/TOSCA-149 (Create an ind ependent section to describe a single requirement definition '\;s grammar)\n*** https://tools.oasis-open.org/issues/br owse/TOSCA-150 (Work towards a common syntax for Requirement definitions)\n*** https://tools.oasis-open.org/issues/brows e/TOSCA-151 (Resolve spec. behavior if name collisions occur on named Requirements )\n*** https://tools.oasis-open.org/i ssues/browse/TOSCA-152 (Extend Requirement grammar to suppor t "\;Optional/Best Can"\; Capability Type matching)\ n*** https://tools.oasis-open.org/issues/browse/TOSCA-153 (D efine grammar and usage of Service Template keyname)\n*** ht tps://tools.oasis-open.org/issues/browse/TOSCA-154(Decide ho w security/access control work with Nodes\, update grammar\, etc.)\n*** https://tools.oasis-open.org/issues/browse/TOSCA -155 (How do we provide constraints on properties declared a s simple YAML lists)\n*** https://tools.oasis-open.org/issue s/browse/TOSCA-156 (Are there IPv6 considerations (e.g.\, ne w properties) for tosca.capabilities.Endpoint)\n*** https:// tools.oasis-open.org/issues/browse/TOSCA-157 (Can/how do we make a property defn. "\;final"\; or "\;read-onl y"\;)\n*** https://tools.oasis-open.org/issues/browse/TO SCA-158 (Provide prose describging how Feature matching is d one by orchestrators)\n*** https://tools.oasis-open.org/issu es/browse/TOSCA-159 (Describe how not all interfaces need to supply scripts (artifacts)\, it is a no-op behavior)\n*** h ttps://tools.oasis-open.org/issues/browse/TOSCA-160 (Need ex amples of using the "\;tosca.interfaces.relationship.Con figure"\; 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)\n*** https://tools.oasis-open.org/issues/browse/T OSCA-162 (Provide recognized values fo tosca.nodes.compute p roperties: os_arch)\n*** https://tools.oasis-open.org/issues /browse/TOSCA-163(Provide recognized values fo tosca.nodes.B lockStorage: store_fs_type)\n*** https://tools.oasis-open.or g/issues/browse/TOSCA-164 (Do we need a restart lifecycle op eration for nodes?)\n*** https://tools.oasis-open.org/issues /browse/TOSCA-165https://tools.oasis-open.org/issues/browse/ TOSCA-165 (New use case / example: Selection/Replacement of web server type)\n*** https://tools.oasis-open.org/issues/br owse/TOSCA-166 (New use case / example: Web Server with (one or more) runtimes environments)\n*** https://tools.oasis-op en.org/issues/browse/TOSCA-169 (Resolve text and grammar for the "\;get_ref_property"\; function)\n*** https://t ools.oasis-open.org/issues/browse/TOSCA-170 (Explicit textua l mention\, and grammar support\, for adding (extending) nod e operations) \n\nCSD03-related issues (The below was previo usly introduced to the TC. Any questions\, suggestions\, or requests to discuss further?)\n\n*** https://tools.oasis-ope n.org/issues/browse/TOSCA-167 (New use case / example: Show abstract substitution of Compute node OS...) \n*** https://t ools.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.org/issues/browse/TOSCA-126 (Specifying connectivity to endpoints hosted outside a Servi ce Template)\n** https://tools.oasis-open.org/issues/browse/ TOSCA-127 (Conventions for provisioning network connectivity for Service Templates)\n** https://tools.oasis-open.org/iss ues/browse/TOSCA-114(Composite Capabilities and Requirements )\n\n \n\n** https://tools.oasis-open.org/issues/browse/TOSC A-12 (Basic Node Types) -- also related is https://tools.oas is-open.org/issues/browse/TOSCA-11 (Lifecycle Operations) - - Simple Profile\, essentially\n\nREMINDER: While a general approach can be decided by motion\, specific proposals and c ontributions need to be JIRA issue\n\n \nGroup: OASIS Topolo gy and Orchestration Specification for Cloud Applications (T OSCA) TC\nCreator: Mr. Paul Lipton URL:https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=35874 UID:https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=35874 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]