Thanks Michal. Yes, my scenario is same which you mentioned. But I don't want to use COE atm. So. the OVS and neutron-agent running inside the VM will be communicating with compute node neutron agent? Thanks & Regards, Vikrant Aggarwal On Fri, Nov 30, 2018 at 9:31 PM Michał Dulko <mdulko@redhat.com> wrote:
On Fri, 2018-11-30 at 09:38 +0530, Vikrant Aggarwal wrote:
Hello Team,
I have seen the steps of starting the kuryr libnetwork container on compute node. But If I need to run the same container inside the VM running on compute node, is't possible to do that?
I am not sure how can I map the /var/run/openvswitch inside the nested VM because this is present on compute node.
I think that if you want to run Neutron-networked Docker containers on an OpenStack VM, you'll need OpenvSwitch and neutron-agent installed on that VM as well.
A better-suited approach would be to run K8s on OpenStack and use kuryr-kubernetes instead. That way Neutron subports are used to network pods. We have such a K8s-on-VM use case described in the docs [1].
[1] https://docs.openstack.org/kuryr-kubernetes/latest/installation/devstack/nes...
https://docs.openstack.org/kuryr-libnetwork/latest/readme.html
Thanks & Regards, Vikrant Aggarwal