-
Notifications
You must be signed in to change notification settings - Fork 475
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
SR-IOV GA: add default route overwrite example #57
SR-IOV GA: add default route overwrite example #57
Conversation
@squeed a follow-up PR for SR-IOV GA enhancement, adding example of default route overwrite config. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Thanks!
5ed6f83
to
dbeafa0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Thanks!
From my perspective, it seems that it would be more useful to be able to declare arbitrary network-gateway pairs via Multus. Something like
|
Hey Casey, I think that kind of structure is probably more useful in general and covers a further number of scenarios than what we currently have. What we decided to address in this current version of the NPWG de-facto standard was simply a proposal for "Default route selection". Zenghui's example in this PR is based on this proposal, which is available in this doc @ https://docs.google.com/document/d/1pqbWYtFdEYyXd1cXuyvq_J5SRnhiXCRptXho63gI4A8/edit (Granted yes, it's still a proposal, we're hopeful to ratify this in the upcoming NPWG meeting next week) We currently believe that this should be sufficient for SR-IOV GA, but... What I really like about what you've sketched out is that it's generally useful for routing. Definitely worth further consideration for the next version of the de-facto standard. |
@dougbtv @zshi-redhat Hi, can you take a look at this enhancement and see if it should be rebased or just closed? It looks like a pretty minor addition that we should be able to either update to reflect the current status and merge, or just close. |
dbeafa0
to
5ccd9c7
Compare
Rebased and updated the PR to reflect current fact (no additional features added). |
5ccd9c7
to
d025955
Compare
Thanks! /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: russellb, s1061123, zshi-redhat The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
No description provided.