Hi Eduardo,
No, they were not created by default I had to follow the workaround only
then they are getting created
I'm just bringing to your notice that the issue is still there because they
are not present after the deployment :)
Now even after the tunnels are created VM's are not getting the
Hi Goutham,
VXLAN tunnels are created between network/compute hosts in expected
interface (ens3):
df_default="true", in_key=flow, local_ip="192.168.122.215",
out_key=flow, remote_ip="192.168.122.177"
Where is exactly failing? Instances not get IP, DHCP does not work,
vm-to-vm traffic issues,
Hi Eduardo,
I am trying to deploy self-service network topology.
I think then I shouldn't be bothered about the `ens8` because I'm not
dealing with provider networks
and attached are the outputs requested...
Ps: Controller and the network node are both same in my setup.
Thanks in advance
Hi,
In kolla,VXLAN tunnels are connfigured in ``tunnel_interface`` variable
which defaults to ``network_interface``, ``neutron_external_interface`` is
used for public floating IPs in neutron.
Please share your globals.yml, ``ip a`` output in compute/network hosts and
``ovs-vsctl show`` from
i guess you didn't enabled one of following[0]
enable_neutron_dvr: yes
enable_neutron_provider_networks: yes
I hit this recently. i am thinking we should remove this or make
enable_neutron_provider_network=yes in default.
[0]