13:31:40 #startmeeting OPNFV release daily 13:31:40 Meeting started Fri Mar 31 13:31:40 2017 UTC. The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:31:40 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:31:40 The meeting name has been set to 'opnfv_release_daily' 13:31:52 #topic roll call 13:32:44 #info Justin 13:32:46 #info Alexandru Avadanii (Enea/ARMBand) 13:33:14 #info David McBride 13:33:18 #info kubi 13:33:46 documentation looks better today 13:34:31 #info Jose Lausuch 13:34:45 is it IRC only? 13:35:33 jose_lausuch: yes, the daily meeting is IRC only 13:36:08 dmcbride: I guess some projects are still in the Release-notes section 13:36:17 sofiawallin: are you available? 13:36:28 dmcbride: I guess some projects are still missing in the Release-notes section 13:36:35 dmcbride: yes 13:36:41 #info Tim Rozet 13:36:55 kubi: I noticed that ONOSFW is still missing 13:37:10 Storperf 13:37:16 but I think that is being resolved 13:37:20 It's not http://docs.opnfv.org/en/latest/release/userguide.introduction.html 13:37:26 ONOSFW is included 13:38:12 Storperf added as well http://docs.opnfv.org/en/latest/testing/testing-user.html 13:38:43 sofiawallin: I mean release note section http://docs.opnfv.org/en/stable-danube/release/release-notes.html 13:39:29 mbeierl: are you available? 13:39:42 kubi: Oh ok - I guess we need to add that is you have release notes available 13:40:43 sofiawallin: not from me:) Yardstick's release note have been added 13:41:11 sofiawallin: storperf ==> mbeierl 13:42:33 dmcbride: what about it? it's added here http://docs.opnfv.org/en/latest/testing/testing-user.html 13:43:49 sofiawallin: ok - I see it 13:44:17 sofiawallin: it seems from the email I read that ONOSFW will be resolved soon? 13:44:42 #topic documentation status 13:44:43 kubi: just checked storperf's repo. They don't have any release notes 13:45:22 sofiawallin: OK, I see, thanks 13:45:46 dmcbride: yes, except the scenario that they where talking about 13:46:01 never got an answer if the documentation is ready or not 13:47:06 sofiawallin: so, what is this? http://docs.opnfv.org/en/stable-danube/submodules/vswitchperf/docs/release/release-notes/index.html#vswitchperf-releasenotes 13:47:18 oh wait, wrong project 13:47:20 duh 13:47:45 too early, not enough coffee 13:48:00 mbeierl: ping 13:49:37 sofiawallin: any other missing items? 13:50:47 #info StorPerf project is missing release notes 13:52:51 dmcbride: I would say no. I mean whatever is in by now will make it I guess 13:54:07 #info sofiawallin does not think that anything else is missing, other than the StorPerf release notes 13:56:36 trozet: any issues? 13:56:56 narinder: any issues? 13:57:05 dmcbride: not that I know of. Going to start building the artifact for release shortly. What is the label for the artifact? 13:57:24 dmcbride, not I am aware of. 13:58:33 dmcbride: is the label 'danube-4.0' 13:58:56 dmcbride: or maybe we use 4.0 in apex for rpm ver 13:59:03 dmcbride: should it just be danube? 13:59:51 https://wiki.opnfv.org/display/SWREL/Git+Tagging+Instructions+for+Danube 14:00:37 trozet: for Danube, we're following the same nomenclature format at Colorado 14:01:33 pma: any issues? 14:01:46 chigang: any issues? 14:02:50 AlexAvadanii: any issues? Is Armband ready to release? 14:03:14 dmcbride: no major issues, yes, we are ready 14:03:55 #topic git tagging 14:04:01 #link https://wiki.opnfv.org/display/SWREL/Git+Tagging+Instructions+for+Danube 14:04:30 project PTLs, please make sure that you tag your projects 14:05:07 note that we are using a preliminary "RC" label for this release in order to avoid the dreaded "1.0.1" 14:05:21 #info Functest tagged 14:05:58 test projects need to build the tagged docker image danube.1.0 14:06:01 jose_lausuch: I have one question about functest's jose_lausuch: 14:06:11 I have one question about functest's reporting page 14:06:11 kubi: go ahead 14:06:31 jose_lausuch: http://testresults.opnfv.org/reporting/functest/release/danube/index-status-apex.html 14:06:51 yes? 14:07:43 jose_lausuch: for "os-odl_l2-fdio-ha" ,I check the build log for CI, I think the ci job failed at the begining. but there were some score for this scenario 14:07:59 dmcbride> no, no issue 14:08:09 jose_lausuch: https://build.opnfv.org/ci/view/functest/job/functest-apex-apex-daily-danube-daily-danube/84/console 14:09:19 kubi: that error is because space left on lf-pod1 14:09:28 but the dashboard collects data from 10 last runs 14:09:32 or days 14:09:34 so 14:09:41 maybe previous runs worked... 14:12:05 jose_lausuch: I check the history only two or three times run in 10 last runs, but I find the iteration times is 8 , I wonder if there are other source tor report? 14:12:27 ok - we're well over time 14:12:31 jose_lausuch: most job failed like this https://build.opnfv.org/ci/view/functest/job/functest-apex-apex-daily-danube-daily-danube/59/console 14:12:34 kubi: I will check 14:12:39 please ping me with questions/issues 14:12:47 dmcbride: Error: Can't start another meeting, one is in progress. Use #endmeeting first. 14:12:55 ok 14:16:04 dmcbride: no major issue, repo has been tagged for release. 14:20:28 #endmeeting