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, 07 August 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:

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

 

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:

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

 

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
* July 24: https://www.oasis-open.org/committees/document.php?document_id=53680&wg_abbrev=tosca
** Thanks to Richard Probst for scribing
* Informal co-chair remarks
* Suggested Motion: The TC approves a 2nd Leave of Absense within 12 months for Peter Gibbels between July 31- August 22, 2014
** ODCA Forecast 2014 free passes (see here)
** TOSCA TC nominated for OASIS Open Standards Cup Outstanding Acccomplished TC (see email here
** Also, please welcome new TC members Jim Hunter from CA Technologies, Vasile Radoaca from Alcatel-Lucent, Noa Koffman from Alcatel-LucentLarry Lamers from VMWare, Kurt Spence from CA Technologies, and Wayne Witzel III from Canonical 
*** 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-08-04: https://www.oasis-open.org/apps/org/workgroup/tosca-interop/email/archives/201408/msg00002.html
** Minutes of 2014-07-28: https://www.oasis-open.org/apps/org/workgroup/tosca-interop/email/archives/201407/msg00004.html
*** IMPORTANT: You only need 1 slide to participate in the ODCA video (before next Monday)! 
** ODCA Forecast Conference Kiosk Video Slides (8/5 work-in-progress): https://www.oasis-open.org/committees/document.php?document_id=53733&wg_abbrev=tosca
** TC-approved short abstract and long abstract  for ODCA 2014 Forecast Conference

 

Technical Marketing and Education Ad Hoc (lead: Karsten Beins)  
TOSCA-131 - This issue related to all such activities 

 

Ad Hoc on Container Support, e.g., Docker, and TOSCA synergies (lead: Hemal Surti) 
TOSCA-174 - This issue related to group activities

 

Ad Hoc to Specify 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. Use cases from Derek, Dale, others. Search in JIRA for other "network" related issues. 
TOSCA-175 (Support navigation within the service template)

 

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 technical issues or questions. The below issues at the discretion of the co-chairs and time permitting. 

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 being done first on the YAML rendering and Simple Profile Document (last TC approved Committee Spec Draft is CSD01 posted March 27, 2014) 
*** See TOSCA-7 (Alternate encodings Service Templates, e.g., YAML/JSON)
** 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)
Editor's Report

Newly-Introduced Issues -- Brief Overview for TC and Discussion
*** TOSCA-176 (Add connectivity ability to Compute) 
*** TOSCA-177 (Cardinality for node template)
*** TOSCA-179 (Add "timeout" and "retry" keynames to an operation)
*** TOSCA-180 (Support of secured repositories for artifacts)

 

These issues have been recently introduced to the TC
NOTE: These should be associated with a CSD, e.g., CSD02 or CSD03
*** TOSCA-178 (Define how an operation can expose outputs)

 

CSD02-related issues (The below was previously introduced to the TC. Any questions, suggestions, or requests to discuss further?)
Note: Review issues that are receiving most attention in the YAML ad hoc. Any decisions or challenges? 
*** 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-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)
*** 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) 

 

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

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

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

** TOSCA-12 (Basic Node Types) -- also related is TOSCA-11 (Lifecycle Operations)  -- Simple Profile, essentially

 

TOSCA v1.0 
TOSCA-171 (Various v1.0 spec bugs)

* AOB

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_35872.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:20140807T022038Z
DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20140807T120000
DTEND;VALUE=DATE-TIME;TZID=America/New_York:20140807T133000
SEQUENCE:7882
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:20140807T022038Z
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
  \n\nP 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\nDue to prankster calls\, please contact th
 e co-chairs using your OASIS-registered email address to obt
 ain 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\nParti
 cipants are responsible to log their attendance on this Kavi
  calendar entry. When you join the meeting\, use this page t
 o record your attendance by clicking &quot\;Record My Attend
 ance&quot\;. If you are not on the internet\, you can reques
 t the chair to record your attendance on your behalf.\n\n \n
 \n  \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\
 n\nEvery person in the TC is asked to take their turn at scr
 ibing a meeting. When your name is called by the co-chair\, 
 please take your turn. You will use the chat room for the in
 itial scribing.\n\n \n\nScribing is easy:\n\n1. Change your 
 name using setting button in the chat room to &quot\;YOUR NA
 ME (Scribe - CO). \n\n2. Record motions/votes and some conte
 xt in the chat room during the meeting (people will add deta
 ils and help). You don&#39\;t have to quote people.\n\n3. La
 ter\, 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%2
 0Minutes%20Template.docx (Copy/append the raw chat room cont
 ents at the end of the doc (copy/paste works fine in most br
 owsers).\n\n4. Post draft file called &quot\;TOSCA TC Minute
 s 2012-MM-DD&quot\; to &quot\;Meeting Notes&quot\; folder he
 re: http://www.oasis-open.org/apps/org/workgroup/tosca/docum
 ents.php\n\n \n\n  \n\nT R A C K   Y O U R   V O T I N G   R
  I G H T S\n\nParticipants are responsible for the state of 
 their voting rights. The co-chairs will endeavor to update t
 he roster at http://www.oasis-open.org/apps/org/workgroup/to
 sca/members/roster.php before meetings. Except for leaves of
  absence\, the general rule is that a Voting Member who is a
 bsent from two consecutive meetings loses his or her voting 
 rights at the end of the second Meeting missed\, and a TC Me
 mber 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 f
 or more details).\n\n \n\n \n\nO T H E R   R E S O U R C E S
  \n\nTOSCA TC PAGE:\n\nhttp://www.oasis-open.org/apps/org/wo
 rkgroup/tosca/index.php\n\n \n\nTOSCA JIRA Project (all prop
 osals and issues): http://tools.oasis-open.org/issues/browse
 /TOSCA\n\n \n\nPROPOSALS AND ISSUES:\n\nTC standing rules fo
 r JIRA mandate that all technical and deliverable proposals 
 and issues be in the form of JIRA issues and will only be vo
 ted 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/msg
 00030.html\n\n \n\n \n\nP 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\nDue to prankster calls\
 , please contact the co-chairs using your OASIS-registered e
 mail address to obtain this information (reference: https://
 www.oasis-open.org/apps/org/workgroup/tosca/email/archives/2
 01307/msg00013.html)\n\n \n\n*** This meeting will use the p
 hone 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\nR E C O R D   Y O U R   O W N   A T T E N
  D A N C E\n\nParticipants are responsible to log their atte
 ndance on this Kavi calendar entry. When you join the meetin
 g\, use this page to record your attendance by clicking &quo
 t\;Record My Attendance&quot\;. If you are not on the intern
 et\, you can request the chair to record your attendance on 
 your behalf.\n\n \n\n  \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\n\nEvery person in the TC is asked to tak
 e their turn at scribing a meeting. When your name is called
  by the co-chair\, please take your turn. You will use the c
 hat room for the initial scribing.\n\n \n\nScribing is easy:
 \n\n1. Change your name using setting button in the chat roo
 m to &quot\;YOUR NAME (Scribe - CO). \n\n2. Record motions/v
 otes and some context in the chat room during the meeting (p
 eople will add details and help). You don&#39\;t have to quo
 te people.\n\n3. Later\, use this template document to produ
 ce draft minutes of the meeting as recorded in the chat room
 : http://www.oasis-open.org/apps/org/workgroup/tosca/downloa
 d.php/45088/TOSCA%20Minutes%20Template.docx (Copy/append the
  raw chat room contents at the end of the doc (copy/paste wo
 rks fine in most browsers).\n\n4. Post draft file called &qu
 ot\;TOSCA TC Minutes 2012-MM-DD&quot\; to &quot\;Meeting Not
 es&quot\; folder here: http://www.oasis-open.org/apps/org/wo
 rkgroup/tosca/documents.php\n\n \n\n  \n\nT R A C K   Y O U 
 R   V O T I N G   R I G H T S\n\nParticipants are responsibl
 e for the state of their voting rights. The co-chairs will e
 ndeavor to update the roster at http://www.oasis-open.org/ap
 ps/org/workgroup/tosca/members/roster.php before meetings. E
 xcept for leaves of absence\, the general rule is that a Vot
 ing Member who is absent from two consecutive meetings loses
  his or her voting rights at the end of the second Meeting m
 issed\, and a TC Member who has lost his or her voting right
 s shall regain them by attending two consecutive meetings af
 ter the end of the second Meeting attended. (see the TC Proc
 ess section 2.4.4 for more details).\n\n \n\n \n\nO T H E R 
   R E S O U R C E S \n\nTOSCA TC PAGE:\n\nhttp://www.oasis-o
 pen.org/apps/org/workgroup/tosca/index.php\n\n \n\nTOSCA JIR
 A Project (all proposals and issues): http://tools.oasis-ope
 n.org/issues/browse/TOSCA\n\n \n\nPROPOSALS AND ISSUES:\n\nT
 C standing rules for JIRA mandate that all technical and del
 iverable proposals and issues be in the form of JIRA issues 
 and will only be voted upon after 1 week. Issues can be disc
 ussed at any time. For details\, see the approved proposal a
 t: http://www.oasis-open.org/apps/org/workgroup/tosca/email/
 archives/201112/msg00030.html\n\nAgenda: Welcome / Roll\nCo-
 chair appoints a scribe\nReview/approve draft proposed agend
 a\nReview/approve draft minutes\n* July 24: https://www.oasi
 s-open.org/committees/document.php?document_id=53680&wg_abbr
 ev=tosca\n** Thanks to Richard Probst for scribing\n* Inform
 al co-chair remarks\n* Suggested Motion: The TC approves a 2
 nd Leave of Absense within 12 months for Peter Gibbels betwe
 en July 31- August 22\, 2014\n** ODCA Forecast 2014 free pas
 ses (see https://www.oasis-open.org/apps/org/workgroup/tosca
 /email/archives/201407/msg00041.html)\n** TOSCA TC nominated
  for OASIS Open Standards Cup Outstanding Acccomplished TC (
 see email https://lists.oasis-open.org/archives/members/2014
 07/msg00012.html) \n** Also\, please welcome new TC members 
 Jim Hunter from CA Technologies\, Vasile Radoaca from Alcate
 l-Lucent\, Noa Koffman from Alcatel-Lucent\, Larry Lamers fr
 om VMWare\, Kurt Spence from CA Technologies\, and Wayne Wit
 zel III from Canonical \n*** New members: expect a delay\, b
 ut you will be added to this list within a couple weeks of j
 oining of the TC\n\nInteroperability Subcommittee Report\n* 
 Status and updates from co-chairs (Matt Rutkowski and Richar
 d Probst) \n** Minutes of 2014-08-04: https://www.oasis-open
 .org/apps/org/workgroup/tosca-interop/email/archives/201408/
 msg00002.html\n** Minutes of 2014-07-28: https://www.oasis-o
 pen.org/apps/org/workgroup/tosca-interop/email/archives/2014
 07/msg00004.html\n*** IMPORTANT: You only need 1 slide to pa
 rticipate in the ODCA video (before next Monday)! \n** ODCA 
 Forecast Conference Kiosk Video Slides (8/5 work-in-progress
 ): https://www.oasis-open.org/committees/document.php?docume
 nt_id=53733&wg_abbrev=tosca\n** TC-approved https://www.oasi
 s-open.org/committees/document.php?document_id=53479&wg_abbr
 ev=tosca and https://www.oasis-open.org/committees/document.
 php?document_id=53430&wg_abbrev=tosca-interop  for ODCA 2014
  Forecast Conference\n\n \n\nTechnical Marketing and Educati
 on Ad Hoc (lead: Karsten Beins)  \n* https://tools.oasis-ope
 n.org/issues/browse/TOSCA-131 - This issue related to all su
 ch activities \n\n \n\nAd Hoc on Container Support\, e.g.\, 
 Docker\, and TOSCA synergies (lead: Hemal Surti) \n* https:/
 /tools.oasis-open.org/issues/browse/TOSCA-174 - This issue r
 elated to group activities\n\n \n\nAd Hoc to Specify Network
  Features (lead: Avi Vachnis)\n\n* https://www.oasis-open.or
 g/apps/org/workgroup/tosca/email/archives/201407/msg00000.ht
 ml (open to all TC members\, of course) \n* https://tools.oa
 sis-open.org/issues/browse/TOSCA-173 - This issue related to
  general group activities. Use cases from Derek\, Dale\, oth
 ers. Search in JIRA for other &quot\;network&quot\; related 
 issues. \n* https://tools.oasis-open.org/issues/browse/TOSCA
 -175 (Support navigation within the service template)\n\n \n
 \nTOSCA v1.1\nNOTE: As always\, only JIRA issues will be con
 sidered 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 technical issues or
  questions. The below issues at the discretion of the co-cha
 irs and time permitting. \n\n* Resources\n** See https://www
 .oasis-open.org/apps/org/workgroup/tosca/email/archives/2014
 07/msg00007.html\n** Current &quot\;base&quot\; for v1.1 XML
  Spec and Simple Profile is the http://docs.oasis-open.org/t
 osca/TOSCA/v1.0/os/ (public)\n** Note however that much work
  for v1.1 being done first on the YAML rendering and Simple 
 Profile Document (last TC approved Committee Spec Draft is h
 ttp://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1
 .0/posted March 27\, 2014) \n*** See https://tools.oasis-ope
 n.org/issues/browse/TOSCA-7 (Alternate encodings Service Tem
 plates\, e.g.\, YAML/JSON)\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\, layout (use for all v1.1 documents)\n* Edi
 tor&#39\;s Report\n\nNewly-Introduced Issues -- Brief Overvi
 ew for TC and Discussion\n*** https://issues.oasis-open.org/
 browse/TOSCA-176 (Add connectivity ability to Compute) \n***
  https://issues.oasis-open.org/browse/TOSCA-177 (Cardinality
  for node template)\n*** https://issues.oasis-open.org/brows
 e/TOSCA-179 (Add &quot\;timeout&quot\; and &quot\;retry&quot
 \; keynames to an operation)\n*** https://issues.oasis-open.
 org/browse/TOSCA-180 (Support of secured repositories for ar
 tifacts)\n\n \n\nThese issues have been recently introduced 
 to the TC\nNOTE: These should be associated with a CSD\, e.g
 .\, CSD02 or CSD03\n*** https://issues.oasis-open.org/browse
 /TOSCA-178 (Define how an operation can expose outputs)\n\n 
 \n\nCSD02-related issues (The below was previously introduce
 d to the TC. Any questions\, suggestions\, or requests to di
 scuss further?)\nNote: Review issues that are receiving most
  attention in the YAML ad hoc. Any decisions or challenges? 
 \n*** https://tools.oasis-open.org/issues/browse/TOSCA-132(U
 se &quot\;set_property&quot\; methods to &quot\;push&quot\; 
 values from template inputs to nodes) \n*** https://tools.oa
 sis-open.org/issues/browse/TOSCA-133 (add material for defin
 ing a nested template that implements a node type)\n*** http
 s://tools.oasis-open.org/issues/browse/TOSCA-134 (Define TOS
 CA version type based upon Apache Maven versioning)\n*** htt
 ps://tools.oasis-open.org/issues/browse/TOSCA-135 (Define/re
 ference 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/b
 rowse/TOSCA-140 (Constraining the capabilities of multiple n
 ode templates)\n*** https://tools.oasis-open.org/issues/brow
 se/TOSCA-141 (Specifying Environment Constraints for Node Te
 mplates) \n*** https://tools.oasis-open.org/issues/browse/TO
 SCA-142 (Define normative Artifact Types \n*** https://tools
 .oasis-open.org/issues/browse/TOSCA-143 (Define normative to
 sca.nodes.Network Node Type)\n*** https://tools.oasis-open.o
 rg/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/TOS
 CA-145 (Update Ch 7\, Example 6\, &quot\;Template for deploy
 ing a two-tier application on two servers.&quot\;)\n*** http
 s://tools.oasis-open.org/issues/browse/TOSCA-146 (Define a g
 rammar for each property function and provide examples)\n\n*
 ** https://tools.oasis-open.org/issues/browse/TOSCA-147 (Def
 ine 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 def
 inition&#39\;s grammar)\n*** https://tools.oasis-open.org/is
 sues/browse/TOSCA-150 (Work towards a common syntax for Requ
 irement definitions)\n*** https://tools.oasis-open.org/issue
 s/browse/TOSCA-151 (Resolve spec. behavior if name collision
 s occur on named Requirements )\n*** https://tools.oasis-ope
 n.org/issues/browse/TOSCA-152 (Extend Requirement grammar to
  support &quot\;Optional/Best Can&quot\; Capability Type mat
 ching)\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(De
 cide how security/access control work with Nodes\, update gr
 ammar\, etc.)\n*** https://tools.oasis-open.org/issues/brows
 e/TOSCA-155 (How do we provide constraints on properties dec
 lared as simple YAML lists)\n*** https://tools.oasis-open.or
 g/issues/browse/TOSCA-156 (Are there IPv6 considerations (e.
 g.\, new properties) for tosca.capabilities.Endpoint)\n*** h
 ttps://tools.oasis-open.org/issues/browse/TOSCA-157 (Can/how
  do we make a property defn. &quot\;final&quot\; or &quot\;r
 ead-only&quot\;)\n*** https://tools.oasis-open.org/issues/br
 owse/TOSCA-158 (Provide prose describging how Feature matchi
 ng is done by orchestrators)\n*** https://tools.oasis-open.o
 rg/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 &quot\;tosca.interfaces.relations
 hip.Configure&quot\; interface)\n*** https://tools.oasis-ope
 n.org/issues/browse/TOSCA-161 (Need examples of using the bu
 ilt-in feature (Capability) and dependency (Requirement) of 
 tosca.nodes.Root)\n*** https://tools.oasis-open.org/issues/b
 rowse/TOSCA-162 (Provide recognized values fo tosca.nodes.co
 mpute 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 lifec
 ycle 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/Replacem
 ent of web server type)\n*** https://tools.oasis-open.org/is
 sues/browse/TOSCA-166 (New use case / example: Web Server wi
 th (one or more) runtimes environments)\n*** https://tools.o
 asis-open.org/issues/browse/TOSCA-169 (Resolve text and gram
 mar for the &quot\;get_ref_property&quot\; function)\n*** ht
 tps://tools.oasis-open.org/issues/browse/TOSCA-170 (Explicit
  textual mention\, and grammar support\, for adding (extendi
 ng) node operations) \n\n \n\nCSD03-related issues (New or R
 eady to be Revisited -- Overview for TC and Discussion/Quest
 ions)\n\nCSD03-related issues (The below was previously intr
 oduced to the TC. Any questions\, suggestions\, or requests 
 to discuss further?)\n*** https://tools.oasis-open.org/issue
 s/browse/TOSCA-167 (New use case / example: Show abstract su
 bstitution of Compute node OS...) \n*** https://tools.oasis-
 open.org/issues/browse/TOSCA-168 (New use case / example: Sh
 ow how substitution of IaaS can be accomplished) \n\n** http
 s://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 Servic
 e Templates)\n** https://tools.oasis-open.org/issues/browse/
 TOSCA-114(Composite Capabilities and Requirements)\n\n** htt
 ps://tools.oasis-open.org/issues/browse/TOSCA-12 (Basic Node
  Types) -- also related is https://tools.oasis-open.org/issu
 es/browse/TOSCA-11 (Lifecycle Operations)  -- Simple Profile
 \, essentially\n\n \n\nTOSCA v1.0 \n* https://tools.oasis-op
 en.org/issues/browse/TOSCA-171 (Various v1.0 spec bugs)\n\n*
  AOB\n\nREMINDER: While a general approach can be decided by
  motion\, specific proposals and contributions need to be JI
 RA issue\nGroup: OASIS Topology and Orchestration Specificat
 ion for Cloud Applications (TOSCA) TC\nCreator: Mr. Paul Lip
 ton
URL:https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=35872
UID:https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=35872
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]