15:01:08 #startmeeting kolla 15:01:09 Meeting started Wed Jun 24 15:01:08 2020 UTC and is due to finish in 60 minutes. The chair is mgoddard. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:12 #topic rollcall 15:01:13 The meeting name has been set to 'kolla' 15:01:20 \o 15:01:29 o/ 15:02:10 0/ 15:02:41 o/ 15:02:58 o/ 15:04:31 #topic agenda 15:04:46 * Roll-call 15:04:48 * Announcements 15:04:50 ** Kolla Ussuri released! 15:04:52 * Review action items from last meeting 15:04:54 * CI status 15:04:56 * Ussuri release planning (kayobe) 15:04:58 * Ussuri release planning (kolla & kolla ansible) 15:05:00 * Kolla klub 15:05:02 #topic Announcements 15:05:12 #info Kolla Ussuri released! 15:05:24 yay 15:05:28 Well done everyone 15:05:29 woopee 15:05:51 * yoctozepto popping champagne bottles 15:06:22 we actually got kayobe out at the same time \o/ 15:06:29 congrats, kayobe! 15:07:01 good work! 15:07:11 @mgoddard sorry for late !! 15:07:33 oh hi suryasingh :) welcome back 15:07:39 thanks for all the hard work everybody :) 15:07:50 +1 15:07:51 welcome back, suryasingh! 15:08:08 now we continue with Victoria development 15:08:18 #topic Review action items from last meeting 15:08:23 @mgoddard @yoctozepto +1 15:08:44 there were none 15:08:50 #topic CI status 15:10:34 whiteboard says kolla master and ussuri are broken, but I think this is wrong 15:10:40 I hope so since we just released :) 15:11:35 mnasiadka: that kolla clustercheck issue resolved itself? 15:11:50 mgoddard: yes, Fedora git started working and it resolved itself 15:11:55 ok 15:12:02 but a change with a curl macro is underway 15:12:10 just needs some more love 15:12:52 how about stein? 15:13:11 still having the tox/virtualenv issue? 15:13:23 yup 15:13:51 right, I haven't backported the changes 15:14:04 did somebody do it, or should I? 15:14:14 I don't see them 15:14:17 can you? 15:14:43 mnasiadka: if you can, please do 15:14:48 they are likely unclean though 15:14:55 yeah, they will need some work 15:15:02 but it shouldn't be much, will do it after the meeting 15:15:07 #action mnasiadka backport stein CI fixes 15:15:08 thanks 15:15:15 +1 15:16:01 kolla-ansible happy 15:16:47 kayobe is ok back to stein 15:16:56 rocky we had to make some jobs non-voting, queens is bust 15:17:22 #topic Victoria release planning (kayobe) 15:18:00 Victoria... 15:18:14 What's in the pipeline? 15:18:18 I think we can call time on https://etherpad.opendev.org/p/kolla-victoria-priorities 15:18:45 I will spend a few minutes doing the sums 15:19:16 Michal Nasiadka proposed openstack/kolla-ansible stable/stein: Run tox in venv in case of building images https://review.opendev.org/737829 15:22:50 ok, some big winners: 15:22:54 infra images - 7 15:23:12 octavia - 9 15:23:18 designate - 7 15:23:30 letsencrypt - 10 15:23:38 docs refresh - 8 15:23:46 federated keystone - 7 15:24:07 health checks - 7 15:24:17 kayobe docs - 7 15:24:37 4 of those involve improvements to docs. Take note :) 15:25:07 any comments? 15:25:18 anyone want to put their name on one? 15:25:36 I'll take letsencrypt :) 15:25:52 headphoneJames: cool 15:26:00 Mr TLS 15:26:41 anyone else? 15:27:29 Michal Nasiadka proposed openstack/kolla stable/stein: CI: Install python deps, fix mod_wsgi in cyborg-api, disable masakari-monitors https://review.opendev.org/737831 15:27:34 mgoddard: I guess my name is superglued to healthchecks 15:27:42 right 15:28:50 Mark Goddard proposed openstack/kolla-ansible stable/train: barbican: Use python3 plugin in uwsgi config https://review.opendev.org/733805 15:29:06 Anything else to say about ussuri? 15:29:10 sorry, victoira 15:29:35 I can put my name on designate if no better candidates exist 15:30:08 cool 15:30:22 the general docs topic is great but I don't think it's one-man's job unfortunately 15:30:22 i added my to few of the priority items :) 15:30:39 Bharat Kunwar proposed openstack/kolla-ansible master: Use internalURL endpoint_type for all clients used by Magnum https://review.opendev.org/737834 15:30:47 I can cooperate with someone on any docs, grammar fiend soul here 15:31:01 yoctozepto: +1 15:31:20 it doesn't have to be one person per item 15:31:55 I think about docs - it would be good to have a list of things to work on 15:32:02 ok, then mention my name 15:32:24 I guess we can mix the docs and scenarios planning as well 15:32:33 they kinda have to match anyhow 15:32:57 I was thinking the docs item could start with a review of our docs 15:33:01 then go from there 15:33:10 while we are on that 15:33:22 could we set up kolla dev calls for that? 15:33:31 one hour every two weeks, apart from kolla klub? 15:33:50 might be more effective than just irc meetings 15:33:58 or we could mix that in kolla klub 15:34:02 for housekeeping? 15:34:11 for the reviews and planning 15:34:19 and housekeeping when done with planning 15:34:28 planning > housekeeping 15:35:09 Kolla Kalls 15:35:22 Agree with yoctozepto +1 Kolla calls 15:35:33 Kalls* :D 15:35:54 :) nice name 15:37:21 do you want to handle setting this up yoctozepto? 15:37:39 Michal Nasiadka proposed openstack/kolla-ansible master: Change neutron-ovs-agent deploy only with manila generic backend https://review.opendev.org/737768 15:37:43 propose the same slot as kolla klub, on alternate weeks? 15:37:59 mgoddard: sounds sane 15:38:13 mgoddard: what does "setting this up" involve? 15:38:23 mgoddard: I can post to ml about it 15:38:25 good q 15:38:34 and set some agenda 15:38:51 we can reuse wiki for that obviously 15:38:53 email the list to begin with 15:39:32 reuse wiki? same page or different? 15:39:46 can go either way 15:39:52 pages are free to create 15:39:58 thankfully! 15:40:55 separate is probably better 15:41:04 ++ 15:41:10 #action yoctozepto to email list about kolla dev kalls 15:41:13 sorry guys this may be lame....does Kolla club same as Kolla weekly meeting or something else :( 15:41:24 suryasingh: separate event 15:41:41 suryasingh: we meet with operators all around the world every 2nd Thursday via a video call 15:41:47 https://docs.google.com/document/d/1EwQs2GXF-EvJZamEx9vQAOSDB5tCjsDCJyHQN5_4_Sw/edit?pli=1 15:42:08 wow great yoctozepto +2 15:42:29 and I proposed to fill the other weeks' Thursdays with Kolla Kalls 15:42:43 the time seems safe for most 15:42:50 kolla klub is operator-oriented 15:43:10 we might want to use kolla klub as kolla kalls food for thought generator 15:43:36 our weekly irc meetings have this standard structure where we discuss general and current thingies 15:44:00 open to improvements on the structure 15:44:18 it works quite well around release time, but could be improved 15:44:33 I don't think we can squeeze more efficiency from irc talks 15:45:16 or, to rephrase, I have no idea how to approach that 15:45:27 happy to discuss either 15:45:53 seems we are discussing a lot on kayobe section atm 15:45:55 ;d 15:46:04 mgoddard topic switch? 15:46:18 #topic Victoria release planning (kolla & kolla ansible) 15:46:27 I think we covered everything in the last one 15:46:31 indeed 15:46:35 unless people have other things 15:46:47 #topic Kolla klub 15:46:54 https://docs.google.com/document/d/1EwQs2GXF-EvJZamEx9vQAOSDB5tCjsDCJyHQN5_4_Sw/edit#heading=h.u784zrqsv2k1 15:47:15 next week we have: 15:47:16 Gaƫl: Offline usage of Kolla & Kolla Ansible 15:47:18 Justinas: host OS lifecycle management 15:47:25 other topics welcome 15:47:45 #topic open discussion 15:48:02 we might want to add the priorities summary and review discussion to that 15:49:04 good idea 15:49:27 mgoddard: ack, was testing comments 15:50:45 mnasiadka: any thoughts? 15:51:34 I recently played with masakari quite a bit 15:51:46 how is it? 15:52:03 thoughts? about what? 15:52:19 mnasiadka: about Victoria, life, anything 15:52:21 i know it was developed by one of my friend 15:52:27 what to know yoctozepto 15:52:28 * suryasingh ? 15:52:51 mgoddard: looks decent, played outside of kolla because of pacemaker 15:53:18 I might be able to pick up Gaetan's work 15:53:19 yoctozepto: no thoughts at all, priorities are one thing, life dictates another ones dynamically :) 15:53:34 mnasiadka: oh my ;d 15:53:43 so not really a fan of planning :) 15:53:51 mnasiadka: covid isolation => baby boom? 15:54:10 yoctozepto: naah, just laughing - one kid is enough :) 15:54:10 suryasingh: could be, so far no questions from me 15:54:29 yoctozepto: noted +1 15:54:36 Michal Nasiadka proposed openstack/kolla-ansible stable/stein: Run tox in venv in case of building images https://review.opendev.org/737829 15:55:46 the major parts missing in kolla rely on pacemaker; this work has not been finished 15:55:53 in kolla-ansible 15:56:04 pacemaker in a container, ugh 15:56:05 we have some images in kolla already 15:56:13 yeah, feels wrong 15:56:13 yoctozepto: do you know if the missing package is a blocker? 15:56:32 mgoddard: I know it's not, unless Gaetan planned to use it for bootstrap 15:56:37 but we can safely drop it 15:56:48 as well as the whole image with it 15:57:04 ok 15:57:19 if pacemaker in containers is wrong, we don't have to do it that way 15:57:38 just sounds like an overkill, but could be nice to try 15:57:53 but hey, you could argue the same with mariadb and lots of others 15:58:17 quite 15:59:22 are you running HA on instances in other ways or no such need so far? 15:59:55 I think one could argue you don't need such functionality in a cloud :) 15:59:55 typically it's done at a higher layer 16:00:05 cattle etc 16:00:34 but not everyone agrees 16:01:00 ok, we're at the end of the meeting 16:01:02 Thanks everyone 16:01:04 #endmeeting