<div dir="ltr">This explanation doesn't line up with what I understood from the above two sources. Infact, according to the sources, it addresses the problem of choice<br><div>for the end user if there are multiple provider networks. My question is specifically about this point. How does routed provider networks address this</div><div>choice issue for the user, since it is presented as one single L3 layer, how does the user choose if he wants to choose one particular L2 provider network ?</div><div><br></div><div>Hope you got my question. </div></div><br>On Friday, July 30, 2021, Sean Mooney <<a href="mailto:smooney@redhat.com" target="_blank">smooney@redhat.com</a>> wrote:<br>> On Thu, 2021-07-29 at 22:45 +0530, Gk Gk wrote:<br>>> Hi,<br>>><br>>> I learnt that routed provider networks from the below links:<br>>><br>>> <a href="https://docs.openstack.org/neutron/latest/admin/config-routed-networks.html" target="_blank">https://docs.openstack.org/neutron/latest/admin/config-routed-networks.html</a><br>>> <a href="https://www.youtube.com/watch?v=HwQFmzXdqZM" target="_blank">https://www.youtube.com/watch?v=HwQFmzXdqZM</a><br>>><br>>> This concept, according to them solves two issues:<br>>><br>>> 1. Large broadcast L2 domains with failure domains<br>>><br>>> 2. If there are multiple L2 provider networks, users are confused, unable<br>>> to choose a particular network.<br>>><br>>> My question is, how does routed provider networks solve the second problem<br>>> mentioned above ?<br>>><br>> it does not really what it does is force providers to create network that the normaly users just use<br>> it moves away form the idea of self service tenant network to provider or operator created networks.<br>><br>>>  If one user wants to use external network for internet,<br>>> how can he choose from this one single routed provider network ?<br>>><br>> if the deploymen is using routed networks all netwosk shoudl provide external internet connectivy as you should be routign to<br>> the out side in your datacenter infractufrue.<br>>>  Or, if<br>>> another user wants another provider network, how can he choose that<br>>> particular network ?<br>><br>> they user will see a precreted list of networks that you created and marked as shared in teh env.<br>> they then choose form that list.<br>><br>> this feature is really for the use case where the tenant is also the person that runs the cloud or has a very close<br>> relation ship like two teams in the same company wehre by they can get a view into the underlying host toplogy.<br>>><br>>> Also the same can also be achieved by creating nova aggregates or<br>>> availability zones and<br>>> mapping computes with particular provider network connections and ask<br>>> users to use that particular nova AZ, without creating routed provider<br>>> networks at all ?<br>><br>> you can get a simialr affect by creatign small AZ although you dont really map those to provider network the same way.<br>><br>> although you could aligh yoru physnet definitons to yoru AZ bondaryies if you want e.g. name it physnet_az_1 and physnet_az_2 ectra.<br>> that however does nto really help since the user cannot articalte the phynet mapping sicne they wotn know you have done that.<br>><br>> if you want to supprot self service networks with l3 routeing instead of routed provider networks whant you really want is<br>> callico. <a href="https://docs.projectcalico.org/getting-started/openstack/overview" target="_blank">https://docs.projectcalico.org/getting-started/openstack/overview</a><br>><br>> this will replace the use of ovs or linux bridge as the networkign backend with calico which will provide l3 conenctivity to teants<br>> using bgp. this will reuslt in an networkign architcxture that is similar to that used in kubernetess but with more power over things liek<br>> haveign multiple prots on the same vm and other things not supprot by a k8s pod spec and the cni interface.<br>><br>>><br>>> Can someone clarify this for me ?<br>>><br>>><br>>> Thanks<br>>> Kumar<br>><br>><br>>