15:00:13 <vishalmanchanda> #startmeeting horizon
15:00:13 <opendevmeet> Meeting started Wed Mar 23 15:00:13 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:13 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:13 <opendevmeet> The meeting name has been set to 'horizon'
15:00:58 <vishalmanchanda> hello
15:01:02 <tmazur> o/
15:02:05 <amotoki> o/
15:02:20 <vishalmanchanda> e0ne:rdopiera :ping for horizon weekly meeting
15:04:10 <vishalmanchanda> ok let's start the meeting.
15:04:58 <vishalmanchanda> We have  only one topic added in our today agenda https://etherpad.opendev.org/p/horizon-release-priorities (at Line 32)
15:05:08 <vishalmanchanda> #topic Notices
15:05:29 <vishalmanchanda> few announcements from my side for this week.
15:05:41 <vishalmanchanda> Yoga Schedule https://releases.openstack.org/yoga/schedule.html
15:05:50 <vishalmanchanda> This week is R1 week.
15:06:12 <vishalmanchanda> I have cut the final release of horizon for Yoga cycle and patch is merged.
15:06:36 <amotoki> R1 week is important to us
15:06:40 <vishalmanchanda> #link https://review.opendev.org/c/openstack/releases/+/834444
15:06:48 <amotoki> is tomorrow the deadline for us?
15:07:51 <vishalmanchanda> amotoki: Now release team will use above patch to create stable/yoga branch.
15:08:01 <vishalmanchanda> See https://review.opendev.org/c/openstack/releases/+/833603
15:08:33 <vishalmanchanda> Most probably above merge will merge by today.
15:09:05 <amotoki> vishalmanchanda: I know. I just wonder what is/are requried and what are not?
15:09:54 <vishalmanchanda> Unfortunately https://review.opendev.org/c/openstack/horizon/+/818763 unbales to merge as random integration tests failing again and again.
15:10:12 <vishalmanchanda> unable*
15:11:00 <vishalmanchanda> Once stable/yoga branch is created, any important bug fixed in master needs to backport to stable/yoga branch.
15:12:16 <vishalmanchanda> Let's backport https://review.opendev.org/c/openstack/horizon/+/818763 to stable/yoga after it lands and then after 2-3 weeks we can cut  a new release of horizon for stable/yoga branch.
15:13:30 <vishalmanchanda> amotoki: Do you have any other patch in mind which you are considering for yoga cycle.
15:13:52 <vishalmanchanda> amotoki: np.
15:14:18 <amotoki> vishalmanchanda: I am not sure how horizon works with the default devstack setting for yoga.
15:14:36 <amotoki> perhaps all of you know more :-)
15:14:52 <amotoki> https://bugs.launchpad.net/horizon/+bug/1950659 hits me
15:15:33 <vishalmanchanda> amotoki: yeah let's discuss it separately.
15:15:43 <amotoki> and I am not sure how the situation would be better if we have the better situation with the system-scoped token support
15:16:21 <amotoki> vishalmanchanda: go ahead
15:16:41 <vishalmanchanda> ok moving to next announcement.
15:16:59 <vishalmanchanda> PTG reminder, Please register yourself for PTG if not done yet.
15:17:55 <vishalmanchanda> Also, please add your name if you are going to attend horizon PTG and any topic you would like discuss in PTG and then I will add time slots for all topics.
15:18:07 <vishalmanchanda> #link https://etherpad.opendev.org/p/horizon-zed-ptg
15:19:05 <vishalmanchanda> that's all announcement from my side for this week.
15:19:14 <vishalmanchanda> moving to next topic.
15:19:29 <vishalmanchanda> #topic Bug deputy report
15:19:37 <vishalmanchanda> https://bugs.launchpad.net/horizon/+bug/1950659
15:20:52 <vishalmanchanda> Now if someone uses the latest devstack env. then all of Identity Panel stops working except for Application Credentials.
15:21:34 <vishalmanchanda> You can find more details about the issue in https://bugs.launchpad.net/horizon/+bug/1965969
15:21:49 <vishalmanchanda> which is duplicate of bug 1950659.
15:22:41 <vishalmanchanda> It happens because horizon still uses keystone admin endpoint which is dropped by keystone.
15:23:11 <vishalmanchanda> amotoki: I tried a workaround which fix the issue but not sure if that is accepted.
15:24:13 <amotoki> I did not succeed to run horizon properly just after adding 'admin' endpoint of 'identity' service.
15:24:33 <amotoki> I did not have enough time to debug it today
15:24:38 <vishalmanchanda> amotoki: what I have done replace  'adminURL': 'admin' with  'adminURL': 'public' here https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/base.py#L302
15:25:50 <amotoki> not sure. IMHO I don't perfer such ad-hoc workaround though.
15:26:27 <vishalmanchanda> I was looking at what other OpenStack projects have done and found something like this.
15:27:21 <amotoki> vishalmanchanda: at least other core services work properly
15:27:35 <vishalmanchanda> amotoki: yes.
15:28:04 <vishalmanchanda> ok, let's keep investigating this issue.
15:28:06 <amotoki> (except documented downsides like neutron admin-ness)
15:29:23 <vishalmanchanda> amotoki: sorry what do you mean? are you saying that we should document this as a known issue in our docs?
15:29:29 <amotoki> I think what we need at least is to clarify what do work and what do not work
15:29:46 <vishalmanchanda> yes.
15:30:50 <vishalmanchanda> amotoki: Could you push a patch for the documentation about this issue.
15:30:54 <amotoki> vishalmanchanda: regarding neutron, (while it does not land and/or it is not proposed yet) the neutron team recognizes what is the gap and we need to document the gap. That is what I would like to kena.
15:31:22 <amotoki> vishalmanchanda: I can push a patch for neutron but not for horizon :p
15:32:32 <amotoki> for example, neutron now requires to specify --project to allow for the operators to cratea a provider network.
15:32:34 <vishalmanchanda> amotoki: ok where we should document this in the horizon? I can push a patch.
15:32:40 <amotoki> this is an example.
15:33:06 <amotoki> vishalmanchanda: if there is a gap, we need to document it at least.
15:34:02 <vishalmanchanda> amotoki: I am asking about the path where we should document it.
15:34:21 <amotoki> vishalmanchanda: as the baseline, does yoga horizon work as operators expect what they expect for xena?
15:35:16 <amotoki> vishalmanchanda: there are several ways to document it but I am not sure what is the current stuations....
15:35:43 <amotoki> tmazur: do you have any inputs from rhosp perspective?
15:37:45 <vishalmanchanda> Ok, I will take a look and try to push a patch to document this gap/issue.
15:40:31 <tmazur> amotoki: I don't think we have anything from our perspective
15:40:52 <vishalmanchanda> Deos anyone like to discuss any other topics?
15:41:53 <amotoki> tmazur: thanks. let's clarfiy whether it is okay or not. At least I failed to run horizon with the latest devstack with the default configs today...
15:43:51 <amotoki> vishalmanchanda: I wonder if the system-scoped update is required for the initial yoga release or not. what's really missing?
15:44:27 <amotoki> what does not work with the system-scoped token support and what does work with it?
15:45:10 <amotoki> I think it is important whether horizon is totally broken or not.
15:45:32 <rdopiera> only the identity panel works with system scope, all the other services are "working on it"
15:46:59 <amotoki> rdopiera: do you mean we need to configure SYSTEM_SCOPE_SERVICES = ['identity'] after your patch?
15:47:44 <rdopiera> amotoki: if you want to use the system scope token, yes, otherwise leave it empty and it will all work as it did in previous versions, without the system scope token
15:47:52 <vishalmanchanda> ++
15:47:59 <rdopiera> amotoki: I left it empty as the default
15:49:26 <vishalmanchanda> amotoki: You can run horizon with devstack after you enable https://github.com/openstack/devstack/blob/master/lib/keystone#L125 I guess.
15:49:28 <amotoki> rdopiera: is it compatbile with xena? I haven't checked what is compatible with xena after 'admin' endpoint for identity was dropped in yoga.
15:50:20 <rdopiera> amotoki: I think I tested it on xena
15:50:31 <amotoki> vishalmanchanda: do you suggest to try KEYSTONE_ADMIN_ENDPOINT == True?
15:50:54 <rdopiera> actually, I even tested it with wallaby
15:51:09 <vishalmanchanda> amotoki: yes, and then you can test rdopiera patch.
15:51:26 <amotoki> rdopiera: I hope so but I failed to check it as several things are mixed.
15:52:35 <amotoki> I see several points:
15:53:01 <rdopiera> there are basically 2 things it should do: 1. if it's non-empty, the system scope option will appear in the menu, 2. the panels associated with the services listed will be moved from project to system scope menu
15:54:34 <rdopiera> without the patch, the system scope menu will be always visible for users who have access to it, and the panels will appear both in project and in system scope
15:55:57 <amotoki> rdopiera: generally you are right, but I was confused because horizon does not work properly after 'admin' identity endpoint was dropped from devstack (without 'admin' endpoint configurred in horizon CI)
15:56:22 <amotoki> rdopiera: it blocks me to test various cases.....
15:56:45 <rdopiera> I see, I missed that
15:58:27 <rdopiera> we can ship without that patch, I'm just afraid that people will be confused with the new menu option and most things not working in it
15:58:51 <rdopiera> it doesn't break anything, it just exposes new functionality that doesn't work yet
15:59:18 <rdopiera> and only to the admin user by default
15:59:30 <vishalmanchanda> rdopiera: honestly I don't see any issue with merging that patch.
15:59:35 <amotoki> regardless of whether your patch lands or not, I think we need to verify our status
16:00:23 <amotoki> I think https://bugs.launchpad.net/horizon/+bug/1965969 is worth checking
16:00:33 <vishalmanchanda> ok we are out time.
16:00:56 <amotoki> I hit it when I tried the latest horizon and it is my outcome
16:01:10 <vishalmanchanda> ending this meeting, please continue your discussion here even after the meeting.
16:01:17 <vishalmanchanda> Thanks everyone for joining!
16:01:28 <vishalmanchanda> #endmeeting