08:03:04 <yasufum> #startmeeting tacker
08:03:04 <opendevmeet> Meeting started Tue Jun 22 08:03:04 2021 UTC and is due to finish in 60 minutes.  The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:03:04 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:03:04 <opendevmeet> The meeting name has been set to 'tacker'
08:04:20 <yasufum> We have two topics on etherpad.
08:04:35 <yasufum> #link https://etherpad.opendev.org/p/tacker-meeting
08:04:57 <yasufum> Can we start from first one?
08:07:10 <h_asahina> Sure. Can I explain it?
08:07:29 <yasufum> yes
08:09:25 <h_asahina> Recently, we are considering to provide vagrant box on the official document of Tacker for the ease of development.
08:10:10 <h_asahina> We'd like to know if it's useful or not.
08:11:16 <h_asahina> So, please tell us the development environment you use on the etherpad. I made a survey form.
08:13:52 <yasufum> Thanks
08:15:30 <ueha> I wrote on etherpad. (Vagrant+)
08:15:50 <h_asahina> Thanks
08:16:29 <yasufum> I’d confirm the point of your survey correctly.
08:18:19 <yasufum> because vagrant provides several types of provider, such as virtual box or vmware or so
08:18:36 <yasufum> What do you want know is the number of people using vagrant, right?
08:19:50 <yasufum> Do you think of providing several types of boxes?
08:20:46 <yasufum> In my case, I use vagrant with virtualbox.
08:21:48 <h_asahina> I think we can, but I assumed the vagrant with virtualbox.
08:22:59 <yasufum> understand
08:24:38 <h_asahina> I think write it clearly, i.e., we are basically assuming vagrant with virtualbox. What do you think?
08:25:16 <yasufum> umm… I’m not sure it is the typical case.
08:26:40 <yasufum> What do you think adding options, virtualbox and libvirt are enough, under ‘Vagrant’ instead?
08:29:28 <h_asahina> Sorry, what do you mean? do you mean intergrating virtualbox and libvirt into Vagrant?
08:30:10 <yasufum> Anyway, I hope everyone tell us your usecase on the survey, thanks.
08:30:34 <yasufum> Is there any other comment?
08:30:49 <ueha> I use vagrant with libvirt as provider. but I think either is fine as long as it can be used as a development environment.
08:31:11 <yasufum> :)
08:32:13 <ueha> Will you create a vagrant box and upload it to the cloud? Or will you start up a virtual machine with a provision in the Vagrantfile?
08:33:54 <ueha> I want to know what mean "to provide vagrant box" you said.
08:35:40 <h_asahina> I mean uploading the boxes with the development environment to Vagrant Cloud.
08:38:02 <ueha> Thanks, I understood. Does box contain everything before users clone devstack to build the environment?
08:39:15 <ueha> I think users want to use latest environment or any stable version.
08:40:49 <h_asahina> I understood.
08:41:02 <ueha> Anyway, it's great to make it easier for new users and developers to build environment!
08:41:34 <h_asahina> I considered to provide the box that VNF package has already instantiated.
08:41:59 <h_asahina> So that user can follow the instruction on the official document easily.
08:42:21 <h_asahina> So, it might not be the latest version.
08:44:05 <h_asahina> But, we can provide a box with the latest version of Tacker as well. So the answer for your question can be YES.
08:45:33 <ueha> Thanks, It would be good if the user can customize it easily.
08:45:52 <yasufum> I believe we have several options for providing such a environment,
08:46:24 <yasufum> for example, providing several boxes, or boxes only for stable and Vagrantfile for the latest, or so.
08:46:52 <yasufum> I think we need to have further discussion for conclusion.
08:47:09 <h_asahina> I agree
08:47:20 <yasufum> Please continue to do so on the next meetings or etherpad.
08:47:46 <h_asahina> I got it
08:48:18 <yasufum> If no more comment, go to the next topic.
08:48:31 <yasufum> from ueha
08:48:46 <ueha> Yes, it is the topic that I announced last week.
08:49:11 <ueha> Just information sharing from me about "Zuul FT Environmental Performance of MgmtDriver".
08:49:34 <ueha> In the Wallaby release, the FT on Zuul in mgmtDriver, which builds the k8s cluster, had a problem and placed it in the sample folder.
08:49:51 <ueha> As discussed in the past, refer to https://meetings.opendev.org/meetings/tacker/2021/tacker.2021-02-09-08.03.log.html#l-65
08:50:26 <ueha> Since then we have continued to try to pass FT of  the mgmtDriver for k8s cluster on Zuul, and found that the Zuul environmental performance made it difficult to complete the FT in time.
08:51:28 <ueha> The Xena release also updates the mgmtDriver for k8s cluster, but I think it is difficult to pass the Zuul FT by above reason.
08:52:48 <ueha> So I would like to share with you that we are going to place the Xena development results (mgmtDriver for k8s driver) in the sample folder.
08:53:36 <ueha> That's all from my side. any comment or question?
08:54:21 <yasufum> Do you know what is the reason why it doesn’t pass?
08:55:37 <ueha> The reason is that it times out with a time limit of 3 hours.
08:56:13 <yasufum> I don’t know it can be fixed or not actually.
08:57:15 <yasufum> I remember we had similar issue before, and fixed it by separating zuul’s tasks.
08:58:24 <yasufum> What do you think we cau take the same approach, or difficult to separate?
08:59:20 <ueha> Yes, but too many times spend during build k8s cluster in one testing. So it is difficult to separate..
09:00:00 <yasufum> Sorry, divided processes into several nodes correctly.
09:01:58 <ueha> Currently, the time has expired when the k8s master node was built by mgmtDriver.
09:03:53 <yasufum> Do you know which part of building k8s is the most costly?
09:05:44 <ueha> "k8s master node was built by mgmtDriver" is most costly, at the moment.
09:06:28 <ueha> but, then there is the worker node build.
09:07:33 <ueha> (85 minutes is needed to installing a single MasterNode.)
09:08:43 <yasufum> OK, I understand about the situation roughly.
09:09:30 <yasufum> It seems we have no other choices now…
09:09:58 <ueha> Yes..
09:10:46 <yasufum> but I would like to dive into it because it should be tested if possible, not just a sample code.
09:11:25 <yasufum> Is there any question or comment?
09:11:58 <yasufum> or topic?
09:12:09 <manpreetk> JFYI, the FT cases are failing while migrating sqlalchemy 4.1.
09:12:09 <manpreetk> https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_95f/796160/4/check/tacker-functional-devstack-multinode-legacy/95f3b8e/testr_results.html
09:12:09 <manpreetk> I am trying to reproduce the issue in local env.
09:12:09 <manpreetk> On reproduction, would revert sqlalchemy changes to rule out the cause of gate job failure.
09:12:09 <manpreetk> And in parallel I am investigating aodhclient error, one pointed by Ueha san.
09:12:11 <manpreetk> https://zuul.opendev.org/t/openstack/build/95f3b8e79e7f4635b8d5a44ee85673a0/log/controller/logs/screen-h-eng.txt?severity=4
09:12:40 <ueha> yasufum: thanks
09:13:32 <yasufum> manpreet: thank you for your effort.
09:15:04 <yasufum> Unit tests are all green, but just some failures remained in FTs.
09:15:50 <manpreetk> Yes and need to check whether its SQL changes or something else. Any help will be highly appreciated :) Thanks
09:16:04 <yasufum> thanks
09:16:58 <ueha> Thank you! I will comment again if I know something.
09:17:05 <manpreetk> Thanks ueha :)
09:18:09 <manpreetk> Thats all from my side. Thanks
09:20:28 <yasufum> Although it is the time to close this meeting, I have one thing to ask you shortly.
09:22:00 <yasufum> It is closed to the end of the time for spec freeze, June 30th as we agreed in the previous vPTG,  so please help reviewing sugggested speces.
09:22:09 <yasufum> going to be merged.
09:22:37 <hirofumi-noguchi> I will upload patch sets of my Specs by the end of this week.
09:22:55 <hirofumi-noguchi> I am making corrections corresponding to the review comments.
09:23:35 <takahashi-tsc> Sorry, we should update some spec but not completed yet, We will hurry in this week
09:23:36 <hirofumi-noguchi> In addition, I will upload a new Spec regarding SOL v3 API.
09:24:12 <hirofumi-noguchi> The upload of new Spec is likely to be next week or the week after. I am sorry for late.
09:24:28 <hirofumi-noguchi> I would like to update it if I can.
09:25:06 <masaki-ueno> I'm also working on correcting specs, thank you for your comments. > ueha, manpreet :)
09:26:05 <yasufum> hirofumi-noguchi: For the new one, is it not so big change as required to have a discussion for, right?
09:27:33 <hirofumi-noguchi> Yes, most of all are same as v1 API. I think the changes are very small.
09:28:13 <yasufum> OK, thanks
09:28:48 <yasufum> masaki-ueno: Thanks for sharing.
09:29:46 <yasufum> If no more comment, I’d like to close this meeting.
09:30:41 <yasufum> Thanks for joining, bye.
09:30:45 <takahashi-tsc> thanks
09:30:46 <ueha> Thanks, bye
09:30:49 <manpreetk> thanks bye
09:30:51 <hirofumi-noguchi> thanks
09:30:53 <masaki-ueno> bye
09:31:06 <yasufum> #endmeeting