15:00:15 #startmeeting kolla 15:00:15 Meeting started Wed Jun 16 15:00:15 2021 UTC and is due to finish in 60 minutes. The chair is mgoddard. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:15 The meeting name has been set to 'kolla' 15:00:30 #topic rollcall 15:01:03 8< 8< 8< 15:03:22 o/ 15:03:29 \o 15:03:39 \o/ 15:03:43 ]o[ 15:04:23 #topic agenda 15:04:28 (mgoddard: yup, but it could be threaded) 15:04:33 * Roll-call 15:04:35 * Agenda 15:04:37 * Announcements 15:04:39 * Review action items from the last meeting 15:04:41 * CI status 15:04:43 * Wallaby release planning 15:04:45 ** libvirt/OVMF bug 15:04:47 * Xena cycle planning 15:04:49 ** master branch life cycle https://review.opendev.org/c/openstack/kolla/+/795320 15:04:51 ** Testing log coverage (and more?) https://review.opendev.org/c/openstack/kolla-ansible/+/795512 15:04:53 * Open discussion 15:05:39 #topic announcements 15:05:48 None from me 15:06:26 none 15:06:26 #topic 15:06:29 nope 15:06:29 #topic Review action items from the last meeting 15:06:35 mgoddard email openstack-discuss about quay.io credentials 15:06:37 mnasiadka perform R-17 release tasks 15:06:45 mgoddard: nope 15:06:49 mnasiadka: started 15:07:07 I'm dropping that one. It's on a personal TODO list, just low priority 15:07:12 ok 15:07:17 #topic CI status 15:07:46 centos8 broke masakari-monitors in train 15:07:50 otherwise pretty green 15:07:52 kolla: [train] libvirt-python dep broke masakari-monitors build on c8 15:07:58 with the random failure on neutron upgrades 15:08:26 re masakari-monitors and c8 15:08:29 we have a bug report 15:08:36 that it fails up to victoria 15:08:41 fails to build* 15:08:48 but CI confirms only for train 15:08:59 I did not have time to dive in 15:09:00 but priteau did 15:09:14 I said I would try a build in victoria but lost access to my env so haven't completed it 15:09:22 https://review.opendev.org/c/openstack/kolla/+/796387 15:09:27 no problem 15:09:34 I wanted to mention the workaround ^^ 15:10:26 doesn't seem to work 15:11:07 ? 15:11:08 Are you saying this because of Zuul -1? The centos jobs passed 15:11:09 it built 15:11:14 not debian 15:11:33 debian's patch is broken on centos8 not passing 15:11:43 https://review.opendev.org/c/openstack/kolla/+/795874 15:11:50 and so is final bump 15:11:55 and so is our em release 15:12:21 so should we combine those patches and merge 15:12:23 ? 15:12:56 debian is non-voting 15:13:08 the workaround doesn't seem any worse than the existing code 15:13:09 I guess we could go with the workaround 15:13:17 and bury train 15:13:25 then worry about ussuri+ 15:13:54 we might get pressure to tag our EM soon 15:13:59 indeed 15:14:01 don't want to get caught with our pants down 15:14:03 I'm rechecking priteau's workaround 15:14:16 ok 15:14:21 priteau to lift w-1 15:14:30 and /me rebasing other patches 15:14:33 k 15:14:58 I'll recheck too because of the POST_FAILURE 15:15:03 Radosław Piliszek proposed openstack/kolla stable/train: Enable Debian updates repo https://review.opendev.org/c/openstack/kolla/+/795874 15:15:05 You already did 15:15:12 Radosław Piliszek proposed openstack/kolla stable/train: Bump final OpenStack versions for Train https://review.opendev.org/c/openstack/kolla/+/795258 15:15:17 fingers crossed 15:15:22 priteau: yeah 15:15:28 priteau: just need w0 from you 15:15:31 done 15:15:36 ok 15:15:37 thx 15:15:51 mgoddard: cr+2w+1? 15:15:54 the train is ready to go 15:15:56 all the patches 15:16:08 I'll wait for zuul 15:16:21 #topic Wallaby release planning / libvirt/OVMF bug 15:16:37 mgoddard ok 15:16:40 How are we looking with this one? 15:16:44 priteau also knows 15:17:29 So, we appear to have a fix because c8 AV imported libvirt 7.0, although I would think it should *not* work 15:17:45 But anyway, c8s is due to fix their AV repo package today 15:17:53 Which will give us libvirt 7.4 15:18:12 So I am refreshing http://mirror.centos.org/centos/8-stream/extras/x86_64/os/Packages/ multiple times, but still no updated package 15:18:53 hughesjr said by wednesday cob us time 15:18:56 So we continue to wait 15:19:08 unfortunately yes 15:19:14 hopefully tomorrow 15:19:44 #topic Xena cycle planning / master branch life cycle 15:19:44 If someone wants to proactively test libvirt 7.4, we could just update the repo file after the package has been installed 15:19:57 #link https://review.opendev.org/c/openstack/kolla/+/795320 15:20:15 Not much to say on this one 15:20:21 Except please review 15:20:52 #topic Testing log coverage (and more?) 15:20:58 #link https://review.opendev.org/c/openstack/kolla-ansible/+/795512 15:21:55 This is a patch that I've been iterating on recently, that could improve our log coverage 15:22:24 We currently have no real test coverage of our logging 15:22:28 yeah, we need something in that direction 15:22:29 This should help 15:23:24 Basic idea is, we have an output plugin in fluentd image that writes a tab separated values file containing various labels for each log message 15:23:57 Then in kolla-ansible we have a new test that ingests that TSV file and verifies that everything is as expected 15:24:35 The test is implemented using py.test / testinfra 15:24:41 #link https://review.opendev.org/c/openstack/kolla-ansible/+/795512/13/tests/test-fluentd.py 15:25:03 this obviously tests only whether we log at least one message 15:25:06 I think we could really tighten up our testing by introducing this 15:25:18 yoctozepto: correct, currently 15:25:22 yeah 15:25:36 I think someone worked on improving the fluentd integration 15:25:38 re parsing 15:25:52 so that we don't lose messages or get weird entries 15:25:59 right 15:26:24 we could do more in the output plugin to validate each fluentd event, currently it is quite minimal 15:26:37 e.g. does it have at least Hostname, programname, log_level set 15:27:12 I wanted to get the moving parts in place then it can be iterated on 15:27:37 great, I am all in 15:27:40 will review for sure 15:27:42 excellent 15:28:19 I think the existing tests/check-* scripts could be added to this py.test 15:28:32 then we get results in one place 15:28:46 and zuul and expose them as artifacts 15:29:19 we're using this approach in kayobe already: https://opendev.org/openstack/kayobe/src/branch/master/playbooks/kayobe-overcloud-host-configure-base/tests/test_overcloud_host_configure.py 15:29:50 ++ 15:31:00 Any other comments/suggestions? 15:32:09 Looking good :) 15:33:15 cool 15:33:17 #topic Open discussion 15:33:28 Does anyone have anything else to discuss today? 15:34:55 I'm reviving https://review.opendev.org/c/openstack/kolla-ansible/+/692179 15:34:55 nope 15:35:38 that's good headphoneJames 15:35:52 are you still planning to email openstack-discuss? 15:36:28 Yes. Would like to get this one at least working first 15:36:59 ok 15:39:51 Mark Goddard proposed openstack/kolla master: docs: Update release management for Xena process https://review.opendev.org/c/openstack/kolla/+/795320 15:41:33 Let's wrap up there then 15:41:36 Thanks al 15:41:38 Mark Goddard proposed openstack/kolla master: docs: Update release management for Xena process https://review.opendev.org/c/openstack/kolla/+/795320 15:41:40 *all 15:41:43 #endmeeting