From aa89bee13d1d528948bf8a67de88d3db41d39ac1 Mon Sep 17 00:00:00 2001 From: Peter Boy Date: Apr 07 2021 16:23:49 +0000 Subject: Added content to installation guide --- diff --git a/docs/modules/ROOT/pages/server-installation.adoc b/docs/modules/ROOT/pages/server-installation.adoc index b895516..4f4dad4 100644 --- a/docs/modules/ROOT/pages/server-installation.adoc +++ b/docs/modules/ROOT/pages/server-installation.adoc @@ -1,45 +1,70 @@ -= Fedora Server Installation Guides += Fedora Server Installation Guide Peter Boy; Jan Kuparinen :page-authors: {author}, {author_2} [sidebar] **** -Author: Peter Boy (pboy) | Creation Date: 2021-04-05 | Last update: 2021-04-05**** | Related Fedora Version(s): 34 +Author: Peter Boy (pboy) | Creation Date: 2021-04-05 | Last update: 2021-04-05 | Related Fedora Version(s): 33,34 **** [NOTE] ==== First Draft! Please comment on server mailing list ==== -- Fedora Server uses the Fedora standard installation system: Anaconda -- Follow Procedures as described in the Fedora Installation Guide -- However, there are some peculiarities and differences for Fedora Server Edition that should be noted in deviation or in addition to the explanations there. They are explained in the following. - -Basic installation is covered by Fedora's overall Installation Guide (link). But there are several of Fedora Server specific topics which are not included. +Fedora Server Edition uses the same installation procedure as most of the other editions and spins. Basic installation is covered by https://docs.fedoraproject.org[Fedora's overall Installation Guides]. However, there are some peculiarities and differences for Fedora Server Edition that should be noted in deviation or in addition to the explanations over there. These are outlined in the following sections. == Choosing the right installation medium -- Choose Fedora Server Edition iso, either full installation or netinstall -- avoid using any of the other iso files and then select "Fedora Server". The program and the GUI look alike, but the underlying tailoring of anaconda is different! +Fedora Server comes with its own special installation iso image, either as a full installation or as a network installation. If at all possible, use one of the two Fedora Server Edition alternatives and avoid booting from another image, for example 'Everything' and then selecting Fedora Server as the installation target, or changing the installation source to 'Fedora Server' afterwards. Anaconda, the installation program and the GUI look alike for any edition or spin, but are tailored differently under the skin, e.g. with different configuration defaults. + +== Disk partitioning + +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. It depends on different goals and weightings. + +=== What default partitioning does + +By default, Anaconda as tailored for Fedora Server Edition creates in case of a bios boot hardware a small /boot partition on the first drive. It fills the remaining area with another partition and creates one volume group (VG) therein. In case of a disk larger then 2 TB it uses a GPT partition table and adds a BIOSboot partition, otherwise the traditional DOS partition table. + +Therein, a logical volume of approx. 15 GB (the exact value depends on the disk capacity) 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 (details later). + +=== The rationale + +The rationale behind this is a separation of system and user data. This should ease system administration, increase security, and decrease error-proneness. The system area, i.e. the operating system including installed utility programs and software must be maintainable completely independently of the storage of user data. System maintenance must not jeopardise user data under any circumstances. If necessary, it must be possible to unmount user data. + +=== Further rationale reinforcement + +You may further reinforce that rationale and even create another small partition and VG dedicated to the operating system (in addition to the partition for /boot). A good size for this volume group, eg. sysvg, is approx. 30 GiB. Create an LV, e.g. 'sys_root' of 15 GiB for the operating system and maybe additional LVs for the runtime environment, e.g. a LV 'sys_log' of about 5 GiB for /var/log to prevent log files to flood and block the system. The remaining free space is left for disposal as needed for whatever maintenance work. The remaining area of the hard disk is filled by a large partition and VG for user data, e.g. usrvg. Similar to the standard partition, all user data is created as LVs in usrvg and mounted in corresponding directories of the system area. This is the maximum possible separation of system and user data if only one hard disk is available. And with today's typical hard drive size of 2 TB and more, those dedicated 30 GiB don't interfere with effective use of disk space anymore. + +- (UEFI boot) + +=== Raid system + +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 volume group. + +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. Manual partitioning is necessary for this. Under the installation step "Installation Destination", the options "Custom" and "Advanced Custom (Blivet-GUI)" are available. + +On Bios hardware and hard disks with a maximum of 2 TB, select the comfortable "Custom" option. + +- Add a Partition, select mount point /boot, 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 mbr on each included disks. If the first disk fails it can boot using the other one. -== Disk Partitioning +- Add additional raid partitions as needed. -- What default partitioning does -- Raid system -- Hard disk larger than 2 TB in Raid set-ups -- UEFI boot +Hard disks larger than 2 TB require a GPT disk label and an additional BIOSboot partition. The Custom option can't handle this in a RAID configuration. You have to choose the 'Advanced custon' option. == Networking - Static configuration, appropriate for servers - Post F32 network config file locations -== Creating Users +== Creating users - root, don't modify security settings - If no direkt terminal access: create fall back user with password authentication active and administration privilege (group wheel & sudo su) -== time zone and time synchronization +== Time zone and time synchronization - correct date & time is relevant for various security measures - check time zone