#14: Investigate systemd-networkd
------------------------------+--------------------------------
Reporter: mattdm | Owner: janeznemanic
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Alpha)
Component: Cloud Base Image | Resolution:
Keywords: |
------------------------------+--------------------------------
Comment (by gospo):
Replying to [comment:7 mattdm]:
>
> It's important to note that the Fedora Cloud image, we disable this
feature (ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules),
because systemd's priority is consistency of naming when there are
multiple interfaces on the same system. By and large, our concern is with
consistency of a *single* device name whereever the image boots, so the
network interface is traditional eth0 (or eth* if more than one).
I was thinking about the fact that the slot-naming-rules could be modified
so that the first NIC found was named em1, second em2, etc, but disabling
the rules completely seems fine.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/14#comment:9>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
