08:00:08 #startmeeting Functest weekly meeting February 2nd 08:00:08 Meeting started Tue Feb 2 08:00:08 2016 UTC. The chair is morgan_orange. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:08 Useful Commands: #action #agreed #help #info #idea #link #topic. 08:00:08 The meeting name has been set to 'functest_weekly_meeting_february_2nd' 08:00:14 #info Morgan Richomme 08:00:18 #info Viktor Tikkanen 08:00:19 #info Juha Kosonen 08:00:54 #info agenda https://wiki.opnfv.org/functest_meeting 08:01:12 #info topic Action point follow up 08:01:21 #link http://ircbot.wl.linuxfoundation.org/meetings/opnfv-testperf/2016/opnfv-testperf.2016-01-26-08.00.html 08:01:49 hi 08:01:50 #info hardware configuration check done on Huawei, Orange POD2 and LF POD2 08:01:55 #info Jose Lausuch 08:01:59 hi jose_lausuch and raghavendrachari 08:02:11 Hi 08:02:17 have a nice day .!! 08:02:49 :) 08:02:49 as far as I understand we excluded a problem tempest worker / hardware config of the jumphost 08:02:52 what is the topic sorry? 08:03:08 just reviewing the action points of last week 08:03:30 we checked the HW config of the jumphost to see if it was the cause of the worker issue detected by viktor_nokia 08:03:49 yes 08:03:53 did we reach any conclussion? 08:04:42 I think we got the same config on LF POD1 and LF POD2 and had issue on LF POD1 not on LF POD2 so ...my understanding that this is not the cause of the error 08:04:49 but I may be wrong... 08:05:05 and huawey pod had similar HW 08:05:17 a lot of CPUs in all the cases... 08:05:21 on the jumphost I mean 08:05:53 Huawei sorry 08:05:55 #info juhak refactoring of volume management on rally-cert done 08:06:08 #info morgan_orange adaptation of oDL suite for JOID done 08:06:17 juhak: rally shows always problems with live migration 08:06:29 shall we say live migration of VMs is not supported ? 08:06:45 #info robot scenario path changed in ODL repo, but scenario did not change 08:06:57 #topic Release B 08:06:58 live migration requires shared storage 08:07:14 but we have ceph in theory... 08:07:28 #info refactoring of traces of Tempest and Rally in Jenkins done => nice results 08:07:33 or we don't use it for ephemeral... 08:07:49 #info question on rally issue on live migration => shall these scenario be excluded? 08:07:59 should we exclude live migration cases - for the time being? 08:08:42 I don't know how the tests are performed, but I imagine it uses ephemeral (local disk) which I think it is not ceph, it's just local , but I'm not 100% 08:08:43 sure 08:08:53 but we might exclude them 08:08:54 if we know why it is failing...it makes sense... 08:09:09 and just show the tests that are in tempest (if any) to prove that it fails 08:09:19 and explain why 08:09:43 May-meimei: can you check on Compass pods how is that implemented? 08:09:49 #info possible now to have a synthetic view of the different results 08:09:57 #link http://testresults.opnfv.org/proto/index-pod.html 08:09:57 ceph for cinder? ceph for ephemeral? 08:10:07 #link http://testresults.opnfv.org/proto/index-scenario.html 08:10:18 #link http://testresults.opnfv.org/proto/index2.html 08:10:23 on Orange POD it is Ceph 08:10:38 joid? 08:10:55 so tests should run but since yesterday we got regression, no Tempest tests are run (error saying that the config file cannot be found) 08:11:02 jose_lausuch: yes joid /orange POD2 08:11:23 morgan_orange: ok, thanks, I see that live migration doesn't fail on orange pod2, but cinder stuff failed.. 08:12:13 so if it is OK on some PODs, I suggest to keep the test and explains in the user guide... 08:12:17 yes 08:12:20 +1 08:12:26 ok 08:12:36 do we know why volume rally tests fail on that pod? 08:12:43 test scenario CinderVolumes.create_and_attach_volume 08:12:48 test scenario CinderVolumes.create_and_delete_volume 08:12:53 test scenario CinderVolumes.list_volumes 08:12:57 test scenario CinderVolumes.create_nested_snapshots_and_attach_volume3 08:13:01 those are success 0% 08:13:04 here https://build.opnfv.org/ci/view/functest/job/functest-joid-orange-pod2-daily-master/55/console 08:13:11 to further investigate 08:13:14 not now :) 08:13:36 action someone with access to orange pod 2 08:13:38 David? :) 08:13:58 I think David_Orange juhak viktor_nokia raghavendrachari and myself have access to this POD... 08:14:41 yes am having access 08:14:43 #info regarding B release, still investigations mainly on vPing, vIMS 08:15:04 yes, i can execute cinder cases manually in pod2 and check what's the problem 08:15:42 juhak: ok, thanks. just things like that, cinder list, cinder create, snapshots, etc 08:15:52 #action juhak perform cinder test on Orange pod2 08:15:54 attach 08:16:03 #info ODL suite on joid now looks like in apex (15OK /3 KO) I think that it is due to an update of the code, the tests did not follow => so I can change the test or just document it 08:16:09 #info ONOS tests OK 08:16:22 #info promise tests run 08:16:52 #info Tempest was relatively stable alert on regression on Orange POD2 (last 2 run => impossible to find the config) => I will have a look at it 08:17:05 #action morgan_orange Tempest on Orange POD2 where is the tempest.conf... 08:17:13 morgan_orange: remember the tests that fail are the lats ones, delete stuff, that is what pbandzi did, not taken from the repo, maybe there is something to change 08:17:36 jose_lausuch: yes I will check that too 08:17:37 yes, something fishy happens with tempest.conf 08:17:45 I've seen it several times 08:17:47 ok 08:18:01 #action morgan_orange ODL check the delete scenario from upstream repo (instead of tests in OPNFV repo) 08:18:22 what is strange is that it was very stable...I can do it manually to see what happens 08:19:02 #info Rally suite seems Ok for the release 08:19:25 I saw some errors on heat scenario but nothing critical for the release 08:19:42 yep 08:19:47 heat was failing in some cases too 08:19:49 for the vPing/SSH, I saw success results in Apex, Compass and Joid 08:19:58 with ODL or ONOS? 08:20:05 are you IRC only? GTM tells me waiting for moderator. 08:20:19 GeraldK_: yes, IRC only :) 08:20:38 for the vPing/SSH apex and joid with odl_l2 08:20:48 for compass also I think 08:20:49 okay. just wondered as the invitation had a GTM link 08:20:55 : I'll check those heat cases too on pod2 08:21:08 morgan_orange: floating ips didnt work in Apex+ONOS 08:21:21 #action juhak checkheat cases on Orange POD2 08:21:40 neither in Apex+ODL-l3 08:21:41 jose_lausuch: but it works once with apex now? 08:21:52 apex/odl_l2 08:22:11 so https://wiki.opnfv.org/vping_brahmaputra_page?&#vping is up to date? 08:22:11 Apex+ODL-L2 08:22:12 yes 08:22:25 comapss I saw something successfull with onos 08:22:38 very long 266s but it was ok 08:23:32 morgan_orange: compass+ODL-l2 failed too https://build.opnfv.org/ci/view/functest/job/functest-compass-huawei-us-deploy-bare-1-daily-brahmaputra/57/consoleFull 08:23:36 Cannot establish connection to IP '192.168.10.101'. Aborting 08:23:45 yes the last success was compass/onos 08:24:09 Valentin_Orange: status on vIMS? 08:24:09 yes https://build.opnfv.org/ci/view/functest/job/functest-compass-huawei-us-deploy-bare-1-daily-brahmaputra/56/consoleFull 08:24:37 #info vPing some scenario now working apex/odl_l2, compass/onos, joid/odl_l2.... 08:24:40 #action jose_lausuch push to DB if vPing test timeout 08:24:52 #info more run needed to update and confirm the status 08:26:10 #info as you know theoretically we have slot for troubleshooting 08:26:31 morgan_orange: ok on apex/odl_l2 08:26:49 morgan_orange: ok on fuel/odl_l2 08:27:08 morgan_orange: KO on joid/odl_l2 .. 08:28:17 #link https://wiki.opnfv.org/vims_brahmaputra_page 08:28:29 #info progress on vIMS test case 08:28:49 #info vIMS OK on fuel and apex odl_l2, investigation in progress on joid and compass 08:29:08 #info reminder troubleshooting slots for Functest : LF POD1 (Apex) 18-20 UTC / LF POD2 (Fuel) 5-16 UTC, POD5 (Joid) 19-18 UTC, POD8 (Compass??) 13-15UTC, POD6 (joid), 19-20 UTC... 08:29:25 jose_lausuch: did you get access to POD5 and POD6? 08:29:40 just to know if it is now easier than LF POD access... 08:29:44 morgan_orange: not yet, still waiting, the JIRA issue was changed to another person 08:29:49 :) 08:30:13 I think we can report that access to the POD is still an issue...and yesterday no POD was abvailable for testing... 08:30:26 we are supposed to be in testing phase with stable System Under Test.... 08:30:35 no run of Fuel since 2 or 3 days.. 08:30:51 The graphs are crual but they do not lie... 08:30:53 still failed deployments sometimes :) 08:31:26 #info so to summarize on Functest for B release 08:32:10 #info vPing => need more scenario to check, recent progress in apex/odl_l2 and compass/onos but all combinations still not there 08:32:14 vIMS is so not stable 08:32:22 all kinds of problems 08:32:53 #info vPing_userdata need more scenario to confirm existing results (all old_l2 scenario OK) 08:33:32 #info ODL => check the 3 custom tests but OK on the different labs (just a test to check norhbound API of the Controller at the end) 08:33:50 #info ONOS => ok on all installers (need more run to confirm stability) 08:34:30 good 08:34:45 #info vIMS OK on apex/fuel still issues with compass/joid, complex test cases (more close to realistic needs of Telco) 08:34:56 leo_wang: how could we investigate more efficiently 08:35:06 would it be possible to grant access to Valentin_Orange? 08:35:15 we are lacking direct access to a compass lab 08:35:33 Intel POD8 has been assigned but can we use it? is there any Compass solution with a scneario running in this lab? 08:35:42 the problem varies every time 08:36:11 a priori not with apex and fuel 08:36:16 even failed to download cfy blueprint 08:36:23 network issue 08:37:01 and create a venv may fail too 08:37:01 ok continue discuss it with Valentin_Orange offline but it would be great to have an access to the lab to help you 08:37:42 :( 08:37:51 ok 08:38:01 #info promise OK 08:38:22 #info ovno a bit late but theoretically it is ready from a Functest/CI perspective 08:38:44 #info sdnvpn idem ovno wait for a run of the scenario to see if the tests are properly triggered 08:39:05 I think we should ask for a strategy on scenario on CI 08:39:22 what do you mean? 08:39:29 CI slots have been defined..these slots must be used to run the different scenario 08:39:42 It is strange to have 1 run / day last week end for each installer... 08:39:49 yes 08:39:54 that is not acceptable 08:39:57 during the CI slot we should have at least 2 runs with 2 different scenario 08:40:26 #action morgan_orange propose scenario strategy for CI to get more deployment and then more tests 08:40:54 #info labs still not really ready for troubleshooting (no CI labs available yesterady) 08:41:37 #info doc has been updated, ChrisPriceAB split it to provide a global doc, everbody can still review it and patch it especially for the troubleshooting section 08:41:48 we have lots of things to say... :) 08:41:55 anythging else on B release? 08:42:24 Once the docs are on master I should be able to put them in context. Then we may need some editing. But otherwise on track. 08:42:30 #action leo_wang provide access to Compass labs to Valentin_Orange for vIMS troubleshooting on compass 08:42:52 ChrisPriceAB: aren't they on master already? what do you mean? 08:43:24 They are, just saying I will have a central doc up soon. Then whateer is on master will be pulled in. (Patches will not) 08:43:42 ChrisPriceAB: ok, thanks ! 08:44:25 ok viktor_nokia juhak jose_lausuch Valentin_Orange ChrisPriceAB raghavendrachari leo_wang May-meimei anything else to add for B release... 08:44:55 #topic plugfest 08:44:56 1 small thing 08:45:00 #undo 08:45:00 Removing item from minutes: 08:45:16 it seems everyone liked the new way of cleaning openstack defaults 08:45:25 oh yes... 08:45:30 well done 08:45:33 I'll merge https://gerrit.opnfv.org/gerrit/#/c/8927/1 08:45:41 ok 08:45:46 :) :) 08:46:06 if all the installers would have provide a consistent config, it would not have been needed but...we can see that it is useful... 08:46:20 maybe for the next release we can have 2 options 08:46:38 cleanup everything, or just cleanup the things that were there before the tests 08:46:41 let's discuss in the last 10 minutes discussions on next release... 08:46:45 #topic plugfest 08:46:50 sure 08:47:03 #info as you know a plug fest is on track. it will be organized in Colorado in May (Cable Labs) 08:47:09 question 1: who will attend? 08:47:24 I mean from Functest contributor;.. 08:47:37 * jose_lausuch doesn't... 08:47:50 I will try to follow the discussion on dovetail on this topic but not easy to find time 08:48:04 I am not sure we are mandatory for such plugfest but our tests will be... 08:48:09 Nokia is planning to participate PlugFest. don't know yet if Viktor or me will be there 08:48:52 I think Orange will probably also participate but not clear who, all the more as we are supposed to organize a plugfest in Q3 in France 08:49:27 so is userguide + container + adapation of the graphs enough as Functest contribution to this plugfest? 08:49:37 or do you see stuff we should have to do from no to May 08:49:45 specifically for such event? 08:50:22 #info Nokia and Orange will probably participate (need confirmation, people not designated at the moment) 08:50:47 #info question what can we bring as input for such event 08:50:50 I think that event is more focus on NFV point of view right? 08:50:58 something maybe more important for yardstick guys 08:51:40 yep even if running our basic suites gives already a good feedback...and provide some elements of comparison... 08:52:07 but OK the idea is not to answer today, I will keep a small point also next weeks to discuss that and I will try to follow a little bit more dovetail 08:52:11 I think there will be some YardStick people there and Fuel. 08:52:19 #topic Release C 08:52:36 But functest has a bunch of troubleshooting skils that would be applicable so don't not go... :D 08:52:59 #link https://etherpad.opnfv.org/p/functest_release_C 08:53:23 ChrisPriceAB: :) to what level troubleshooting fits in that event? 08:53:37 #info for the moment it is a white page, I see already some possible actions/improvements and I have questions 08:54:15 plugging in new components, running our software on new hardware. There is likely trouble in those waters... (back on topic jose_lausuch) 08:54:17 morgan_orange: I will fill some info, some ideas 08:54:39 ChrisPriceAB: ok, I see, thanks 08:54:40 for ODL, I do not know if we should keep it inside or externalize it (as ONOS) 08:55:06 I think it is time to try to give back to rally and to contribute directly on rally to define Telco KPI 08:55:15 question who goes to Austin for the OpenStack summit... 08:55:25 I think it would be easier to do that in Barcelona... 08:55:28 morgan_orange: I will add some titles (blocks) for each component, so people can add ideas in an ordered way 08:55:48 Barcelona is closer ;) 08:55:48 yes I think we should consider 08:56:01 not in time.. 08:56:10 - existing testcases (evolution, ...) 08:56:20 - nex test cases (sync with Intel and new VNF) 08:56:33 - use of orchestrator? 08:56:34 yep 08:56:42 something to be discussed of course 08:56:44 - better analytics of our results (we are building a mine) 08:57:04 - move to current home API to something like ELK ? 08:57:12 ELK? 08:57:22 Elastic Search / Logstash / Kibana 08:57:22 ah ok 08:57:28 yep 08:57:46 discuss when we should onboard or externalize companion test cases 08:57:47 shall we everyone take the action to write ideas? 08:58:09 #info etherpad open for Functest Release C 08:58:18 #info we should consider: 08:58:36 #info - existing testcases (evolution, in&out) 08:58:45 #info next test cases (sync with Intel and new VNF) 08:58:54 #info role of orchestrator for testing 08:59:08 #info -upstream contribution( E.g. Rally) 08:59:17 #info - analytics? 08:59:35 #info moving from home made API + Mongo to ELK? 08:59:52 #action evrybody complete this etherpad 09:00:02 #link https://etherpad.opnfv.org/p/functest_release_C 09:00:27 we will have more time after C release, but we will probably not see in real before Berlin, which will be too late for new feature definition 09:00:52 we need to have a clear view of our vizion for March/April => idea is to define the figure as we did for brahmaputra 09:01:15 https://wiki.opnfv.org/functextnexttaks 09:01:27 The figure has not been changed since last July 09:01:43 and it is was not fully stupid... 09:01:53 #topic AoB 09:01:57 we are 1 minute late 09:02:12 anything you want to share before ending the meeting? 09:02:22 nop 09:02:27 I want to share one => vote for jose to quartely awards... 09:02:29 everything ok 09:02:54 hahaha its not needed, you are too nice :) 09:02:59 we can vote also to viktor_nokia: juhak Valentin_Orange for their contribution 09:03:13 and also May-meimei of course 09:03:41 I'm already the Rock'n Tester... ChrisPriceAB^ 09:04:14 ok so have a good week, lots of work ahead...meaning that such system needs still some testing... 09:04:27 #endmeeting