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, 09 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 2: https://www.oasis-open.org/committees/document.php?document_id=54242&wg_abbrev=tosca
** Thanks to Moshe Elisha for scribing 
* Informal co-chair remarks
** Also, please welcome new TC members Nikunj Nemani from VMware, Wan Anfeng from Huawei, Radek Pospisil from Hewlett-Packard, Chris Lauwers (Individual Member) and Idan Moyal from GigaSpaces Technologies 
*** 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: short meeting. 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-186 (Model Composition) - Oct. 9th
TOSCA-187 (Using TOSCA models to describe NFV forward graph) - Oct. 9th
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)

 

CSD02-related issues (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)

CSD03-related issues (The below was previously introduced to the TC. Any questions, suggestions, or requests to discuss further?)
Not for discussion this TC meeting (these issues will be restored after CSD02 is approved.

** 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_35881.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:20141009T153423Z
DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20141009T120000
DTEND;VALUE=DATE-TIME;TZID=America/New_York:20141009T133000
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:20141009T153423Z
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 2: https://www.oasis-open.o
 rg/committees/document.php?document_id=54242&wg_abbrev=tosca
 \n** Thanks to Moshe Elisha for scribing \n* Informal co-cha
 ir remarks\n** Also\, please welcome new TC members Nikunj N
 emani from VMware\, Wan Anfeng from Huawei\, Radek Pospisil 
 from Hewlett-Packard\, Chris Lauwers (Individual Member) and
  Idan Moyal from GigaSpaces Technologies \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: shor
 t meeting. no minutes recorded. \n \n\nTechnical Marketing &
  Education Ad Hoc (lead: Karsten Beins)\n* https://tools.oas
 is-open.org/issues/browse/TOSCA-131 - This issue related to 
 all such activities \n* https://www.oasis-open.org/committee
 s/document.php?document_id=54092&wg_abbrev=tosca Video propo
 sed for OASIS TOSCA playlist (first submitted company/organi
 zation video for OASIS YouTube\, but others expected and req
 uested!)\n** NOTE: Submit organization/company videos by upl
 oading them to the OASIS 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 Network 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 - Th
 is issue related to general group activities.  \n\nAd Hoc on
  Container Support\, e.g.\, Docker (lead: Hemal Surti) \n* h
 ttps://tools.oasis-open.org/issues/browse/TOSCA-174 - This i
 ssue related to group activities\n\nTOSCA v1.1\nNOTE: As alw
 ays\, only JIRA issues will be considered by the TC for v1.1
  for validation and approval. Note that any TC member can cr
 eate or comment on a JIRA issue\, upload related documents t
 o Kavi (the OASIS website)\, etc. Please contact the co-chai
 rs if you have any questions. The below issues at the discre
 tion of the co-chairs and time permitting. \n*** See https:/
 /tools.oasis-open.org/issues/browse/TOSCA-7 (Alternate encod
 ings Service Templates\, e.g.\, YAML/JSON and Simple Profile
 )\n* Resources\n** See https://www.oasis-open.org/apps/org/w
 orkgroup/tosca/email/archives/201407/msg00007.html\n** Curre
 nt &quot\;base&quot\; for v1.1 XML Spec and Simple Profile i
 s the http://docs.oasis-open.org/tosca/TOSCA/v1.0/os/ (publi
 c)\n** Note however that much work for v1.1 is being done fi
 rst on the YAML rendering and Simple Profile Document (last 
 TC approved CSD is http://docs.oasis-open.org/tosca/TOSCA-Si
 mple-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 Semantics\, e.g
 .\, spelling\, grammar\, readability (use for all v1.1 docum
 ents)\n\nNewly-Introduced Issues -- Brief Overview for TC an
 d Discussion\n* https://issues.oasis-open.org/browse/TOSCA-1
 86 (Model Composition) - Oct. 9th\n* https://issues.oasis-op
 en.org/browse/TOSCA-187 (Using TOSCA models to describe NFV 
 forward graph) - Oct. 9th\n* https://issues.oasis-open.org/b
 rowse/TOSCA-188 (Requirements section should be turned to a 
 map instead of list)\n* https://issues.oasis-open.org/browse
 /TOSCA-189 (Application Monitoring - Proposal)\n* https://is
 sues.oasis-open.org/browse/TOSCA-190 (Fix grammar for &quot\
 ;Constraints&quot\; on a Target node of a requirement)\n* ht
 tps://issues.oasis-open.org/browse/TOSCA-191 (&ldquo\;augmen
 tation&rdquo\; behavior after relationship is selected in a 
 requirement)\n* https://issues.oasis-open.org/browse/TOSCA-1
 92 (how to differentiate get_propertiy and get_attribute)\n\
 n \n\nCSD02-related issues (The below was previously introdu
 ced to the TC. Any questions\, suggestions\, or requests to 
 discuss further?)\nSuggested activity (time permitting): The
  TC (with input from the Simple Profile Ad Hoc members) is a
 sked to briefly consider scan the list to see if it is possi
 ble to close any of the below issues.  \n*** https://tools.o
 asis-open.org/issues/browse/TOSCA-132(Use &quot\;set_propert
 y&quot\; methods to &quot\;push&quot\; values from template 
 inputs to nodes) \n*** https://tools.oasis-open.org/issues/b
 rowse/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*** https://tools.oasis-open
 .org/issues/browse/TOSCA-135 (Define/reference a Regex langu
 age (or subset) we wish to support for constraints)\n*** htt
 ps://tools.oasis-open.org/issues/browse/TOSCA-136 (Rules to 
 Ensure Uniqueness of Requirement and Capability Names)  \n**
 * https://tools.oasis-open.org/issues/browse/TOSCA-137 (Need
  to address &quot\;optional&quot\; and &quot\;best can&quot\
 ; on node requirements)  \n*** https://tools.oasis-open.org/
 issues/browse/TOSCA-138 (Define a Network topology for L2 Ne
 tworks\, etc.)\n*** https://tools.oasis-open.org/issues/brow
 se/TOSCA-139 (Compute node scalability should be specified w
 ith a Compute node capability)\n*** https://tools.oasis-open
 .org/issues/browse/TOSCA-140 (Constraining the capabilities 
 of multiple node templates)\n*** https://tools.oasis-open.or
 g/issues/browse/TOSCA-141 (Specifying Environment Constraint
 s for Node Templates) \n*** https://tools.oasis-open.org/iss
 ues/browse/TOSCA-142 (Define normative Artifact 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(Update Ch 6\, Exampl
 e 5\, &quot\;Template for deploying a two-tier application s
 ervers.on two&quot\;)\n*** https://tools.oasis-open.org/issu
 es/browse/TOSCA-145 (Update Ch 7\, Example 6\, &quot\;Templa
 te for deploying a two-tier application on two servers.&quot
 \;)\n*** https://tools.oasis-open.org/issues/browse/TOSCA-14
 6 (Define a grammar for each property function and provide e
 xamples)\n*** https://tools.oasis-open.org/issues/browse/TOS
 CA-147 (Define grammar for and examples of using Relationshi
 p templates)\n*** https://tools.oasis-open.org/issues/browse
 /TOSCA-148 (Need a means to express cardinality on relations
 hips)\n*** https://tools.oasis-open.org/issues/browse/TOSCA-
 149 (Create an independent section to describe a single requ
 irement definition&#39\;s grammar)\n*** https://tools.oasis-
 open.org/issues/browse/TOSCA-150 (Work towards a common synt
 ax for Requirement definitions)\n*** https://tools.oasis-ope
 n.org/issues/browse/TOSCA-151 (Resolve spec. behavior if nam
 e 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/b
 rowse/TOSCA-153 (Define grammar and usage of Service Templat
 e keyname)\n*** https://tools.oasis-open.org/issues/browse/T
 OSCA-154(Decide how security/access control work with Nodes\
 , update grammar\, etc.)\n*** https://tools.oasis-open.org/i
 ssues/browse/TOSCA-155 (How do we provide constraints on pro
 perties declared as simple YAML lists)\n*** https://tools.oa
 sis-open.org/issues/browse/TOSCA-156 (Are there IPv6 conside
 rations (e.g.\, new properties) for tosca.capabilities.Endpo
 int)\n*** https://tools.oasis-open.org/issues/browse/TOSCA-1
 57 (Can/how do we make a property defn. &quot\;final&quot\; 
 or &quot\;read-only&quot\;)\n*** https://tools.oasis-open.or
 g/issues/browse/TOSCA-158 (Provide prose describging how Fea
 ture matching is done by orchestrators)\n*** https://tools.o
 asis-open.org/issues/browse/TOSCA-159 (Describe how not all 
 interfaces need to supply scripts (artifacts)\, it is a no-o
 p behavior)\n*** https://tools.oasis-open.org/issues/browse/
 TOSCA-160 (Need examples of using the &quot\;tosca.interface
 s.relationship.Configure&quot\; interface)\n*** https://tool
 s.oasis-open.org/issues/browse/TOSCA-161 (Need examples of u
 sing the built-in feature (Capability) and dependency (Requi
 rement) of tosca.nodes.Root - see TOSCA-181)\n*** https://to
 ols.oasis-open.org/issues/browse/TOSCA-162 (Provide recogniz
 ed values fo tosca.nodes.compute properties: os_arch)\n*** h
 ttps://tools.oasis-open.org/issues/browse/TOSCA-163(Provide 
 recognized values fo tosca.nodes.BlockStorage: store_fs_type
 )\n*** https://tools.oasis-open.org/issues/browse/TOSCA-164 
 (Do we need a restart lifecycle operation for nodes?)\n*** h
 ttps://tools.oasis-open.org/issues/browse/TOSCA-165https://t
 ools.oasis-open.org/issues/browse/TOSCA-165 (New use case / 
 example: Selection/Replacement of web server type)\n*** http
 s://tools.oasis-open.org/issues/browse/TOSCA-166 (New use ca
 se / example: Web Server with (one or more) runtimes environ
 ments)\n*** https://tools.oasis-open.org/issues/browse/TOSCA
 -169 (Resolve text and grammar for the &quot\;get_ref_proper
 ty&quot\; function)\n*** https://tools.oasis-open.org/issues
 /browse/TOSCA-170 (Explicit textual mention\, and grammar su
 pport\, for adding (extending) node operations) \n*** https:
 //issues.oasis-open.org/browse/TOSCA-176 (Add connectivity a
 bility to Compute) \n*** https://issues.oasis-open.org/brows
 e/TOSCA-177 (Cardinality for node template) \n*** https://is
 sues.oasis-open.org/browse/TOSCA-178 (Define how an operatio
 n can expose outputs)\n*** https://issues.oasis-open.org/bro
 wse/TOSCA-179 (Add &quot\;timeout&quot\; and &quot\;retry&qu
 ot\; keynames to an operation)\n*** https://issues.oasis-ope
 n.org/browse/TOSCA-180 (Support of secured repositories for 
 artifacts)\n*** https://issues.oasis-open.org/browse/TOSCA-1
 81 (Dependency requirement type should match any target node
  - see TOSCA-161)\n\nCSD03-related issues (The below was pre
 viously introduced to the TC. Any questions\, suggestions\, 
 or requests to discuss further?)\nNot for discussion this TC
  meeting (these issues will be restored after CSD02 is appro
 ved.\n\n** Root issues for all Simple Profile work\, essenti
 ally: https://tools.oasis-open.org/issues/browse/TOSCA-12 (B
 asic Node Types) -- also related is https://tools.oasis-open
 .org/issues/browse/TOSCA-11 (Lifecycle Operations)  \n\nREMI
 NDER: While a general approach can be decided by motion\, sp
 ecific proposals and contributions need to be JIRA issue\nGr
 oup: OASIS Topology and Orchestration Specification for Clou
 d Applications (TOSCA) TC\nCreator: Mr. Paul Lipton
URL:https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=35881
UID:https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=35881
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]