WRT
```
network:
version: 2
ethernets:
enP2p0s0:
dhcp4: true
```
Today, MANA devices should not be directly configured as they are bound
to the Hyper-V nic (e.g. "eth0" would be configured in this example of
enP2p0s0 as its master interface).
I think the concern here is that we want to get this change in (if
possible) before the next generation of MANA which will be directly
configurable as the bonded hyper-v nic will no longer be surfaced.
I cannot say there's zero risk of a customer using some configuration
that uses the name of MANA VF but no use case comes to mind for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2134334
Title:
Add ID_NET_NAME_INCLUDE_DOMAIN property support to systemd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2134334/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
