Flat openstack network
Good day, I have a question, how to configure neutron in openstack kolla, so as not to make a vrouter but to make a flat network and pass vlans to openstack and make a public network directly in openstack kolla. at the moment I have it on vrouter but it is not a good solution for me. and I would need to set up several networks in openstack Could someone suggest where to find it and how to set it up?
Hey Mateusz! If you have simple setup without Ironic, with ml2 deployed, basically you need to enable neutron provider networks: https://docs.openstack.org/kolla-ansible/latest/reference/networking/neutron... and configure those networks in neutron with --provider-network-type and --provider-physical-network arguments (or in Horizon via Admin panel). BR, Franek
On 4 Feb 2025, at 18:19, Mateusz Woźniakowski <matek7323@interia.pl> wrote:
Good day,
I have a question, how to configure neutron in openstack kolla, so as not to make a vrouter but to make a flat network and pass vlans to openstack and make a public network directly in openstack kolla. at the moment I have it on vrouter but it is not a good solution for me. and I would need to set up several networks in openstack Could someone suggest where to find it and how to set it up?
Hello, my globals.yml config looks like this workaround_ansible_issue_8743: yes kolla_base_distro: "ubuntu" openstack_release: "master" kolla_internal_vip_address: "192.168.1.250" neutron_plugin_agent: "openvswitch" enable_openstack_core: "yes" enable_hacluster: "yes" enable_haproxy: "yes" enable_cinder: "yes" enable_cinder_backup: "yes" enable_mariabackup: "yes" enable_masakari: "yes" ceph_cinder_user: "admin" ceph_cinder_pool_name: "os-rbd" ceph_cinder_backup_user: "admin" ceph_cinder_backup_pool_name: "os-rbd" cinder_cluster_name: ceph cinder_backend_ceph: "yes" cinder_backup_driver: "nfs" cinder_backup_share: "192.168.1.251:/mnt/OSBACKUP" cinder_backup_mount_options_nfs: "vers=4" enable_neutron_provider_networks: "yes" I am currently setting up a DEV environment of 3 controllers and 3 nodes. It will be a bit more in production. It currently works for me on a similar configuration, but I use vrouter and private class. I want to give up on this and have two options Some machines will have a public IP address right away, and some will not, but I want it in a different project so that they go through vrouter and have a private class. Do we just set it in globals or do we also have to dig into the neutron files?
Hello, I did another test and yes, The first configuration does not work openstack network create vps_network --share --enable --external --project CLOUD.VPS --provider-network-type flat --provider-physical-network physnet1 openstack subnet create vps_subnet --network vps_network --project CLOUD.VPS --subnet-range 192.168.250.0/24 --gateway 192.168.250.1 --ip-version 4 --allocation-pool start=192.168.250.210,end=192.168.250.220 --no-dhcp But it works fine openstack network create \ --no-share \ --enable \ --project admin \ --description "WAN - Wyjście na świat" \ --external \ --provider-network-type flat \ --provider-physical-network physnet1 \ METRO openstack subnet create \ --project admin \ --subnet-range 192.168.250.0/24 \ --no-dhcp \ --gateway 192.168.250.1 \ --ip-version 4 \ --network METRO \ --allocation-pool start=192.168.250.200,end=192.168.250.210 \ PublicIP openstack network create \ --no-share \ --enable \ --project CLOUD.VPS \ --description "Wewnętrzna sieć OpenStack" \ --internal \ vNet0 openstack subnet create \ --project CLOUD.VPS \ --subnet-range 10.200.0.0/16 \ --dhcp \ --gateway 10.200.255.254 \ --ip-version 4 \ --network vNet0 \ --allocation-pool start=10.200.0.1,end=10.200.255.253 \ PrivateIP openstack router create \ --enable \ --ha \ --project CLOUD.VPS \ --external-gateway METRO \ --enable-snat \ vRouter0 # Create vRouter openstack router add subnet vRouter0 PrivateIP # Create floating addresses for i in {210..220} do openstack floating ip create --project CLOUD.VPS --floating-ip-address 192.168.250.$i METRO; done Do you have any ideas or does anyone have any ideas what else might be wrong?
participants (2)
-
Franciszek Przewoźny
-
Mateusz Woźniakowski