08:02:14 #startmeeting tacker 08:02:14 Meeting started Tue Apr 25 08:02:14 2023 UTC and is due to finish in 60 minutes. The chair is yasufum-o. 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:24 #link https://etherpad.opendev.org/p/tacker-meeting 08:03:15 There are two items on the etherpad for today's meeting. 08:04:44 So, let's start from the first item. 08:04:55 #topic SoftwareDeployment support in heat support 08:05:41 As you may know, it has been proposed to drop SoftwareDeployment in Heat 08:06:03 on openstack discuss ML 08:06:35 and we've asked if it's acceptable because this feature is used in heat-translator 08:07:14 although only few codes depending actually. 08:08:00 If we drop this feature, not so many changes in tacker 08:08:20 but required for heat-translator. 08:09:36 In my opinion, there is no proplem if it's dropped 08:10:08 but I'd like to hear thinking 08:10:29 if there is any concerns. 08:10:38 What do you guys think? 08:10:56 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033396.html 08:11:16 You can find the details on the thread. 08:12:34 I think no problem too. I looked at the Tacker code, it seems to be used only for legacy testing. 08:14:23 sure 08:15:41 The concern is for heat-translator :) 08:15:59 I also agree. I'm only wondering if Tacker team need to announce something. 08:16:18 Could I confirm who is core of heat-translator from our team again? 08:18:26 heat-translator core is me and h_asahina-san 08:18:57 OK, thanks. 08:19:58 I'd like to reply the mail to agree to drop it. 08:20:24 +1 08:20:55 We have to delete code related with SoftwareDeployment from "heat-translator" before deleting it from "heat", so I'm worried about the schedule. 08:21:08 I'm sorry I didn't see all the emails, but do you know when heat-team plan to delete it? 08:21:13 Let's discuss a plan how we proceed the task later. 08:22:02 no 08:22:50 Anyway, we can ask it. 08:23:24 any other comment? 08:23:33 Thank you. 08:24:47 I also think schedule and task are important. Let's discuss them continuously. 08:24:52 good 08:24:59 thanks 08:25:52 So, go to the next item. 08:26:44 #topic Next PTG at OIS Vancouver 08:27:39 As already announced on the ML, the next summit will be held 13-15 Jun, and also PTG. 08:29:42 I've just registerd tacker will join the event. 08:30:45 because we NTT guys going to join the event, 08:31:10 and there might be something should be discussed as mid term of the cycle. 08:31:59 I think someone also join from KDDI, correct? 08:33:05 Yes, I and will join from KDDI 08:33:20 Thanks 08:34:30 And there is other possibility of having cross community session also nothing is fixed yet. 08:36:10 Anyway, two people from KDDI and four from NTT are going to go to Vancouver at least. 08:36:57 and more possibly. 08:37:37 So, I'd upload an etherpad for the PTG later before. 08:38:47 I'm not sure if we can join from remote, but it might be doable 08:38:58 via any video conference such as zoom. 08:39:18 That's all 08:39:23 Any comment? 08:41:43 Oops, I've missed to share the link of announcemento of the PTG. 08:41:47 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033291.html 08:44:22 nothing? 08:44:28 good 08:46:00 Although all topics done for today, please keep it in mind that spec freeze is 30th June. 08:46:16 So, let's close this meeting if no more topics. 08:46:36 Sorry, I will share about Zuul CI (ubuntu-focal job) error. 08:47:06 The errors that occurred in the ubuntu-focal job until today are due to updates of other projects. 08:47:20 Currently, the revert patches of the update that affected the error has been merged and probably will pass if you recheck it. 08:47:31 * 881329: Revert "update constraint for tooz to new release 4.0.0" | https://review.opendev.org/c/openstack/requirements/+/881329 08:47:41 * 881430: Revert "Move to python3.9 as minimal python version" | https://review.opendev.org/c/openstack/neutron/+/881430 08:47:58 There may be other problems, but I will let you know the current situation. 08:48:14 That's all 08:48:21 OK, thanks. 08:49:53 Hmm, it seems enough. 08:50:03 Thank you for joining, bye! 08:50:26 Thanks, bye 08:50:27 bye!!! 08:50:36 #endmeeting