09:04:56 #startmeeting Compass4nfv weekly meeting 09:04:56 Meeting started Wed Nov 15 09:04:56 2017 UTC. The chair is chigang_. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:04:56 Useful Commands: #action #agreed #help #info #idea #link #topic. 09:04:56 The meeting name has been set to 'compass4nfv_weekly_meeting' 09:05:44 #topic roll call 09:05:50 #info Justin 09:05:52 #info Yifei 09:05:59 #info harry 09:06:42 #info tianwei wu 09:07:08 #topic update from Release meeting 09:07:49 #info Fraser MS3.0 and Euphrates 5.1 release on Dec 15 09:08:31 kvm and ovs_dpdk scenarios are still no t stable in Euphrates 09:09:14 kvm still have restart issue 09:09:42 and dpdk has same restart code 09:10:02 Harry_Huang: yes, kvm failed log in #link https://build.opnfv.org/ci/job/compass-deploy-baremetal-daily-euphrates/256/consoleFull 09:10:46 can we add e.g. wait 3 minutes? 09:11:57 #info kvm and ovs_dpdk scenarios failed because ansible lost compute nodes link after nodes reset 09:12:27 any other suggest? 09:12:41 any other suggestion? 09:13:45 yifei: how long does it wait? 09:14:10 it's a async job 09:14:20 chigang_: it waits for the system up 09:14:35 chigang_: not some time now 09:15:03 https://www.irccloud.com/pastebin/dMLqZiml/reboot_node_code_section 09:15:18 I check the code, it waits 10 minutes 09:16:21 it works fine in HUAWEI-POD2, but fails in HUAWEI-POD1 sometimes 09:16:23 here restart code contains two parts 09:16:54 first is simple restart second is waiting 09:18:00 Harry_Huang: go on 09:19:38 first part is a "fire and go" which is async time period of 1 sec 09:20:23 ansible still connect to this machine in this 1 s 09:21:37 because there are different blade type in HUAWEI-POD1 and POD2, maybe it depends on blade's reset time. 09:22:21 maybe, pod1 are 2288 and pod2 are 1288 09:23:13 the performance of POD2 is better than POD1 09:23:24 hw_wutianwei: thanks 09:23:32 does dpdk scenario have the same situation that successes on pod2, fails on pod1? 09:24:01 one more thing to notice: there is a "sleep 2" in this 1 s async task 09:25:39 KVM often fail on pod2 09:26:26 I suppose we can try to set timeout=1200s delay=10s, it will reduce the networks traffic. 09:28:22 We can first try it to see if it is due to the performance of the restart time. 09:29:38 how about it? 09:30:19 we can test it just on pod2 09:30:57 ok 09:31:05 sure, just checkpick it into Euphrates branch. 09:31:40 #topic Tasks assignment in Fraser release 09:32:15 #undo 09:32:15 Removing item from minutes: 09:33:13 #info set timeout=1200s delay=10s in Euphrates kvm scenarios to check if it is due to the performance of the restart time. 09:33:40 #topic Tasks assignment in Fraser release 09:34:17 #info Fraser tasks are create in #link https://wiki.opnfv.org/display/compass4nfv/Compass4nfv+Fraser+release+plan 09:35:22 #info Please add your name in Own field if you are doing it. 09:35:46 OK 09:36:21 #info If the priority is not appropriate, you can adjust yourself 09:37:28 the wiki page is created according to https://etherpad.opnfv.org/p/compass_release_fraser 09:38:00 you can get more information from #link https://etherpad.opnfv.org/p/compass_release_fraser 09:39:07 #info If the JIRA is missed, please raise a JIRA and paste the JIRA into the WIKI page #link https://wiki.opnfv.org/display/compass4nfv/Compass4nfv+Fraser+release+plan 09:40:02 if I missed some tasks, please add them :) 09:41:06 yifei: I saw your updates, Great jobs 09:41:49 chigang_: THX. Some of them have been done 09:42:05 yifei: super hero in Compass 09:43:08 if there are unclear for some tasks, please mail me. 09:43:28 any comments for this topic? 09:44:20 #topic POD resources update for Fraser release 09:45:33 #info there are 3 physical POD for Compass Fraser release development 09:46:54 #info Intel POD17, Jack Morgen assigns it for Compass #link https://wiki.opnfv.org/display/pharos/Intel+POD17 09:47:49 Intel POD17 VPN access will sent to Yifei and me. 09:48:56 yifei: please follow the status of this POD, it isn't online now. 09:49:14 chigang_: OK 09:50:22 #info the 2nd POD is HUAWEI-POD1 in Huawei Hosting 09:51:23 #info the 3rd POD is HUAWEI ARM POD, it still in progress, maybe online at the end of Dec. 09:52:16 Taishan 2280/256G memory/4T disk/10GE, it is well performance 09:52:36 hw_wutianwei: if some wrong, please correct me. 09:53:09 chigang_: you are right 09:53:28 hw_wutianwei: thanks. 09:54:19 that's all topics from my side, any others? 09:54:28 no 09:55:01 no 09:55:29 fine, it is dinner time. bye. 09:55:41 #endmeeting