Fedora Server Installation Guide
Fedora Server Edition uses the same installation procedure as most of the other editions and spins. Basic installation is covered by Fedora’s overall Installation Guides.
While Fedora Server Edition uses the same package set as all Fedora editions, the defaults are different and more tailored to a server install. These defaults are outlined in the following sections, and can, of course, be overridden either in kickstart or the installer itself
And of course, the installation planning depends on the details of the target environment. As an example, a virtual machine installation requires a different approach to storage than a bare metal installation. In the former case, one does not need to worry about a RAID system.
These instructions and notes primarily concern a bare metal installation. A "bare metal installation" is one where the Operating System (Fedora Server Edition in this case) is installed directly on the computer vs a virtual machine, in the cloud, etc.
Fedora Server comes with its own special installation ISO image, either as a full local installation or as a network installation. If at all possible, use one of the two Fedora Server Edition alternatives ("Standard" or "Netinstall") and avoid booting from another image. Anaconda, the installation program and the GUI look alike for any edition or spin, but are tailored differently under the surface, e.g. with different configuration defaults.
If you ask 3 system administrators about the best practice for hard disk partitioning, you will get at least 5 different answers. There is no clear, best way to partition your disks. While this subject is beyond the scope of this document, we can offer that we can expect 4g for a typical install. Talk to your friends, read up on the subject, search for articles, and make your own judgment. Many solutions are editable after installation (but not all!).
By default, on a BIOS booting machine, Anaconda creates a small
partition on the first drive, used by the Grub2 bootloader. The remaining area is filled with another partition and one volume group (VG) created therein. In case of a disk larger then 2 TB it uses a GPT partition table and adds a BIOSboot partition to the described scheme, otherwise it uses the traditional DOS partition table.
In the case of a UEFI boot system, Anaconda creates first the required 'EFI System' partition and then adds the aforementioned
partition and LVM partition and Volume Group (VG).
A logical volume of approximately 15 GB (the exact value depends on the disk capacity of your system) is created for the operating system and its software. The other available space remains free for the creation of Logical Volumes (LVs) for user data, which are to be mounted at the appropriate positions in the directory tree of the system area.
The rationale behind this is a separation of system and user data, which eases system administration, increases security, and decreases the likelihood of errors. The system area (i.e. the operating system including installed software) must be maintainable completely independently of the storage of user data. System maintenance must not jeopardize user data under any circumstances. If necessary, it must be possible to unmount user data.
If you are a more experienced administrator, you may wish further the rationale above with increased separation.
Create another small partition and VG dedicated to the operating system (resulting in three partitions: system, user, & boot). A good size for this VG (eg.
) is, approximately, 30 GB. Create a LV (e.g.
) of 15 GB for the operating system and maybe additional LVs for the runtime environment (e.g. a LV
) of about 5 GB. Mount it at
to prevent log files from flooding and blocking the system and, vice versa, prevent that any other space issue on the root partition blocking your logs. The remaining free space is left for distribution as needed over time. The remaining area of the hard disk is filled by a large partition and a VG for user data (e.g.
). Similar to the default partitioning, all user data is created as LVs in
and mounted in the corresponding directories of the system. This is the maximum possible separation of system and user data with only one hard disk is available. And with today’s typical hard drive size of 2 TB and more, those dedicated 30 GBs don’t interfere with the effective use of disk space anymore.
If there is more than one disk available, the default partitioning creates, on each of the other disks, one big partition with a Physical Volume (PV) and adds it to the VG.
On a server, this is usually not optimal. Rather, several disks should store data redundantly in order to maintain operation in the event of a hardware failure. Configuring a RAID system is one such solution. For details see the Creating Software RAID section of the Installation Guide. NOTE: both of these links are to the Fedora 34 version of the docs. Please confirm your are using that version or find the same docs for your version.
Manual partitioning is necessary for RAID setup. Select "Installation Destination" in the Summary Screen, the options "Custom" and "Advanced Custom (Blivet-GUI)" both enable manual partitioning.
On BIOS boot machines and hard disks with a maximum of 2 TB, select the comfortable "Custom" option.
If any exist, delete any partitions (use the '-' sign at the bottom of the left box).
Add a Partition, select a mount point (e.g.
), type changes from default LVM to standard, select size 1 Gib.
After creation modify the partition type to RAID.
Anaconda later detects the raid configuration of /boot and installs the
on each included disk. If the first disk fails it can boot using the other one.
Add additional RAID partitions as needed.
Hard disks larger than 2 TB require a
By default the installation program creates a DHCP configuration for each network interface. In the case of an active connection it is automatically started during boot.
In case of servers it is often preferable to configure a static IP address. This ensures a valid network connection at system start even if the DHCP server is defective. Select the network interface, activate the IPv4 or IPv6 tab. Switch from "Automatic (DHCP)" to "Manual" and add an IP specification.
|Post Fedora 32, NetworkManager stores the configuration in /etc/NetworkManager/connected_systems/*.network|
At a minimum, you must set a password for the ROOT account. Select 'Root Password' below 'USER SETTINGS' and enter an appropriate password. For security reasons, ssh login as root is only allowed with key-file, but the account is not locked. It is not advisable to modify these security settings! Secure root access via ssh key file is an option and, in an emergency, access with a password via an attached console or Cockpit login.
If there is no direct terminal access available create a fall back user (e.g.
) with password authentication active and administrative privilege (group
). In such a case, this is the only way to get access to the server after the reboot! And even later, it is the only way to get administrative access if the private key file is not available.
For the operation of a server, a crucial condition is to ensure the correct time setting. As a very simple example, you need to find a specific event in the log files. Therefore, the correct settings for date and time are of utmost importance.
On the "Installation Summary" page select "Time & Date" and check time, time zone and activation of time synchronization.
Then, when all settings and configurations fit, select Begin Installation and lean back (or get a coffee!). When finished, confirm the option to restart the computer. Log in and follow the post installation suggestions in the Fedora Server Edition System Administration Guide.