Ask Your Question

Revision history [back]

Neutron is the OpenStack component that manages virtual networks. There are many ways of mapping virtual networks to your physical infrastructure. You opted for OVN as the so-called mechanism driver, the method by which instances are attached to the network. This driver does not support the Neutron Load Balancer, VPN and Firewall as a Service features.

Furthermore, the so-called type driver, which ensures that virtual networks are separated from each other, is Geneve.

Since OpenStack Stein, Packstack uses OVN and Geneve by default. In principle, this should only be a problem if you plan to deploy LBaaS, VPNaaS or FWaaS. However, to me this new setup caused other headaches, which I fixed by configuring the old Openvswitch and VXLAN drivers.

Neutron is the OpenStack component that manages virtual networks. There are many ways of mapping virtual networks to your physical infrastructure. You opted for Since OpenStack Stein, Packstack uses OVN as the so-called mechanism driver, driver by default. This is the method by which instances are attached to the network. This driver does not support the Neutron Load Balancer, VPN and Firewall as a Service features.

Furthermore, the so-called Packstack's default type driver, driver, which ensures that virtual networks are separated from each other, is us Geneve.

Since OpenStack Stein, Packstack uses OVN and Geneve by default. In principle, this should only be a problem if you plan to deploy LBaaS, VPNaaS or FWaaS. However, to me this new setup caused me other headaches, which I fixed by configuring the old Openvswitch mechanism driver and VXLAN driverstype driver.

Neutron is the OpenStack component that manages virtual networks. There are many ways of mapping virtual networks to your physical infrastructure. Since OpenStack Stein, Packstack uses OVN as the so-called mechanism driver by default. This is the method by which instances are attached to the network. This driver does not support the Neutron Load Balancer, VPN Balancer, VPN and Firewall as a Service Service features.

Furthermore, Packstack's default type driver, which ensures that virtual networks are separated from each other, us Geneve.

In principle, this should only be a problem if you plan to deploy LBaaS, VPNaaS or FWaaS. However, this new setup caused me other headaches, which I fixed by configuring the old Openvswitch mechanism driver and VXLAN type driver.