15:00:10 #startmeeting kolla 15:00:11 Meeting started Wed Aug 12 15:00:10 2020 UTC and is due to finish in 60 minutes. The chair is mgoddard. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:14 The meeting name has been set to 'kolla' 15:00:17 #topic rollcall 15:00:20 o/ 15:01:01 hi everybody 15:01:09 o/ 15:01:13 hi jovial[m] 15:01:15 \o 15:03:25 #topic agenda 15:03:34 * Roll-call 15:03:35 o/ 15:03:36 * Announcements 15:03:38 ** Kolla klub tomorrow 15:03:40 * Review action items from last meeting 15:03:42 * CI status 15:03:44 * Victoria release planning (kayobe) 15:03:46 * Victoria release planning (kolla & kolla ansible) 15:03:48 * Kolla klub and kall 15:03:50 #topic announcements 15:04:23 o/ 15:04:35 #info Taking a break from Kolla Klub meetings for a while. The next meeting will be 10th September 15:04:42 Any others? 15:05:41 nope 15:05:57 #info PTL away next week Tuesday - Thursday 15:06:16 Looking for someone to chair the meeting, and kolla kall 15:06:57 \o/ 15:07:04 two hands 15:07:09 thanks yoctozepto 15:07:22 #topic Review action items from last meeting 15:07:43 mnasiadka to look into kolla stein ironic-conductor failure 15:07:45 mgoddard to message openstack-discuss about focal & victoria upgrade 15:08:26 I didn't see anything from mnasiadka about it 15:08:42 I started an email but didn't hit send.... 15:08:50 #action mgoddard to message openstack-discuss about focal & victoria upgrade 15:08:54 #topic CI status 15:09:13 We had a few issues recently 15:09:19 Ansible breaking changes 15:09:38 Looks like the whiteboard needs updating 15:09:41 handled for ci 15:09:48 yoctozepto: I think master and ussuri are fixed? 15:09:56 yes, these 15:10:02 the rest are red 15:10:12 the wb is up-to-dat 15:10:16 e 15:10:46 haha, true that 15:12:25 I think that bifrost on train issue is still present 15:13:44 any other CI issues we should discuss? 15:13:51 yeah, i haven't looked into it, left ironic to ironic experts :-) 15:14:02 nah, etcd3gw being handled right now 15:14:19 we could discuss the non-ci approach to new ansible behaviour 15:14:36 but I guess they will be reverting it for now, so only need for future versions 15:15:01 ansible-lint might start alerting soon 15:16:33 #topic Victoria release planning (kayobe) 15:16:49 priteau jovial[m] dougsz 15:17:07 o/ 15:17:13 anything happening in kayobe land? 15:17:31 Not much at the moment :( 15:17:44 sorry, been on holiday, so no updates from me 15:17:52 ok 15:18:17 #topic Victoria release planning (kolla & kolla ansbile) 15:18:37 nice to see focal merge 15:18:44 ++ 15:18:46 is there more we need to do there? 15:18:54 I turned to optimisations and refactoring 15:19:06 I guess clean up after the workaround 15:19:10 but it's included 15:19:16 otherwise focal seems focally working 15:19:18 infra images are boring 15:19:32 I rebased them and iirc they even passed zuul 15:20:03 have to sit one day and take a look what needs to be done 15:20:09 that's good, we should aim to focus on those soon 15:20:56 as I am losing track 15:22:13 Any other things to discuss? 15:22:26 we should try to look at wuchunyang's octavia patch too 15:22:49 and recheck victoria 'priorities' 15:23:05 which ones will go and which postpone 15:23:51 now , neutron plugin linuxbridge has some problem with multi nodes 15:23:58 I am operating at 1/2 speed. It is 33C here 15:24:44 mgoddard: similar issues here :-( 15:24:45 is anyone good at neutron ? 15:25:19 wuchunyang: I guess me and mnasiadka 15:25:49 i will message you after meeting. 15:25:55 I just never really touched octavia 15:26:11 I will be out but yeah, give me a ping about it 15:26:15 I haven't really used linuxbridge 15:26:33 yes ,i have not use linuxbridge.. but we support it 15:26:41 we do 15:26:51 ovs tests well .. 15:27:05 i works with multi nodes . 15:28:49 mgoddard what about we don't support linxubridge neutron plugin agent when network type is tenant ? 15:29:06 wuchunyang: that would be fine for me 15:29:42 we can document it, if someone wants to improve, they can 15:30:13 ok, i will remove the linuxbridge network code .i someone needed , use provider network instead.. 15:30:21 has anyone looked at the lets encrypt patches yet? 15:30:29 started to 15:31:01 wuchunyang: and what about ovn? 15:31:42 sorry - working on a deployment atm 15:31:49 now i only work on openvswitch. .. 15:33:28 ok 15:33:35 # Valid options are [ openvswitch, linuxbridge, vmware_nsxv, vmware_nsxv3, vmware_dvs ] 15:33:36 # if vmware_nsxv3 is selected, enable_openvswitch MUST be set to "no" (default is yes) 15:33:36 neutron_plugin_agent: "linuxbridge" 15:33:50 do we support ovn ? 15:35:17 Looks like globals.yml needs updating 15:35:36 add ovn to Valid options ? 15:35:48 yes 15:36:07 ok, i add it now .. 15:36:47 thanks 15:37:08 Any other Victoria features to discuss? 15:37:37 I will look more into letsencrypt this week 15:38:11 we will likely need a new command to generate certs from letsencrypt 15:38:23 headphoneJames: a new command? 15:39:13 the command needs to first deploy containers (including web server to respond to certbot), then execute certbot 15:39:28 assuming this happens prior to openstack deploy 15:39:56 is this not something we can just integrate into the existing flow? 15:40:04 I might be missing something 15:40:14 or I might be :) 15:40:40 the "certificates" command does not execute any deployment 15:41:03 I thought that you could just deploy certbot and have it request and rotate certs in the background? 15:41:19 or perhaps under cron 15:41:23 haven't used it directly 15:41:29 I believe there needs to be a webserver component as well 15:41:37 yes 15:41:43 for the challenge 15:41:49 certbot can listen on it's own for challenge 15:41:52 that letsencrypt uses to validate the challenge 15:42:21 hrw: ok, I'll look into that 15:42:38 we should probably read the patch and then discuss 15:42:58 however, certbot needs to run on the server that the domain name is pointing to 15:43:08 that still required a container running certbot 15:43:34 right, I think it needs to run wherever haproxy runs? 15:43:46 yes 15:43:59 and we would have a haproxy rule to forward a certain path to certbot 15:44:56 so, how would this integrate into our "certificates" role, which is execute before deployment? 15:44:56 I'm sure we aren't the first people to try this. We should look for other examples of good practise 15:45:39 does this need to integrate with the certificates role? 15:45:59 no, but thats what the patch indicates 15:46:04 ok 15:46:31 let's move on as I don't know what I'm talking about 15:46:39 Any other V topics? 15:48:51 #topic Open discussion 15:49:08 https://review.opendev.org/#/c/745214/ 15:49:08 patch 745214 - kolla-ansible - Add Keep Alive Timeout for httpd - 2 patch sets 15:49:31 anything left to do in this patch? 15:49:57 headphoneJames: it has my +2... 15:51:03 * hrw off 15:52:05 ok, let's end it there 15:52:07 thanks everyone 15:52:09 #endmeeting