08:04:11 #startmeeting tacker 08:04:12 Meeting started Tue Jul 12 08:04:11 2022 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:04:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:04:12 The meeting name has been set to 'tacker' 08:04:31 #link https://etherpad.opendev.org/p/tacker-meeting 08:04:36 Now I write very small 2 confirmation. 08:04:47 Can I start? 08:05:12 go ahead please 08:05:42 First, about PTG and just confirm update. Does anyone know PTG is only F2F or hybrid? 08:06:11 I'm concerned that early bird deadline is soon... 08:07:22 I think so 08:08:21 If noone know, I'll confirm to some TC members... 08:08:34 I've been confirming about it via team survey on ptg registration, but not sure when a response will be made. 08:09:15 Thanks. OK... we will confirm it continuousky. 08:09:40 #link https://www.eventbrite.com/e/project-teams-gathering-columbus-2022-tickets-374118026087?_ga=2.224692186.1944712300.1657557943-21017074.1657557943 08:10:25 as takahashi-tsc mentioned, it's $250 USD for early bird, deadline is the end of this month. 08:11:05 It's not free for the next ptg unexpectedly :) 08:11:39 yeah... 08:12:40 Anyway, now no one know it, Please share the information if you get. 08:13:13 sure 08:13:33 If no other comments, I'll move on next topic. 08:13:41 ok 08:14:26 2nd topic is about python-tackerclient. Now my team member faces issue. Does anyone know there is some issue of python-tackerclient? 08:14:27 https://review.opendev.org/c/openstack/python-tackerclient/+/847746 08:15:05 This is just confirmation. We will share our understanding at next this IRC. but If someone know the cause, I'd like to know. 08:15:15 I haven't noticed the issue. 08:17:15 OK... it seems environment issue, so we will investigate it and want to discuss it at next IRC. 08:17:30 It seems a problem of dependencies of libs from the log. 08:17:44 Yes. 08:19:50 OK, if you know or notice something, please let me know. At least we will share our understanding. 08:20:33 Or... we may submit some patch to resovle it. 08:21:27 ok 08:21:43 That's it. Thanks, 08:22:41 thanks for sharing 08:23:56 Any other topic, or close this meeting? 08:24:01 i have one topic, but forgot to update etherpad. should i carry it over to the next week? i'm not in rush 08:24:38 no problem discussing today. 08:24:50 thanks 08:25:42 my topic is about mistral. as you know, Tacker has the dependecy on mistral. 08:26:17 so we need to deploy mistral along with takcer 08:26:52 but, usually, it's just used for vim alive monitoring. 08:27:38 that you can see as `Reachable/Unreachable` when you call `openstack vim list` 08:28:13 Since Tacker is VNFM now, alive monitoring for vim is not a requierement. 08:28:28 so, we want to add configuration to disable this feature. 08:28:36 so that we can deploy tacker without mistral. 08:28:56 could you tell me your opinion? 08:30:48 any comment? 08:31:12 I think there was a proposal to change to not use "mistral". 08:31:23 spec: https://opendev.org/openstack/tacker-specs/src/branch/master/specs/yoga/vim-monitor-feature.rst 08:31:33 WIP patch: https://review.opendev.org/c/openstack/tacker/+/828638 08:31:52 Is it different from this? 08:33:00 Ah, this is my team's patch.Basically it may work, but now we do not proceed with it. 08:34:18 looks similar, but it adds a new feature, isn't it? 08:34:19 (just priority...) 08:34:43 Yes. we plan to add new monitoring feature. 08:35:12 But h_asahina's proposal is, monitoring feature itself is out of scope, isn't it? 08:35:23 yes 08:35:58 but my first priority is excluding mistral when deploying tacker, so it might work. 08:36:26 if this patch doesn't use mistral. 08:36:42 Yes, tihs doesn't use mistral. 08:37:30 let me confirm. the reason you leave vim monitoring feature is the backward compatibility? 08:37:31 The first purpose of this patch is to fix some bug, but now the bug is not reproducible (I forget the details...) 08:38:44 i mean you can just remove the dependency on mistral, but you didn't 08:40:08 Purpose is to fix bug, and the way is remove dependecy on mistral because it is difficult to follow fully mistral features. 08:41:00 Maybe... sometimes VIM status is not changed to Reachable even VIM works properly. 08:41:40 Sorry, VIM status *was* not changed to Reachable, but now the bug is not reproducible. 08:42:52 if so, removing the vim monitoring can be an option. 08:43:00 Yes, correct. 08:43:57 if there's no objection, I'd like to recommend to change this patch to remove the vim monitoring itself. 08:45:02 also, maybe, we can take over that patch, if the original commiter don't have enough time and if he/she doesn't mind. 08:46:04 I agree with you. In addition, I tihink VIM status is only used for desply the status. e.g. Tacker try to use VIM even if the status is unreachable. This status is meaningless... 08:46:23 Thanks, could you take over the patch? 08:46:43 yes. i will. 08:47:02 Many thanks. 08:47:20 my pleasure. thank you too. 08:47:41 thx 08:49:14 so, it might be discussed enough 08:51:10 Let's close this meeting if no one has item anymore. 08:52:44 ok 08:52:57 Thank you for joining, bye! 08:53:06 thanks bye. 08:53:07 bye 08:53:09 nye 08:53:13 bye 08:53:14 thanks, bye 08:53:16 bye 08:53:19 bye 08:53:20 thanks bye. 08:53:27 #endmeeting