[Openstack] [Networking] Single L3 composed of multiple distinct L2 segments

Joe Harrison joehazzers at gmail.com
Tue Jul 15 14:35:10 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Everyone,

I have raised this topic before (to little avail), but it seems with
the existence of the multi-provider extension in Neutron and the
upcoming scalability improvements in the K release along with the
migration script(s), I might wish to move to Neutron from Nova-Network
quite soon.

The issue is that I have a network in which only certain IP subnets
are available to certain compute nodes.

Say for example Rack A only has access to 192.168.0.0/24 whilst Rack B
only has access to 192.168.1.0/24. It would be useless (if not
frustrating to the user) to have an instance scheduled, receive a port
only to find that the instance was scheduled on a compute node
somewhere in Rack A, but the port assigned to it has an IP address in
the subnet 192.168.1.0/24.

With the multi-provider networks, is it possible to create an L3
segment composed of multiple L2 segments, or is such functionality
possible otherwise?

I can foresee some sort of mapping of subnets on agents much in the
same way as physical network mappings on those machines, or some sort
of "meta network" whereby a single network can be composed of multiple
other networks.

The issue is that I have multiple racks in different subnets, and
VLANs (currently) can't be exposed to the compute nodes, and even if
they were I'd have the headache of again restricting subnets to
specific segments.

Is anyone running such a system with Neutron in a production
environment (I'm running such a system with Nova-Network), or is there
an actual use case for this, and if so what is the best approach?


Thanks,
Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTxTweAAoJEHYEICnOV08jZIgQAOQbkCSWj1jvIj+NMIopEs/s
itDG6QeY18NQky5mAiFr9ejPUtQVKovQmDyvA1NpwtKqRcBBM87znWg5UnWO2nwG
19JQjfrjhOHaQiNqcrYZdcIFSxqcxL9K9dkQcp1FIyMxWuCTEgHtrQ9/reYodoeW
ABBxfp5Vo1oF+ib7fHJo9pCw83wCE/gpsjzcfNeAirvjBjM0JZSrf+IJXL7bn5Gp
bmYMnVvFLaR7kkCoQk5vuVOf1+f17DERyKHzQ38JkUUM/BYg6rfavDDzeXi9eKl2
piOE4A2QSrIUeN4HpOkCp1mHYvkIqsOzaWRluJ6eKZRchFkKioTCcxLbznoK5RIm
X6tq+cPLMHNxUQ6b5JDWOKpbTbsmOgRFQn6XsHIFxFg5/+k5I8B1vV2mmECAZhgl
1bGf8ec6igUYKYqyNVP/b/XoccryTOr4b/i5UeDSRLq0hC9Kxa/jwBAvcZ181iMk
/AwHA5iaI6BFVS5WzE4G570ZVEZezVAQC7ah7Za5OWUXqgGR5a3yr6UdG1tIWyNw
1Exl/FcvQY5PvPxhV2bK6feR/369E4lcG7MKiBkpEl/KKVt+a5JEIAHECOOEqnzX
mt8CW9pLUkolNfdBZl3u130Y77OA74RR9EAgV42zZmKWA2r4GnWTu5wn8v2VAOzG
FDLf+j92m6zUalcIG3sq
=U88f
-----END PGP SIGNATURE-----




More information about the Openstack mailing list