08:00:02 <jose_lausuch> #startmeeting Functest weekly meeting June 27th 2017
08:00:02 <collabot`> Meeting started Tue Jun 27 08:00:02 2017 UTC.  The chair is jose_lausuch. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:00:02 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
08:00:02 <collabot`> The meeting name has been set to 'functest_weekly_meeting_june_27th_2017'
08:00:05 <jlinkes> morgan_orange: is this the fix for the dashboards issue we talked about yesterday? https://gerrit.opnfv.org/gerrit/#/c/36527/
08:00:06 <jose_lausuch> #topic role call
08:00:26 <juhak> #info Juha Kosonen
08:00:27 <jose_lausuch> jlinkes: that fixes the iterations problem
08:00:30 <jose_lausuch> #info Jose Lausuch
08:00:35 <CristinaPauna> #info Cristina Pauna (Enea)
08:00:44 <morgan_orange> jlinkes: yes
08:01:06 <jlinkes> morgan_orange: could you re-generate http://testresults.opnfv.org/reporting2/display/danube/functest/status-apex.html then, please?
08:01:08 <LindaWang> #info Linda Wang
08:01:18 <jose_lausuch> #chair morgan_orange
08:01:18 <collabot`> Current chairs: jose_lausuch morgan_orange
08:01:18 <morgan_orange> jlinkes: basicaly pagination has been introduced in the API then when I was colelcting the results, I always got the first page by default that is why the number of iterations and scenarios was no more correct
08:01:20 <SerenaFeng> #info SerenaFeng
08:01:42 <morgan_orange> jlinkes: I tested the fix on http://testresults.opnfv.org/reporting2/display/danube/functest/status-apex.html, seems OK
08:01:45 <jose_lausuch> #info agenda for today: https://wiki.opnfv.org/display/functest/Functest+5.+Meeting#Functest5.Meeting-27/06(8UTC)
08:01:52 <morgan_orange> #info Morgan Richomme
08:02:17 <jose_lausuch> #topic Action Point follow-up
08:02:24 <jose_lausuch> #info AP SerenaFeng jose_lausuch align in TestAPI authentication, next steps.
08:02:33 <jose_lausuch> #info We brought the topic to the Test working group and Trevor will help us identifying the requirements.
08:02:54 <SerenaFeng> Trevor said he will create a wiki page for it,
08:02:57 <jlinkes> morgan_orange: sorry, I meant version1: http://testresults.opnfv.org/reporting/functest/release/danube/index-status-apex.html
08:03:03 <SerenaFeng> do you know what's the progress?
08:03:13 <jose_lausuch> #info Trevor will create a wiki with proposal/questions
08:03:13 <morgan_orange> jlinkes:  in progress...
08:03:21 <jose_lausuch> I don't know, I'll try to talk to him today
08:03:24 <jlinkes> morgan_orange: thanks
08:03:28 <SerenaFeng> ok
08:03:30 <MatthewLi> #info Jun Li
08:04:05 <jose_lausuch> #topic Framework status
08:04:17 <jose_lausuch> let me post some information
08:04:24 <jose_lausuch> and we can then comment on the different topics/issues
08:04:29 <jose_lausuch> #info major changes in the framework have been merged and some bugs have been fixed
08:04:38 <jose_lausuch> #info Floating ips issue: newer nova client doesn't support floating ip creation. It's now managed by neutron client --> Fixed in Functest utils and SNAPS
08:04:50 <jose_lausuch> #info Glance images issue: newer nova client doesn't support image creation. It is now managed by glance client --> Fixed in Functest utils and SNAPS
08:04:52 <MatthewLi> #link https://wiki.opnfv.org/display/dovetail/Dovetail+Test+Result+Database created by trevor
08:05:08 <jose_lausuch> MatthewLi: ah, ok! Thanks!
08:05:13 <MatthewLi> :)
08:05:33 <SerenaFeng> Great thanks MatthewLi
08:05:59 <jose_lausuch> #info Public endpoint stauts (no admin access). Now supported in Functest but we still need to enable it in SNAPS: https://gerrit.opnfv.org/gerrit/#/c/36441/
08:06:02 <MatthewLi> my favor
08:06:10 <jose_lausuch> LindaWang: any comments about it?
08:06:26 <LindaWang> jose_lausuch: I think i have fixed it
08:06:39 <LindaWang> by reseting interface to public by default
08:06:47 <jose_lausuch> aha ok
08:07:07 <jose_lausuch> we still need confirmation from Steven
08:07:12 <jose_lausuch> does anyone has an apex deployment?
08:07:15 <LindaWang> Sure
08:07:33 <LindaWang> jose_lausuch: I have already got one
08:07:42 <jose_lausuch> I mean, to help testing it
08:07:42 <LindaWang> both v2 and v3 are supported.
08:07:46 <LindaWang> ok
08:07:52 <jose_lausuch> ok, that sounds good
08:08:06 <jose_lausuch> I think I can borrow a deployment from a colleague for some hours
08:08:09 <jose_lausuch> I can also test that patch
08:08:16 <LindaWang> Thank you
08:08:27 <jose_lausuch> #info HTTPS: supported in Functest and now enabled in SNAPS: https://gerrit.opnfv.org/gerrit/#/c/36221/
08:08:34 <jose_lausuch> thanks LindaWang for this work
08:09:29 <jose_lausuch> any comments ?
08:10:32 <morgan_orange> thanks LindaWang
08:11:01 <LindaWang> Steven helps a lot
08:11:54 <jose_lausuch> #info added unit tests for healtcheck tier. Please help review: https://gerrit.opnfv.org/gerrit/#/c/35661    there are 2 +2's . I plan to merge today
08:12:35 <jose_lausuch> ok, let's talk about the Refstack status
08:12:38 <jose_lausuch> #topic Tempest & Refstack in Functest
08:12:45 <jose_lausuch> let me give some background information for everyone
08:12:51 <jose_lausuch> #link https://gerrit.opnfv.org/gerrit/#/c/36463/
08:12:56 <jose_lausuch> #info We need to have the tempest repository in the container for Rally to install it and create the Rally verify environment.
08:13:23 <jose_lausuch> #info This has been discussed with Rally team, there is no workaround. If we don't clone it, Rally will pull the repository from the internet anyway when configuring rally verify (which is against going Functest offline).
08:13:30 <jose_lausuch> #info Now we clone Tempest in the Dockerfile
08:13:53 <jose_lausuch> #info When we install Refstack, it also clones the repostory and it creates the .venv directory (that is the main difference between this directory and the tempest repo we clone in the Dockerfile)
08:14:00 <jose_lausuch> #info The path to Tempest used by Refstack is in /home/opnfv/.tempest
08:14:14 <jose_lausuch> #info The path to where we clone Tempest is /home/opnfv/repos/tempest
08:14:41 <jose_lausuch> #info Refstack script hardcodes that path. It is not configuratble.  See  https://github.com/openstack/refstack-client/blob/master/setup_env#L57
08:14:47 <jose_lausuch> now, comments :)
08:15:59 <SerenaFeng> is it possible to convince refstack to make it configurable ?
08:16:44 <LindaWang> We should talk with refstack team to check that.
08:16:54 <SerenaFeng> or else it seems like we have no choice but to leverage link
08:16:56 <jose_lausuch> I can do that
08:17:00 <jose_lausuch> I know the PTL
08:17:04 <jose_lausuch> I think it should be ok
08:17:11 <SerenaFeng> I think so
08:17:14 <jose_lausuch> but it's not there for now, so we need to come up with something in the meantime
08:17:24 <LindaWang> But the symlink is also a good option.
08:17:38 <jose_lausuch> what do you mean?
08:17:45 <jose_lausuch> so, we remove the clone of tempest
08:18:00 <jose_lausuch> and create a symlink from /home/opnfv/repos/tempest to /home/opnfv/.tempest ?
08:18:08 <SerenaFeng> currently, symlink is ok, as we did in that patch
08:18:33 <jose_lausuch> the only difference between those 2 directories is the .venv   that refstack installs
08:19:13 <LindaWang> Do you mean you want to create verifier by /home/opnfv/.tempest
08:19:14 <LindaWang> ?
08:19:34 <jose_lausuch> would it work?
08:19:58 <LindaWang> rally verify create-verifier --source /home/opnfv/repos/tempest --name opnfv-tempest --type tempest --system-wide
08:20:08 <LindaWang> rally verify create-verifier --source /home/opnfv/.tempest--name opnfv-tempest --type tempest --system-wide???
08:20:10 <LindaWang> I am not sure
08:20:18 <LindaWang> Maybe we should check.
08:20:30 <jose_lausuch> ln -s  /home/opnfv/.tempest   /home/opnfv/repos/tempest
08:20:52 <jose_lausuch> so
08:20:53 <jose_lausuch> 2 options
08:21:07 <jose_lausuch> 1) we change the rally verify command pointing to /home/opnfv/.tempest
08:21:08 <jose_lausuch> or
08:21:22 <SerenaFeng> I think tempest is also installable, am I right?
08:21:25 <jose_lausuch> 2) we remove tempest repo in the image and create symlink   ln -s  /home/opnfv/.tempest   /home/opnfv/repos/tempest
08:22:01 <jose_lausuch> in both cases, we remove the tempest repo in the image
08:22:07 <jose_lausuch> I think so
08:22:07 <LindaWang> I have checked, rally verify create-verifier --source /home/opnfv/.tempest--name opnfv-tempest --type tempest --system-wide
08:22:11 <LindaWang> It is ok
08:22:22 <jose_lausuch> does it work?
08:22:25 <LindaWang> yES
08:22:36 <jose_lausuch> what sall we do then?
08:22:40 <jose_lausuch> option 1?
08:22:47 <jose_lausuch> and remove /home/opnfv/repos/tempest  ?
08:22:48 <SerenaFeng> I prefer the first 1
08:23:01 <jose_lausuch> ok
08:23:04 <LindaWang> +1, also waiting for your tests.
08:23:14 <SerenaFeng> yes
08:23:20 <jose_lausuch> I can create a patch with that change
08:23:27 <SerenaFeng> when is /home/opnfv.tempest create?
08:23:31 <SerenaFeng> by refstack?
08:23:40 <LindaWang> After refstack is installed.
08:24:08 <jose_lausuch> SerenaFeng: https://gerrit.opnfv.org/gerrit/gitweb?p=functest.git;a=blob;f=docker/Dockerfile;h=4c03a697d84be6e7a491e47fd6320970032ade2c;hb=refs/heads/master#l139
08:24:13 <morgan_orange> so it means that the installation order will be important and we create a dependency Refstack/Rally, right?
08:24:13 <jose_lausuch> it is created here
08:24:17 <jose_lausuch> by the setup_env script
08:24:30 <jose_lausuch> morgan_orange: not really
08:24:44 <jose_lausuch> Rally needs the repo when doing functest env prepare, not in the docker build
08:25:09 <LindaWang> rally verify create-verifier will be executed in "functest env prepare"
08:25:16 <morgan_orange> ok
08:25:56 <jose_lausuch> but yes, the dependency is that if some day we remove refstack from Functest (which I dont think it will happen), rally will fail
08:26:02 <jose_lausuch> but we can always add the repo back
08:26:11 <jose_lausuch> but that is unlikely to happen
08:26:23 <jose_lausuch> so, I'm fine with relying on option 1
08:26:35 <LindaWang> Aha
08:26:47 <LindaWang> Sounds more reasonal
08:27:16 <LindaWang> typo: reasonable
08:27:59 <SerenaFeng> I would recommend to install tempest if possible, then make symlink for both rally and refstack if needed
08:28:25 <jose_lausuch> but the way Rally manages it is different
08:28:26 <LindaWang> Then you will make it more complicated.
08:28:27 <SerenaFeng> in that case the tempest version we leverage will not rely on either rally or refstack
08:28:34 <jose_lausuch> Rally only needs the tempes repo, not the installation
08:28:47 <jose_lausuch> we can control the version anyway
08:29:08 <SerenaFeng> the point is decouple rally/refstack
08:29:09 <LindaWang> When it comes to refstack, the tempest version is supposed managed by restack.
08:29:16 <SerenaFeng> let them rely on tempest directly
08:29:28 <SerenaFeng> I don't think it will make it more complicated
08:29:53 <LindaWang> That is why there is a ARG REFSTACK_TAG in Dockerfile.
08:30:11 <LindaWang> Actually REFSTACK_TAG refers to tempest version
08:30:51 <LindaWang> But we hope it should be controlled by refstack
08:30:58 <SerenaFeng> why?
08:31:13 <SerenaFeng> why it should be controlled by refstack?
08:31:40 <jose_lausuch> refstack and rally should execute the same tempest version in my opinion
08:31:46 <SerenaFeng> refstack is only a tool to drive tempest, it should be able to drive any tempest version
08:31:57 <SerenaFeng> jose_lausuch totally agree
08:32:05 <SerenaFeng> and it can not be determined by refstack
08:32:55 <LindaWang> jose_lausuch:  we can not make sure higher version of tempest will be run successfully by refstack sometimes
08:33:13 <jose_lausuch> I am looking at the setup_env
08:33:13 <jose_lausuch> https://github.com/openstack/refstack-client/blob/master/setup_env#L104
08:33:18 <jose_lausuch> it seems it clones latest
08:33:28 <jose_lausuch> git clone https://github.com/openstack/tempest.git ${TEMPEST_DIR}
08:33:28 <LindaWang> We want to make it more controllable.
08:33:36 <SerenaFeng> it depends on us to choose the proper version, but it doesn't mean to be controlled by refstack
08:34:04 <jose_lausuch> then, option 1) is not valid
08:34:09 <LindaWang> jose_lausuch:  tempest repo here should be 15.0.0
08:34:21 <LindaWang> But you git cloned the latest version
08:35:05 <LindaWang> I am confused: git clone --depth 1 -b $TEMPEST_TAG https://github.com/openstack/tempest.git ${REPOS_DIR}/tempest
08:35:18 <jose_lausuch> in the setup_env script from refstack, it is possible to specify the tempest installation
08:35:28 <jose_lausuch> maybe SerenaFeng is right if we install tempest ourselves
08:35:37 <jose_lausuch> python virtualenv.py ${TEMPEST_DIR}/.venv --python="${PYPATH}"
08:35:56 <SerenaFeng> I just check the setup_env
08:36:10 <SerenaFeng> it seems like what we discussed here is not supported
08:36:24 <jose_lausuch> they hardcode the directory to .tempest
08:36:29 <SerenaFeng> because in refstack it checks if tempest_dir exist
08:36:34 <SerenaFeng> it will remove it first
08:36:48 <SerenaFeng> then git clone a new latest one
08:36:52 <jose_lausuch> right
08:37:06 <MatthewLi> after seen this doscussion, actually not get the main point. refstack use tempest, do many env prepare actions by https://github.com/openstack/refstack-client/blob/master/setup_env, and it may changes as master code grows. let's inherit refstack steps directly without trying to add or amend the steps by using own defined steps
08:37:22 <LindaWang> NO
08:37:29 <LindaWang> Not the latest
08:37:30 <LindaWang> git checkout $CHECKOUT_POINT || if [ $? -ne 0 ]; then exit 1; fi
08:37:58 <jose_lausuch> ah ok, great
08:38:06 <jose_lausuch> we can give the commit ID to Refstack script
08:38:10 <LindaWang> CHECKOUT_POINT="-q ${OPTARG}, Here OPTARG can be changed by -t parameter
08:38:11 <jose_lausuch> that makes things easier
08:38:27 <jose_lausuch> MatthewLi: I think we should use a fixed tempest version, not latest
08:38:43 <LindaWang> jose_lausuch:  Why?
08:38:46 <MatthewLi> jose_lausuch: yep we use 15.0.0 not latest
08:38:50 <LindaWang> It is 15.0.0
08:38:52 <LindaWang> YES
08:39:06 <jose_lausuch> so
08:39:11 <LindaWang> setup_env -t ${REFSTACK_TAG}
08:39:19 <jose_lausuch> 1) we change the rally verify command pointing to /home/opnfv/.tempest
08:39:20 <LindaWang> REFSTACK_TAG=15.0.0
08:39:40 <MatthewLi> that's also defcore 2016.08 requirements 15.0.0
08:39:44 <jose_lausuch> #info agreed to change the rally verify command pointing to /home/opnfv/.tempest  and removing the clone of tempest repo
08:39:48 <jose_lausuch> is it right?
08:40:04 <LindaWang> YES
08:40:23 <jose_lausuch> #info this way we use 15.0.0 version in Rally-tempest and Refstack
08:41:43 <jose_lausuch> ok?
08:41:48 <jose_lausuch> everyone agrees?
08:41:51 <SerenaFeng> currently, ok
08:41:52 <morgan_orange> ok
08:41:53 <LindaWang> AGREE
08:41:56 <SerenaFeng> we have no choice
08:41:57 <juhak> +1
08:41:59 <MatthewLi> as for the rally, if decide to do so, not object now, however, don't know if have problems. at least separate tempest repos for refstack and rally will not have problems :)
08:42:48 <jose_lausuch> MatthewLi: why separating repos? this way we don't duplicate files and we control the version only 1 time
08:43:26 <SerenaFeng> better to leverage only 1 tempest
08:43:31 <LindaWang> Now there is only one tempest repo.
08:43:52 <jose_lausuch> ok
08:44:02 <jose_lausuch> who will work on that change?
08:44:05 <LindaWang> We'd better be careful about tempest verison in future. It affects a lot.
08:44:05 <jose_lausuch> I volunteer
08:45:25 <jose_lausuch> #topic Functest offline
08:45:37 <jose_lausuch> #info help review this https://gerrit.opnfv.org/gerrit/#/c/35593/
08:45:44 <jose_lausuch> what is the status in offline LindaWang ?
08:45:47 <jose_lausuch> what is missing?
08:46:10 <LindaWang> Only healthcheck tier
08:46:28 <jose_lausuch> so , that patch
08:46:32 <LindaWang> There are also 2 large imags(ubuntu and centos) needed
08:46:50 <LindaWang> https://gerrit.opnfv.org/gerrit/#/c/35593/
08:47:06 <LindaWang> They are needed by 3 tests from snaps_smoke
08:47:31 <LindaWang> We need to discuss with Steven.
08:47:41 <jose_lausuch> ok
08:47:53 <jose_lausuch> I wouldn't like to abandon that patch
08:47:57 <jose_lausuch> he is tired of rebasing
08:48:01 <jose_lausuch> we are not providing enough feedback
08:48:03 <LindaWang> Whether remove the 3 tests or download these images by download_images.sh
08:48:09 <OPNFV-Gerrit-Bot> Ryota Mibu proposed functest: enable doctor-notification test case  https://gerrit.opnfv.org/gerrit/36561
08:48:24 <jose_lausuch> I would put those images in dowload images.sh
08:48:30 <LindaWang> I made some comments there.
08:48:31 <jose_lausuch> no need to remove the tests
08:48:54 <LindaWang> ok
08:49:48 <morgan_orange> jlinkes: it is done http://testresults.opnfv.org/reporting/functest/release/danube/index-status-apex.html
08:50:01 <jose_lausuch> LindaWang: you mean , which tests need to be removed? from snaps_smoke ?
08:50:28 <jlinkes> morgan_orange: thanks
08:51:03 <LindaWang> test_dual_ports_dhcp (snaps.openstack.tests.create_instance_tests.CreateInstancePubPrivNetTests)
08:51:03 <LindaWang> test_apply_simple_playbook (snaps.provisioning.tests.ansible_utils_tests.AnsibleProvisioningTests)
08:51:03 <LindaWang> test_apply_template_playbook (snaps.provisioning.tests.ansible_utils_tests.AnsibleProvisioningTests)
08:51:10 <jose_lausuch> please all read latest comments here https://gerrit.opnfv.org/gerrit/#/c/35593/  and provide feedback
08:51:13 <LindaWang> Yes, from snaps_smoke
08:51:18 <SerenaFeng> I think we discussed before that large images will be processed with volume, no ?
08:51:21 <jose_lausuch> question is: shall we keep them or remove them?
08:51:30 <jose_lausuch> yes
08:51:33 <jose_lausuch> that is the idea
08:52:30 <jose_lausuch> ok, let's discuss in the gerrit commit
08:52:32 <SerenaFeng> then what's the problem now?
08:52:55 <jose_lausuch> #info move large images to download_images.sh
08:52:57 <jose_lausuch> #AoB
08:53:00 <jose_lausuch> no problem
08:53:13 <jose_lausuch> #info morgan_orange fixed iterations in the Functest Dashboard.
08:53:14 <jose_lausuch> thank you!
08:53:25 <morgan_orange> #info it seems that we cannot generate anymore Danube docker file...
08:53:33 <HelenYao> will we discuss the rest api?
08:53:59 <HelenYao> is the info on wiki agreed by all of us?
08:54:09 <morgan_orange> yes for me
08:54:15 <jose_lausuch> HelenYao: we can, I didn't see further comments on it, so I'm fine with it
08:54:27 <jose_lausuch> if someone doesn't agree, shout
08:54:31 <jose_lausuch> :)
08:54:52 <HelenYao> another thing is, i am leaving this week. I would like to hand the work over to Linda
08:55:11 <HelenYao> I will shout at him loudly
08:55:34 <jose_lausuch> HelenYao: but will you still do things in Functest?
08:56:00 <HelenYao> yes. when is the rest api supposed to be ready?
08:56:17 <jose_lausuch> there is no date, everything is asap :D
08:56:37 <HelenYao> I　will still in Functest
08:56:42 <MatthewLi> how is the progress of testapi?
08:57:11 <jose_lausuch> MatthewLi: this is about a new feature, the rest api for functest, not the Test api
08:57:15 <HelenYao> Linda will be more focused than me. I would be glad to work with her on rest api
08:57:24 <jose_lausuch> ok
08:57:27 <MatthewLi> #by now, can satisfy the requirement in https://wiki.opnfv.org/display/dovetail/Dovetail+Test+Result+Database
08:57:33 <jose_lausuch> how long will you be off?
08:57:44 <HelenYao> next week
08:57:57 <HelenYao> the whole week
08:58:00 <jose_lausuch> ok
08:58:07 <MatthewLi> jose_lausuch, SerenaFeng: yep I mean the testapi not restapi
08:58:26 <jose_lausuch> what requirement?
08:58:29 <SerenaFeng> cannot satisfy now
08:58:34 <SerenaFeng> I just know it :)
08:58:34 <jose_lausuch> authentication? n
08:58:35 <jose_lausuch> no
08:58:59 <MatthewLi> SerenaFeng: so when will finish that? need which resource?
08:59:14 <SerenaFeng> I will finish it asap
08:59:22 <SerenaFeng> and I still need requirements from landing page
08:59:23 <jose_lausuch> it's not an easy task
08:59:39 <jose_lausuch> it seems there is no need for landing page in this wiki
08:59:49 <MatthewLi> maybe we need that in urgent, for landing page do u need which resource?
09:00:03 <SerenaFeng> I don't know
09:00:28 <SerenaFeng> I will discuss with Morgan and Jack
09:00:35 <jose_lausuch> let's focus on authentication for testapi, and leave landing page for later
09:00:39 <MatthewLi> little confused.... OK, thanks....
09:00:50 <SerenaFeng> morgan_organge any requirements from landing page
09:00:55 <jose_lausuch> I really CVP should provide people to work on it, not us doing all the work
09:01:10 <MatthewLi> jose_lausuch: yep let's let's focus on authentication for testapi, and leave landing page for later
09:01:13 <jose_lausuch> a landing page for CVP should be managed by CVP, not by Functest
09:01:21 <morgan_orange> SerenaFeng: landing page Dovetail or landing page testing working group?
09:01:38 <SerenaFeng> the one Jack works on
09:01:50 <jose_lausuch> but that's a different thing
09:01:50 <morgan_orange> ok so the one from the testing group
09:01:54 <SerenaFeng> I remember you mentioned that you want to make some update on scenarios
09:01:54 <jose_lausuch> that is the test catalog, right?
09:02:10 <morgan_orange> catalog, test list customization, ...
09:02:13 <morgan_orange> I take the point
09:02:15 <jose_lausuch> #info focus on authentication for testapi, and leave landing page for later
09:02:16 <SerenaFeng> yes, that one
09:02:17 <JackChan_> https://wiki.opnfv.org/display/dovetail/Dovetail+Test+Result+Database
09:02:18 <morgan_orange> I send a mail
09:02:21 <MatthewLi> I will contact Jack to fully support this work
09:02:46 <jose_lausuch> ok
09:02:47 <JackChan_> Hi, the requirements from landing page is also here.
09:02:48 <jose_lausuch> time's up
09:02:48 <SerenaFeng> JackChan_ also included in the same wiki page?
09:02:54 <SerenaFeng> ok
09:02:56 <JackChan_> SerenaFeng: yes
09:02:57 <SerenaFeng> I will check that
09:03:18 <morgan_orange> jose_lausuch: how can we do to generate a Danube functest docker?
09:03:55 <jose_lausuch> morgan_orange: https://build.opnfv.org/ci/view/functest/job/functest-docker-build-push-danube/
09:04:14 <jose_lausuch> it is failing
09:04:15 <morgan_orange> yep but error with bgpvpn
09:04:19 <jose_lausuch> I will check
09:04:30 <jose_lausuch> #action jose_lausuch check problem with docker image build in danube https://build.opnfv.org/ci/view/functest/job/functest-docker-build-push-danube/
09:04:34 <morgan_orange> 2 attempts (orchestra change + exclude Domino for Apex)
09:04:45 <jose_lausuch> ok
09:04:48 <jose_lausuch> I'll work on that
09:04:49 <jose_lausuch> thanks all
09:04:50 <leo_wang> @serena i check the openstackid, and it supports OAuth2.0, that can be used for auth
09:04:50 <collabot`> leo_wang: Error: "serena" is not a valid command.
09:04:53 <SerenaFeng> I think the problem is casuse by pylint in requirements.txt in bgpvpn repo
09:04:55 <morgan_orange> #action morgan_orange sync with JackChan_ for next steps on landing page
09:05:13 <SerenaFeng> upgrade setuptools will work
09:05:16 <morgan_orange> SerenaFeng: there was not such things in Danube..
09:05:25 <leo_wang> SerenaFeng: i check the openstackid, and it supports OAuth2.0, that can be used for auth
09:05:26 <SerenaFeng> okey
09:05:43 <jose_lausuch> https://gerrit.opnfv.org/gerrit/gitweb?p=sdnvpn.git;a=blob;f=setup.py;h=a6372603e2050eef972b726e466c6bdd0b5a86de;hb=refs/heads/stable/danube
09:05:47 <SerenaFeng> we can discuss offline
09:05:52 <jose_lausuch> #endmeeting