From 7a717065e0b8d60874f13cc6e611ebe3c2046fc7 Mon Sep 17 00:00:00 2001 From: Martin Tzvetanov Grigorov Date: Wed, 13 Dec 2023 10:59:21 +0200 Subject: [PATCH] Add chapter 2 - Base Operating System (BOS) Signed-off-by: Martin Tzvetanov Grigorov --- .../install/quarto/_quarto-english.yml | 50 ++++++++++++++----- docs/recipes/install/quarto/_quarto.yml | 1 + .../content/baseOS/BaseOperatingSystem.qmd | 14 ++++++ docs/recipes/install/quarto/guide.qmd | 13 +---- 4 files changed, 53 insertions(+), 25 deletions(-) create mode 100644 docs/recipes/install/quarto/content/baseOS/BaseOperatingSystem.qmd diff --git a/docs/recipes/install/quarto/_quarto-english.yml b/docs/recipes/install/quarto/_quarto-english.yml index 93521ef4ce..f9941783c8 100644 --- a/docs/recipes/install/quarto/_quarto-english.yml +++ b/docs/recipes/install/quarto/_quarto-english.yml @@ -6,20 +6,21 @@ ohpc: introduction: title: Introduction contents: | - This guide presents a simple cluster installation procedure using components +

This guide presents a simple cluster installation procedure using components from the {{< meta ohpc.openhpc >}} software stack. {{< meta ohpc.openhpc >}} represents an aggregation of a number of common ingredients required to deploy and manage an HPC Linux* cluster including provisioning tools, resource management, I/O clients, development tools, and a variety of scientific libraries. These packages have been pre-built with HPC integration in mind while conforming to common \Linux{} - distribution standards. - The documentation herein is intended to + distribution standards.

+ +

The documentation herein is intended to be reasonably generic, but uses the underlying motivation of a small, 4-node \iftoggleverb{isxCATstateful} stateful \else stateless \fi cluster installation to define a step-by-step process. Several optional customizations are included and the intent is that these collective - instructions can be modified as needed for local site customizations. + instructions can be modified as needed for local site customizations.

base_edition: | **Base Linux Edition**: this edition of the guide highlights installation without the use of a companion configuration management system and @@ -95,16 +96,39 @@ ohpc: used throughout this recipe are presented below. Note that while the example definitions above correspond to a small 4-node compute subsystem, the compute parameters are defined in array format to accommodate logical extension to larger node counts. + bos: + title: Install Base Operating System (BOS) + paragraph1: | +

In an external setting, installing the desired BOS on a + *master* SMS host typically involves booting from a DVD ISO image on a new + server. With this approach, insert the {{< meta ohpc.baseOS >}} DVD, power cycle the host, and + follow the distro provided directions to install the BOS on your chosen {*master*} host. + Alternatively, if choosing to use a pre-installed server, please + verify that it is provisioned with the required {{< meta ohpc.baseOS >}} distribution.

+ +

Prior to beginning the installation process of {{< meta ohpc.OHPC >}} components, several additional + considerations are noted here for the SMS host configuration. First, + the installation recipe herein assumes that + the SMS host name is resolvable locally. Depending on the manner in which you + installed the BOS, there may be an adequate entry already defined + in **/etc/hosts**. If not, the following addition can be used to identify + your SMS host.

+ paragraph2: | +

While it is theoretically possible to enable SELinux on a cluster provisioned + with {{< meta ohpc.provisioner >}}, + doing so is beyond the scope of this document. Even the use of + permissive mode can be problematic and we therefore recommend disabling SELinux on the + *master* SMS host. If SELinux components are installed locally, + the *selinuxenabled* command can be used to determine if SELinux is + currently enabled. If enabled, consult the distro documentation for information + on how to disable.

+ +

Finally, provisioning services rely on DHCP, TFTP, and HTTP network protocols. + Depending on the local BOS configuration on the SMS host, default firewall + rules may prohibit these services. Consequently, this recipe assumes that the local + firewall running on the SMS host is disabled. If installed, the default + firewall service can be disabled as follows:

- level1: - heading: An English heading - text: Level 1 text - level2: - heading: Level 2 heading - text: Level 2 text - level3: - heading: Level 3 heading - text: Level 3 text title: clusterBuildingRecipes: Cluster Building Recipes baseOsSuffix: Base OS diff --git a/docs/recipes/install/quarto/_quarto.yml b/docs/recipes/install/quarto/_quarto.yml index 3c5fd582a9..5043d299fe 100644 --- a/docs/recipes/install/quarto/_quarto.yml +++ b/docs/recipes/install/quarto/_quarto.yml @@ -31,6 +31,7 @@ format: # OpenHPC specific metadata that is applicable to all profiles ohpc: openhpc: OpenHPC + OHPC: OpenHPC revision: 3.x version: 3.1 # Define package manager commands diff --git a/docs/recipes/install/quarto/content/baseOS/BaseOperatingSystem.qmd b/docs/recipes/install/quarto/content/baseOS/BaseOperatingSystem.qmd new file mode 100644 index 0000000000..78fc1d6ede --- /dev/null +++ b/docs/recipes/install/quarto/content/baseOS/BaseOperatingSystem.qmd @@ -0,0 +1,14 @@ +# {{< meta ohpc.content.bos.title >}} + +{{< meta ohpc.content.bos.paragraph1 >}} + +```bash +[sms]# echo ${sms_ip} ${sms_name} >> /etc/hosts +``` + +{{< meta ohpc.content.bos.paragraph2 >}} + +```bash +[sms]# systemctl disable firewalld +[sms]# systemctl stop firewalld +``` \ No newline at end of file diff --git a/docs/recipes/install/quarto/guide.qmd b/docs/recipes/install/quarto/guide.qmd index 96658a4bb1..d1bf20775b 100644 --- a/docs/recipes/install/quarto/guide.qmd +++ b/docs/recipes/install/quarto/guide.qmd @@ -7,15 +7,4 @@ toc-depth: 5 {{< include content/introduction.qmd >}} -# {{< meta ohpc.content.level1.heading >}} - -{{< meta ohpc.content.level1.text >}} - -## {{< meta ohpc.content.level2.heading >}} - -{{< meta ohpc.content.level2.text >}} - -### {{< meta ohpc.content.level3.heading >}} - -{{< meta ohpc.content.level3.text >}} - +{{< include content/baseOS/BaseOperatingSystem.qmd >}}