17:10:33 <aspiers> #startmeeting self-healing
17:10:34 <openstack> Meeting started Wed Aug 28 17:10:33 2019 UTC and is due to finish in 60 minutes.  The chair is aspiers. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:10:35 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:10:37 <openstack> The meeting name has been set to 'self_healing'
17:10:46 <aspiers> Let's have a quick chat, I guess we won't need too long
17:10:57 <aspiers> #topic list of testing tools
17:11:07 <aspiers> #link https://review.opendev.org/#/c/675138/
17:11:22 <ihti> aspiers, thanks for formatting and proof reading the list.
17:11:37 <aspiers> ihti: you're welcome, thanks a lot for addressing all the feedback so well
17:11:51 <aspiers> I think this looks great and we can merge now if that's alright with you guys?
17:12:00 <ekcs> great!
17:12:02 <aspiers> We can easily submit follow-ups as needed
17:12:25 <aspiers> but if we merge now then we can get it out to our contacts at the mentioned projects
17:12:39 <aspiers> and then when they've had a chance to review, we can announce to the whole community
17:12:57 <aspiers> Does that make sense?
17:13:16 <ihti> I tried to add the maturity column but after going through all of them it seems like all of them are mature, couldn't really tell if they are unfinished or immature based on their git repos.
17:13:24 <ihti> aspiers, yes make sense
17:14:09 <aspiers> That's fine, I guess the activity column is enough, and maturity is subjective anyway
17:14:53 <aspiers> OK great
17:15:05 <aspiers> ihti: Do you have plans for any next steps?
17:15:28 <ihti> as for the practical work on Eris I am trying to run the demo.
17:15:36 <aspiers> Awesome
17:16:01 <ihti> but have been stuck on setting up openstack with mkcloud with HA enabled
17:16:07 <aspiers> Ah OK
17:16:25 <aspiers> Ping me on our internal #cloud channel if you need help
17:16:31 <ihti> since the last week so hopefully will be solved this week
17:16:32 <aspiers> Either I can help or whoever else sees your message
17:16:39 <aspiers> Great
17:17:10 <ihti> but yes, for the next steps I am just planning to analyze Eris more.
17:17:23 <aspiers> That would be helpful
17:17:32 <aspiers> I don't know how useful it is in its current state
17:17:53 <aspiers> but would be good to learn how close it is to something useful
17:18:19 <aspiers> IIRC this project is timeboxed for you, right? How much time do you have left?
17:18:21 <ihti> not really as its mentioned that its pre-alpha version in the demo
17:18:32 <ihti> yes it is
17:18:33 <aspiers> OK pre-alpha is about what I expected :)
17:18:50 <ihti> till Febraury
17:18:53 <aspiers> OK cool
17:19:17 <ihti> so I would like to also focus on the practical implementation as well as the litrature of how things are done right now
17:19:17 <aspiers> Do you have a good idea of what you want to do until then, or does it depend a lot on how each step goes?
17:19:27 <aspiers> Yes the practical side is very important
17:19:53 <aspiers> #topic practical investigation of testing frameworks
17:20:03 <ihti> Yes so I would like to do control and data plane testing with failure injecions
17:20:12 <ihti> that would be the first priority
17:20:19 <aspiers> Great, that would be extremely useful
17:20:25 <ihti> and then move to performance/benchmarking
17:20:30 <aspiers> Yep
17:20:49 <aspiers> It would be great if it was possible to try that with 2 or 3 different frameworks and see how they perform
17:20:52 <ihti> and if possible the scalability/concurrency
17:21:08 <aspiers> e.g. Eris vs. Yardstick or whatever
17:21:20 <ihti> alright
17:21:57 <aspiers> Cool
17:22:03 <ihti> yes, I will try out some tools wrt of these points
17:22:10 <aspiers> Don't hesitate to ping me if you need help at any point
17:22:12 <ihti> and then we can decide which can be used
17:22:16 <aspiers> Yup
17:22:30 <ihti> sure
17:22:39 <aspiers> We should probably also announce to the community that you are working on this
17:22:49 <openstackgerrit> Merged openstack/self-healing-sig master: Add list of tools for Openstack testing  https://review.opendev.org/675138
17:22:55 <aspiers> \o/
17:23:01 <aspiers> :)
17:23:02 <ihti> yes
17:23:05 <ihti> Nice!
17:23:08 <ihti> :)
17:23:25 <ekcs> = p
17:23:29 <aspiers> In the next few minutes, it should appear at https://docs.openstack.org/self-healing-sig/latest/
17:23:47 <ihti> cool, thanks!
17:24:32 <aspiers> http://zuul.openstack.org/stream/33fa4c0db0564b598f31074d67d18b07?logfile=console.log
17:24:36 <aspiers> That's the promotion job
17:24:46 <aspiers> from http://zuul.openstack.org/status
17:25:15 <ihti> ah nice, pretty helpful.
17:25:20 <aspiers> https://docs.openstack.org/self-healing-sig/latest/testing/tools-list.html
17:25:22 <aspiers> landed :)
17:25:51 <ihti> awesome!
17:26:02 <aspiers> OK, I guess I should send out an update about that
17:26:25 <ihti> to the tool developers?
17:26:33 <ihti> or whole community
17:26:40 <aspiers> I think just to the tool devs first
17:26:45 <aspiers> give them a chance to make sure it's accurate
17:26:51 <ihti> yes, sound better.
17:27:06 <ihti> I can collect there authors/devs
17:27:08 <aspiers> I mean, I'm sure it's accurate but sometime they might want things portrayed slightly differently
17:27:15 <aspiers> That would be super helpful, thanks!
17:27:48 <aspiers> I guess in some cases it might mean finding a mailing list or IRC channel, or submitting a ticket to a github issue tracker, or just emailing the maintainer
17:27:57 <ihti> I think it would be more helpful if they review them themselves, I am sure it missed many things.
17:28:31 <ihti> I will keep that in mind and look out for those as well.
17:28:48 <aspiers> Maybe we can start an etherpad for tracking this?
17:29:03 <ihti> yes, that's good idea
17:29:13 <ihti> is there an etherpad instance for openstack?
17:29:29 <aspiers> https://etherpad.openstack.org/p/extreme-testing-tools-contacts
17:30:53 <aspiers> OK
17:31:15 <aspiers> So we can copy and paste the list of tools into that, and maybe share out the work of contacting each tool community
17:31:28 <aspiers> ekcs: any chance that's something you could help out with too? no worries if you're too busy though
17:31:46 <ihti> got it, thanks
17:31:51 <ekcs> yup I can help
17:33:38 <aspiers> great
17:34:46 <aspiers> OK, just stubbed out that etherpad
17:35:33 <aspiers> So we can mark on that list who is dealing with each tool
17:35:44 <aspiers> to avoid two people duplicating the same work
17:35:47 <ihti> I can take of all
17:35:51 <ihti> shoudln't be aproblem
17:35:58 <ihti> *care
17:35:59 <aspiers> Oh amazing, thank you so much :)
17:36:34 <aspiers> OK this is great progress
17:36:39 <ihti> your welcome, they aren't many :)
17:37:04 <aspiers> Anything else on this topic?
17:37:11 <ihti> noe
17:37:14 <aspiers> OK
17:37:18 <aspiers> #topic AOB
17:37:42 <aspiers> ekcs: do we need to discuss Shanghai any more? IIRC we are all set with session booking etc.?
17:38:16 <ekcs> I think we are ok on shanghai for now. of course we’ll need to start brainstorming topics etc at some point.
17:38:24 <aspiers> yup
17:38:38 <aspiers> OK, anything else to discuss at all?
17:39:31 <ekcs> not at this point = )
17:40:05 <aspiers> OK cool, thanks very much both and cu online!
17:40:15 <aspiers> o/
17:40:32 <ihti> bye! :)
17:40:54 <aspiers> bye :)
17:40:56 <aspiers> #endmeeting