#opnfv-meeting: OPNFV Test & Performance Weekly Meeting

Meeting started by bryan_att at 14:26:18 UTC (full logs).

Meeting summary

    1. Bryan Sullivan (bryan_att, 14:26:33)

  2. Release Candidate Process use of Technical Calls for Reporting (bryan_att, 14:26:34)
    1. ChrisPriceAB: we need to use the technacal call for reporting on progress toward the release date (bryan_att, 14:27:21)
    2. Wenjing: Is the Pharos spec what we are targeting for the test environment for the first release? (bryan_att, 14:28:21)
    3. ChrisP: the doc needs to be more detailed so guide those who have HW and want to deploy the platform for test (bryan_att, 14:28:51)
    4. https://wiki.opnfv.org/pharos/pharos_specification (bryan_att, 14:31:30)
    5. ChrisP: the doc doesn't exist yet, we need to write it based upon the info on the Pharos page (bryan_att, 14:32:05)
    6. ... the doc should be started by April 2 (bryan_att, 14:32:47)
    7. ACTION: Pharos Team to document HW spec for Release 1 (bryan_att, 14:33:32)
    8. ACTION: Iben to help pull together the Pharos HW doc (bryan_att, 14:34:21)

  3. Functional Test (bryan_att, 14:34:32)
    1. 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 (bryan_att, 14:35:56)
    2. Wenjing: who are the main contributors? (bryan_att, 14:36:09)
    3. ChrisP: describes who is working on the different script activities (bryan_att, 14:36:49)
    4. ACTION: Functest Project to elect a project lead (bryan_att, 14:37:23)
    5. Peter Bandzi: am working on the Robot. Not sure of the status right now. (bryan_att, 14:38:15)
    6. Iben: question about the Clearwater IMS team status (bryan_att, 14:38:55)
    7. 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 (bryan_att, 14:39:43)
    8. Iben: there was an action on someone to help MetaSwitch get access to the Intel labs (bryan_att, 14:40:13)
    9. : Andy: we have VPN access but need further details e.g. in a getting started guide (bryan_att, 14:40:36)
    10. : Iben: need to connect MetaSwitch to the BGS infra (bryan_att, 14:41:08)
    11. : ChrisP: suggest that MetaSwitch gen on the BGS call (bryan_att, 14:41:32)
    12. : Iben: would like to have access to the heart temapltes so can try them out in the meantime (bryan_att, 14:41:57)
    13. : Andy: the templates are in a public repository (bryan_att, 14:42:15)
    14. : ChrisP: we should put them where we have community access (bryan_att, 14:42:32)
    15. : Andy: see no issue with cloning into the OPNFV repository (bryan_att, 14:42:55)
    16. :Iben suggests looking at https://wiki.opnfv.org/_media/pharos/opnfv_intel_hf_testbed_-_configuration.xlsx for Intel PODS info (bryan_att, 14:43:59)
    17. : Iben suggests looking at https://wiki.opnfv.org/_media/pharos/opnfv_intel_hf_testbed_-_configuration.xlsx for Intel PODS info (bryan_att, 14:44:12)
    18. last time people also mentioned vPing test is crucial, and there is tempest test for it.. (peng_li_, 14:44:14)
    19. Iben: we could use a Jenkins job to auto pull the updates (bryan_att, 14:45:44)
    20. ChrisP: we should discuss in Jira to get to a common view (bryan_att, 14:46:23)
    21. Andy: we could start with a thin wrapper e.g. shell script to transfer the updates (bryan_att, 14:48:19)
    22. peng_li: we have vPing and it's part of the tempest suite. Not sure if the work is fully done yet. (bryan_att, 14:49:54)
    23. ... people are still trying to figure out what can be done for ODL in functest (bryan_att, 14:50:32)
    24. Peter: currently using test scripts from the ODL project, not aware of any other plans (bryan_att, 14:51:00)
    25. Iben: also test for Cinder were proposed on the wiki (bryan_att, 14:51:22)
    26. Wenjing: hearing that we intend to support tesing for IMS, vPing, Robot, Tempest, Cinder, ... (bryan_att, 14:52:19)
    27. Iben: we can reorg the functest page to show what we will do first, e.g. for release candidate and then later (bryan_att, 14:53:14)
    28. ChrisP: test coverage is one of the test docs we need to produce in the Documentation project. will discuss on the TSC call (bryan_att, 14:53:56)
    29. Iben: we could create the Jenkins jobs now with stubs to outline what we intend to do (bryan_att, 14:54:39)
    30. Wenjing: will discuss further at TSC on Tue (bryan_att, 14:57:38)


Meeting ended at 14:57:41 UTC (full logs).

Action items

  1. Pharos Team to document HW spec for Release 1
  2. Iben to help pull together the Pharos HW doc
  3. Functest Project to elect a project lead


People present (lines said)

  1. bryan_att (42)
  2. fdegir (5)
  3. collabot (3)
  4. pbandzi (2)
  5. peng_li_ (1)


Generated by MeetBot 0.1.4.