16:00:01 #startmeeting Octavia 16:00:02 Meeting started Wed May 13 16:00:01 2020 UTC and is due to finish in 60 minutes. The chair is johnsom. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:04 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:06 The meeting name has been set to 'octavia' 16:00:16 #chair rm_work 16:00:16 Current chairs: johnsom rm_work 16:00:20 hi 16:00:28 hi 16:00:40 Hi everyone! 16:00:53 hi 16:01:19 #topic Announcements 16:01:34 Ussuri is released! 16:01:36 #link https://www.openstack.org/software/ussuri/ 16:01:52 If you didn't attend the highlights meeting this morning, the release is out. 16:02:02 Thank you all for your contributions! 16:02:37 Octavia got some attention this cycle in the release announcements, etc. so good stuff. 16:02:57 Both AZs and TLS ciphers are in the screenshots section 16:03:18 well done, team! 16:03:30 Along those lines, thank you to rm_work for his leadership during Ussuri! 16:03:58 This is his last week as PTL and then you are stuck with me. grin 16:04:08 ... again 16:04:14 lol 16:04:14 thank you, rm_work! 16:04:53 As the release is out, we are officially open for Victoria patch merge. (Though I think we have been for a bit anyway) 16:05:21 Also a friendly reminder, PTG registration is open: 16:05:28 #link https://www.openstack.org/ptg/ 16:05:35 and we have an etherpad: 16:05:42 #link https://etherpad.opendev.org/p/octavia-virtual-V-ptg 16:05:58 Please include any topics you would like to discuss during our PTG sessions. 16:06:15 Any other announcements this week? 16:07:01 #topic Brief progress reports / bugs needing review 16:07:40 Ok, other than some reviews and working on the content the foundation requested, I have been focusing on an internal project this week. 16:08:39 I pushed small patch for an issue I discovered on our internal cloud 16:08:43 #link https://review.opendev.org/#/c/726084/ 16:09:00 some reviews appreciated :) 16:09:09 I should also mention I am giving a short talk at the OpenStack meetings today covering our Ussuri highlights. So, shout outs for those features. 16:10:15 same content as meeting ~2 hours ago, right? 16:10:19 Hmm, interesting. Even an API get is failing... 16:10:33 Yes, same exact content, just a separate time (zone) 16:11:20 ataraday_ Looks good. My only comment would be to maybe tie the retry counts to configuration file settings. 16:11:37 We have got feedback in the past that some people want things to retry forever. 16:12:05 Personally, I'm getting a bit concerned about the number of these "retry" values we have defined in the configuration file. 16:12:24 johnsom, sure, will add it 16:12:33 yeah, to many reties... 16:12:33 I would be interested to hear if people have ideas/thoughts on how to improve that situation or if it is ok as it is. 16:12:55 Maybe we can consolidate them somehow. 16:13:39 I know I have added a bunch of them, and I'm just not sure if it's useful for tuning, or just too much. 16:13:47 ideally we want to have all retries configurable? 16:14:12 ataraday_ Historically that has been our position. 16:14:54 Mostly because of the very wide performance difference between the nested virtualization the zuul gates use vs. the production situations. 16:15:25 But I would like to have a discussion about it. Is it too much, is it good, etc. 16:18:18 No other comments? 16:18:47 I have been trying to get the gates functional, https://review.opendev.org/#/c/726972/ and https://review.opendev.org/#/c/727280/ (ussuri, needs further work) 16:18:50 The question with retries would also be - should be a big number by default or not, I guess a lot can be disscussed.. 16:19:23 Yes, I agree. I think it would be good for the team to have that discussion. Maybe this is a good PTG topic 16:19:34 haleyb Thank you. 16:20:05 I did have a question I haven't posted for one of your patches yet. If we fix those issues, why do we still need to pin it? 16:21:04 johnsom: well, for stable we're only fixing until the next release of flake8/pycodestyle/etc since they're unbounded 16:21:18 Ugh, looks like we are caught in the "zuul is really busy, so jobs randomly timeout" cycle there 16:22:04 yeah, pile-up in zuul 16:22:58 This is a cap for Ussuri right? 16:23:00 #link https://review.opendev.org/#/c/727280/ 16:23:33 yes, but i'm assuming other branches are broken too, at least they are in neutron back to rocky 16:24:02 Ok, so your plan was to fix master, cap the stable branches? 16:24:38 johnsom: yes, just based on how large the patch was 16:24:45 I think requirements has talked about capping the linters for stable branches before, but it tends to get messy 16:25:13 Yeah, though it's pretty low risk assuming it's just the single letter variable name issue 16:25:39 who doesn't like the letter 'l' ? :) 16:26:02 I don't 16:26:04 lol 16:26:58 Funny story actually of being a wise guy in college and getting stuck in a 101 class due to requirements. I crashed the compiler because I variables were too descriptive. 16:27:04 Ah the good old days. 16:27:08 i might need to cherry-pick if that cap doesn't work 16:27:21 Ok, I am not opposed to that 16:27:29 * cgoncalves challenges johnsom to not use letter 'l' until end of the meeting 16:27:30 Thanks for working on it! 16:27:37 we all learned in school to use i, j, k for looping, guess that's all we're allowed 16:28:20 Ok, any other topics today? 16:28:42 * johnsom notes, none of that character in the sentence.... 16:29:38 #topic Open Discussion 16:29:47 opps, forgot the topic change 16:30:43 Ok, thank you everyone! Happy Ussuri re1ease day! 16:31:00 gotcha! re*l*ease! 16:31:12 thanks! 16:31:13 he used a 1 to be snarky 16:31:14 That was #1 16:31:18 grin 16:31:25 #endmeeting