#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 mattdm):
Replying to [comment:17 janeznemanic]:
> So what's the plan here? How do we proceed? What shall I do?
It might be useful to put together a variant of the kickstart file used to
produce the current cloud image which uses systemd-networkd for eth0
instead of initscripts. See https://git.fedorahosted.org/cgit/spin-
kickstarts.git/tree/fedora-cloud-base.ks and basically search for
"network" for parts that might need to be changed.
Then, you should be able to feed that kickstart file into ImageFactory (or
appliance-creator) and get a qcow2 image we can test.
I suppose that someone should file an RFE for systemd to have a
"generator" (that's a typical systemd construct) for handling legacy ifcfg
files (as above), and to create the ifup/ifdown compatibility scripts.
Most ideally, someone will contribute that as patches to systemd upstream,
because code always speaks louder than wishes :) but, just explaining what
we need is a good start.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/14#comment:18>
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
