systemd

Sometimes network interface autonegotiation doesn’t work as well as it should. Luckily, you can fix it with systemd-networkd. 🔧

After a recent OpenStack-Ansible (OSA) deployment on CentOS, I found that keepalived was not starting properly at boot time:

Although OpenStack-Ansible doesn’t fully support CentOS 7 yet, the support is almost ready.

My OpenStack cloud depends on Ubuntu, and the latest release of OpenStack-Ansible (what I use to deploy OpenStack) requires Ubuntu 16.

All systems running systemd come with a powerful tool for reviewing the system journal: journalctl.

I’ve gone on some mini-rants in other posts about starting daemons immediately after they’re installed in Ubuntu and Debian.

Switching to systemd-networkd for managing your networking interfaces makes things quite a bit simpler over standard networking scripts or NetworkManager.

Earlier today, I wrote a post about my first thoughts on the Supermicro 5028D-T4NT server.

I’ve recently moved over to Rackspace’s OpenStack Private Cloud team and the role is full of some great challenges.

If you’re running Fedora 22 and you’ve recently updated to systemd-219-24.

This post originally appeared on the Fedora Magazine blog.

I talked a bit about systemd’s network device name in my earlier post about systemd-networkd and bonding and I received some questions about how systemd rolls through the possible names of network devices to choose the final name.

I’ve written about systemd-networkd in the past and how easy it can be to set up new network devices and tunnels.

I’ve recently set up a Fedora 22 firewall/router at home (more on that later) and I noticed that remote ssh logins were extremely slow.

My older post about rotating GNOME’s wallpaper with systemd timers doesn’t seem to work in Fedora 22.

With Fedora 22’s release date quickly approaching, it’s time to familiarize yourself with dnf.

There are plenty of guides out there for making ethernet bridges in Linux to support virtual machines using built-in network scripts or NetworkManager.

NOTE: This works in Fedora 21, but not in Fedora 22.

While using a Dell R720 at work today, we stumbled upon a problem where the predictable network device naming with systemd gave us some unpredictable results.

It seems like everyone is embracing systemd these days.

SELinux isn’t a technology that’s easy to tackle for newcomers.