08:04:40 <yasufum> #startmeeting tacker
08:04:41 <openstack> Meeting started Tue Jul 28 08:04:40 2020 UTC and is due to finish in 60 minutes.  The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:04:42 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:04:44 <openstack> The meeting name has been set to 'tacker'
08:06:25 <yasufum> As I shared in #tacker after last meeting, we have four topics remained.
08:06:29 <yasufum> #link https://etherpad.opendev.org/p/tacker-meeting
08:07:01 <yasufum> I would like to start today from the first topic.
08:07:14 <yasufum> #topic tacker_studio
08:08:16 <yasufum> I suggested dropping tacker studio if no one continueing to develop this feature.
08:09:01 <yasufum> Is there anyone to continue that, or agree to drop? What do you think?
08:09:45 <hyunsikyang__> I think let's drop it.
08:10:15 <hyunsikyang__> If we have it , it is useful but, I think it is not Must function.
08:10:15 <yoshito-ito_> I agree to drop it. Unfortunately I can't handle it.
08:10:19 <takahashi-tsc> Unfortunately, I think it will be drop...
08:10:32 <masazumi-ota> I agree to drop.
08:11:57 <yasufum> Thanks.
08:12:11 <hyunsikyang__> good:)
08:12:43 <yasufum> I would like to go to the next topic.
08:12:56 <yasufum> #topic doc_redhat_distro
08:15:14 <yasufum> I remember that Koichi Edogawa proposed a patch for CentOS and asked to support redhat distro. I agreed with him.
08:16:05 <takahashi-tsc> If no one will be assigned, could we proceed with it? As you say, our team has CentOS development environment.
08:16:06 <yasufum> I think supporting redhat in tacker is poor now actually.
08:16:19 <hyunsikyang__> I think so.
08:19:15 <yasufum> I wounder if he or someone using redhat will have the responsibility if possible. Unfortunately, I am a Ubuntu user, and need to some extra work if I i will do it myself…
08:20:25 <takahashi-tsc> Sorry I write proposal above. Could we proceed with it? He is working with me.
08:20:56 <yasufum> Sure, thanks!
08:22:44 <takahashi-tsc> We plan to check docs with CentOS environment. If something is wrong, we will commit patch.
08:26:01 <yoshito-ito_> Thank you takahashi-tsc! I will review it.
08:26:08 <yoshito-ito_> can we move to next topic?
08:26:13 <hyunsikyang__> yes!
08:26:19 <hyunsikyang__> I will review it too.
08:26:50 <takahashi-tsc> thanks!
08:27:21 <yasufum> #topic update_old_doc
08:29:31 <yasufum> As manpreet suggested, there are bugs or wrong descriptions remained. So we should think to revise them.
08:30:17 <yasufum> I am talking about previous releases.
08:32:38 <yasufum> Although it is impossible to fix all of previous docs, I would like to revise not only latest but previous docs as best effort.
08:33:24 <yoshito-ito_> In the main contents, I think `Tacker Installation Guide` and `Tacker User Guide` should be revised because they are important for new uesrs.
08:33:25 <yasufum> manpreet: What do you think? Is it OK, or any other suggestion?
08:33:51 <yasufum> yoshito-ito: Yes. I agree.
08:34:00 <manpreet> Thanks for addressing the issue, yes this would be good initiative.
08:34:51 <yoshito-ito_> `Tacker Installation Guide` is partially updated by yasufumi, and Redhat distro part will be added by takahashi-tsc, so it seems enough.
08:35:28 <yoshito-ito_> but `Tacker User Guide` is missing part.
08:35:41 <manpreet> Just a suggestion, tacker user and contribution guide also have missing links
08:36:08 <manpreet> some are old links
08:37:34 <takahashi-tsc> We should check it... We can detect such missing links because that troubles do not depend on distro.
08:37:51 <takahashi-tsc> "We" means our checking work with CentOS
08:39:43 <yasufum> Thanks
08:40:37 <takahashi-tsc> Please let me confirm, our target is both fixing older documents ( e.g. https://docs.openstack.org/tacker/train/ ) and latest documents?
08:42:35 <yasufum> I think it is yes basically, without critical ones.
08:44:13 <takahashi-tsc> All old document? I think that means 4 version.
08:44:34 <yasufum> However, it depends on how much it is critical, and no need to care before tarin basically.
08:46:09 <takahashi-tsc> Sure. Actually I want to make old one's priority lower...
08:46:47 <takahashi-tsc> Anyway, critical issue should be fixed in old docs too. That's depends on case. I agree
08:48:14 <yasufum> Sure. If there is no comments anymore, go to the next topic.
08:48:50 <yasufum> #topic join-networking-sfc
08:49:04 <yasufum> It is not a topic actually.
08:49:51 <yasufum> manpreet suggested kindly to join for helping networking-sfc.
08:50:13 <yasufum> I am very appreciate if you will do that actually.
08:50:39 <manpreet> Thanks, i have started looking into code..
08:51:23 <manpreet> are we planning to include networking-sfc as part or tacker??
08:52:04 <yasufum> No. It is remained as a sub project of neutron.
08:52:36 <manpreet> Ok I understand
08:52:44 <yasufum> I cannot still make nothing because I have struggled with some tox problem in networking-sfc.
08:53:44 <yasufum> It might be happened only on my env
08:54:01 <yasufum> I would like to start to review it after fixing the issue :)
08:55:30 <yasufum> Although we have almost no time today, is there any other topics?
08:55:48 <takahashi-tsc> Just infromation, today's TST meeting will be skipped...
08:56:00 <yoshito-ito_> Oh...
08:57:03 <takahashi-tsc> Instead, they plan a meeting with members who understand the tests in more detail (STF team)
08:58:19 <takahashi-tsc> I will announce the details if I know.
08:59:46 <yasufum> Thanks for sharing. I understand you are keeping on a talking and going well.
09:00:50 <Liang> Sorry I have a topic about rollback function in cnf-instantiation, could I share it now?
09:01:06 <yasufum> Sure, please go a head.
09:01:52 <Liang> Thanks, in openstack driver, pre_instantion is called during request to write information into VNF_resource table
09:02:48 <Liang> however, the information is seems to be passed by a parameter called "vnf_software_images“
09:03:47 <Liang> in cnf instantiate, we also want to store cnf information by calling pre_instantion, but in cnf instantiate we dont have "vnf_softerware_images"
09:04:12 <Liang> and the information of cnf is saved in artifact_files in instantiate request instead
09:05:07 <Liang> So here, I want to confirm could we add instantiate_request to pre_instantiation, to parse cnf information
09:05:55 <Liang> of course, this parametere change is also needed in openstack_driver and lcm_driver samely
09:10:12 <yasufum> Liang: Thanks for sharing. It seems just a bit complex to discuss now. So could you share this issue on ether pad and we continue to discuss?
09:10:20 <yasufum> here, https://etherpad.opendev.org/p/tacker-meeting
09:10:46 <Liang> sorry for confusing topic.... of course , I will update it to etherpad
09:11:36 <yoshito-ito_> I will put some comments on the etherpad, too
09:11:51 <yasufum> You can add your topic as 6th one.
09:12:18 <yasufum> Ah, it seems you are already editing. Thanks.
09:12:24 <Liang> yoshito-ito_: Thanks!
09:13:07 <yasufum> I would like to wrap up this meeting, thnaks for joining.
09:13:27 <takahashi-tsc> Thanks
09:13:32 <yasufum> bye
09:13:35 <manpreet> thanks bye
09:13:48 <yasufum> #endmeeting