08:00:06 <morgan_orange> #startmeeting Functest weekly meeting 5/9
08:00:06 <collabot> Meeting started Tue Sep  5 08:00:06 2017 UTC.  The chair is morgan_orange. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:00:06 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
08:00:06 <collabot> The meeting name has been set to 'functest_weekly_meeting_5_9'
08:00:19 <jose_lausuch> #info Jose Lausuch
08:00:19 <morgan_orange> #info PTL is back.......
08:00:25 <morgan_orange> #topic call role
08:00:28 <morgan_orange> #chait jose_lausuch
08:00:33 <morgan_orange> #chair jose_lausuch
08:00:33 <collabot> Current chairs: jose_lausuch morgan_orange
08:00:41 <morgan_orange> #info Morgan Richomme
08:00:41 <LindaWang> #info Linda Wang
08:00:42 <jose_lausuch> hi everyone :)
08:00:57 <juhak> #info Juha Kosonen
08:00:57 <LindaWang> jose_lausuch: Hello. :)
08:01:08 <CristinaPauna> jose_lausuch: Hi
08:01:08 <debayan> #info Debayan
08:01:11 <iabashin> #info Ilia Abashin
08:01:14 <morgan_orange> #info agenda for today https://wiki.opnfv.org/display/functest/Functest+5.+Meeting
08:01:16 <CristinaPauna> #info Cristina Pauna (Enea)
08:01:31 <morgan_orange> any topic you want to add?
08:02:01 <morgan_orange> iabashin: is here for calipso, debayan for vEPC integration there are also parser contributors on the chan
08:02:24 <morgan_orange> #topic action points follow up
08:02:30 <morgan_orange> #info AP1: morgan_orange contact orchestra regarding orchestra_* test cases
08:02:34 <ollivier> shangxdy_: no it cannot work as you keep the same package name as Official package. It breaks the offical upper constraints.
08:02:39 <morgan_orange> #info done, regression introduced yesterday but should be fixed now
08:02:49 <morgan_orange> #info 1 successful reun for orchestra_clearwaterims on daisy
08:02:55 <morgan_orange> #info AP2: LindaWang revert from artifact to cirios web site (patch done yesterday to run CI despite cirrios web site weas no more answering)
08:02:59 <morgan_orange> #info done
08:03:06 <morgan_orange> #info discussions on image downlaod in next topic (avoid blocking due to open baton image on some pods
08:03:13 <morgan_orange> #info AP3 morgan_orange contact releng to see if we could not avoid cleaning downloaded images after each job (cache mechanism to save time on CI pipeline)
08:03:17 <morgan_orange> #info forgotten..not done..
08:03:28 <morgan_orange> #info connected to wget discussion in next topics, i could reaction myself
08:03:35 <morgan_orange> #info AP4 ollivier patch set-functest-env.sh to indicate download failure issue
08:03:41 <morgan_orange> #info done but logs of the downlaod are very verbose....
08:03:45 <jose_lausuch> AP3 downloaded images? docker?
08:03:51 <ollivier> In case of openbaton it cannot work as we cannot check timestamps (see Linda report)
08:04:04 <morgan_orange> #info AP5 morgan_orange disable Promise, Domino, Doctor from reporting (focus on healtcheck and smoke...)
08:04:10 <morgan_orange> #info done: only healtcheck and smoke tests used in reporting pages
08:04:17 <morgan_orange> #info AP6: Shuya_ool remove dependency on fuel in testcases.yaml to try to run the testcase with all the installers
08:04:23 <morgan_orange> #info done first CI runs on vyos_vrouter
08:04:28 <morgan_orange> #info AP7: Debayan put the code for review on OPNFV repo
08:04:35 <morgan_orange> #info discussion in progress, should be done this week
08:04:40 <morgan_orange> debayan: you want to add somethign?
08:04:57 <debayan> This is ongoing; and we are waiting for an invitation from OPNFV helpdesk to proceed further ...
08:05:38 <morgan_orange> ah ok invitation still not sent...I hope it will be faster than the violations plugin in jenkins...jira created 5 weeks ago..
08:05:45 <debayan> Otherwise what you mentioned is fine Morgan ....
08:05:55 <morgan_orange> #info juju_epc team waiting for LF invitation to push code
08:05:58 <ollivier> shangxdy_: you must consider changing package name as you forked. The root name should be changed as well.
08:06:05 <morgan_orange> #info AP8: ollivier shangxdy clarify Parser requirement for functest by mail
08:06:18 <morgan_orange> as you can see...discussion in progress
08:06:21 <morgan_orange> I planned a dedicated slot
08:06:27 <morgan_orange> #info discussion in progress, see dedicated section
08:06:32 <morgan_orange> #info AP9: morgan_orange prepare list of students/ internships
08:06:42 <morgan_orange> #info done see topic internship
08:06:50 <morgan_orange> any comment on the action points?
08:06:58 <jose_lausuch> yes
08:07:06 <LindaWang> morgan_orange: The dir holding downloaded images in CI Pods was not cleaned  actually.
08:07:07 <jose_lausuch> AP3 refers to docker images?
08:07:25 <morgan_orange> no to the images we download for the tests
08:07:32 <jose_lausuch> ok
08:07:41 <jose_lausuch> I thought they were not cleaned
08:07:52 <morgan_orange> #topic Euphrates Status
08:08:17 <shangxdy_> It's inappropriate to change the root package, it will change too much.
08:08:35 <morgan_orange> maybe let's start with the downloading point
08:08:40 <jose_lausuch> ok
08:08:58 <morgan_orange> #info image download: we now do a wget with all the needed images for the tests
08:09:13 <ollivier> quite simple. We cannot check timestamps in case of one image. Then it will be downloaded for any releng job.
08:09:19 <morgan_orange> #info as it is done in the prepare env, it means that we download openbaton images even for healthcheck
08:09:46 <morgan_orange> #info it is another argument to move to alpine...where we could download the images according to the tier/tests we are doing
08:09:48 <ollivier> Yes. We must rewrite jjobs...
08:10:16 <shangxdy_> ollivier,  we continue to disccusse through email
08:10:43 <jose_lausuch> so, the idea is to download the images depending on the scenario, right?
08:10:45 <morgan_orange> shangxdy_: I planned a section for parter - at least to share the view with other contriutors
08:11:51 <ollivier> I will provide all the possible list of links. But I think this is not the key action points.
08:12:05 <LindaWang> if it depends on the scenario, how to deal with the situation: most CI jobs about compass patch verification will definitely be blocked because of timeout.
08:12:27 <LindaWang> in compass patch verification job, only healtheck and vping are run
08:12:32 <ollivier> I do think we should remove the image and disable the 2 testcases.
08:12:59 <ollivier> (timestamps cannot be checked.)
08:13:05 <jose_lausuch> what is the solution then?
08:13:11 <morgan_orange> if it is blocking a gate, It is also my view. Orchestra team did not reply to LindaWang
08:13:33 <morgan_orange> so for short term to avoid wasting CI time => disable the 2 test cases at least on compass (seems OK on apex)
08:13:41 <ollivier> Yes the tests done by Linda are much more important.
08:13:47 <morgan_orange> for mid term find a way to download the images according to the tier
08:13:50 <LindaWang> Maybe it is better for them  to  fix the image with time-stamps turning on or something like this to keep this image unchanged.
08:14:06 <morgan_orange> hence my proposal to move the gating to alpines and work on a txt file per tier
08:14:08 <ollivier> Let me disable them.
08:14:20 <ollivier> #agree
08:14:38 <jose_lausuch> txt file per tier containing what exactly?
08:15:01 <morgan_orange> the list of images needed by the tier
08:15:12 <LindaWang> the image is used by orchestra_openims and rchestra_clearwaterims?
08:15:16 <jose_lausuch> ok
08:15:29 <jose_lausuch> can't that be included in testcases.yaml?
08:15:35 <morgan_orange> jose_lausuch:  https://git.opnfv.org/functest/tree/functest/ci/download_images.sh is used whatever we are testing
08:15:37 <jose_lausuch> we have testcases.yaml for each alpine container, right?
08:15:44 <morgan_orange> yes
08:16:16 <jose_lausuch> oh, this file has changed quite a lot
08:16:24 <jose_lausuch> we had some if-else conditions before
08:16:29 <morgan_orange> lots of things changed .. :)
08:16:39 <jose_lausuch> anyway, the way you are saying sounds good
08:16:40 <LindaWang> Aha :)
08:17:08 <morgan_orange> do we agree to switch our CI gating to alpine rather than our traditional Ubuntu (except for aarch64)?
08:17:35 <jose_lausuch> from opnfv dockerhub?
08:18:08 <morgan_orange> from CI instead of pulling opnfv/functest we pull opnfv/functest-healtcheck / smoke / features and vnf
08:18:36 <jose_lausuch> so, this one for gating https://hub.docker.com/r/opnfv/functest-healthcheck/
08:18:37 <CristinaPauna> morgan_orange: do you plan to do this for E1?
08:18:48 <LindaWang> But Functest RestApi has not be ready for alpine based image. morgan_orange
08:19:27 <morgan_orange> ok so no rush...
08:19:53 <morgan_orange> short term => openbaton test constarint => only with apex (no download issue) until they fixed their timestamp issue
08:20:16 <morgan_orange> #action morgan_orange restrict orchestra test to apex (to avoid blocking compass gate)
08:20:19 <ollivier> Yezs we should swith to alpine
08:20:37 <LindaWang> When?
08:20:53 <morgan_orange> #info switch to Alpine gating to be considered. Evaluate the impacts - what is missing (functest API / consequence for aarch6', ..)
08:21:55 <morgan_orange> we can continue offline, the decission is important but in line with xci evolution and slicing demand...we are closed to the release but it is a CI question, the code is ready anyway
08:22:00 <morgan_orange> #topic calipso
08:22:30 <morgan_orange> iabashin: can you summarize for Functest contributors what calipso is doing, what are the etsts and what are your plans for E
08:22:36 <iabashin> Hi everyone
08:22:36 <ollivier> yes it's huge effort ot cobntinue maintaining the former Dockerfile
08:23:24 <morgan_orange> #link https://wiki.opnfv.org/display/vina/Calipso+Project+Proposal
08:23:29 <OPNFV-Gerrit-Bot> Cedric Ollivier proposed functest: Stop downloading openbaton image.  https://gerrit.opnfv.org/gerrit/41051
08:23:57 <morgan_orange> iabashin: can you summarize for us.. :)
08:24:16 <iabashin> Let me try..
08:25:31 <iabashin> Calipso is a standalone project in opnfv, we provide insights on network topologies (currently using OpenStack data) and in general are independent of other opnfv projects
08:26:03 <iabashin> We use docker containers to run our microservices and are currently working on integration with apex
08:26:35 <morgan_orange> iabashin: so your docker will be installed as part of an apex scenario, right?
08:26:46 <iabashin> Also we need to integrate with (I guess not into, but "with") functest in order to comply with Euphrates requirements
08:27:26 <iabashin> Yes, we do have a scenario in mind, I don't think it's approved into apex master yet though
08:28:02 <morgan_orange> it should be - all the scenarios are supposed to be frozen from several weeks but anyway..that is joy of integration :)
08:28:20 <iabashin> morgan_orange: Koren knows more about the current status (see email)
08:28:26 <morgan_orange> so y view (correct me if I am wrong): we have a system preinstalled Apex + calipso extension
08:28:47 <morgan_orange> and you would like to perform basic tests (today just check that the dockers are here)
08:28:49 <iabashin> Yeah, we're still integrating as it has been going very slowly due to lack of our experience with opnfv integration
08:28:57 <iabashin> Yes, correct
08:29:07 <jose_lausuch> iabashin: so, you basically run your stuff from your containers?
08:29:09 <morgan_orange> it could be done through a simple bash scripts but in the future you want to add more tests and you started writting so python code
08:29:24 <iabashin> But we also want to keep it generic (create a python test suite) for future testing
08:29:37 <serena-zte> agree morgan_orange
08:29:38 <morgan_orange> you expect Functest to run your tests for your future scenario on apex
08:30:13 <iabashin> jose_lausuch: I'm not sure what you refer to... We deploy our containers on a host and run our code in containers, right
08:30:55 <morgan_orange> #link https://git.opnfv.org/calipso/tree/calipso/tests/functest/smoke_test.py
08:31:01 <jose_lausuch> ok, is the code available
08:31:02 <jose_lausuch> ah ok
08:31:03 <jose_lausuch> thanks
08:31:29 <iabashin> morgan_orange: yes, and we'd prefer to do just one change to the testcases.yaml in functest and keep growing testbase without affecting the testcases.yaml
08:31:35 <morgan_orange> the code is stand alone..and as said it could have been done in a simple bash script. It seems that there is no requirements towards openStack or any uostream (just sys library)
08:32:43 <iabashin> morgan_orange: so far no. But what if there will be more specific tests in the future? We don't support just any OpenStack distribution
08:32:54 <iabashin> And, for exmaple, we require python >= 3.5
08:33:49 <morgan_orange> for the tests?
08:34:27 <iabashin> Say we've created a simple python test suite (that just runs smoke_test.py for now) and want to add it to testcases.yaml. What do I need to know more to make it happen?
08:34:52 <iabashin> For the project and preferably for the tests (to exclude possible issues in the future)
08:35:50 <morgan_orange> when I have a look at the code, I am a bit puzzled, you run command docker ps to list if calipso docker are there. But if you do that from functest docker (on the jumphost) it will not really make sense
08:36:34 <iabashin> Hm, I'll relay that to the author of the test, thanks.
08:36:35 <ollivier> or you must do it over tcp what a huge security issue regarding Docker API
08:37:16 <morgan_orange> functest runs on a docker file on the jumphost and consider the SUT as a "black box"
08:38:24 <LindaWang> morgan_orange: Not really. it can still check if calipso docker are there even though " docker ps" is executed in the functest container.
08:39:02 <serena-zte> in that case docker client needs to be installed in functest container
08:39:04 <morgan_orange> LindaWang: even if calispo dockers are on node and not on jumphost?
08:39:16 <ollivier> you can only doing that over tcp. But docker doesn't use credentials in this case. Then anyone can stop or remove containers.
08:39:23 <LindaWang> calispo dockers should be on jumphosts
08:39:24 <serena-zte> I remember docker provide APIs
08:39:39 <LindaWang> yes, Docker API makes it easy.
08:39:44 <morgan_orange> iabashin: where do you install calipso dockers?
08:39:48 <ollivier> that's why docker uses an unix socket...
08:40:16 <iabashin> I definitely recall us using jumphost
08:40:32 <morgan_orange> iabashin: ok so it shall be possible
08:40:44 <morgan_orange> we need to continue offline to address other topics
08:40:50 <iabashin> I'm not really a devops guy in our team so I am not a reliable source of info on that point
08:40:57 <morgan_orange> #info calipso docker run on jumphost
08:41:10 <morgan_orange> #info calipso testing today = check that calipso docker are there
08:41:26 <morgan_orange> #info python script created for more evolutive testing in the future
08:41:45 <jose_lausuch> iabashin: what do the containers do? what command do they run?
08:41:53 <morgan_orange> #info needs to get more info on apex scenario dealing with calipso
08:42:15 <morgan_orange> #action iabashin give details on the sceanrio planned for calipso
08:42:27 <morgan_orange> sorry we need to move
08:42:28 <serena-zte> iabashin, I think, where to install calipso is not that important, as long as it can access to OpenStack, am I right?
08:42:39 <morgan_orange> #topic Parser
08:43:11 <iabashin> jose_lausuch: we have several that run services like mongo, sensu, etc and some running our project scripts
08:43:36 <iabashin> morgan_orange: so we continue on email?
08:43:40 <serena-zte> so multiple containers?
08:43:55 <morgan_orange> iabashin: yes
08:43:55 <jose_lausuch> yes
08:43:59 <iabashin> serena-zte: yes and yes
08:44:06 <morgan_orange> shangxdy_: can you give a status
08:44:53 <morgan_orange> as far as I understand parser is not really following usual rules => Euphrates was supposed to be aligned with ocata but you are using pike
08:45:07 <shangxdy_> morgan_orange: parser has been disccussed
08:45:29 <ollivier> you must also note it also forks OpenStack projects which adds difficulties
08:46:37 <ollivier> (fork in a bad way, as it only changes info in setup.cfg instead changing egg name, namespaces...)
08:47:05 <shangxdy_> ollivier: i just repled your email, please check it.
08:47:16 <morgan_orange> is it reasonable to onboard it for E at this stage? what is the tradeoff sigularity/complexity to integrate for us?
08:48:19 <morgan_orange> #info integration still not clear: not aligned with Release management rules (Ocata based for OpenStack), fork.
08:48:39 <morgan_orange> ok let's continue also this thread by mail
08:48:47 <jose_lausuch> maybe that should be brought to release meeting?
08:48:59 <ollivier> For us? a dedicated container for Alpine, tweak OpenSTack upper constraints and create a venv in the Ubuntu one.
08:49:22 <shangxdy_> ollivier: we already concern that it doesn't work only change the setup.cfg
08:49:23 <jose_lausuch> that sounds a hassle at this stage…
08:49:42 <morgan_orange> another argument for alpine => possibility to isolate "singular " cases to onboard... :)
08:50:00 <ollivier> TYes but if we don't swithc to Alpine it's time to stop rushing isn't it?
08:50:15 <shangxdy_> morgan_orange: parser will follow the releae rules in release E, as what i said in email to ollivier
08:51:03 <morgan_orange> jose_lausuch: there were 5 persons in the last release meeting...
08:51:04 <ollivier> It won't be enough to syunc the requirements. We must tweak OpenSTack's constraints too which oblige to use the offical versions.
08:51:26 <morgan_orange> #topic Euphrates CI
08:51:28 <ollivier> If you can sync them to stable/ocata, it's already a huge task.
08:51:37 <morgan_orange> #info mail sent yesterday to give an overview of the status
08:51:52 <morgan_orange> one of the main problem is today the regression introduced by the cleaning mechanism on tempest/refstack
08:52:15 <morgan_orange> juhak: could you have a look at that. I think Martin is not there anymore
08:52:39 <juhak> I'll take a look
08:52:47 <morgan_orange> whenc cleaning fails => tempest is not executed => it affects lots of scenarios but..it seems hard to predict...
08:53:06 <morgan_orange> #action juhak look at the cleaning issue on Tempest/Refstack issue
08:53:42 <morgan_orange> #info do not hesitate to react on the mail on the different status
08:53:46 <LindaWang> it only works on fuel whatever the scenario is ha or noha.
08:54:12 <morgan_orange> there are still lots of troubleshooting especially with feature projects...
08:54:27 <morgan_orange> #topic Internships: what's next
08:54:39 <morgan_orange> #info several students contact us recently
08:54:44 <morgan_orange> #info 4 topics
08:54:48 <morgan_orange> #info 1) Security groups test case in Functest
08:54:54 <morgan_orange> #info 10/8 Yolande Amate <yolandeamate AT gmail.com>
08:54:57 <morgan_orange> #info 22/8 jayadityagupta11 AT gmail.com
08:55:01 <morgan_orange> #info 25/8 sauravmalani1 AT gmail.com
08:55:04 <morgan_orange> #info 31/8 janvi.palan AT gmail.com
08:55:08 <morgan_orange> #info 2) Web Portal for OPNFV Test AP
08:55:11 <morgan_orange> #info 9/8 rutuja.r.surve AT gmail.com
08:55:14 <morgan_orange> #info 18/8 anurag30671371 AT gmail.com
08:55:18 <morgan_orange> #info 3) VNF catalog
08:55:21 <morgan_orange> #info 24/8 Manoj Nirania <manojnirania AT gmail.com>
08:55:25 <morgan_orange> #info 4) Kubernetes testing
08:55:28 <morgan_orange> #info 2/8 konraddjimeli AT gmail.com
08:55:33 <morgan_orange> #info how do we proceed? enough mentors for the internships? topics still aligned with our needs?...
08:55:37 <morgan_orange> we shall at east answer
08:55:47 <morgan_orange> Serena is managing the one dealing with test api
08:55:57 <morgan_orange> but we need to answer to the others
08:56:03 <morgan_orange> jose_lausuch: can i action you on that?
08:56:20 <jose_lausuch> I will interview Konrad this week
08:56:51 <serena-zte> yes, I asked them to submit 3 patches before the interview :)
08:56:56 <jose_lausuch> I don't have the original emails
08:57:00 <serena-zte> I think one is almost there
08:57:20 <morgan_orange> independently from the interview, we should check if we have the resources (enough mentors) if the topics are still in line with our expectiations and we shall answer to them...
08:57:35 <morgan_orange> serena-zte: patch selection...
08:57:43 <morgan_orange> I will never have been recruited :)
08:57:50 <jose_lausuch> segarding security groups
08:58:00 <jose_lausuch> do we have a clear picture of what that means?
08:58:13 <serena-zte> because I am not very familiar with front-end, so I need some talent guy
08:58:15 <serena-zte> :)
08:58:38 <morgan_orange> jose_lausuch: yes I think David_Orange wrote everything in a web pages...it is a bit old but as far as I know such testing still does not exist...
08:59:12 <jose_lausuch> no, it doesn't
08:59:19 <jose_lausuch> maybe the task can be to investigate what's missing
08:59:23 <jose_lausuch> and implement it
08:59:26 <morgan_orange> #action jose_lausuch review the different internship requests / send mail to functest team / prepare answers to the students
08:59:46 <morgan_orange> we can help of course but if you could centralize it will be cool
08:59:52 <jose_lausuch> can you forward me the emails?
09:00:03 <morgan_orange> #action morgan_orange forward the different emails
09:00:08 <morgan_orange> #topic AoB
09:00:12 <morgan_orange> any topic you want to raise
09:00:39 <morgan_orange> the branching window is open...we did not discuss when we want to branch - usually we do that at the end of the window (end of September)
09:00:59 <jose_lausuch> yes, let´s wait
09:01:02 <ollivier> Too much work required. We should wait
09:01:09 <jose_lausuch> to not start cherry pick too much
09:01:37 <morgan_orange> #info not time for branching (too much work for integration)
09:02:00 <morgan_orange> #info Cedric sent a mail to Release Manager to educate on requirements/dependencies...which asked him to write a powerpoint (keep cool :) ) for technical meeting then TSC
09:02:26 <ollivier> Maybe i should do the same for switching to Alpine
09:02:28 <morgan_orange> #link https://wiki.opnfv.org/display/functest/Requirements+management
09:03:17 <morgan_orange> ollivier: I do not see major obstacles for the switch... LindaWang how do you see that / the internal API?
09:03:41 <ollivier> Yes. I know the gap between them the price to maintain both
09:04:24 <morgan_orange> anyway with aarch64 we will still have 2 to maintain, no?
09:04:59 <morgan_orange> CristinaPauna: you think you could investigate the topic in armband?
09:05:48 <morgan_orange> ok we are already 5 minutes late
09:06:07 <morgan_orange> it was my last interim chair..next week jose_lausuch will have read all his summer emails.. :)
09:06:15 <morgan_orange> any other topic you want to raise?
09:06:21 <jose_lausuch> hopefully :)
09:06:23 <morgan_orange> any candidate for the TSC at large
09:06:28 <jose_lausuch> thanks for taking care morgan_orange
09:06:42 <morgan_orange> I will not candidate
09:06:50 <jose_lausuch> not any more?
09:07:06 <jose_lausuch> let's discuss offline
09:07:12 <jose_lausuch> and end meeting
09:07:12 <morgan_orange> we should renew and give a chance to young people.. :)
09:07:25 <morgan_orange> ok thanks for joing still lots of pending topics
09:07:29 <morgan_orange> #endmeeting