The current HOS 2.0 Provider network configuration documentation assumes that the compute and controller nodes will be using separate physical network adapters rather than the default Bond0. See here.
This makes perfect sense in a production environment where you may need true network separation.
However, for dev and test environments it is also possible to simply ‘pipe’ (technical term) the provider vlan down the Bond0 interface as follows [assuming new provider vlan id is 999 and the default hos 2.0 sample configuration which uses physnet1]:
neutron net-create --provider:network_type vlan --provider:physical_network physnet1 --provider:segmentation_id 999 provnet999
When you login to Horizon now you will see the new provider network which you can configure with the necessary subnet details before it can be consumed by tenants – as long as they have access.