From e08d1faa8b2e820652a04c74eeaa442d19a35308 Mon Sep 17 00:00:00 2001 From: Mark Gurevich Date: Mon, 21 Feb 2022 14:13:54 -0500 Subject: [PATCH] Modify docs to describe how to add extra drivers/modules for discovery --- .../manage_clusters/ppc64le/discovery/index.rst | 3 +++ .../source/references/coral/known_issues/genesis_base.rst | 8 +++++--- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/index.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/index.rst index 61de0fdc5..85187a5af 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/index.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/index.rst @@ -15,9 +15,11 @@ xCAT provides several *automatic hardware discovery* methods to assist with hard manually_define.rst manually_discovery.rst +.. note:: You can optionaly add drivers or modules to the network boot image used during the discovery: :doc:`xCAT Genesis Base ` Following are the brief characteristics and adaptability of each method, you can select a proper one according to your cluster size and other consideration. + * **Manually Define Nodes** Manually collect information for target servers and manually define them to xCAT **Node Object** through ``mkdef`` command. @@ -82,3 +84,4 @@ Following are the brief characteristics and adaptability of each method, you can You have to strictly boot on the node in order if you want the node has the expected name. Generally you have to waiting for the discovery process finished before power on the next one. + diff --git a/docs/source/references/coral/known_issues/genesis_base.rst b/docs/source/references/coral/known_issues/genesis_base.rst index 8476841cd..a1715acb4 100644 --- a/docs/source/references/coral/known_issues/genesis_base.rst +++ b/docs/source/references/coral/known_issues/genesis_base.rst @@ -3,19 +3,21 @@ xCAT Genesis Base xCAT ships a ``xCAT-genesis-base`` package as part of xcat-deps. This is a light-weight diskless linux image based currently on Fedora28, that is used by xCAT to do hardware discovery. -To build your own version of the ``xCAT-genesis-base`` on-site using a server running OS other than Fedora28, like Red Hat Enterprise Linux 8, follow the steps below. Building ``xCAT-genesis-base`` on a server running Red Hat Enterprise Linux 7 or earlier, is no longer supported. +Follow the steps below to build your own version of the ``xCAT-genesis-base`` on-site. Your can include additonal drivers or modules or you can build your own version of the ``xCAT-genesis-base`` on-site using a server running OS other than Fedora28, like Red Hat Enterprise Linux 8. Building ``xCAT-genesis-base`` on a server running Red Hat Enterprise Linux 7 or earlier, is no longer supported. 1. Download the latest timestamp version of the ``xCAT-genesis-builder`` RPM provided here: http://xcat.org/files/xcat/xcat-dep/2.x_Linux/beta/ 2. Install the ``xCAT-genesis-builder`` RPM on a node installed with desired OS (currently verified with Fedora28 and Red Hat Enterprise Linux 8). For more details: https://github.com/xcat2/xcat-core/tree/master/xCAT-genesis-builder#readme -3. Build the ``xCAT-genesis-base`` RPM: :: +3. If additional drivers or modules need to be loaded when genesis kernel boots, edit ``xCAT-genesis-builder/xcat-cmdline.sh`` and add ``modprobe`` statements for each one. + +4. Build the new ``xCAT-genesis-base`` RPM: :: /opt/xcat/share/xcat/netboot/genesis/builder/buildrpm To use the generated RPM from the step above for node discovery: -1. Install the generated ``xCAT-genesis-base`` RPM on the xCAT Management node +1. Uninstall the old ``xCAT-genesis-base`` RPM and install the newly built ``xCAT-genesis-base`` RPM on the xCAT Management node 2. Execute: ``mknb ppc64`` 3. Follow :doc:`discover nodes `