08:01:58 #startmeeting tacker 08:01:58 Meeting started Tue Feb 27 08:01:58 2024 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:01:58 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:01:58 The meeting name has been set to 'tacker' 08:02:04 #link https://etherpad.opendev.org/p/tacker-meeting 08:02:27 Hello everyone 08:02:37 hi 08:03:08 So, let's start the meeting 08:03:28 The first item is just an announcement for the next vPTG. 08:04:39 It's also announced on the ML, so please find the details of the event. 08:05:18 I'll book our time slots as we usually setup, 05:00-07:00 UTC or 15:00-17:00 JST. 08:05:53 I think three days is enough for our sessions, but it can be changed. 08:06:41 Please let me know if you request other than my candidate days will be registered on PTG bot page later. 08:06:43 Thanks 08:06:55 Any question, or go to the next item? 08:07:41 Nothing, thanks for your announcement. 08:07:50 OK, go to next. 08:08:08 It's a request for review from ueha. 08:08:18 Yes, I have requested some reviews for bug-fix patches. 08:08:30 This weekend (1st Mar.) is "Final release for client libraries", so please kindly review the python-tackerclient patches especially. thank you. 08:08:42 ok, thanks. 08:09:29 good 08:10:02 And the rest of the two items are from renu. 08:10:59 The item is "Regarding zuul job for compliance test in tacker from non-voting state to Voting" 08:11:50 As per investigation, current type of operationParams in DB is ‘longtext’. it is not possible to store object type directly in DB. So, will have to convert object type operationParams to json string before storing in DB and convert it back to json object from json string when retrieving from DB 08:12:30 We are planning as a fix no change in field type in Database keep is same as "‘longtext". ​ Storing operationParams as json string(in logtext type as in current flow) in the database and convert it back to object when retrieving data from the database. 08:13:18 We would like to get input from community member for bug fixes approach 08:14:15 thanks 08:14:22 Any comment? 08:16:40 I'm not sure actually, but it seems nothing bad from the change. 08:16:55 of planning. 08:18:22 renu: Do you know is there any concern, or nothing? 08:18:42 Yes , I would like to know if any concern 08:20:20 OK, there is no negative feedback from the team. 08:20:31 great , thanks 08:22:06 good 08:22:20 So, let's move on to the final topic. 08:22:33 Next item is "Regarding Dockerfile fix for CentOS support patch https://review.opendev.org/c/openstack/tacker/+/909072" 08:23:40 Currently working CentOS support patch and facing issue in zuul build. Currently, the sol_kubernetes_v2 job fails on CentOS due to the usage of the 'apt-get' command in the Dockerfile, which is specific to Ubuntu and not supported in CentOS 08:24:12 As per investigation of code, https://github.com/openstack/tacker/blob/master/samples/tests/functional/sol_kubernetes_v2/tacker-monitoring-test/Dockerfile#L29 08:24:28 The Dockerfile for the sol_kubernetes_v2 job contains the 'apt-get' command for installing the SSH server, which is incompatible with CentOS, leading to job failure on CentOS instances 08:25:41 We would like to community member opinion on the fix approach (resolving the compatibility issue with CentOS in the sol_kubernetes_v2 job Dockerfile)? 08:26:45 thanks 08:28:09 It's OK for me 08:28:17 Thanks 08:29:36 Good 08:30:11 Now all the topics done for today. 08:32:34 So, let's close this meeting. 08:33:46 Before closing, please remind you that it's R5 week and please help for reviewing for remained patches for this release. 08:33:50 Thanks. 08:34:00 Bye. 08:34:04 thanks, bye. 08:34:04 bye 08:34:09 #endmeeting