*** openstackgerrit has quit IRC | 00:49 | |
*** openstackstatus has quit IRC | 01:20 | |
*** openstack has joined #openstack-masakari | 01:24 | |
*** ChanServ sets mode: +o openstack | 01:24 | |
*** vishalmanchanda has joined #openstack-masakari | 06:56 | |
yoctozepto | #startmeeting masakari | 07:00 |
---|---|---|
openstack | Meeting started Tue Feb 9 07:00:30 2021 UTC and is due to finish in 60 minutes. The chair is yoctozepto. Information about MeetBot at http://wiki.debian.org/MeetBot. | 07:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 07:00 |
*** openstack changes topic to " (Meeting topic: masakari)" | 07:00 | |
openstack | The meeting name has been set to 'masakari' | 07:00 |
yoctozepto | #topic Roll-call | 07:00 |
*** openstack changes topic to "Roll-call (Meeting topic: masakari)" | 07:00 | |
yoctozepto | \o/ | 07:00 |
jopdorp | o/ | 07:01 |
yoctozepto | hi jopdorp | 07:02 |
yoctozepto | suzhengwei is on holidays (lunar new year celebration) so let's start | 07:02 |
yoctozepto | #topic Agenda | 07:02 |
*** openstack changes topic to "Agenda (Meeting topic: masakari)" | 07:02 | |
yoctozepto | * Roll-call | 07:02 |
yoctozepto | * Agenda | 07:02 |
yoctozepto | * Announcements | 07:02 |
yoctozepto | * Review action items from the last meeting | 07:02 |
yoctozepto | * CI status | 07:02 |
yoctozepto | * Backports pending reviews | 07:02 |
yoctozepto | * Release planning https://etherpad.opendev.org/p/masakari-wallaby-vptg | 07:02 |
yoctozepto | * Open discussion | 07:02 |
yoctozepto | #topic Announcements | 07:03 |
*** openstack changes topic to "Announcements (Meeting topic: masakari)" | 07:03 | |
yoctozepto | I have none | 07:03 |
jopdorp | Me neither | 07:03 |
yoctozepto | we are at R-9 | 07:03 |
yoctozepto | so it's very very close to freeze and release | 07:04 |
yoctozepto | in fact feature freeze and the 3rd milestone is in 4 weeks | 07:04 |
yoctozepto | need to merge some features! | 07:04 |
jopdorp | Ok | 07:04 |
yoctozepto | #topic Review action items from the last meeting | 07:04 |
*** openstack changes topic to "Review action items from the last meeting (Meeting topic: masakari)" | 07:04 | |
yoctozepto | there were none | 07:04 |
yoctozepto | #topic CI status | 07:04 |
*** openstack changes topic to "CI status (Meeting topic: masakari)" | 07:04 | |
yoctozepto | green now | 07:04 |
yoctozepto | we were hit by alembic upgrade that caused taskflow to fail | 07:05 |
yoctozepto | but that was quickly handled | 07:05 |
yoctozepto | #topic Backports pending reviews | 07:05 |
*** openstack changes topic to "Backports pending reviews (Meeting topic: masakari)" | 07:05 | |
yoctozepto | and there are none! | 07:05 |
jopdorp | Ha! | 07:05 |
yoctozepto | #topic Release planning https://etherpad.opendev.org/p/masakari-wallaby-vptg | 07:05 |
*** openstack changes topic to "Release planning https://etherpad.opendev.org/p/masakari-wallaby-vptg (Meeting topic: masakari)" | 07:05 | |
yoctozepto | any progress on these points? | 07:06 |
jopdorp | What about the features we should get merged? | 07:06 |
yoctozepto | right | 07:07 |
yoctozepto | I guess the enabling/disabling segments is very close | 07:07 |
yoctozepto | we just need to do it nicely | 07:07 |
yoctozepto | or as nice as we can afford to | 07:07 |
yoctozepto | others are a bit further off | 07:08 |
yoctozepto | gladly this cycle was nice for its bugfixes and I have some pending ones up my sleeve | 07:08 |
yoctozepto | but that's about it from me - could not get enough priority on it | 07:08 |
yoctozepto | well, we still have 4 weeks till freeze | 07:09 |
yoctozepto | and I will accept freeze exemptions if changes are safe enough not to break the whole thing | 07:09 |
jopdorp | I did creste add a blueprint that goes with the auto reenable hosts a while ago | 07:11 |
jopdorp | Create* | 07:11 |
yoctozepto | ah, yes, I remember | 07:12 |
yoctozepto | I think I did not get much time to digest it though | 07:12 |
yoctozepto | do you have a prototype implementation to see as well? | 07:12 |
jopdorp | No | 07:12 |
jopdorp | But I could make it | 07:12 |
jopdorp | Not sure l'll be able to get it into the release though | 07:13 |
jopdorp | Although in the end a lot can be done in 4 weeks | 07:13 |
yoctozepto | that's true | 07:14 |
yoctozepto | I have one important deadline this week so can't promise anything about reviewing things | 07:15 |
jopdorp | Ok | 07:15 |
yoctozepto | (though I sometimes relax by reviewing changes) | 07:15 |
jopdorp | Should I have a look st enabling/disabling segments? | 07:16 |
yoctozepto | anyhow, please be welcome to propose a prototype | 07:16 |
yoctozepto | at least it will be ready for the next cycle | 07:16 |
yoctozepto | I think you did | 07:16 |
jopdorp | Yeah | 07:16 |
yoctozepto | you can check it again though | 07:16 |
yoctozepto | I had some comments | 07:16 |
yoctozepto | in the client | 07:16 |
jopdorp | If su is on vacation I may be able to create a new patch | 07:17 |
jopdorp | Or is that agaonst etiquette? :P | 07:17 |
yoctozepto | if you know how to tackle the issue, then please do | 07:18 |
yoctozepto | we can always revert | 07:18 |
jopdorp | Ok | 07:18 |
yoctozepto | I think the priority is to get the feature in | 07:18 |
yoctozepto | not dwell on who worked the most on it | 07:18 |
jopdorp | Yeah | 07:19 |
yoctozepto | all right | 07:19 |
yoctozepto | #topic Open discussion | 07:19 |
*** openstack changes topic to "Open discussion (Meeting topic: masakari)" | 07:19 | |
yoctozepto | if there is anything else... I'm all ears | 07:19 |
jopdorp | Nothing here | 07:20 |
jopdorp | Oh | 07:20 |
jopdorp | Maybe this | 07:20 |
jopdorp | Do you have any idea of the tempest tests? | 07:20 |
jopdorp | Is it our responsibility to uodate those too? | 07:21 |
jopdorp | Update* | 07:21 |
jopdorp | Do they even exist? | 07:21 |
yoctozepto | the story is the following | 07:23 |
yoctozepto | if you look closely at our functional tests job | 07:24 |
yoctozepto | it's not the expected functional tests job | 07:24 |
yoctozepto | it actually sets up the whole environment with devstack | 07:24 |
yoctozepto | and runs "functional tests" | 07:24 |
yoctozepto | they are almost like integration tests but their coverage is a tad bit less than what one would expect from integration tests | 07:25 |
jopdorp | ok | 07:25 |
yoctozepto | so we don't have masakari in tempest | 07:25 |
yoctozepto | but this job kind of aspires to do that | 07:25 |
yoctozepto | complicated, I know | 07:25 |
yoctozepto | also, there is this job that runs in NTT | 07:26 |
yoctozepto | which I have no idea what it tests because I have not received any e-mail back | 07:26 |
jopdorp | Right | 07:26 |
jopdorp | We don't have access to that source code? | 07:26 |
yoctozepto | nope | 07:26 |
yoctozepto | it's some black box | 07:26 |
jopdorp | Weird | 07:27 |
yoctozepto | yup, but NTT really is not obliged to tell us | 07:27 |
yoctozepto | I hoped they would tell me | 07:27 |
jopdorp | The functional tests are supposed to be unit tests? | 07:27 |
yoctozepto | but I am not planning to write to all NTT folks with questions, already wrote to 3 addresses | 07:28 |
yoctozepto | apart from the mailing list itself | 07:28 |
yoctozepto | nope, the unit tests are unit tests | 07:28 |
yoctozepto | they are there | 07:28 |
yoctozepto | in these tox-py36/8 jobs | 07:28 |
jopdorp | Should we at some point migrate the integration tests to tempest and write unit tests in our functional tests? | 07:28 |
yoctozepto | our current functional is between what normally is functional and integration | 07:29 |
yoctozepto | because in functional one expects to still try to isolate parts | 07:29 |
jopdorp | I guess I'm not clear on what should be the difference between functional and integration tests then | 07:29 |
yoctozepto | well, in unit tests you fake the code state (functions environments) and test code parts (functions) | 07:30 |
yoctozepto | in functional testing you fake the app environment and test the app | 07:30 |
jopdorp | Then unit tests one class, functional tests multiple classes, but all inside out project and integration tests also use a live keystone and nova? | 07:30 |
jopdorp | Our* project | 07:31 |
yoctozepto | so, the assumption would be you don't actually spin up nova for masakari functional testing | 07:31 |
jopdorp | Yeah got it | 07:31 |
jopdorp | And we do | 07:31 |
yoctozepto | functional tests actually "run the apps" | 07:31 |
yoctozepto | yup, that's it | 07:31 |
yoctozepto | and that should be done via tempest jobs | 07:31 |
yoctozepto | but then again the actual coverage of integration | 07:31 |
yoctozepto | is not that great | 07:31 |
yoctozepto | it's a good point | 07:32 |
yoctozepto | but I'm afraid we are extremely understaffed | 07:32 |
yoctozepto | to do that AND do something visible to the users | 07:32 |
yoctozepto | but still, I am tempted to improve testing coverage | 07:32 |
yoctozepto | always :-) | 07:32 |
jopdorp | Hehe | 07:32 |
jopdorp | Yeah tests can be relaxing to write | 07:33 |
yoctozepto | https://assets.mugglenet.com/wp-content/uploads/2016/01/Always.gif | 07:33 |
jopdorp | Haha | 07:33 |
yoctozepto | not only that, but the peace of mind one can get from knowing the testing pipeline and coverage are sane | 07:33 |
jopdorp | Are there coverage reports somewhere? | 07:33 |
yoctozepto | not sure, but they are only ever calculated for the unit tests I think | 07:34 |
yoctozepto | try `tox -e cover` | 07:34 |
jopdorp | Ok | 07:34 |
jopdorp | I don't understand why | 07:34 |
jopdorp | Any test framework usually has coverage reports right? | 07:35 |
jopdorp | Most stuff I do for myself has all three kinds of tests using the same framework | 07:36 |
jopdorp | Then you can generate the coverage reports separately, but also the combined coverage | 07:36 |
yoctozepto | I am pretty sure the limitation is fictitious and boils down to the general lack of order :-) | 07:37 |
jopdorp | Yeah | 07:37 |
jopdorp | Lol | 07:37 |
jopdorp | Off-topic | 07:38 |
jopdorp | I'm hapoy that they finally merged in my s3 backup driver for cinder :p | 07:38 |
yoctozepto | well, congrats! | 07:38 |
yoctozepto | then more time for masakari! :D | 07:39 |
jopdorp | Haha yes! | 07:39 |
jopdorp | I'm also happy we don't have as complicated politics as there | 07:39 |
yoctozepto | well, it would be impractical to apply anything now with the current developer base | 07:40 |
yoctozepto | so running off common sense only | 07:40 |
jopdorp | Yeah | 07:41 |
yoctozepto | thank you for the meeting jopdorp | 07:42 |
jopdorp | I think we can close the meeting | 07:42 |
yoctozepto | #endmeeting | 07:42 |
*** openstack changes topic to "This channel is *LOGGED* | IRC meetings on Tuesdays @ 07:00 UTC | Whiteboard: https://etherpad.opendev.org/p/masakari-whiteboard" | 07:42 | |
jopdorp | Thank you! | 07:42 |
openstack | Meeting ended Tue Feb 9 07:42:37 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 07:42 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/masakari/2021/masakari.2021-02-09-07.00.html | 07:42 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/masakari/2021/masakari.2021-02-09-07.00.txt | 07:42 |
openstack | Log: http://eavesdrop.openstack.org/meetings/masakari/2021/masakari.2021-02-09-07.00.log.html | 07:42 |
yoctozepto | jopdorp: nice sync! | 07:42 |
*** coreycb has quit IRC | 11:10 | |
*** uneek has quit IRC | 11:10 | |
*** uneek has joined #openstack-masakari | 11:11 | |
*** jopdorp has quit IRC | 11:11 | |
*** jopdorp has joined #openstack-masakari | 11:11 | |
*** coreycb has joined #openstack-masakari | 11:11 | |
*** jopdorp has quit IRC | 12:08 | |
*** coreycb has quit IRC | 12:08 | |
*** vishalmanchanda has quit IRC | 12:09 | |
*** uneek has quit IRC | 12:09 | |
*** vishalmanchanda has joined #openstack-masakari | 12:10 | |
*** coreycb has joined #openstack-masakari | 12:10 | |
*** jopdorp has joined #openstack-masakari | 12:11 | |
*** uneek has joined #openstack-masakari | 12:11 | |
*** gmann is now known as gmann_afk | 22:13 | |
*** vishalmanchanda has quit IRC | 23:15 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!