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: Groups - Event "NEW! TOSCA TC Regular Meeting" modified


Event Title: NEW! TOSCA TC Regular Meeting

Date: Thursday, 27 March 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, 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:
 
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:
 
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
Co-chair appoints a scribe
Review/approve draft proposed agenda
Review/approve draft minutes
* March 20: https://www.oasis-open.org/committees/document.php?document_id=52567&wg_abbrev=tosca
** Thanks to Juergen Meynert for scribing
* Informal co-chair remarks

 

Interoperability Subcommittee Report
Status and updates from co-chairs
* Note: no minutes available as the Interop SC has temporarily given up its meeting time to informally suppliment the CxO Presentation/Whitepaper ad hoc group activities (Meetings are wiithout standing. See below.) 

 

Ad Hoc to Develop a CxO, Line-of-Business, Thought-Leader Focused Presentation and White Paper 
TOSCA-131 - This issue related to all such activities 

 
TOSCA v1.0
Note: The spec editors may wish to discuss some of the work done on the errata 
* TOSCA-124 (Errata - Reference Corrections)

TOSCA v1.1
NOTE: As always, only JIRA issues will be considered by the TC for v1.1 document changes (any TC member can create a JIRA issue. These issues at the discretion of the co-chairs and time permitting. Please contact the co-chairs if you have technical issues or questions)

Resources
* Current "base" for proposed spec changes, see Candidate OASIS Standard (public)
TOSCA-108: Catch-all for All Editorial Suggestions That Do NOT Change Semantics, e.g., spelling, grammar, readability, layout (use for all v1.1 documents)
* TOSCA-171 (Various v1.0 spec bugs)
Editor's Report
TOSCA-7 (Alternate encodings Service Templates, e.g., YAML/JSON
Note: The TC may wish to consider the following motion (or equivalent): The TC approves TOSCA Simple Profile in YAML Version 1.0, WD01 rev 38> at https://www.oasis-open.org/committees/document.php?document_id=52571&wg_abbrev=tosca as a Committee Specification Draft document and designates  the PDF version of the specification as authoritative.

 

WD01-related issue

Note: Can any of these issues be closed, since WD01 has been accepted? 
*** TOSCA-136 (Rules to Ensure Uniqueness of Requirement and Capability Names)  
*** TOSCA-137 (Need to address "optional" and "best can" on node requirements)  
*** 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.")

 

WD02-related issues (New or Ready to be Revisited -- Overview for TC and Discussion/Questions)

 

WD03-related issues (New or Ready to be Revisited -- Overview for TC and Discussion/Questions)

 

WD03-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 with different Node Type Impls.) 
*** TOSCA-168 (New use case / example: Show how substitution of IaaS can be accomplished) 

 

WD02-related issues (The below was previously introduced to the TC. Any questions, suggestions, or requests to discuss further?)
*** 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-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-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)
*** 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-12 (Set of Basic Node Types) -- also related is TOSCA-11 (Set of Fundamental Lifecycle Operations)  -- Simple Profile, essentially??

** TOSCA-115 (Requirements Capabilities to Provide Interfaces)
** TOSCA-114 (Composite Capabilities and Requirements)
** TOSCA-126 (Specifying connectivity to endpoints hosted outside a Service Template)
** TOSCA-127 (Conventions for provisioning network connectivity for Service Templates)

* AOB

REMINDER: While a general approach can be decided by motion, specific proposals and contributions need to be JIRA issues

 


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

NOTE: The best way to keep your desktop calendar updated is to subscribe to the Group calendar.

  • Learn more about subscribing here.
  • View the updated Group web calendar here.
BEGIN:VCALENDAR
CALSCALE:GREGORIAN
METHOD:PUBLISH
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
CATEGORIES:MEETING
STATUS:CONFIRMED
TRANSP:OPAQUE
DTSTAMP:20140327T000000Z
DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20140327T120000
DTEND;VALUE=DATE-TIME;TZID=America/New_York:20140327T133000
SEQUENCE:7361
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.
DESCRIPTION:\n	IMPORTANT: Please examine this entire event description
  for a handy list of resources, responsibilities, and
  more!\n\n	\n		 \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\n	\n		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)\n	\n		
  \n	\n		*** 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 ***\n	\n		 \n	\n		
   \n	\n		R E C O R D   Y O U R   O W N   A T T E N D A N C
  E\n	\n		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.\n	\n		
  \n	\n		  \n	\n		Y O U R   S C R I B E   R E S P O N S I B I
  L I T Y\n	\n		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.\n	\n		 \n	\n		Scribing is
  easy:\n	\n		1. Change your name using setting button in the
  chat room to "YOUR NAME (Scribe - CO). \n	\n		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.\n	\n		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).\n	\n		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\n	\n		
  \n	\n		  \n	\n		T R A C K   Y O U R   V O T I N G   R I G H
  T S\n	\n		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).\n	\n		 \n	\n		 \n	\n		O T H E R   R E S O U R C E
  S \n	\n		TOSCA TC
  PAGE:\n	\n		http://www.oasis-open.org/apps/org/workgroup/tosca/index.php\n	\n		
  \n	\n		TOSCA JIRA Project (all proposals and issues):
  http://tools.oasis-open.org/issues/browse/TOSCA\n	\n		
  \n	\n		PROPOSALS AND ISSUES:\n	\n		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\n\n\n	
  \n\n	\n		 \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\n	\n		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)\n	\n		
  \n	\n		*** 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 ***\n	\n		 \n	\n		
   \n	\n		R E C O R D   Y O U R   O W N   A T T E N D A N C
  E\n	\n		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.\n	\n		
  \n	\n		  \n	\n		Y O U R   S C R I B E   R E S P O N S I B I
  L I T Y\n	\n		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.\n	\n		 \n	\n		Scribing is
  easy:\n	\n		1. Change your name using setting button in the
  chat room to "YOUR NAME (Scribe - CO). \n	\n		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.\n	\n		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).\n	\n		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\n	\n		
  \n	\n		  \n	\n		T R A C K   Y O U R   V O T I N G   R I G H
  T S\n	\n		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).\n	\n		 \n	\n		 \n	\n		O T H E R   R E S O U R C E
  S \n	\n		TOSCA TC
  PAGE:\n	\n		http://www.oasis-open.org/apps/org/workgroup/tosca/index.php\n	\n		
  \n	\n		TOSCA JIRA Project (all proposals and issues):
  http://tools.oasis-open.org/issues/browse/TOSCA\n	\n		
  \n	\n		PROPOSALS AND ISSUES:\n	\n		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\n\n\n	
  \n\nAgenda: \n	Welcome / Roll\n	Co-chair appoints a
  scribe\n	Review/approve draft proposed
  agenda\n	Review/approve draft minutes\n	* March 20:
  https://www.oasis-open.org/committees/document.php?document_id=52567&wg_abbrev=tosca\n	**
  Thanks to Juergen Meynert for scribing\n	* Informal co-chair
  remarks\n\n	 \n\n	\n		Interoperability Subcommittee
  Report\n		* Status and updates from co-chairs\n		* Note: no
  minutes available as the Interop SC has temporarily given up
  its meeting time to informally suppliment the CxO
  Presentation/Whitepaper ad hoc group activities (Meetings
  are wiithout standing. See below.) \n	\n		 \n	\n		Ad Hoc to
  Develop a CxO, Line-of-Business, Thought-Leader Focused
  Presentation and White Paper \n		*
  https://tools.oasis-open.org/issues/browse/TOSCA-131 - This
  issue related to all such activities \n	\n		 \n	\n		TOSCA
  v1.0\n	\n		Note: The spec editors may wish to discuss some
  of the work done on the errata \n	\n		*
  https://tools.oasis-open.org/issues/browse/TOSCA-124 (Errata
  - Reference Corrections)\n\n\n	TOSCA v1.1\n	NOTE: As always,
  only JIRA issues will be considered by the TC for v1.1
  document changes (any TC member can create a JIRA issue.
  These issues at the discretion of the co-chairs and time
  permitting. Please contact the co-chairs if you have
  technical issues or questions)\n\n	* Resources\n	* Current
  "base" for proposed spec changes, see
  http://docs.oasis-open.org/tosca/TOSCA/v1.0/cos01/
  (public)\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, layout (use
  for all v1.1 documents)\n	*
  https://tools.oasis-open.org/issues/browse/TOSCA-171
  (Various v1.0 spec bugs)\n	* Editor's Report\n	*
  https://tools.oasis-open.org/issues/browse/TOSCA-7
  (Alternate encodings Service Templates, e.g.,
  YAML/JSON\n	Note: The TC may wish to consider the following
  motion (or equivalent): The TC approves TOSCA Simple Profile
  in YAML Version 1.0, WD01 rev 38> at
  https://www.oasis-open.org/committees/document.php?document_id=52571&wg_abbrev=tosca
  as a Committee Specification Draft document and designates 
  the PDF version of the specification as authoritative.\n\n	
  \n\n	WD01-related issue\n\n	Note: Can any of these issues be
  closed, since WD01 has been accepted? \n	***
  https://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 "optional" and "best can" on node
  requirements)  \n	***
  https://tools.oasis-open.org/issues/browse/TOSCA-144(Update
  Ch 6, Example 5, "Template 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 two-tier
  application on two servers.")\n\n	 \n\n	WD02-related issues
  (New or Ready to be Revisited -- Overview for TC and
  Discussion/Questions)\n	\n	 \n\n	WD03-related issues (New or
  Ready to be Revisited -- Overview for TC and
  Discussion/Questions)\n\n	 \n\n	WD03-related issues (The
  below was previously introduced to the TC. Any questions,
  suggestions, or requests to discuss further?)\n	***
  https://tools.oasis-open.org/issues/browse/TOSCA-167 (New
  use case / example: Show abstract substitution of Compute
  node OS with different Node Type Impls.) \n	***
  https://tools.oasis-open.org/issues/browse/TOSCA-168 (New
  use case / example: Show how substitution of IaaS can be
  accomplished) \n\n	 \n\n	WD02-related issues (The below was
  previously introduced to the TC. Any questions, suggestions,
  or requests to discuss further?)\n	***
  https://tools.oasis-open.org/issues/browse/TOSCA-132(Use
  "set_property" methods to "push" values from template inputs
  to nodes) \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 (Define
  TOSCA version type based upon Apache Maven versioning)\n	***
  https://tools.oasis-open.org/issues/browse/TOSCA-135
  (Define/reference a Regex language (or subset) we wish to
  support for constraints)\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
  (Compute node scalability should be specified with 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.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-open.org/issues/browse/TOSCA-143 (Define
  normative tosca.nodes.Network Node Type)\n	***
  https://tools.oasis-open.org/issues/browse/TOSCA-146 (Define
  a grammar for 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	***
  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 independent section to describe a single requirement
  definition's grammar)\n	***
  https://tools.oasis-open.org/issues/browse/TOSCA-150 (Work
  towards a common syntax for Requirement definitions)\n	***
  https://tools.oasis-open.org/issues/browse/TOSCA-151
  (Resolve spec. behavior if name collisions occur on named
  Requirements )\n	***
  https://tools.oasis-open.org/issues/browse/TOSCA-152 (Extend
  Requirement grammar to support "Optional/Best Can"
  Capability Type matching)\n	***
  https://tools.oasis-open.org/issues/browse/TOSCA-153 (Define
  grammar and usage of Service Template keyname)\n	***
  https://tools.oasis-open.org/issues/browse/TOSCA-154(Decide
  how 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 as simple YAML
  lists)\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-157
  (Can/how do we make a property defn. "final" or
  "read-only")\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/browse/TOSCA-159
  (Describe how not all interfaces need to supply scripts
  (artifacts), it is a no-op behavior)\n	***
  https://tools.oasis-open.org/issues/browse/TOSCA-160 (Need
  examples of using the
  "tosca.interfaces.relationship.Configure" interface)\n	***
  https://tools.oasis-open.org/issues/browse/TOSCA-161 (Need
  examples of using the built-in feature (Capability) and
  dependency (Requirement) of tosca.nodes.Root)\n	***
  https://tools.oasis-open.org/issues/browse/TOSCA-162
  (Provide recognized values fo tosca.nodes.compute
  properties: os_arch)\n	***
  https://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	***
  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/browse/TOSCA-166 (New
  use case / example: Web Server with (one or more) runtimes
  environments)\n	***
  https://tools.oasis-open.org/issues/browse/TOSCA-169
  (Resolve text and grammar for the "get_ref_property"
  function)\n	***
  https://tools.oasis-open.org/issues/browse/TOSCA-170
  (Explicit textual mention, and grammar support, for adding
  (extending) node operations) \n\n	 \n\n	**
  https://tools.oasis-open.org/issues/browse/TOSCA-12 (Set of
  Basic Node Types) -- also related is
  https://tools.oasis-open.org/issues/browse/TOSCA-11 (Set of
  Fundamental Lifecycle Operations)  -- Simple Profile,
  essentially??\n\n	**
  https://tools.oasis-open.org/issues/browse/TOSCA-115
  (Requirements Capabilities to Provide Interfaces)\n	**
  https://tools.oasis-open.org/issues/browse/TOSCA-114(Composite
  Capabilities and Requirements)\n	**
  https://tools.oasis-open.org/issues/browse/TOSCA-126
  (Specifying connectivity to endpoints hosted outside a
  Service Template)\n	**
  https://tools.oasis-open.org/issues/browse/TOSCA-127
  (Conventions for provisioning network connectivity for
  Service Templates)\n\n	* AOB\n\n	REMINDER: While a general
  approach can be decided by motion, specific proposals and
  contributions need to be JIRA issues\n\n	 \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=35853
UID:https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=35853
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]