硬件要求

下表概述了 x86-64、ARM、ppc64le 和 s390x 体系结构上的 SUSE Multi-Linux Manager 服务器与代理的硬件和软件要求。

基于 ppc64le 或 s390x 体系结构的 SUSE Multi-Linux Manager 安装无法使用安全引导来引导网络客户端。存在此限制是因为 shim 引导加载程序不适用于这两种体系结构。

有关 SUSE Multi-Linux Manager for Retail 硬件要求，请参见 Retail Requirements。

1. 服务器要求

容器主机的操作系统为 SL Micro 6.2 或 SUSE Linux Enterprise Server 15 SP7。

在下文中，仅当 SUSE Linux Enterprise Server 作为已安装的主机操作系统会产生影响时，才会明确提及该系统；否则，我们将使用 SL Micro 或直接统称“主机操作系统”。

操作系统为 SL Micro 的容器主机的可用磁盘空间要求如下：

至少 100 GB 用于基础安装
再加上至少 130 GB 用于储存库数据

使用 SUSE Linux Enterprise Server 操作系统时，所需的磁盘空间可能要多很多，具体取决于所选软件的数量。

By default the SUSE Multi-Linux Manager Server container stores mirrored repository (packages or products), database, and other data in subdirectories of the /var/lib/containers/storage/volumes/ directory. Repository synchronization fails if this directory runs out of disk space. Estimate how much space the /var/lib/containers/storage/volumes/ directory requires based on the number and kind of clients and repositories you plan to mirror.

有关文件系统和分区细节的详细信息，请参见永久性存储和权限和本指南的安装和部署相关章节中的详细安装说明。

Table 1. 服务器硬件要求
Hardware	Details	Recommendation
CPU	x86-64, ARM, ppc64le or s390x	Minimum 4 dedicated 64-bit CPU cores
RAM	Minimum	16 GB
	Recommended	32 GB
Disk Space	`/` (root directory)	40 GB
	`/var/lib/containers/storage/volumes`	Minimum 150 GB (depending on the number of products)
	`/var/lib/containers/storage/volumes/var-pgsql`	Minimum 50 GB
Swap space	Systems can benefit from additional swap space. SUSE recommends using a swap file instead of a swap partition. For more information about swap space, see 交换空间.	8 to 12 GB

The images by default have a 40 GB / partition. The cloud image of SL Micro 6.2 has just a 5 GB / partition. Both work flawlessly with SUSE Multi-Linux Manager. As long as external storage is mounted to /var/lib/containers/storage/volumes, SUSE Multi-Linux Manager does not need or use storage on the / partition, but leaves that to the management of the container host itself.

SUSE Multi-Linux Manager 性能取决于硬件资源、网络带宽、客户端与服务器之间的延迟，等等。

根据所用体验和部署方式的不同，SUSE Multi-Linux Manager 服务器与足够数量的代理配套使用时，建议每个服务器处理的客户端不要超过 10,000 个，以便获得最佳性能。当客户端数量超过 10,000 个时，强烈建议改为使用集线器设置并咨询相关专业人员。即使优化了设置并配备了充足的代理，数量如此庞大的客户端也可能导致发生性能问题。

有关如何管理大量客户端的详细信息，请参见 Multiple Servers with Hub to Manage Large Scale Deployments。

2. 代理要求

容器主机的操作系统为 SL Micro 6.2 或 SUSE Linux Enterprise Server 15 SP7。

最低要求适用于快速测试安装，例如包含一个客户端的代理。如果您想要使用生产环境，请使用建议的值开始操作。

Table 2. 代理硬件要求
Hardware	Details	Recommendation
CPU	x86-64, ARM	Minimum 2 dedicated 64-bit CPU cores
	Recommended	The same as minimum values
RAM	Minimum	2 GB
	Recommended	8 GB
Disk Space	`/` (root directory)	Minimum 40 GB
	`/var/lib/containers/storage/volumes`	Minimum 100 GB
Swap space	Systems can benefit from additional swap space. SUSE recommends using a swap file instead of a swap partition. For more information about swap space, see 交换空间.	4 to 8 GB

By default the SUSE Multi-Linux Manager Proxy container caches packages in the /var/lib/containers/storage/volumes/uyuni-proxy-squid-cache/ directory. If there is not enough space available, the proxy will remove old, unused packages and replace them with newer packages.

鉴于这种行为：

The larger /var/lib/containers/storage/volumes/uyuni-proxy-squid-cache/ directory is on the proxy, the less traffic will be between the proxy and the SUSE Multi-Linux Manager Server.
By making the /var/lib/containers/storage/volumes/uyuni-proxy-squid-cache/ directory on the proxy the same size as /var/lib/containers/storage/volumes/var-spacewalk/ on the SUSE Multi-Linux Manager Server, you avoid a large amount of traffic after the first synchronization.
The /var/lib/containers/storage/volumes/uyuni-proxy-squid-cache/ directory can be small on the SUSE Multi-Linux Manager Server compared to the proxy. For a guide to size estimation, see the 服务器要求 section.

In general, SUSE recommends to adjust the value for the cache directory to about 80 % of available free space. The cache_dir value is set when generating proxy configuration on the server. You cannot set the option directly in squid.conf.

3. 交换空间

不同系统的工作负载各不相同。无论 RAM 总容量是多少，对于工作负载较大或波动不定的系统而言，额外配置交换空间均有助于提升性能。建议将交换空间部署在可用的最快存储设备上（例如 SSD）。SUSE 建议使用交换文件而非交换分区。

有关交换空间大小建议，请参见上文表格。

以下外壳命令片段可创建一个 8GiB 大小的交换文件。

A swap file on BtrFS filesystem prevent creating of a snapshot of that volume. /var in the following example is already excluded from the snapper snapshots, so it is safe to use /var/swap.

## setup swapfile at /var/swap
# run following as a root user

# allocate 8GiB for swap file
fallocate -l 8G /var/swap
# ensure CoW is disabled for the swap file
chattr +C /var/swap
# allow only root access
chmod 600 /var/swap
# make swap file based on allocated file
mkswap /var/swap
# activate swap use for the running system
swapon /var/swap
# activate swap during the next boots
echo "/var/swap swap swap defaults 0 0" >> /etc/fstab

4. 数据库要求

PostgreSQL 是唯一受支持的数据库。不支持使用远程 PostgreSQL 数据库或装有 PostgreSQL 数据库的远程文件系统（例如 NFS）。换句话说，PostgreSQL 应该位于 SUSE Multi-Linux Manager 可用的最快的存储设备上。

由于存在潜在性能问题，我们不建议从 SUSE Multi-Linux Manager 远程运行 PostgreSQL 数据库。虽然这种环境在很多情况下是可行的甚至非常稳定，但如果发生问题，始终存在丢失数据的风险。

如果发生这种情况，SUSE 可能无法提供帮助。

5. 永久性存储和权限

默认情况下，在部署容器时会创建永久性卷。

但建议您将卷存储在一个或多个单独的存储设备上。这种设置有助于避免生产环境中丢失数据。此操作可在部署容器后再进行。

最好在首次部署容器之后设置存储设备。有关更多细节，请参见永久性容器卷。

我们建议使用 XFS 作为所有卷的文件系统类型。用于存储储存库的磁盘大小取决于您要使用 SUSE Multi-Linux Manager 管理的发行套件和通道数目。请参见本节中的表格来估算所需大小。

请勿为 Cobbler 或 PostgreSQL 使用 NFS 格式的存储空间，此外在 SELinux 环境中也不要使用 NFS。这些场景不受支持。

在 SUSE Multi-Linux Manager 服务器上，使用以下命令找到所有可用的存储设备：

hwinfo --disk | grep -E "Device File:"

Use the lsblk command to see the name and size of each device.

Use the mgr-storage-server command with the device names to set up the external disks as the locations for the storage and, optionally on a disk of its own, for the database:

mgr-storage-server <storage-disk-device> [<database-disk-device>]

例如：

mgr-storage-server /dev/nvme1n1 /dev/nvme2n1

The external storage volumes are set up as XFS partitions mounted at /manager_storage and /pgsql_storage.

This command will create the persistent storage volumes at /var/lib/containers/storage/volumes.

有关详细信息，请参见永久性容器卷。

It is possible to use the same storage device for both channel data and the database. This is not recommended, as growing channel repositories might fill up the storage, which poses a risk to database integrity. Using separate storage devices may also increase performance. If you want to use a single storage device, run mgr-storage-server with a single device name parameter.

If you are installing a proxy, the mgr-storage-proxy command takes only one device name parameter and will set up the external storage location as the Squid cache.

6. 逻辑卷管理 (LVM)

对于所有类型的虚拟机 (VM)，通常都不需要 LVM，也不建议使用。磁盘设置是虚拟的，因此卷可以使用单独的磁盘，这也是建议的做法。

对于其他部署，也建议为卷使用单独的磁盘。

On the container host of the SUSE Multi-Linux Manager Server, the mgr-storage-server command moves the complete content of the /var/lib/containers/storage/volumes directory to a separate disk and remounts it to /var/lib/containers/storage/volumes.

Optionally, if a second device name is specified, mgr-storage-server moves the content of the /var/lib/containers/storage/volumes/var-pgsql database directory to a second separate disk and remounts it to /var/lib/containers/storage/volumes/var-pgsql.

Similarly, on the container host of the SUSE Multi-Linux Manager Proxy, the mgr-storage-proxy command moves the complete content of the /var/lib/containers/storage/volumes directory to a separate disk and remounts it to /var/lib/containers/storage/volumes.