08:00:27 <ollivier> #startmeeting Functest weekly meeting 3 Apr. 2018
08:00:27 <collabot> Meeting started Tue Apr  3 08:00:27 2018 UTC.  The chair is ollivier. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:00:27 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
08:00:27 <collabot> The meeting name has been set to 'functest_weekly_meeting_3_apr__2018'
08:00:30 <ollivier> hi
08:00:39 <ollivier> #info Cédric Ollivier
08:00:59 <juhak> #info Juha Kosonen
08:01:26 <LindaWang> #info Linda Wang
08:01:54 <depo> #info Delia Popescu
08:03:02 <ollivier> #topic Action point follow-up
08:04:19 <ollivier> #info I will send you a full report about ONS
08:04:31 <ollivier> #link https://wiki.lfnetworking.org/display/LN/LFN+Developer+Forum+Schedule?preview=/328197/328329/ONS-OPNFV%20framework%20tests%20for%20LFN%20projects.pdf
08:04:41 <ollivier> #link http://testresults.opnfv.org/functest/gambiachallenges/
08:05:13 <ollivier> #info A new release model has been proposed (see https://gerrit.opnfv.org/gerrit/#/c/54533/)
08:06:01 <ollivier> It could raise effects in Functest but it's at early stage.
08:06:28 <LindaWang> what effects?
08:06:57 <ollivier> Functest could have to validate multiple OpenStack versions.
08:07:52 <ollivier> Classical model (Pike) + master model (XCI, APEX)
08:08:12 <LindaWang> Now functest is capable enough to test both pre-Queens and Pike?
08:09:23 <ollivier> I have already written an email about that. It could work to test euphrates, pike and master with E but it's not enforced.
08:09:42 <ollivier> We may have to refactor the testcase and consider tempest as verifier
08:10:40 <ollivier> For the time being, it was a draft handled by David and Tim
08:11:34 <ollivier> Sorry: it could work to test queens, pike and master with E but it's not enforced
08:11:44 <LindaWang> we have to refactor the test for F ?
08:12:28 <ollivier> at least the test suite. But it's not the key topic for today's meeting. I will prefer switching to the next release Fraser
08:12:42 <ollivier> #topic functest
08:12:52 <ollivier> #info stable/fraser was created:
08:13:04 <ollivier> #link https://gerrit.opnfv.org/gerrit/#/c/54443/
08:13:14 <ollivier> #link https://gerrit.opnfv.org/gerrit/#/c/54705/
08:13:21 <ollivier> #link https://gerrit.opnfv.org/gerrit/#/c/54711/
08:13:28 <ollivier> #link https://gerrit.opnfv.org/gerrit/#/c/54699/
08:13:42 <ollivier> #info opnfv/functest-restapi is being removed
08:13:51 <ollivier> #link https://gerrit.opnfv.org/gerrit/#/c/54709/
08:13:58 <ollivier> I personnaly don't understand the -2
08:14:05 <LindaWang> i do not agree to it.
08:14:11 <ollivier> https://wiki.opnfv.org/pages/viewpage.action?pageId=13211751
08:14:14 <ollivier> #link https://wiki.opnfv.org/pages/viewpage.action?pageId=13211751
08:15:00 <LindaWang> the endusers have to launch different containers according to tests. it is not a good restapi technically
08:15:39 <ollivier> We are promoting Docker Sling ?
08:15:43 <ollivier> Slicing
08:15:53 <LindaWang> yes, i understand.
08:16:35 <ollivier> I don't see the point about enduser. This code is useless from a Functest and Docker POV
08:16:47 <LindaWang> i mean we could create a shell script to launch the restapi server. maybe like functest-alpine.sh
08:17:23 <ollivier> It's just about overriding the default command. Why should we maintain that which was an exception for E.
08:18:21 <ollivier> I also double check with Dovetail PTL during ONS.
08:18:51 <LindaWang> Dovetail does not use our restapi
08:18:58 <ollivier> Who are using it?
08:19:39 <LindaWang> some product deployment.
08:19:42 <ollivier> As written in the wiki page, any functest container could run the REST API; https://wiki.opnfv.org/pages/viewpage.action?pageId=13211751
08:21:25 <ollivier> We shouldn't duplicate work for something which is useless in our Project. Functest is promoting Docker Slicing
08:22:13 <ollivier> If your commercial product is tested vs restapi I would say be free to built the container in your internal repo.
08:23:19 <LindaWang> i'd like to maintain it, at least until i propose a new way for the enduser of restapi.
08:23:20 <ollivier> Our documentation and releng jjobs are listing the other containers
08:24:10 <LindaWang> i will discuss it with my colleagues later, ok?
08:24:39 <ollivier> we have already waited too much
08:25:51 <LindaWang> sorry, but i thought it will be kept for F
08:26:19 <ollivier> We are also wating for unit tests regarding Rest API. This code is not run when gating .
08:26:22 <ollivier> #link https://jira.opnfv.org/browse/FUNCTEST-943
08:26:57 <LindaWang> and i saw your presentation about functst gambiachallenges, where restapi is included.
08:27:45 <ollivier> My presentation was done before discussing with Dovetail
08:28:23 <LindaWang> but Dovetail is not the user of restapi any more
08:28:56 <ollivier> Yes. That was I propose to remove it.
08:29:34 <ollivier> Technically speaking, it's useless to maintain it and none is calling it in OPNFV world
08:30:19 <LindaWang> Functest is also very important for other community or product, like ONAP.
08:31:07 <ollivier> The proposal for ONAP is to leverage on the classical containers and Xtesting
08:33:49 <ollivier> They are interested in our docker slicing approach.
08:34:23 <LindaWang> if restapi has to be removed, a new shell script about launching restapi and running test automatically should be accepted.
08:34:50 <ollivier> -2  look like abuse of power
08:35:18 <ollivier> #topic functest-kubernetes
08:35:32 <ollivier> #info Konrad is converting his presentation to markdown.
08:35:46 <ollivier> #info the env var KUBECONFIG was removed
08:35:59 <ollivier> #link https://gerrit.opnfv.org/gerrit/54093
08:36:14 <ollivier> #info stable/fraser was created
08:36:25 <ollivier> stor4vnf should be moved into a feature container, shouldn't it?
08:36:42 <ollivier> #info clover team is asking for late integration
08:37:32 <ollivier> I think stor4vnf and clover should be part of a feature container as for OpenStack
08:38:03 <LindaWang> i think so too.
08:38:26 <ollivier> I precise that clover is not gated.
08:39:35 <ollivier> The current proposal can't be merged. https://gerrit.opnfv.org/gerrit/#/c/54543/
08:40:43 <ollivier> and https://gerrit.opnfv.org/gerrit/#/c/54695/
08:41:34 <LindaWang> what does "clover is not gated" mean?
08:41:59 <ollivier> It's not run by releng jjobs if I understood correctly.
08:42:57 <ollivier> stor4vnf is at least run vs Compass
08:45:35 <ollivier> We should not prepare testcases.yaml for projects which are not running in OPNFV CI.
08:45:45 <liangqi> hi ollivier, sorry for late attend functest meeting.
08:45:46 <liangqi> https://build.opnfv.org/ci/view/clover/job/clover-daily-deploy-master/
08:45:58 <liangqi> here is the clover daily job link
08:46:26 <ollivier> liangqi: thank you
08:46:34 <ollivier> liangqi: no pb.
08:47:07 <liangqi> with the time limitted i call functest in clover's ci script
08:47:24 <liangqi> not triggerd by releng as other project
08:47:25 <ollivier> liangqi: we are proposing to move clover and stor4vnf in a new container
08:47:55 * liangqi https://git.opnfv.org/clover/tree/ci/deploy.sh#n68
08:48:12 <liangqi> here is the script you cloud take a look at
08:49:32 <liangqi> i don't know how functest handle  openstack  related feature project's testcase
08:50:45 <liangqi> And for F stable branch merege this https://gerrit.opnfv.org/gerrit/#/c/54695/ cloud be  very helpful :).
08:51:14 <ollivier> Not like this.
08:51:36 <ollivier> But it will merge in another container
08:52:06 <ollivier> https://git.opnfv.org/functest/tree/docker/features
08:52:11 <liangqi> move clover and stor4nfv in a new container is ok for me :)
08:52:47 <ollivier> It will optimize the size of your container...
08:53:13 <ollivier> else we switch to functest-kubernetes-restapi
08:53:51 <ollivier> liangqi: I will update your change if you agree
08:54:43 <liangqi> so functeat k8s related test case will split to k8s-official, stor4nfv, clover, other continers?
08:55:47 <ollivier> Yes. As you don't need K8s binaries, it will decrease the containers hosting OPNFV features.
08:56:50 <liangqi> ok, make sense.
08:57:01 <ollivier> But the key point is to manage correctly the default value to allow any end user to run easily the testcase even if it's not an OPNFV installer as K8s testcases are asking for the time being.
08:57:22 <ollivier> #topic AoB
08:58:29 <ollivier> #endmeeting