Comment 6 for bug 1664466

@Boden, @Armando,

Per our discussion at Atlanta PTG, the provider:network_type is associated provider_net, and not the tenant networks. In other words, this attribute is supported only from the admin mode.

See here all the attributes associated with network - https://github.com/openstack/neutron-lib/blob/master/neutron_lib/api/definitions/network.py#L33

And, here to see how provider:network_type is used/specified- https://github.com/openstack/neutron-lib/blob/master/neutron_lib/api/definitions/provider_net.py#L62

Just for the fun, I tried creating a network with network_type as a tenant and it was rejected. However, when I create it as an admin, I can do it....

So, the bottom line is this only available for provider networks.

If we can make this available as a general attribute of the network, that would be great - and, that is what this RFE is all about.

As to the examples (or use cases), I provided few examples earlier, another one brought up in the Gluon meeting was MPLS/GRE - hope this answers your question.

On an orthogonal note/topic, there seems to be some confusion about the the ML2 type driver being able to specify the network type - that is really not true. ML2 type drivers specify the segmentation type for the segments or a network, and a network can have multiple segments.
For example a neutron network can have three segments like VLAN-VxLAN-VLAN.