Compare commits
2 commits
fd47c0373c
...
02c8a43336
| Author | SHA1 | Date | |
|---|---|---|---|
| 02c8a43336 | |||
| 77d291421c |
5 changed files with 57 additions and 57 deletions
|
|
@ -11,11 +11,11 @@ Peter Boy; Kevin Fenzi; Jan Kuparinen
|
|||
// ====
|
||||
|
||||
[abstract]
|
||||
A good and sustaining server installation benefits from some plannings ahead. As the saying goes, planning ahead will substitute for many a mishap. This chapter and its subchapters cover general planning principles and focus on a _bare metal_ installation. The implementation of the principles for a virtual machine covers the chapter __Virtualization__.
|
||||
A good and sustainable server installation benefits from some planning ahead. As the saying goes, planning ahead averts many mishaps. This chapter and its subchapters cover general planning principles and focus on a _bare metal_ installation. The implementation of the principles for a virtual machine covers the chapter __Virtualization__.
|
||||
|
||||
Fedora Server Edition uses the Fedora installation program, Anaconda, as several other editions and spins.
|
||||
|
||||
While Fedora Server Edition uses the same rpm package repository as all Fedora editions, the composition of the packages and especially the defaults of the runtime environment are different and more tailored to a server requirements. The following paragraphs describe some of the most important ones. Of course, the administrator can override any of them.
|
||||
While Fedora Server Edition uses the same RPM package repository as all other Fedora editions, its package composition and the defaults of the runtime environment are tailored to server requirements. The following paragraphs describe some of the most important ones. Of course, the administrator can override any of them.
|
||||
|
||||
The installation planning depends on the details of the target environment. Anaconda can install on 'bare metal' directly on server hardware as well as in a virtual environment on a virtual machine (VM). While both targets are similar in many ways, they also differ in key technical details. As an example, on both targets, the storage organization is a very important planning item, but on a virtual machine the system administrator does not need to worry about a RAID system.
|
||||
|
||||
|
|
@ -28,11 +28,11 @@ Having done various decisions and some preparations, the installation itself is
|
|||
|
||||
=== Minimum requirements
|
||||
|
||||
The question of the minimum requirements is always raised, even though it is obvious to anybody that it depends entirely on the deployment plan.
|
||||
The minimum requirements are often questioned, though they depend on the deployment plan.
|
||||
|
||||
Nevertheless, technically, you can run a default Fedora Server on a storage space of about 5 GiB. The installed system occupies about 2.5 GiB. Of course, such a server would hardly be useful for anything. The smallest disc currently available for purchase is 64 GiB. With that, you could satisfactorily run a small to medium server for web and mail services. For virtual machines, we currently use 40 GiB as default.
|
||||
Nevertheless, technically, you can run a default Fedora Server on a storage space of about 5 GiB. The installed system occupies about 2.5 GiB. Of course, such a server would have limited usefulness. The smallest disk currently available for purchase is 64 GiB. With that, you could satisfactorily run a small to medium server for web and mail services. For virtual machines, we currently use 40 GiB as default.
|
||||
|
||||
Again, from a purely technical point of view, a standard Fedora server would get by with about 1 GiB of memory. Again, without being able to do anything useful. The smallest memory chip currently available is 4GiB. In at least a dual channel server system you need 2, so you have at least 8 GiB of RAM. For a small to medium sized server for web and mail services, this is perfectly adequate.
|
||||
Again, from a purely technical point of view, a standard Fedora server would get by with about 1 GiB of memory. Again, without being able to do anything useful. The smallest memory chip currently available is 4GiB. In a dual-channel server system, you need two modules, providing at least 8 GiB of RAM. For a small to medium sized server for web and mail services, this is perfectly adequate.
|
||||
|
||||
So, with today's smallest possible purchasable hardware, a Fedora server can be run perfectly for a small to medium deployment.
|
||||
|
||||
|
|
@ -51,7 +51,7 @@ A new Fedora installation creates a (modern) GPT partition table by default.
|
|||
|
||||
On a _BIOSboot_ machine, Anaconda creates at first a small (1 MiB) ```BIOS boot``` system partition on the first drive. It stores the second stage bootloader which is required by GNU/Grub. Subsequently, it creates a ``/boot``` partition of 1 GiB. It contains all the files necessary for booting Linux, especially the kernel. The remaining area is completely filled with a third partition containing one large volume group (LVM VG) named `fedora` by default. You end up with 3 primary partitions on the hard disk that use all the available space.
|
||||
|
||||
Fedora can still use the (legacy) MBR partition scheme, provided that the disc is not larger than 2 TB. It then omits the ```BIOSboot``` partition and uses only the other two partitions.
|
||||
Fedora can still use the (legacy) MBR partition scheme, provided that the disk is not larger than 2 TB. It then omits the ```BIOSboot``` partition and uses only the other two partitions.
|
||||
|
||||
In the case of a _UEFI_ boot system, Anaconda creates first the required 'EFI System' partition and then adds the aforementioned ```/boot``` partition and one large LVM partition and Volume Group (VG) as described above. You will end up with 3 partitions on the hard disk that completely occupy the available space.
|
||||
|
||||
|
|
@ -97,7 +97,7 @@ That's why you don't get a "Fedora Server Edition" as a result with the "__Every
|
|||
|
||||
=== Download the proper installation media
|
||||
|
||||
Wether on hardware or on a virtual machine, an installation requires the download and the verification of an appropriate installation medium. On your Workstation, you can either use the web browser to download the image file or open a terminal window and perform the download via CLI commands.
|
||||
Whether on hardware or on a virtual machine, an installation requires the download and verification of an appropriate installation medium. On your Workstation, you can either use the web browser to download the image file or open a terminal window and perform the download via CLI commands.
|
||||
|
||||
In the former case, navigate your browser to _https://fedoraproject.org/server/download_, select your hardware architecture, and follow the instructions to download and verify the image.
|
||||
|
||||
|
|
@ -118,7 +118,7 @@ You can safely ignore the last command's warning about incorrectly formatted lin
|
|||
|
||||
=== Create a bootable installation medium
|
||||
|
||||
A installation on bare metal requires to transfer the installation file to a bootable media, mostly an USB memory stick. There are several option:
|
||||
An installation on bare metal requires transferring the installation file to bootable media, typically a USB memory stick. There are several options.
|
||||
|
||||
. As a (typically hands-off) server sysadmin, you can use the "Media Writer" graphical utility provided by the Fedora Project to accomplish this task. See https://docs.fedoraproject.org/en-US/quick-docs/creating-and-using-a-live-installation-image/#using-fedora-media-writer[Creating and using a live installation image - Using Fedora Media Writer] for guidance on using this program.
|
||||
|
||||
|
|
|
|||
|
|
@ -10,16 +10,16 @@ Peter Boy; Kevin Fenzi; Emmanuel Seyman
|
|||
This is the default method for manually installing Fedora if console access is available. The graphical interface is designed with the goal of making the installation as simple and speedy as possible. It is intended to facilitate the work of the system administrator by preassigning as many installation options as possible after analyzing the hardware.
|
||||
|
||||
|
||||
// Before publishin, comment out the warning.
|
||||
// Before publishing, comment out the warning.
|
||||
// Comment in again when start to update.
|
||||
//[WARNING]
|
||||
//====
|
||||
//
|
||||
//This documentsis not approved yet and may be incomplete and/or incorrect.
|
||||
// This document is not approved yet and may be incomplete and/or incorrect.
|
||||
|
||||
// *Status of this document*: Updated to f44.
|
||||
// ToDo:
|
||||
// * Update images from F41 toF44
|
||||
// * Update images from F41 to F44
|
||||
// * Update complete text
|
||||
//====
|
||||
|
||||
|
|
@ -53,7 +53,7 @@ Anaconda does not allow the installation to begin until all marked items have be
|
|||
|
||||
The default values assigned are usually acceptable. However, two items deserve the administrator's attention:
|
||||
|
||||
* __Keyboard__ in case on a non-US runtime environment
|
||||
* __Keyboard__ in case of a non-US runtime environment
|
||||
* __Network & Host Name__
|
||||
|
||||
[TIP]
|
||||
|
|
@ -78,7 +78,7 @@ __Non-US users__ should specifically check the keyboard layout. Selecting this i
|
|||
|
||||
=== Installation Source
|
||||
|
||||
In a standard installation (using the "Standard ISO image"), Anaconda uses "Local media" which will pull packages from the ISO image on your install media.
|
||||
In a standard installation (using the "Standard ISO image"), Anaconda uses "Local media" which will pull packages from the ISO image on your install media.
|
||||
|
||||
In a network installation select the item and edit the form appropriately.
|
||||
|
||||
|
|
@ -128,7 +128,7 @@ If you are satisfied with the Fedora Server default hard disk partitioning as de
|
|||
Fedora Server uses LVM by default and creates a Volume Group to enclose the root filesystem. The default name is `fedora`. When you first edit the network configuration and specify a custom hostname, it is appended, i.e. the VG name becomes `fedora_<hostname>`. This is often useful if managing multiple Fedora servers in a federation, as it avoids duplicate VG names. In any case, you can edit the Volume Group name later in _Installation Destination_.
|
||||
====
|
||||
|
||||
No further steps are required besides the disks already contain partitions and file systems. In this case you may want to select the option "Free up space by removing or shrinking existing partitions". Then select _Done_ in the upper bar and you are 'done'.
|
||||
No further steps are required beyond the disks that already contain partitions and file systems. In this case you may want to select the option "Free up space by removing or shrinking existing partitions". Then select _Done_ in the upper bar and you are 'done'.
|
||||
|
||||
====
|
||||
If you selected the option to free up space, a window will open after you click _Done_ giving you the opportunity to confirm to delete partitions and file systems to make space for your Fedora Server installation or to retain one or more partition.
|
||||
|
|
@ -144,11 +144,11 @@ image::installation/interactive-local-070.png[]
|
|||
|
||||
By clicking onto the + sign you can add partitions according to your storage concept.
|
||||
|
||||
Fedora uses a GPT partitioning scheme. Thus, on a BIOSboot system you must add a BIOSboot partion, preferrably as the first one. On a UEFIboot system you have to add a EFI system partition, preferrably as the first one. If you forget it, Anaconda will remind you.
|
||||
Fedora uses a GPT partitioning scheme. Thus, on a BIOSboot system you must add a BIOSboot partition, preferably as the first one. On a UEFIboot system you have to add an EFI system partition, preferably as the first one. If you forget it, Anaconda will remind you.
|
||||
|
||||
===== How to find out if firmware is efi-boot or bios-boot
|
||||
|
||||
Open a temporay shell by using `<alt>+<ctrl>+<F2>` and type into the terminal window:
|
||||
Open a temporary shell by using `<alt>+<ctrl>+<F2>` and type into the terminal window:
|
||||
|
||||
[source,console]
|
||||
----
|
||||
|
|
|
|||
|
|
@ -30,8 +30,8 @@ Performing an RDP installation requires an RDP client running on your workstatio
|
|||
The following RDP clients are available in __Fedora__:
|
||||
+
|
||||
--
|
||||
* __GNOME Connections__ – a remote desktop client for the GNOME desktop environment.
|
||||
* __freerdp__ – Free implementation of the Remote Desktop Protocol (RDP)
|
||||
* __GNOME Connections__ - a remote desktop client for the GNOME desktop environment.
|
||||
* __freerdp__ - Free implementation of the Remote Desktop Protocol (RDP)
|
||||
--
|
||||
+
|
||||
Use your desktop software installation program to install any of the clients listed above.
|
||||
|
|
@ -39,9 +39,9 @@ Use your desktop software installation program to install any of the clients lis
|
|||
For MacOS you may use one of the following options:
|
||||
+
|
||||
--
|
||||
* __Windows App__ – provided by Microsoft for free via App Store
|
||||
* __Jump Desktop__ – commercial application via App Store
|
||||
* __freerdp__ – Free implementation of the Remote Desktop Protocol installable via homebrew or macport
|
||||
* __Windows App__ - provided by Microsoft for free via App Store
|
||||
* __Jump Desktop__ - commercial application via App Store
|
||||
* __freerdp__ - Free implementation of the Remote Desktop Protocol installable via homebrew or macport
|
||||
--
|
||||
|
||||
== Booting the server
|
||||
|
|
@ -94,7 +94,7 @@ The system will initialize the installation program and start the necessary serv
|
|||
----
|
||||
Continue with __3.2. Connecting to the server__.
|
||||
|
||||
=== No Console access available – provide a kickstart medium
|
||||
=== No Console access available - provide a kickstart medium
|
||||
|
||||
You will need two usable USB ports or DVD drives on the server, one for the installation medium, one for a kickstart flash drive.
|
||||
|
||||
|
|
@ -131,7 +131,7 @@ $ sudo mount /dev/sdb1 /mnt
|
|||
|
||||
. Create and edit a kickstart file _ks.cfg_ in the root directory of the USB flash drive.
|
||||
+
|
||||
If possible, you should provide a static network configuration, so you'll know the IP address. If that isn't possible and DHCP is available, you can omit the “network” line. Anaconda will then use DHCP and display the address it receives.
|
||||
If possible, you should provide a static network configuration, so you'll know the IP address. If that isn't possible and DHCP is available, you can omit the "network" line. Anaconda will then use DHCP and display the address it receives.
|
||||
+
|
||||
[source,bash]
|
||||
----
|
||||
|
|
@ -150,7 +150,7 @@ With _Fedora 44_ you get some Python error messages you can ignore. It works any
|
|||
|
||||
Continue with __3.2. Connecting to the server__.
|
||||
|
||||
=== No console access available – patch installation medium
|
||||
=== No console access available - patch installation medium
|
||||
|
||||
If none of the above options work with your server and network configuration, you could patch the installation media as a last resort. As an example, you can change the grub boot lines in /isolinux/grub.conf. You would need to add the RDP parameter and remove the integrity test, as this is the default line but would fail after patching.
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ This guide offers a recommended checklist of tasks to ensure the safe and reliab
|
|||
|
||||
The following descriptions assume that the administrator is working at their workstation and accessing the server via SSH. However, most of the configuration instructions described can also be executed on the server console.
|
||||
|
||||
SSH is included by default on Linux and macOS. Windows 10 requires at least version 1809 or the additional program putty.
|
||||
SSH is included by default on Linux and macOS. Windows 10 requires at least version 1809, or the additional program PuTTY.
|
||||
|
||||
== Simplified access for the administrative account
|
||||
|
||||
|
|
@ -69,11 +69,11 @@ include::partial$installation/post-install/cockpit-secure-access.adoc[]
|
|||
|
||||
== Optionally: Set up root login via key file
|
||||
|
||||
Even if you activated root access during installation, you have hopefully kept the default option to restrict root to key file authentification. So you have to set up a key file prior to any ssh login. But be aware! You can still log in to Cockpit's web interface. Therefore, in this case, be sure to implement the additional security measures described in the previous chapter!
|
||||
Even if you activated root access during installation, you have hopefully kept the default option to restrict root to key file authentication. So you have to set up a key file prior to any ssh login. But be aware! You can still log in to Cockpit's web interface. Therefore, in this case, be sure to implement the additional security measures described in the previous chapter!
|
||||
|
||||
=== Prepare a pair of private / public keys
|
||||
|
||||
This step is to be performed only if a pair of keys does not already exist. It is best to create the key in the _.ssh_ directory of the desktop user. It should not be secured by password to enable automatic processing. The naming with leading 'id_' und trailing types abbreviation, e.g. '_rsa' is just a common convention, yet helpful.
|
||||
This step is to be performed only if a pair of keys does not already exist. It is best to create the key in the _.ssh_ directory of the desktop user. It should not be secured by password to enable automatic processing. The naming with leading 'id_' and trailing types abbreviation, e.g. '_rsa', is just a common convention, yet helpful.
|
||||
|
||||
a. Execute on the local desktop
|
||||
+
|
||||
|
|
@ -324,20 +324,20 @@ Depending on how you decided on data storage during installation, different supp
|
|||
|
||||
a. If you have chosen the _Default_ partitioning and are content with the basic principle of creating logical volumes for user and any other payload data, there is nothing to do at the moment. The creation of these logical volumes happens in the context of the installation of the corresponding application software.
|
||||
+
|
||||
You may ensure that the volume group – default name `fedora` – fills the complete disk. Using Cockpit, in the section `Storage` you see the available devices and their partitioning as well as Volume Group and Logical Volumes.
|
||||
You may ensure that the volume group (default name: fedora) fills the complete disk. Using Cockpit, in the section `Storage` you see the available devices and their partitioning as well as Volume Group and Logical Volumes.
|
||||
|
||||
b. If you have chosen the _Default_ partitioning but are _not content_ with the basic principle of creating Logical volumes for user and any other payload data but prefer to store everything in one big filesystem, you have now to extend the existing root logical volume to accomodate your data.
|
||||
b. If you have chosen the _Default_ partitioning but are _not content_ with the basic principle of creating Logical volumes for user and any other payload data but prefer to store everything in one big filesystem, you have now to extend the existing root logical volume to accommodate your data.
|
||||
+
|
||||
[CAUTION]
|
||||
====
|
||||
This is not a recommended procedure! Don't complain in case of issues.
|
||||
====
|
||||
+
|
||||
Cockpit provides an easy way for this. On the right side of the 'root' filesytem line select the 3 dot button. Choose _Grow_ for the logical volume. Determine the new size as needed.
|
||||
Cockpit provides an easy way for this. On the right side of the 'root' filesystem line select the 3 dot button. Choose _Grow_ for the logical volume. Determine the new size as needed.
|
||||
|
||||
c. If you have decided for a stricter _separation of system and payload data_ by using a separate volume group for each, you may have already created an additional partition and Volume Group in Anaconda. Otherwise you have to create it now.
|
||||
+
|
||||
Select `Storage` in Cockpit's main menu and then your drive in the right column. Select `Create new partition` and fill in the upcomming form accordingly. In the box "Devices" select from the Menu "Create LVM2 volume group" and fill in the upcomming form accordingly.
|
||||
Select `Storage` in Cockpit's main menu and then your drive in the right column. Select `Create new partition` and fill in the upcoming form accordingly. In the box "Devices" select from the Menu "Create LVM2 volume group" and fill in the upcoming form accordingly.
|
||||
|
||||
|
||||
|
||||
|
|
@ -397,7 +397,7 @@ You can view the status of LLMNR and mDNS with the following command: `sudo syst
|
|||
|
||||
== Manage system updates
|
||||
|
||||
It is common sense among system administrators,that regular installation of bug fixes and closing of security vulnerabilities is essential, i.e. applying updates in a systremtatic way. An important step is to automate the process as much as it is reasonable.
|
||||
It is common sense among system administrators that regular installation of bug fixes and closing of security vulnerabilities is essential; applying updates in a systematic way. An important step is to automate the process as much as it is reasonable.
|
||||
|
||||
// ===============================================================
|
||||
include::partial$installation/post-install/manage-dnf-updates.adoc[]
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ Peter Boy; Stephen Daley; Kevin Fenzi
|
|||
:revdate: 2026-04-28
|
||||
|
||||
[abstract]
|
||||
This Exkurs describes the configuration of a _software RAID_ as part of an interactive Fedora Server Edition installation. In this case, the RAID capability is provided by operating system drivers and processed bei the computer CPU. It does not cover firmware raid (also called Windows RAID), which provide this capability via the computer internal firmware, nor hardware raid, where dedicated integrated hardware modules or adapters completely relieve the computer CPU of the raid processing.
|
||||
This Exkurs describes the configuration of a _software RAID_ as part of an interactive Fedora Server Edition installation. In this case, the RAID capability is provided by operating system drivers and processed by the computer CPU. It does not cover firmware raid (also called Windows RAID), which provide this capability via the computer internal firmware, nor hardware raid, where dedicated integrated hardware modules or adapters completely relieve the computer CPU of the raid processing.
|
||||
|
||||
|
||||
The RAID configuraton starts at the "Installation Destination" window.
|
||||
|
|
@ -19,7 +19,7 @@ Before you start with partitioning, you have to determine the boot type of your
|
|||
|
||||
NOTE: Just in case you need a DOS/MBR partitioning scheme for some good reason, you can override the GPT default by adding "inst.mbr" to the kernel boot parameter at the initial boot screen.
|
||||
|
||||
If you don't know the type of your system for sure, you can check the system now. Open a temporay shell by using `<alt>+<ctrl>+<F2>` and type into the terminal window:
|
||||
If you don't know the type of your system for sure, you can check the system now. Open a temporary shell by using `<alt>+<ctrl>+<F2>` and type into the terminal window:
|
||||
[source,console]
|
||||
----
|
||||
# [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS
|
||||
|
|
@ -41,7 +41,7 @@ This way, you can and must perform each individual step of partitioning, configu
|
|||
+
|
||||
The advantage is that you can define every detail and you will get a partitioning exactly according to your plan. And the GUI supports the work very effectively.
|
||||
|
||||
Select all drives you want to include in the prospective RAID drive, click on the partitioning option you want to use and then on Done in the uper left corner.
|
||||
Select all drives you want to include in the prospective RAID drive, click on the partitioning option you want to use and then on Done in the upper left corner.
|
||||
|
||||
== Custom partitioning
|
||||
|
||||
|
|
@ -93,7 +93,7 @@ image:installation/sw-raid/120-custom-efi-1.png[]
|
|||
+
|
||||
Anaconda sets up an EFI partition on the first disk. But a RAID system must be able to boot from any of the available disks, not just the first one. Otherwise, the system would be paralyzed if that failed. One solution is to set up the EFI partition as a RAID as well.
|
||||
+
|
||||
Find the property Device Type and use the drop down list to change Standard partition to RAID. In the right side shows up a new selection box RAID level showing initially RAID1 (mirroring) in this example, because we have just 2 disks. Leave the file system as “EFI System Partition”. Choose an optional label, e.g. sysefi, and And trigger “Update Settings” further below.
|
||||
Find the property Device Type and use the drop down list to change Standard partition to RAID. In the right side shows up a new selection box RAID level showing initially RAID1 (mirroring) in this example, because we have just 2 disks. Leave the file system as “EFI System Partition”. Choose an optional label, e.g. sysefi, and trigger “Update Settings” further below.
|
||||
+
|
||||
.Final EFI system partition properties
|
||||
image:installation/sw-raid/125-custom-efi-2.png[]
|
||||
|
|
@ -115,7 +115,7 @@ image:installation/sw-raid/130-custom-finalbootform.png[]
|
|||
|
||||
. *Add a _root_ mount point*
|
||||
+
|
||||
Use the "+" sign to add another Moint Point
|
||||
Use the "+" sign to add another Mount Point
|
||||
+
|
||||
* select / as the mount point
|
||||
* enter 15 Gib as size
|
||||
|
|
@ -126,7 +126,7 @@ Anaconda creates a new mount point. From the context Anaconda guesses to assign
|
|||
.Anaconda generated LVM root volume and filesystem
|
||||
image:installation/sw-raid/140-custom-generated-root.png[]
|
||||
+
|
||||
Now you have the opportunity the adjust Anacondas guessings.
|
||||
Now you have the opportunity to adjust Anaconda's guesses.
|
||||
+
|
||||
The most important one is to adjust the RAID level. Anaconda configures a LVM without RAID by default. Tick the modify button of the LVM property.
|
||||
+
|
||||
|
|
@ -135,25 +135,25 @@ image:installation/sw-raid/145-custom-lvm-properties.png[]
|
|||
+
|
||||
Select a proper RAID level and check the size policy.
|
||||
|
||||
* _Automatic_ means that the size of the partition and the Volume Group is just as large as the Logical Volumes you create with Anaconda here. That provides you a maximum of flexibilty to later adjust the storage organisation but also involves some additional steps to handle the Volume Group and its partition when you want do add a Logical Volume and file system.
|
||||
* _Automatic_ means that the size of the partition and the Volume Group is just as large as the Logical Volumes you create with Anaconda here. That provides you a maximum of flexibility to later adjust the storage organization but also involves some additional steps to handle the Volume Group and its partition when you want do add a Logical Volume and file system.
|
||||
* _Maximum size_ expands the Volume Group to fill up the complete hard disk, so you can add Logical Volumes with a minimum of effort. That is the recommended way for medium size disks.
|
||||
* _Fixed size_ lets you specify a size that fulfills your foreseeable requirements and leaving some space for later adjustments that come up as a surprise.
|
||||
+
|
||||
This option also allows for an __even stronger separation of system and user data__. Specify a fixed size of 20-30 GiB for a system volume group (named e.g. fedora_sysvg). This contains the root file system and, if applicable, further system-related logical volumes. In the remaining space you will later set up a user volume group (correspondingly named fedora_usrvg) and logical volumes for user data. This gives you the greatest possible flexibility to adapt the system area to changes in demand or technical developments without touching the precious user data at all. This is recommended for large hard disks, servers with a planned longtime lifespan, or remotely located servers.
|
||||
|
||||
. *Customize the storage organisation to your requirements*
|
||||
. *Customize the storage organization to your requirements*
|
||||
+
|
||||
Finally, you can further customize the storage organization to your requirements.
|
||||
+
|
||||
Some adminmistrators like to confine the /var/log subdirectory in its own Logical Volume. This prevents excessive logging from filling up the root file system. But also vice versa, that excessive outputs of a program fill up the root file system to such an extent that no more log outputs can be saved and troubleshooting is made more difficult.
|
||||
Some administrators like to confine the /var/log subdirectory in its own Logical Volume. This prevents excessive logging from filling up the root file system. But also vice versa, that excessive outputs of a program fill up the root file system to such an extent that no more log outputs can be saved and troubleshooting is made more difficult.
|
||||
|
||||
Finally, click on Done, in the upcomming list accept the Changes and return now to the original guide, probably xref::installation/interactive-local.adoc#_networking[Fedora Server interactive local installation] guide.
|
||||
Finally, click on Done, in the upcoming list accept the Changes and return now to the original guide, probably xref::installation/interactive-local.adoc#_networking[Fedora Server interactive local installation] guide.
|
||||
|
||||
== Advanced Custom partitioning
|
||||
|
||||
Anaconda opens a new window:
|
||||
|
||||
.The advancced custom partitioning start up screen
|
||||
.The advanced custom partitioning start up screen
|
||||
image:installation/sw-raid/201-adv-custom-start.png[]
|
||||
|
||||
. *Check all disks for existing partitions*
|
||||
|
|
@ -230,7 +230,7 @@ image:installation/sw-raid/217-adv-custom-bootlist.png[]
|
|||
+
|
||||
Click into the free space on sda to activate it and tick the "+" sign again to open a new device form.
|
||||
+
|
||||
.Creating a system Volme Group partition
|
||||
.Creating a system Volume Group partition
|
||||
image:installation/sw-raid/220-adv-custom-syspv.png[]
|
||||
+
|
||||
Again, in the “Device type” selection box, select “Software RAID” and then fill out the rest of the form as indicated.
|
||||
|
|
@ -260,7 +260,7 @@ Double-click onto the syspv icon in the left bar to activate it and then on the
|
|||
.Partitions list including EFI, boot and physical volume partitions
|
||||
image:installation/sw-raid/224-adv-custom-sysvgform.png[]
|
||||
+
|
||||
Leave the Device type and Size field as is und enter "sysvg" into the Name field. Tick OK to submit the form.
|
||||
Leave the Device type and Size field as is and enter "sysvg" into the Name field. Tick OK to submit the form.
|
||||
+
|
||||
The overview list screen now shows a new Volume Group device "sysvg" beyond a new category "LVM".
|
||||
+
|
||||
|
|
@ -283,7 +283,7 @@ Either leave the suggested size value as it is to set up the entire free area fo
|
|||
.Partitions list including EFI, boot and physical volume partitions
|
||||
image:installation/sw-raid/234-adv-custom-usrvg.png[]
|
||||
+
|
||||
Leave the Device type and Size field as is und enter "usrvg" into the Name field. Tick OK to submit the form.
|
||||
Leave the Device type and Size field as is and enter "usrvg" into the Name field. Tick OK to submit the form.
|
||||
+
|
||||
The overview list screen now shows a new Volume Group device "sysvg" beyond a new category "LVM".
|
||||
+
|
||||
|
|
@ -297,7 +297,7 @@ As in the previous steps, clicking on symbol sysvg activates the unit for editin
|
|||
.Creating the ROOT file system
|
||||
image:installation/sw-raid/240-adv-custom-rootfsform.png[]
|
||||
+
|
||||
Leave the Device type and Avalable devices as is.
|
||||
Leave the Device type and Available devices as is.
|
||||
|
||||
* Specify the size of the root file system. A value of 12 GiB for the mere system files is large enough for the usual use cases and still has a lot of leeway for unusual situations.
|
||||
* Complete the other fields as indicated and tick OK.
|
||||
|
|
@ -312,14 +312,14 @@ Finally, you can further customize the storage organization to your requirements
|
|||
|
||||
* __Optional: Create a separate log file system__
|
||||
+
|
||||
Some adminmistrators like to confine the /var/log subdirectory in its own Logical Volume. This prevents excessive logging from filling up the root file system. But also vice versa, that excessive outputs of a program fill up the root file system to such an extent that no more log outputs can be saved and troubleshooting is made more difficult.
|
||||
Some administrators like to confine the /var/log subdirectory in its own Logical Volume. This prevents excessive logging from filling up the root file system. But also vice versa, that excessive outputs of a program fill up the root file system to such an extent that no more log outputs can be saved and troubleshooting is made more difficult.
|
||||
+
|
||||
As in the previous steps, clicking on symbol sysvg activates the unit for editing and clicking on the free area releases the plus sign. A click on the plus sign opens the dialogue for setting up a file system.
|
||||
+
|
||||
.Creating log file system
|
||||
image:installation/sw-raid/250-adv-custom-varlogform.png[]
|
||||
+
|
||||
Leave the Device type and Avalable devices as is
|
||||
Leave the Device type and Available devices as is
|
||||
+
|
||||
** Specify the size of the file system. A value of 3 or 5 GiB is usually large enough.
|
||||
** Complete the form as indicated
|
||||
|
|
@ -336,13 +336,13 @@ But sometimes they need to upload some data for further processing on the server
|
|||
+
|
||||
For a large number of users, use the user area, if available
|
||||
+
|
||||
** Select a siutable Volume Group, double-click on the device in the left column (sysvg or usrvg), and then into the free space to release the "plus" button.
|
||||
** Select a suitable Volume Group, double-click on the device in the left column (sysvg or usrvg), and then into the free space to release the "plus" button.
|
||||
+
|
||||
.Creating a home file system
|
||||
image:installation/sw-raid/260-adv-custom-usrhomeform.png[]
|
||||
|
||||
** Leave the Device type and Avalable devices as is
|
||||
** Specify a reasonable size of the home file system. For a system with only administravie users, a value of 3 or 5 GiB is usually large enough.
|
||||
** Leave the Device type and Available devices as is
|
||||
** Specify a reasonable size of the home file system. For a system with only administrative users, a value of 3 or 5 GiB is usually large enough.
|
||||
** Complete the form as indicated
|
||||
+
|
||||
.Storage overview including a home file system
|
||||
|
|
@ -357,8 +357,8 @@ According to the Filesystem Hierarchy Standard (FHS), a system should store site
|
|||
.Creating a srv file system
|
||||
image:installation/sw-raid/270-adv-custom-srvform.png[]
|
||||
|
||||
** Leave the Device type and Avalable devices as is.
|
||||
** Specify a reasonable size depending on your system plannings.
|
||||
** Leave the Device type and Available devices as is.
|
||||
** Specify a reasonable size depending on your system planning.
|
||||
** Complete the form as indicated.
|
||||
+
|
||||
.Devices list showing the srv file system
|
||||
|
|
@ -372,12 +372,12 @@ image:installation/sw-raid/274-adv-custom-srvlist.png[]
|
|||
.Creating a libvirt file system
|
||||
image:installation/sw-raid/280-adv-libvirtform.png[]
|
||||
|
||||
** Leave the Device type and Avalable devices as is.
|
||||
** Specify a reasonable size depending on your system plannings.
|
||||
** Leave the Device type and Available devices as is.
|
||||
** Specify a reasonable size depending on your system planning.
|
||||
** Complete the form as indicated.
|
||||
+
|
||||
.Devices list showing libvirt file system
|
||||
image:installation/sw-raid/284-adv-custom-libvirtlist.png[]
|
||||
|
||||
|
||||
Finally, click on Done, in the upcomming list accept the Changes and return now to the original guide, probably xref::installation/interactive-local.adoc#_networking[Fedora Server interactive local installation] guide.
|
||||
Finally, click on Done, in the upcoming list accept the Changes and return now to the original guide, probably xref::installation/interactive-local.adoc#_networking[Fedora Server interactive local installation] guide.
|
||||
Loading…
Add table
Add a link
Reference in a new issue