systemd/network: Ignore mana VFs on Azure#106
Conversation
Azure is introducing a new generation of NICs, that are architected the same way as the current Mellanox based ones: there is a synthetic (vmbus) NIC for handling some control traffic (including DHCP) and a VF that is enslaved to the synthetic NIC. We therefore need to exclude the devices manage by the mana driver from IP management. Signed-off-by: Jeremi Piotrowski <jpiotrowski@microsoft.com>
pothos
left a comment
There was a problem hiding this comment.
Reminds me that this file is something afterburn could generate based on the MAC address instead of having to chase driver changes.
Existing issue for that: flatcar/Flatcar#554 |
|
interesting - my initial thought was "i can implement that" but then i realised we also need it to work for hotplugged interfaces, so we'd need to re-run afterburn if we did this. how about i just configure the list to say |
Ah, the metadata server output will change then? Retriggering afterburn from udev could work in that case.
We still need to restrict the matching to "meant to be physical" NICs. If they are all PCI devices, that can work with matching for the path or something but otherwise we could also take the restriction list from the default rule as this is also for that type of NICs. |
|
FYI, also needs a PR for bootengine:dracut/03flatcar-network/yy-azure-sriov.network and bootengine:dracut/03flatcar-network/yy-azure-sriov-coreos.network (yeah, two files here and two files there to keep in sync…) |
|
Opened the second PR here: |
Ignore mana VFs on Azure
Azure is introducing a new generation of NICs, that are architected the same way as the current Mellanox based ones: there is a synthetic (vmbus) NIC for handling some control traffic (including DHCP) and a VF that is enslaved to the synthetic NIC. We therefore need to exclude the devices manage by the mana driver from IP management.
How to use
[ describe what reviewers need to do in order to validate this PR ]
Testing done
No testing, just got a LISA bugreport.
changelog/directory (user-facing change, bug fix, security fix, update)/bootand/usrsize, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.