[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Modified: TOSCA Monitoring ad hoc group
|
Event Title: TOSCA Monitoring ad hoc group Date: Monday, 04 April 2016, 12:00pm to 01:00pm EDT Description Hallo monitorers,
RSVP Agenda Capability for monitoring and solve some doubts like: How the express the expected behaviour is the orchestrator is not capable to satisfy monitoring? Is this needed to be inside the capability of each single node or we need something at service level? Owner: Mr. Luca Gioppo 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. |
Attachment:
ical_41579.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:20160404T092641Z
DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20160404T120000
DTEND;VALUE=DATE-TIME;TZID=America/New_York:20160404T130000
SEQUENCE:6
SUMMARY:TOSCA Monitoring ad hoc group
LAST-MODIFIED:20160404T092641Z
ORGANIZER:workgroup_mailer@lists.oasis-open.org
DESCRIPTION:Hallo monitorers\,\nToday we will have the call here is the
info for the meeting for today and the usual link to the gdo
c.\nThe task for today will be working on the use cases.\nGo
al is agreeing on the Capability for monitoring and giving a
nswers to some points\nLuca and Saji\n\n \nhttps://docs.goog
le.com/document/d/1opZu-dJT6ANS-NKrmeyIOHm5sbTom03TqtfV7gWOY
b0/edit\n>\; \n>\; \n>\; \n>\; [tosca] TOSCA
Monitoring ad hoc group\n>\; >\; \n>\; >\; Ever
y Monday\, from Monday\, January 25\, 2016\, to no end date\
n>\; >\; \n>\; >\; 10:30 pm | India Time (Mum
bai\, GMT+05:30) | 1 hr 30 mins\n>\; >\; \n>\; &
gt\; \n>\; >\; \n>\; >\; \n>\; >\; \n>\;
>\; Join WebEx meeting <\;\n>\; >\; https://wi
procon.webex.com/wiprocon/j.php?MTID=me7b922781943d23ac1bc4f
430e1d9e69>\;\n>\; >\; \n>\; >\; \n>\; >
\; Meeting number:\n>\; >\; \n>\; >\; 577 770
466\n>\; >\; \n>\; >\; Meeting password:\n>\;
>\; \n>\; >\; wipro1234\n>\; >\; \n>\;
>\; \n>\; >\; \n>\; >\; \n>\; >\; \n>
\; >\; Join by phone\n>\; >\; \n>\; >\; Ca
ll-in toll-free number: 180030104185 (India)\n>\; >\;
\n>\; >\; Call-in number: +91-08033572664 (India)\n
>\; >\; Call-in 954 514 9085 (USA)\n>\; >\; \n&
gt\; >\; Show global numbers<\;\n>\; >\; https:
//www.tcconline.com/offSite/OffSiteController.jpf?cc=6742830
703>\;\n>\; >\; \n>\; >\; Conference Code: 67
4 283 0703\n>\; >\; \n>\; >\; \n>\; >\; \n
>\; >\; \n>\; >\; \n>\; >\; Add this meet
ing<\;\n>\; >\; https://wiprocon.webex.com/wiprocon/
j.php?MTID=m25a2b2dd887598b5315909f08b07da80>\;\n>\; &
gt\; to your calendar. (Cannot add from mobile devices.)\n&g
t\; >\; \n>\; >\; \n>\; >\; \n>\; >\;
\n>\; >\; \n>\; >\; Can'\;t join the meeting
? Contact support.<\;\n>\; >\; https://wiprocon.webe
x.com/wiprocon/mc>\;\n>\; >\; \n>\; >\; \n>\
; >\; \n>\; >\; \n>\; >\; \n>\; >\; I
MPORTANT NOTICE: Please note that this WebEx service allows
audio and\n>\; >\; other information sent during the s
ession to be recorded\, which may be\n>\; >\; discover
able in a legal matter. By joining this session\, you automa
tically\n>\; >\; consent to such recordings. If you do
not consent to being recorded\,\n>\; >\; discuss your
concerns with the host or do not join the session.\n>\;
>\; \n>\; >\; \n\n\n https://docs.google.com/docume
nt/d/1opZu-dJT6ANS-NKrmeyIOHm5sbTom03TqtfV7gWOYb0/edit\n\nAg
enda: Capability for monitoring and solve some doubts like:\
n\nHow the express the expected behaviour is the orchestrato
r is not capable to satisfy monitoring?\n\nIs this needed to
be inside the capability of each single node or we need som
ething at service level?\nGroup: OASIS Topology and Orchestr
ation Specification for Cloud Applications (TOSCA) TC\nCreat
or: Mr. Luca Gioppo
URL:https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=41579
UID:https://www.oasis-open.org/apps/org/workgroup/tosca/event.php?event_id=41579
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]