12:52:14 #startmeeting OPNFV Functest 12:52:14 Meeting started Tue Apr 7 12:52:14 2015 UTC. The chair is trevor_intel. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:52:14 Useful Commands: #action #agreed #help #info #idea #link #topic. 12:52:14 The meeting name has been set to 'opnfv_functest' 12:53:05 #info Trevor Cooper (Intel) 12:53:50 Hello everyone@ 12:54:24 I see you have documentation already on the agenda 12:55:39 #info morgan 12:55:45 as part of that can we get Victor Laza (Vic) to be added as a contributor? 12:55:52 #info Iben 12:56:11 It is possible from any partner can create an audio bridge? 12:56:19 for the record - this is an IRC only meeting??? no g2m? 12:56:19 or just vlaza , so we don't overcomplicate 12:56:47 #info vlaza Victor Laza - from Cloudbase Solutions - will be helping with documentation 12:57:15 Yes, from the invitation I think this is an irc only meeting 13:00:33 hi 13:00:33 hi vlaza 13:00:34 We cant use the GTM because there is the weekly Doctor meeting now 13:00:39 hello 13:00:44 I can provide a dial-in audio bridge if that will help 13:00:45 hi 13:00:45 Should I send out an Intel bridge? 13:00:53 Ok Bryan thanks 13:00:56 In the US, either: +1-888-388-6645x2125903# or +1-212-372-3682x2125903# 13:01:13 #info Peter Bandzi 13:01:14 A number in your country or in a country close to you (may be toll free): https://www.teleconference.att.com/servlet/glbAccess?process=1&accessNumber=8883886645&accessCode=2125903 13:02:33 #info Bryan Sullivan 13:04:13 #chair bryan_att 13:04:13 Current chairs: bryan_att trevor_intel 13:04:48 bryan_att: Error: Can't start another meeting, one is in progress. Use #endmeeting first. 13:05:02 #topic Agenda runthru 13:05:06 bryan_att: trevor_intel already initiated the conf 13:06:22 #info Trevor: at the RC meeting there wasn't functest representation. An action was given to provide the R1 functest state. Emails showed unclarity on who to contact etc for the project. This call is to help coordinate. 13:06:48 #topic 1. Functest leader 13:07:26 #topic Agenda runthru 13:07:39 (sorry - got ahead of myself) 13:08:21 can we limit the time for each topic? 13:08:27 documentation is pretty important. 13:08:41 #info Trevor runs thru the rest of the agenda sent via email to the list 13:08:43 #topic 1. Functest leader 13:09:21 #info Uli: about the committers - we would like to add a committer from Huawei 13:10:06 new commiters should have a role 13:10:10 what will they do? 13:10:20 #info morgan: anyone should be able to nominate - its just a standard vote process 13:10:21 # info Fuqiao 13:10:26 we had requests for some simple background for each new committer? 13:10:51 what will they be working on? area of expertise? 13:11:19 #info Trevor: just submit and we will vote 13:11:54 iben: good point, would be nice to know details like this; also related to the part of the project an individual contributes 13:11:56 +1 Morgan 13:11:57 #info ... Morgan was nominated by me; does he accept? any other nominations? 13:11:58 +1 for Morgan - but does he want it? 13:12:11 #info Morgan: accepts 13:12:15 no 13:12:47 +1 Morgan 13:12:49 +1 Morgan 13:12:58 +1 Morgan 13:13:05 #info Trevor: any other nominations? (no answer). Majority committer vote is required, offline since we don't have majority here 13:13:07 is morgan_orange already a committer? 13:13:15 we want to promote him to PTL 13:13:15 iyes 13:13:48 existing commiters are in the info file - right? 13:13:49 +1 Morgan 13:14:08 +1 Morgan 13:14:25 #info Trevor: if no other nominations for leader, there is no competition and no need for a vote? (presumed) 13:14:32 +1 Morgan 13:14:58 thsi the list of committers get pruned? That might make this process easier too 13:14:59 Congratulation Morange 13:15:04 :) 13:15:04 did 13:15:11 #info ... We will asseume Morgan is the leader for now (we will verify the election process as needed) 13:15:21 #topic 2. RC1 13:16:16 #info Morgan: we will have 5 test cases per the wiki, automated within the CI 13:16:34 (we need a link to the wiki page, someone) 13:17:08 https://wiki.opnfv.org/opnfv_functional_testing ? 13:17:08 #info ... for R1 this is all that is achievable. Progress is bring made on the 5 test cases 13:17:43 #link https://wiki.opnfv.org/opnfv_functional_testing 13:17:52 #link https://wiki.opnfv.org/pharos_testing 13:18:08 this is a new page 13:18:37 #info this wiki page was made to replace the original page so now there are 2 - they need to be merged 13:18:53 #action morgan_orange to merge these pages 13:18:59 #info ... will reformat the tests on the Pharos page onto the Functest wiki 13:19:07 will there still be a pharos project? 13:19:17 #info ... the Functest page will be the single ref for Functest 13:19:57 #info ... re Pharos, it will continue to define the testbed hardware, but not the actual testing 13:20:23 #info trevor_intel is in charge of the pharos project 13:20:51 #info ... need to create a RST file for the repository since that's the R1 product 13:21:11 bryan_att: that’s what vlaza will be helping with 13:21:16 Does the opnfv jira require a login just to view Jiras? 13:21:20 or can help with if needed 13:21:41 #info ... the testing info will include the hardware (Pharos), stacks, additional functions being tested (IPv6), etc 13:21:42 but we need vlaza added as a commiter 13:22:21 if I can commit, I can write or rewrite whatever documentation in reST markup 13:22:41 #info ... committed the RST file for Functest 13:23:01 (someone please #link the gerrit review page for the RST file)\ 13:23:36 #link https://gerrit.opnfv.org/gerrit/#/c/257/ 13:23:41 #info Trevor: what review needs to be done before commit is done? 13:24:46 #info Morgan: already have support from various people; still working on Intel lab connection; need Jenkins support 13:24:58 #info ... (support from Intel) 13:25:39 #info ... will redo on a local testbed; who can help? 13:26:21 #info Trevor: list who needs to be on a live debug session and will set it up 13:28:11 #info Iben: a number of Jenkins server setups are underway - get together onto #opnfv; Victor is helping the setup process 13:28:43 what is meant with Jenkins servers? 13:28:47 #info ... i.e. a number of debug sessions are needed 13:28:57 can someone clarify please? 13:29:06 Jenkins is the client that pulls the repository info to the lab machines 13:29:19 we have one Jenkins for OPNFV 13:29:28 does "Jenkins servers" mean slaves? 13:29:33 yes 13:29:36 ok 13:29:37 thanks 13:29:39 #link https://build.opnfv.org/ci/ 13:29:40 clear now 13:30:44 need someone from Intel (FW) on #opnfv 13:31:36 #info Trevor: still need to know who to setup the debug session with 13:31:44 i’m dropping to IRC only 13:32:05 #info Morgan: ask the Intel person to join the IRC channel 13:32:17 aricg from lf can join a bridge if you need him to 13:32:22 #info Trevor: will try but not sure that will help 13:32:27 just coordinate with him on irc 13:32:53 #info ... I will be the point of contact for now 13:34:29 suggest we move onto other agenda topics... 13:34:57 #topic 3. Communication 13:35:40 #info Morgan: IRC channel #testperf, Etherpad (link?), document in the repo 13:36:01 #link https://etherpad.opnfv.org/p/functiontestrelease1activities 13:36:11 #info ... we should have enough channels to communicate 13:36:52 #info ... will setup a weekly meeting for Functest, IRC only if possible; can report during Thurs meeting 13:37:16 #info Trevor: suggest to use the weekly (Thurs) meeting for Functest update also until release 13:38:51 #info Morgan: it's not clear the diff between the #opnfv channel and the #opnfv-ci channel 13:39:11 I can also provide a webex for jenkins server troubleshooting sessions if needed. 13:39:20 #info ... the #opnfv-octopus channel 13:39:30 #topic 4. Documentation 13:40:13 #info Morgan: for R1, the RST is the most important; ask for contributors to complete their part; test case descriptions, automation in CI, ... 13:40:27 #info ... we can work on the wiki in the meantime 13:40:36 I think we should use IRC 13:40:43 #info ... sent a proposal for the repo tree for the scripts 13:41:00 jenkins related stuff has been discussed in #opnfv-octopus channel mainly 13:41:17 so the plan will be to convert to reST the documentation that will be present on wiki? 13:41:23 #info ... don't need more documents; assume we are using a lot of info from other projects 13:42:14 (note) I suggest that the points you want to make are picked up by the chair and voiced on the call if you're not on, otherwise speak up for the floor 13:42:31 #info Trevor: is it clear who owns the sections? 13:42:58 #info bryan: it should be in the doc as a placeholder 13:43:24 #action Morgan to put contributor info into the RST 13:43:34 #topic 5. CI integration 13:43:56 #info Morgan: Intel and Spirent are already connected 13:44:01 #link https://etherpad.opnfv.org/p/octopus 13:44:05 #info ... the procedure looks pretty clear 13:44:54 #info ... still need the scripts to run tests; but first need to get connectivity 13:45:42 #info ... anyone from CI on the bridge/IRC? 13:45:53 #info ... any testing already integrated into CI? 13:46:10 #info We haven't integrated any testing in CI 13:46:16 #info Uli: no auto integration yet 13:47:32 #info bryan: is the install a blocking issue for getting the scripts updated? 13:47:35 sorry lost my audio ...... 13:49:38 #info Morgan: we can write scripts to run the tests; we don't have to wait 13:50:08 #topic 6. Testing 13:50:25 #info Morgan: new test case is vPing 13:51:10 #info malla: connected two machines in the POD for the ping test 13:51:31 #info ... just doing local testing for now 13:51:46 #info Trevor: any issues still creating VMs? 13:51:56 #info malla: still an issue, working on it 13:52:06 #info Trevor: need help or Intel POD support? 13:52:18 #info malla: yes; will contact Morgan 13:53:33 #info Morgan: the installation is not complete, the config of OpenStack is likely blocking VM creation; need to discuss with BGS people 13:54:01 #info ... had to load a CentOS image (the ones there were private) etc 13:54:32 #info ... the lab is pre-release based upon the Foreman installer 13:54:58 #info ... still some config work to do; to be sure we are not trying to test with blocking issues 13:57:21 #info bryan: who knows how to verify that the config is right; we need to document those steps 13:57:52 #info ... then firgure out a way to automate it 13:58:29 #info Trevor: for work on R1, POD2 assumes manual steps relative to Foreman; is Functest only supporting Foreman? 13:58:45 #info Morgan: should support any installer 13:59:05 #info Trevor: but with 2 weeks left; is anyone doing that for Fuel, now? 13:59:27 #info Morgan: don't think so, all focus is on one installer; difficult to do this in parallel 13:59:55 #info ... goal is to test using Fuel on the Ericsson POD; the challenge is to get it working in one case first 14:00:25 #info ... in Fuel, Tempest and Rally are integrated; we need to pull that out of the installer 14:00:49 #info ... vIMS, ODL, vPING should be testable using Fuel 14:01:01 #topic 7. vIMS test suite progress 14:01:21 #info Martin: blocked by inability to bring up VMs on the POD2 platform 14:01:48 #info ... working to debug the OpenStack installation left by the Foreman installer; appears incomplete/misonfigured 14:02:05 #info ... need to feed that back to BGS 14:03:04 #info Morgan: if we are blocked, should we pause on the Ericsson POD? 14:04:32 #info (corrected) should work on the Ericsson / Fuel POD in the meantime since we have a block on the Intel POD 14:04:58 #info Trevor: need to coordinate with who is using the Ericsson POD 14:05:49 bryan_att: me (Fatih Degirmenci) and Jonas Bjurel can be contacted regarding Ericsson POD 14:06:20 #info Morgan: will reach out to (Fatih Degirmenci) and Jonas Bjurel can be contacted regarding Ericsson POD 14:08:48 #info Need to get back to BGS (Foreman) for starting point to beable to spin up VMs 14:09:25 #info continue on Thursday test and performacne meeting 14:09:37 #endmeeting