-
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
add SR-IOV GA proposal #6
add SR-IOV GA proposal #6
Conversation
/uncc |
|
||
#### Multus | ||
|
||
Static IPAM plugin is used to assign IPv4 and IPv6 addresses statically to |
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.
This is going to be hard, because Multus has to ask for runtimeConfiguration via its CNI configuration file, which is static. We'll probably need to think of a way for NetworkAttachmentDefinitions to ask for CNI capabilites.
cc @dcbw
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.
We use network selection element in Pod annotation to describe IP/Mac, not in network attachment definition.
In K8s NPWG, we're already finalize about it and implemented in multus.
See the following Spec/PR for the detail:
Spec proposal: https://docs.google.com/document/d/1j9kSTIIKydjqGiYd8Ni9Tej7gv1sxf9VcWeRYXFe5ko/edit
PR: k8snetworkplumbingwg/multus-cni#387
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.
So, the proposal is just about passing the IP runtimeConfig? That makes more sense.
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.
Right.
|
||
##### Default Route Overwrite | ||
|
||
Every pod comes with a default route added via openshift-sdn. It is not |
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.
This just sounds like https://github.com/nokia/danm
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.
@squeed so you think that we should NOT do that? If so, could you please let us know why?
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.
@squeed Is it because that with default route overwrite
, Multus is doing too much other than just calling delegated plugins which sounds like a thick plugin such as danm?
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.
@squeed btw, we're going to use https://github.com/redhat-nfvpe/cni-route-override to override CNI route (except default route). For default route, we are proposing 'gateway' feature in NPWG.
If you think that multus includes route manipulation inside it and getting thick plugin, that is not correct, actually. We're still designing as minimum as possible.
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.
Okay, that should work as well. Could you provide some example configuration? It's important that we design something that will work with CNI CHECK.
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.
Here is the example config:
https://github.com/redhat-nfvpe/cni-route-override#example-configuration
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.
@squeed I will add a default route overwrite example soon in a separate PR, sth like this:
kind: Pod
metadata:
name: my-pod
namespace: my-namespace
annotations:
k8s.v1.cni.cncf.io/networks: |
[
{ "name":"net-a" },
{
"name":"net-b",
"default-route": ["10.0.0.1"]
}
]
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.
also paste the link for default route overwirte proposal: https://docs.google.com/document/d/1pqbWYtFdEYyXd1cXuyvq_J5SRnhiXCRptXho63gI4A8/edit
enhancements/20190903-SRIOV-GA.md
Outdated
|
||
### Risks and Mitigations | ||
|
||
#### NUMA |
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.
This should be part of GA now that we have 1.16 in 4.3.
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.
fixed
enhancements/20190903-SRIOV-GA.md
Outdated
- Manage SR-IOV end to end deployment and configuration via Operator | ||
- Sufficient test coverage (upgrade, negative and performance) | ||
- IP and MAC address management for SR-IOV interfaces | ||
- Security and QoS support for SR-IOV interfaces |
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.
Security and QoS flags are not a requirements for GA.
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.
Removed
- Compare SR-IOV network performance w/wo NUMA affinity | ||
- Support SR-IOV QoS flags | ||
- Add SR-IOV Metrics and Alerting | ||
- Support both RHEL and RHCOS worker nodes |
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.
Add NUMA support here.
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.
added
0c9b484
to
a171753
Compare
/lgtm |
/approve As discussed elsewhere, I'd like to see a follow-up PR that outlines how routes will be configured. But that isn't blocking. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fepan, squeed, 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 |
Adding risks - mitigations
No description provided.