#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 janeznemanic):
Replying to [comment:7 mattdm]:
> Replying to [comment:5 gospo]:
> > > One more thing that's been bothering me for a few days now. How does
systemd name network interfaces when Fedora is run on top of different
hypervisors? If xen or kvm is used how does systemd name network
interfaces?
> >
> > Systemd will name the device based on the bus/device/function of the
interfaces, so there could be some differences in the name chosen
depending on the hypervisor used (since each hypervisor may chose a
difference bus/dev/function for a given emulated interface.
>
> 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).
That's a good news. It makes things a lot less complicated.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/14#comment:12>
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
