Wednesday, 2018-12-05

*** witek has quit IRC02:00
*** witek has joined #openstack-self-healing02:00
openstackgerritVieri proposed openstack/ha-guide master: Change openstack-dev to openstack-discuss  https://review.openstack.org/62278604:11
*** ifat_afek has joined #openstack-self-healing06:55
*** pgaxatte1 has joined #openstack-self-healing08:02
*** pgaxatte has quit IRC08:02
*** pgaxatte1 has quit IRC08:02
*** pgaxatte has joined #openstack-self-healing08:02
*** bogdando has joined #openstack-self-healing08:18
witekgood morning09:02
ifat_afekHi :-)09:02
witekaspiers: are you around?09:03
ifat_afekwitek: since you are here, have a look09:09
ifat_afek#link https://review.openstack.org/#/c/622899/09:09
ifat_afekTrove contributors pushed a draft of Monasca datasource :-)09:10
witekfantastic!09:10
ifat_afekAnd here is the POC demo they showed in Berlin, in case you didn’t see it09:10
ifat_afek#link https://www.openstack.org/videos/berlin-2018/towards-production-grade-database-as-a-service-in-openstack09:10
witekno, I've missed that one09:11
witekhave you talked with them?09:11
ifat_afekYes (later, I didn’t attend the summit). I understood that they finished the POC but don’t have time to finish the datasource. I asked them to push what they have so hopefully one of us can go on with it09:12
ifat_afekI also invited them to join the SIG, but I’m not sure they will09:13
ifat_afekThey pushed the code about 5 min ago :-)09:13
witekadded myself to review as well09:14
aspiersifat_afek, witek: argh sorry guys09:29
aspiersthat's great news though09:31
witekno worries09:31
witekfunny, that we've just talked about Monasca datasource in Vitrage last time :)09:32
aspiersindeed :)09:32
ifat_afekI’m very happy that we’ll have this datasource. It’s really important09:32
ifat_afekI didn’t review it yet though, so I don’t have an estimation of the amount of work left09:32
aspiers#startmeeting self-healing09:33
openstackMeeting started Wed Dec  5 09:33:01 2018 UTC and is due to finish in 60 minutes.  The chair is aspiers. Information about MeetBot at http://wiki.debian.org/MeetBot.09:33
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:33
*** openstack changes topic to " (Meeting topic: self-healing)"09:33
openstackThe meeting name has been set to 'self_healing'09:33
aspierssince we're here I might as well officially record what we're talking about :)09:33
aspiersin case anyone checks for minutes09:33
aspiers#topic Monasca datasource in Vitrage09:33
*** openstack changes topic to "Monasca datasource in Vitrage (Meeting topic: self-healing)"09:33
aspiers<ifat_afek> Trove contributors pushed a draft of Monasca datasource :-)09:34
aspiers<ifat_afek> #link https://review.openstack.org/#/c/622899/09:34
aspiers<ifat_afek> And here is the POC demo they showed in Berlin, in case you didn’t see it09:34
aspiers<ifat_afek> #link https://www.openstack.org/videos/berlin-2018/towards-production-grade-database-as-a-service-in-openstack09:34
aspiers<witek> have you talked with them?09:35
aspiers<ifat_afek> Yes (later, I didn’t attend the summit). I understood that they finished the POC but don’t have time to finish the datasource. I asked them to push what they have so hopefully one of us can go on with it09:35
aspierslooks like we already have a story for this https://storyboard.openstack.org/#!/story/200406409:36
ifat_afekGreat, so we can update the commit message09:36
witekcorrect09:36
aspiersyup09:36
aspiersand it's already linked from https://etherpad.openstack.org/p/self-healing-project-integrations09:36
witek#link https://storyboard.openstack.org/#!/story/200406409:36
aspiers#topic actions from last meeting09:37
*** openstack changes topic to "actions from last meeting (Meeting topic: self-healing)"09:37
aspiersEric and I have been doing a little bit of work on actions from last meeting09:37
aspiersthe actions are in the minutes: http://eavesdrop.openstack.org/meetings/self_healing/2018/self_healing.2018-11-21-09.02.html09:37
aspiersI've submitted storyboard tasks for some of the actions09:38
aspiersothers were simple so I just did them09:38
aspiersekcs submitted https://review.openstack.org/#/c/620424/09:38
aspiersI think we can easily finish that off, maybe I'll do it later today09:39
aspiersnew stories:09:39
aspiershttps://storyboard.openstack.org/#!/story/2004537 (Encourage more participation in SIG)09:39
ifat_afekYou forgot #link09:40
aspiershttps://storyboard.openstack.org/#!/story/2004536 (Make it clearer how to contribute to the self-healing SIG)09:40
aspiersI don't think #link is needed09:40
aspiersIIRC the bot picks up all links09:40
aspiersmaybe I'm wrong09:40
ifat_afekThis is what I thought, I’ll check it09:40
aspiers#link https://storyboard.openstack.org/#!/story/2004537 (Encourage more participation in SIG)09:40
aspiers#link https://storyboard.openstack.org/#!/story/2004536 (Make it clearer how to contribute to the self-healing SIG)09:41
aspiersjust in case :)09:41
ifat_afekSo now we won’t be able to tell if it worked :-)09:41
witekI think it picks all the lines starting with the URL09:41
aspierswe'll see when I end the meeting ;-)09:41
ifat_afekOk, thanks09:41
witeknot ones with URL inside09:41
aspiersI doubt it has deduplication09:42
aspiersah yeah, maybe09:42
aspiershehe :)09:42
aspiers#link https://storyboard.openstack.org/#!/story/2004535 (Self-healing for memory leaks | StoryBoard)09:42
aspiersI think that's it09:42
aspiers#topic AOB (Any Other Business)09:42
*** openstack changes topic to "AOB (Any Other Business) (Meeting topic: self-healing)"09:42
aspiersI think that's all I had09:43
aspiersoh, progress with HA guide is slow but real :)09:43
aspiersanyone want to raise anything else?09:43
ifat_afekNothing on my side09:43
aspiersoh yeah, I just remembered09:43
aspiersthe health checking TC discussion09:44
aspiers#link http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000599.html09:44
aspiersjust started yesterday09:44
aspiersI hope my assumption was correct that this could be very useful for Vitrage09:44
ifat_afekI just noticed you sent it, I’ll go over the discussion09:45
aspierscool09:45
aspiersI updated https://storyboard.openstack.org/#!/story/2001439 (Drive health check APIs for OpenStack infrastructure) accordingly09:45
aspierswe can use this line to test the #-link behaviour ;-)09:45
ifat_afek:-)09:46
witek:)09:46
aspiersalright, I guess we can wrap it up here then09:46
aspierssorry I was late!09:47
witekthanks aspiers for updating StoryBoard09:47
ifat_afek+109:47
aspiersyw, thanks for turning up to the meeting ;-)09:47
witekit's easier to find AIs09:47
ifat_afekBTW, I won’t be able to attend the second meeting today09:47
aspiersno problem at all09:47
aspiersI don't expect anyone expect myself to attend both09:47
witeksame for me probably09:47
aspiers*anyone except :)09:47
aspiers#endmeeting09:48
*** openstack changes topic to "https://wiki.openstack.org/wiki/Self_healing_SIG | https://storyboard.openstack.org/#!/project/openstack/self-healing-sig"09:48
openstackMeeting ended Wed Dec  5 09:48:25 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/self_healing/2018/self_healing.2018-12-05-09.33.html09:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/self_healing/2018/self_healing.2018-12-05-09.33.txt09:48
openstackLog:            http://eavesdrop.openstack.org/meetings/self_healing/2018/self_healing.2018-12-05-09.33.log.html09:48
aspiersso witek was right :)09:48
aspierslinks are only picked up if they start the line or have #link09:49
ifat_afekGood to know09:49
aspiersyup09:49
aspiersI wonder if #link has any point at all09:49
*** witek has quit IRC09:50
*** ifat_afek has quit IRC10:06
*** witek has joined #openstack-self-healing10:10
openstackgerritMerged openstack/ha-guide master: Change openstack-dev to openstack-discuss  https://review.openstack.org/62278610:20
*** ifat_afek has joined #openstack-self-healing10:47
*** ifat_afek has quit IRC11:43
*** quadam has joined #openstack-self-healing12:22
quadamHello everyone12:39
quadamWhat forms of healing are you doing on your self?12:39
quadamI wrote some articles they are mainly in Turkish though I have some articles that are in English too12:40
quadamhttps://medium.com/sifagonullusu/english/home12:40
quadamI mainly do Regression and Healing for Past Lives and Dispelling/Removing Curses lately12:41
*** mrhillsman has joined #openstack-self-healing13:10
*** pgaxatte has quit IRC16:51
*** bogdando has quit IRC16:54
*** ricolin has quit IRC17:00
aspiershi17:04
aspierstsk, I'm late again17:04
aspiersanyone around?17:04
aspiershi quadam17:05
ekcshi aspiers17:05
aspiersahhh haha, quadam this is not that type of self-healing!! X-D17:05
aspiershey ekcs :)17:05
aspiers#startmeeting self-healing17:07
openstackMeeting started Wed Dec  5 17:07:18 2018 UTC and is due to finish in 60 minutes.  The chair is aspiers. Information about MeetBot at http://wiki.debian.org/MeetBot.17:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:07
*** openstack changes topic to " (Meeting topic: self-healing)"17:07
openstackThe meeting name has been set to 'self_healing'17:07
aspiersekcs: did you see the minutes from earlier today? no worries if not17:07
ekcsyup. I just read it.17:07
aspierscool17:08
aspiershttp://eavesdrop.openstack.org/meetings/self_healing/2018/self_healing.2018-12-05-09.33.html in case anyone else is wondering17:08
aspiers#topic actions from meeting two weeks ago17:08
*** openstack changes topic to "actions from meeting two weeks ago (Meeting topic: self-healing)"17:08
aspiersI think I've either taken care of each action, or added it to storyboard17:08
aspiersbut let me know if I've missed anything17:09
ekcsyup.17:09
aspiersI also got a mail from (I guess) the same person who contacted Ifat earlier about the monasca/vitrage integration work17:09
aspiersit was a very helpful and encouraging mail, so I'll respond soon17:10
aspiersI only have a couple of things to discuss17:10
ekcsthat’s great!17:10
aspiers#topic clarifying how to contribute to the SIG17:10
*** openstack changes topic to "clarifying how to contribute to the SIG (Meeting topic: self-healing)"17:10
aspiershttps://review.openstack.org/#/c/620424/17:10
aspiersdid my review make sense?17:11
aspierse.g. the thing about how to handle implemented vs. not-yet-implemented use cases17:11
aspiersI'm currently thinking an extra section in the template makes the most sense17:12
ekcsyes thanks for the comments!17:14
ekcsi’m not totally clear on the “status” idea.17:14
aspiersso I think we definitely want to allow both use cases which are and aren't implemented17:14
aspierse.g. the memory leaks one suggested in Berlin has no "upstream" implementation yet17:15
aspiersbut describing the problem is a good first step towards that17:15
aspiersthe question is, how should we split those two categories up? into separate subdirectories is one possibility, but I think that's problematic17:16
aspierse.g. it would require moving the file when an implementation emerges, and the categories aren't really binary black-and-white anyway17:16
aspiersso I'd prefer a "Current status" section in the template, which allows a freeform text description of the status17:17
ekcshmmm.17:18
aspiersallowing things like "this bit is implemented, but this other bit isn't yet"17:18
aspierswhich can give more clarity17:18
ekcsah i see.17:18
ekcsok just to clarify, you mean this would be in categorizing use-cases17:18
ekcswhat about specs?17:18
aspiersfor use cases, yes17:18
aspiersI think specs could be handled in the way they are handled in other repos17:19
ekcsok so specs are still separate.17:19
aspiersyup17:19
aspiersspecs are for focusing on specific implementation details17:19
ekcsso up till now use casse have been used for implemented cases.17:20
aspiersyes, that would continue17:20
aspiersspecs are only for driving future dev work17:20
aspierssorry17:20
aspiersmaybe I wasn't clear here :)17:20
aspierslet me rephrase17:20
aspiersyour point is that up till now, use-cases have *only* been used for implemented cases, and not for unimplemented?17:21
aspiersI'm not sure that's true actually17:21
ekcsok.17:21
aspiershttps://docs.openstack.org/self-healing-sig/latest/use-cases/fenix-rolling-upgrade.html is arguably not yet implemented17:22
aspiersat least not fully17:22
aspierswhich sort of demonstrates my point that "implemented vs. unimplemented" isn't a straightforward binary choice17:22
ekcsso going forward we want use-cases to be used for use-cases at all stages of implementation. not started, in progress. completed. and everything in between.17:22
aspiersexactly!17:22
aspiersand a "Current status" section can give info on the status, or at least clues for where to look17:23
aspierse.g. it could just say "go check this storyboard story"17:23
ekcsyea that makes sense.17:23
aspiersthat's up to the use case owner17:23
aspiersOK great, let's take that approach then17:23
ekcsstill I think at some point we want to draw some kind of categorization.17:23
aspiers#agreed Add a "Current status" section to use-cases/*.rst17:24
ekcsfor that someone who’s just looking to see how to use things won’t be confused or mislead by the unimplemented use cases.17:24
aspiersWe could separate them out in the index.rst, would that work?17:24
ekcsit doesn’t have to be a separate dir but yes separate in index.rst can work17:25
aspiersOK17:25
aspiersI don't want to rule a separate dir out either17:25
aspiersbut I think for now we don't need it17:25
ekcsok not be belabor this too much.17:25
aspiersright :)17:25
ekcsbut what’s the real disadvantage of separate dir?17:25
aspiersmainly that it's not always clear which dir a use case should go in17:26
aspierse.g. the fenix one17:26
ekcsit could help people who are just browsing git dir17:26
ekcsok17:26
ekcsyea let’s just do with same dir then.17:27
aspiersok17:27
aspiers#agreed stick with a single use-cases/ directory for now17:27
aspiers#topic where to store high-level SIG info17:27
*** openstack changes topic to "where to store high-level SIG info (Meeting topic: self-healing)"17:27
aspiersso this is another thing which came up in that review17:27
aspierscurrently the SIG mission statement / scope are in the wiki17:27
aspierswhich is not subject to peer review17:27
aspiersfor that reason I think I'd prefer to move it to the git repo17:28
aspierse.g. I added a paragraph to the scope yesterday, but doing that didn't feel very democratic ;-)17:28
aspiersdo you think it's reasonable to move the more static info from the wiki into the git repo?17:29
aspierswe could keep the more fluid sections in the wiki, e.g. upcoming and past events17:29
aspiersbut the rest could be moved to the docs and replaced with a link17:29
aspiersmaybe the project contacts could stay there too, I don't know17:30
ekcsthat makes sense. I agree that ultimately reviewed is better. at the same time, I feel it’s beneficial but not high priority at this point.17:30
aspiersit probably doesn't matter too much17:30
aspiersagreed17:30
aspiers#agreed would be nice to move more static info about the SIG from the wiki to the git repo, but not high priority17:31
aspiers#topic AOB17:31
*** openstack changes topic to "AOB (Meeting topic: self-healing)"17:31
aspiersI think that's all I've got17:31
aspiersanything from you?17:31
ekcsno nothing more.17:31
aspiersOK cool, thanks!17:32
aspiers#endmeeting17:32
ekcsi’ll finish up the patch.17:32
*** openstack changes topic to "https://wiki.openstack.org/wiki/Self_healing_SIG | https://storyboard.openstack.org/#!/project/openstack/self-healing-sig"17:32
openstackMeeting ended Wed Dec  5 17:32:14 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/self_healing/2018/self_healing.2018-12-05-17.07.html17:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/self_healing/2018/self_healing.2018-12-05-17.07.txt17:32
openstackLog:            http://eavesdrop.openstack.org/meetings/self_healing/2018/self_healing.2018-12-05-17.07.log.html17:32
aspiersawesome17:32
ekcsbased on our discussions.17:32
aspiersOK great, catch you soon :)17:32
ekcsok later. thanks aspiers !17:33
*** mrhillsman has quit IRC17:51
*** mrhillsman has joined #openstack-self-healing17:52
*** mannamne has joined #openstack-self-healing18:29
*** mannamne has quit IRC20:22
*** mannamne has joined #openstack-self-healing21:18
*** quadam has left #openstack-self-healing21:24
*** tojuvone has quit IRC21:34
*** tojuvone has joined #openstack-self-healing21:34
*** mannamne has quit IRC22:02
*** mannamne has joined #openstack-self-healing22:03
*** ekcs has quit IRC22:21
openstackgerritEric Kao proposed openstack/self-healing-sig master: improve CONTRIBUTING.rst to explain how/when to propose stories/specs  https://review.openstack.org/62042422:42
*** mannamne has quit IRC22:49

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