Rsvp auto ero generation based on learned TE topology from IGP #299
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 is the proposal to add auto ero support to RSVP-TE in the OTG model based on the issue #298. The redocly view of the changes (https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/open-traffic-generator/models/rsvp_ero/artifacts/openapi.yaml&nocors#tag/Configuration/operation/set_config)
In this example, there are two test ports connected to a System Under Test with multiple routers.
Test port1 is acting as the ingress for two uni-directional tunnels. Both the tunnels are originating from the loopback
interface on the device on port1 and terminating in the loopback of the device on port2 , which is also a test port. In between there
is a collection of routers under test which allow creation of LSPs to the same destination via multiple paths. One LSP is created with
auto ero enabled while the other LSP carries a static user configured ERO.