Wednesday, 2019-01-02

*** sapd1 has joined #openstack-self-healing02:11
*** ifat_afek has joined #openstack-self-healing06:53
*** sapd1 has quit IRC08:31
*** sapd1 has joined #openstack-self-healing08:47
*** bogdando has joined #openstack-self-healing08:48
aspiersHappy New Year everyone :)09:00
aspiersI guess most people are still on vacation?09:00
ifat_afekHappy New Year :-)09:00
aspiersahah :)09:00
aspiersifat_afek: anything you want to discuss / share today?09:01
ifat_afekNot really, since most people are on vacation there is not much progress regarding Monasca09:01
aspiersThat's what I expected :)09:01
ifat_afekI wrote a spec about the mapping of Monasca dimensions to a Vitrage resource, waiting for feedbacks09:01
aspiersYeah, I saw it09:01
aspiersHaven't managed to review yet though09:01
ifat_afekIt is currently on hold, until people review and comment09:02
ifat_afekSo I have no updates09:02
aspiersI expect it will help my understanding of the topic a lot, although I'm not expecting to be able to contribute a huge amount :)09:02
ifat_afekAren’t you on vacation?09:03
aspiersNope09:03
aspiersI usually save most of mine for the summer09:04
ifat_afekWell… I guess there is no meeting today? ;-)09:07
aspiersI guess there is not much point09:09
ifat_afekOk, so see you next meeting09:09
aspiersSorry, should have said that explicitly ;-)09:09
aspiersOK, thanks!09:09
*** bogdando has quit IRC09:10
*** bogdando has joined #openstack-self-healing09:10
*** sapd1 has quit IRC09:29
*** sapd1 has joined #openstack-self-healing10:13
*** ifat_afek has quit IRC10:18
*** witek has quit IRC10:25
*** bogdando has quit IRC10:33
*** ifat_afek has joined #openstack-self-healing11:36
*** bogdando has joined #openstack-self-healing12:46
*** ifat_afek has quit IRC13:15
*** ifat_afek has joined #openstack-self-healing13:17
*** ifat_afek has quit IRC13:20
*** bogdando has quit IRC15:59
*** sapd1 has quit IRC16:06
*** sapd1 has joined #openstack-self-healing16:38
*** ekcs has joined #openstack-self-healing16:53
aspierswhoops, lost track of time17:03
aspiersAnyone around know who wants to talk about self-healing?17:04
aspiersNot a problem if we don't have critical mass, I guess most people are still on vacation17:04
ekcshi aspiers ! I’m here17:04
aspiershi ekcs!17:04
aspiersHappy New Year!17:04
ekcshappy new year!17:04
aspiers:)17:04
aspiersI guess we could have a quick meeting to check the backlog?17:05
ekcssounds good!17:05
aspiersI haven't looked at it since before Xmas17:05
aspiers#startmeeting self-healing17:05
openstackMeeting started Wed Jan  2 17:05:39 2019 UTC and is due to finish in 60 minutes.  The chair is aspiers. Information about MeetBot at http://wiki.debian.org/MeetBot.17:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:05
*** openstack changes topic to " (Meeting topic: self-healing)"17:05
openstackThe meeting name has been set to 'self_healing'17:05
aspiers#topic backlog review17:05
*** openstack changes topic to "backlog review (Meeting topic: self-healing)"17:05
aspiersBTW I noticed that storyboard has nice permalinks now17:06
aspiers#link https://storyboard.openstack.org/#!/project/openstack/self-healing-sig for SIG backlog17:06
aspiers#link http://eavesdrop.openstack.org/meetings/self_healing/2018/self_healing.2018-12-19-09.02.html last meeting17:06
aspierswe didn't have a meeting this morning, but I had a quick chat with ifat_afek17:07
aspiersin Dec she already delivered on the action from last meeting about submitting a spec17:07
aspiers#link https://review.openstack.org/#/c/627180/17:07
aspiersI think that's all you missed recently17:08
ekcsoh got it that’s great17:08
ekcsvery helpful work to document how to identify with monasca alarms based on dimensions.17:09
aspiersyeah17:09
ekcswill be useful even beyond vitrage.17:09
aspiersI need to get my head around that, it's new stuff for me17:09
aspiersjust looking at what else is ongoing17:10
aspiersdamn, I still didn't send out a summary of Berlin17:10
ekcsaspiers: I see you’ve signed up for quite a few SIG admin things. I can off load some if you’d like just let me know.17:10
aspiersthat would be great :)17:11
aspiersI feel like we have to keep hammering away at https://storyboard.openstack.org/#!/story/200453717:11
aspiersIt's gonna take regular publicity from multiple angles17:11
aspiersmaybe you could take 28285 or 28309?17:12
ekcsgreat.17:13
ekcsI can take both.17:13
ekcschanged on board.17:13
aspiersawesome thanks!17:15
aspiersI guess it should be easy to finish https://storyboard.openstack.org/#!/story/200453617:15
aspiersI can do that now17:15
ekcsof back to f2f events: if you already have events in mind to look into pls let me know so I can make sure I don’t overlook them in my search.17:16
aspiersI don't have any in mind17:16
aspiersnot sure where to get visibility of that17:16
aspiersmaybe we can reach out to the UC?17:17
aspiersI guess they will know about all the OpenStack Days and Meetups17:17
ekcsok great I’ll dig around and update.17:17
aspiersI'm gonna ask on #openstack-uc now17:17
ekcsok17:17
aspiersOK done17:18
aspiers#action clarify on wiki page where to find docs / storyboard17:18
aspiershrm forgot to include action owner17:18
aspiers#action aspiers to ask the UC about how to find out upcoming events17:20
aspiersregarding https://storyboard.openstack.org/#!/story/2004535 I emailed the guy who proposed it but never heard back17:20
aspiersso I guess it's up to us to submit this use case (task 28279)17:20
ekcsI see317:21
aspiersI can try to find time for that, unless it's particularly appealing to you17:21
ekcsI am interested. But I’m quite unfamiliar with that territory.17:22
aspiersNo less familiar than me I guess ;-)17:22
aspiersIt's just a matter of taking the template and replacing the boilerplate with the info about a memory leak scenario17:22
ekcscool I’ll take a first crack at it.17:23
aspierscool thanks!17:23
aspiersthe example he gave was a leak in ovs-vswitchd17:23
aspiershttps://etherpad.openstack.org/p/berlin-self-healing-sig-brainstorm line 5317:23
aspiersbut it could be any service really17:23
ekcsI’ll need to read up on current practices on how to even detect memory leaks over time.17:24
aspiersyeah17:24
aspiersthe use case doc doesn't necessarily have to go into details, at least not at first17:25
aspiersI think it's OK if it's initially quite vague17:25
ekcsok got it.17:25
aspierswe can flesh it out later, or add details in a separate spec if coding is required17:25
aspiersmaybe it can all be done simply using Vitrage + Mistral + $monitoring_component17:26
aspiersit would still be nice just to have the idea documented, to get people's creative juices flowing :)17:26
ekcsperfect.17:26
aspiersI think we can abandon https://storyboard.openstack.org/#!/story/200342317:27
aspiersbased on discussion in Berlin, or maybe it was Denver - I can't remember :)17:27
ekcsyes that makes sense.17:27
ekcsdenver.17:27
aspiersfungi suggested using survey.openstack.org instead17:27
aspiersand we already have a task for that17:27
aspiersOK cool, I'll add a comment and close it17:28
aspiers#action find the Denver etherpad which covered the User Survey discussion, and close the corresponding story17:29
aspiersdoh, forgot to assign myself again17:29
aspiersI guess we don't need to discuss https://storyboard.openstack.org/#!/story/200268417:30
aspierssince that's already in Ifat's very capable hands :)17:30
aspiersnext one is https://storyboard.openstack.org/#!/story/200212917:30
aspiersugh, I have been the bottleneck on that forever :-(17:31
aspiersneed to resurrect that doodle poll17:31
aspiersdo you think my idea of a kickoff video conference still makes sense? I feel like the key to success here would be to get SUSE + Red Hat + one or two other companies to all donate ~0.5 engineers to the cause17:33
aspiersto form a virtual team17:33
aspierswithout a bit of dedicated resource it seems unlikely it will happen any time soon, since it's not trivial17:33
aspierssampath would definitely join the effort17:33
aspierssince he's probably the only one working on it right now17:34
ekcshmm. that makes sense.17:35
aspiersmaybe rather than spend the next 25 mins discussing the rest of the backlog, we could wrap up this meeting early and I could actually see how many things I can close off in 25 mins ;-)17:35
aspiersfor example https://storyboard.openstack.org/#!/story/2001628 should be low-hanging fruit too17:35
ekcsnot sure how best to take the initial approach tho.17:35
*** mvkr has quit IRC17:35
aspierswell, we can at least try to get enough interested people in the same conf call17:36
ekcsgreat.17:36
aspiersif it works, great - if not, we tried :)17:36
ekcsright.17:36
aspiersalright17:36
aspiersanything else you wanna raise right now?17:36
ekcsnothing on my side at the moment =)17:37
aspiersOK cool17:37
aspiersI'll be around on this channel anyway17:37
aspiersthanks!17:37
aspiers#endmeeting17:37
*** openstack changes topic to "https://wiki.openstack.org/wiki/Self_healing_SIG | https://storyboard.openstack.org/#!/project/openstack/self-healing-sig"17:37
openstackMeeting ended Wed Jan  2 17:37:36 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/self_healing/2019/self_healing.2019-01-02-17.05.html17:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/self_healing/2019/self_healing.2019-01-02-17.05.txt17:37
openstackLog:            http://eavesdrop.openstack.org/meetings/self_healing/2019/self_healing.2019-01-02-17.05.log.html17:37
ekcsthanks later then!17:37
*** ekcs has quit IRC17:40
*** ekcs has joined #openstack-self-healing18:36
*** mvkr has joined #openstack-self-healing22:23

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