Closed mardim91 closed 3 months ago
There was a decision in the last tsc to put the code here initially until we decide in which separate repo to put it and with what name.
There was a decision in the last tsc to put the code here initially until we decide in which separate repo to put it and with what name.
doesn't make sense to me to move code around, we can create a new repo quickly and rename it several times later... much harder to rip out folder from existing project with all the history
This was the decision from the last TSC. We have said to put it here temporarily as we need this merged until Friday as initial implementation mostly for bureaucratic reasons. After Christmas vacation we can come up with a proper strategy and proper naming that eveybody is alligned with and move the code to a new repo maybe. But this is a decision that we will make in TSC and we need time for this. @sandersms was in TSC and can confirm
I have tried to resolve some "low hanging fruits" comments. The rest of those I will resolve in additional PRs in this repo if the current PR is merged until Friday or in a new repo that TSC decides to put the CNI.
Thank you
I'm completely fine with a new repo. put the code there and approve the thing.
Created a new repo to address the concerns on that aspect at https://github.com/opiproject/opi-gateway-evpn-cni
since new repo created, closing this
The EVPN-GW-CNI is a CNI which enables the consumption and configuration of xPU VFs in a K8s environment specifically for EVPN GW offload on xPUs usecase.
Currently it integrates directly and has been developed to serve the EVPN-GW API and supports VFs that are based on the Intel's IPU Mt.Evans cards. In the future hopefully it will support more than one xPU card vendors.