e87e080281
1. What is the problem? VLAN network has some restrictions that VxLAN network doesn't have. For more flexible networking deployment, we consider supporting cross-pod VxLAN network. We are going to use shadow agent/port mechanism to synchronize VTEP information and make cross-pod VxLAN networking available, as discussed in the specification document[1]. In part1[2], we have added the necessary logic to retrieve agent info from local Neutron and save it in the shadow agent table in central Neutron. Now we need to utilize this info to create shadow agent and shadow port. 2. What is the solution to the problem? An asynchronous job triggered when instance port is updated to active is added. It calculates needed shadow ports and then create them in the target pod. 3. What the features need to be implemented to the Tricircle to realize the solution? This is the second patch for cross-pod VxLAN networking support, which introduces the following changes: (1) A new asynchronous job setup_shadow_ports is added. Each asynchronous job only handles the shadow ports setup in one given pod for one given network. If shadow ports in other pod also needs to be updated, the job registers one new job for each pod. [1] https://review.openstack.org/#/c/429155/ [2] https://review.openstack.org/#/c/425128/ Change-Id: I9481016b54feb57aacd03688de882b8912a78018 |
||
|---|---|---|
| .. | ||
| api | ||
| cmd | ||
| common | ||
| db | ||
| network | ||
| tempestplugin | ||
| tests | ||
| xjob | ||
| __init__.py | ||