Deploying Cluster Bring-Up WEB Framework
This section describes how to deploy Cluster Bring-Up Web on a Linux machine.
Python 3.6 or greater is required on the host where the framework is to be deployed.
The system that runs the cluster bring-up framework must satisfy the following requirements:
- At least 4GB of memory
- At least 2 CPU cores
- At least 30GB of space
- Running Kubernetes
Supported Operating Systems
- CentOS 8 or later 64-bit (x86)
- Red Hat Enterprise Linux 8.2 or later 64-bit (x86)
- Ubuntu 20.04 or later 64-bit (x86)
Supported Deployment Platforms
NVIDIA currently supports running cluster bring-up framework as a containerized application using Docker images deployed to a Kubernetes cluster.
In the following sections, you'll find deployment details and instructions for a Kubernetes platform.
Deploying via Kubernetes
This section describes how to deploy Cluster Bring-Up WEB in Kubernetes cluster.
There are two supported modes of installation: Online installation and installation using an image.
This section details how to install the Cluster Bring-Up WEB in each mode.
Your machine must have Internet access to pull the container images and install the Python packages.
A Kubernetes deployment requires users to have access to a Kubernetes cluster. The kubectl command-line tool must also be configured to communicate with the cluster.
The following requirements must be met on the host where the framework is deployed:
- Kubernetes server 1.14 or greater
- kubectl 1.14 or greater
- Python 3.6 or greater
Follow the following steps to deploy the framework on a Kubernetes platform:
- Log into the installation machine as
- Ensure Kubernetes is installed.
- Untar the cluster bring-up package.
- Run the installation script.
Keep in mind that you may get an
ErrImagePull message which indicates that you have exceeded the pull rate limit. For more information about this issue, see Docker's article "Understanding Docker Hub Rate Limiting".
Installation with Image
This section shows how to install the and deploy the cluster-bring up in offline mode which requires the user to download and restore a machine image with most of the dependencies already located on the machine.
The following is a list of requirements that must be met:
- Clonezilla version 18.104.22.168
For offline installation, perform the following steps:
- Download the tar image file located here.
- Move the download file to the data center and untar the file.
- Restore the image on your machine via Clonezilla. See section Restore Image for procedure.
- Log into the installation machine as
rootuser with password
Make sure Kubernetes is running in
Change directory to the location of the installation script located under
Run the installation script with the
As part of the installation process, an image with Kubernetes and AWX-Operator already present must be restored on a machine. To restore, the Clonezilla software must be utilized.
Restore VM Using Hypervisor
The Clonezeilla restoration procedure can also be used for virtualization.
The following subsections provide the list of virtualization solutions that are supported.
Kernel-based Virtual Machine, or KVM, is a full virtualization solution for Linux on x86 hardware containing virtualization extensions. Using KVM, users can run multiple VMs running unmodified Linux or Windows images. Each VM has private virtualized hardware: A network card, disk, graphics adapter, etc.
The following is a list of required dependencies:
- virt-manager application
Follow these steps to restore the image on a VM. Each step has a name prepended to the step which indicated from which machine to perform the action:
On the machine running a hypervisor, check if there is enough space in the root and
On the machine running the hypervisor, download Clonezilla ISO and move it to the
- On the machine running the hypervisor, create a new directory in the
/imagesdirectory with the name of the newly created machine.
On the machine running the hypervisor, create a disk image with 65G.
On the machine running the hypervisor, open the Virtual Manager GUI.
- In the Virtual Manager GUI, click the "Create a virtual machine" icon on the top left.
- Create a new VM (5 steps):
- Select "Local install media".
- For "Choose ISO", select the Clonezilla ISO placed in
/tmp, uncheck "Automatically detect from the installation media", type and select the OS of choice (must be supported).
- Memory: 4096; CPUs: 2
- For "Select or create custom storage" and browse to the image disk created earlier.
- Type in a unique machine name and check the "Customize configuration before install" box
- Click "Finish".
- In the Virtual Manager GUI, change the boot order:
- Open the settings of the VM you are restoring on.
- Boot Options.
- Check the "Clonezilla CDROM" box and click the up arrow to move it up in the boot order.
- Click "Apply".
- After restarting the machine, the Clonezilla software will boot. Follow these steps to successfully restore the image:
- Clonezilla live
- Type the IP address of the machine where the clone is located.
- Port stays at "22" (default ssh).
- Keep "root" as user.
- Where to search:
- Type password to
- Mode: Beginner.
- Type in unique name.
- Yes, check
- In the Virtual Manager GUI, select "Change Boot Order" and place (SATA) disk image first instead of Clonezilla (CDROM).
- In the Virtual Manager GUI, select "Force off" and "Start VM".
After booting, log in as root.
(Restore) Change the name of the machine since it has the cloned machine name configured.
(Restore) If no Internet access is available on the machine, change the network interface in use.
- (Restore) Reboot machine → reboot.
Restore on Bare Metal
This section explains how to restore the image on a physical computer server.
ProLiant DL380p Gen8
- Connect to machine's remote management, ILO for HPE.
- Mount/add Clonezilla ISO via: Virtual Drives → Image File CDROM → Select Clonezilla ISO
- Reset the machine: Power Switch → Reset.
- Boot via Clonezilla ISO: Press F11 on startup → select CDROM Clonezilla ISO for boot.
- Continue from step 9 of section Restore on VM Machine to the end.
For additional information on HPE's remote management, visit HPE's support website.
The installation script,
install.sh, performs the following operations:
- Creates a new virtual environment for installation
- Ensures the dependencies for the installer are installed
- Deploys cluster bring-up WEB framework on Kubernetes platform
- Deploys cluster bring-up AWX framework on Kubernetes platform
- Configures AWX resources for cluster orchestration
The following options are available for the installation script:
|Specify path to hosts file that contains hostnames for the inventory|
|Specify host list expression that represents hostnames for the inventory|
|Specify hostname to be a member of the |
|Specify username to authenticate against the hosts|
|Specify password (encoded in base64) to authenticate against the hosts|
|Specify to run the installation script in offline mode. Supported only when using COT image.|
|Specify the path to the configuration file to incorporate into the installation|
In this example, 3 hosts named
ib-node-05 are added to the inventory.
In addition, the
ib-node-01 host configured to be a member of the
ib_host_manager group for the In-Band operations.
This section provides the required information to add a YAML configuration file during the installation process.
Currently, the configuration file only supports adding inventory variables so that they are included in the IB Cluster Inventory variable list when AWX loads for the first time.
The YAML file must consist of an
extra_variables parent key paired with a dictionary value. That dictionary must include an
inventory_vars key which also has its own dictionary value. It will consist of a list of key-value pairs that are added to the inventory variables.
YAML configuration file example:
In this example, there are two variables,
anotherVar, that will be added to the inventory variables list in AWX.
Example usage with the configuration file flag:
As seen in the picture above,
anotherVar have been added to the IB Cluster Inventory after AWX loads for the first time.
This section details the operations that could be performed once the installation process concludes.
The following code block demonstrates all the available actions:
The install and uninstall operations must be utilized via the
The update command allows updating certain components of the Cluster Bring-up Tool.
The update command relies on the
cot_dir argument, which refers to the path of the folder extracted from the
tar.gz file given .
Specify the path of the folder extracted from the new
The tool uses the data inside the folder as the new data for the update operation.
|Update the ansible playbooks|
|Update the AWX templates (job templates and workflows). This updates the ansible playbooks as a pre-task.|
|Update the COT client (on the |
|Get AWX URL and credentials|
|Get file server URL and files folder|
|Get the REST API URL|