Wednesday, 2020-09-02

*** baojg has quit IRC00:09
*** baojg has joined #openstack-meeting-alt00:10
*** vishakha has quit IRC00:30
*** ayoung has quit IRC00:43
*** ayoung has joined #openstack-meeting-alt00:46
*** rcernin_ has joined #openstack-meeting-alt00:46
*** rcernin has quit IRC00:47
*** masahito has joined #openstack-meeting-alt01:04
*** tmazur has quit IRC01:10
*** ijw__ has quit IRC01:20
*** ijw has joined #openstack-meeting-alt01:20
*** ayoung has quit IRC01:29
*** ayoung has joined #openstack-meeting-alt01:30
*** ayoung has quit IRC01:34
*** baojg has quit IRC02:32
*** baojg has joined #openstack-meeting-alt02:33
*** rcernin_ has quit IRC03:19
*** rcernin_ has joined #openstack-meeting-alt03:35
*** masahito has quit IRC03:40
*** whoami-rajat__ has joined #openstack-meeting-alt03:55
*** apetrich has joined #openstack-meeting-alt04:36
*** masahito has joined #openstack-meeting-alt04:38
*** apetrich has quit IRC04:41
*** vishalmanchanda has joined #openstack-meeting-alt04:55
*** gyee has quit IRC05:07
*** baojg has quit IRC05:12
*** baojg has joined #openstack-meeting-alt05:13
*** kevinz has joined #openstack-meeting-alt05:34
*** slaweq has joined #openstack-meeting-alt05:53
*** lamt has quit IRC06:00
*** jopdorp has quit IRC06:01
*** jopdorp has joined #openstack-meeting-alt06:02
*** baojg has quit IRC06:02
*** rajinir__ has joined #openstack-meeting-alt06:02
*** rajinir has quit IRC06:03
*** rajinir__ is now known as rajinir06:03
*** baojg has joined #openstack-meeting-alt06:03
*** slaweq has quit IRC06:18
*** ralonsoh has joined #openstack-meeting-alt06:39
*** apetrich has joined #openstack-meeting-alt06:41
*** rcernin_ has quit IRC06:51
*** rcernin_ has joined #openstack-meeting-alt06:55
*** slaweq has joined #openstack-meeting-alt06:55
*** jtomasek has joined #openstack-meeting-alt07:00
*** ralonsoh has quit IRC07:04
*** ralonsoh has joined #openstack-meeting-alt07:09
*** e0ne has joined #openstack-meeting-alt07:26
*** rcernin_ has quit IRC07:35
*** tosky has joined #openstack-meeting-alt07:38
*** ralonsoh has quit IRC07:43
*** baojg has quit IRC07:53
*** baojg has joined #openstack-meeting-alt07:53
*** baojg has quit IRC07:59
*** rcernin_ has joined #openstack-meeting-alt08:40
*** rcernin_ has quit IRC08:46
*** derekh has joined #openstack-meeting-alt09:05
*** baojg has joined #openstack-meeting-alt09:28
*** zzzeek has quit IRC09:32
*** zzzeek has joined #openstack-meeting-alt09:33
*** zzzeek has quit IRC09:48
*** zzzeek has joined #openstack-meeting-alt09:49
*** baojg has quit IRC09:54
*** vhari has joined #openstack-meeting-alt09:59
*** zzzeek has quit IRC10:08
*** zzzeek has joined #openstack-meeting-alt10:10
*** ijw has quit IRC10:19
*** ijw has joined #openstack-meeting-alt10:20
*** ijw has quit IRC10:25
*** ijw has joined #openstack-meeting-alt10:39
*** ijw has quit IRC10:44
*** lpetrut has joined #openstack-meeting-alt10:47
*** zzzeek has quit IRC10:57
*** zzzeek has joined #openstack-meeting-alt11:00
*** masahito has quit IRC11:00
*** sridharg has joined #openstack-meeting-alt11:03
*** ijw has joined #openstack-meeting-alt11:11
*** ijw has quit IRC11:15
*** ijw has joined #openstack-meeting-alt11:42
*** ijw has quit IRC11:47
*** raildo has joined #openstack-meeting-alt11:56
*** derekh has quit IRC12:09
*** sridharg has quit IRC12:12
*** ijw has joined #openstack-meeting-alt12:14
*** dave-mccowan has joined #openstack-meeting-alt12:19
*** ijw has quit IRC12:19
*** lbragstad has quit IRC12:35
*** lbragstad has joined #openstack-meeting-alt12:38
*** ijw has joined #openstack-meeting-alt12:46
*** derekh has joined #openstack-meeting-alt13:03
*** tmazur has joined #openstack-meeting-alt13:31
*** enriquetaso has joined #openstack-meeting-alt13:47
*** kaisers has joined #openstack-meeting-alt13:50
*** rosmaita has joined #openstack-meeting-alt13:51
*** whoami-rajat has joined #openstack-meeting-alt13:58
*** Liang__ has joined #openstack-meeting-alt13:58
*** Liang__ is now known as LiangFang13:59
*** ijw has quit IRC14:00
rosmaita#startmeeting cinder14:00
openstackMeeting started Wed Sep  2 14:00:20 2020 UTC and is due to finish in 60 minutes.  The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: cinder)"14:00
openstackThe meeting name has been set to 'cinder'14:00
rosmaita#topic roll call14:00
*** openstack changes topic to "roll call (Meeting topic: cinder)"14:00
whoami-rajatHi14:00
e0nehi14:00
kaisershi14:00
enriquetasoji14:00
LiangFanghi14:00
eharneyhi14:00
enriquetasohi*14:00
smcginnis.o.14:00
hemnamep14:00
rosmaitagood turnout14:01
rosmaita#link https://etherpad.openstack.org/p/cinder-victoria-meetings14:01
rosmaita#topic announcements14:01
*** openstack changes topic to "announcements (Meeting topic: cinder)"14:01
rosmaitareminder about Forum brainstorming14:02
rosmaitai sent something to the ML to solicit ideas from operators and other cinder users14:02
rosmaita#link http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016659.html14:02
rosmaitaand here is where you can add ideas:14:02
rosmaita#link https://etherpad.opendev.org/p/2020-Wallaby-cinder-brainstorming14:02
*** sfernand has joined #openstack-meeting-alt14:03
m5zhi =]14:03
rosmaitawe will pick what topics to propose at next week's meeting14:03
rajiniro/14:03
rosmaitain the meantime, you need to be registered for the Summit to attend the Forum14:03
rosmaitait's free, so go ahead and register14:04
rosmaita#link https://openinfrasummit2020.eventbrite.com/14:04
rosmaitaalso, we have the Wallaby PTG coming up14:05
enriquetasois the deadline for proposing topics on Wed 9 sept ?14:05
rosmaitaenriquetaso: i thought friday that week?14:05
enriquetasothanks!14:05
rosmaitabut if you have an idea, add it to the forum etherpad14:06
enriquetaso++14:06
rosmaitaand the wallaby PTG etherpad is14:06
rosmaita#link https://etherpad.opendev.org/p/wallaby-ptg-cinder-planning14:06
rosmaita#topic updates - releases14:07
*** openstack changes topic to "updates - releases (Meeting topic: cinder)"14:07
rosmaitaok, os-brick for victoria has to be released tomorrow14:07
rosmaitawe have one patch in the gate now14:07
rosmaita#link https://review.opendev.org/73037614:07
rosmaitaprevious release was 3.2.114:08
rosmaitathis will be 4.0.0 because we removed a bunch of connectors for drivers that were removed from cinder14:08
e0nethanks everybody for the feedback to the patch above14:08
rosmaitawe have some stuff piled up for stable/ussuri and train in os-brick14:08
rosmaitaso i will put up patches for those releases soon14:09
rosmaitanext up: python-cinderclient release next week14:09
rosmaitasomeone please look at this one! it's a 2 line change! cinderclient support for mv 3.61 (which has merged on cinder side)14:09
rosmaita#link https://review.opendev.org/#/c/742994/14:09
rosmaitathe big thing to focus on is cinder patch for per-project default volume types:14:09
rosmaita#link https://review.opendev.org/#/c/737707/14:10
* e0ne is feeling like a release-blocker person14:10
rosmaitabecause that has a cinderclient support patch:14:10
rosmaita#link https://review.opendev.org/73922314:10
hemnalooks like that patch only bumps the microversion number ?14:10
rosmaitahemna: yes14:10
e0nehemna: yes14:10
hemnaok done14:11
rosmaitawhoami-rajat has revised https://review.opendev.org/#/c/742994/14:11
e0nesmcginnis, hemna: thank you!14:11
rosmaitaso it could use some eyes, need to make sure it's acceptable so that we know the cinderclient side is correct14:12
whoami-rajatrosmaita, that's not the patch ...14:12
*** LiangFang has quit IRC14:12
rosmaitaoops14:12
whoami-rajat#link https://review.opendev.org/#/c/739223/14:12
rosmaita#link https://review.opendev.org/#/c/737707/14:12
rosmaitawe need the cinder-side patch merged first, i think14:12
rosmaitaso to be completely clear: these are really high priority patches14:13
rosmaita#link https://review.opendev.org/#/c/737707/14:13
whoami-rajatoh the API one14:13
whoami-rajatok14:13
rosmaita#link https://review.opendev.org/73922314:13
rosmaitaok, next priority are other cinder features for victoria14:13
rosmaitause the blueprints:14:13
rosmaita#link https://blueprints.launchpad.net/cinder/victoria14:13
rosmaitabut i will point out some really easy reviews (and they have been sitting quite a while ...)14:14
rosmaitasupport zstd compression:14:14
rosmaita#link https://review.opendev.org/72676514:14
rosmaitaextra-specs support for volume local cache:14:14
rosmaita#link https://review.opendev.org/#/c/700799/14:14
rosmaitastop sending notifications to deprecated nonstandard publisher_id14:14
rosmaita#link https://review.opendev.org/74754014:14
rosmaitahemna: would like you to take a look ^^14:14
*** Liang__ has joined #openstack-meeting-alt14:14
hemnaok14:14
rosmaitaremove deprecated rbd option for OSSN-008514:14
rosmaita#link https://review.opendev.org/#/c/747494/14:14
rosmaitaand there are the driver features14:14
hemnaah yes cool14:15
rosmaitaok, so to be completely clear: top priority is whoami-rajat's per-project-default-type stuff14:15
rosmaitabecause we must release cinderclient next week14:15
rosmaitaso no possibility of FFE to help there14:16
rosmaitaand a reminder to people with driver features14:16
rosmaitareviewing other people's patches will help you get yours reviewed faster14:16
rosmaita(we do pay attention)14:16
hemnalots of failures on the per project default type patch :(14:16
*** ijw has joined #openstack-meeting-alt14:17
rosmaitayeah, the gate has been really unstable14:17
rosmaitaany other announcements?14:17
rosmaita(that's all from me)14:18
rosmaita#topic RBD connector fix 14:18
*** openstack changes topic to "RBD connector fix  (Meeting topic: cinder)"14:18
rosmaitathere was some discussion about this today in the cinder channel14:18
rosmaitait may be possible to simplify the patch, but it requires more testing against various ceph versions14:19
rosmaita#link https://review.opendev.org/#/c/730376/14:20
e0neI tested only with octopus and nautilus14:20
e0nethe idea is to test against supported versions to check if [global] section works for every supported ceph release14:21
rosmaitaso to be clear,the patch is backward compatible right now, and since the issue has only been reported for octopus, we should be OK14:21
*** ijw has quit IRC14:21
rosmaitabut it may be possible to remove the conditional logic14:22
rosmaitaso for ceph-inclined people, that's something to take a look at14:22
rosmaitae0ne: anything else?14:22
e0nerosmaita: that's all for me14:22
e0neI raised this topic only because release deadline14:22
rosmaitaand quite appropriately, too14:23
rosmaita#topic service creation race condition14:23
*** openstack changes topic to "service creation race condition (Meeting topic: cinder)"14:23
rosmaita#link https://bugs.launchpad.net/cinder/+bug/189133014:23
openstackLaunchpad bug 1891330 in Cinder "Duplicate Cinder services DB entries after upgrade" [Low,Triaged]14:23
rosmaitai mostly just want to raise some awareness14:23
rosmaitathere is an abandoned patch (link in the bug)14:23
rosmaitabut the major objection was that cinder didn't support A/A yet14:23
rosmaitawhich isn't the case any more14:23
e0neI'm all for restoring proposed patch to add unique constraints into the DB14:24
rosmaitawell, ordinarily, i would be too, but my experience this past week is making me a bit gun-shy14:24
rosmaitaas we will discuss in a minute14:24
rosmaitabut, it does look like an easy fix14:25
rosmaita#topic ussuri upgrade issue14:25
*** openstack changes topic to "ussuri upgrade issue (Meeting topic: cinder)"14:25
rosmaitathis is the issue14:26
rosmaita#link https://bugs.launchpad.net/cinder/+bug/189310714:26
openstackLaunchpad bug 1893107 in Cinder "Upgrade to Ussuri fails if deleted volumes exist prior to Train" [High,In progress] - Assigned to Mohammed Naser (mnaser)14:26
rosmaitawell, i spent a bunch of time trying to figure out a way to fix this that was low-impact on operators14:27
rosmaitaand i thought i had a solution14:27
rosmaitabut, wound up going back to the original proposal14:27
rosmaitathe issue in a nutshell is that the online migrations to set __DEFAULT__ as the volume type for all untyped volumes/snapshots in Train14:27
rosmaitadid not take into account the soft-deleted volumes/snapshots14:28
rosmaitaso when you try to upgrade to ussuri14:28
rosmaitaand the db_sync puts a non-nullability constraint on the columns14:28
rosmaitathe db_sync fails14:28
rosmaitathis is complicated by the fact that someone discovered a way to delete the __DEFAULT__ volume type in train14:28
rosmaitaso, we don't know for sure that it actually exists14:29
rosmaitabut, the issue only applies to people who upgraded from Stein to Train without first purging the database14:29
rosmaita(which may actually be a lot of people)14:29
rosmaitaanyway, the best thing i could come up with are these patches:14:30
rosmaita#link https://review.opendev.org/#/c/748481/14:30
whoami-rajat(but if they don't have issue purging it then they can purge anytime and upgrade successfully)14:30
rosmaita#link https://review.opendev.org/#/c/748482/14:30
rosmaitaso, my first ask is for careful reviews of those patches14:31
rosmaitathe code change is simple, and there are tests14:31
e0newhoami-rajat: sometimes operators can't do purge because they use deleted volumes for billing14:31
rosmaitabut there is manual operator intervention required when you don't do the purge14:31
rosmaitaso PLEASE read the release notes carefully to see if i covered everything14:31
whoami-rajate0ne, yep, that's why i said if they don't have issue/don't need that info14:31
rosmaitaand if you are interested in all the crazy schemes i thought of that didn't work, you can read the sorry story here:14:32
hemnafwiw, we do purging14:32
rosmaita#link https://etherpad.opendev.org/p/ussuri-upgrade-issue14:32
rosmaitayes, so this shows a weakness in grenade testing of T->U upgrades14:33
rosmaitathe problem only happens in S->T->U upgrades14:33
rosmaitabut i am not going to propose a 3 stage grenade job14:34
rosmaitathe reason i had this on the agenda was that i was going to propose using some of the "placeholder" db migrations14:35
rosmaitabut it turned out that wasn't going to really help14:35
rosmaitaso we are left with really long release notes explaining how to do it yourself14:35
rosmaitathat's all from me, unless anyone has questions14:36
whoami-rajatexcluding the part that they've renamed the __DEFAULT__ type, they just have to run migrations14:36
rosmaita#topic open discussion14:38
*** openstack changes topic to "open discussion (Meeting topic: cinder)"14:38
kaisersIf i may, just a small note:14:38
kaisersOur CI (Quobyte) is one of the failing 3rdparty CIs.14:39
kaisersI've been trying to fix it in the last but that did not work out.14:39
kaisersI'm currently setting up a completely new CI stack14:39
kaisersSo i hope i get this back online in the next days14:39
kaisers<done>14:39
smcginnisThanks kaisers14:40
rosmaitaok, thanks for the update14:40
whoami-rajati would like some feedback on the idea to backport https://review.opendev.org/#/c/741498/14:40
whoami-rajatthis doesn't change anything on a normal deployment just this allows the operators to delete the __DEFAULT__ type if they've14:40
whoami-rajatset a valid default_volume_type in the conf14:40
rosmaitaon the plus side, that would make the behavior consistent from Train through Victoria14:41
rosmaitaand it doesn't really impact the upgrade issue we just talked about14:41
hemnathat patch makes setting the default_volume_type conf entry manditory14:41
hemnawhich might bust older deployments if you are backporting this14:42
rosmaitahow?14:42
whoami-rajatyep, and it defaults to __DEFAULT__14:42
hemnaif that setting isn't in cinder.conf14:42
hemnawhat happens?14:42
hemnasince it's manditory14:42
hemnacinder won't start?14:42
whoami-rajat^^14:42
rosmaitawell, if they don't set it, they get __DEFAULT__14:42
rosmaitaif they do set it, they get whatever they set14:43
hemnaso then it's not manditory14:43
whoami-rajathemna, https://review.opendev.org/#/c/741498/16/cinder/common/config.py14:43
eharneyi think mandatory here means it isn't set to empty/none ?14:43
rosmaitawell, depends on what you mean14:43
* hemna has a confusion14:43
rosmaitait's required but it also has a default value14:43
hemnaIMHO manditory means that you must set it in cinder.conf and have a valid value14:43
hemnaif it has a default value then it's not manditory to set it14:43
e0nehemna: +114:44
hemnait's confusing14:44
whoami-rajatto preserve the current behavior, we have defaulted it to __DEFAULT__ so there14:45
whoami-rajat's no effort to set it manually14:45
whoami-rajatbut if you're going to set it, it should be a valid type14:45
whoami-rajatalso deleting the value set in default_volume_type is not allowed so we atleast have 1 type in deployment and don't allow untyped volumes14:46
rosmaitaof all the confusing things in cinder, this is like the least confusing thing i can think of! :)14:46
smcginnishemna: I had the same reaction. ;)14:47
rosmaitai think what it comes down to is that we want to encourage operators to set that config value14:48
*** ijw has joined #openstack-meeting-alt14:48
rosmaitabut, they don't have to14:48
rosmaitayou must have a default_volume_type correctly defined at all times, or you can't create volumes14:49
rosmaitawhether you let us define it as __DEFAULT__ or whether you do it yourself14:49
rosmaitaso that strikes me as "mandatory" in at least some aspect of the term14:49
whoami-rajatall these changes are a part of a bug saying operators/users get *confused* with the name __DEFAULT__ when they've a different default_volume_type set14:51
hemnaI guess it's just the wording that makes it confusing is all.14:51
smcginnisThe confusion is all based on the fact that we didn't do that right and should have kept __DEFAULT__ a hidden internal thing if someone didn't provide a type.14:52
hemnaif it's manditory, then the deployer must set it.   but he doesn't because there is a default.   hence the confusing.14:52
rosmaitait's not too late to revise the release note to be more clear14:52
*** eharney has left #openstack-meeting-alt14:52
rosmaitahttps://review.opendev.org/#/c/741498/16/releasenotes/notes/allow-deleting-__DEFAULT__-type-d35dfb5d89760b9b.yaml14:53
rosmaitaso, anyone interested in this issue, please read through ^^14:53
*** ijw has quit IRC14:53
rosmaitawe can get that clarified and then decide about the backports, squashing in the revised release note14:53
whoami-rajatthe reported bug mentions the train and ussuri releases so that's also a consideration to backport it14:56
rosmaitacoming up on 2 minutes left14:57
rosmaitaok, looks like we're done for today!14:58
rosmaitaPlease ... look at the release notes on the upgrade issue patches -- with Victoria release coming up, i think people will realize they need to upgrade to ussuri14:58
rosmaitahttps://review.opendev.org/#/c/748481/14:59
rosmaitahttps://review.opendev.org/#/c/748482/14:59
rosmaitaok, thanks everyone!  let's clear out so horizon can start on time14:59
rosmaitahappy reviewing!14:59
rosmaita#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:59
openstackMeeting ended Wed Sep  2 14:59:43 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-09-02-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-09-02-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-09-02-14.00.log.html14:59
*** belmoreira has joined #openstack-meeting-alt14:59
whoami-rajatThanks!15:00
e0ne#startmeeting horizon15:01
openstackMeeting started Wed Sep  2 15:01:00 2020 UTC and is due to finish in 60 minutes.  The chair is e0ne. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: horizon)"15:01
openstackThe meeting name has been set to 'horizon'15:01
e0nehi everybody15:01
tmazurhi o/15:01
vishalmanchandahi15:01
*** rosmaita has left #openstack-meeting-alt15:01
e0neok, let's start15:04
e0neI hope amotoki and Radomir will join us later15:04
e0ne#topic Notices15:04
*** openstack changes topic to "Notices (Meeting topic: horizon)"15:04
tmazurRadomir is on PTO15:04
e0netmazur: thanks for the information15:04
e0nePTG planing15:05
e0neplease, don't forget to register for PTG if you're going to attend it15:05
e0ne#link https://www.openstack.org/ptg/15:05
e0neregistration is free and fast enough15:06
e0nealso, there is our usual PTG planning etherpad15:06
e0ne#link https://etherpad.opendev.org/p/horizon-w-ptg15:06
e0nefeel free to add topics you would like to discuss15:07
e0neyou can find our timeslots in the etherpad15:07
e0neforgot to mention, it will be a virtual PTG again15:07
e0ne#topic Release priorities15:11
*** openstack changes topic to "Release priorities (Meeting topic: horizon)"15:11
e0ne#link https://releases.openstack.org/victoria/schedule.html15:11
e0newe're one week away from Victoria-3 milestone15:12
e0neonce we'll reach it, no more features will be allowed to merge15:12
e0neof course, FFE (Feature Freeze Exception) mechanism is still working but I would like to have everything merged before the deadline15:13
e0neyou can find a list of proposed patches with features in our therpad https://etherpad.opendev.org/p/horizon-release-priorities15:15
e0nes/therpad/etherpad15:15
e0nefeel free to add anything I missed15:15
vishalmanchandaCan I have a 2nd review on https://review.opendev.org/#/c/734161/(cinder-user-facing-messages) and https://review.opendev.org/#/c/708069/(refactor-error-messages)15:15
vishalmanchandaIf I missed anything i can cover-up it in a follow-up patch.15:16
e0nevishalmanchanda: I will review your patches tonight or tomorrow morning15:16
vishalmanchandae0ne: thanks.15:17
e0neIt will be great to have them merged15:17
e0nein this release :)15:17
vishalmanchandayeah15:17
e0neI hope, it will be a priority for all  cores to review new features15:19
e0netmazur: your reviews are welcome too :)15:19
tmazure0ne, as a former/hopefully future core, yep15:19
e0netmazur: :)15:19
*** ijw has joined #openstack-meeting-alt15:19
e0netmazur: I believe you know about angularized side more than all of us15:20
tmazurSpeaking of Angular! I have a question on AngularJS unit tests. Should I wait for the open discussion?15:20
e0netmazur: please15:21
tmazurSo first of all thanks for the merging this small patch on filters. I ran into an interesting fact while working on it. We do have 22 tests with "SPEC HAS NO EXPECTATIONS" which means that those tests are doing nothing right now.15:22
e0netmazur, vishalmanchanda:  do you have something to add about our future relese?15:23
tmazurOops, sorry. Please ignore until the open discussion15:23
vishalmanchandae0ne: nothing from my side.15:23
e0nevishalmanchanda: ok15:24
tmazurNothing from my side about future release15:24
*** ijw has quit IRC15:24
e0neI've got few more topics to discuss in our etherpad (tempest plugin and Chainese languages), but I would ike to to discuss it with Akihiro and Radomir too15:25
e0ne#topic Open Discussion15:25
*** openstack changes topic to "Open Discussion (Meeting topic: horizon)"15:25
e0netmazur: TBH, I don't surprised on it, we'd got some unit/integration tests which were broken from the beginning in the past :(15:26
e0netmazur: do you have a list of such tests?15:26
tmazurSo, the tests. I've made a quick research and it has to do with unresolved promises. Also they cannot be fixed all in once, each case is pretty unique.15:27
amotokihi, sorry for late.15:27
e0neamotoki: welcome!15:27
tmazurI can make the list, it could be easily extracted from jasmine results15:28
tmazurIt would be nice to make them work one by one, otherwise it's just confusing.15:29
*** Liang__ has quit IRC15:29
e0netmazur: +115:29
vishalmanchanda+1.15:29
tmazurI can start to work on it but I'm not sure about my current priorities. So apparently it hasn't to be scheduled to future release.15:30
e0netmazur: is any way to catch such tests on CI to prevent such issues in the future?15:31
tmazure0ne: we should catch these "SPEC HAS NO EXPECTATIONS" warnings.15:31
*** tosky has quit IRC15:31
e0necan we treat such warnings as errors on CI?15:32
amotokiin my understandng, it means no test actually.15:32
e0neamotoki: +115:32
tmazurtheoretically yes. I will tackle this as well15:32
e0netmazur: it will be awesome15:32
tmazurThat means unresolved promise, once it is resolved, a test fails with an error.15:33
tmazurBut in the current way, yes, no test at all15:34
amotokitmazur: I don't see any "SPEC HAS NO EXPECTATIONS" in our npm test result. how did you get the warning?15:36
tmazuramotoki, I was using jasmine15:36
amotokiI see. so cannot we avoid it with our current test runner?15:38
amotoki(I don't know JS test suite very much)15:38
tmazuramotoki, I don't know yet. My plan is to fix current 22 tests which are doing nothing and then to tackle how we can avoid this situation in future15:39
amotokitmazur: no problem. your plan sounds good.15:40
tmazurAlso, another question. What is the current situation on angularization? I can see there were some efforts on instances page a while ago. I understand it's not a high priority right now, but what is the optimistic plan?15:42
e0neremove angularjs?15:42
tmazurEssentially: do we still need it or not?15:42
e0neit's a joke15:42
tmazurHaha, you got me :D15:43
e0nehonestly, I don't know15:43
e0nefrom one side it would be good to to complete angularization15:43
e0nefrom other side, I don't like a lot to work with old almost unsupported framework15:44
tmazurit's understandable.15:44
amotokiI see one priority which is to close gaps in AngularJS panels used by default15:45
amotokilike Instance Launch form.15:45
e0neamotoki: that's what I was going to say15:45
tmazurand do not touch it anymore? :)15:45
amotokifor others it needs more discussion.15:46
amotokiOur current status comes from the lack of JS developers.15:46
tmazurI was just looking on ugly filtering system at instances page and was thinking how it would be easier to angularize it, only the filter or the whole page15:46
e0nelet's discuss it during the PTG15:48
e0neit's important topic15:48
tmazure0ne, Absolutely!15:48
amotokiagree15:48
e0neit doesn't mean I don't want to discuss it now or on the next meeting15:48
amotokione thing I would like to note is that there is no way to call Django form or page from angular pages15:48
e0neI mean that during virtual face-to-face on the PTG it will be more productive for this particular case15:49
amotokiso angular migration tends to be slow because we cannot switch it until the whole migration is completed.15:49
e0neamotoki: that's why I prefer to use modern frameworks like react or vue: they don't require to re-implement the whole page to start work15:50
amotokihehe15:50
e0ne:)15:51
*** ijw has joined #openstack-meeting-alt15:52
*** lpetrut has quit IRC15:53
tmazurok let's discuss it during the PTG15:53
*** belmoreira has quit IRC15:53
e0newe've got 5 minutes left15:54
e0nedoes anybody have anything to discuss?15:54
tmazurNothing more from my side15:54
amotokie0ne: I see you mentioned "tempest plugin and Chainese languages".15:54
vishalmanchandaI am working on this bug https://bugs.launchpad.net/horizon/+bug/1893305 and need some help.15:54
openstackLaunchpad bug 1893305 in OpenStack Dashboard (Horizon) "Details href still displayed when details is empty and redirect is false." [Undecided,New] - Assigned to Vishal Manchanda (vishalmanchanda)15:54
vishalmanchandabut we can discuss it in horizon channel.15:55
e0neamotoki: I moved them to the next meeting15:55
amotokie0ne: okay. I just wonder what is the topic about tempest plugin.15:55
e0neamotoki: QA team wants to merge our plugin (actually, only one test) into the tempest core15:56
amotokie0ne: ah, got it.15:56
*** ijw has quit IRC15:57
e0neamotoki: that's what they said to me, so I decided to discuss it with the whole horizon team15:57
e0newe're almost out of time15:58
e0nevishalmanchanda: we can move to our channel if you need to dicsuss something15:59
e0nethanks everybody for your contributions! see you next week15:59
e0ne#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:59
openstackMeeting ended Wed Sep  2 15:59:35 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-09-02-15.01.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-09-02-15.01.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-09-02-15.01.log.html15:59
vishalmanchandabye15:59
tmazurThanks everyone!15:59
amotokio/16:00
*** ijw has joined #openstack-meeting-alt16:00
*** ijw has quit IRC16:01
*** ijw has joined #openstack-meeting-alt16:01
*** enriquetaso has quit IRC16:40
*** enriquetaso has joined #openstack-meeting-alt16:56
*** derekh has quit IRC17:08
*** ayoung has joined #openstack-meeting-alt17:37
*** e0ne has quit IRC18:29
*** vishalmanchanda has quit IRC18:43
*** zzzeek has quit IRC19:17
*** zzzeek has joined #openstack-meeting-alt19:18
*** zzzeek has quit IRC19:25
*** zzzeek has joined #openstack-meeting-alt19:27
*** ajitha has joined #openstack-meeting-alt19:39
*** ajitha has left #openstack-meeting-alt19:40
*** e0ne has joined #openstack-meeting-alt19:51
*** zzzeek has quit IRC19:53
*** zzzeek has joined #openstack-meeting-alt19:56
*** apetrich has quit IRC20:07
*** gyee has joined #openstack-meeting-alt20:17
*** ijw has quit IRC20:34
*** ijw has joined #openstack-meeting-alt20:35
*** jtomasek has quit IRC20:42
*** e0ne has quit IRC20:44
*** zzzeek has quit IRC20:50
*** zzzeek has joined #openstack-meeting-alt20:51
*** dustinc has joined #openstack-meeting-alt20:58
*** rcernin_ has joined #openstack-meeting-alt21:07
*** rcernin_ has quit IRC21:12
*** ijw has quit IRC21:14
*** ijw has joined #openstack-meeting-alt21:14
*** rcernin_ has joined #openstack-meeting-alt22:16
*** raildo_ has joined #openstack-meeting-alt22:30
*** raildo has quit IRC22:32
*** enriquetaso has quit IRC22:58
*** tmazur has quit IRC23:03
*** rcernin_ has quit IRC23:04
*** rcernin has joined #openstack-meeting-alt23:04
*** dustinc has quit IRC23:08
*** lifeless has quit IRC23:29
*** irclogbot_3 has quit IRC23:29
*** irclogbot_0 has joined #openstack-meeting-alt23:33
*** whoami-rajat has quit IRC23:35
*** kopecmartin has quit IRC23:40
*** kopecmartin has joined #openstack-meeting-alt23:40

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