Three weeks after the launch of the Fedora 27 Linux operating system, the Fedora Project announced the release of Fedora 27 Server edition, but it’s not what you might have expected.

Fedora Project released the latest version of the Red Hat-sponsored Fedora Linux operating system, Fedora 27, last month on November 14. Users were able to download Fedora 27 Workstation and Atomic Host editions, as well as any other flavor from the official Fedora Labs, Fedora Spins, and Fedora ARM projects.

The team decided not to release a Fedora 27 Server edition at that time because they wanted to get the pulse of the community for a new Server flavor called Fedora Modular Server, which was available as a beta release when Fedora 27 was announced last month, offering modularity to the Fedora Server operating system.

But it looks like the modularity aspect wasn’t welcomed in the Fedora Linux community, so they had to release the classic Fedora 27 Server. “Based on feedback from that beta, they decided to take a different approach, and the Modularity subproject is going back to the drawing board,” writes Matthew Miller, Fedora Project Leader.
Those who want to download Fedora 27 Server or (finally) upgrade their Fedora 26 Server installations can now download the netinstall or classic install images. Fedora 27 Server is available for 32-bit (i386), 64-bit (x86_64), ARM64 (AArch64), ARMhfp, PPC64 (PowerPC 64-bit), PPC64el (PowerPC 64-bit Little Endian), and s390x (IBM System z) architectures.

—cut here—
So I started with my first server yesterday (the least critical one) and went down the path to upgrade the operating system from Fedora 26 to Fedora 27 on a 64bit system.
1. make sure the system is uptodate
dnf –refresh upgrade
2. make sure the upgrade package is in place
dnf install python3-dnf-plugin-system-upgrade
3. Go!
dnf system-upgrade download –refresh –releasever=27
Transaction Summary
Install 38 Packages
Upgrade 686 Packages
Remove 3 Packages
Total download size: 404 M
DNF will only download packages, install gpg keys, and check the transaction.
Is this ok [y/N]:Y
4. reboot to start upgrade at 09:30
dnf system-upgrade reboot
completed at 09:43 and reboot into Linux version 4.14.3-300.fc27.x86_64
5. Clean up and check more more updates/upgrades
dnf clean packages
dnf upgrade

Start to finish was under 15 minutes on a 120GB sata SSD drive. And it worked! And there were no issues!

I let it run for a few hours to see if it was stable or if any problems might develop, and they did not.
So that same afternoon I went in and did the 2nd least critical system.
I followed the same steps above and completed in approx 30 minutes (on a slower system with a spinning hard drive).

Both ran well overnight without any issues.
This morning I started the 3rd least critical system upgrade (with a spinning drive). It completed with a couple of small issues
09:42 – 11:19 or 100 minutes. It is now running and being checked for stability.
The two small issues were a previously installed package that blocked the upgrade process. It was solved by dnf remove package
The 2nd issue was after the upgrade when apache would not start.

Dec 14 11:14:34 httpd[819]: AH00526: Syntax error on line 33 of /etc/httpd/conf/httpd.conf:
Dec 14 11:14:34 httpd[819]: Invalid command ‘MaxSpareServers’, perhaps misspelled or defined by a module not included
commenting out that command in the file fixed that issue.