b502502f2f
Implement cross pod l3 networking functionality. In this first patch, we finish the logic to prepare related resources when user issues router-interface-add request, including bottom router, bottom network, bridge network, etc. In the first step, we only consider the scenario that networks do not cross pods. Each tenant has a cross-pods VLAN network (the bridge network mentioned above) to connect different tenant networks in different pods and we use extra routes to route packets between pods. We ultilize the AZ hint attribute of network to figure out which pod the network belongs to, so we do not need to wait for the creation of the first VM to know which pod to create the bottom network. The configuration of extra routes will be implemented in the second patch. Change-Id: Ia455812732bc825c9367df0e2c4e23c512d8f401 |
||
---|---|---|
.. | ||
functional | ||
unit | ||
__init__.py | ||
base.py |