BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:Pacific Standard Time BEGIN:STANDARD DTSTART:16010101T020000 TZOFFSETFROM:-0700 TZOFFSETTO:-0800 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020000 TZOFFSETFROM:-0800 TZOFFSETTO:-0700 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT ORGANIZER;CN="Ranganath, Sunku":mailto:sunku.rangan...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech -discuss:mailto:opnfv-tech-discuss@lists.opnfv.org ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Muldoon, K illian":mailto:killian.muld...@intel.com DESCRIPTION;LANGUAGE=en-US:Agenda:\nKillian Muldoon\, from Intel\, would be presenting about on-going work in Kubernetes community about Telemetry Aw are Scheduling and Horizontal Pod Auto-scaler in relation to closed loop a utomation. He will presenting following use cases and corresponding demos. \nFeel free to join in.\n\nPower scheduling and scaling:\nSelf-healing and self-optimizing network infrastructures require a combination of fine-gra ined visibility and control of platform features to help ensure an optimum Quality of Service (QoS). One such automation use case is platform power monitoring and overload detection. This demo is built on container Bare Me tal Reference Architecture – a standardized Kubernetes deployment that e xposes platform features for increased and deterministic network performan ce. Platform telemetry insights are provided to detect a potential platfor m overload scenario when workloads are operating under compute intensive c onditions. Automatic scaling combined with intelligent scheduling is trigg ered when overloaded nodes are identified\, provisioning additional worklo ads and ensuring their placement on nodes with capacity for additional wor k.\n\nHealth Metrics for workload scheduling and rescheduling:\nThis is a closed loop platform automation resiliency demo that shows a mechanism to minimize service outage time through automation of scheduling and workload migration in Kubernetes. Using Intel® architecture platform specific met rics and events\, we can monitor the health of the platform and identify i ssues that may impact the end-user experience. By looking at the trend of these indicators we can decide to take specific pre-emptive action\, and r espond appropriately to minor and critical alerts on platform health.\n\n\ nWebex details\n\nJoin link: https://intel.webex.com/meet/sranga4\nID to J oin: 258 449 189\n\nThanks\nSunku\n\n UID:040000008200E00074C5B7101A82E00800000000E0A59C88C485D601000000000000000 0100000007E0F7E275E06984C8AEDCD5D9481AA87 SUMMARY;LANGUAGE=en-US:[CLA WG] Kubernetes based Closed Loops - Power & Pla tform Health DTSTART;TZID=Pacific Standard Time:20200924T060000 DTEND;TZID=Pacific Standard Time:20200924T070000 CLASS:PUBLIC PRIORITY:5 DTSTAMP:20200908T175135Z TRANSP:OPAQUE STATUS:CONFIRMED SEQUENCE:0 LOCATION;LANGUAGE=en-US:Webex X-MICROSOFT-CDO-APPT-SEQUENCE:0 X-MICROSOFT-CDO-OWNERAPPTID:1030264804 X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY X-MICROSOFT-CDO-ALLDAYEVENT:FALSE X-MICROSOFT-CDO-IMPORTANCE:1 X-MICROSOFT-CDO-INSTTYPE:0 X-MICROSOFT-DONOTFORWARDMEETING:FALSE X-MICROSOFT-DISALLOW-COUNTER:FALSE X-MICROSOFT-LOCATIONS:[ { "DisplayName" : "Webex"\, "LocationAnnotation" : ""\, "LocationSource" : 0\, "Unresolved" : false\, "LocationUri" : "" } ] BEGIN:VALARM DESCRIPTION:REMINDER TRIGGER;RELATED=START:-PT15M ACTION:DISPLAY END:VALARM END:VEVENT END:VCALENDAR
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group.
View/Reply Online (#24369): https://lists.opnfv.org/g/opnfv-tech-discuss/message/24369 Mute This Topic: https://lists.opnfv.org/mt/76714742/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
