Github user remibergsma commented on the pull request:
https://github.com/apache/cloudstack/pull/811#issuecomment-139854597
@giraffeforestg Thanks. Is it an idea to add all possible systemd names to
prevent more issues in the future?
```
With systemd 197 we have added native support for a number of different
naming policies into systemd/udevd proper and made a scheme similar to
biosdevname's (but generally more powerful, and closer to kernel-internal
device identification schemes) the default. The following different naming
schemes for network interfaces are now supported by udev natively:
Names incorporating Firmware/BIOS provided index numbers for on-board
devices (example: eno1)
Names incorporating Firmware/BIOS provided PCI Express hotplug slot index
numbers (example: ens1)
Names incorporating physical/geographical location of the connector of the
hardware (example: enp2s0)
Names incorporating the interfaces's MAC address (example: enx78e7d1ea46da)
Classic, unpredictable kernel-native ethX naming (example: eth0)
```
Source:
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
Shall we add: enoX enpX enxX as well?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
