Peng Liu
Peng Liu
> An alternative could be to have a place for the entire org to host project charts (A gh_pages branch in https://github.com/k8snetworkplumbingwg/helm-charts ?) I prefer this approach. @dougbtv What's your...
@martinkennelly I'm open to add this ddp selector to the SRIOV operator. However, we also need to think about how to discover the ddp profiles on different NIC models.
move here from https://github.com/openshift/sriov-network-operator/issues/438 @zshi-redhat @moshe010 @adrianchiris
There will some difficulty for Openshift. MCO uses MachineConfigPool to group the worker nodes with different MachineConfig. However, for one node, it can only belong to one MachineConfigPool. If we...
Currently, the operator only watches the SriovNetwork CR in its own namespace. And we need to create net-att-def CR in different namespaces. That is why we have `networkNamespace` field.
@DolceTriade What functions do you want the SRIOV network operator to configure the ACC100? creating VFs, loading drivers, and configuring the device plugin? I assume, there are some other functions...
Agree. As OLM has supported ConfigMap https://github.com/operator-framework/operator-lifecycle-manager/issues/1120.
> Small sidenote, I noticed this operator has 2 repositories (here and Openshift). I'm assuming this is the new upstream location and the report is in the right repo? Yes,...
Did you bind vfio driver to the PF? We need a way to find out which devices are network devices if not using the `./net` directory? Any suggestion?
/retest-failed