Install - Prerequisites & Preparation

This section details prerequisites for a successful implementation of KumoScale in Appliance mode. You should not proceed with an installation until you have verified that your environment supports these requirements.

Hardware Requirements

KumoScale software may be installed on any of the server and network configurations defined in the KumoScale Hardware Compatibility List (HCL).

Installation Device

KumoScale software supports deployment on platforms with either SATA drives or NVMe drives. By default, SATA drive(s) is/are used for installation. NVMe drive(s) will be used if no SATA drive is available. The installation devices are formatted as mirrored (RAID-1) devices if at least two drives are available. Otherwise, the installation is done on the single drive. More installation device options can be found under the Installation Command Line Parameters of Single Node Deployment and Multinode Production.

NOTE: We recommend using two SATA SSDs as installation media.

 Network and Environment Requirements

NOTE: KumoScale storage node installation is supported only on platforms that are configured for UEF

There are three ways you can boot into the image depending on the device you choose:

Network Installation: This is the preferred installation method when installing a large number of nodes. It works when installing remotely. This installation requires a TFTP/DHCP PXE server that supports DNS, HTTP / HTTPS / FTP services on the installation site.

Virtual CD Installation: This option should be used when a PXE server is not available, and only remote access is available to the setup. It requires a way to transfer files over the network such as a WebDAV server, TFTP server etc. The Virtual CD is a remote server containing the image and must be accessible from either the Baseboard Management Controller (BMC), iLO or iDRAC of the server.

USB Installation: This method installs the image directly on a server using a USB drive. This option is typically chosen when installing on a small number of nodes, or when a PXE server is not available. This method does not assume any special conditions.

WARNING: Do not connect the bootable USB drive to a production server, since it might delete its content without a prior warning

Configuration Requirements

In order to configure storage nodes, you will need your license key. Details on how the storage cluster should be configured in your environment, and a remote host with the kubectl tool are provided below.

License Key

You will need a copy of the license key file provided to you by KIOXIA in order to configure the storage nodes.

Number of Masters

A KumoScale storage cluster is optimally configured with an odd number of masters on the same subnet. For single node deployments, one (1) master is sufficient. High Availability (HA) systems should contain at least three (3) masters. Table 1. KumoScale Cluster Configurations shows possible cluster configurations.

Note: The master nodes must all be on the same subnet.

Table 1. KumoScale Cluster Configurations

Cluster size

Number of Master Nodes

Number of Worker Nodes

Deployment Environment

1

1

0

No resiliency

3

3

0

 

4

3

1

Odd number of masters

5

5

0

Best practice

More than 5

5

1+

 

The number of master nodes is specified when you install the first node. If the number of master nodes is specified as, say, three, then the first three nodes installed are master nodes. All nodes added after that are configured as worker nodes. You may add nodes to your KumoScale cluster at any time. Note that it is possible to prevent a node from joining as a master node (see Custom Requirements for the Masters below).

VIP for the First Master

The KumoScale storage cluster has a Virtual IP Address (VIP Address). It is defined when you install KumoScale software on the very first node (details are in Installation Command Line Parameters). However, as noted earlier, all master nodes must be on the same subnet so a node will join as a master only if it is on the same subnet as the first master.

Custom Requirements for the Masters

KumoScale enables you to specify requirements for when a node can join as a master of the KumoScale storage cluster. These restrictions need to be provided when configuring the Master CR. In particular you will need to select whether you want a node to join only when there is affinity or antiaffinity or neither. You cannot have both. The default setting is neither.

Affinity: the node meets a certain set of requirements such as it is located in a specific rack, or it has a particular name.

Antiaffinity: the node does not meet a certain set of requirements such as it is NOT located in a specific rack.

You will express this in the Master CR at Configure the first master for the KumoScale storage cluster. You will need the information gathered in this section. Examples of syntax are provided in that section.

Administrative Host with Support for Kubernetes kubectl

For security reasons, users are not given direct access to the storage cluster or storage nodes. All post-install steps are executed on your Windows™/OS X/Linux™ host that can connect to the KumoScale master node via over the network and supports the Kubernetes command-line tool, kubectl. Ensure that you have access to a host with this tool before starting the installation. This is your administrative host.

To install kubectl on your administrative host, please follow the steps here.

 

For multinode deployment, Next: Install: Multinode/Production

For single node deployment, Next: Install: Singlenode