Tuesday, 2021-02-09

*** openstackgerrit has quit IRC00:49
*** openstackstatus has quit IRC01:20
*** openstack has joined #openstack-masakari01:24
*** ChanServ sets mode: +o openstack01:24
*** vishalmanchanda has joined #openstack-masakari06:56
yoctozepto#startmeeting masakari07:00
openstackMeeting 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:00
*** openstack changes topic to " (Meeting topic: masakari)"07:00
openstackThe meeting name has been set to 'masakari'07:00
yoctozepto#topic Roll-call07:00
*** openstack changes topic to "Roll-call (Meeting topic: masakari)"07:00
yoctozepto\o/07:00
jopdorpo/07:01
yoctozeptohi jopdorp07:02
yoctozeptosuzhengwei is on holidays (lunar new year celebration) so let's start07:02
yoctozepto#topic Agenda07:02
*** openstack changes topic to "Agenda (Meeting topic: masakari)"07:02
yoctozepto* Roll-call07:02
yoctozepto* Agenda07:02
yoctozepto* Announcements07:02
yoctozepto* Review action items from the last meeting07:02
yoctozepto* CI status07:02
yoctozepto* Backports pending reviews07:02
yoctozepto* Release planning https://etherpad.opendev.org/p/masakari-wallaby-vptg07:02
yoctozepto* Open discussion07:02
yoctozepto#topic Announcements07:03
*** openstack changes topic to "Announcements (Meeting topic: masakari)"07:03
yoctozeptoI have none07:03
jopdorpMe neither07:03
yoctozeptowe are at R-907:03
yoctozeptoso it's very very close to freeze and release07:04
yoctozeptoin fact feature freeze and the 3rd milestone is in 4 weeks07:04
yoctozeptoneed to merge some features!07:04
jopdorpOk07:04
yoctozepto#topic Review action items from the last meeting07:04
*** openstack changes topic to "Review action items from the last meeting (Meeting topic: masakari)"07:04
yoctozeptothere were none07:04
yoctozepto#topic CI status07:04
*** openstack changes topic to "CI status (Meeting topic: masakari)"07:04
yoctozeptogreen now07:04
yoctozeptowe were hit by alembic upgrade that caused taskflow to fail07:05
yoctozeptobut that was quickly handled07:05
yoctozepto#topic Backports pending reviews07:05
*** openstack changes topic to "Backports pending reviews (Meeting topic: masakari)"07:05
yoctozeptoand there are none!07:05
jopdorpHa!07:05
yoctozepto#topic Release planning https://etherpad.opendev.org/p/masakari-wallaby-vptg07:05
*** openstack changes topic to "Release planning https://etherpad.opendev.org/p/masakari-wallaby-vptg (Meeting topic: masakari)"07:05
yoctozeptoany progress on these points?07:06
jopdorpWhat about the features we should get merged?07:06
yoctozeptoright07:07
yoctozeptoI guess the enabling/disabling segments is very close07:07
yoctozeptowe just need to do it nicely07:07
yoctozeptoor as nice as we can afford to07:07
yoctozeptoothers are a bit further off07:08
yoctozeptogladly this cycle was nice for its bugfixes and I have some pending ones up my sleeve07:08
yoctozeptobut that's about it from me - could not get enough priority on it07:08
yoctozeptowell, we still have 4 weeks till freeze07:09
yoctozeptoand I will accept freeze exemptions if changes are safe enough not to break the whole thing07:09
jopdorpI did creste add a blueprint that goes with the auto reenable hosts a while ago07:11
jopdorpCreate*07:11
yoctozeptoah, yes, I remember07:12
yoctozeptoI think I did not get much time to digest it though07:12
yoctozeptodo you have a prototype implementation to see as well?07:12
jopdorpNo07:12
jopdorpBut I could make it07:12
jopdorpNot sure l'll be able to get it into the release though07:13
jopdorpAlthough in the end a lot can be done in 4 weeks07:13
yoctozeptothat's true07:14
yoctozeptoI have one important deadline this week so can't promise anything about reviewing things07:15
jopdorpOk07:15
yoctozepto(though I sometimes relax by reviewing changes)07:15
jopdorpShould I have a look st enabling/disabling segments?07:16
yoctozeptoanyhow, please be welcome to propose a prototype07:16
yoctozeptoat least it will be ready for the next cycle07:16
yoctozeptoI think you did07:16
jopdorpYeah07:16
yoctozeptoyou can check it again though07:16
yoctozeptoI had some comments07:16
yoctozeptoin the client07:16
jopdorpIf su is on vacation I may be able to create a new patch07:17
jopdorpOr is that agaonst etiquette? :P07:17
yoctozeptoif you know how to tackle the issue, then please do07:18
yoctozeptowe can always revert07:18
jopdorpOk07:18
yoctozeptoI think the priority is to get the feature in07:18
yoctozeptonot dwell on who worked the most on it07:18
jopdorpYeah07:19
yoctozeptoall right07:19
yoctozepto#topic Open discussion07:19
*** openstack changes topic to "Open discussion (Meeting topic: masakari)"07:19
yoctozeptoif there is anything else... I'm all ears07:19
jopdorpNothing here07:20
jopdorpOh07:20
jopdorpMaybe this07:20
jopdorpDo you have any idea of the tempest tests?07:20
jopdorpIs it our responsibility to uodate those too?07:21
jopdorpUpdate*07:21
jopdorpDo they even exist?07:21
yoctozeptothe story is the following07:23
yoctozeptoif you look closely at our functional tests job07:24
yoctozeptoit's not the expected functional tests job07:24
yoctozeptoit actually sets up the whole environment with devstack07:24
yoctozeptoand runs "functional tests"07:24
yoctozeptothey are almost like integration tests but their coverage is a tad bit less than what one would expect from integration tests07:25
jopdorpok07:25
yoctozeptoso we don't have masakari in tempest07:25
yoctozeptobut this job kind of aspires to do that07:25
yoctozeptocomplicated, I know07:25
yoctozeptoalso, there is this job that runs in NTT07:26
yoctozeptowhich I have no idea what it tests because I have not received any e-mail back07:26
jopdorpRight07:26
jopdorpWe don't have access to that source code?07:26
yoctozeptonope07:26
yoctozeptoit's some black box07:26
jopdorpWeird07:27
yoctozeptoyup, but NTT really is not obliged to tell us07:27
yoctozeptoI hoped they would tell me07:27
jopdorpThe functional tests are supposed to be unit tests?07:27
yoctozeptobut I am not planning to write to all NTT folks with questions, already wrote to 3 addresses07:28
yoctozeptoapart from the mailing list itself07:28
yoctozeptonope, the unit tests are unit tests07:28
yoctozeptothey are there07:28
yoctozeptoin these tox-py36/8 jobs07:28
jopdorpShould we at some point migrate the integration tests to tempest and write unit tests in our functional tests?07:28
yoctozeptoour current functional is between what normally is functional and integration07:29
yoctozeptobecause in functional one expects to still try to isolate parts07:29
jopdorpI guess I'm not clear on what should be the difference between functional and integration tests then07:29
yoctozeptowell, in unit tests you fake the code state (functions environments) and test code parts (functions)07:30
yoctozeptoin functional testing you fake the app environment and test the app07:30
jopdorpThen 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
jopdorpOur* project07:31
yoctozeptoso, the assumption would be you don't actually spin up nova for masakari functional testing07:31
jopdorpYeah got it07:31
jopdorpAnd we do07:31
yoctozeptofunctional tests actually "run the apps"07:31
yoctozeptoyup, that's it07:31
yoctozeptoand that should be done via tempest jobs07:31
yoctozeptobut then again the actual coverage of integration07:31
yoctozeptois not that great07:31
yoctozeptoit's a good point07:32
yoctozeptobut I'm afraid we are extremely understaffed07:32
yoctozeptoto do that AND do something visible to the users07:32
yoctozeptobut still, I am tempted to improve testing coverage07:32
yoctozeptoalways :-)07:32
jopdorpHehe07:32
jopdorpYeah tests can be relaxing to write07:33
yoctozeptohttps://assets.mugglenet.com/wp-content/uploads/2016/01/Always.gif07:33
jopdorpHaha07:33
yoctozeptonot only that, but the peace of mind one can get from knowing the testing pipeline and coverage are sane07:33
jopdorpAre there coverage reports somewhere?07:33
yoctozeptonot sure, but they are only ever calculated for the unit tests I think07:34
yoctozeptotry `tox -e cover`07:34
jopdorpOk07:34
jopdorpI don't understand why07:34
jopdorpAny test framework usually has coverage reports right?07:35
jopdorpMost stuff I do for myself has all three kinds of tests using the same framework07:36
jopdorpThen you can generate the coverage reports separately, but also the combined coverage07:36
yoctozeptoI am pretty sure the limitation is fictitious and boils down to the general lack of order :-)07:37
jopdorpYeah07:37
jopdorpLol07:37
jopdorpOff-topic07:38
jopdorpI'm hapoy that they finally merged in my s3 backup driver for cinder :p07:38
yoctozeptowell, congrats!07:38
yoctozeptothen more time for masakari! :D07:39
jopdorpHaha yes!07:39
jopdorpI'm also happy we don't have as complicated politics as there07:39
yoctozeptowell, it would be impractical to apply anything now with the current developer base07:40
yoctozeptoso running off common sense only07:40
jopdorpYeah07:41
yoctozeptothank you for the meeting jopdorp07:42
jopdorpI think we can close the meeting07:42
yoctozepto#endmeeting07: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
jopdorpThank you!07:42
openstackMeeting ended Tue Feb  9 07:42:37 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2021/masakari.2021-02-09-07.00.html07:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2021/masakari.2021-02-09-07.00.txt07:42
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2021/masakari.2021-02-09-07.00.log.html07:42
yoctozeptojopdorp: nice sync!07:42
*** coreycb has quit IRC11:10
*** uneek has quit IRC11:10
*** uneek has joined #openstack-masakari11:11
*** jopdorp has quit IRC11:11
*** jopdorp has joined #openstack-masakari11:11
*** coreycb has joined #openstack-masakari11:11
*** jopdorp has quit IRC12:08
*** coreycb has quit IRC12:08
*** vishalmanchanda has quit IRC12:09
*** uneek has quit IRC12:09
*** vishalmanchanda has joined #openstack-masakari12:10
*** coreycb has joined #openstack-masakari12:10
*** jopdorp has joined #openstack-masakari12:11
*** uneek has joined #openstack-masakari12:11
*** gmann is now known as gmann_afk22:13
*** vishalmanchanda has quit IRC23:15

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!