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.

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

[hld]: Support for multiple routing type actions #273

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

theasianpianist
Copy link
Contributor

@theasianpianist theasianpianist commented Nov 3, 2022

Some routing types require multiple actions to be performed in order. This PR updates the DASH_ROUTING_TYPE_TABLE schema to allow for this by adding a second schema for the table. The existing schema will be used for all routing types requiring only a single action. Routing types requiring multiple actions will use the new schema.

Signed-off-by: Lawrence Lee [email protected]

@theasianpianist theasianpianist marked this pull request as draft November 3, 2022 05:13
```
key = DASH_ROUTING_TYPE_TABLE:routing_type; routing type can be {direct, vnet, vnet_direct, vnet_encap, appliance, privatelink, privatelinknsg, servicetunnel}; actions can be a list of action_types
DASH_ROUTING_TYPE_TABLE:{{routing_type}}:{{action_name}}
"action_type": {{action_type}}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Further changes will be needed here since we cannot guarantee that all actions for a routing type will be programmed at the same time - there may be a delay between them which need to be handled before we push the updates to SAI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant