17:05:02 <aspiers> #startmeeting self-healing
17:05:03 <openstack> Meeting started Wed Jan 30 17:05:02 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:04 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:05:06 <openstack> The meeting name has been set to 'self_healing'
17:05:11 <aspiers> #topic quick status check
17:05:18 <aspiers> I guess we can just review where we are
17:05:24 <ekcs> haha sounds like you need some self healing!
17:05:29 <aspiers> haha yeah!
17:05:54 <aspiers> I expect this will consist mostly of reminding me of all the things I forgot to do
17:06:34 * aspiers looks at storyboard
17:06:41 <ekcs> haha.
17:07:19 <aspiers> oh well, there was actually a little bit of movement on healthcheck APIs
17:07:23 <aspiers> #link https://storyboard.openstack.org/#!/story/2001439
17:07:48 <aspiers> the SUSE cloud team had an all hands workshop in Nuremberg, and we did a tiny bit of hacking on the code
17:08:02 <aspiers> and also discussed what we could do to push this forwards
17:08:23 <aspiers> IIRC JP pointed out that there is a deadline for the pre-work, and maybe we just missed that already
17:09:01 <aspiers> I'll need to check
17:09:22 <aspiers> but we wanted to see if we could quickly get a PoC working with devstack and one other project
17:09:35 <aspiers> no conclusions yet
17:10:33 <aspiers> also witek and ifat_afek and I submitted a talk for Denver covering a use case for this new API
17:10:46 <ekcs> Very cool.
17:10:55 <aspiers> and for the new vitrage/monasca integration
17:11:11 <aspiers> It should be super cool especially if we can get a demo working in time :)
17:12:13 <aspiers> I think that's maybe all I have to report, unfortunately
17:12:21 <aspiers> been busy with other stuff...
17:12:45 <aspiers> Anything you want to add or discuss? No problem if not
17:12:47 <ekcs> that’s great progress!
17:13:31 <ekcs> on my end:
17:14:13 <ekcs> #link https://storyboard.openstack.org/#!/story/2004537
17:14:45 <aspiers> Oh - I forgot! There was this discussion on health checks:
17:14:47 <aspiers> http://lists.openstack.org/pipermail/openstack-discuss/2019-January/002125.html
17:15:15 <aspiers> Ah yes, the survey idea
17:18:17 <evrardjp> o/
17:18:54 <aspiers> hey evrardjp :)
17:19:06 <aspiers> I was just updating ekcs on the health checks API
17:19:12 <aspiers> have we missed a deadline already?
17:19:17 <evrardjp> nope
17:19:36 <evrardjp> it's not too late to work on that.
17:19:37 <aspiers> but it's close, right?
17:19:48 <aspiers> can you summarise the process? I can't remember how it works
17:22:42 <evrardjp> Yes so basically first step is forum (which is already passed for this case), where we list all the possible community goals contenders. We then recap and evaluate the contenders on the ML . All of that is already done.
17:22:54 <aspiers> OK
17:23:09 <aspiers> #topic process for Stein community goals
17:23:12 <evrardjp> Then we evaluate the pre-work, and contact the potential champions (that's what's happening right now)
17:23:41 <evrardjp> The next step will be to put the goals for review in governance. We want that to happen for March.
17:23:49 <evrardjp> IIRC
17:23:53 <aspiers> OK cool
17:23:55 <evrardjp> (I have to double check on the deadline)
17:24:09 <aspiers> didn't you say we only had a week or two for the pre-work though?
17:24:17 <evrardjp> So to get something for proposal on march, we need to know what's going.
17:24:19 <aspiers> and that was already >1 week ago
17:24:21 <evrardjp> what's going on*
17:24:56 <evrardjp> The idea was to have an idea of contenders and the scope of the work in February, so pre-work can be started during february.
17:25:15 <aspiers> ah OK
17:26:03 <evrardjp> there is no urgency but things needs to be done in the next weeks, else it's too late for getting an accurate proposal. If the proposal is too vague, it will not likely be accepted.
17:26:49 <aspiers> got it
17:27:53 <aspiers> alright, good to have that captured
17:27:56 <aspiers> thanks!
17:28:09 <evrardjp> I can double check the dates to give you a valid confirmation
17:28:17 <aspiers> would be useful
17:28:18 <evrardjp> but that's what I remember.
17:28:22 <aspiers> or maybe you can just post to -discuss
17:28:33 <evrardjp> yeah.
17:28:35 <evrardjp> clarify that.
17:28:53 <evrardjp> I will discuss that with lance tomorrow anyway, so we'll probably send an update tomorrow.
17:29:00 <aspiers> awesome
17:29:35 <aspiers> ekcs: so you're still working on the survey, anything else to mention? if not we can wrap up here
17:29:56 <ekcs> I have organized an etherpad of potential events and meetups where the SIG’s work could be of interest. https://etherpad.openstack.org/p/OS-events-self-healing
17:30:17 <ekcs> OS Days in London seems like a good candidate. website says their CFP will go out soon.
17:30:23 <ekcs> At some point I hope to explore the SF bay area meetups to see what connections could be made.
17:30:39 <ekcs> If there are other locations to look into I can do that too.
17:30:51 <ekcs> On the survey, I've gotten started with an account but haven't gotten very far. Still figuring out how to use limesurvey.
17:31:12 <ekcs> also making good progress on the memory leak use case. expect to have something on gerrit today.
17:31:17 <ekcs> that’s all from me.
17:31:21 <aspiers> amazing!
17:31:34 <aspiers> yeah, I spotted London and was intending to go
17:32:04 <aspiers> oh crap, no I wasn't - it clashes with SUSECON :-(
17:32:16 <aspiers> well, I don't know for sure I'm going to SUSECON yet, so we'll see
17:33:16 <ekcs> got it!
17:33:37 <aspiers> I'll try to review your use case soon after you submit
17:34:02 <ekcs> great thanks!
17:35:08 <aspiers> alright, so I guess we can wrap up
17:35:12 <aspiers> great work and talk soon!
17:35:31 <ekcs> ok yes later then!
17:35:36 <aspiers> o/
17:35:39 <aspiers> #endmeeting