Description of problem: When configuring networking for routed spine/leaf deployments, router interfaces are required for every VLAN delivered to the bare metal hosts. This can be time-consuming and error-prone if done by hand, and must be done correctly on all switches prior to deployment. Invalid configuration can cause deployments to fail in difficult-to-troubleshoot ways. It would be fantastic if we could automate this process and configure L3 interfaces on VLANs when they are created on the switch. Version-Release number of selected component (if applicable): Rocky Actual results: There is currently no way to automatically configure hardware router interfaces via Ansible, but we have that data in the configuration data for every VLAN/subnet. Expected results: In order to implement this within the Neutron plugin architecture, there will need to be a configuration flag for Neutron routers that configures the router on an external hardware device. When a network subnet is created in Neutron, we should be able to define that the router for the subnet should be configured on the switch. Additional info: We may need a new option in Neutron, it isn't clear if there is already a way to flag a router as existing externally. There is currently a --distributed or --centralized, but there isn't an apparent way to tag a router for creation externally. It's also possible that there is some way to drive this via the gateway address in the subnet table rather than the neutron router table, if Neutron router objects are only intended to be used for internal L3 agent/OVN/etc. routers. Additionally, there may be a need to configure subnet host routes on the L3 router.
Removing release flag, this has not been discussed or planned in anyway on the development side.
networking-ansible no longer supported closing wontfix Should the situation change, please discuss with PM for reconsideration