14:26:18 <bryan_att> #startmeeting OPNFV Test & Performance Weekly Meeting 14:26:18 <collabot> Meeting started Thu Mar 26 14:26:18 2015 UTC. The chair is bryan_att. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:26:18 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic. 14:26:18 <collabot> The meeting name has been set to 'opnfv_test___performance_weekly_meeting' 14:26:33 <bryan_att> #info Bryan Sullivan 14:26:34 <bryan_att> #topic Release Candidate Process use of Technical Calls for Reporting 14:27:21 <bryan_att> #info ChrisPriceAB: we need to use the technacal call for reporting on progress toward the release date 14:28:21 <bryan_att> #info Wenjing: Is the Pharos spec what we are targeting for the test environment for the first release? 14:28:51 <bryan_att> #info ChrisP: the doc needs to be more detailed so guide those who have HW and want to deploy the platform for test 14:29:57 <pbandzi> link: https://wiki.opnfv.org/pharos/pharos_specification 14:31:30 <bryan_att> #link https://wiki.opnfv.org/pharos/pharos_specification 14:32:05 <bryan_att> #info ChrisP: the doc doesn't exist yet, we need to write it based upon the info on the Pharos page 14:32:47 <bryan_att> #info ... the doc should be started by April 2 14:33:32 <bryan_att> #action Pharos Team to document HW spec for Release 1 14:34:21 <bryan_att> #action Iben to help pull together the Pharos HW doc 14:34:32 <bryan_att> #topic Functional Test 14:35:56 <bryan_att> #info ChrisP: the team has a number of procedures defined in Jira - the schedule shows VNF should be ready for validation by next week, exercisable by Jenkins 14:36:09 <bryan_att> #info Wenjing: who are the main contributors? 14:36:49 <bryan_att> #info ChrisP: describes who is working on the different script activities 14:37:23 <bryan_att> #action Functest Project to elect a project lead 14:38:15 <bryan_att> #info Peter Bandzi: am working on the Robot. Not sure of the status right now. 14:38:55 <bryan_att> #info Iben: question about the Clearwater IMS team status 14:39:43 <bryan_att> #info Andy Caldwell: have done the heat integration on a local test system. Trouble getting access to the test system to integrate with Jenkins. Need access to Horizon, User Accounts, etc 14:40:13 <bryan_att> #info Iben: there was an action on someone to help MetaSwitch get access to the Intel labs 14:40:36 <bryan_att> #info: Andy: we have VPN access but need further details e.g. in a getting started guide 14:41:08 <bryan_att> #info: Iben: need to connect MetaSwitch to the BGS infra 14:41:32 <bryan_att> #info: ChrisP: suggest that MetaSwitch gen on the BGS call 14:41:57 <bryan_att> #info: Iben: would like to have access to the heart temapltes so can try them out in the meantime 14:42:15 <bryan_att> #info: Andy: the templates are in a public repository 14:42:32 <bryan_att> #info: ChrisP: we should put them where we have community access 14:42:55 <bryan_att> #info: Andy: see no issue with cloning into the OPNFV repository 14:43:18 <pbandzi> iben: for the access to intel PODs did you check https://wiki.opnfv.org/_media/pharos/opnfv_intel_hf_testbed_-_configuration.xlsx ? 14:43:59 <bryan_att> #info:Iben suggests looking at https://wiki.opnfv.org/_media/pharos/opnfv_intel_hf_testbed_-_configuration.xlsx for Intel PODS info 14:44:12 <bryan_att> #info: Iben suggests looking at https://wiki.opnfv.org/_media/pharos/opnfv_intel_hf_testbed_-_configuration.xlsx for Intel PODS info 14:44:14 <peng_li_> #info last time people also mentioned vPing test is crucial, and there is tempest test for it.. 14:45:44 <bryan_att> #info Iben: we could use a Jenkins job to auto pull the updates 14:46:23 <bryan_att> #info ChrisP: we should discuss in Jira to get to a common view 14:48:19 <bryan_att> #info Andy: we could start with a thin wrapper e.g. shell script to transfer the updates 14:49:03 <fdegir> please pass the details to me and I can distribute to Octopus team; fatih.degirmenci@ericsson.com 14:49:54 <bryan_att> #info peng_li: we have vPing and it's part of the tempest suite. Not sure if the work is fully done yet. 14:50:32 <bryan_att> #info ... people are still trying to figure out what can be done for ODL in functest 14:51:00 <bryan_att> #info Peter: currently using test scripts from the ODL project, not aware of any other plans 14:51:22 <bryan_att> #info Iben: also test for Cinder were proposed on the wiki 14:52:19 <bryan_att> #info Wenjing: hearing that we intend to support tesing for IMS, vPing, Robot, Tempest, Cinder, ... 14:53:14 <bryan_att> #info Iben: we can reorg the functest page to show what we will do first, e.g. for release candidate and then later 14:53:56 <bryan_att> #info ChrisP: test coverage is one of the test docs we need to produce in the Documentation project. will discuss on the TSC call 14:54:39 <bryan_att> #info Iben: we could create the Jenkins jobs now with stubs to outline what we intend to do 14:55:06 <fdegir> jenkins jobs should not know which TCs should be run 14:55:26 <fdegir> they should be in configuration files based on test FW and pointed by scripts 14:55:35 <fdegir> jenkins jobs should only execute a script 14:56:19 <fdegir> per test FW 14:57:38 <bryan_att> #info Wenjing: will discuss further at TSC on Tue 14:57:41 <bryan_att> #endmeeting