08:30:35 #startmeeting yardstick work meeting 08:30:35 Meeting started Mon Oct 30 08:30:35 2017 UTC. The chair is rbbratta. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:30:35 Useful Commands: #action #agreed #help #info #idea #link #topic. 08:30:35 The meeting name has been set to 'yardstick_work_meeting' 08:30:43 #topic roll call 08:30:48 #info Kubi 08:30:53 #info Ross 08:30:58 #info Jack 08:30:58 #info ace___ 08:30:59 #info JingLu 08:31:52 #info Kanglin 08:31:57 #info zhihui 08:33:19 #info Agenda: Docker Ubuntu 16.04, and proposal to add Gotomeeting to this time slot 08:33:42 any other agenda items? 08:34:11 F planning? 08:34:33 #info Rex 08:35:06 rbbratta: for NSB off-line image in artifacts. 08:35:34 kubi001: anything specific for F release planning? 08:35:56 ace___: not sure what you mean, can you clarify? 08:36:34 rbbratta: i think we can move it from etherpad to wiki and organize 08:36:36 rbbratta: did we already go through the F release planning, I missed last week meeting 08:37:08 #link https://etherpad.opnfv.org/p/yardstick_release_f 08:37:10 we started F release gathering. I don't think we have heard from everyone yet 08:37:21 Was looking for China Mobile input 08:37:22 rbbratta: I think we could discuss where could we download NSB openstack image for off0line test. 08:37:42 fanyamei1: ping 08:37:54 Mingjiang: do you have a proposed format to do planning in the wiki? 08:38:12 Where could we local this image , in Yardstick or SampleVNF project artifacts site. 08:38:52 Also today is Holiday in Ireland, so I don't have any more input for features from Intel Ireland team. 08:39:41 ace___: you mean ubuntu cloud image? or do you want to create full NSB SampleVNF image? 08:40:29 rbbratta: i think we can have some epic name defined and then split requirements into each epic. after gathering and discussion, all can be transform to JIRA tasks 08:40:30 kubi001, rbbratta we will discuss about the F release planning test cases and syc it in the etherpad page. 08:40:49 ace___: I think standard procedure is to have the user always build their own image, so they latest image for security updates 08:41:52 Mingjiang: can you create a wiki template for F release planning? 08:41:54 rbbratta: I guess we need to figure out the summary of Fraser planning before this weekend,it cloud be high level and draft. MS1 is Nov. 3 08:42:18 rbbratta: for full image , someone want to have a off-line image to test there openstack environment, If there have one place, I think I could maintain the image as latest. 08:42:26 cloud => could 08:42:27 rbbratta: ok, i'd like to do it. 08:42:51 #link https://etherpad.opnfv.org/p/HA_Testcases_F_Release 08:43:03 this link is from HA team 08:43:07 kubi001: yes, for MS1 we have to produce a release plan, I haven't looked into the details yet. Do you have input? 08:43:59 rbbratta: we need to fill this table before MS1 https://wiki.opnfv.org/display/SWREL/Summary+of+Release+Plans+for+Fraser 08:44:15 ace___: agree, we can keep one in artifacts, someone can build himself whenever he want. 08:44:36 rbbratta: https://wiki.opnfv.org/display/functest/6.+Fraser that is what Functest did 08:45:04 kubi001: okay thanks, I'm looking at the links now 08:45:54 JackChan, ace___ : I think full SampleVNF image is >6GB, can we store large image in artifacts? 08:46:10 rbbratta: seems to large... 08:46:15 to->too 08:46:46 fanyamei1: where there any framework features you need for F-release. I think we talked about call Ansible playbooks from framework. 08:47:01 rbbratta: I have test the image , its almost 4.2GB now 08:47:32 fanyamei1: I remember you proposed some new test cases from CMCC. but I can't find the link now 08:48:19 ace___: when we included collectd with all plugins and DPDK built as shared library it grew to > 4GB yes. 08:49:29 Recently, I put some HA test cases to the HA F release plan 08:50:04 https://etherpad.opnfv.org/p/HA_Testcases_F_Release 08:50:15 fanyamei1: yes, I see, any other test cases from CMCC would be proposed? 08:51:17 As HA and Yardstick Intern project, jianpu developed some test cases for yardstick, do you have any plan to uploaded that test case? 08:51:46 If needed, I can make a more specific need for the framework. 08:53:06 fanyamei1: thanks, besides framework, new test case is also an important part of release planning. 08:53:18 kubi001,yeah, there will be more test cases that we work on in last few months. 08:53:42 fanyamei1: got it 08:55:12 I think for Ubuntu 16.04 ,yardstick need to update the original ubuntu image. Some tools is based on 16.04 now. 08:55:17 Thanks a lot! 08:55:35 kubi001, fanyamei1 : if we add new test cases that installers may want to run as part of CI, that would be useful for the release, especially if Yardstick and Functest results are used to determine release quality. 08:56:27 rbbratta: good point, that test cases would give more high level confidence to end user 08:56:29 ace___: do you mean Docker image, or VNF Ubuntu cloud image 08:57:04 we also have new stress testing POD that we will share time with Bottlenecks team, so we should look at longer duration tests. 08:57:15 Docker image. 08:57:20 :q 08:57:21 and Mingjiang proposed re-balancing the test matrix to increase coverage. 08:57:25 Yeah, that's our target. 08:57:30 sorry... 08:57:37 ace___: yes JIRA https://jira.opnfv.org/browse/YARDSTICK-690 08:57:39 JackChan: do you want to quit? 08:57:59 #topic Update Docker image to Ubuntu 16.04 08:58:11 kubi001: haha...absolutely not 08:58:20 do we know of anything blocking Docker image update from 14.04 to 16.04? 08:58:30 are there old dependencies? 08:59:01 rbbratta: not sure, we need to have a try. Maybe some dependencies. 08:59:29 Do we have volunteer to work on Ubuntu docker update? YARDSTICK-690 09:00:16 I would like to work on it. 09:00:16 rbbratta: I will do this 09:00:20 I think it would be good to start work on YARDSTICK-690 so we can update master container 09:01:23 zhihui_wu, ace___ you can work together? or one can update, the other can test? 09:01:32 maybe I am more familiar with Ubuntu 16.04 "mount" problem. 09:02:22 so I could build the image and debug the problem may happen in NSB image build. 09:02:31 okay, ace___ can update and zhihui_wu you can verify? 09:03:01 yes. sure 09:03:07 ace__, you can build image, I can help to verify the image 09:03:09 we also need to check the API server and GUI and all the features with 16.04 image. 09:03:29 rbbratta: OK, I will take it. 09:03:45 zhihui_wu: I will let you know when I will finish the work. 09:04:08 okay, we are over time limit. any last business? 09:04:08 OK 09:04:14 #topic AoB 09:04:24 The off-line image 09:04:40 #info US Daylight savings time changes on November 5th, need to figure out if GTM meetings change 09:05:13 I think its necessary in offline openstack test. 09:05:20 #info Ross traveling November 5th, might miss meeting, will send email when I know more. 09:05:45 ace___: do you have a proposal? or a Jira task? 09:06:07 I think its not code job. 09:06:33 we need to upload the image ,but where should we load this? 09:06:40 #info I would like to add GTM for this time slot for Intel Ireland team. Will propose details after Daylight savings time change 09:06:42 I will create one Jira 09:06:50 Maybe we can postpone US GTM for an hour 09:07:30 ace___: maybe we could convert SampleVNFs to docker image, and use docker inside the VNF? 09:07:51 JingLu: sounds reasonable 09:08:53 JingLu: you mean Tuesday UTC 00:30 meeting postpone one hour? 09:09:35 I will debug the Ubuntu 16.04 docker first. We could discuss this after the docker job. 09:09:36 yes, does it fit for you? 09:11:59 JingLu: is one hour later better for Shanghai time? 09:12:41 rbbratta yes, it is better for us too. 09:15:24 JingLu: I'll have to check, with Daylight savings time change as well. 09:16:13 we can discuss more next meeting. any other business? 09:17:30 ok 09:18:09 okay, we are done 09:18:12 #endmeeting