Interop testing Call

[OASIS Open<workgroup_mailer@lists.oasis-open.org>]

Event Title: Interop testing Call

---

Date: Wednesday, 01 March 2017, 12:00pm to 01:00pm EST
Location: GoToMeeting
Description

https://global.gotomeeting.com/join/645215981

You can also dial in using your phone.

Norway: +47 21 04 30 59
France: +33 (0) 170 950 590
Germany: +49 (0) 692 5736 7300
Italy: +39 0 699 26 68 65
United Kingdom: +44 (0) 20 3713 5011
United States: +1 (312) 757-3119

Access Code: 645-215-981

This meeting counts towards voter eligibility.

---

Agenda

1. Status on TAs for “parser” implementations, Github logistics,  evaluation of remaining work.
2. What is the highest priority for TOSCA testing? (highest return for TOSCA users?) What conformance targets are most important in the short-mid term? “orchestrator” ? parser?
3. Can we identify some feature sets -  conformance  profiles?
4. TA design & practical aspects: should we assume a representative set of predefined, minimal “service templates” as basis for testing? Or should we be able to use any template during testing?

---

Owner: Mr Jacques Durand
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

• Learn more about subscribing here.
• View the OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC calendar here.
• You may receive future notifications with updates to this event. Update the event on your calendar by accepting the changes.

Attachment: ical_45000.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:20170301T001520Z
DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20170301T120000
DTEND;VALUE=DATE-TIME;TZID=America/New_York:20170301T130000
SEQUENCE:0
SUMMARY:Interop testing Call
LOCATION:GoToMeeting
LAST-MODIFIED:20170301T001520Z
ORGANIZER:workgroup_mailer@lists.oasis-open.org
ATTENDEE;CUTYPE=GROUP:MAILTO:tosca@lists.oasis-open.org
DESCRIPTION:https://global.gotomeeting.com/join/645215981\n\nYou can als
 o dial in using your phone.\n\nNorway: +47 21 04 30 59\nFran
 ce: +33 (0) 170 950 590\nGermany: +49 (0) 692 5736 7300\nIta
 ly: +39 0 699 26 68 65\nUnited Kingdom: +44 (0) 20 3713 5011
 \nUnited States: +1 (312) 757-3119\n\nAccess Code: 645-215-9
 81\n\nAgenda: \n	Status on TAs for &ldquo\;parser&rdquo\; im
 plementations\, Github logistics\,  evaluation of remaining 
 work.\n	What is the highest priority for TOSCA testing? (hig
 hest return for TOSCA users?) What conformance targets are m
 ost important in the short-mid term? &ldquo\;orchestrator&rd
 quo\; ? parser?\n	Can we identify some feature sets -  confo
 rmance  profiles?\n	TA design & practical aspects: should we
  assume a representative set of predefined\, minimal &ldquo\
 ;service templates&rdquo\; as basis for testing? Or should w
 e be able to use any template during testing?\n\nGroup: OASI
 S Topology and Orchestration Specification for Cloud Applica
 tions (TOSCA) TC\nCreator: Mr Jacques Durand
URL:https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=45000
UID:https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=45000
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT00H15M00S
END:VALARM
END:VEVENT
END:VCALENDAR