On Sun, 2018-12-02 at 09:33 +0530, Vikrant Aggarwal wrote:

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?

I've did some more research and seems like nested deployments actually got implemented in kuryr-libnetwork around 3 years ago. I don't know if that still works though. Also there seem to be no documentation, so unfortunately you'll need to figure it out by reading the code. See blueprint [1] for a list of related patches. Remember that this requires the cloud to support subports and trunk ports in Neutron. VMs get the trunk ports attached and the containers get the subports. This doesn't require neutron-agent running on the VMs. [1] https://blueprints.launchpad.net/kuryr/+spec/containers-in-instances

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