08:02:49 #startmeeting tacker 08:02:49 Meeting started Tue Jan 17 08:02:49 2023 UTC and is due to finish in 60 minutes. The chair is yasufum0. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:02:49 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:02:49 The meeting name has been set to 'tacker' 08:04:08 #link https://etherpad.opendev.org/p/tacker-meeting 08:05:18 Three topics on the etherpad, but the last one might be just a notice. 08:05:42 The first one is a new proposal from yota-kazato. 08:05:50 #topic Proposal to change `token_endpoint` for OAuth2.0 Token 08:05:59 OK. 08:07:06 My proposed topic is regarding `token_endpoint` for OAuth2.0 Token in Tacker. 08:07:49 `token_endpoint` used to get the oauth2 token. 08:08:05 #link https://docs.openstack.org/tacker/latest/configuration/config.html 08:08:28 Current Tacker includes a hard-coding to add `/token` to `token_endpoint`. 08:08:36 #link https://github.com/openstack/tacker/blob/stable/zed/tacker/sol_refactored/common/http_client.py#L204 08:09:09 url = self.token_endpoint + '/token' 08:10:58 `url` means the endpoint of oauth2 token that Tacker requests. 08:11:51 However, this process is redundant or confused for users because the `token_endpoint` of standard auth services includes `/token` in the URIs. 08:13:59 For example, OpenID connect (related to OAuth2) shows that "token_endpoint":"https://server.example.com/connect/token". 08:14:27 #link https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderMetadata 08:15:04 Therefore, I will propose to change `token_endpoint` without the hard-coding " + '/token' ". 08:16:10 My plan is to fix tacker codes (e.g., http_client.py) and documents in Antelope Cycle. 08:16:45 That's all from my sides. Do you have any comments or feedbacks? 08:18:40 I'm still not sure how the current code should be changed. 08:19:01 Need to wait your patch? 08:20:09 To add to the proposed plan, 'url' and 'token_endpoint' will be the same value (not add `/token`.) 08:21:56 > yasufum0 Thanks, your comments. I proposed this topic on IRC meeting because of the impact on existing users/developers. 08:24:07 OK, I understand it's just a tiny change. 08:24:11 If there is no problem from Tacker teams, I would like to discuss how the current code should be changed on the modified patch:) 08:24:46 >it's just a tiny change. Yes 08:25:42 '/token' is included in the variable token_endpoint if it's required 08:25:51 without adding the string value. 08:26:32 I think it's OK to accept the proposal. 08:26:42 Thanks. 08:27:10 Thanks for the summary and agreement. 08:27:34 Any other question, or agree guys? 08:27:42 +1, and will you post blueprint (or bug report?) to LaunchPad? 08:28:47 IMO, registring blueprint should be required, 08:29:14 Thanks, ueha-san. I think it's not a bag, so I will post blueprint. 08:29:20 but not for a bug report or wishlist. 08:29:47 Thanks, I agree. 08:30:15 Thanks all. 08:30:28 Thanks. 08:30:56 So, let's move on to the next topic. 08:31:09 #topic Fix tox4 error 08:32:03 I'd like to share the current status of the fix among team. 08:32:16 Although it's not a patch of mine. 08:32:21 #link https://review.opendev.org/c/openstack/tacker/+/868851 08:33:51 As you may know, we have had several failures in FTs for the critical update. 08:35:34 Many of them might be coinsidental ones as we've already met, and can avoid while several retries. 08:36:27 But one of failure of fenix might not be coincidental possibly. 08:37:49 ueha has tried to find the cause and proposed a possible fix. 08:38:31 Yes, I suspect a bug in the upgraded oslo.db. 08:38:36 as for now. 08:39:20 Do you think the failure will be fixed if oslo.db is modified? 08:39:27 So, just before this meeting, I commented on the survey to Mike who was added to the reviewer. 08:39:48 Yes, I think so 08:40:03 ueha: Thanks for investigating, could you please upload the patch in oslo.db branch, IMO we can get a quick review. 08:40:13 In my environment, I changed oslo.db's code and works fine it. 08:41:07 manpreetk: okay, I will post the patch to oslo.db. 08:41:36 Thanks 08:42:05 After posting the patch, I think you can check with "depends-on" to see if Tacker works. 08:42:18 yes will do 08:42:39 I'm still not sure why the behavior of wsrep_sync_wait has impact on the result because of my lack of understanding, but would like to wait your update. 08:43:59 ok, please wait the patch. :) 08:46:33 I think it might be enough for the topic. 08:48:06 For the last topic, is there any comment for that? 08:48:18 Although I'm not sure who is the owner of the item. 08:49:49 FYI? I added last week. 08:50:22 yes 08:51:08 Is there any reason to remain as today's item? 08:51:56 OIS2023 Tacker proposals are the list I mentioned in the previous IRC meetings. If anyone has the new items, please add titles. 08:52:08 I see. 08:52:16 if nothing, I will close the topic. 08:53:13 might be nothing :) 08:53:30 Anyway, thanks for your notice. 08:54:44 OK, I will close. 08:54:46 And PTG2023 schedule is opened. This is just FYI. 08:55:05 #link https://openinfra.dev/ptg/ 08:55:24 Sure, hope to see you on the event. 08:55:40 Good! 08:56:06 OK, let's close this meeting. 08:56:14 Thanks for joining, bye! 08:56:19 thanks 08:56:26 Thanks, bye. 08:56:27 Ty..Bye. 08:56:41 thanks bye 08:56:43 #endmeeting