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
Just some cleanup of issue lists (repeats, etc.).
-- Mr. Paul Lipton
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
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. Please contact the co-chairs from your OASIS registered email address if you have a problem. 

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. You are encouraged to volunteer, and the co-chairs make this easy by providing a "cheatsheet" to make the task easy. Otherwise, when your name is called by the co-chair, please take your turn. You will use the chat room for the initial scribing.

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

OASIS Youtube TOSCA Playlist: https://www.youtube.com/playlist?list=PLaYKtNo_BitZXdvyNDwBi290IHxdi459v

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
* October 30: https://www.oasis-open.org/committees/document.php?document_id=54444&wg_abbrev=tosca
** Thanks to Lowell Higley for scribing 
* Informal co-chair remarks and notables 
** Very successful half-day November 13th ad hoc meeting. Minutes can be found here
** TOSCA v1.0 CSD02 Errata published 
** 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, Wan Anfeng from Huawei, and Radek Pospisil from Hewlett-Packard 
*** 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-11-10: https://www.oasis-open.org/apps/org/workgroup/tosca-interop/email/archives/201411/msg00000.html
 

Technical Marketing & Education Ad Hoc (lead: Karsten Beins)
TOSCA-131 - This issue related to all such activities 
** INVITATION TO ALL TC MEMBERS: Submit organization/company videos by uploading them to the OASIS TOSCA TC Documents section (Working Drafts folder) 
** All TC approved videos at: OASIS TOSCA YouTube Playlist

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.  

Ad Hoc on Container Support, e.g., Docker (lead: Hemal Surti) 
* Hemal is leading work on container white paper 
TOSCA-174 - This issue related to group activities

Ad Hoc on Monitoring (formation) 
* Call for candidates (current self-nominations: Chip Holden & Tomer Shtilman)
* Statements (if more than 2 candidates)
* Motion to approve 

 

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) 
1. Each issue will be briefly described along with an equally brief description of the resolution. 
2. The Co-Chair will ask if any TC member would oppose closure and note such
3. At the end of the review, non-contested issues will be motioned for closure. 
​4. Contested issues will be discussed, time permitting. 
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-139 (Compute node scalability should be specified with a Compute node capability)
TOSCA-147 (Define grammar for and examples of using Relationship templates)
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-157 (Can/how do we make a property defn. "final" or "read-only")* TOSCA-157 (Can/how do we make a property defn. "final" or "read-only")
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-164 (Do we need a restart lifecycle operation for nodes?)
TOSCA-177 (Cardinality for node template) 
TOSCA-190 (Fix grammar for "Constraints" on a Target node of a requirement)
* TOSCA-203 (Properties defined with type number (should be integer or float based on the valid types)

TOSCA v1.1 Simple Profile and YAML Language Rendering (can optionally be conducted in conjunction with review of candidate issues for closure) 
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 and Simple Profile)
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)

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) 
1. Each issue will be briefly described along with an equally brief description of the resolution. 
2. The Co-Chair will ask if any TC member would oppose deferal and note such
3. At the end of the review, non-contested issues will be motioned for deferal 
​4. Contested issues will be discussed, time permitting. 
TOSCA-154 (Decide how security/access control work with Nodes, update grammar, etc.)
TOSCA-156 (Are there IPv6 considerations (e.g., new properties) for tosca.capabilities.Endpoint)
TOSCA-158 (Provide prose describging how Feature matching is done by orchestrators)
TOSCA-161 (Need examples of using the built-in feature (Capability) and dependency (Requirement) of tosca.nodes.Root - see TOSCA-181)
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-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-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-176 (Add connectivity ability to Compute) 
TOSCA-179 (Add "timeout" and "retry" keynames to an operation)
* TOSCA-201 (Harmonize Properties and Capabilities in Node Types)
 

Newly-Introduced Issues -- Brief Overview for TC and Discussion
TOSCA-193 (Need to support "implements" keyword and add to grammar) 
TOSCA-194 (Nested Service Templates should be able to define additional operations)
TOSCA-195 (Add new normative Runtime capability in the TOSCA spec)

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_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:20141120T051129Z
DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20141120T120000
DTEND;VALUE=DATE-TIME;TZID=America/New_York:20141120T133000
SEQUENCE:7889
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:20141120T051129Z
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 &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 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 and notables \n** Very successful half-day Nove
 mber 13th ad hoc meeting. Minutes can be found https://www.o
 asis-open.org/apps/org/workgroup/tosca/email/archives/201411
 /msg00158.html. \n** TOSCA v1.0 CSD02 Errata https://www.oas
 is-open.org/apps/org/workgroup/tosca/email/archives/201410/m
 sg00074.html\n** Also\, please welcome new TC members Mr. Ra
 n Ziv from GigaSpaces Technologies\, Mr. Li Xu of Neusoft\, 
 Mr. Nati Shalom from GigaSpaces Technologies\, Ms. chunxiu j
 ia from Huawei\, Nikunj Nemani from VMware\, Wan Anfeng from
  Huawei\, and Radek Pospisil from Hewlett-Packard \n*** New 
 members: expect a delay\, but you will be added to this list
  within a couple weeks of joining of the TC\n\nInteroperabil
 ity Subcommittee Report\n* Status and updates from co-chairs
  (Matt Rutkowski and Richard Probst) \n** Minutes of 2014-11
 -10: https://www.oasis-open.org/apps/org/workgroup/tosca-int
 erop/email/archives/201411/msg00000.html\n \n\nTechnical Mar
 keting & 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** INVITATION TO ALL TC MEMBER
 S: Submit organization/company videos by uploading them to t
 he OASIS TOSCA TC Documents section (Working Drafts folder) 
 \n** All TC approved videos at: https://www.youtube.com/play
 list?list=PLaYKtNo_BitZXdvyNDwBi290IHxdi459v\n\nAd Hoc on Ne
 twork Features (lead: Avi Vachnis)\n* https://www.oasis-open
 .org/apps/org/workgroup/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 activities.  \n\nAd Hoc on Container Suppo
 rt\, e.g.\, Docker (lead: Hemal Surti) \n* Hemal is leading 
 work on container white paper \n* https://tools.oasis-open.o
 rg/issues/browse/TOSCA-174 - This issue related to group act
 ivities\n\nAd Hoc on Monitoring (formation) \n* Call for can
 didates (current self-nominations: Chip Holden & Tomer Shtil
 man)\n* Statements (if more than 2 candidates)\n* Motion to 
 approve \n\n \n\nReview and Consideration of Issues Nominate
 d for Closure by Nov. 13th Ad Hoc Meeting (can optionally be
  conducted in conjunction with review of latest WD of Simple
  Profile / YAML doc) \n1. Each issue will be briefly describ
 ed along with an equally brief description of the resolution
 . \n2. The Co-Chair will ask if any TC member would oppose c
 losure and note such\n3. At the end of the review\, non-cont
 ested issues will be motioned for closure. \n&#8203\;4. Cont
 ested issues will be discussed\, time permitting. \n* https:
 //tools.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 (De
 fine TOSCA version type based upon Apache Maven versioning)\
 n* https://tools.oasis-open.org/issues/browse/TOSCA-139 (Com
 pute node scalability should be specified with a Compute nod
 e capability)\n* https://tools.oasis-open.org/issues/browse/
 TOSCA-147 (Define grammar for and examples of using Relation
 ship templates)\n* https://tools.oasis-open.org/issues/brows
 e/TOSCA-149 (Create an independent section to describe a sin
 gle requirement definition&#39\;s grammar)\n* https://tools.
 oasis-open.org/issues/browse/TOSCA-150 (Work towards a commo
 n syntax for Requirement definitions)\n* https://tools.oasis
 -open.org/issues/browse/TOSCA-157 (Can/how do we make a prop
 erty defn. &quot\;final&quot\; or &quot\;read-only&quot\;)* 
 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-159 (Describe how not all interfaces need to suppl
 y scripts (artifacts)\, it is a no-op behavior)\n* https://t
 ools.oasis-open.org/issues/browse/TOSCA-160 (Need examples o
 f using the &quot\;tosca.interfaces.relationship.Configure&q
 uot\; interface)\n* https://tools.oasis-open.org/issues/brow
 se/TOSCA-164 (Do we need a restart lifecycle operation for n
 odes?)\n* https://issues.oasis-open.org/browse/TOSCA-177 (Ca
 rdinality for node template) \n* https://issues.oasis-open.o
 rg/browse/TOSCA-190 (Fix grammar for &quot\;Constraints&quot
 \; on a Target node of a requirement)\n* https://issues.oasi
 s-open.org/browse/TOSCA-203 (Properties defined with type nu
 mber (should be integer or float based on the valid types)\n
 \nTOSCA v1.1 Simple Profile and YAML Language Rendering (can
  optionally be conducted in conjunction with review of candi
 date issues for closure) \nNOTE: As always\, only JIRA issue
 s will be considered by the TC for v1.1 for validation and a
 pproval. Note that any TC member can create or comment on a 
 JIRA issue\, upload related documents to Kavi (the OASIS web
 site)\, etc. Please contact the co-chairs if you have any qu
 estions. The below issues at the discretion of the co-chairs
  and time permitting. \n*** See https://tools.oasis-open.org
 /issues/browse/TOSCA-7 (Alternate encodings Service Template
 s\, e.g.\, YAML/JSON and Simple Profile)\n* Resources\n** Se
 e https://www.oasis-open.org/apps/org/workgroup/tosca/email/
 archives/201407/msg00007.html\n** Current &quot\;base&quot\;
  for v1.1 XML Spec and Simple Profile is the http://docs.oas
 is-open.org/tosca/TOSCA/v1.0/os/ (public)\n** Note however t
 hat much work for v1.1 is being done first on the YAML rende
 ring and Simple Profile Document (last TC approved CSD is ht
 tp://docs.oasis-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 Suggest
 ions That Do NOT Change Semantics\, e.g.\, spelling\, gramma
 r\, readability (use for all v1.1 documents)\n\nReview and C
 onsideration of Issues Nominated for Deferal by Nov. 13th Ad
  Hoc Meeting (can optionally be conducted in conjunction wit
 h review of latest WD of Simple Profile / YAML doc) \n1. Eac
 h issue will be briefly described along with an equally brie
 f description of the resolution. \n2. The Co-Chair will ask 
 if any TC member would oppose deferal and note such\n3. At t
 he end of the review\, non-contested issues will be motioned
  for deferal \n&#8203\;4. Contested issues will be discussed
 \, time permitting. \n* https://tools.oasis-open.org/issues/
 browse/TOSCA-154(Decide how security/access control work wit
 h Nodes\, 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* 
 https://tools.oasis-open.org/issues/browse/TOSCA-158 (Provid
 e prose describging how Feature matching is done by orchestr
 ators)\n* https://tools.oasis-open.org/issues/browse/TOSCA-1
 61 (Need examples of using the built-in feature (Capability)
  and dependency (Requirement) of tosca.nodes.Root - see TOSC
 A-181)\n* https://tools.oasis-open.org/issues/browse/TOSCA-1
 62 (Provide recognized values fo tosca.nodes.compute propert
 ies: os_arch)\n* https://tools.oasis-open.org/issues/browse/
 TOSCA-163(Provide recognized values fo tosca.nodes.BlockStor
 age: store_fs_type)\n* https://tools.oasis-open.org/issues/b
 rowse/TOSCA-165https://tools.oasis-open.org/issues/browse/TO
 SCA-165 (New use case / example: Selection/Replacement of we
 b server type)\n* https://tools.oasis-open.org/issues/browse
 /TOSCA-166 (New use case / example: Web Server with (one or 
 more) runtimes environments)\n* https://tools.oasis-open.org
 /issues/browse/TOSCA-167 (New use case / example: Show abstr
 act substitution of Compute node OS...) \n* https://tools.oa
 sis-open.org/issues/browse/TOSCA-168 (New use case / example
 : Show how substitution of IaaS can be accomplished) \n* htt
 ps://issues.oasis-open.org/browse/TOSCA-176 (Add connectivit
 y ability to Compute) \n* https://issues.oasis-open.org/brow
 se/TOSCA-179 (Add &quot\;timeout&quot\; and &quot\;retry&quo
 t\; keynames to an operation)\n* https://issues.oasis-open.o
 rg/browse/TOSCA-201 (Harmonize Properties and Capabilities i
 n Node Types)\n \n\nNewly-Introduced Issues -- Brief Overvie
 w for TC and Discussion\n* https://issues.oasis-open.org/bro
 wse/TOSCA-193 (Need to support &quot\;implements&quot\; keyw
 ord and add to grammar) \n* https://issues.oasis-open.org/br
 owse/TOSCA-194 (Nested Service Templates should be able to d
 efine additional operations)\n* https://issues.oasis-open.or
 g/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 ne
 ed to be JIRA issue\nGroup: OASIS Topology and Orchestration
  Specification for Cloud Applications (TOSCA) TC\nCreator: M
 r. Paul Lipton
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]