ipng/vppcfg
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Break into three sections

Browse Source
This commit is contained in:
Pim van Pelt
2022-03-23 17:16:29 +00:00
parent bcc4c8ff05
commit f37b80c012
1 changed files with 74 additions and 57 deletions
Download Patch File Download Diff File Expand all files Collapse all files

65
README.md
View File

@ -112,34 +112,47 @@ Fields:
## Reconsiling
The second important task of this utility is to take the wellformed (validated) configuration and
apply it to the VPP dataplane. The overall flow is this:
apply it to the VPP dataplane. The overall flow consists of three phases:
1. Prune phase (things in VPP that are not in the config), the order is:
1. Retrieve all LCP interfaces from VPP
1. Create phase (things in the config that are not in VPP), the order is:
1. Sync phase, for each interface in the configuration
When removing things, care has to be taken to remove inner-most objects first. For example,
QinQ/QinAD sub-interfaces should be removed before before their intermediary Dot1Q/Dot1AD. Another
example, MTU of parents should raise before their children, while children should shrink before their
parent. Order matters, so first the tool will ensure all items do not have config which they should
not, then it will ensure that all items that are not yet present, get created in the right order,
and finally for all interfaces, they are synchronized with the configuratino (IP addresses, MTU etc).
### Pruning
1. Retrieve all LCP interfaces from VPP
* Starting with QinQ/QinAD, then Dot1Q/Dot1AD, then (BondEthernets, Tunnels, PHYs)
* Remove those that do not exist in the config
* Remove those that do exist in the config but are on a different phy
* Remove those that do exist in the config but have a different encapsulation
1. Retrieve all Loopbacks and BVIs from VPP
1. Retrieve all Loopbacks and BVIs from VPP
* Remove those that do not exist in the config
* Remove all IP addresses that are not in the config
1. Retrieve all Bridge Domains from VPP
1. Retrieve all Bridge Domains from VPP
* Remove those that do not exist in the config
* Remove all IP addresses that are not in the config
* Remove all member interfaces that are not in the config, return them to L3 mode
* Remove tag-rewrite options on member interfaces if they have encapsulation
1. For L2 Cross Connects from VPP
1. For L2 Cross Connects from VPP
* For interfaces that do not exist in the config (either as source or target):
* Return the interface to L3 mode
* Remove tag-rewrite options on if it has encapsulation
1. Retrieve all BondEthernets from VPP
1. Retrieve all BondEthernets from VPP
* Remove those that do not exist in the config
* Remove all member interfaces that are not in the config, return them to L3 mode
* Remove all IP addresses that are not in the config
1. Retrieve all Tunnels from VPP
1. Retrieve all Tunnels from VPP
* Remove those that do not exist in the config
* Remove all IP addresses that are not in the config
1. Retrieve all interfaces from VPP
1. Retrieve all interfaces from VPP
* Starting with QinQ/QinAD, then Dot1Q/Dot1AD, then (BondEthernets, Tunnels):
* Remove those that do not exist in the config
* Remove those that do exist in the config but have a different encapsulation
@ -147,29 +160,33 @@ apply it to the VPP dataplane. The overall flow is this:
* And finally, for each PHY:
* Remove all IP addresses that are not in the config
* If not in the config, return to default (L3 mode, MTU 9000, admin-state down)
1. Create phase (things in the config that are not in VPP), the order is:
1. Loopbacks and BVIs
1. Bridge Domains
1. BondEthernets
1. Tunnels
1. Dot1Q and Dot1AD sub-interfaces
1. Qin1Q and Qin1AD sub-interfaces
1. LCP pairs
1. Sync phase, for each interface in the configuration
1. For BondEthernets:
### Creating
1. Loopbacks and BVIs
1. Bridge Domains
1. BondEthernets
1. Tunnels
1. Dot1Q and Dot1AD sub-interfaces
1. Qin1Q and Qin1AD sub-interfaces
1. LCP pairs
### Syncing
1. For BondEthernets:
* Set MTU of member interfaces
* Add them as slaves, lexicographically sorted by name
* Set their admin-state up
* Ensure LCP has the same MAC as the BondEthernet
1. For Bridge Domains:
1. For Bridge Domains:
* Set the MTU of the member interface (including BVI)
* Add the members (including the BVI)
* Set tag-rewrite options if any of the interfaces have encapsulation
1. For L2 Cross Connects, if applicable:
1. For L2 Cross Connects, if applicable:
* Set the MTU of the two interfaces
* Set the L2XC option on both
* Set tag-rewrite options if any of the interfaces have encapsulation
1. Decrease MTU for QinQ/QinAD, then Dot1Q/Dot1AD, then (BondEthernets, Tunnels, PHYs)
1. Raise MTU for (PHYs, Tunnels, BondEthernets), then Dot1Q/Dot1AD, then QinQ/QinAD
1. Add IPv4/IPv6 addresses
1. Set admin state up
1. Decrease MTU for QinQ/QinAD, then Dot1Q/Dot1AD, then (BondEthernets, Tunnels, PHYs)
1. Raise MTU for (PHYs, Tunnels, BondEthernets), then Dot1Q/Dot1AD, then QinQ/QinAD
1. Add IPv4/IPv6 addresses
1. Set admin state up