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


Event Title: NEW! TOSCA TC Regular Meeting

Date: Thursday, 23 October 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. 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 9: https://www.oasis-open.org/committees/document.php?document_id=54280&wg_abbrev=tosca
** Thanks to Chip Holden for scribing 
* Informal co-chair remarks
** Also, please welcome new TC members Mr. Li Xu of Neusoft, Mr. Nati Shalom from GigaSpaces Technologies, Ms. chunxiu jia from Huawei, Nikunj Nemani from VMware, Wan Anfeng from Huawei, Radek Pospisil from Hewlett-Packard, and Chris Lauwers (Individual Member)  
*** 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-10-06 & 2014-10=13: short meetings. no minutes recorded. 
 

Technical Marketing & Education Ad Hoc (lead: Karsten Beins)
TOSCA-131 - This issue related to all such activities 
HP Video proposed for OASIS TOSCA playlist (first submitted company/organization video for OASIS YouTube, but others expected and requested!)
** NOTE: 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) 
TOSCA-174 - This issue related to group activities

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

Newly-Introduced Issues -- Brief Overview for TC and Discussion
TOSCA-188 (Requirements section should be turned to a map instead of list)
TOSCA-189 (Application Monitoring - Proposal)
TOSCA-190 (Fix grammar for "Constraints" on a Target node of a requirement)
TOSCA-191 (“augmentation” behavior after relationship is selected in a requirement)
TOSCA-192 (how to differentiate get_propertiy and get_attribute)

 

The below was previously introduced to the TC. Any questions, suggestions, or requests to discuss further?
Suggested activity (time permitting): The TC (with input from the Simple Profile Ad Hoc members) is asked to briefly consider scan the list to see if it is possible to close any of the below issues.  
*** 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-136 (Rules to Ensure Uniqueness of Requirement and Capability Names)  
*** TOSCA-137 (Need to address "optional" and "best can" on node requirements)  
*** 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 - 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-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) 
*** TOSCA-176 (Add connectivity ability to Compute) 
*** TOSCA-177 (Cardinality for node template) 
*** TOSCA-178 (Define how an operation can expose outputs)
*** TOSCA-179 (Add "timeout" and "retry" keynames to an operation)
*** TOSCA-180 (Support of secured repositories for artifacts)
*** TOSCA-181 (Dependency requirement type should match any target node - see TOSCA-161)
*** TOSCA-186 (Model Composition) - Oct. 9th
*** TOSCA-187 (Using TOSCA models to describe NFV forward graph) - Oct. 9th

** Root issues for all Simple Profile work, essentially: TOSCA-12 (Basic Node Types) -- also related is TOSCA-11 (Lifecycle Operations)  

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_35883.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:20141020T223447Z
DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20141023T120000
DTEND;VALUE=DATE-TIME;TZID=America/New_York:20141023T133000
SEQUENCE:7885
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:20141020T223447Z
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 9: https://www.oasis-open.o
 rg/committees/document.php?document_id=54280&wg_abbrev=tosca
 \n** Thanks to Chip Holden for scribing \n* Informal co-chai
 r remarks\n** Also\, please welcome new TC members 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\, Radek Pospisil from Hewlett-Packard\
 , and Chris Lauwers (Individual Member)  \n*** New members: 
 expect a delay\, but you will be added to this list within a
  couple weeks of joining of the TC\n\nInteroperability Subco
 mmittee Report\n* Status and updates from co-chairs (Matt Ru
 tkowski and Richard Probst) \n** Minutes of 2014-10-06 & 201
 4-10=13: short meetings. no minutes recorded. \n \n\nTechnic
 al Marketing & Education Ad Hoc (lead: Karsten Beins)\n* htt
 ps://tools.oasis-open.org/issues/browse/TOSCA-131 - This iss
 ue related to all such activities \n* https://www.oasis-open
 .org/committees/document.php?document_id=54092&wg_abbrev=tos
 ca Video proposed for OASIS TOSCA playlist (first submitted 
 company/organization video for OASIS YouTube\, but others ex
 pected and requested!)\n** NOTE: Submit organization/company
  videos by uploading them to the OASIS TOSCA TC Documents se
 ction (Working Drafts folder) \n** All TC approved videos at
 : https://www.youtube.com/playlist?list=PLaYKtNo_BitZXdvyNDw
 Bi290IHxdi459v\n\nAd Hoc on Network Features (lead: Avi Vach
 nis)\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 Support\, e.g.\, Docker (lead: Hema
 l Surti) \n* https://tools.oasis-open.org/issues/browse/TOSC
 A-174 - This issue related to group activities\n\nTOSCA v1.1
 \nNOTE: As always\, only JIRA issues will be considered by t
 he TC for v1.1 for validation and approval. Note that any TC
  member can create or comment on a JIRA issue\, upload relat
 ed documents to Kavi (the OASIS website)\, etc. Please conta
 ct the co-chairs if you have any questions. The below issues
  at the discretion of the co-chairs and time permitting. \n*
 ** See https://tools.oasis-open.org/issues/browse/TOSCA-7 (A
 lternate encodings Service Templates\, e.g.\, YAML/JSON and 
 Simple Profile)\n* Resources\n** See 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 Si
 mple Profile is the http://docs.oasis-open.org/tosca/TOSCA/v
 1.0/os/ (public)\n** Note however that much work for v1.1 is
  being done first on the YAML rendering and Simple Profile D
 ocument (last TC approved CSD is http://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 Suggestions That Do NOT Change S
 emantics\, e.g.\, spelling\, grammar\, readability (use for 
 all v1.1 documents)\n\nNewly-Introduced Issues -- Brief Over
 view for TC and Discussion\n* https://issues.oasis-open.org/
 browse/TOSCA-188 (Requirements section should be turned to a
  map instead of list)\n* https://issues.oasis-open.org/brows
 e/TOSCA-189 (Application Monitoring - Proposal)\n* https://i
 ssues.oasis-open.org/browse/TOSCA-190 (Fix grammar for &quot
 \;Constraints&quot\; on a Target node of a requirement)\n* h
 ttps://issues.oasis-open.org/browse/TOSCA-191 (&ldquo\;augme
 ntation&rdquo\; behavior after relationship is selected in a
  requirement)\n* https://issues.oasis-open.org/browse/TOSCA-
 192 (how to differentiate get_propertiy and get_attribute)\n
 \n \n\nThe below was previously introduced to the TC. Any qu
 estions\, suggestions\, or requests to discuss further?\nSug
 gested activity (time permitting): The TC (with input from t
 he Simple Profile Ad Hoc members) is asked to briefly consid
 er scan the list to see if it is possible to close any of th
 e below issues.  \n*** https://tools.oasis-open.org/issues/b
 rowse/TOSCA-132(Use &quot\;set_property&quot\; methods to &q
 uot\;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/TOSC
 A-134 (Define TOSCA version type based upon Apache Maven ver
 sioning)\n*** https://tools.oasis-open.org/issues/browse/TOS
 CA-135 (Define/reference a Regex language (or subset) we wis
 h to support for constraints)\n*** https://tools.oasis-open.
 org/issues/browse/TOSCA-136 (Rules to Ensure Uniqueness of R
 equirement and Capability Names)  \n*** https://tools.oasis-
 open.org/issues/browse/TOSCA-137 (Need to address &quot\;opt
 ional&quot\; and &quot\;best can&quot\; on node requirements
 )  \n*** https://tools.oasis-open.org/issues/browse/TOSCA-13
 8 (Define a Network topology for L2 Networks\, etc.)\n*** ht
 tps://tools.oasis-open.org/issues/browse/TOSCA-139 (Compute 
 node scalability should be specified with a Compute node cap
 ability)\n*** https://tools.oasis-open.org/issues/browse/TOS
 CA-140 (Constraining the capabilities of multiple node templ
 ates)\n*** https://tools.oasis-open.org/issues/browse/TOSCA-
 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-op
 en.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 application servers.on two&quot\;)\
 n*** https://tools.oasis-open.org/issues/browse/TOSCA-145 (U
 pdate Ch 7\, Example 6\, &quot\;Template for deploying a two
 -tier application on two servers.&quot\;)\n*** https://tools
 .oasis-open.org/issues/browse/TOSCA-146 (Define a grammar fo
 r each property function and provide examples)\n*** https://
 tools.oasis-open.org/issues/browse/TOSCA-147 (Define grammar
  for and examples of using Relationship templates)\n*** http
 s://tools.oasis-open.org/issues/browse/TOSCA-148 (Need a mea
 ns to express cardinality on relationships)\n*** https://too
 ls.oasis-open.org/issues/browse/TOSCA-149 (Create an indepen
 dent section to describe a single requirement definition&#39
 \;s grammar)\n*** https://tools.oasis-open.org/issues/browse
 /TOSCA-150 (Work towards a common syntax for Requirement def
 initions)\n*** https://tools.oasis-open.org/issues/browse/TO
 SCA-151 (Resolve spec. behavior if name collisions occur on 
 named Requirements )\n*** https://tools.oasis-open.org/issue
 s/browse/TOSCA-152 (Extend Requirement grammar to support &q
 uot\;Optional/Best Can&quot\; Capability Type matching)\n***
  https://tools.oasis-open.org/issues/browse/TOSCA-153 (Defin
 e grammar and usage of Service Template keyname)\n*** https:
 //tools.oasis-open.org/issues/browse/TOSCA-154(Decide how se
 curity/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 as si
 mple YAML lists)\n*** https://tools.oasis-open.org/issues/br
 owse/TOSCA-156 (Are there IPv6 considerations (e.g.\, new pr
 operties) for tosca.capabilities.Endpoint)\n*** https://tool
 s.oasis-open.org/issues/browse/TOSCA-157 (Can/how do we make
  a property defn. &quot\;final&quot\; or &quot\;read-only&qu
 ot\;)\n*** https://tools.oasis-open.org/issues/browse/TOSCA-
 158 (Provide prose describging how Feature matching is done 
 by orchestrators)\n*** https://tools.oasis-open.org/issues/b
 rowse/TOSCA-159 (Describe how not all interfaces need to sup
 ply scripts (artifacts)\, it is a no-op behavior)\n*** https
 ://tools.oasis-open.org/issues/browse/TOSCA-160 (Need exampl
 es of using the &quot\;tosca.interfaces.relationship.Configu
 re&quot\; interface)\n*** https://tools.oasis-open.org/issue
 s/browse/TOSCA-161 (Need examples of using the built-in feat
 ure (Capability) and dependency (Requirement) of tosca.nodes
 .Root - see TOSCA-181)\n*** https://tools.oasis-open.org/iss
 ues/browse/TOSCA-162 (Provide recognized values fo tosca.nod
 es.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.o
 asis-open.org/issues/browse/TOSCA-164 (Do we need a restart 
 lifecycle operation for nodes?)\n*** https://tools.oasis-ope
 n.org/issues/browse/TOSCA-165https://tools.oasis-open.org/is
 sues/browse/TOSCA-165 (New use case / example: Selection/Rep
 lacement of web server type)\n*** https://tools.oasis-open.o
 rg/issues/browse/TOSCA-166 (New use case / example: Web Serv
 er with (one or more) runtimes environments)\n*** https://to
 ols.oasis-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 (Exp
 licit textual mention\, and grammar support\, for adding (ex
 tending) node operations) \n*** https://issues.oasis-open.or
 g/browse/TOSCA-176 (Add connectivity ability to Compute) \n*
 ** https://issues.oasis-open.org/browse/TOSCA-177 (Cardinali
 ty for node template) \n*** https://issues.oasis-open.org/br
 owse/TOSCA-178 (Define how an operation can expose outputs)\
 n*** https://issues.oasis-open.org/browse/TOSCA-179 (Add &qu
 ot\;timeout&quot\; and &quot\;retry&quot\; keynames to an op
 eration)\n*** https://issues.oasis-open.org/browse/TOSCA-180
  (Support of secured repositories for artifacts)\n*** https:
 //issues.oasis-open.org/browse/TOSCA-181 (Dependency require
 ment type should match any target node - see TOSCA-161)\n***
  https://issues.oasis-open.org/browse/TOSCA-186 (Model Compo
 sition) - Oct. 9th\n*** https://issues.oasis-open.org/browse
 /TOSCA-187 (Using TOSCA models to describe NFV forward graph
 ) - Oct. 9th\n\n** Root issues for all Simple Profile work\,
  essentially: https://tools.oasis-open.org/issues/browse/TOS
 CA-12 (Basic Node Types) -- also related is https://tools.oa
 sis-open.org/issues/browse/TOSCA-11 (Lifecycle Operations)  
 \n\nREMINDER: While a general approach can be decided by mot
 ion\, specific proposals and contributions need to be JIRA i
 ssue\nGroup: OASIS Topology and Orchestration Specification 
 for Cloud Applications (TOSCA) TC\nCreator: Mr. Paul Lipton
URL:https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=35883
UID:https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=35883
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]