This repository has been archived by the owner on Sep 26, 2019. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[aim_mapping] Per-l3p implicit contracts
The implicit AIM contracts were being earlier created per tenant (lazily created when the first l2p is created) and used by the default_epg and all other epgs created by a consequence of the user actions. As we move towards a model of supporting multiple l3ps in the same AIM VRF, we will need per-l3p contracts to enforce isolation between l3ps. This patch is the first step in that direction where the per-tenant implicit contracts are now created per-l3p. Contracts are created when l3p is created and deleted when l3p is deleted. This patch also fixes the problem of implicit contracts being not cleaned up when the last two l2ps in a tenant were being deleted concurrently. Existing AIM deployments might need to be migrated to this new model. Migration strategies would differ per deployment but might at least require running a script that creates the implicit contracts per existing l3ps. Change-Id: I7f18c672db5ffcec9ce445bc1a32d508a685c9c6
- Loading branch information
Showing
3 changed files
with
209 additions
and
213 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Oops, something went wrong.