#opnfv-meeting: Weekly Technical Discussion

Meeting started by bin_ at 14:02:47 UTC (full logs).

Meeting summary

    1. Bin Hu (bin_, 14:03:00)
    2. Carlos Goncalves (cgoncalves, 14:03:53)
    3. hongbo (hongbo1, 14:04:01)
    4. Morgan Richomme (morgan_orange, 14:04:10)
    5. rprakash (rprakash, 14:05:37)

  2. Certification Program and Dovetail (bin_, 14:06:05)
    1. Wenjing introduced background of CVP, which was chartered by Board (bin_, 14:06:52)
    2. Dovetail defines test case etc (bin_, 14:07:09)
    3. Team looked at scenarios, configurations, feature use cases, etc. (bin_, 14:10:24)
    4. intend to define test framework, tools and test cases (bin_, 14:10:55)
    5. Wenjing described OPNFV Reference Platform concept and diagram on slide #2 (bin_, 14:12:29)
    6. and common interface points on slide #3 (bin_, 14:13:13)
    7. there are 2 types of SUTs. Hardware platform and NFVI+VIM (software), illustrated on slide #4 (bin_, 14:16:58)
    8. Morgan asked if the word "derived" means something from existing tests or something different (bin_, 14:18:36)
    9. Wenjing said now it is identical, in the future, it might be slightly different (bin_, 14:19:10)
    10. Wenjing said main difference could be in NFVI to VIM interface (bin_, 14:19:50)
    11. Morgan said it should be possible to flag those test cases that will be used for certification tests (bin_, 14:20:53)
    12. There could be additional test cases for certification tests purpose (bin_, 14:21:27)
    13. if there are just additional functions, it can be added to existing test cases. No problem to add improvement in existing test cases (bin_, 14:24:23)
    14. if there are new features such as onboarding, Yardstick can do. (bin_, 14:24:52)
    15. Hongbo said FuncTest and Yardstick have already helped a lot, and we will work together (bin_, 14:25:49)
    16. Wenjing introduced self-testing method on slide #5 (bin_, 14:26:35)
    17. One is to validate hardware SUT, and the other is to validate HW+NFVI+VIM SUT (bin_, 14:27:21)
    18. and the documentation needed (bin_, 14:28:07)
    19. a view of test suite coverage is presented on slide #6 (bin_, 14:28:40)
    20. IPv6 will be covered (bin_, 14:30:46)
    21. SDNVPN is considered (bin_, 14:31:09)
    22. MANO will be in the future (bin_, 14:31:16)
    23. a workflow from test suite, test area, test case, tools is depicted on slide #7 (bin_, 14:32:54)
    24. Morgan mentioned test WG's workflow, including CI, is very similar. (bin_, 14:34:19)
    25. several categories have been defined already (bin_, 14:34:34)
    26. there are unit test cases such as Tempest, all the VIM part, and smoke tests (bin_, 14:35:06)
    27. Larry Lamers (ljlamers, 14:35:54)
    28. So current test WG workflow could satisfy the need of certification test, because all the mechanisms have been in place (bin_, 14:36:07)
    29. Wenjing mentioned it could be great to harmonize, especially for Danube (bin_, 14:37:12)
    30. Other general project information is available on slide #8 (bin_, 14:37:56)
    31. Hongbo introduced PlugFest planned for December (bin_, 14:38:28)
    32. First try to run Dovetail on different hardware platform (bin_, 14:39:01)
    33. Second task to try to use some tools for interoperability (bin_, 14:39:26)
    34. we are developing some tools (bin_, 14:39:57)
    35. need to collaborate with test WG (bin_, 14:40:17)
    36. Wenjing asked for questions (bin_, 14:40:48)
    37. Dave N said the purpose is to raise community awareness, and get feedback from community (bin_, 14:41:18)
    38. Wenjing welcome more participation in PlugFest (bin_, 14:42:57)
    39. Bryan asked where was the awareness of dovetail came from (bin_, 14:43:38)
    40. Wenjing answered from TSC call, Infra WG, etc. for lacking the visibility (bin_, 14:44:25)

  3. OPNFV Vision and Priorities for Danube (bin_, 14:51:16)
    1. Morgan indicated that it is not ready for community discussion yet (bin_, 14:51:35)
    2. we started discussion on TSC, and will create a wiki based on discussion on TSC (bin_, 14:51:56)
    3. we are not trying to create competition among project (bin_, 14:52:11)
    4. but to optimize resources and harmonization (bin_, 14:52:36)
    5. the discussion is collected in etherpad for various points (bin_, 14:52:57)
    6. such as what are 5 priorities in Danube (bin_, 14:53:19)
    7. the coordination is already a challenging (bin_, 14:53:38)
    8. difficult to explain new features and new scenarios in marketing (bin_, 14:55:36)
    9. the idea is to collect points before December (bin_, 14:55:57)
    10. to know where we want to go (bin_, 14:56:15)
    11. and a little bit steering from TSC (bin_, 14:56:38)
    12. Morgan will send email in a few days to initiate the discussion (bin_, 14:59:33)

  4. AOB (bin_, 14:59:38)
    1. Because of Thanksgiving Holiday in US on next Thursday, all agreed to cancel the meeting next Thursday Nov 24. (bin_, 15:00:07)
    2. all agreed to re-convene the weekly technical discussion in 2 weeks on Dec 1. (bin_, 15:00:32)
    3. there will be OPNFV Bay Area User Meetup tomorrow Friday hosted by Huawei. All in Bay Area are encouraged to participate in person (bin_, 15:01:21)
    4. please RSVP first for logistic purpose (bin_, 15:02:07)
    5. https://www.opnfv.org/news-faq/events/2016-11-18/opnfv-bay-area-user-group-meetup (bin_, 15:02:11)
    6. Meeting adjourned (bin_, 15:02:22)


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

Action items

  1. (none)


People present (lines said)

  1. bin_ (64)
  2. hongbo1 (3)
  3. collabot` (3)
  4. cgoncalves (1)
  5. rprakash (1)
  6. morgan_orange (1)
  7. ljlamers (1)


Generated by MeetBot 0.1.4.