Before proceeding with this step, you must create an Inventory and Configuration file. If you are unsure how to do this, see the example instructions below.
This section discusses the following main topics:
- Creating an Inventory or Configuration File
- Kernel Upgrade
- Nauta Installation
- Installation Script Options
- Access Files for the kubectl Client
- Upgrading Nauta Procedure
The Inventory file defines where your master and worker nodes reside, and how to access them. The Configuration file defines your proxy settings, network quirks, and file system preferences. Should you need to create an Inventory and/or Configuration follow the instructions below.
To create Nauta's Inventory file, do the following:
-
Copy the Inventory file example information: Inventory File Information.
-
Modify the newly created Inventory file to suit your needs using your favorite text editor (vi for example).
To modify Nauta's Configuration file to define your proxy, network quirks, and file system preferences. To create the configuration file, follow these steps:
-
Copy the Configuration file example information: Configuration File Information.
-
Modify the newly created Configuration file to suit your needs using your favorite text editor (vi for example).
If you run Linux kernel prior to 4.x version, it is recommended that you upgrade the kernel on all nodes of a cluster before performing a platform installation.
Running heavy training jobs on workers with the operating system kernel older than 4.x may lead to hanging the worker node.
- Refer to Red Hat Bugzilla – Bug 1507149 for more information.
This may occur when a memory limit for a training job is set to a value close to the maximum amount of memory installed on this node. These problems are caused by errors in handling memory limits in older versions of the kernel.
The following kernel was verified as a viable fix for this issue (see link below).
To install the new kernel refer to CHAPTER 5. MANUALLY UPGRADING THE KERNEL in Red Hats Kernel Administration Guide.
Note: The above kernel does not include Red Hat's optimizations and hardware drivers.
BTo install Nauta, follow these steps.
To install Nauta, follow these steps:
- Set the following environment variables that point to the configuration and inventory file on the Installer Machine.
-
ENV_INVENTORY (mandatory): Inventory file location, for example:
export ENV_INVENTORY=<absolute path to inventory file> -
ENV_CONFIG (mandatory): Configuration file location, for example:
export ENV_CONFIG=<absolute path to config file>
-
Run the installation:
./installer.sh install
Invoke ./installer.sh with one of the following options:
- install: Use this option to install Kubernetes and Nauta as part of your installation.
- platform-install: Use this option to install Kubernetes only.
- nauta-install: Use this option to install Nauta only.
- Note: If you select this option, it is assumed that Kubernetes is already installed. In addition, this requires the same procedure for Nauta upgrades (see below).
- nauta-upgrade: Nauta installation upgrade (see Nauta Installation Process for Nauta upgrade procedures).
Nauta is installed on cluster nodes in the following folders: /opt/nauta,/usr/bin, /etc/nauta-cluster
On your Installer Machine, the following files are created in the Installation folder. These files are access files used to connect to the cluster using kubectl client.
As an output of Kubernetes installation, platform-admin.config file is created and the installation log is written into the log folder in the main installation directory:
platform-admin.config - cluster admin config file
As an output of the Nauta installation, As an output of Kubernetes installation, platform-admin.config file is created and the installation log is written into the log folder in the main installation directory:
nauta-admin.config - NAUTA admin config file
As an administrator, you may be required to upgrade Nauta to gain new features, implement new networking configurations, or stay up-to-date with current versions, and so on.
To upgrade Nauta, do the following:
- Set the following environment variables that point to the configuration, inventory and configuration file on the Installer Machine:
-
ENV_INVENTORY (mandatory): Inventory file location, for example:
export ENV_INVENTORY=<absolute path to inventory file> -
ENV_CONFIG (mandatory): Configuration file location, for example:
export ENV_CONFIG=<absolute path to config file> -
NAUTA_KUBECONFIG (mandatory): Nauta admin file location, for example:
export NAUTA_KUBECONFIG=<absolute path to nauta-admin.config file>
-
Call the installer with nauta-upgrade option:
./installer.sh nauta-upgrade
Note: It is recommended that you do not use the cluster during an upgrade.
-
After successful execution of platform upgrade you need to also upgrade all users by running:
nctl user upgrade
Note: This command can be run only by an administrator.
This completes the Nauta Upgrade Process.