08:02:29 #startmeeting Functest weekly meeting 6 Mar. 2018 08:02:29 Meeting started Tue Mar 6 08:02:29 2018 UTC. The chair is ollivier. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:02:29 Useful Commands: #action #agreed #help #info #idea #link #topic. 08:02:29 The meeting name has been set to 'functest_weekly_meeting_6_mar__2018' 08:02:49 #info Delia Popescu 08:03:27 #info Linda Wang 08:03:47 #info Juha Kosonen 08:04:23 #info SerenaFeng 08:04:30 #info Cédric Ollivier 08:04:42 #topic Action point follow-up 08:05:11 #info David agreed that the former Jenkins jobs can be removed 08:05:37 #info Viktor Tikkanen 08:05:42 The former gerrit change https://gerrit.opnfv.org/gerrit/#/c/51853/ can be merged again 08:05:58 great 08:06:24 Aric said that we should first delete the jobs, then remerge 08:06:31 depo: could you please take the actions on that again? 08:06:36 it wil fail if not, anyway 08:06:40 yes 08:06:46 Yes. Aric could do that this week (it was busy last Friday 08:06:56 ..he was busy.. 08:07:03 I will contct him 08:07:12 thank you. 08:07:40 #info all opnfv docker repos were created last week (functest-kubernetes, functest-patrole ...) 08:08:11 opnfv/xtesting would have been a Docker automated build instead but it will be fixed later. 08:09:05 will functest-core container be removed soon? 08:09:06 Then other container could be built on top of functest/xtesting? 08:09:17 We are still waiting for https://gerrit.opnfv.org/gerrit/#/c/53001/ . 08:09:43 we should keep functest-core for all OpenStack testcases built on top of xtesting 08:10:07 functest-core also contains utils and core/vnf for third-parties 08:10:19 you mean functest-core could be built on top of functest/xtesting? 08:10:56 on top of Alpine (xtesting installed as a python package) or on top of xtesting. Both are fine 08:11:09 From the time being, opnfv/xtesting is not built for arm 08:11:39 Then we should keep the current model (xtesting is installed by dependencies) 08:12:12 https://git.opnfv.org/functest/tree/requirements.txt#n29 08:13:01 I think the current model is better because it avoids race conditions between docker image builds. 08:13:25 But opnfV/xtesting should be built for arm too. 08:13:52 #topiv Xtesting 08:13:59 #topic Xtesting 08:14:24 I just set the right topic :) 08:15:03 #info the python package xtesting has been published 08:15:23 #link http://xtesting.readthedocs.io/en/latest/apidoc/xtesting.html 08:15:33 #info Functest, Functest Kubernetes and OPNFV features integrated in Functest were updated 08:16:05 #info new OPNAP testing docker images have been built on top of xtesting 08:16:15 #link new OPNAP testing docker images have been built on top of xtesting 08:16:23 #undo 08:16:23 Removing item from minutes: 08:16:33 #link https://hub.docker.com/r/colvert22/functest-onap/~/dockerfile/ 08:17:08 This docker inherits from the official Docker image. 08:18:10 I will send an email to opnfv-tech-discuss about xtesting. It will detail how to install it via pip or how to run the container. 08:18:36 By default, samples are run. 08:22:02 Please let me know if you want much details. I think all adaptations have been done. 08:22:32 since onap is built based on functest/xtesting 08:23:04 i think it is better if other functest containers are built on functest/xtesting 08:23:33 even though installing xtesting packages also works 08:24:13 We could switch only if we prepare a new multijob for xtesting. 08:25:19 but I'm quite afraid of race conditions and managing upper-constraints allows a kind of delay between xtesting and functest. 08:25:29 now functest/xtesting would be built once new patch is merged. NO? 08:25:37 see snaps and functest 08:26:10 yes, that is true. 08:26:16 Yes. But to go as fast as possible, I list xtesting in the classical Docker job instead of creating a new multijob. 08:26:54 I think the current model is fine for this release. xtesting should support ARM too even if this image is unused by Functest. 08:27:48 functest-kubernetes directly inherits from Alpine. 08:27:52 https://git.opnfv.org/functest-kubernetes/tree/docker/Dockerfile 08:30:04 I think it's clean and we can select the right xtesting version by upper-constraints. 08:31:03 #topic functest 08:31:22 i will do that, add a new upper-contraints file 08:31:58 https://git.opnfv.org/functest/tree/upper-constraints.txt 08:32:35 https://git.opnfv.org/functest-kubernetes/tree/docker/Dockerfile#n18 08:32:56 At the end it should be centralized in the requirement project. 08:33:23 oh, this upper-contraints is from functest 08:34:10 Yes. as the previous release everything is hosted in functest from the time beign 08:34:29 #info A new wiki page gathers all results 08:34:39 #link https://wiki.opnfv.org/display/functest/Fraser+Release+Gating+via+Functest 08:36:16 It has already been shared with David and Gabriel. The pupose is to convince that Functest is working and avoids what happens in the previous release (all installers decided what scenarios were working) 08:36:38 It should be broadcast to Dovetail for their next releases. 08:37:31 yes, i will tell Dovetail team. 08:37:49 #info we have already fixed 3 bugs 08:38:01 #link https://jira.opnfv.org/browse/FUNCTEST-945 08:38:09 #link https://jira.opnfv.org/browse/FUNCTEST-946 08:38:19 #link https://jira.opnfv.org/browse/FUNCTEST-947 08:38:40 But we have to wait the next ci runs to update the pretty tables. Thank you for all fixes. 08:39:10 I consider that all testcases are good enough for gating 08:39:42 Pelase let me know if you are considering any exception 08:40:47 JOID is defining non default Keystone v3 domains which may require additional updates in vnf but it should be ok 08:41:01 there is a possible mismatch between cloud configurations and testcase preferences in vnfs 08:41:51 should we also list the successful testcases? 08:42:05 #link https://gerrit.opnfv.org/gerrit/#/c/53073/ 08:42:13 Yes it's possible. 08:42:39 If everybody agrees, I can easily update the tables. 08:43:14 it was caused by the two patches: 08:43:27 #link https://gerrit.opnfv.org/gerrit/#/c/51845/ 08:43:30 #link https://gerrit.opnfv.org/gerrit/#/c/51933/ 08:44:12 listing all the testcases would be better in the release gating, and i could help maintain this page. 08:44:30 Ok I will update all the tables after the meeting 08:44:44 i do not understand why the DNS configuration was removed in Snaps. 08:45:07 Regarding 8.8.8.8, we shouldn't consider it as an issue. The issue is more or less to force 8.8.8.8 as DNS which is a Cloud preference 08:45:58 We can bypass installer limitations but Functest could be reused in DC where a local DNS is used. 08:46:32 Setting 8.8.8.8 would break any deployment when public identity endpoint are a local name instead of an IP 08:48:15 Both patches about snaps were fine. I will double check the default OpenStack behavior if dns is unset. 08:49:19 We can bypass that for the release if it requires too much Installer updates 08:50:04 #info the testcase about Patrole was merged: 08:50:15 #info the multijob update is still under review 08:50:24 #link https://gerrit.opnfv.org/gerrit/#/c/53001/ 08:50:38 #info the testing part update is proposed too but we must first check all the results 08:50:53 #link https://gerrit.opnfv.org/gerrit/#/c/53045/ 08:51:27 have you run it locally? 08:51:32 Yes. 08:51:45 I did not notice we should also download policy.json 08:52:09 The results are bad if no policy.json are provided (it seems that Patrole doesn't skip correctly lots of tests) 08:52:24 We could have run it without policy.json. 08:53:20 REgardign the current results we must set the lowest criteria if we merge https://gerrit.opnfv.org/gerrit/#/c/53045/ 08:53:44 but in fact it only makes sense with policy.json , right? 08:53:45 It seems not so bad if we add all policy.json but it requires an update of this patch. 08:53:48 yes 08:54:21 we have to use opnfv module from releng to fetch the policy.json from controllers? 08:54:53 that's a proposal. Or we download the official ones from repositories when building the containers. 08:55:10 but I think they are being removed from tree (by design) 08:55:45 i am wondering the policy.json is not different from different installers. 08:56:22 That's the question. But we could easily override the policy.json by docker args. 08:56:24 at least they are quite strict on some product deployments. 08:56:52 From products deployment or legals, they have to be overriden but it's already possible 08:57:16 We are working on that with Remi. At least Patrole is already well integrated 08:57:46 sorry we are late again. Few works about functest-kubernetes 08:57:54 #topic functest-kubernetes 08:58:04 #info two testcases are now available in our containers 08:58:15 #info the first unit tests was merged 08:58:23 #link https://gerrit.opnfv.org/gerrit/#/c/52337/ 08:58:33 #link https://build.opnfv.org/ci/view/functest/job/functest-compass-virtual-daily-master/3174/console 08:58:42 logs must be published and testcases declared in TEST DB 08:58:58 A new wiki page could be written to explain how to run the new testcases 08:59:18 That's great 08:59:27 #info we are waiting for the first CI runs on JOID 08:59:28 i will help create a new wiki 08:59:45 but i failed to post the testcase to TEST DB 09:00:13 i failed to declare the testcases to TEST DB 09:00:18 Thank you. I think it can follow the same model https://wiki.opnfv.org/pages/viewpage.action?pageId=13211751 09:00:37 I will try to create them. I need to declare patrole too. 09:00:55 thanks 09:01:08 #topic AoB 09:01:40 I think we can already fix the version of our external dependencies (rally, odl tests). Do you agree? 09:01:59 Several of them should be fixed by commit id. 09:02:13 which version of rally 09:02:25 (I forget refstack_client) 09:02:55 Do we switch to 0.10.1 ? 09:03:20 stable 0.10 seems fine 09:03:46 A stable branch is good enough 09:04:43 For E we selected a tag (ARG RALLY_TAG=0.9.1) 09:04:53 juhak: what do you think? 09:05:30 i think 0.10 is fine now 09:05:56 ok. Thank you 09:06:17 For the others external dependencies? 09:06:52 I would prefer fixing them right now 09:07:01 (refstack, odl, ...) 09:07:25 We will see later. 09:08:28 Thank you for the meeting. Great week again. 09:08:31 #endmeeting