08:02:14 #startmeeting tacker 08:02:14 Meeting started Tue Jun 25 08:02:14 2024 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:02:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:02:14 The meeting name has been set to 'tacker' 08:02:26 #link https://etherpad.opendev.org/p/tacker-meeting 08:10:09 sorry, recovered.. 08:10:39 how the meeting going? 08:10:59 nothing discussed yet 08:11:05 ok, thanks. 08:11:20 So, let's start the meeting again. 08:11:56 The first topic is for shareing about the current zuul failure for sqlalchemy. 08:12:27 All the failures on UTs have been fixed, but not yet for FTs. 08:12:48 I'm trying to fix them. 08:13:24 Is there any comment? 08:13:52 Good, it seems nothing. 08:14:29 Then, for the second topic, I don't have any progress for, sorry. 08:15:22 I'm still going to upload it after zuul failures are fixed. 08:16:05 Please discuss the date of spec freeze then. 08:16:28 Any comment, or go to the next topic? 08:16:55 good 08:18:03 The third topic is for sharing a bug report and request for review for the fix. 08:18:23 I've already left some comments on the patch. 08:18:48 And no response from Tatsuji for now. 08:18:57 Yes, thank you yasufm-san. I'll fix the code later. 08:19:09 OK, thanks. 08:20:44 The next topic is about a change plan for documentation of openstack-helm 08:21:01 ok 08:21:11 for which w-juso has asked barbican team. 08:21:27 I share the status regarding the Barbican installation in the openStack-helm documentation that we previously shared on IRC. 08:21:44 hmm 08:22:10 The installation of Tacker using openstack-helm requires the installation of Barbican. 08:22:39 We consulted with the Barbican PJ about making changes to the documentation. 08:23:09 But, Barbican PJ is currently not considering adding this information to the installation documentation. 08:23:38 Therefore, we plan to add a note in the Tacker section of openstack-helm installation document. 08:24:06 I agree. 08:24:16 thank you. 08:24:42 We have not created the patch yet, but we'll share it after uploaded. 08:25:08 that's all from my side 08:26:24 thanks 08:26:46 So, let's move on to the final topic. 08:27:02 By the way, who is the owner of this one? 08:27:35 sorry it's me 08:27:50 OK, thanks. 08:28:58 like I wrote, Kuryr is going to be retired 08:30:08 In dev env with devstack and in FT, Tacker depends on Kuryr 08:30:31 I think we need to find an alternative way 08:31:35 such as creating guidline and Zuul configs to set up K8s VIM on another node from one that Tacker is installed 08:33:33 I suggest that at least we should make a consensus to deal with this issue. What do you think? 08:34:48 Basically, I don't want to maintain kuryr-kubernetes by our team. 08:35:19 agree 08:35:25 I also agree 08:36:23 I think we can drop the dependency from tacker possibly. 08:37:33 Although we need study current codes and confirm it can be done actually. 08:38:03 It might take some time. 08:38:52 Anyway, kuryr-kubernetes will be remained for a while. 08:39:37 So, let's discuss the issue as one of the item 08:39:46 in the next release cycle. 08:40:02 At the next vPTG. 08:40:14 ok, sounds good. I also agree with starting from investigation 08:40:21 +1 08:40:26 yeah 08:41:21 I've already asked some guys understanding tacker's kuryr dependency to analyze 08:42:06 what is required if we drop the dependency. 08:42:31 So, I'll share about them later, or next vPTG. 08:43:14 Thanks 08:43:23 Any other comment? 08:44:19 good 08:44:39 All topics done for today. 08:44:51 Let's wrap up this meeting. 08:45:06 Thank you for joining, bye! 08:45:17 bye 08:45:19 bye 08:45:22 bye 08:45:26 thank you, bye 08:45:29 #endmeeting