13:00:20 <bh526r> #startmeeting Weekly Technical Discussion 13:00:20 <collabot> Meeting started Thu Aug 30 13:00:20 2018 UTC. The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:20 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic. 13:00:20 <collabot> The meeting name has been set to 'weekly_technical_discussion' 13:02:03 <bh526r> #topic Roll Call 13:02:09 <bh526r> #info Bin Hu 13:04:29 <bh526r> #info Srini Addepalli (Intel) 13:04:52 <bh526r> #info Tina Tsou (ARM) 13:05:02 <bh526r> #info Tapio Tallgren (Nokia) 13:05:22 <bh526r> #info Trinath Somanchi 13:05:38 <bh526r> #info Ryota Mibu 13:06:53 <bh526r> #info David McBride 13:07:36 <bh526r> #topic OVN4NFV Support of K8S by Srini and Trinath 13:08:29 <bh526r> #info Srini started with describing how ONAP supports K8S-based remote regions 13:11:31 <bh526r> #info and the scope of current K8S Plugin work in ONAP 13:13:26 <bh526r> #info Then OVN background was introduced 13:22:07 <bh526r> #info proposal is to develop a new plugin in OVN to support both networking workloads and normal application workloads 13:22:34 <bh526r> #info OPNFV OVN4NFV Project is the right place to develop this new plugin 13:23:14 <bh526r> #info create a PoC and make sure it works with ONAP 13:24:10 <bh526r> #info Then finally upstream it to OVN community either as a new plugin or as part of the existing plugin 13:24:59 <bh526r> #info David McBride asked who said it should not be part of OPNFV 13:25:33 <bh526r> #info Srini got the feeling when communicating with some projects, maybe the feeling is not correct 13:27:16 <bh526r> #info David further asked why not in OVN instead of OPNFV 13:29:33 <bh526r> #info 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 13:30:45 <bh526r> #info Srini further explained that it is a good approach to start with PoC in OPNFV, and the goal is to upstream to OVN eventually 13:31:05 <bh526r> #info Tapio also agreed that the goal is to upstream 13:31:56 <bh526r> #info Tapio further asked if OVN is more stable than OVS 13:32:22 <bh526r> #info Srini said what he heard is pretty well 13:32:44 <bh526r> #info David asked if there is timeline of upstreaming it 13:33:42 <bh526r> #info Srini shared that the plan is to start the upstreaming it in the middle of next year 13:34:08 <bh526r> #info There has been technical discussion with OVN community, but not the upstream plan 13:34:46 <bh526r> #info David suggested that it is better to communicate with them regarding the upstream plan 13:35:13 <bh526r> #info Srini agreed to communicate 13:35:57 <bh526r> #info David suggested to document this work in the project, and future release plan 13:36:23 <bh526r> #info e.g. align with Hunter release 13:36:51 <bh526r> #info Trinath agreed, and also CI/CD details 13:37:32 <bh526r> #info David suggested to communicate with Infra WG (Trevor B) 13:38:48 <bh526r> #info and also installer project 13:41:12 <bh526r> #info and helpdesk for repo 13:45:48 <bh526r> #info As a summary: 13:46:51 <bh526r> #info (1) All agreed that this new plugin K8SOVN4NFV will be one of the work item within the scope of OVN4NFV project 13:47:12 <bh526r> (2) Trinath will document it in wiki and any other places of documentation as necessary 13:48:31 <bh526r> #info (2) Trinath will document it in wiki and any other places of documentation as necessary 13:49:02 <bh526r> #info (3) Trinath will upload the presentation to OVN4NFV wiki page 13:49:36 <bh526r> #info (4) Trinath will put this new plugin as deliverables in future release plan starting from Hunter release 13:50:29 <bh526r> #info (5) Trinath and Srini will execute the implementation of this new plugin development work, including: 13:51:19 <bh526r> #info (5.1) communicate and work with Infra WG (Trevor B) for necessary needs in CI/CD pipeline 13:52:26 <bh526r> #info (5.2) communicate and work with Installer projects, e.g. Apex (Tim R.) for necessary support of integrating new scenarios in installers 13:52:56 <bh526r> #info (5.3) communicate and work with Help Desk (Aric G.) for creating new repo 13:53:59 <bh526r> #info (5.4) and any other tasks and steps in executing the new plugin and achieving deliverables (BAU) 13:54:22 <bh526r> #topic AOB 13:54:28 <bh526r> #info None 13:54:33 <bh526r> #info Meeting adjourned 13:54:37 <bh526r> #endmeeting