Wednesday, 2018-11-21

aspiershi all, the first ever self-healing IRC meeting is in this channel less than 9 hours from now! 9am UTC http://eavesdrop.openstack.org/#Self-healing_SIG_Meeting00:18
aspiersbeekhof: you might even be able to attend :)00:19
aspiersand then there's one later at 5pm UTC00:19
beekhofaspiers: :)00:31
beekhofi might be at a town fire meeting, but otherwise i'll show my face00:31
aspiersok00:31
*** Xiangyu has joined #openstack-self-healing05:02
*** Xiangyu has quit IRC05:04
*** Xiangyu has joined #openstack-self-healing05:05
*** Xiangyu has quit IRC05:41
*** Xiangyu has joined #openstack-self-healing05:42
*** d0ugal has quit IRC06:05
*** ifat_afek has joined #openstack-self-healing06:53
*** Xiangyu has quit IRC08:08
*** Xiangyu has joined #openstack-self-healing08:11
*** XiangyuLi has joined #openstack-self-healing08:26
*** Xiangyu has quit IRC08:30
*** XiangyuLi has quit IRC08:49
*** Xiangyu has joined #openstack-self-healing08:50
*** Xiangyu has quit IRC08:56
*** Xiangyu has joined #openstack-self-healing08:58
aspiershi all09:00
aspierswho's around today?09:00
ifat_afekHi :-)09:00
aspiershi ifat_afek!09:00
tojuvoneHi Adam, Ifat09:01
aspiershi Tomi :)09:01
aspiersI wonder if we have anyone else - the IRC meeting review only got merged yesterday09:01
aspiersso I expect most people didn't notice yet09:02
XiangyuHi Adam, I'm Xiangyu Li from China Mobile.09:02
ifat_afekDid you announce it on the mailing list? or did you discuss it in Berlin?09:02
aspiers#startmeeting self-healing09:02
openstackMeeting started Wed Nov 21 09:02:47 2018 UTC and is due to finish in 60 minutes.  The chair is aspiers. Information about MeetBot at http://wiki.debian.org/MeetBot.09:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:02
*** openstack changes topic to " (Meeting topic: self-healing)"09:02
openstackThe meeting name has been set to 'self_healing'09:02
*** witek has joined #openstack-self-healing09:02
aspiersWell it looks like we have critical mass for the first ever meeting :)09:03
* witek waves09:03
aspiersifat_afek: yes, we discussed the meeting in Berlin. No, I meant to announce it on the list in the last day or two but I had too many things going on in my head so I forgot ;-/09:04
aspiershi witek!09:04
aspiersand hi Xiangyu! really glad you could make it09:04
ifat_afekaspiers: ok, thanks09:04
aspiers#action aspiers to announce the meeting times on the list09:04
aspiers#link http://eavesdrop.openstack.org/#Self-healing_SIG_Meeting09:05
aspiers#topic Berlin recap09:05
*** openstack changes topic to "Berlin recap (Meeting topic: self-healing)"09:05
aspiersOK, let's do a quick recap of the two Berlin sessions09:05
aspiers#link https://etherpad.openstack.org/p/berlin-self-healing-sig-brainstorm09:06
aspiersThat's the etherpad we used for both sessions09:06
aspiersThe first session was a BoF, and the second was the Forum's official working group session for the SIG09:06
aspiersWe tried to play the agenda for both by ear, depending on who was there and what they were interested in09:07
aspiers#action aspiers to send a recap of the Berlin sessions to the list (and maybe blog about it too)09:08
aspiersWe had good attendance and some nice discussions09:08
aspiersAlso there seems to still be quite a bit of interest in compute node HA09:08
aspiersThere was one new interesting use case raised around memory leaks in OVS09:09
aspiersI think we had a volunteer to submit a use case to the repo for that, but I forgot to take a name09:10
aspiers#action try to find out who raised memory leak use case09:10
*** d0ugal has joined #openstack-self-healing09:11
aspiersI think we can talk about compute node HA as a separate topic in the next few minutes09:11
aspiersbut first, any questions about the items in the etherpad?09:11
aspiersespecially from people who weren't there09:11
ifat_afekUnfortunately I couldn’t attend this summit, seems like you had interesting discussions09:11
ifat_afekI’m going over them now...09:11
aspiersYeah it was good, people came and went from the two sessions so I think we must have had more than 40 people in total09:12
tojuvoneyes, we had plenty of people while room was hard to reach09:13
aspiersright, the room was the furthest away in the whole conference ;-)09:13
aspiersifat_afek: there were questions about what to use for notification09:13
ifat_afekWhat kind of notification?09:13
aspierssorry, I mean monitoring ;-)09:14
aspiersbrain is not working yet09:14
ifat_afekOh :-)09:14
aspiersI said that I thought the SIG should not be opinionated about that, but only assist in sharing knowledge09:14
aspiersabout what is possible, or what is being worked on09:14
ifat_afekI’m familiar with Zabbix and a bit Prometheus. I’m not sure if the SIG should recommend monitors09:14
aspierssince some operators want to use monasca / zabbix etc.09:15
ifat_afekI would expect a general architecture that allows using different monitors09:15
aspiersexactly09:15
ifat_afekOf course, Monasca as well09:15
aspiersright09:15
witekMonasca gives great monitoring possibilities, which should also be listed with other options09:15
ifat_afekRight09:15
aspiers#action aspiers to update the SIG scope on the wiki home page to be clear about not being opinionated about which components to use09:16
witekMonasca having support for Prometheus, so Prometheus metrics can be scraped and stored in Monasca backend09:16
ifat_afekSounds good09:16
aspiers#topic compute HA09:16
*** openstack changes topic to "compute HA (Meeting topic: self-healing)"09:16
aspierssince we have Xiangyu here, let's talk about compute HA09:17
aspiersthere were two presentations on new solutions for compute HA09:17
aspiersone from China Mobile09:17
aspierson Guardian09:17
aspiersand I am trying to remember the other one :)09:18
aspiersit's in my notes somewhere ...09:18
aspiersah, found it09:18
aspiershttps://www.openstack.org/summit/berlin-2018/summit-schedule/events/22100/a-better-vm-ha-solution-split-brain-solving-and-host-network-fault-awareness09:18
aspierssampath and I attended both talks and talked to the presenters afterwards09:18
aspiersto ask if they would like to collaborate with upstream, especially with masakari09:19
aspierssince masakari is already an official project doing compute HA09:19
aspiersboth of the new solutions have some interesting features which masakari does not have, but they also overlap a lot too09:19
aspiersIIUC currently neither are open source yet, but there are plans to open source Guardian I think09:20
ifat_afekWere they aware of Masakari?09:20
aspiersI think so09:20
aspiersthe Fiberhome solution decided to avoid existing solutions, but the reasons they gave did not make sense to me09:21
aspiersbut maybe I was missing something09:21
*** d0ugal has quit IRC09:22
aspiersXiangyu: would you like to say anything about Guardian?09:22
aspierse.g. possibility to collaborate upstream?09:22
Xiangyuyes, we would like to share our gains.09:23
aspiersBTW we heard from Chinese contributors in a separate session (TC community outreach) that IRC meetings are sometimes difficult for Chinese contributors, so I'm really glad to see you here :)09:23
aspiersXiangyu: I see you are on #openstack-masakari too, so we can discuss there also09:24
XiangyuGuardian is also focus on VM HA now, and has some special features.09:25
aspiersyes it has some nice features, so it would be great to converge to one solution upstream09:25
aspiersmaybe we can set up a separate meeting with samP about this?09:25
XiangyuI'm also very glad to join in this meeting.09:25
*** d0ugal has joined #openstack-self-healing09:26
Xiangyuyes, of course.09:26
aspiersOK, great! I am always available in IRC to discuss, since I know masakari reasonably well09:26
aspiersand I know samP is keen to discuss too09:27
aspiersOK, I guess we don't need to go into the details of that now09:27
aspiers#topic raising awareness of the SIG09:27
*** openstack changes topic to "raising awareness of the SIG (Meeting topic: self-healing)"09:27
aspiersI raised this topic in a seperate Forum session https://etherpad.openstack.org/p/expose-sigs-and-wgs09:27
*** bogdando has joined #openstack-self-healing09:28
aspiersactually, Rico Lin raised it09:28
aspiersbut there are a few different aspects:09:28
aspiers1. collecting feedback from users/ops09:28
aspiers2. coordinating work across projects09:29
aspiers3. finding developers09:29
aspiersself-healing SIG currently needs help most with 1.09:29
aspiersI think 2. is already working fine via Storyboard and we have a specs template too (not used yet, but hopefully soon!)09:29
ifat_afekSorry to interrupt, I need to leave for another meeting… I plan to join the second meeting today09:30
aspiersIIRC the session agreed that 3. is not a good idea. If the devs are available, they are available. If not, there is no magic solution to find them09:30
aspiersno problem ifat_afek, thanks a lot for coming and see you later!09:30
aspiersif anyone has ideas on how to increase engagement with ops/users, it would be really helpful to hear them09:31
aspierseither now or later on IRC or the mailing list09:31
witekad. 2 do we have the link to specs page on wiki?09:31
aspiersgood question09:32
aspierswell, there is a link yes09:32
aspierssecond link under https://wiki.openstack.org/wiki/Self-healing_SIG#Community_Infrastructure_.2F_Resources09:32
witekgot it09:32
aspiersbut it's called "Official SIG documentation" so maybe it's not obvious enough09:33
aspiers#action aspiers to clarify docs link on wiki page09:33
aspiers#action aspiers to update meeting info in wiki page09:33
aspiersjust noticed that too ;-)09:33
witekad. 1 should we advertise StoryBoard as the place to collect user stories from ops?09:34
witekis it the right tool?09:34
aspiersI'm not sure09:34
aspiersit's a lot better than nothing09:34
witek:)09:34
aspierspersonally I think I would prefer them to first discuss on IRC or mailing list09:34
aspiersand then submit to the git repo09:34
aspiersbut Storyboard could be used to track it too09:35
aspiersRico did originally suggest this09:35
aspiersso we should probably try it and see how it goes09:35
witekas of now, git repo holds implemented use cases and has a place for design documents09:36
aspiers#action aspiers to put another call for user stories out to the list09:36
aspiersright09:36
aspiersbut the git repo can hold unimplemented use cases too :)09:36
aspiersthat was always my intention09:36
witekIRC or mailing list is good, proposing a spec is more effort and could be a barrier I think09:36
aspiersalthough I'm not sure if I made that clear09:37
aspiersI agree, spec is more about technical details of implementation09:37
aspiersspec would only happen once there are developers on board09:37
aspiersso maybe we need a "How To Contribute" document09:37
aspiersto make this clear09:37
tojuvoneMaybe some short instructions to write a story if not irc first09:38
aspiersyes09:38
aspiersah09:38
tojuvoneit is easy to write09:38
aspiersI just remembered09:38
aspiershttps://docs.openstack.org/self-healing-sig/latest/meta/CONTRIBUTING.html09:38
aspiersI wrote this :-)09:38
aspiers#action improve CONTRIBUTING.rst to explain how / when to propose stories / specs09:39
aspiers#action link to CONTRIBUTING.html from wiki page09:39
aspiersOK09:40
aspierstojuvone: do you want to discuss Fenix a bit?09:40
tojuvonewell, ifat_afek is not present09:40
tojuvonemaybe just some words09:40
aspiersah, OK we can discuss later today too09:41
aspiers#topic Fenix (new project)09:41
*** openstack changes topic to "Fenix (new project) (Meeting topic: self-healing)"09:41
tojuvoneSo, there is new project: Fenix - Rolling maintenance, upgrade and scaling09:41
aspiers#link https://wiki.openstack.org/wiki/Fenix09:41
tojuvoneI introdicid a bit in session09:41
tojuvoneand one can find link to it from the etherpad09:41
tojuvoneread and reach to know more09:42
aspiersdo you have an IRC channel?09:42
tojuvonejust the bit for any self-healing project like Vitrage and Masakari09:42
tojuvone#link https://fenix.readthedocs.io/en/latest/notification/notifications.html#admin09:42
tojuvoneSo as Fenix does maintenance there is a notification telling host is in maintenance or not09:43
tojuvoneso this awareness might be good for those projects09:43
tojuvoneYes, irc is: #openstack-fenix09:43
* aspiers joins :)09:43
aspiersOK cool09:44
tojuvoneMaybe not more for here now09:44
aspierslet's discuss again with ifat_afek at the meeting later today09:44
aspiersthanks tojuvone :)09:44
aspiers#topic AOB (Any Other Business)09:44
*** openstack changes topic to "AOB (Any Other Business) (Meeting topic: self-healing)"09:44
aspiersdoes anyone else want to bring up any other topics?09:44
aspierswitek: anything from you?09:45
witekperhaps short update from previous virtual Vitrage PTG09:45
aspiersoh that would be great!09:45
witekI have joined to discuss Monasca - Vitrage integration09:45
aspiersvery nice :)09:46
witekwe've created three stories in StoryBoard for this09:46
aspiersthis was one of the big gaps in Vitrage IIUC09:46
witekhttps://storyboard.openstack.org/#!/story/200406409:46
witekunfortunately we don't have anyone who could work on this now :(09:47
aspiersah :/09:47
witeklooking for developers09:47
aspierswell, a plan is a good start anyway09:47
aspiersmaybe this SIG can help find developers09:47
witekthat's our hope, too09:48
aspiersI have added the link in line 74 of https://etherpad.openstack.org/p/self-healing-project-integrations09:48
witekthanks09:48
aspiersI would love to work on that, but won't be able to any time soon :-/09:48
aspiersmaybe in the future09:48
aspierscan you share a link to the virtual PTG?09:49
witekthe work item seems pretty well defined, so it should be well suited for new developers09:49
aspiersnice09:49
witekalso, we're willing to help09:49
witekI'd have to dig for the PTG link09:50
aspiersI think it's https://etherpad.openstack.org/p/vitrage-ptg-queens09:50
aspiersno09:50
aspiersthat's old09:50
aspiershttps://etherpad.openstack.org/p/vitrage-stein-ptg09:51
aspiersthat one, right?09:51
witekyes, thanks09:52
aspierscool09:52
aspiersOK, anything else anyone wants to mention?09:52
aspiersI think we are pretty much done09:52
tojuvonenothing from my side09:53
aspiersof course anyone is very welcome to also join the Americas/EMEA session in ~7 hours from now09:53
aspiershopefully ekcs will be joining then too09:53
aspierssince I might have to drop early from that one :-o09:53
aspiersand of course anyone is free to chat in this channel at any other times too09:54
aspiersthanks a lot everyone and bye for now!09:54
aspierso/09:54
witekthanks everyone, bye09:54
tojuvonetnaks, byez09:54
aspiers#endmeeting09:54
*** openstack changes topic to "https://wiki.openstack.org/wiki/Self_healing_SIG | https://storyboard.openstack.org/#!/project/917"09:54
openstackMeeting ended Wed Nov 21 09:54:56 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/self_healing/2018/self_healing.2018-11-21-09.02.html09:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/self_healing/2018/self_healing.2018-11-21-09.02.txt09:54
openstackLog:            http://eavesdrop.openstack.org/meetings/self_healing/2018/self_healing.2018-11-21-09.02.log.html09:55
*** Xiangyu has quit IRC10:00
*** ifat_afek has quit IRC10:58
*** ricolin has joined #openstack-self-healing10:59
*** mvkr has quit IRC11:03
*** mvkr has joined #openstack-self-healing11:43
*** mugsie has joined #openstack-self-healing11:50
*** ifat_afek has joined #openstack-self-healing12:01
*** ifat_afek has quit IRC13:30
*** ifat_afek has joined #openstack-self-healing14:09
*** ricolin has quit IRC14:16
*** witek has quit IRC14:21
*** witek has joined #openstack-self-healing14:40
aspierso/17:01
ifat_afekHi17:02
ifat_afekI got confused about the meeting hour… and I need to leave in 10 minutes :-(17:03
aspiersthat's fine17:05
aspiersI managed to double-book myself anyway :-o17:05
aspiersso I will try to multi-task17:06
aspiersifat_afek: unless you were just planning to listen in?17:06
aspiersbut if you have anything you wanna discuss, we can chat quickly17:06
*** bogdando has quit IRC17:09
ifat_afekaspiers: I can’t listen either sorry…. leaving now17:12
aspiersno problem!17:12
aspiersOK, I guess we don't have critical mass for today :) That actually solves my double-booking mistake anyway ;)17:12
ifat_afekSee you in two weeks (unless we’ll have some email discussions :-))17:12
aspiersSounds good, thanks!17:12
ifat_afekHappy to help ;-)17:12
aspiershaha17:12
aspierssee ya ;-)17:13
*** ifat_afek has quit IRC17:13
tojuvoneHi, also here17:15
*** mvkr has quit IRC19:40
*** mvkr has joined #openstack-self-healing20:35

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!