<html xmlns="http://www.w3.org/1999/xhtml" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office"><head><!--[if gte mso 9]><xml><o:OfficeDocumentSettings><o:AllowPNG/><o:PixelsPerInch>96</o:PixelsPerInch></o:OfficeDocumentSettings></xml><![endif]--></head><body>
<!--[if gte mso 9]><xml><o:OfficeDocumentSettings><o:AllowPNG/><o:PixelsPerInch>96</o:PixelsPerInch></o:OfficeDocumentSettings></xml><![endif]-->
<!--[if gte mso 9]><xml><o:OfficeDocumentSettings><o:AllowPNG/><o:PixelsPerInch>96</o:PixelsPerInch></o:OfficeDocumentSettings></xml><![endif]-->
<!--[if gte mso 9]><xml><o:OfficeDocumentSettings><o:AllowPNG/><o:PixelsPerInch>96</o:PixelsPerInch></o:OfficeDocumentSettings></xml><![endif]-->
<!--[if gte mso 9]><xml><o:OfficeDocumentSettings><o:AllowPNG/><o:PixelsPerInch>96</o:PixelsPerInch></o:OfficeDocumentSettings></xml><![endif]-->
<!--[if gte mso 9]><xml><o:OfficeDocumentSettings><o:AllowPNG/><o:PixelsPerInch>96</o:PixelsPerInch></o:OfficeDocumentSettings></xml><![endif]-->
<!--[if gte mso 9]><xml><o:OfficeDocumentSettings><o:AllowPNG/><o:PixelsPerInch>96</o:PixelsPerInch></o:OfficeDocumentSettings></xml><![endif]-->
Hi Adam,<div><br></div><div>Two other sesdion proposals for Vancouver that are related to self healing:</div><div><br></div><div><br></div><div><h3 data-reactid=".0.1.2.0.$20964.0.0.2.2.0.0.0.1" style="box-sizing: border-box; line-height: 1.1; margin-top: 5px; margin-bottom: 10px;"><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0); font-weight: normal;">Proactive Root Cause Analysis with Vitrage, Kubernetes, Zabbix and Prometheus:</span></h3></div><div></div><div><div> <a rel="nofollow" target="_blank" href="https://www.openstack.org/summit/vancouver-2018/vote-for-speakers/#/20964" style="text-decoration: underline; -webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">https://www.openstack.org/summit/vancouver-2018/vote-for-speakers/#/20964</a></div><div><br></div><div>Closing the loop: VNF end-to-end failure detection and auto healing:</div><div><p class="yiv5295450144MsoNormal"><a rel="nofollow" target="_blank" href="https://www.openstack.org/summit/vancouver-2018/vote-for-speakers/#/20839" style="text-decoration: underline; -webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">https://www.openstack.org/summit/vancouver-2018/vote-for-speakers/#/20839</a></p><p class="yiv5295450144MsoNormal"><br></p><p class="yiv5295450144MsoNormal"><span style="-webkit-text-size-adjust: auto;">Thanks,</span></p><p class="yiv5295450144MsoNormal">Ifat</p><div><br></div></div><div><br></div><br><br><br><p class="yahoo-quoted-begin" style="font-size: 15px; color: #715FFA; padding-top: 15px; margin-top: 0">On Friday, February 23, 2018, 10:59 AM, Bedyk, Witold <witold.bedyk@est.fujitsu.com> wrote:</p><blockquote class="iosymail"><div dir="ltr">Hi Adam,<br></div><div dir="ltr"><br></div><div dir="ltr">related to the Doctor collaboration which you've added to the agenda, there is a presentation proposal for Vancouver.<br></div><div dir="ltr"><br></div><div dir="ltr">Automated NFV Fault Management: Integrated Solution of Monasca+Congress+Tacker in Doctor Framework<br></div><div dir="ltr"><a href="https://www.openstack.org/summit/vancouver-2018/vote-for-speakers/#/21356" target="_blank">https://www.openstack.org/summit/vancouver-2018/vote-for-speakers/#/21356</a><br></div><div dir="ltr"><br></div><div dir="ltr">Cheers<br></div><div dir="ltr">Witek<br></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">> -----Original Message-----<br></div><div dir="ltr">> From: Adam Spiers [mailto:<a ymailto="mailto:aspiers@suse.com" href="mailto:aspiers@suse.com">aspiers@suse.com</a>]<br></div><div dir="ltr">> Sent: Donnerstag, 22. Februar 2018 22:30<br></div><div dir="ltr">> To: OpenStack SIGs list <<a ymailto="mailto:openstack-sigs@lists.openstack.org" href="mailto:openstack-sigs@lists.openstack.org">openstack-sigs@lists.openstack.org</a>>; openstack-<br></div><div dir="ltr">> dev mailing list <<a ymailto="mailto:openstack-dev@lists.openstack.org" href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>; openstack-operators<br></div><div dir="ltr">> mailing list <<a ymailto="mailto:openstack-operators@lists.openstack.org" href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>><br></div><div dir="ltr">> Subject: [Openstack-sigs] [self-healing][PTG] etherpad for PTG session on<br></div><div dir="ltr">> self-healing<br></div><div dir="ltr">> <br></div><div dir="ltr">> Hi all,<br></div><div dir="ltr">> <br></div><div dir="ltr">> Yushiro kindly created an etherpad for the self-healing SIG session at the<br></div><div dir="ltr">> Dublin PTG on Tuesday afternoon next week, and I've fleshed it out a bit:<br></div><div dir="ltr">> <br></div><div dir="ltr">> <a href="https://etherpad.openstack.org/p/self-healing-ptg-rocky" target="_blank">https://etherpad.openstack.org/p/self-healing-ptg-rocky</a><br></div><div dir="ltr">> <br></div><div dir="ltr">> Anyone with an interest in self-healing is of course very welcome to attend<br></div><div dir="ltr">> (or keep an eye on it remotely!) This SIG is still very young, so it's a great<br></div><div dir="ltr">> chance for you to shape the direction it takes :-) If you are able to attend,<br></div><div dir="ltr">> please add your name, and also feel free to add topics which you would like<br></div><div dir="ltr">> to see covered.<br></div><div dir="ltr">> <br></div><div dir="ltr">> It would be particularly helpful if operators could participate and share their<br></div><div dir="ltr">> experiences of what is or isn't (yet!) working with self-healing in OpenStack,<br></div><div dir="ltr">> so that those of us on the development side can aim to solve the right<br></div><div dir="ltr">> problems :-)<br></div><div dir="ltr">> <br></div><div dir="ltr">> Thanks, and see some of you in Dublin!<br></div><div dir="ltr">> <br></div><div dir="ltr">> Adam<br></div><div dir="ltr"><br></div><blockquote></blockquote></blockquote></div>
</body></html>