Kushal Das4

FOSS and life. Kushal Das talks here.

Testing systemd-networkd based Fedora 22 AMI(s)

Few days back I wrote about a locally built Fedora 22 image which has systemd-networkd handling the network configuration. You can test that image locally on your system, or on an Openstack Cloud. In case you want to test the same on AWS, we now have two AMI(s) for the same, one in the us-west-1, and the other in ap-southeast-1. Details about the AMI(s) are below:

Region AMI Name AMI ID Virtualization
ap-southeast-1 fedora22-networkd ami-e89895ba HVM
us-west-1 fedora22-networkd ami-c9e21e8d HVM

Start an instance from these images, and login. In case you want to use some different DNS settings, feel free to remove /etc/resolv.conf link, and put up a normal /etc/resolv.conf file with the content you want.

Testing Fedora Cloud image with systemd-networkd

One of the change proposal I have submitted for Fedora 23 is about having systemd-netowrkd for network configuration. You can find the change page here. Instead of carrying the old network-scripts, we wanted to move to networkd, which is a part of systemd. Couple of the notable benefits are about how it will help us to keep the image size sane by not bringing in any external dependencies, and also about similarity between many different distribution based cloud images from users’ point of view. You can look into the discussions on the Talk page, and the trac ticket.

In the last week’s cloud meeting we decided to have a build of Fedora 22 cloud image with systemd-networkd on it. I made the required changes, and did the local build. You can download the qcow2 image, remember it is 218MB. You can use it in any cloud environment in a normal way. If you want to learn, and play around with the configurations, you may want to read this page. Please try the image and tell us what do you think in the comments section of this post.