17:30:35 #startmeeting self-healing 17:30:36 Meeting started Wed Aug 14 17:30:35 2019 UTC and is due to finish in 60 minutes. The chair is aspiers. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:30:37 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:30:39 The meeting name has been set to 'self_healing' 17:30:43 #topic automated testing 17:30:52 ihti: anything you want to bring up? 17:31:12 for the minutes ... 17:31:34 #link https://review.opendev.org/#/c/675138/ adds a list of testing frameworks to the SIG repo 17:31:35 not much from my side yet, playing around with Rally on a dev setup 17:31:38 cool 17:31:48 the matrix clearly shows an awful lot of overlap 17:32:05 it occurred to me that we should try to get all the maintainers of the various tools to review that matrix 17:32:20 yes, it have, rally covering most of the features 17:32:27 as they may be able to offer extra info 17:33:00 yes, that would be very helpful with and would make the whole list more accurate 17:33:13 #link https://logs.opendev.org/38/675138/4/check/openstack-tox-docs/344de18/html/testing/tools-list.html Zuul build of the new doc 17:33:41 Yardstick + Doctor also seems to cover everything 17:34:26 +NFV bench 17:34:30 ihti: Oh I just noticed, Eris is not in there yet 17:34:37 I guess that's intentional? 17:34:43 yes 17:34:58 as it will be worked on so i thought not include it yet? 17:35:04 not sure 17:35:19 I think it would be better to include it, but add a new column "maturity" 17:35:43 e.g. unfinished/alpha/beta/immature/mature 17:36:04 that's good idea. 17:36:08 also maybe another column for "OpenStack-specific" 17:36:16 since tools like Jepsen are agnostic 17:37:15 and there is no column for performance testing, unless that is under "Scalability testing"? 17:37:24 but I think they are different things 17:37:34 so separate columns would be useful 17:37:37 'Openstack-specific' one I added but then removed it afterwards, as I jepsen was the only one falling in that category 17:37:47 Hmm 17:38:40 OK, so maybe change the Jepsen cell to read "Jepsen (not specific to OpenStack)" 17:39:16 Another suggestion: add a separate column for reliability testing 17:39:38 For performance I thought it overlaps with 'data plane testing'? I could be off 17:39:38 since the ability to inject disruptions / failures is separate from the ability to test resilience against them 17:39:58 I think we need performance testing for control plane operations oto 17:39:59 too 17:40:01 okay I will mention that for jepsen 17:40:22 so no, I would consider performance testing somewhat separate to data plane 17:40:40 control plane operations can be slow 17:40:41 alright 17:40:44 especially things like failover 17:41:02 Sorry, I am just thinking of this new feedback now :) 17:41:36 no worries, I appreciate it :) 17:41:43 Another column we need is around the level of community activity 17:41:49 Some of these tools are dead 17:41:54 That is an important datapoint 17:41:56 alright, yes that's true 17:42:04 Other tools are not dead, but only have a few contributors 17:42:07 not update for a couple of years 17:42:25 so a column "size of active community" would help 17:42:40 but maybe it's not just size, but also level of activity 17:43:12 e.g. 2 contributors could do total of 500 commits in a month, or 20 contributors could do total of 10 commits in a month ... 17:43:39 These are important considerations when designing a full solution 17:45:13 that makes sense and can be easily gathered by having a look at repos 17:45:48 yea maybe instead of putting up a static “grade” we can just link to the repo activities page. 17:47:03 well it's useful to be able to compare them all at a glance 17:47:09 that's kind of the point of this matrix 17:47:28 any cell could change, but that's OK :) 17:47:29 yea that makes sense too. 17:48:13 I can add both a link and value 17:48:17 perfect! 17:48:18 to each sell 17:48:21 *cell 17:48:28 that would be great 17:48:39 sorry, so it seems I asked for like 59 new columns :) 17:49:14 I think its good and makes the decision making process much easier 17:49:21 yes 17:49:52 maybe once you've updated the matrix we can try to contact the communities of the various tools for feedback 17:50:03 some of them are already cc'd on the review 17:50:16 but we'll need to find others probably 17:50:46 ihti, ekcs: OK anything else on this topic? 17:50:51 cool 17:50:55 great 17:50:55 no 17:51:05 no topic from my side 17:51:11 so we can move on, or end the meeting 17:51:23 ekcs: anything to discuss about Shanghai at this point, or anything else? 17:51:38 ihti: thanks a LOT for all your great work so far! 17:51:45 it's hugely appreciated 17:51:50 not really. my focus now is just to find time to complete this task finally: https://storyboard.openstack.org/#!/story/2005641 17:52:02 thanks for the reviews and feedback :) 17:52:09 thank you ihti ! 17:52:20 ekcs: oh nice, that would be great!! 17:52:39 ihti: BTW soon we should email openstack-discuss announcing this new doc 17:52:46 maybe we can announce after merging 17:53:30 OK, sounds like we are done for today 17:53:35 yes, after reviews by the tool devs is done, it would be good idea to spread it out 17:53:41 yup 17:53:56 it will help restart the discussion around how to fix this 17:54:28 ihti: don't hesitate to ask me if you have any questions or need support on anything 17:55:09 see you both online, bye for now! o/ 17:55:09 aspiers, sure i will, thanks very much till now :) 17:55:21 :) 17:55:24 bye! 17:55:31 #endmeeting