#opnfv-meeting: dovetail weekly meeting

Meeting started by hongbo123 at 14:00:56 UTC (full logs).

Meeting summary

    1. Thaj (thaj, 14:01:25)
    2. Jun Li (MatthewLi, 14:02:10)
    3. Chris Price (ChrisPriceAB, 14:02:25)
    4. Uli Kleber (uli-k, 14:03:32)
    5. Jose Lausuch (jose_lausuch, 14:05:09)
    6. Wenjing (Wenjing, 14:07:27)

  2. Atlanta PTG interop WG meeting with OPNFV test teams (ChrisPriceAB, 14:07:39)
    1. jose outlines the role of refstack, which provides the openstack certification test cases for the openstack interop WG (ChrisPriceAB, 14:08:07)
    2. refstack is used to achieve the openstack logo for products (ChrisPriceAB, 14:08:19)
    3. refstack has a suite of required test cases, and a set of optional test cases. (ChrisPriceAB, 14:08:34)
    4. the required testcases are called "defcore" which are maintained in the refstack repository (ChrisPriceAB, 14:08:55)
    5. there is a refstack client which runs the tests and reports the results back into the openstack refstack server (ChrisPriceAB, 14:09:24)
    6. the test results stored are published anonymously by the tool. (only the foundation staff have access to the user data) (ChrisPriceAB, 14:09:54)
    7. it is also possible to have a private account that you can use for those results, publishing is optional (ChrisPriceAB, 14:10:14)
    8. there is currently no encryption in these tools aside from OpenID (ChrisPriceAB, 14:10:36)
    9. the Interop WG agree on the possibility to create an NFV reference suite, we should do this together with OPNFV being the drivers. (ChrisPriceAB, 14:11:07)
    10. the NFV suite woudl then be approved by the openstack board, the board member at the meeting was supportive of doing this. (ChrisPriceAB, 14:11:29)
    11. the Interop WG agreed to creating an openstack NFV reference as an upstream reference for openstack, not limited to pharos for instance. OPNFV specifics should be maintained in OPNFV as our values (ChrisPriceAB, 14:12:36)
    12. Mika Rautakumpu (Mika_R, 14:13:07)
    13. use cases that we value in NFV can be promoted to the interop WG as an NFV reference to be evaluated according to the refstack criteria (applied to NFV) (ChrisPriceAB, 14:13:19)
    14. https://refstack.openstack.org/#/guidelines (jose_lausuch, 14:13:57)
    15. test cases we want to promote into the "NFV refstack suite" should be implemented in tempest in openstack. (ChrisPriceAB, 14:14:06)
    16. wenjing asks if these would be "NFV extentions" to refstack. (ChrisPriceAB, 14:14:23)
    17. Jose answers that we may choose to both add NFV tests and maybe remove other refstack tests from an NFV suite. (ChrisPriceAB, 14:15:00)
    18. Wenjing asks what we would do with OPNFV specific test cases that do not apply to pure openstack? (ChrisPriceAB, 14:15:34)
    19. Jose responds that these woudl not be handled in the NFV refstack suite. They would need to be handled in OPNFV. (ChrisPriceAB, 14:16:02)
    20. The topic of SDN use cases is raised which do not fit into the tempest suite as part of our CVP. (ChrisPriceAB, 14:21:50)
    21. Jose acknowledges that there will be test cases and guidelines in OPNFV that will not be handled by the refstack suite. (ChrisPriceAB, 14:22:16)
    22. https://refstack.openstack.org/#/guidelines (jose_lausuch, 14:22:30)
    23. chris asks what is the way forward. (ChrisPriceAB, 14:30:19)
    24. Jose answers that we need to start by looking at what they have and evaluating it. (ChrisPriceAB, 14:30:36)
    25. next we need to identify the test cases we would like to add to the "NFV refstack suite" (ChrisPriceAB, 14:31:02)
    26. then see if the tests exist in tempest or not. If not we should identify how to proceed either by contributing upstream or handling it ourselves. (ChrisPriceAB, 14:31:44)
    27. chris asks if functest will evaluate what exists in defcore. (ChrisPriceAB, 14:32:12)
    28. jose answers that running these tests can be done by functest already today. (ChrisPriceAB, 14:32:41)
    29. further the defcore client could be integrated as a second phase. (ChrisPriceAB, 14:32:55)
    30. ACTION: Jose to identify and run the refstack list against some basic scenario's (ChrisPriceAB, 14:35:33)
    31. ACTION: Jose to report back on how this went next week. (ChrisPriceAB, 14:36:15)
    32. ACTION: Jose to report to the test WG to make sure they are aware of what is going on. (ChrisPriceAB, 14:36:50)
    33. Goerg asks how an advisory test case becomes a mandatory test case. What is the process? (ChrisPriceAB, 14:37:29)
    34. Jose answers that every 6 months new test cases are added to the advisory test list, they need to be sufficiently mature and reviewed by the interop WG to promote these to mandatory. (ChrisPriceAB, 14:38:22)
    35. It seems to ChrisPriceAB that we may need to identify an NFV advisory list that we can publish as we do not have time to have all our needs promoted to mandatory in our timeframe. (ChrisPriceAB, 14:39:06)
    36. once we have identified the test cases we can inherit from refstack we can analyze the gaps and plan how to close them. (ChrisPriceAB, 14:45:47)
    37. Jose asks if it is OK for us to publish the results to the openstack server? (ChrisPriceAB, 14:46:03)
    38. Chris answers that for general running of test it would be OK, but for the CVP we would need to have our own solution. (ChrisPriceAB, 14:47:30)
    39. Wenjong adds that we will likely have more than just the refstack solution for our testing. (ChrisPriceAB, 14:47:58)
    40. it may be possible to leverage the refstack server solution in our own facilities to ease our own implementation work. (ChrisPriceAB, 14:48:28)
    41. Howard adds that we should likely discuss this on the OpenStack board before we use it. (ChrisPriceAB can discuss with Egle if this will be an issue and jointly approach the board) (ChrisPriceAB, 14:49:32)
    42. ACTION: Wenjing to start an etherpad for Danube project planning. (ChrisPriceAB, 15:02:41)


Meeting ended at 15:02:47 UTC (full logs).

Action items

  1. Jose to identify and run the refstack list against some basic scenario's
  2. Jose to report back on how this went next week.
  3. Jose to report to the test WG to make sure they are aware of what is going on.
  4. Wenjing to start an etherpad for Danube project planning.


Action items, by person

  1. Wenjing
    1. Wenjing to start an etherpad for Danube project planning.
  2. UNASSIGNED
    1. Jose to identify and run the refstack list against some basic scenario's
    2. Jose to report back on how this went next week.
    3. Jose to report to the test WG to make sure they are aware of what is going on.


People present (lines said)

  1. ChrisPriceAB (44)
  2. hongbo123 (16)
  3. collabot` (5)
  4. jose_lausuch (3)
  5. uli-k (2)
  6. MatthewLi (1)
  7. thaj (1)
  8. Mika_R (1)
  9. Wenjing (1)


Generated by MeetBot 0.1.4.