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 #1659

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

Conversation

aka7
Copy link
Contributor

@aka7 aka7 commented Feb 20, 2024

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

  • Why the change is necessary.
    allow creation of route rules with all options.
  • What backwards incompatibility it may introduce.
    none.

@aka7 aka7 requested a review from jrha February 20, 2024 18:42
@aka7
Copy link
Contributor Author

aka7 commented Feb 20, 2024

@jrha created this for discussion on if there will a way to create sperate schemas for nmstate only options. something to think about. as discussed before.

this isnt urgent but at some point we may need to create unreachable routes and only way to do this with nmstate is through route-rules.

- provide additional route rule parameters for nmstate config as defined in
https://nmstate.io/devel/yaml_api.html#routes
@aka7 aka7 force-pushed the ncm_network_nmstate_rule_param branch from f47225c to 1450ec3 Compare February 20, 2024 19:13
@jrha
Copy link
Member

jrha commented Feb 22, 2024

I'll try and do some testing to establish a way of making the schema modular, but otherwise having these options as a separate nmstate sub-dict would seem cleanest.

@jrha jrha added this to the 24.3 milestone Feb 22, 2024
@@ -77,6 +77,16 @@ type structure_rule = {
"table" ? network_valid_routing_table
@{priority, The priority of the rule over the others. Required by Network Manager when setting routing rules.}
"priority" ? long(0..0xffffffff)
@{nmstate-action used by nmstate module}
Copy link
Member

Choose a reason for hiding this comment

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

i am not in favour of the naming.
at least make a structure_rule_nmstate and move them there.

are these simply ignored by the old network.pm code? if so, i see not much harm.

wrt separate scheam's i can make a PR. i need to work in the core schema anyway to add the IB support.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@stdweird I may need some help/guide from you to move this into the new structure you created, please.

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.

None yet

3 participants