# Pastebin TyPtD0Kb
A couple of cabs of gear that are controlled by Ironic (indirectly by Neutron and Nova). “openstack network create” calls our custom ML2 plugin which pokes Nautobot to create the VNI. When a server is created in nova, the physical port is attached to the local VLAN which maps to the provisioning VNI. There’s no ability to select the port via Nova (known limitation). To get the correct physical port selected since we’re using VXLAN needed to create our own custom VXLAN type driver which brought the functionality in the VLAN type driver that networking-generic-switch uses. From here everything seems to work. We’ve even used the trunk plugin for neutron and created the ports as trunks and attached multiple networks to the physical machines. This requires you to tag the traffic correctly from your server. Provisioning this network information does not work (it doesn’t even work for nova/kvm and I’ve made a ticket about this). We’ve further created our own L3 router plugin, this has required us to disable or copy and paste some of the other neutron plugins because they have hardcoded load dependencies on either “ovn” or the default l3 plugin. This custom L3 router plugin is mostly a stub but we intend on having it to regular Neutron Routers as a basic case but then using the “service provider” plugin interface to register “network flavors” of L3_ROUTER_NAT to create virtual appliances of Palo Altos and the such which can than be consumed by FWaaS.