Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Rsvp auto ero generation based on learned TE topology from IGP #299

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Rsvp auto ero generation based on learned TE topology from IGP #299

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
db9ec62
auto ero changes
SouravSinhaRoy Feb 7, 2023
f0680b4
Update auto generated content
actions-user Feb 7, 2023
e954d45
ero mode choice addition
Feb 9, 2023
47ba31f
Update auto generated content
actions-user Feb 9, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions artifacts/openapi.html
View file
Open in desktop

Large diffs are not rendered by default.

33 changes: 29 additions & 4 deletions artifacts/openapi.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

31 changes: 27 additions & 4 deletions artifacts/otg.proto
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

30 changes: 26 additions & 4 deletions device/rsvp/rsvpEro.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,31 @@ components:
Configuration for the optional RSVP-TE explicit route object(ERO) object included in Path Messages.
type: object
properties:
choice:
description: EROs can be either manually configured or automatically. If auto mode for ERO is selected, the learned
TE topology from the connected IGP (OSPF, ISIS) is used to calculate the explicit path to egress based on IGP supplied constraints, destination IP and
available bandwidth and auto-create explicit ERO for tunnels between ingress and egress. If manual mode is selected
user configured EROs will be included in Path Messages.
type: string
default: manual
x-field-uid: 4
x-enum:
manual:
x-field-uid: 1
auto:
x-field-uid: 2
manual:
description: User configured EROs will be included in Path Messages.
type: string
x-field-uid: 5
auto:
description: The learned TE topology from the connected IGP (OSPF, ISIS) is used to calculate the explicit path to egress.
type: string
x-field-uid: 6
prepend_neighbor_ip:
description: >-
Determines whether the IP address of the RSVP neighbor should be added as an ERO sub-object.
If it is to be included, it can be included as a Loose hop or as a Strict hop.
If it is to be included, it can be included as a Loose hop or as a Strict hop. Only applicable when choice is manual.
type: string
x-enum:
dont_prepend:
Expand All @@ -21,7 +42,8 @@ components:
x-field-uid: 1
prefix_length:
description: >-
If prepend_egress_ip is set to one of 'prepend_loose' or 'prepend_strict', then set this value as the prefix length of the ERO sub-object containing egress IP address.
If prepend_egress_ip is set to one of 'prepend_loose' or 'prepend_strict', then set this value as the prefix length of the ERO sub-object
containing egress IP address. Only applicable when choice is manual.
type: integer
default: 32
minimum: 0
Expand All @@ -30,11 +52,11 @@ components:
subobjects:
description: >-
Array of sub-objects to be included in the ERO. These sub-objects contain the intermediate hops to be traversed by the LSP while being forwarded towards the egress endpoint.
These sub-objects are included after the optional sub-object containing IP address of egress endpoint of the LSP (when present).
These sub-objects are included after the optional sub-object containing IP address of egress endpoint of the LSP (when present). Only applicable when choice is manual.
type: array
items:
$ref: './rsvpIngressP2PLsp.yaml#/components/schemas/Rsvp.Ero.Subobject'
x-field-uid: 3
x-field-uid: 3
Rsvp.Ero.Subobject:
description: >-
Configuration for the ERO sub-object.
Expand Down