08:01:55 <yasufum> #startmeeting tacker
08:01:56 <openstack> Meeting started Tue Nov 10 08:01:55 2020 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 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:02:00 <openstack> The meeting name has been set to 'tacker'
08:02:33 <yasufum> Do you have any topic today?
08:03:36 <yoshito-ito> hi
08:03:38 <takahashi-tsc> I'd like to share current FT status. I'm updating etherp.ad now
08:04:00 <yasufum> #topic ft-status
08:04:08 <yasufum> OK, please go ahead
08:05:51 <takahashi-tsc> https://etherpad.opendev.org/p/tacker-meeting
08:06:04 <takahashi-tsc> L468-
08:07:32 <takahashi-tsc> I've almost explained but now Ceilometer leads to POST_FAILURE, and Barbican issue is resolved. And recently, some POST_FAILURE occur without ceilometer.
08:08:41 <takahashi-tsc> Now FT environment does not use Ceilometer. First, we should resolve POST_FAILURE without Ceiloemeter (Etherpad L624-)
08:13:37 <takahashi-tsc> Root cause may be out of memory (it is unconfirmed...) But first, we may be able to resolve POST_FAILURE with xz command option. It seems workaround, but should we proceed with such workaround?
08:14:38 <yasufum> It looks this issue has been resolved recently, for example https://review.opendev.org/#/c/751173/
08:15:21 <yasufum> What do you think?
08:20:02 <takahashi-tsc> Hmm... this POST_FAILURE *sometimes* occurs. I think we need some fundamental fix...
08:22:05 <takahashi-tsc> But it does not occur now... I'd like to decide action if POST_FAILURE occurs again.
08:22:16 <yasufum> It might be because some failure was fixed in this patch and many of error logs are disappeared possilbly.
08:22:35 <yasufum> #link https://review.opendev.org/#/c/731636/
08:24:05 <yasufum> But I am not sure that it is the reason why the POST_FAILURE was fixed actually…
08:24:31 <yasufum> We need to have some more study for that as you said.
08:26:21 <yasufum> Anyway, I think we can find logs of FT and continue to review patches from NEC
08:26:31 <takahashi-tsc> OK, first I'll check whether using ceilometer leads to POST_FAILURE again with DNM patch. If occurs again, I'll investigate and share it with Tacker team. I'll also investigate above workaround(xz memory limit).
08:27:16 <takahashi-tsc> And yes, some NEC patches have FT failure... I'll fix them.
08:29:41 <yasufum> FYI. It is still suspicious that some limitations of resources on zuul env is the cause of POST_FAILURE. So, VALinux guys have started to inspect it by this patch.
08:30:03 <yasufum> #link https://review.opendev.org/#/c/762034/
08:30:54 <yasufum> I would like to share the result if needed
08:31:54 <takahashi-tsc> Yes, I've checked it. It seems 1 good approach. I'm glad if we can share the result.
08:33:31 <yasufum> OK, any other comments for the topic?
08:34:48 <takahashi-tsc> I've updated etherpad. (L635-)
08:35:39 <yasufum> thanks
08:36:46 <yasufum> go to the next topic
08:37:29 <yasufum> Do you have any topic, or ask to review your patch?
08:39:21 <yasufum> It seems all for today
08:39:55 <yasufum> But I would like to confirm about specs proposed in the vPTG
08:40:44 <yasufum> I think almost of discussion was finished on etherpad
08:40:49 <yasufum> #link https://etherpad.opendev.org/p/Tacker-PTG-Wallaby
08:41:34 <yasufum> And all of you agree to the proposals.
08:43:02 <yasufum> If no objections for that, I would like to ask you to review tacker-specs to merge them. Thanks.
08:44:40 <yoshito-ito> OK, I will.
08:45:20 <masazumi-ota> OK, I'll check them.
08:45:35 <yasufum> thanks
08:46:08 <yasufum> wrap up this meeting. thank you for joining.
08:46:10 <yasufum> bye
08:46:14 <masazumi-ota> gye
08:46:23 <masazumi-ota> bye
08:46:33 <yasufum> #endmeeting tacker