08:03:10 #startmeeting Functest weekly meeting 13 Feb. 2018 08:03:10 Meeting started Tue Feb 13 08:03:10 2018 UTC. The chair is ollivier. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:03:10 Useful Commands: #action #agreed #help #info #idea #link #topic. 08:03:10 The meeting name has been set to 'functest_weekly_meeting_13_feb__2018' 08:03:17 #info Cédric Ollivier 08:03:37 #info Juha Kosonen 08:03:39 #info Linda Wang 08:05:01 #topic action point follow-up 08:05:06 #info Jose Lausuch 08:05:23 2 jira tickets were closed 08:05:36 #link https://jira.opnfv.org/browse/FUNCTEST-929 08:05:43 #link https://jira.opnfv.org/browse/FUNCTEST-913 08:05:52 #info we should still find the best solution about "Fix the config of fixed_network_name in tempest" 08:06:14 i updated the patch without modifying the network 08:06:18 LindaWang: it seems that you publish a new update. Did you change the shared attribute? 08:06:19 #info pkaralis 08:06:21 ok :) 08:06:48 Then it could be reviewed. I think Morgan already voted +2 08:06:57 #link https://gerrit.opnfv.org/gerrit/51381 08:07:04 i tested tempest and refstack on compass without configuring fixed_network_name, it worked 08:07:20 #info mainly refstack_defcore(under investigation), rally_sanity(under investigation) cloudify_ims and vyos_vrouter have to fixed 08:07:38 #info juju_epc is now working fine 08:07:50 #info the second Kubernetes testcase is still under review 08:07:58 #link https://gerrit.opnfv.org/gerrit/51635 08:08:16 thank you for all changes. 08:08:35 still some issues about results parsing 08:08:45 refstack? 08:08:52 no, k8s_conformance 08:08:54 k8s? 08:09:15 yes 08:09:31 Ok. Then be free to vote Verify -1. Have you updated the logging part? 08:09:47 not yet 08:10:02 Konrad will update it later. 08:10:05 #info Delia Popescu 08:11:12 Noted. I haven't checked if Compass deployment is currently working. 08:11:45 compass has failed to deploy k8s these days 08:11:54 #info https://gerrit.opnfv.org/gerrit/#/c/50213/ 08:11:58 #undo 08:11:58 Removing item from minutes: 08:12:02 #link https://gerrit.opnfv.org/gerrit/#/c/50213/ 08:12:39 XCI support K8s deployment now. 08:12:57 good to know 08:13:33 #topic Xtesting 08:13:41 #link https://gerrit.opnfv.org/gerrit/#/q/project:functest+branch:master+topic:xtesting 08:13:54 #info all key changes have been published and samples work well locally 08:14:16 I'm leveraging on git sparse checkout to check it (simply cloning part of functest) 08:14:33 #info we are waiting for a full synchonization between functest and functest-xtesting 08:14:40 we can't push all changes due to rules vs authors 08:14:58 I sent an email to Trevor and Aric. 08:15:49 This rule could be removed as it double check the owner. It fails as I was pushing changes done by the whole functest community. 08:16:49 At least we are ready to publish xtesting. I think the log part could be improved in a second step (/home/opnfv/functest/results/functest.log). 08:18:04 #topic Code improvement 08:18:47 Lots of changes have been already published. 08:19:28 The key ideas are to manipulate (read/write) env vars via os.environ instead of CONST and to switch to gettattr/setattr for the remaining configs read operations. 08:19:47 #link https://jira.opnfv.org/browse/FUNCTEST-931 08:19:54 #link https://jira.opnfv.org/browse/FUNCTEST-932 08:20:04 #link https://jira.opnfv.org/browse/FUNCTEST-933 08:20:31 Please let me know if you disagree or if it's not clear. 08:21:25 do you mean we still keep config.py to parse config_functest.yaml? 08:22:00 Yes. We may switch to oslo.db but from the time being it's quite fine. 08:22:06 ok 08:22:57 Using const for env vars simply adds complexity (see CI_LOOP bug as jjobs didn't set it) 08:23:25 Now we can easily removes the former env vars and set the default values. 08:23:52 As already published we can safely remove IS_CI_RUN and CI_DEBUG 08:24:22 (CI_DEBUG is set in jjobs to print to stdout) 08:25:15 I think we could set os-nosdn-nofeature-noha when getting os.environ DEPLOY_SCENARIO. 08:25:30 or os-nosdn-nofeature-noha ? 08:25:37 os-nosdn-nofeature-ha ? 08:25:45 either is fine 08:25:53 I would prefer noha even if we do modify testcases.yaml 08:27:01 their main difference lies in running vnf or not locally. 08:27:04 (It seems fine to run vnf when noha scenarios). 08:27:45 in CI, we do not have to worry as DEPLOY_SCENARIO is provided 08:27:47 I think we should run them locally. The key point is to list (in wiki pages and docs) the mandatory env vars 08:28:18 from my side, my local deployment is only virtual 08:28:19 I think it's too much to ask a non OPNFV user to set DEPLOY_SCENARIO . 08:29:13 os-nosdn-nofeature-noha could be considered as a default value. 08:30:07 sounds better. 08:30:16 INSTALLER_IP and INSTALLER_TYPE are required in few testcases and we could skip them in the main configs 08:30:45 https://wiki.opnfv.org/pages/viewpage.action?pageId=13211751 08:31:06 In fact only EXTERNAL_NETWORK could be enough for most of the testcases. 08:31:30 We should precise the added env vars when running ODL, SFC and doctor 08:31:37 in the right sections. 08:32:11 (as for CI_LOOP=weekly in case of components) 08:33:04 I will update the next change https://gerrit.opnfv.org/gerrit/#/c/52047/ 08:34:03 About OS_AUTH_URL, every testcase should check a possible KeyError. 08:34:33 NODE_NAME & BUILD_TAG are required only when publishing data to DB or when collecting energy 08:35:23 another issue is when publishing the data to a local file, NODE_NAME & BUILD_TAG are also required 08:35:37 it does not make much sense 08:36:28 Yes. In case of a classical run by hand, they are useless. 08:38:01 #action Cédric to update the Alpine wiki pages (configguide) and to update the env vars processing if needed. 08:38:31 Are cli modules still used? 08:40:06 Should we maintain them? It adds an icmp test which could raise side effects (port forwarding over ssh) 08:40:07 yes 08:40:18 cli is used by Dovetail 08:40:40 Dovetail doesn't use master ? 08:40:52 they are using Euphrates now 08:41:36 and api modules reply on cli 08:41:38 I'm only considering modifying master. I think Euphrates should be updated only in case of bugs. 08:42:57 what does `icmp test` mean? 08:42:58 I think api should use cli in between. From the time being, we can maintain this modules. We have to take care of different processing when using run_tests or cli (icmp packets, BUILD_TAG regex) 08:43:16 ...api shoudn't use cli in between.. 08:43:51 response = os.system("ping -c 1 " + self.endpoint_ip + ">/dev/null") 08:44:27 This doesn't work in case of port forwarding (sshuttle) 08:45:24 I'm fine to add an icmp test but we should test the reachability in both calls. 08:45:31 not in only one. 08:46:07 we could update the 'functest openstack check' if necessary 08:46:15 We could maintain both run_test and cli but the behavior should be the same. 08:46:18 Yes. 08:46:46 I think there is one diff regarding BUILD_TAG regex as well. 08:47:02 but cli is easy for users, which would provide some guidance 08:47:56 why not but it duplicated work and only run_test is tested by CI/CD. 08:49:05 LindaWang: could you please update them. I would prefer that Dovetail use the main entry point 08:49:24 #topic Functest 08:49:38 #info tempest has been refactored/improved 08:49:44 #link https://gerrit.opnfv.org/gerrit/51889 08:49:51 #link https://gerrit.opnfv.org/gerrit/51963 08:50:00 #info rebaca team is updating juju_epc to leverage on snaps instead of openstack_utils 08:50:21 only vnfs are currently linked to openstack utils. 08:51:01 jose_lausuch: + maybe SFC and SDNVPN 08:51:52 I haven´t found any other project using our utils 08:52:09 for instance, barometer is based on our test case classes, but without using any other things 08:52:10 thank you. Previous action done. 08:53:22 Then be free to update vyos_router (planed end of February) or orchestra testcase (not clear) which are not updated yet. 08:53:36 #topic Releng 08:53:42 #info the falsy snaps testcase was fixed: 08:53:48 #link https://jira.opnfv.org/browse/SNAPS-263 08:53:59 #info gating is now working except for Apex jobs which are blocked by doctor-notification (timeout) 08:54:25 We should disable it till we haven't published our new jenkins jobs. 08:54:54 #info a proposal rewriting our Jenkins jobs has been published for reviews 08:55:02 #link https://gerrit.opnfv.org/gerrit/#/c/51853/ 08:55:38 Be free to review Delia's proposal. It would avoid one testcase blocking the full suites. 08:56:42 We could also removing former pods to avoid multiplying jobs for nothing. 08:57:01 jose_lausuch: morgan_orange: I will ask your help about History :) 08:57:32 ok 08:58:42 The git commit message is clear. Regarding the last proposal, we should care about verify jobs which could have been removed. 08:59:23 thx 08:59:28 #topic AoB 08:59:43 Do we miss a key point? 08:59:55 hi ollivier LindaWang all 09:00:02 I'd like to run the latest smoke-tempest suite. This is related to jira: FUNCTEST-926. Can you provide me any instructions / info / link / document for that? 09:00:40 Yes. We have to work on that too. 09:01:10 it seems the lists are provided in neutron repo, which uses tempest as a plugin? 09:01:11 The point is about integration trunk port tests (tempest) 09:01:40 We don't clone neutron repo. We simply install the python package. 09:01:42 LindaWang, yes 09:02:44 we have to figure out how to install neutron python and install tempest, then generate a test list 09:03:05 ollivier, my initial problem is how I could run the latest smoke-tempest suite without the neutron plugin. As it is. 09:03:10 I think we can close the meeting. Stay tuned for trunk ports. 09:03:20 #endmeeting