[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, 20 November 2014, 12:00pm to 01:30pm EST 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 OASIS Youtube TOSCA Playlist: https://www.youtube.com/playlist?list=PLaYKtNo_BitZXdvyNDwBi290IHxdi459v PROPOSALS AND ISSUES: This meeting counts towards voter eligibility. Agenda Welcome / Roll Interoperability Subcommittee Report Technical Marketing & Education Ad Hoc (lead: Karsten Beins) Ad Hoc on Network Features (lead: Avi Vachnis) Ad Hoc on Container Support, e.g., Docker (lead: Hemal Surti) Ad Hoc on Monitoring (formation)
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) TOSCA v1.1 Simple Profile and YAML Language Rendering (can optionally be conducted in conjunction with review of candidate issues for closure) 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) Newly-Introduced Issues -- Brief Overview for TC and Discussion 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_35887.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:20141120T042044Z DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20141120T120000 DTEND;VALUE=DATE-TIME;TZID=America/New_York:20141120T133000 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:20141120T042044Z 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 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 "\;Record My Attendance"\;. 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 "\;cheatsheet"\; 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 30: https://www.oasis-open. org/committees/document.php?document_id=54444&wg_abbrev=tosc a\n** Thanks to Lowell Higley for scribing \n* Informal co-c hair remarks\n** TOSCA v1.0 CSD02 Errata https://www.oasis-o pen.org/apps/org/workgroup/tosca/email/archives/201410/msg00 074.html\n** Also\, please welcome new TC members Mr. Ran Zi v from GigaSpaces Technologies\, Mr. Li Xu of Neusoft\, Mr. Nati Shalom from GigaSpaces Technologies\, Ms. chunxiu jia f rom Huawei\, Nikunj Nemani from VMware\, Wan Anfeng from Hua wei\, and Radek Pospisil from Hewlett-Packard \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-11-10: https://www.oasis-open.org/apps/org/workgroup/tosca-interop /email/archives/201411/msg00000.html\n \n\nTechnical Marketi ng & 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: S ubmit organization/company videos by uploading them to the O ASIS TOSCA TC Documents section (Working Drafts folder) \n** All TC approved videos at: https://www.youtube.com/playlist ?list=PLaYKtNo_BitZXdvyNDwBi290IHxdi459v\n\nAd Hoc on Networ k Features (lead: Avi Vachnis)\n* https://www.oasis-open.org /apps/org/workgroup/tosca/email/archives/201407/msg00000.htm l (open to all TC members\, of course) \n* https://tools.oas is-open.org/issues/browse/TOSCA-173 - This issue related to general group activities. \n\nAd Hoc on Container Support\, e.g.\, Docker (lead: Hemal Surti) \n* Hemal is leading work on container white paper \n* https://tools.oasis-open.org/i ssues/browse/TOSCA-174 - This issue related to group activit ies\n\nAd Hoc on Monitoring (formation) \n* Call for candida tes (current self-nominations: Chip Holden & Tomer Shtilman) \n* Statements (if more than 2 candidates)\n* Motion to appr ove \n\n \n\nReview and Consideration of Issues Nominated fo r Closure by Nov. 13th Ad Hoc Meeting (can optionally be con ducted in conjunction with review of latest WD of Simple Pro file / YAML doc) \n1. Each issue will be briefly described a long with an equally brief description of the resolution. \n 2. The Co-Chair will ask if any TC member would oppose closu re and note such\n3. At the end of the review\, non-conteste d issues will be motioned for closure. \n​\;4. Conteste d issues will be discussed\, time permitting. \n* https://to ols.oasis-open.org/issues/browse/TOSCA-133 (add material for defining a nested template that implements a node type)\n* https://tools.oasis-open.org/issues/browse/TOSCA-134 (Define TOSCA version type based upon Apache Maven versioning)\n* h ttps://tools.oasis-open.org/issues/browse/TOSCA-139 (Compute node scalability should be specified with a Compute node ca pability)\n* https://tools.oasis-open.org/issues/browse/TOSC A-147 (Define grammar for and examples of using Relationship templates)\n* https://tools.oasis-open.org/issues/browse/TO SCA-149 (Create an independent section to describe a single requirement definition'\;s grammar)\n* https://tools.oasi s-open.org/issues/browse/TOSCA-150 (Work towards a common sy ntax for Requirement definitions)\n* https://tools.oasis-ope n.org/issues/browse/TOSCA-157 (Can/how do we make a property defn. "\;final"\; or "\;read-only"\;)* http s://tools.oasis-open.org/issues/browse/TOSCA-157 (Can/how do we make a property defn. "\;final"\; or "\;read -only"\;)\n* https://tools.oasis-open.org/issues/browse/ TOSCA-159 (Describe how not all interfaces need to supply sc ripts (artifacts)\, it is a no-op behavior)\n* https://tools .oasis-open.org/issues/browse/TOSCA-160 (Need examples of us ing the "\;tosca.interfaces.relationship.Configure"\ ; interface)\n* https://tools.oasis-open.org/issues/browse/T OSCA-164 (Do we need a restart lifecycle operation for nodes ?)\n* https://issues.oasis-open.org/browse/TOSCA-177 (Cardin ality for node template) \n* https://issues.oasis-open.org/b rowse/TOSCA-190 (Fix grammar for "\;Constraints"\; o n a Target node of a requirement)\n* https://issues.oasis-op en.org/browse/TOSCA-203 (Properties defined with type number (should be integer or float based on the valid types)\n\nTO SCA v1.1 Simple Profile and YAML Language Rendering (can opt ionally be conducted in conjunction with review of candidate issues for closure) \nNOTE: As always\, only JIRA issues wi ll be considered by the TC for v1.1 for validation and appro val. 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 questi ons. The below issues at the discretion of the co-chairs and time permitting. \n*** See https://tools.oasis-open.org/iss ues/browse/TOSCA-7 (Alternate encodings Service Templates\, e.g.\, YAML/JSON and Simple Profile)\n* Resources\n** See ht tps://www.oasis-open.org/apps/org/workgroup/tosca/email/arch ives/201407/msg00007.html\n** Current "\;base"\; for v1.1 XML Spec and Simple Profile is the http://docs.oasis-o pen.org/tosca/TOSCA/v1.0/os/ (public)\n** 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 http:/ /docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.0/po sted March 27\, 2014) \n** https://tools.oasis-open.org/issu es/browse/TOSCA-108: Catch-all for All Editorial Suggestions That Do NOT Change Semantics\, e.g.\, spelling\, grammar\, readability (use for all v1.1 documents)\n\nReview and Consi deration of Issues Nominated for Deferal by Nov. 13th Ad Hoc Meeting (can optionally be conducted in conjunction with re view of latest WD of Simple Profile / YAML doc) \n1. Each is sue will be briefly described along with an equally brief de scription of the resolution. \n2. The Co-Chair will ask if a ny TC member would oppose deferal and note such\n3. At the e nd of the review\, non-contested issues will be motioned for deferal \n​\;4. Contested issues will be discussed\, t ime permitting. \n* https://tools.oasis-open.org/issues/brow se/TOSCA-154(Decide how security/access control work with No des\, update grammar\, etc.)\n* https://tools.oasis-open.org /issues/browse/TOSCA-156 (Are there IPv6 considerations (e.g .\, new properties) for tosca.capabilities.Endpoint)\n* http s://tools.oasis-open.org/issues/browse/TOSCA-158 (Provide pr ose describging how Feature matching is done by orchestrator s)* https://tools.oasis-open.org/issues/browse/TOSCA-160 (Ne ed examples of using the "\;tosca.interfaces.relationshi p.Configure"\; interface)\n* https://tools.oasis-open.or g/issues/browse/TOSCA-161 (Need examples of using the built- in feature (Capability) and dependency (Requirement) of tosc a.nodes.Root - see TOSCA-181)\n* https://tools.oasis-open.or g/issues/browse/TOSCA-162 (Provide recognized values fo tosc a.nodes.compute properties: os_arch)\n* https://tools.oasis- open.org/issues/browse/TOSCA-163(Provide recognized values f o tosca.nodes.BlockStorage: store_fs_type)\n* https://tools. oasis-open.org/issues/browse/TOSCA-165https://tools.oasis-op en.org/issues/browse/TOSCA-165 (New use case / example: Sele ction/Replacement of web server type)\n* https://tools.oasis -open.org/issues/browse/TOSCA-166 (New use case / example: W eb Server with (one or more) runtimes environments)\n* https ://tools.oasis-open.org/issues/browse/TOSCA-166 (New use cas e / example: Web Server with (one or more) runtimes environm ents)\n* https://tools.oasis-open.org/issues/browse/TOSCA-16 6 (New use case / example: Web Server with (one or more) run times environments)\n* https://tools.oasis-open.org/issues/b rowse/TOSCA-167 (New use case / example: Show abstract subst itution of Compute node OS...) \n* https://tools.oasis-open. org/issues/browse/TOSCA-168 (New use case / example: Show ho w substitution of IaaS can be accomplished) \n* https://issu es.oasis-open.org/browse/TOSCA-176 (Add connectivity ability to Compute) \n* https://issues.oasis-open.org/browse/TOSCA- 179 (Add "\;timeout"\; and "\;retry"\; keyna mes to an operation)\n* https://issues.oasis-open.org/browse /TOSCA-201 (Harmonize Properties and Capabilities in Node Ty pes)\n \n\nNewly-Introduced Issues -- Brief Overview for TC and Discussion\n* https://issues.oasis-open.org/browse/TOSCA -193 (Need to support "\;implements"\; keyword and a dd to grammar) \n* https://issues.oasis-open.org/browse/TOSC A-194 (Nested Service Templates should be able to define add itional operations)\n* https://issues.oasis-open.org/browse/ TOSCA-195 (Add new normative Runtime capability in the TOSCA spec)\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=35887 UID:https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=35887 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]