Install networking-ansible in the Triple-o Undercloud to do an overcloud deployment.
Currently the undercloud expects that the underlay network for the overcloud is pre-configured by networking administrators. This is a day 1 deployment feature using the functionality in networking-ansible to deploy the network topology for the overcloud's underlay network. This could configure this topology at deploy time by the undercloud instead of preconfigured by networking administrators. Networking-ansible would configure the physical ports the overcloud nodes are connected to assigning the appropriate VLANs for the overcloud's ctlplane/api/storage/etc networks. Initial thought was to do this by loading the topology into Neutron using trunk port designations and letting Neutron do the configuration as the nodes are being provisioned. Alternatively there has been discussion around creating a networking-ansible API interface that could be invoked to do the same configuration but independent of neutron.
networking-ansible is on hold as no customers have adopted the feature. all jobs are disabled. we can re-enable QE jobs and future dev work should the state of the customer changes.