From Fedora Project Wiki
No edit summary
Line 35: Line 35:
</pre>
</pre>


===Further Reading===


* [https://wiki.archlinux.org/index.php/Systemd-networkd ArchLinux systemd-networkd documentation]
* [http://www.freedesktop.org/software/systemd/man/systemd-networkd.service.html Upstream systemd-networkd documentation]


[[User:Gholms|Gholms]] ([[User talk:Gholms|talk]]) 05:49, 27 August 2015 (UTC)
[[User:Gholms|Gholms]] ([[User talk:Gholms|talk]]) 05:49, 27 August 2015 (UTC)

Revision as of 02:20, 29 September 2015

This is a placeholder page for the discussion of what the Cloud image (Base at first, Atomic to follow) requires from a networking stack on it's images.


- configure DHCP, renew dhcp leases - configure with cloud-init - configure with traditional RH-ecosystem ifcfg-eth0 file (log warnings for unsupported options)


Questions!

- Q: any need to support more than one interface? - Q: if single interface, should we standardize on "eth0"" - Q: dns configuration? - Q: support static IP (via cloud-init?)


Several use cases in EC2 involve instances with multiple network interfaces and occasionally multiple addresses on a single interface. I do not believe all of those need to be configured automatically, but it ought to remain possible for a user/script/etc to make network configuration changes that persist across reboots.

Work in progress
mhayden is doing some rambling on systemd-networkd here since maxamillion asked so nicely.

systemd-networkd use cases

Here are some sample use cases for systemd-networkd and example configurations.

Simple DHCP on a single interface

For an interface eth0, a single .network file is needed:

# cat /etc/systemd/network/eth0.network
[Match]
Name=eth0

[Network]
DHCP=yes

Further Reading

Gholms (talk) 05:49, 27 August 2015 (UTC)