#opnfv-meeting: Weekly Technical Discussion

Meeting started by bh526r at 13:00:20 UTC (full logs).

Meeting summary

  1. Roll Call (bh526r, 13:02:03)
    1. Bin Hu (bh526r, 13:02:09)
    2. Srini Addepalli (Intel) (bh526r, 13:04:29)
    3. Tina Tsou (ARM) (bh526r, 13:04:52)
    4. Tapio Tallgren (Nokia) (bh526r, 13:05:02)
    5. Trinath Somanchi (bh526r, 13:05:22)
    6. Ryota Mibu (bh526r, 13:05:38)
    7. David McBride (bh526r, 13:06:53)

  2. OVN4NFV Support of K8S by Srini and Trinath (bh526r, 13:07:36)
    1. Srini started with describing how ONAP supports K8S-based remote regions (bh526r, 13:08:29)
    2. and the scope of current K8S Plugin work in ONAP (bh526r, 13:11:31)
    3. Then OVN background was introduced (bh526r, 13:13:26)
    4. proposal is to develop a new plugin in OVN to support both networking workloads and normal application workloads (bh526r, 13:22:07)
    5. OPNFV OVN4NFV Project is the right place to develop this new plugin (bh526r, 13:22:34)
    6. create a PoC and make sure it works with ONAP (bh526r, 13:23:14)
    7. Then finally upstream it to OVN community either as a new plugin or as part of the existing plugin (bh526r, 13:24:10)
    8. David McBride asked who said it should not be part of OPNFV (bh526r, 13:24:59)
    9. Srini got the feeling when communicating with some projects, maybe the feeling is not correct (bh526r, 13:25:33)
    10. David further asked why not in OVN instead of OPNFV (bh526r, 13:27:16)
    11. Trinath said that OVN is more focused on enterprise now. This proposed new plugin K8SOVN4NFV is just for NFV workloads. OVN4NFV is a better place, because it is OPNFV is one of the best community for NFV, and OVN4NFV already works on addressing NFV needs using OVN (bh526r, 13:29:33)
    12. Srini further explained that it is a good approach to start with PoC in OPNFV, and the goal is to upstream to OVN eventually (bh526r, 13:30:45)
    13. Tapio also agreed that the goal is to upstream (bh526r, 13:31:05)
    14. Tapio further asked if OVN is more stable than OVS (bh526r, 13:31:56)
    15. Srini said what he heard is pretty well (bh526r, 13:32:22)
    16. David asked if there is timeline of upstreaming it (bh526r, 13:32:44)
    17. Srini shared that the plan is to start the upstreaming it in the middle of next year (bh526r, 13:33:42)
    18. There has been technical discussion with OVN community, but not the upstream plan (bh526r, 13:34:08)
    19. David suggested that it is better to communicate with them regarding the upstream plan (bh526r, 13:34:46)
    20. Srini agreed to communicate (bh526r, 13:35:13)
    21. David suggested to document this work in the project, and future release plan (bh526r, 13:35:57)
    22. e.g. align with Hunter release (bh526r, 13:36:23)
    23. Trinath agreed, and also CI/CD details (bh526r, 13:36:51)
    24. David suggested to communicate with Infra WG (Trevor B) (bh526r, 13:37:32)
    25. and also installer project (bh526r, 13:38:48)
    26. and helpdesk for repo (bh526r, 13:41:12)
    27. As a summary: (bh526r, 13:45:48)
    28. (1) All agreed that this new plugin K8SOVN4NFV will be one of the work item within the scope of OVN4NFV project (bh526r, 13:46:51)
    29. (2) Trinath will document it in wiki and any other places of documentation as necessary (bh526r, 13:48:31)
    30. (3) Trinath will upload the presentation to OVN4NFV wiki page (bh526r, 13:49:02)
    31. (4) Trinath will put this new plugin as deliverables in future release plan starting from Hunter release (bh526r, 13:49:36)
    32. (5) Trinath and Srini will execute the implementation of this new plugin development work, including: (bh526r, 13:50:29)
    33. (5.1) communicate and work with Infra WG (Trevor B) for necessary needs in CI/CD pipeline (bh526r, 13:51:19)
    34. (5.2) communicate and work with Installer projects, e.g. Apex (Tim R.) for necessary support of integrating new scenarios in installers (bh526r, 13:52:26)
    35. (5.3) communicate and work with Help Desk (Aric G.) for creating new repo (bh526r, 13:52:56)
    36. (5.4) and any other tasks and steps in executing the new plugin and achieving deliverables (BAU) (bh526r, 13:53:59)

  3. AOB (bh526r, 13:54:22)
    1. None (bh526r, 13:54:28)
    2. Meeting adjourned (bh526r, 13:54:33)


Meeting ended at 13:54:37 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. bh526r (51)
  2. collabot (3)


Generated by MeetBot 0.1.4.