15:00:11 <vishalmanchanda> #startmeeting horizon
15:00:11 <opendevmeet> Meeting started Wed Mar  1 15:00:11 2023 UTC and is due to finish in 60 minutes.  The chair is vishalmanchanda. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:11 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:11 <opendevmeet> The meeting name has been set to 'horizon'
15:01:19 <rdopiera> o/
15:01:31 <vishalmanchanda> hello everyone
15:01:37 <amotoki> hi
15:02:31 <vishalmanchanda> ok let's start the meeting
15:02:46 <vishalmanchanda> agenda of meeting can be found here https://etherpad.opendev.org/p/horizon-release-priorities#L39
15:03:05 <vishalmanchanda> There is no topic added for today's discussion.
15:03:33 <vishalmanchanda> let me start with announcement for this week.
15:03:43 <vishalmanchanda> #topic Notices
15:03:58 <vishalmanchanda> A casual reminder about schedule.
15:04:09 <vishalmanchanda> This week is R-3 week.
15:04:21 <vishalmanchanda> For more info about schedule please refer https://releases.openstack.org/antelope/schedule.html
15:05:13 <amotoki> till when do we need to land patches for the next release?
15:05:35 <amotoki> I think there was a notice that horizon did not cut a release recently in the mailing list.
15:05:47 <vishalmanchanda> I have purposed a patch to cut a release of horizon which can be use to create stable/antelope
15:05:53 <vishalmanchanda> https://review.opendev.org/c/openstack/releases/+/874758
15:06:25 <vishalmanchanda> amotoki: yeah I saw that mail and purposed a patch 874758
15:06:53 <vishalmanchanda> I am just waiting if https://review.opendev.org/c/openstack/horizon/+/868368/ got merged
15:07:23 <rdopiera> I tried to review that patch, but I don't have port forwarding support enabled
15:07:40 <vishalmanchanda> otherwise we can move forward without above feature 🤞
15:08:37 <amotoki> i haven't tested it yet. I dropped not small number of commetns after static reviews.
15:08:45 <vishalmanchanda> rdopiera: ok, you have to add "enable_service port_forwarding" in your devstack ``local.conf``
15:09:06 <amotoki> vishalmanchanda: perhaps whta rdopiera said is related to his neutron env
15:09:30 <vishalmanchanda> rdopiera: to enable the floating ip in your devstack env.
15:09:33 <rdopiera> yeah, I will need to install a devstack and try again
15:09:41 <rdopiera> thanks for the hint
15:09:43 <vishalmanchanda> amotoki: yeah I know.
15:10:51 <vishalmanchanda> rdopiera: Also don't forgot to install python-neutronclient version >=8.1.0
15:11:02 <amotoki> I would like to hear your opinion on whether we should have a config option in horizon for FIP port fwd or check the availability of the coresponding neutron extentension
15:11:08 <amotoki> what do you think?
15:11:56 <amotoki> vishalmanchanda: regarding neutronclient version, we should not hit this issue for a fresh devstack env. do you re-use your env?
15:12:53 <vishalmanchanda> amotoki: In the Intial patch sets author didn't added config option, he added config option in last few P.S.
15:14:14 <vishalmanchanda> amotoki: I am ok with  check the availability of the coresponding neutron extentension
15:14:49 <vishalmanchanda> amotoki: yeah I am using re-use env.
15:15:25 <amotoki> the proposed patch does not check the extnesion availability and just checks the new config option. even if we have the option, the extension should be checked.
15:16:17 <amotoki> vishalmanchanda: if you re-use your env, it is your responsibility to update python requirements. it is not what devstakc does not cover.
15:16:40 <amotoki> * for most cases
15:18:13 <vishalmanchanda> amotoki: yeah, he also add version check code but removed it after your suggestion. Now added  extension check availability function https://review.opendev.org/c/openstack/horizon/+/868368/17/openstack_dashboard/api/neutron.py#2301 which looks good to me.
15:19:03 <vishalmanchanda> amotoki: ok, got your point about updating python requirements for a re-use env.
15:20:48 <vishalmanchanda> rdopiera: feel free to ping me if you need any help to setup env. to check floating-ip fwd feature because maybe I also faced the same issue you are facing now.
15:20:52 <vishalmanchanda> tmazur: ^^
15:20:55 <rdopiera> vishalmanchanda: thanks
15:21:30 <vishalmanchanda> rdopiera: yw.
15:21:50 <vishalmanchanda> moving to next announcement
15:22:33 <vishalmanchanda> You may know that we have a virtual PTG from March 27-31, 2023.
15:23:20 <vishalmanchanda> I have registered Horizon for virtual PTG, please register yourself for virtual PTG to get related updates.
15:23:42 <vishalmanchanda> It is free https://openinfra-ptg.eventbrite.com/
15:24:30 <vishalmanchanda> I will create a etherpad to collect topics for Bobcat cycle PTG after this meeting.
15:25:32 <vishalmanchanda> I have no other announcements to make, if anyone have any announcement to make. please go ahead
15:26:41 <vishalmanchanda> moving to the next topic
15:26:53 <vishalmanchanda> #topic open-discussion
15:28:17 <vishalmanchanda> I have no other topic to discuss for today's meeting. If anyone have any topic to discuss, please go ahead.
15:29:15 <vishalmanchanda> Also just want to know, if anyone of you attending Vancouver OpenInfra Summit?
15:30:46 <amotoki> I haven't decided it yet, but at least the reason would not be related to horizon even if I can be there :p
15:31:14 <vishalmanchanda> amotoki: ack.
15:31:54 <tmazur> I am not going most likely
15:32:45 <vishalmanchanda> tmazur: ok and I thought you were travelling as you live in Canada.
15:33:15 <tmazur> I am not sure yet actually
15:33:23 <vishalmanchanda> tmazur: ok.
15:34:11 <vishalmanchanda> Do we have any other topic to discuss?
15:34:14 <amotoki> do we have any progress on https://bugs.launchpad.net/horizon/+bug/2007574 ?
15:34:44 <amotoki> IIRC we discussed it for a while but I am not sure who attended the meeting at that time
15:34:49 <vishalmanchanda> amotoki: no progress, I am still investigating.
15:35:21 <amotoki> as I mentioned before, it looks not specific to horizon
15:35:45 <amotoki> it looks like the way used in xstatic packages hits the issue
15:36:03 <vishalmanchanda> rdopiera: Could you please take a look at 2007574  as you know more about Xstatic.
15:36:37 <amotoki> the github issue found in the lp bug helps us understand the issue
15:38:55 <amotoki> https://github.com/pypa/setuptools/issues/3824#issuecomment-1432936270 and the next comment highlight the issue
15:41:39 <amotoki> I know it needs more discussion to address the issue, but what is a good way to track it?
15:42:30 <amotoki> do we track it in our meeting? perhaps it is more than a simple launchpad bug . LP bugs are not well tracked easily :-(
15:45:04 <vishalmanchanda> amotoki: we can track it in launchpad and add the discussion we do here in launchpad, I will bring this topic in our weekly meeting.
15:45:30 <vishalmanchanda> amotoki: if you have some other suggestion, please let us know.
15:45:41 <vishalmanchanda> amotoki: I mean on etherpad or on ML.
15:47:02 <amotoki> the detail can be tracked in launchpad bugs. my point is how we can keep checking important topics.
15:47:46 <vishalmanchanda> I will add it under https://etherpad.opendev.org/p/horizon-release-priorities#L12
15:48:04 <rdopiera> vishalmanchanda: ouch, I will look into that
15:48:07 <amotoki> we did not idscuss prioritiized topics in our past metings.... hey "no topics" this week
15:48:46 <vishalmanchanda> becuase we don't have any updates that's why.
15:50:12 <amotoki> rdopiera: thanks. I think it is common to xstatic packages. your double check would be really appreciated as I think you were more involved in its design
15:52:29 <vishalmanchanda> What I  can do bring release priories topic in weekly meeting even if I have no updates for that week.
15:56:32 <vishalmanchanda> If no other topic to discuss, let's end this meeting.
15:56:42 <vishalmanchanda> Thanks everyone for joining.
15:56:55 <vishalmanchanda> #endmeeting