Hi Giuseppe, >Bruno, >VxLAN is an overlay solution as well, it uses UDP for transporting L2 >frames, so it is not required to have a VxLAN compatible switch. My >suggestion is to use the default configuration. >@Spain node: can you confirm that VxLAN can be used? I don't see any issue >on that. We had network issues using vxlan and, also, the documentation explicitly says that vxlan must be supported by the network equipment, as shown below. ---"By default VXLAN tunnels will be used (can be changed to GRE via Fuel CLI). The networking equipment must support VXLAN segmentation. This option supports millions of tenant data networks." >If you want to use GRE you have 2 possibilities: >1) Use the FUEL CLI >https://docs.mirantis.com/openstack/fuel/fuel-7.0/user-guide.html#using-fuel-cli >* e.g., >fuel env create --name MyEnv --release 2 --mode ha --network-mode neutron >--net-segment-type gre Thanks for the pointers, we tried to set the network-segment-type in an already existing environment and it did not work. We will try this. >2) Enabling GRE on /etc/neutron/plugin.ini after the OpenStack deployment. >e.g., >------------------------------------------------ >[ml2] >type_drivers = local,flat,vlan,gre >tenant_network_types = flat,vlan,gre >mechanism_drivers =openvswitch >[agent] >l2_population=False >polling_interval=2 >arp_responder=False >dont_fragment=False >tunnel_types=gre >----------------------------------------------- >Regards, >Giuseppe BR, Bruno.
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy