From 3161e3452f16c8e269e3b9d7fed175343c6c1468 Mon Sep 17 00:00:00 2001 From: Peter Boy Date: Apr 09 2021 08:38:51 +0000 Subject: Completed the server installation page beta and some modifications on index page1 --- diff --git a/docs/modules/ROOT/pages/index.adoc b/docs/modules/ROOT/pages/index.adoc index 68993fe..6b9805e 100644 --- a/docs/modules/ROOT/pages/index.adoc +++ b/docs/modules/ROOT/pages/index.adoc @@ -5,14 +5,14 @@ Peter Boy; Jan Kuparinen image::Logo_server2.png[Server] -[sidebar] -**** -Creation Date: 2021-03-10 | Last update: 2021-03-28 | Related Fedora Version(s): 34 -**** [NOTE] ==== **Beta 1**! Please comment on server mailing list ==== +[sidebar] +**** +Creation Date: 2021-03-10 | Last update: 2021-03-28 | Related Fedora Version(s): 34 +**** == Our Mission @@ -41,7 +41,7 @@ Stay tuned. The results will soon be visible. Fedora Server Edition offers users and system administrators several attractive features -* The biannual release cycle allows the latest stable versions of system and application software with new or improved features to be used almost immediately. Users and system administrators can swiftly respond to new market options and changing or expanding customer requirements. +* The biannual release cycle allows the inclusion of the latest versions of system and application software almost immediately. This empowers users and system administrators to swiftly respond to new market options and changing or expanding customer requirements. * A sophisticated and highly engineered release and quality assurance process enables a high level of reliability and stability, despite a comparatively fast release cycle. This achieves an excellent balance between 'bleeding edge' and maturity for productive use in mainstream deployments. @@ -73,7 +73,7 @@ Detailed step-by-step instructions are given for various typical areas of applic - People, policies, and working methods -== How You Can Contribute +== You Are Welcome to Contribute You don't have to be a programmer, a developer or a technical nerd to contribute to the development of Fedora Server. We are especially interested in feedback from our users and potential new users. diff --git a/docs/modules/ROOT/pages/server-installation.adoc b/docs/modules/ROOT/pages/server-installation.adoc index 4f4dad4..c65c47e 100644 --- a/docs/modules/ROOT/pages/server-installation.adoc +++ b/docs/modules/ROOT/pages/server-installation.adoc @@ -2,30 +2,34 @@ Peter Boy; Jan Kuparinen :page-authors: {author}, {author_2} +[NOTE] +==== +Beta 1 Please comment on server mailing list! +==== [sidebar] **** 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 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. +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]. + +image::serverinstall-summaryscreen.png[Anaconda Installation Summary] + +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 -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. +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 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. +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 regarding partitioning. 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. +By default, Anaconda as tailored for Fedora Server Edition creates in case of a bios boot machine a small /boot partition on the first drive, used by 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 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). +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. === The rationale @@ -33,17 +37,17 @@ The rationale behind this is a separation of system and user data. This should e === 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) +You may reinforce that rationale even further and 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. Mount it at /var/log to prevent log files to flood and block the system and vice versa prevent that any other space issue on root partition blocks your log files. 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 default partitioning, 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. === 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 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. 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. -On Bios hardware and hard disks with a maximum of 2 TB, select the comfortable "Custom" option. +- If exist, delete any partition (use the '-' sign at the bottom of the left box). - Add a Partition, select mount point /boot, type changes from default LVM to standard, select size 1 Gib. @@ -53,23 +57,31 @@ On Bios hardware and hard disks with a maximum of 2 TB, select the comfortable " - Add additional raid partitions as needed. -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. +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 custom' option. == Networking -- Static configuration, appropriate for servers -- Post F32 network config file locations + +By default the installation program creates a DHCP configuration for each network interface. In case of an active connection it is automatically started during boot. + +In case of servers it is often preferrable 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, avtivate the IPv4 rsp. IPv6 tab. Switch from DHCP to manual and add an IP spezification. + +Note: Post F32 NetworkManager stores the configuration in __/etc/NetworkManager/connected_systems/*.network__! == 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) +As 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! + +If there is no direkt terminal access available create a fall back user (e.g. hostmin) with password authentication active and administration privilege (group wheel & sudo su). 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 for some reason the private key file is not available. == Time zone and time synchronization -- correct date & time is relevant for various security measures -- check time zone -- check activation if synchronization +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. + +== Start Installation +Then, when all settings and configurations fit, select _Begin Installation_ and lean back. When finished, confirm a restart. Log in and follow the post installation suggestions in the Fedora Server Edition System Administration Guide.