[openstack-dev] Blueprint to change (expand) traditional Ethernet interface naming schema in Fuel
Albert Syriy
asyriy at mirantis.com
Thu Oct 8 09:46:53 UTC 2015
Hello,
I would like to pay your attention to the changing interface naming schema,
which is proposed to be implemented in Fuel [1]
<https://blueprints.launchpad.net/fuel/+spec/new-network-interfaces-naming-schema>
. In brief, Ethernet network interfaces may not be named as ethX, and there
is a reported bug about it [2]
<https://mail.google.com/mail/u/0/%5Bhttps://bugs.launchpad.net/fuel/+bug/1494223>
There are a lot of reasons to switch to the new naming schema, not only
because it has been used in CentOS 7 (and probably will be used in next
Ubuntu LTS), but because new naming schema gave more predictable interface
names [3]
<http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/>.
There is a reported bug related to the topic [4]
<https://bugs.launchpad.net/mos/+bug/1487044>
I suspect, that changing interface naming schema may impact to the current
Fuel code, manifests and tests, because hard-coded Ethernet interface names
(like eth* ) should be removed from the code.
Any comment on the blueprint?
[1]
https://blueprints.launchpad.net/fuel/+spec/new-network-interfaces-naming-schema
[2] https://bugs.launchpad.net/fuel/+bug/1494223
[3]
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
[4] https://bugs.launchpad.net/mos/+bug/1487044
With Best Regards,
Albert Syriy,
Software Engineer,
Mirantis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151008/df17e694/attachment.html>
More information about the OpenStack-dev
mailing list