08:03:24 #startmeeting tacker 08:03:24 Meeting started Tue Mar 5 08:03:24 2024 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:03:24 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:03:24 The meeting name has been set to 'tacker' 08:03:49 #link https://etherpad.opendev.org/p/tacker-meeting 08:03:57 hi 08:03:59 hi 08:04:27 So, let's start this meeting. 08:04:56 There are five items here on the etherpad. 08:05:06 The first two items are mine. 08:05:21 Both of them are about FFE. 08:07:15 For the first topic of the RBAC, I've not noticed it's required to request FFE actually. 08:09:14 gmann has proposed the request kindly, so I'd like to accept it to merge the patches before the end of this cycle if no opposite from tacker team. 08:09:28 Is there any opinion, or agree? 08:10:45 good 08:11:21 +1 08:11:25 It must be everyone agree. 08:11:27 thansk 08:11:48 It's also the same for the second topic. 08:13:00 Although I proposed a spec at the previous PTG for cilium support, 08:13:41 we've met some difficulties for releasing the feature in this cycle. 08:14:35 More exactly, there is some trouble while deploying cilium by management driver with v2 apis. 08:16:03 However, we could avoid it recently, and might be able to upload the patch before the end of this week. 08:16:38 So, I'd like ot request another FFE for the spec. 08:18:02 We're going to send a email for the request on ML later after the meeting. 08:18:45 Thanks. 08:18:56 Is there any comment? 08:20:05 good 08:20:31 It seems we can go to the next item. 08:20:56 Hi 08:21:00 hi 08:21:04 The next item is a proposal for adding tacker installation guide with openstack-helm in official openstack-helm document. 08:22:45 yes 08:24:01 proposed installation guide will be added in official openstack-helm documentation 08:24:14 Link: https://docs.openstack.org/openstack-helm/latest/install/deploy_openstack.html 08:25:55 sounds good 08:26:23 thanks 08:27:52 By the way, have you already uploaded a candidate patch? 08:28:19 I might have noticed, but missing for now... 08:29:17 or not yet? 08:29:26 yes, that patch was meant for adding in official tacker document 08:29:46 this one is for adding in official openstack-helm document 08:30:05 OK, thanks 08:30:39 Any other comment, team? 08:31:43 I have a comment, I thinks other components need to be installed (like barbican). 08:32:21 Will you add the description about related component to openstack-helm's document? 08:32:42 or Tacker only? 08:34:54 we are doing for tacker only 08:35:28 but other components like keystone, glance, barbican etc. needs to be installed 08:35:47 It feels like the https://docs.openstack.org/openstack-helm/latest/install/deploy_openstack.html page only lists representative OpenStack projects. 08:36:53 keystone and glance ...etc are listed in the page, but tacker's required projects(like barbican) are not listed. 08:37:48 I think we should consider whether it is OK to write "only" Tacker. 08:38:08 What do you think? 08:39:08 we can add barbican component in the document along with tacker 08:40:08 because we have installed barbican before installing tacker 08:40:18 ueha san , our proposal is to add only tacker 08:40:36 As we are contributor for tacker. 08:43:09 I understand we're contributor for Tacker. However, I am concerned about the lack of steps required to make Tacker work.. 08:44:12 If required we can make a note for required pre-requisites 08:45:27 Yeah, IMO, I think it is better to write it as a note. 08:47:04 Thanks for the comments. 08:49:22 ueha: can you any other comment for now, or continue on gerrit? 08:49:38 s/can you/do you have/ 08:49:56 there is no additional comment as for now, so let's continue on gerrit. 08:50:20 thanks 08:50:36 With the suggestion will participate Tacker installation setps and in note will mention pre-requisites information 08:51:52 thanks 08:52:46 thanks for your suggestion. 08:53:06 So, let's move on to the rest of items. 08:54:17 request for review 08:54:28 Yes, the remaining topics are mine. 08:54:43 some patches are listed that we requested to review in IRC last week, and I added new two patches. 08:55:13 These added patches are for "NFV Orchestration API v2.0 in Tacker Horizon" and "Obsolete Legacy API", respectively. 08:55:24 Please kindly review the patches. 08:55:45 I have started to review them, sorry for the delay. 08:56:26 takahashi-tsc: thank you. 08:56:51 yasufum: Also, do I need to send an FFE email about the above patches..? 08:59:56 I'm not sure there's any strict rule for that, but it migth be required fro tacker-horize at least. 09:01:32 I think no need for a bug fix, or documentation. 09:02:24 Thanks, I will send an request FFE about the above patches without bugfix/documentation later just in case. (Sorry for my knowledge about FFE. 09:03:32 any other comments? or can I go to next topic? 09:04:21 Please go to the next item. 09:04:38 Thanks. The last topic is about information sharing the current Zuul status. 09:05:03 As you may know, the following patch merge fixes an error that occurred a while ago by oslo.db upgrade. 09:05:14 https://review.opendev.org/c/openstack/tacker/+/910720 09:05:59 However, new issue is occurring now in the job related with k8s, the issue caused by kuryr-kubernetes setup... 09:06:35 Also I investigate the cause, and I have already posted bug report and fixed patch to kuryr-kubernetes. 09:07:32 Tacker's gate (Functional FT jobs related k8s) will fail until the kuryr-kubernetes's patch is merged, so I will sharing and notice it. 09:07:43 That's all from my side 09:08:30 Thanks for your huge contributions. 09:09:28 I hope it will be fixed very soon. 09:10:15 Yeah, I hope too. but core of kuryr put CR-1 just now.. 09:11:16 Anyway, I would like to adjust it somehow so that the gate of tacker passes. 09:11:36 thx 09:11:45 If you have any support, please comment below to gerrit. 09:11:46 https://review.opendev.org/c/openstack/kuryr-kubernetes/+/910962 09:11:57 Thanks 09:14:27 Thanks all for the discussion. 09:14:46 It's already over the end of the time today. 09:14:55 So, I'd like to close this meeting. 09:15:07 Thank you for joining, bye. 09:15:10 Thanks, bye 09:15:12 thanks, bye 09:15:26 #endmeeting