fuel-dev team mailing list archive

[Andrew Woodward <xarses@xxxxxxxxx>]

Vladimir,

The bp is
https://blueprints.launchpad.net/fuel/+spec/multiple-cluster-networks Ryan
created it a couple of days ago. We will work on getting some diagrams
together to help visualize. The short of it is that because customer want's
to use separate network segments between racks, cages or what ever is their
fancy (contained hopefully by near proximity in the same facility). This
type of network topology is usually referred to as spine and leaf and has
become more common in larger datacenters as it minimizes L2 domains and
increases bandwidth throughput and L3 self healing which is not as easily
possible in a large L2 domain. Because customer requires to deploy this
way, fuel would need support storing and processing many sets of the
networks we would normally deploy (fuelweb_admin, public, management,
storage). In our BP we actually propose moving the networks away from being
bound directly to the clusters and instead, we bind them to the node
(calling them Node Groups). This doubles as a method that in the case the
customer wants to place nodes in multiple clusters that belong to the same
Node Group, they would only have to define the Node Group once.

We have a working beta in our forked branches:
https://github.com/xarses/fuel-web
https://github.com/xarses/fuel-library

Setup of a lab env is a bit tricky and I will work to make fuel-master be
able to make it automatically.

As to the thread's original question, we solved the problem by creating
rule based routes for each interface to return traffic in
https://github.com/xarses/fuel-library/commit/ef70dafae8fa8096526691910a2e1cf148d58bf1