*** hitalia has quit IRC | 01:35 | |
*** armax has quit IRC | 04:44 | |
*** fzdarsky has joined #openstack-neutron-ovn | 08:19 | |
*** armax has joined #openstack-neutron-ovn | 14:57 | |
*** shettyg has joined #openstack-neutron-ovn | 15:11 | |
*** russellb is now known as rustlebee | 15:42 | |
*** fzdarsky has quit IRC | 15:52 | |
*** hitalia has joined #openstack-neutron-ovn | 16:58 | |
*** armax has quit IRC | 17:00 | |
*** armax has joined #openstack-neutron-ovn | 18:25 | |
openstackgerrit | Russell Bryant proposed stackforge/networking-ovn: devstack: Add pre_test_hook.sh. https://review.openstack.org/186894 | 19:55 |
---|---|---|
shettyg | Has anyone thought about OVN + OpenStack + Kubernetes integration? I have spent some time and have some very basic ideas which adds services + pods (bot no load-balancer) and if anyone else is working on it, I am happy to bounce ideas. | 19:56 |
openstackgerrit | Russell Bryant proposed stackforge/networking-ovn: devstack: Add license header to plugin.sh https://review.openstack.org/186895 | 19:57 |
rustlebee | shettyg: i have thought about it from a high level, in that it's something I definitely think we should do :-) | 19:57 |
rustlebee | but haven't spent any time on it | 19:57 |
shettyg | rustlebee: I am building my thinking on top of the the design doc here: https://github.com/openvswitch/ovs/blob/ovn/ovn/CONTAINERS.OpenStack.md | 20:01 |
rustlebee | ok, great | 20:01 |
shettyg | So I am mostly thinking around Kubernetes master spawning containers in other VMs (and not hypervisors) | 20:01 |
rustlebee | +1 | 20:01 |
rustlebee | i think that's a super common use case | 20:01 |
rustlebee | I got asked if were looking at adding support for this stuff in Kubernetes last week | 20:02 |
rustlebee | OpenStack Magnum project people very interested | 20:02 |
rustlebee | i was thinking it pretty much means having Kubernetes optionally use the Neutron API to set up its networks | 20:02 |
shettyg | Yeah. I hear about Magnum project. But I don't really know what their thought process is. | 20:02 |
shettyg | Yes, I am also thinking arounf Kubernetes using Neutron networks. | 20:03 |
rustlebee | in short, think an openstack API wrapper to deploy kubernetes for you | 20:03 |
* rustlebee shrugs | 20:03 | |
rustlebee | not fully convinced ... unclear if hype is because of real value, or just "OMG containers" | 20:04 |
*** openstack has joined #openstack-neutron-ovn | 20:04 | |
shettyg | I see. Looks like we are a little divergent here. I was thinking of starting with a bunch of VMs spawned by Nova (using Neutron-OVN). The tenant installs Kubernetes cluster on that VM. It can spawn pods. But IP addresses is provided by Neutron network. The advantage it provides is that security policy can applied by Neutron in the hypervisor. | 20:06 |
shettyg | The disadvantage is that we no longer use Kubernetes' load balancer | 20:06 |
openstackgerrit | Russell Bryant proposed stackforge/networking-ovn: devstack: Add pre_test_hook.sh. https://review.openstack.org/186894 | 20:07 |
rustlebee | hmm | 20:08 |
rustlebee | load balancer probably pretty important | 20:08 |
rustlebee | but sounds like a good place to start | 20:08 |
rustlebee | to start proving how this stuff can work | 20:08 |
rustlebee | i think the performacne benefits of this integrated networking stack will convince people it's worthwhile | 20:09 |
rustlebee | would be cool to show some performance numbers sometime | 20:09 |
*** openstack has joined #openstack-neutron-ovn | 20:29 | |
*** openstackgerrit has quit IRC | 20:59 | |
*** openstackgerrit has joined #openstack-neutron-ovn | 21:00 | |
*** ajo has quit IRC | 21:07 | |
*** openstack has joined #openstack-neutron-ovn | 21:31 | |
openstackgerrit | Russell Bryant proposed stackforge/networking-ovn: devstack: Add pre_test_hook.sh. https://review.openstack.org/186894 | 21:42 |
*** shettyg has quit IRC | 22:14 | |
*** armax has quit IRC | 22:28 | |
*** armax has joined #openstack-neutron-ovn | 22:29 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!