Wednesday, 2021-03-03

*** enriquetaso has quit IRC00:07
*** whoami-rajat has quit IRC00:15
*** enriquetaso has joined #openstack-meeting-alt00:16
*** tosky has quit IRC00:17
*** macz_ has quit IRC00:49
*** SotK has quit IRC00:58
*** SotK has joined #openstack-meeting-alt00:58
*** jinyuanliu has quit IRC01:04
*** jinyuanliu has joined #openstack-meeting-alt01:05
*** subbareddy has quit IRC01:08
*** gyee has quit IRC01:17
*** tmazur has quit IRC01:22
*** rcernin has quit IRC02:00
*** enriquetaso has quit IRC02:05
*** rcernin has joined #openstack-meeting-alt02:29
*** rcernin has quit IRC02:29
*** gagehugo has quit IRC02:29
*** enriquetaso has joined #openstack-meeting-alt02:30
*** rcernin has joined #openstack-meeting-alt02:30
*** gagehugo has joined #openstack-meeting-alt02:33
*** rcernin has quit IRC02:44
*** macz_ has joined #openstack-meeting-alt02:46
*** macz_ has quit IRC02:50
*** jhouser has quit IRC02:52
*** rcernin has joined #openstack-meeting-alt03:16
*** enriquetaso has quit IRC03:37
*** zzzeek has quit IRC04:17
*** zzzeek has joined #openstack-meeting-alt04:17
*** zzzeek has quit IRC04:22
*** zzzeek has joined #openstack-meeting-alt04:23
*** dviroel has quit IRC04:55
*** whoami-rajat has joined #openstack-meeting-alt04:58
*** vishalmanchanda has joined #openstack-meeting-alt05:27
*** ajitha has joined #openstack-meeting-alt05:48
*** miniroy has quit IRC05:48
*** zzzeek has quit IRC06:06
*** zzzeek has joined #openstack-meeting-alt06:41
*** bnemec has quit IRC06:41
*** bnemec has joined #openstack-meeting-alt06:49
*** ralonsoh has joined #openstack-meeting-alt07:37
*** rcernin has quit IRC07:44
*** browny has quit IRC08:24
*** tosky has joined #openstack-meeting-alt08:34
*** smyers has quit IRC08:34
*** smyers has joined #openstack-meeting-alt08:38
*** browny has joined #openstack-meeting-alt08:42
*** rdopiera has joined #openstack-meeting-alt09:26
*** gshippey has joined #openstack-meeting-alt10:15
*** lpetrut has joined #openstack-meeting-alt10:22
*** carloss has joined #openstack-meeting-alt10:49
*** dviroel has joined #openstack-meeting-alt11:05
*** zoharm has joined #openstack-meeting-alt11:11
*** jinyuanliu has quit IRC12:03
*** jinyuanliu has joined #openstack-meeting-alt12:03
*** GirishChilukuri has joined #openstack-meeting-alt13:14
*** GirishChilukuri has left #openstack-meeting-alt13:15
*** sangeet has joined #openstack-meeting-alt13:21
*** sangeet has left #openstack-meeting-alt13:21
*** kinpaa12389 has joined #openstack-meeting-alt13:22
*** e0ne has joined #openstack-meeting-alt13:45
*** GirishChilukuri has joined #openstack-meeting-alt13:49
*** enriquetaso has joined #openstack-meeting-alt13:50
*** almir-okato has joined #openstack-meeting-alt13:52
*** rosmaita has joined #openstack-meeting-alt13:54
*** amar7ibm_ has joined #openstack-meeting-alt13:58
rosmaita#startmeeting cinder14:00
openstackMeeting started Wed Mar  3 14:00:40 2021 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
toskyo/14:00
enriquetasohi14:00
geguileohi! o/14:00
rosmaita#topic roll call14:00
*** openstack changes topic to "roll call (Meeting topic: cinder)"14:00
whoami-rajatHi14:00
e0nehi14:00
zoharmo714:01
kinpaa12389hi14:01
eharneyhi14:01
rosmaitalooks like a good turnout, let's get started14:01
rosmaita#link https://etherpad.openstack.org/p/cinder-wallaby-meetings14:02
rosmaita#topic announcements14:02
*** openstack changes topic to "announcements (Meeting topic: cinder)"14:02
rosmaitawallaby os-brick release this week (that is, tomorrow)14:02
*** thgcorrea has joined #openstack-meeting-alt14:02
rosmaitacinderclient release next week14:02
rosmaitawallaby feature freeze next week also14:02
rosmaitaso, review priorities are:14:02
rosmaitatoday: os-brick14:02
rosmaitathen, cinderclient and features14:03
rosmaitause launchpad to find features to review14:03
rosmaita#link https://blueprints.launchpad.net/cinder/wallaby14:03
rosmaitaif you have a feature that's not in there, let me know immediately14:03
*** sfernand has joined #openstack-meeting-alt14:04
rosmaitanote to driver developer/maintainers: even if you are not a core, you can review other people's drivers14:04
rosmaitawe have helpful info in the cinder docs if you need suggestions on what to look for14:04
rosmaitathough, you probably know since you are working on your own driver14:05
jungleboyjo/14:05
rosmaita#topic wallaby os-brick release14:05
*** openstack changes topic to "wallaby os-brick release (Meeting topic: cinder)"14:05
rosmaitaok, some patches we need to get in (and that obviously need reviews)14:06
rosmaitafix nvmeof connector regression14:06
rosmaita#link https://review.opendev.org/c/openstack/os-brick/+/77708614:06
rosmaitait's got a -1 from me, but just for minor stuff ... it looks otherwise ok to me14:06
rosmaitait has passed zuul14:07
rosmaitaand passed the mellanox SPDK CI, which consumes the connector in a "legacy" way14:07
rosmaitaand it has passed the kioxia CI, which consumes the connector in the new way14:07
rosmaitaanyway, that's the #1 priority because it corrects a regression14:09
rosmaitaother stuff that is uncontroversial and needs review:14:09
rosmaitaremove six - https://review.opendev.org/c/openstack/os-brick/+/754598/14:09
rosmaitathe nvmeof change doesn't use six at all, so it's not impacted14:10
rosmaitabut i seem to have been reviewing this patch for months and would likeit out of my life14:10
rosmaitachange min version of tox - https://review.opendev.org/c/openstack/os-brick/+/77156814:10
rosmaitai verified that tox is smart enough to update itself when it builds testenvs, so it's not a problem14:11
rosmaitaRBD: catch read exceptions prior to modifying offset14:11
rosmaita#link https://review.opendev.org/c/openstack/os-brick/+/76386714:11
rosmaitawould be good, please look, if it requires work, give it a -114:11
rosmaitaAvoid unhandled exceptions during connecting to iSCSI portals14:12
rosmaita#link https://review.opendev.org/c/openstack/os-brick/+/77554514:12
rosmaitathere's a question about ^^, namely whether it catches too broad an exception14:12
*** felipe_rodrigues has joined #openstack-meeting-alt14:13
rosmaitaso while it would be nice to have, i don't insist on it14:13
rosmaitaso if you have a particular interest in this, please review14:13
rosmaitachange hacking to 4.0.014:13
rosmaita#link https://review.opendev.org/c/openstack/os-brick/+/77488314:13
rosmaitaso, we have already done it for cinder, and the one to cinderclient will probably merge before release14:14
rosmaitanow that i think about it, we could always merge later and backport to stable/wallaby to keep the code consistent14:15
rosmaitaso, let's hold off unless someone here has a strong opinion?14:15
eharneyi think just updating to 4.0.0 is pretty easy?  not sure what you mean14:15
rosmaitawell, i don't know if it will impact any of the other patches14:16
eharneyah14:16
rosmaitai will rebase it after the critical stuff merges and we can see what happens14:17
rosmaitaok, i may put up a patch to update the requirements and lower-constraints14:17
rosmaitait may not be necessary because they were updated in january14:18
rosmaitaanyway, if there is a change, i will individually bug people to look at the patch14:18
rosmaitaok, to summarize14:19
rosmaitathe highest priority for brick is the nvmeof patch14:19
rosmaita#link https://review.opendev.org/c/openstack/os-brick/+/77708614:20
rosmaitaneed quick feedback on this issue: https://review.opendev.org/c/openstack/os-brick/+/777086/8/os_brick/initiator/connectors/nvmeof.py#82914:21
rosmaitaok, if memory serves, e0ne and hemna volunteered to review this?14:22
e0nerosmaita: will do it. last time I +1'ed on it but there was an issue with naming14:23
rosmaitai am right on the verge of +2, but want to make sure we have people who can look at it today14:23
jungleboyjDefinitely need hemna to look at it.14:23
rosmaitae0ne: cool, i think that has been addressed14:23
rosmaitai think hemna looked at an earlier version, so shouldn't be too bad to re-review14:24
jungleboyj++14:24
rosmaitahe may be on the west coast this week, i will look for him later14:24
rosmaita#topic cinderclient14:25
*** openstack changes topic to "cinderclient (Meeting topic: cinder)"14:25
hemnaI'll poke at it14:25
rosmaitahemna: ty!14:25
rosmaitahttps://review.opendev.org/q/project:openstack/python-cinderclient+branch:master+status:open14:25
rosmaitamajor things are to get the MV updated14:25
rosmaitathere's a patch for 3.6314:26
rosmaitathere will be a patch for 3.6414:26
rosmaitabut the cinder-side code needs to merge first14:26
*** miniroy has joined #openstack-meeting-alt14:26
rosmaita#link https://review.opendev.org/q/project:openstack/python-cinderclient+branch:master+status:open14:27
rosmaitabad paste there, sorry14:27
rosmaita#link https://review.opendev.org/c/openstack/cinder/+/77108114:28
rosmaita^^ is a wallaby feature so is a priority review ... also, it's nicely written and has good tests, and one +214:28
* jungleboyj has so many tabs open. :-)14:28
rosmaita:D14:28
rosmaitaok, i am still working on the v2 support removal patch for cinderclient14:28
rosmaitashould have it ready in the next day or so14:29
jungleboyj++14:29
rosmaitaso note to reviewers: there are a bunch of small patches for cinderclient, please address them14:30
rosmaita#topic Request from TC to investigate frequent Gate failures14:30
*** openstack changes topic to "Request from TC to investigate frequent Gate failures (Meeting topic: cinder)"14:30
rosmaitajungleboyj: that's you14:30
*** miniroy has quit IRC14:30
jungleboyjHello.  :-)14:30
jungleboyjSo, as many have hopefully seen, there has been an effort to make our gate jobs more efficient as we have fewer resources for running check/gate.14:31
jungleboyjThere have also been issues with how long patches are taking to get through.14:31
jungleboyjNeutron, Nova, etc have made things more efficient.14:32
jungleboyjThere is still need for improvement.14:32
jungleboyjNow they are looking at how often gate/check runs fail.14:32
jungleboyj#link https://termbin.com/4guht14:33
toskyinteresting enough, the pastebin you linked refers to tempest-integrated-storage failures, I thought we had many more in the lvm-lio-barbican job14:33
jungleboyjdansmith:  Had highlighted two examples above where he was seeing frequent failures for Cinder.14:33
rosmaitadoes dansmith have an elasticsearch query up for these?14:33
eharneythe lio-barbican job is failing a lot, but i think it doesn't show up much where other projects would see it14:33
jungleboyjrosmaita:  I don't think he had put that together yet.  This was just a quick grab.14:34
dansmithnope, haven't done that yet14:34
rosmaitawhat eharney said14:34
rosmaitadansmith: if you have time, that would be great14:34
toskywe have kind of discussed a bit about those in the past, my feeling is that something weird happen on the limited environment14:34
dansmithdefinitely not barbican-related jobs that I've seen14:34
toskyand eharney has started a bit of investigation, I don't remember if there were any findings14:34
eharneytosky: i think there's actually a bug in the target code hitting the lio-barbican job but i guess the questions today are about other issues14:35
rosmaitai think if we can get an elasticsearch query up, that will make it easier to find fresh logs when someone has time to look14:35
toskyeharney: I see14:35
jungleboyjSo, partially, this is a reminder to everyone that we should try to look at failures and not just blindly recheck.  Second, as to see if anyone has been looking at failures.14:36
rosmaitathe big lvm-lio-barbican job failures i have been seeing are related to backup tests and the test-boot-pattern tests14:36
jungleboyjeharney:  It is more of a general call.  Those were just examples.  :-)14:36
jungleboyjrosmaita:  Hasn't that been the case for like 3 years now?14:36
tosky(backup tests which were removed from the main gates because of the failing rates, probably resources )14:36
*** tmazur has joined #openstack-meeting-alt14:37
jungleboyjrosmaita:  Do we have elasticsearch queries for those?14:37
rosmaitai don't think so14:38
jungleboyjSo, that would probably be good to add.14:38
rosmaitasomeone could be a Hero of Cinder and put them together14:38
jungleboyj:-)14:38
rosmaitaand put the links on the meeting etherpad14:38
* jungleboyj looks at our bug here enriquetaso 14:39
jungleboyj*hero14:39
enriquetasosure14:39
rosmaitamaybe a driver maintainer who's waiting for reviews ?14:39
enriquetasonot really sure how but sure14:39
*** jbernard has joined #openstack-meeting-alt14:39
jungleboyjAdd to our weekly bug review an eye on where our gate/check failures are at.14:40
jungleboyjrosmaita:  That is a good idea too.14:40
rosmaitaenriquetaso: you can look by hand, but i think the preferred method is to file a bug and checkout a repo and push a patch14:40
rosmaitamakes it more stable14:40
rosmaitawe can talk offline, i have notes somewhere14:41
rosmaitaor maybe dansmith can volunteer to walk you through the process?14:41
rosmaitaok, so the conclusion is that volume-related gate failures suck and someone needs to do something about it14:42
dansmithtbh, I haven't actually done that in a while14:42
rosmaita#topic Wallaby R-6 Bug Review14:42
*** openstack changes topic to "Wallaby R-6 Bug Review (Meeting topic: cinder)"14:42
enriquetasohi14:42
enriquetasoWe have 6 bugs reported this week. I'd like to show 3 today because I'm not sure about the severity of them.14:42
rosmaitadansmith: that's fine, just may slow things down a bit, as you can see enriquetaso is already kind of busy14:42
enriquetaso#link https://etherpad.opendev.org/p/cinder-wallaby-r6-bug-review14:43
enriquetasobug_1:14:43
enriquetaso Backup create failed: RBD volume flatten too long causing mq to timed out.14:43
jungleboyjrosmaita:  ++ Thank you.14:43
enriquetaso#link14:43
enriquetaso https://bugs.launchpad.net/cinder/+bug/191684314:43
openstackLaunchpad bug 1916843 in Cinder "Backup create failed: RBD volume flatten too long causing mq to timed out." [Medium,New]14:43
enriquetaso#link  https://bugs.launchpad.net/cinder/+bug/191684314:43
enriquetasoIn the process of creating a backup using a snapshot, there is an operation tocreate a temporary volume from a snapshot, which requires cinder-backupand cinder-volume to perform rpc interaction.default configuration"rpc_response_timeout" is 60s.14:43
enriquetasowhoami-rajat: is this related to any of the flatten work you have done?14:44
enriquetasoi can't remember14:44
whoami-rajatcan't recall anything related, will take a thorough look after the meeting14:45
enriquetasoThanks!14:45
rosmaitai think we should ask for more info first14:45
rosmaitasomething about the environment14:45
eharneythe main point in that bug is that the slow call shouldn't block the service up for RPC calls, AFAIK14:45
eharneythe fact that it's slow isn't really the interesting part14:45
rosmaitayeah, but sounds like we would need a major redesign to do that right14:46
eharneyi'm not so sure, need to look around in that area again14:46
dansmithis it just that the operation takes longer than the RPC timeout?14:47
dansmithlike, works for small volumes but large one will always take longer than 60s and the RPC call times out?14:47
rosmaitanot sure, doesn't say14:47
*** zoharm has quit IRC14:47
eharneyi'm thinking more in the direction of librbd not behaving the way most code does with eventlet14:48
dansmithwe had a lot of those sorts of things in nova, so I implemented heartbeating long-call support in oslo.messaging a while back which lets you make much longer RPC calls14:48
eharneybut i don't have enough to make it a useful discussion for now14:48
dansmithokay if you're blocked in a C lib call and not answering RPC, that would also be bad14:48
eharneyright14:48
enriquetasoOK looks like there may be something there14:49
enriquetasonext14:49
enriquetasobug_2: Cinder sends old db object when delete a attachment14:49
enriquetaso#link https://bugs.launchpad.net/cinder/+bug/191698014:49
openstackLaunchpad bug 1916980 in Cinder "cinder sends old db object when delete a attachment" [Undecided,Incomplete] - Assigned to wu.chunyang (wuchunyang)14:49
enriquetasoWhen we delete an attachment Cinder sends a notification with old db object. We should call refresh() function to refresh the object before sending tonotification. after running the refresh function. the status  changes todetached. 14:50
enriquetasoI left a comment on the bug report "Does this problem occur on all backends or on a specific one?"14:50
geguileoenriquetaso: I have fixed that one in my local repo14:50
geguileoenriquetaso: I will submit the patch later today14:50
enriquetasocool14:50
enriquetasothanks!14:50
enriquetasonext14:50
enriquetasobug_3: Scheduling is not even among multiple thin provisioning pools which have different sizes14:50
enriquetaso#link https://bugs.launchpad.net/cinder/+bug/191729314:50
openstackLaunchpad bug 1917293 in Cinder "Scheduling is not even among multiple thin provisioning pools which have different sizes" [Undecided,New]14:50
enriquetasoScheduling is not even among multiple thin provisioning pools14:51
enriquetasowhich have different sizes. For example, there are two thin provisioning14:51
enriquetasopools. Pool0 has 10T capacity, Pool1 has 30T capacity, the max_over_subscription_ratio14:51
enriquetasoof them are both 20. We assume that the provisioned_capacity_gb of Pool114:51
enriquetasois 250T and the provisioned_capacity_gb of Pool0 is 0.14:51
enriquetasoAccording to the formula in the cinder source code, the free capacity of Pool014:51
enriquetasois 10*20-0=200T and the free capacity of Pool1 is 30*20-250=350T.14:51
enriquetasoSo it is clear for us to see that a new created volume is14:51
enriquetasoscheduled to Pool1 instead of Pool0. However, Pool0 is scheduled14:51
enriquetasosince it has bigger real capacity.14:51
enriquetasoIn a word, the scheduler tends to schedule the pool that has bigger size.14:51
geguileoenriquetaso: I haven't looked at the bug, but where they testing on devstack or with a deployment that has 3 schedulers?14:51
eharneyi'd need to look into this one again, but i'm not sure it's a bug, it may be that the reporter's expectations aren't quite right and he's expecting a scheduling algorithm that's smarter than what we actually try to do14:52
geguileoor that the requests are going to different schedulers14:52
geguileoand each scheduler has a different in-memory data at the time of receiving the request...14:52
enriquetasogeguileo, i need to ask because it doesn't says14:52
geguileoenriquetaso: anything that happens with multiple schedulers but doesn't with a single one can be attributed to different in-memory data14:53
enriquetasogeguileo, good point, so we need more info14:54
eharneythis will also depend on how you configure the capacity weigher14:54
enriquetasoOK14:55
enriquetasothat's the last one :)14:55
rosmaitathanks sofia14:55
rosmaita#topic stable branch update14:55
*** openstack changes topic to "stable branch update (Meeting topic: cinder)"14:56
whoami-rajati will provide a quick update14:56
whoami-rajatproposed stable victoria release14:56
whoami-rajat#link https://review.opendev.org/c/openstack/releases/+/77823114:56
whoami-rajat3 patches remaining in ussuri (cinder and os-brick)14:56
whoami-rajat4 remaining in train14:56
whoami-rajatthanks everyone for the reviews this week14:56
whoami-rajatthat's all from my side14:57
*** zoharm has joined #openstack-meeting-alt14:57
rosmaitathanks Rajat14:57
rosmaita#topic conf option workaround14:57
*** openstack changes topic to "conf option workaround (Meeting topic: cinder)"14:57
whoami-rajatAgain me14:57
whoami-rajatso hemna asked a question about the default value of the conf option in rbd clone patch14:58
whoami-rajat#link https://review.opendev.org/c/openstack/cinder/+/75439714:58
eharneyIIRC, this is defaulted off mostly because we don't want to introduce extra risk and complexity, right?14:59
whoami-rajatyes14:59
eharneythat's not really obvious in the patch, but that plus the fact that there are other solutions for people now makes a decent case for defaulting it off i think14:59
rosmaitaok, we are out of time ... let's continue this in openstack-cinder, or respond on the patch14:59
rosmaitathanks everyone14:59
rosmaita#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Wed Mar  3 15:00:02 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
whoami-rajatthis isn't even the actual feature, just a workaround for releases < mimic15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2021/cinder.2021-03-03-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2021/cinder.2021-03-03-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2021/cinder.2021-03-03-14.00.log.html15:00
jungleboyjThanks!15:00
e0ne#startmeeting horizon15:01
openstackMeeting started Wed Mar  3 15:01:26 2021 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
*** GirishChilukuri has left #openstack-meeting-alt15:02
*** amar7ibm_ has left #openstack-meeting-alt15:02
vishalmanchandahi all15:02
e0nehi15:02
rdopierao/15:02
tmazuro/15:02
*** kinpaa12389 has quit IRC15:02
amotokio/15:03
e0ne#topic Notices15:05
*** openstack changes topic to "Notices (Meeting topic: horizon)"15:05
*** jbernard has left #openstack-meeting-alt15:05
e0neTC Nominations and PTL Nominations for Xena release started15:05
e0ne#link https://governance.openstack.org/election/15:06
e0nedo not forget to add you candidacy if you're going to15:06
e0neI'm not going to serve PTL role for one more cycle15:07
e0neI'll still be in the community but my priorities changed15:08
*** ikanias has joined #openstack-meeting-alt15:09
*** lpetrut has quit IRC15:09
e0nenext week is Wallaby-3 milestone15:10
e0ne#link https://releases.openstack.org/wallaby/schedule.html15:10
amotokiperhaps my pririties needs to be changed too :(15:11
e0neit's a feature freeze and soft string freeze too15:11
e0neamotoki: are you leaving openstack community?15:11
amotokie0ne: no15:11
e0neamotoki: good to hear it15:11
amotokiregarding milestone 3, let's check our priorities15:12
amotokire: policy stuff, is there any blocker?15:12
amotokihttps://review.opendev.org/c/openstack/horizon/+/75013415:12
e0ne#link https://etherpad.opendev.org/p/horizon-release-priorities15:13
amotokiwe haven't supported system-scope but at least support of deprecation rules would be a good improvement15:13
e0neamotoki: I put +2 without W+1 on it to let people more time to test and review it15:14
amotokiso that we can sync default policies from backend services.15:14
e0neI don't have any blockers to get it merged15:14
amotokionce it lands, we also need to sync polices as follow-up15:14
e0nelet's give rdopiera  and tmazur some time to review it15:15
amotoki+115:15
vishalmanchanda+1.15:15
*** jinyuanliu has quit IRC15:15
e0neotherwise I'll merge it tonight15:16
*** jinyuanliu has joined #openstack-meeting-alt15:16
tmazurthanks! I had no time to test it properly yet, will do today15:16
e0netmazur: thanks15:16
amotokiregardless of that you can review in time or not, I can help your understanding on policies.15:17
amotokiwe have two more prioritied topics.15:17
vishalmanchandaI have a question if policy rules change for a service like if there are some change in rule for cinder then we are going to update it every time?15:18
amotokithe one is "Merge tempest-horizon into tempest"15:18
amotokivishalmanchanda: what do you mean by "every time"?15:18
vishalmanchandaamotoki: sorry to interrupt please go ahead.15:18
amotokivishalmanchanda: go ahead, you first15:18
amotokiit is better to cover it before moving on15:19
vishalmanchandaamotoki: I mean if there are new rules added in cinder.yaml then we are going to add it horizon as well?15:19
amotokivishalmanchanda: my current answer is that (1) we need to follow policy NAME change at least and (2) sync the latest rules as much as possible per release.15:20
vishalmanchandaamotoki: ok got my answer thanks.15:20
gmannpolicy changes should happen in deprecated way with supporting old rules.15:21
gmannif any service break existing horizon then it break users :)15:21
amotokigmann: yeah15:22
amotokiat least horizon default policies are behind a couple of releases15:22
amotokias we did not support deprecated rules and could not update policy.json files for several releases15:22
amotokiso we need to close the gap at least in this release.15:23
gmann+115:23
amotokithis is the top priority to me in this release.15:23
amotokimore questions on the policy stuff?15:24
vishalmanchandanothing15:25
amotokiokay, let's cover the other two priorites15:25
-amotoki- thinks we can cover prioritised topics in "Notices" section15:26
amotokithe one is "Merge tempest-horizon into tempest".15:26
amotokithis is almost completed. the remaining one is to update queens and rokcy update.15:26
amotokihttps://review.opendev.org/q/topic:%22merge-horizon-test%22+(status:open%20OR%20status:merged)15:26
e0ne#link https://review.opendev.org/q/topic:%22merge-horizon-test%22+(status:open%20OR%20status:merged)15:26
amotokiso it would be simple. on the other hand, I am not sure who are interested in these stabe branches.....15:27
amotokithis would be another discussion on when we should EOL old stable branches, so I don't jump into details.15:28
amotokigmann: I think we can ignore https://review.opendev.org/c/vexxhost/openstack-operator/+/774720 as we got no response so far unfortunately.15:29
gmannamotoki: yeah, there are failing with cirror url so once they fix that they can merge this to get their gate green15:30
amotokigmann: yes. it totally depends on the healthiness of their CI :)15:31
amotokimoving on15:31
amotokithe other is "Chinese locale rename".15:31
amotokiI got a great progress today.15:31
gmannas it is outside of openstack governance I think proposing change is all we can do15:31
amotokigmann: totally agree (as we discussed in the reviews in project-config and governances)15:32
amotokiback to "Chinese locale rename ", the change in openstack-zuul-jobs landed today15:32
amotokiand you see zh-cn/zh-tw are renamed in recent translation import patches.15:33
amotokiI am carefully reviewing the periodic job results in all projects.15:33
amotokibig thanks to the TaCT and I18N SIG members.15:33
vishalmanchandayes I see bot patches in horizon15:33
vishalmanchandahttps://review.opendev.org/c/openstack/horizon/+/77836615:34
amotokithey are my other hats too :)15:34
amotokimore specifically, https://review.opendev.org/q/topic:%2522zanata/translations%2522+(status:open+OR+status:merged)+(project:%255Eopenstack/.*horizon+OR+project:%255Eopenstack/.*-ui+OR+project:%255Eopenstack/.*-dashboard)15:34
amotokiand https://zuul.openstack.org/builds?job_name=propose-translation-update15:35
vishalmanchandaamotoki: nice work:)15:35
e0neglad to see plugins CIs in a good shapte15:35
amotokimore, we need to land https://review.opendev.org/c/openstack/horizon/+/774034 in horizon15:35
amotokiit is mandatory to consume the new locales.15:36
amotokiif you notice any issues or questions feel free to reach me.15:37
amotokie0ne: rdopiera: could you review https://review.opendev.org/c/openstack/horizon/+/774034 for smooth transiation?15:38
e0ne+2'ed15:38
*** hemna has quit IRC15:39
amotokithat's all from me15:39
*** hemna has joined #openstack-meeting-alt15:40
amotokianything other on priorities?15:40
e0nenothing  from me15:42
vishalmanchandaI also want to admin-backup-panel feature to get merged in this release.15:42
vishalmanchandahttps://review.opendev.org/c/openstack/horizon/+/77260315:42
amotokivishalmanchanda: is it a part of priorities?15:42
amotokiif it is a general review request we can cover it later.15:43
vishalmanchandaok15:43
amotokithis is "Notices" topic in the meeting.15:43
vishalmanchandaoops.15:44
amotokimy turn on the priorites is over :) let's move on15:44
e0ne#topic Open discussion15:45
*** openstack changes topic to "Open discussion (Meeting topic: horizon)"15:45
e0nevishalmanchanda: I'll review your patch. it's good to be included in the release15:46
vishalmanchandae0ne: thanks Ivan:)15:46
vishalmanchandano topic from my side.15:48
amotokiI revisited 30~40 bugs last week. I noticed most incoming bugs are not reviewed unless I reviews. I don't want to be alone and being alone discourages me a lot :(15:48
amotoki30~40 bugs are old bugs though15:48
amotokiI suggest you to review bugs :)15:49
vishalmanchandawill do that I was on PTO last week due to some travelling.15:49
amotokivishalmanchanda: np..15:50
amotokiI am talking about general situations in recent cycles. one or two weeks does not matter.15:51
e0neI skipped bug triage during last month :(15:51
amotokiI am trying to be a noisy man as I will descrease my priority in the next cycle and am flushing pending items.15:52
e0neamotoki: it's ok15:53
e0neit's an important topic15:53
*** zoharm has quit IRC15:55
amotokiI think bugs highlight our feature gaps well15:55
amotokie0ne: one question. I see some security bugs assigned to you. are you still working on them?15:56
e0neamotoki: oh.. let me check it. I tottally forgot about it:(15:57
amotokie0ne: thanks15:57
e0neamotoki: could you send me a link? I don't see any security issues assigned to me15:58
e0neonly this one https://bugs.launchpad.net/horizon/+bug/189284815:58
openstackLaunchpad bug 1892848 in OpenStack Security Advisory "XSS in adding JavaScript into the ‘Subnet Name’ field" [Undecided,Incomplete]15:58
amotokie0ne: let me share them later. I donn't have the links now.15:58
amotokie0ne: I am not sure it was "one or more" though15:59
e0newe're out of time. let's continue our discussion in #openstack-horizon channel16:00
amotokigenerally speaking we need to review such bugs http://lists.openstack.org/pipermail/openstack-discuss/2021-February/020577.html16:00
amotokithanks all16:00
e0nethanks everybody for your  contributions16:02
e0ne#endmeeting16:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:02
openstackMeeting ended Wed Mar  3 16:02:16 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2021/horizon.2021-03-03-15.01.html16:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2021/horizon.2021-03-03-15.01.txt16:02
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2021/horizon.2021-03-03-15.01.log.html16:02
*** smcginnis has quit IRC16:25
*** macz_ has joined #openstack-meeting-alt16:25
*** smcginnis has joined #openstack-meeting-alt16:34
*** rosmaita has left #openstack-meeting-alt16:35
*** e0ne has quit IRC16:37
*** macz_ has quit IRC16:46
*** macz_ has joined #openstack-meeting-alt16:47
*** hemna has quit IRC17:01
*** browny has quit IRC17:01
*** ralonsoh has quit IRC17:01
*** lifeless_ has quit IRC17:01
*** ralonsoh has joined #openstack-meeting-alt17:05
*** hemna has joined #openstack-meeting-alt17:06
*** browny has joined #openstack-meeting-alt17:06
*** lifeless_ has joined #openstack-meeting-alt17:06
*** e0ne has joined #openstack-meeting-alt17:13
*** e0ne has quit IRC17:26
*** macz_ has quit IRC17:27
*** subbareddy has joined #openstack-meeting-alt17:27
*** e0ne has joined #openstack-meeting-alt17:43
*** e0ne has quit IRC17:43
*** e0ne has joined #openstack-meeting-alt17:59
*** ralonsoh has quit IRC18:23
*** lpetrut has joined #openstack-meeting-alt18:38
*** lpetrut has quit IRC18:49
*** rdopiera has quit IRC19:25
*** whoami-rajat has quit IRC19:50
*** lifeless_ is now known as lifeless19:56
*** slaweq has quit IRC20:04
*** rcernin has joined #openstack-meeting-alt20:46
*** slaweq has joined #openstack-meeting-alt20:57
*** gyee has joined #openstack-meeting-alt21:01
*** slaweq has quit IRC21:07
*** rcernin has quit IRC21:17
*** e0ne has quit IRC21:23
*** irclogbot_1 has quit IRC21:33
*** bauzas has quit IRC21:33
*** ianw has quit IRC21:33
*** kopecmartin has quit IRC21:33
*** DinaBelova has quit IRC21:33
*** freerunner has quit IRC21:33
*** amotoki has quit IRC21:33
*** johnthetubaguy has quit IRC21:33
*** irclogbot_1 has joined #openstack-meeting-alt21:34
*** bauzas has joined #openstack-meeting-alt21:34
*** ianw has joined #openstack-meeting-alt21:34
*** kopecmartin has joined #openstack-meeting-alt21:34
*** DinaBelova has joined #openstack-meeting-alt21:34
*** freerunner has joined #openstack-meeting-alt21:34
*** amotoki has joined #openstack-meeting-alt21:34
*** johnthetubaguy has joined #openstack-meeting-alt21:34
*** e0ne has joined #openstack-meeting-alt21:38
*** zzzeek has quit IRC21:44
*** zzzeek has joined #openstack-meeting-alt21:45
*** rcernin has joined #openstack-meeting-alt22:05
*** rcernin has quit IRC22:11
*** rcernin has joined #openstack-meeting-alt22:11
*** ajitha has quit IRC22:23
*** gshippey has quit IRC22:25
*** smekala has joined #openstack-meeting-alt22:29
*** e0ne has quit IRC22:42
*** smekala has quit IRC22:55
*** rcernin has quit IRC22:56
*** rcernin has joined #openstack-meeting-alt23:01
*** thgcorrea has quit IRC23:01
*** rcernin has quit IRC23:26
*** zzzeek has quit IRC23:40
*** zzzeek has joined #openstack-meeting-alt23:42
*** vishalmanchanda has quit IRC23:44

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