chore: Enable understack_vni plugin to assign evpn_vni attribute of dynamic VRF routers#2138
Open
stevekeay wants to merge 4 commits into
Open
chore: Enable understack_vni plugin to assign evpn_vni attribute of dynamic VRF routers#2138stevekeay wants to merge 4 commits into
stevekeay wants to merge 4 commits into
Conversation
stevekeay
force-pushed
the
vrf-router-evpn-vni
branch
from
4c0a20e to
8b9a3eb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This addresses some of the review comments from #2109.
This requires the configuration added by https://github.com/RSS-Engineering/undercloud-deploy/pull/1953
It switches over from the upstream evpn driver to our newly implemented understack_vni driver.
The old neutron code is left in place because it included one-way database migrations that have been applied already, so removing/reverting would likely break all future database migrations until we manually fix up the schema and metadata.