13:30:03 <dmcbride> #startmeeting OPNFV daily release 13:30:03 <collabot`> Meeting started Mon Mar 20 13:30:03 2017 UTC. The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:30:03 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic. 13:30:03 <collabot`> The meeting name has been set to 'opnfv_daily_release' 13:30:10 <dmcbride> #topic roll call 13:30:17 <yujunz-zte> #info Yujun Zhang 13:30:18 <dmcbride> #info David McBride 13:30:33 <chigang> #info Justin chi 13:30:37 <trozet> #info Tim Rozet 13:30:43 <trozet> is this irc only or is there gtm? 13:30:53 <dmcbride> trozet: IRC only 13:32:12 <sergmelikyan> #info Serg Melikyan 13:32:50 <dmcbride> #topic installer status 13:33:13 <dmcbride> sergmelikyan: what's the status of Fuel? 13:34:37 <dmcbride> sergmelikyan: looks like daily and verify are passing 13:35:05 <dmcbride> sergmelikyan: but problems with scenario deployment 13:35:28 <dmcbride> trozet: how about Apex? 13:35:38 <trozet> dmcbride: looking much better I think 13:35:45 <sergmelikyan> dmcbride: yep, still working but already close 13:35:59 <trozet> dmcbride: we uncovered a bug yesterday with our fdio deployments and fixed it, so now those are deploying successfully 13:36:15 <trozet> dmcbride: functest results are low for nosdn-fdio, and we ahve a fix for that as well 13:36:40 <trozet> dmcbride: nosdn-nofeature passes all tests except 1 test case in tempest defcore 13:36:57 <dmcbride> #info trozet reports we uncovered a bug yesterday with our fdio deployments and fixed it, so now those are deploying successfully 13:37:06 <trozet> sorry i should have used info 13:37:10 <yujunz-zte> Good news 13:37:50 <dmcbride> #info trozet reports that functest results are low for nosdn-fdio, and we ahve a fix for that as well 13:38:35 <dmcbride> sergmelikyan: what's the status of the blocking issues that you told me about last week? 13:39:28 <dmcbride> Fuel: 13:39:29 <dmcbride> #1672969 - Provison failed with error: Сritical nodes are not available for deployment 13:39:29 <dmcbride> #1672683 - [10.0] Failed to deploy env due to failed connnectivity task 13:39:30 <dmcbride> KVM 13:39:32 <dmcbride> KVMFORNFV-75 - [kvm_ovs_dpdk][kvm_ovs_dpdk_bar][HA][Healthcheck] Couldn't get ip from dhcp 13:39:34 <dmcbride> Tempest 13:39:36 <dmcbride> #1577632 - SSH Client hangs on execute command 13:40:17 <dmcbride> chigang: how is Compass? 13:40:48 <dmcbride> narindergupta: are you available to join on IRC? 13:40:59 <sergmelikyan> I don't have latest status, pma can you clarify for me? 13:41:20 <sergmelikyan> all 4 bugs doesn't have patches in upstream 13:41:30 <sergmelikyan> but I saw that pma is workaround thing in Fuel 13:42:42 <chigang> dmcbride: deployment are ok now, few testcases failed in Functest and yardstick, still in working. 13:43:05 <pma> yeah, we've workaround them until we get them fixed in upstream 13:43:36 <pma> KVMFORNFV-75 stiil in progress 13:44:09 <pma> #1577632 - SSH Client hangs on execute command - is on review 13:44:46 <dmcbride> #info pma provides updates on Fuel blocking issues 13:45:15 <dmcbride> #info pma says #1577632 - SSH Client hangs on execute command - is on review 13:45:38 <dmcbride> #info pma says KVMFORNFV-75 stiil in progress 13:46:24 <dmcbride> #info chigang provides update on compass: deployment are ok now, few testcases failed in Functest and yardstick, still in working. 13:46:59 <dmcbride> chigang: Compass is supporting ONOS, correct? 13:47:59 <chigang> dmcbride: yes, support ONOS-nofeature scenario 13:48:11 <dmcbride> chigang: os-onos-nofeature-ha looks like it just started passing today 13:48:45 <dmcbride> #info chigang notes that Compass does support ONOS-nofeature scenario 13:50:27 <dmcbride> pma: how about 1672969 or 1672683? 13:50:35 <chigang> dmcbride: just cherry-pick on Saturday 13:51:06 <dmcbride> chigang: you mean the fix for the onos scenario? 13:51:39 <pma> dmcbride> still in progress in upstream, but we've woraround for them 13:52:10 <dmcbride> sergmelikyan: any concerns about releasing one week from today? 13:52:11 <pma> dmcbride> they shouldn't affect CI deployments yet 13:52:16 <chigang> yes, the fix patch is merge in branch on Saturday 13:52:29 <chigang> dmcbride: yes, the fix patch is merge in branch on Saturday 13:53:17 <dmcbride> yujunz-zte: I saw your email about qtip. Thanks for the clarification. 13:53:48 <yujunz-zte> You are welcome. dmcbride 13:55:29 <dmcbride> trozet: could you please update the scenario status page: https://wiki.opnfv.org/display/SWREL/Danube+Scenario+Status 13:56:03 <dmcbride> trozet: I need to know your intent to release for scenarios for Danbue 1, 2, 3 13:57:10 <trozet> dmcbride: will do 13:58:54 <dmcbride> #topic schedule 13:59:18 <dmcbride> #info please be aware of important milestones coming up 14:00:54 <dmcbride> #info In two days (March 22) we need to resolve Jira tasks for Danube 1.0. This means that all tasks assigned to Danube 1.0 should be resolved or closed. Any tasks that can't be completed for 1.0 should be reassigned to a future release. 14:01:28 <dmcbride> #info in four days (Fri, March 24) final documentation is due 14:02:05 <dmcbride> #info one week from today (March 27) will be the release of Danube 1.0 14:03:01 <dmcbride> #info if you have not done so, please update the scenario status page with your intent to release for Danube 1, 2, and 3 14:03:07 <dmcbride> #link https://wiki.opnfv.org/display/SWREL/Danube+Scenario+Status 14:03:35 <dmcbride> ok - that's it for today 14:03:48 <yujunz-zte> Thanks, bye 14:03:59 <dmcbride> if you have questions/concerns, catch me on IRC, or send me mail 14:04:05 <dmcbride> #endmeeting