15:32:18 <trinaths> #startmeeting OVN4NFV Weekly Meeting
15:32:18 <collabot> Meeting started Tue Oct 16 15:32:18 2018 UTC.  The chair is trinaths. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:32:18 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:32:18 <collabot> The meeting name has been set to 'ovn4nfv_weekly_meeting'
15:35:07 <trinaths> #topic
15:35:39 <Amir_m> Hello Trinaths
15:36:16 <trinaths> #topic Agenda - https://wiki.opnfv.org/display/OV/Meeting+Agenda
15:36:24 <trinaths> Amir_m:  hi
15:36:30 <trinaths> Amir_m:  how are you doing ?
15:36:43 <Amir_m> I'm good, thank you
15:36:50 <Amir_m> What about you?
15:37:00 <trinaths> doing good
15:37:22 <trinaths> Sorry, unable to host meeting last week, I was travelling home
15:37:38 <Amir_m> No problem
15:37:40 <trinaths> Amir_m:  can you share the work progress if any ?
15:38:18 <Amir_m> As I told you, I was able to bring up a K8s cluster using vagrant
15:38:26 <trinaths> ok.
15:38:28 <Amir_m> The OVN is the network provider
15:38:33 <trinaths> ok
15:38:47 <trinaths> can you document the setup guide and packet path
15:39:05 <trinaths> did you try kubevirt or virtlet
15:39:21 <Amir_m> What do you mean by packet path
15:41:06 <trinaths> how the packet is driving in container environment.
15:41:38 <Amir_m> I'm here confused about using virtlet vs kubevirt. Do you have a preference? and why?
15:42:08 <trinaths> Amir_m: As per the setup you have now, we have OVN working with K8S based container cluster. right ?
15:42:16 <Amir_m> yes
15:43:10 <trinaths> Amir_m: KubeVirt is a virtual machine management add-on for Kubernetes providing control of VMs as Kubernetes Custom Resources. Virtlet, on the other hand is a CRI (Container Runtime Interface) implementation, which means that Kubernetes sees VMs in the same way it sees Docker containers.
15:43:51 <Amir_m> Trinaths: I understand the difference between kubevirt and virtlet
15:44:06 <Amir_m> I'm asking about any preference for our PoC?
15:44:48 <trinaths> Amir_m:  go with virtlet.
15:44:56 <Amir_m> okay, thank you
15:45:09 <trinaths> Amir_m:  i feel this can be more close how k8s treats containers.
15:45:21 <trinaths> Amir_m: Hope you have gone through - https://www.mirantis.com/blog/kubevirt-vs-virtlet-comparison-better/
15:45:24 <trinaths> #link https://www.mirantis.com/blog/kubevirt-vs-virtlet-comparison-better/
15:45:32 <Amir_m> I did
15:46:00 <trinaths> Amir_m: nice.
15:46:26 <trinaths> do let me know one virtlet is working.
15:46:35 <Amir_m> I will
15:47:03 <trinaths> okay.
15:48:21 <trinaths> Once this is completed by our next weekly meeting we will discuss of APEX integration.
15:48:39 <Amir_m> okay
15:49:22 <Amir_m> you mean for the first PoC, right?
15:49:31 <trinaths> yes
15:49:53 <trinaths> both these need to be integrated with any of the installers Apex/Fuel/Compass
15:50:04 <Amir_m> yes
15:50:10 <trinaths> since Apex guys are helping us well, lets go with their installer.
15:51:03 <Amir_m> but non of the K8s scenarios in the previous release was ingerated with APEX
15:51:30 <trinaths> previous ?
15:51:43 <Amir_m> OPNFV release
15:51:55 <trinaths> Installer builds are not stable.
15:52:08 <Amir_m> ?
15:53:06 <trinaths> due the deadlines and other supporting team work constraints, the scenarios are being skipped.
15:53:21 <Amir_m> okay
15:53:29 <trinaths> we are working with RedHat team who are active in OVN and Apex development.
15:54:08 <Amir_m> Okay, once I'm successful with virtlet, will shoot you a note
15:54:09 <trinaths> so there is a more probability that Apex accepts our scenarios.
15:54:47 <trinaths> Amir_m:  yes, please. now with Intel contributing to OVN, you OVN_CN_VM PoC of greater importance for Redhat and Intel teams.
15:55:09 <trinaths> Intel team is on festival vacation.
15:56:22 <trinaths> Amir_m:  lets go with virtlet and complete our PoC. we have 2 more milestones to reach for completion of this internship.
15:56:49 <Amir_m> Trinaths: Okay
15:56:55 <trinaths> Amir_m: Do you want discuss anything more ? Else, we can conclude the meeting for today.
15:58:19 <Amir_m> Ttrinaths: Yes, I have an off topic question: how to relate the work being done with Network service mesh and the Intel K8s-ovn plugin?
15:58:44 <trinaths> Amir_m: can you more elaborate.
16:00:00 <Amir_m> The NSM are trying to introduce a service mesh of containerized network functions (CNFs), which accounts for the data plane network functions
16:00:33 <Amir_m> which includes the need for multiple interfaces/IPs, support SR-IOV, etc.
16:00:49 <trinaths> true, agree
16:01:10 <trinaths> Intel's initial effort for k8s integration is for Multi Cloud regions
16:01:31 <trinaths> #link https://wiki.onap.org/display/DW/Support+for+K8S+%28Kubernetes%29+based+Cloud+regions
16:03:06 <Amir_m> Trinaths: I think I was confused. I will need to read more to clear my confusion, Thank you
16:03:51 <trinaths> they have chosen OVN for its simplicity and distributed nature. where it fits efficiently at the Network Edge.
16:04:06 <trinaths> Intel's OVN discussions- https://wiki.onap.org/display/DW/OVN+integration+discussions
16:04:10 <trinaths> #link https://wiki.onap.org/display/DW/OVN+integration+discussions
16:05:05 <trinaths> their intention is also to empower the service mesh to support CNFs.
16:05:33 <trinaths> with OVN capabilities in Multi cloud scenarios (aka Edge scenarios within ONAP)
16:06:31 <Amir_m> Trinaths: One more question, in a real telco cloud (on-prem, public, hybrid, or multi, and edge), is the NFV placement, migration, and replication represents a challenge that yet to be addressed ?
16:06:48 <trinaths> Amir_m: yes.
16:07:05 <trinaths> Amir_m: I will give you an example which we recently discussed.
16:07:28 <trinaths> Amir_m:  can you check the mirantis link i shared for virtlet vs Kubevirt
16:07:45 <Amir_m> which type of NFV: control plane , management or data plane?
16:08:01 <Amir_m> trinaths: yes
16:08:03 <trinaths> all 3
16:08:33 <Amir_m> okay
16:08:43 <trinaths> telco's are not really focused into CNs. since they have first migrated to VMs and are really learning them.
16:09:01 <trinaths> though technology is fast growing adoption is slow.
16:09:31 <Amir_m> Trinaths: But I think they currently are considering this transitions to use CNs
16:09:58 <trinaths> In the tech-news, you can see orange telco collaborates with Erricsson .
16:10:11 <Amir_m> The resistance comes form vendors side, right?
16:10:12 <trinaths> telefonica collaborates with NeC
16:10:17 <trinaths> True.
16:10:46 <trinaths> if you see RedHat is selling its OpenShft platform for telcos
16:10:56 <trinaths> to move them to Container infra.
16:11:01 <Amir_m> yes I know
16:11:21 <trinaths> but still Container management/scale/migration are in incubation
16:11:33 <Amir_m> okay
16:12:01 <Amir_m> Trinaths: But which VNF type is more challenging ?
16:12:13 <trinaths> with VMs there is a certain saturation for management/scale/migration.
16:12:34 <trinaths> dataplane VNFs are more challenging.
16:12:45 <Amir_m> agree
16:13:09 <trinaths> the data plane requirements itself vary as per the demand and telco requirements.
16:13:34 <trinaths> the telco/SP's requirements are going to even more challenging for designing the VNFs.
16:13:56 <trinaths> they first intend to do in VMs and then move to MicroSvs with CNFs.
16:14:53 <Amir_m> and eventually, utilize the service mesh concepts, but at a lower level (L2-L3)
16:15:08 <trinaths> as you might know working inside mesh is quite more challenging.
16:15:17 <trinaths> the life of packet is miserable.
16:16:41 <Amir_m> Trinaths: Thanks a lot for sharing your thoughts on my off topic questions
16:16:41 <trinaths> also, service mesh is really interesting when ML on network is a requirement
16:17:01 <trinaths> Amir_m:  did I clear atleast some of your doubts ?
16:17:18 <Amir_m> Trinaths: Yes,  most of them, thank you
16:17:28 <trinaths> :) nice
16:17:47 <trinaths> Amir_m:  can you conclude this OVN-VM-CN task my next week meeting ?
16:17:58 <trinaths> we need to focus more on Apex integration/
16:18:00 <Amir_m> I will do my best
16:18:14 <trinaths> ok.
16:18:24 <trinaths> that's all from my end.
16:18:39 <Amir_m> Thank you
16:18:51 <trinaths> Amir_m:  please share you questions, mail too we can discuss them at any time. not only at meeting time
16:19:02 <Amir_m> Okay
16:19:28 <trinaths> nice,
16:19:37 <trinaths> lets continue the good work.
16:19:48 <trinaths> any more to discuss.
16:19:49 <trinaths> ?
16:20:13 <Amir_m> No, Thanks
16:20:17 <trinaths> #endmeeting