Wednesday, 2021-11-17

opendevreviewRadomir Dopieralski proposed openstack/horizon master: Add system scope support to context switcher  https://review.opendev.org/c/openstack/horizon/+/81636810:57
opendevreviewRadomir Dopieralski proposed openstack/horizon master: Add system scope support to context switcher  https://review.opendev.org/c/openstack/horizon/+/81636812:55
opendevreviewRadomir Dopieralski proposed openstack/horizon master: Add system scope support to context switcher  https://review.opendev.org/c/openstack/horizon/+/81636814:44
vishalmanchanda#startmeeting horizon15:00
opendevmeetMeeting started Wed Nov 17 15:00:22 2021 UTC and is due to finish in 60 minutes.  The chair is vishalmanchanda. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'horizon'15:00
rdopierao/15:00
vishalmanchandahi all15:01
vishalmanchanda#link https://etherpad.opendev.org/p/horizon-release-priorities (at line 30)15:01
vishalmanchandalet's wait for few minutes if more people joins us.15:02
tmazuro/15:02
vishalmanchandaok let's start the meeting.15:03
vishalmanchanda#topic Notices15:04
vishalmanchandaThis week is Yoga-1 milestone.15:04
vishalmanchandaYoga Schedule https://releases.openstack.org/yoga/schedule.html15:04
vishalmanchandathat's the only announcement from my side for this week, If anyone else have any announcement to make please go ahead.15:04
vishalmanchandamoving to next topic15:05
vishalmanchanda#topic Django3 Support15:05
vishalmanchandaPatch to bump Django lower version to 3.2 is already merged in openstack/requirements.15:06
vishalmanchanda#link https://review.opendev.org/c/openstack/requirements/+/81509615:06
vishalmanchandaSo Now we can drop the Django2.2 support from horizon and a patch for the same is already up and gate jobs are passing.15:07
vishalmanchandahttps://review.opendev.org/c/openstack/horizon/+/81781415:07
vishalmanchandaPlease take a look at patch, so we can drop Django2.2 support asap.15:08
vishalmanchandamoving to next topic15:08
vishalmanchanda#topic drop django launch instance implementation15:08
vishalmanchandaJust an reminder CI is passing for the patch now so please so we can drop it early in this cycle.15:08
vishalmanchandahttps://review.opendev.org/c/openstack/horizon/+/81630315:09
vishalmanchandae0ne: ^^15:09
vishalmanchandanext topic15:09
vishalmanchanda#topic System Scope support in horizon15:09
vishalmanchandardopiera: Please let me know once your patch is ready to review.15:09
vishalmanchanda#link  https://review.opendev.org/c/openstack/horizon/+/81636815:10
rdopieravishalmanchanda: it should be ready as soon as the tests pass, but I keep finding things I forgot about15:10
rdopieraI would like to ask about opinions on how to proceed from this patch15:11
vishalmanchandardopiera: good, Do I have to apply python-keystoneclinet patch as well in my env to test it?15:11
rdopieraIt only adds the "system scope" menu entry to the context switcher, but we still need to display the correct panels when that is selected15:12
rdopieravishalmanchanda: I made it so that if the keystone client doesn't have that method, it falls back to just trying to get the token and catching the error if it fails15:12
rdopieravishalmanchanda: so it should work with any version of keystone client15:12
rdopierahowever, I noticed that our tests run with keystone api v2 configured, and we need v3 for this to work15:13
amotokirdopiera: which part of our tests uses keystone v2?15:14
vishalmanchanda_sorry I got disconnected.15:14
rdopieraamotoki: I got test failures with: AttributeError: 'AccessInfoV2' object has no attribute 'system_scoped'15:17
rdopierafor example here: https://zuul.opendev.org/t/openstack/build/6f981fa3fcbe4e2789e5c34eb79bb8d715:17
rdopieraI made it fall back to False in such cases15:18
amotokithanks for the pointer. it seems v2 is still the default somewhere...15:21
amotokiI see auth_ref contains keystone v2 information...15:22
rdopierafor now I worked around this15:22
rdopieraI also found another problem with tokens: it seems like we always provide the domain paramater when creating the token, and oslo.policy seems to think that the resulting token is a domain-scoped token, and issues a warning when we try to use it for project-scope actions15:23
rdopieraI'm not sure if the check in oslo.policy is wrong, or if we really are getting domain-scoped token15:24
rdopierahowever, the warning says that it will become an error in the next version15:24
vishalmanchanda_rdopiera: Also, some of the panel are completely broken like flavor panel. 15:27
rdopieravishalmanchanda_: you mean when the system scope is selected?15:27
vishalmanchanda_rdopiera: yes.15:28
rdopieravishalmanchanda_: the next step is to only display the panels that work with system scope when it is selected15:28
rdopieraI'm unsure as to how to implement this exactly15:28
rdopieraI will probably just add a flag in the panel definitions15:29
amotokirdopiera: re: domain_id waring, I think we need to adjust _user_to_credentials() in openstack_auth.policy. domain information is unnecesary for a project scope credential, but I need to confirm oslo.policy side too.15:29
vishalmanchanda_amotoki: how can we decide to display which panel or not, any documentation for that?15:30
rdopieraamotoki: I tested that the warning goes away when we remove the domain info from that function15:30
rdopieravishalmanchanda_: right now we check for the admin role, but that is going to be obsolete with system scope15:30
rdopieraI think it is, at least15:31
rdopieraI'm a bit fuzzy on the details15:31
amotokivishalmanchanda_: yeah, panel visibility is determined based on "permissions" and "policy_rules" fields in panels.15:32
amotokiin addition, "admin" check might be affected since the initial impl.15:32
amotokis/be affected/affect/15:32
vishalmanchanda_rdopiera: amotoki ok.15:33
amotokiI don't think we have a doc on this :p15:33
vishalmanchanda_amotoki: yeah we have to check policy rules for each backend services.15:34
rdopieraanother thing that worries me, is that when we switch to the system scope token, all apis stop working, including the ones that should work with system scope15:34
rdopieranot sure if we need to configure something on the other side15:34
rdopierafor instance, admin->system should probably work15:35
rdopierabut it doesn't15:35
amotokiat the moment, in TC discussion we don't plan to enforce system-scope in Yoga. There are still a lot of work required.15:36
amotokiyou can find some notes in https://etherpad.opendev.org/p/policy-popup-yoga-ptg (around L.548 - 569)15:37
rdopierathanks15:38
amotokirdopiera: what about the identity panel?15:38
amotokiI think the identity dashboard is expected to work most.15:38
rdopieralet me quickly check15:39
rdopierathat works15:40
amotokiawesome15:40
vishalmanchanda_rdopiera: amotoki yeah Identity dashboard is working fine, just checked with rdopiera patch15:41
rdopieraso it's probably on nova side15:41
rdopieraor we need to do something special, like a system-scope token that also specifies a project15:42
rdopieraI will try to find out15:43
amotokithere is a discussion in the rbac meeting on how to handle a project-specific information with system-scoped tokens.15:43
rdopieraamotoki: where is that meeting?15:44
amotokirdopiera: it is a meeting on RBAC15:44
amotokiaka the policy-pop-up meeting15:44
rdopieraah the etherpad you linked15:44
amotokiyes15:45
rdopierathanks, I will look into that15:45
rdopierathat's it from me on the system-scope token15:45
amotokithe current direction is to use a projet-scoped token for such cases but we are trying to document such things15:46
amotokiin the governance patch https://review.opendev.org/c/openstack/governance/+/81515815:46
amotokithere are many corner cases to be addressed.15:46
amotokinothing more from me15:47
vishalmanchanda_ok let's keep discussing this topic in further meetings.15:48
vishalmanchanda_Also, glance and neutron panels are also working if switch to system-scope15:49
vishalmanchanda_rdopiera: nice work:)15:49
vishalmanchanda_moving to next topic15:50
vishalmanchanda_#topic Bug deputy report15:50
vishalmanchanda_We have 3 new bugs reported in last 2 weeks.15:50
vishalmanchanda_First one https://bugs.launchpad.net/horizon/+bug/1950933 need to be verified.15:51
vishalmanchanda_Second looks like duplicate of some existing bug and for last a patch is already merged.15:52
amotokivishalmanchanda_: I think it is a report on a different project named "horizon" :p15:52
vishalmanchanda_amotoki: yeah, I will mark it as invalid.15:53
rdopierawritten in C++15:53
vishalmanchanda_I cannot see any topic to discuss in On-Demand Agenda15:55
vishalmanchanda_If nothing else to discuss, we can end this meeting.15:55
amotokimarked bug 1950933  as Invalid 15:55
vishalmanchanda_amotoki: thanks15:55
amotokimy comment is "We never use C++. I believe you filed a bug to a wrong bug tracker." :-)15:56
vishalmanchanda_Last just a review request from the author https://review.opendev.org/c/openstack/horizon/+/80536015:56
vishalmanchanda_tmazur: Could you also take a look at above patch as code is in angular, thanks.15:58
amotokiit is in my queue but I was busy with internal stuffs.... anyway I will check the qos one.15:58
vishalmanchanda_amotoki: thanks.15:58
tmazurI will15:58
vishalmanchanda_tmazur: cool.15:58
vishalmanchanda_Thanks everyone for joining, See you next week.15:59
vishalmanchanda_#endmeeting15:59
amotokio/16:00
rdopierathanks16:03
amotokivishalmanchanda_: tmazur: please do not approve the QoS patch. I just checked the python side, but it already turns out It still needs a lot of cleanups unfortunately.16:20
tmazuramotoki: ok, thank you for reviewing the patch. I'm checking the angular part now, and there's some minor nits so far16:29
amotokiI am a bit afraid such python codes get +2..... should horizon be a pure JS project? (half joking)16:32
vishalmanchanda_amotoki: I also raised a point about min packet rate but then nitish mentioned in release notes as a issues, So i thought we can accept that.16:34
amotokivishalmanchanda_: I don't think we accepted non-working code in our history.16:35
amotokiI see no reason to accept non-working code16:35
amotokiin addition, the release note is not a good place to mention such things.16:36
vishalmanchanda_amotoki: a patch to add those attribute is already up in python-neutronclient16:36
amotokivishalmanchanda_: but there is no corresponding code in openstack_dashboard/api/neutron.py16:36
amotokivishalmanchanda_: I know it, but if so, the direction should be either to use Depends-On or to land the whole code without the neutronclient patch.16:37
amotokianyway, new code related to min packet rate needs to be added in openstack_dashboard/api/neutron.py later, so why not adding the whole code on min packet rate later.16:39
vishalmanchanda_amotoki: code for the minimum packet rule is also added in openstack_dashboard/api/neutron.py https://review.opendev.org/c/openstack/horizon/+/805360/20/openstack_dashboard/api/neutron.py#213116:39
vishalmanchanda_amotoki: yeah, that make sense or use depends-on tag.16:40
amotokivishalmanchanda_: ah, I missed that part somehow. thanks16:41

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