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

ncm-network: nmstate - add additional route rule parameters #1646

Closed
wants to merge 1 commit into from

Conversation

aka7
Copy link
Contributor

@aka7 aka7 commented Jan 5, 2024

provide additional route rule parameters for nmstate config as defined in https://nmstate.io/devel/yaml_api.html#routes

Also add a default absent rule to clear route rules entries for the table. nmstate by default will merge rules therefore won't clear if there are any old rules already present. This will make sure only rules defined by profile is present.

  • Why the change is necessary.
    Enhancement to policy based routing.
  • What backwards incompatibility it may introduce.
    None.

@aka7 aka7 requested review from ned21 and jrha January 5, 2024 11:00
@aka7 aka7 force-pushed the ncm_network_nmstate_rule_param branch from c4b3700 to 3bf9871 Compare January 8, 2024 10:24
@ned21
Copy link
Contributor

ned21 commented Jan 8, 2024

Thanks for making the changes. I see there's now a merge commit in the branch. Our preference is for a linear history: any chance you can use rebase to bring the branch up to date with main instead of merge?

- provide additional route rule parameters for nmstate config as defined in
https://nmstate.io/devel/yaml_api.html#routes

- add a default absent rule to clear route rules entries for the table.
  nmstate by default will merge rules therefore won't clear if there are any
  old rules already present. This will make sure only rules defined by profile is present.
@aka7 aka7 force-pushed the ncm_network_nmstate_rule_param branch from 28c0265 to d113bfa Compare January 8, 2024 13:57
@aka7
Copy link
Contributor Author

aka7 commented Jan 8, 2024

Thanks for making the changes. I see there's now a merge commit in the branch. Our preference is for a linear history: any chance you can use rebase to bring the branch up to date with main instead of merge?

ah sorry, that's my bad. wasn't meant push the merge commit out.
This is another PR not yet merged but was just testing it again. so no rebase is needed at this point. fixed.

@aka7
Copy link
Contributor Author

aka7 commented Jan 11, 2024

closing PR in favor of one, #1647

@aka7 aka7 closed this Jan 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants