15:00:18 <vishalmanchanda> #startmeeting horizon
15:00:18 <opendevmeet> Meeting started Wed Jul 27 15:00:18 2022 UTC and is due to finish in 60 minutes.  The chair is vishalmanchanda. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:18 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:18 <opendevmeet> The meeting name has been set to 'horizon'
15:01:29 <rdopiera> o/
15:01:44 <vishalmanchanda> Hello everyone
15:01:56 <tmazur> o/
15:02:52 <vishalmanchanda> let's start the meeting
15:02:56 <vishalmanchanda> agenda of meeting can be found here https://etherpad.opendev.org/p/horizon-release-priorities#L39
15:03:15 <vishalmanchanda> #topic Notices
15:03:30 <vishalmanchanda> A casual reminder about schedule.
15:03:42 <vishalmanchanda> This week is R-10 week.
15:03:55 <vishalmanchanda> For more info about schedule please refer https://releases.openstack.org/zed/schedule.html
15:03:58 <amotoki> hi
15:04:10 <vishalmanchanda> moving to next announcement
15:04:43 <vishalmanchanda> OpenStack next release name is announced and it is Antelope.
15:04:52 <vishalmanchanda> https://lists.openstack.org/pipermail/openstack-discuss/2022-July/029672.html
15:06:11 <vishalmanchanda> I have no other announcements to make, if anyone have any announcement to make. please go ahead.
15:06:24 <amotoki> i have one
15:06:42 <amotoki> as discussed last week, I added you horizon cores to horizon-coresec lp team.
15:06:48 <amotoki> you can now check private sec bugs.
15:06:52 <amotoki> non-active members are clean up too.
15:07:39 <vishalmanchanda> amotoki: thanks, I can see private sec bug now.
15:07:59 <amotoki> I also adjusted member list of other launchpad teams like horizon-bugs and horizon-drivers.
15:08:36 <amotoki> horizon-drivers members are updated to have active members only
15:09:20 <amotoki> horizon-bugs includes horizon-drivers team, so members of horizon-drivers (i.e. horizon-cores) are now removed from horizon-bugs to avoid duplications.
15:09:30 <amotoki> that's all from me.
15:10:10 <amotoki> one note: you can find info on lp teams in https://docs.openstack.org/horizon/latest/contributor/policies/horizon-groups.html
15:10:43 <vishalmanchanda> amotoki: ack.
15:12:06 <vishalmanchanda> I am not having many updates for this week because I was on Sick leave and joined today.
15:12:14 <vishalmanchanda> moving to next topic
15:12:25 <vishalmanchanda> #topic Bug deputy report
15:12:51 <vishalmanchanda> There are some new bugs reported in the last few weeks.
15:13:55 <vishalmanchanda> Dropping bug links here https://bugs.launchpad.net/horizon/+bug/1980214
15:14:33 <amotoki> it is specific to django 4
15:15:46 <vishalmanchanda> yeah...
15:16:02 <amotoki> I don't think we need to include a fix for django 4 in stable/yoga.
15:16:24 <vishalmanchanda> amotoki: make sense.
15:16:33 <amotoki> I think it is better to have a fix/workaround in master and let zigo to backport it to stable/yoga.
15:16:50 <amotoki> * stable/yoga in Debian
15:17:24 <vishalmanchanda> amotoki: +1.
15:18:42 <vishalmanchanda> Next bug link https://bugs.launchpad.net/horizon/+bug/1979662
15:19:54 <vishalmanchanda> It looks difficult to reproduce this bug for me in local env.
15:20:45 <amotoki> vishalmanchanda: don't you hit any change around apache reload?
15:21:04 <amotoki> I wonder apache reload happens around log rotation
15:21:51 <zigo> amotoki: If you send me patches, that's fine enough to me ! :)
15:22:02 <zigo> (just pointing me to the review URL)
15:22:14 <zigo> Zed is comming fast anyways...
15:23:26 <vishalmanchanda> amotoki: hmm, I never noticed that so far.
15:23:55 <amotoki> zigo: ack, but it is totally on best effort basis. I am not sure I can work on it soon :p
15:26:29 <vishalmanchanda> Next bug is https://bugs.launchpad.net/horizon/+bug/1981165
15:27:07 <vishalmanchanda> It will check  and confirm this one after the meeting.
15:28:40 <vishalmanchanda> next bug link https://bugs.launchpad.net/horizon/+bug/1982836
15:31:07 <vishalmanchanda> bug 1982836 looks invalid to me becuase error msg metioned in bug summary look valid deprecation warning to me.
15:31:32 <amotoki> it is not so straight-forward.
15:32:00 <amotoki> the deprecation warnings happen even when horizon default policies.
15:32:24 <amotoki> it is not a neglect of operators. they can do nothing.
15:32:33 <amotoki> I know it is very noisy
15:32:52 <vishalmanchanda> Can't someone disable these warning by changing some setting in conf. file?
15:33:31 <amotoki> it can, but I think the default setting (or example settings) should have it.
15:34:58 <amotoki> it sounds a kind of bad default settings to me.
15:37:13 <amotoki> in addition, I haven't check there is a negative impact when dsiabling DeprecationWarning for oslo.policy.
15:38:00 <vishalmanchanda> I'll check that and add my thoughts in bug summary.
15:38:25 <vishalmanchanda> Next bug link https://bugs.launchpad.net/horizon/+bug/1982944
15:40:14 <vishalmanchanda> bug 1982944 needs to check and confirm.
15:40:56 <vishalmanchanda> I'll check and try to reproduce it tommorow.
15:41:25 <rdopiera> it's because horizon doesn't actually check detailed policies
15:41:35 <rdopiera> it just checks if it's an admin
15:42:03 <rdopiera> we have a lot of places where the policies are super-detailed, but horizon simply ignores them
15:42:41 <rdopiera> like, in neutron you can practically change access to individual form fields per user, but horizon just displays them all regardless
15:43:39 <rdopiera> I have a patch for review changing that for a single field that was roblematic, in routers, but I'm not sure we should actually be checking all those policies all the time
15:48:37 <vishalmanchanda> rdopiera: ack.
15:48:54 <amotoki> yeah, we have many hard-coded access checks
15:50:38 <amotoki> honestly I tried to clean them up several years ago, but complexity around mixied situation of Django vs AngularJS and it was on-going and I gave it up :p
15:50:51 <rdopiera> one problem with implementing more detailed checks is that they usually require additional information - like the owner of the network etc. - and that's additional api calls
15:51:50 <amotoki> rdopiera: perhaps we can split problesm into two categories: the one is policy checks based on fields, the other is our hard-coded rules.
15:52:20 <amotoki> the first one requires additional information which leads to extra API calls as you said
15:52:29 <rdopiera> amotoki: by the way, if you have a moment, I would really appreciate if you could take a look and say if I'm doing the check correctly here: https://review.opendev.org/c/openstack/horizon/+/810224
15:52:56 <amotoki> rdopiera: ah, really sorry. I totally forgot it.
15:53:21 <rdopiera> no worries, me too :D
15:53:35 <amotoki> rdopiera: I starred it in gerrit
15:54:31 <rdopiera> sorry for the plug
15:54:56 <rdopiera> going back, I think we are pretty good at least at the menu-level checks
15:55:11 <rdopiera> the actions could use work
15:55:55 <vishalmanchanda> moving to next topic.
15:56:09 <vishalmanchanda> #topic open-discussion
15:56:31 <vishalmanchanda> Does anyone have any other topic to discuss?
15:57:14 <rdopiera> are we doing anything for the ptg?
15:57:40 <rdopiera> is anyone even going?
15:58:19 <vishalmanchanda> I was thinking if we can do it virtually but need to check the process for the same.
15:58:22 <rdopiera> if not, should we arrange a remote planning session shortly after?
15:59:35 <vishalmanchanda> rdopiera: yeah, we can definitely do that.
15:59:39 <rdopiera> doing it during the ptg would have the advantage of making it possible for people from other teams to find us, but then we are also comppeting for time with other sessions
16:01:52 <vishalmanchanda> rdopiera: let's wait for other project team how they plan PTG.
16:03:06 <vishalmanchanda> I just heard from one of my colleagues they will discuss about it in tomorrow's TC meeting.
16:03:32 <vishalmanchanda> then we can also decide.
16:03:57 <vishalmanchanda> anything else to discuss?
16:05:53 <vishalmanchanda> ok let's end this meeting.
16:06:03 <vishalmanchanda> Thanks everyone for joining!
16:06:18 <vishalmanchanda> #endmeeting