Kinetica Installation with KAgent

Cards

Preferred

The cards below have been tested in large-scale production environments and provide the best performance for the database.

Supported

The cards below are supported for Kinetica but should only be used for smaller, testing workloads or as necessary.

Cluster

1. Enter a name for the cluster. The name cannot contain spaces or underscores.

2. Optionally, select one or more of the following packages:

   • Select Core if node(s) in the cluster should have the core database functionality installed on them.

     Important

     First-time setups should always have Core selected.

   • Select etcd if node(s) in the cluster should have etcd installed on them.

     Important

     The etcd package is required for the following:

     • cluster status reporting via KAgent and GAdmin
     • high availability
     • cluster monitoring

   • Select Graph if a node in the cluster should have the graph server installed on it. See Network Graphs & Solvers Concepts for more information.

   • Optionally, select to install AAW (Active Analytics Workbench) if a node should have AAW installed on it. See Active Analytics Workbench for more information.

   • Optionally, select to install KAgent if a node should also have KAgent installed on it. See KAgent for more information.

   • Optionally, select to install RabbitMQ if setting up a ring for High Availability. Review High Availability Architecture and High Availability Configuration & Management for more information.

3. For the Install Mode, select either Online (install directly from the online Kinetica repository) or Offline (install from uploaded packages). If Offline is selected, click Upload Packages, then upload a package file for each component or driver desired for the installation.

   Important

   If performing an offline installation, all necessary dependencies will need to be installed prior to cluster setup.

   

4. For the Version, select either CUDA (GPU) or Intel (CPU-only) to determine the package variant to install.

5. If the Version is set to CUDA, ensure Automatically install Nvidia driver is selected. This will automatically configure the server(s) for an Nvidia GPU driver and install the most compatible driver.

6. Enter the license key.

7. Optionally, provide an external files directory for use with external tables to override the default external files directory parameter value.

8. If AAW is selected to install, select a K8 Setup:

   • Automatic -- KAgent will install Kubernetes / KubeCTL and upload a default configuration file.

     Important

     Before installing the embedded Kubernetes cluster, review the Kubernetes Considerations.

   • Custom -- Upload a configuration file for an already existing Kubernetes installation and provide a public IP address for the server hosting the Kubernetes installation. Note that AAW requires Kubernetes; see Active Analytics Workbench (AAW) Overview for more information.

9. Click Next.

Deployment

1. Select the On Premise deployment method, and click Next.

   Important

   If clearing the Open Firewall Ports checkbox, the firewall then must be configured manually to allow the required ports listed in the default ports table. Consult Adjust Firewall for tips on configuring the firewall.

Security

1. Enter and confirm an Admin Password. It must meet the password strength requirements.

   Important

   This is the password used to access Reveal, Active Analytics Workbench (AAW), KAgent, and GAdmin as the default Admin user.

2. Select an SSL Mode:

   • Cert/key setup not required -- Kinetica will not require SSL certificate/key creation/upload and SSL will not be enabled
   • User-provided cert/key per node -- user must upload an SSL certificate and key for each node; Kinetica copies the cert/key pair to /opt/gpudb/certs, enables HTTPD, and configures HTTPD to use HTTPS
   • Generate self-signed cert/key per node -- KAgent generates a self-signed certificate and key for each node and places it in /opt/gpudb/certs, enables HTTPD, and configures HTTPD to use HTTPS

3. Select an Authentication type and fill the fields as necessary:

   • None -- no authentication or authorization
   • LDAP -- configures Kinetica to authenticate via LDAP; requires authentication to connect to the database, enables authorization, enables external authentication, automatically creates users in the database for LDAP users, and automatically grants roles in the database to LDAP users
   • Active Directory -- configures Kinetica to authenticate via Microsoft Active Directory; requires authentication to connect to the database, enables authorization, enables external authentication, automatically creates users in the database for Active Directory users, and automatically grants roles in the database to Active Directory users
   • Kerberos -- configures Kinetica to authenticate via Kerberos; requires authentication to connect to the database, enables authorization, enables external authentication, automatically creates users in the database for Kerberos users, and automatically grants roles in the database to Kerberos users

   Warning

   No SSL or authentication is not recommended! For more information on security configurations and settings as well as how to manually configure Kinetica for a secure setup, see Security Configuration.

4. Click Next.

Nodes

1. Click Add New Node until there are the desired number of nodes that will have Kinetica (and potentially other services) installed on them.

2. For each node, input a custom Label (hostname is suggested), the Internal IP, and the Public IP.

3. If the User-provided cert/key per node SSL Mode was selected in Security, an SSL column will be added to the configuration page--click the lock icon in the SSL column to open the SSL Certificate/Key window, where the SSL cert and key, along with an optional public hostname, can be provided. Repeat this for each node.

4. Optionally, select if each node should have the Core package installed. The Core package contains access to the database and its core components and functionality. Note that if the core package is not installed on a node, that node cannot be designated as the Head Node.

5. Optionally, select if each node should have the etcd package installed. The etcd package provides a means for each node in the cluster to have a consistent record of statuses and locations for the other node(s) in the cluster. Ensure at least one node will have etcd installed; select additional nodes for redundancy.

   Tip

   etcd works only when there's an odd number of etcd instances (between three and seven instances is best) per KAgent installation, regardless of how many clusters and/or rings are being managed by that KAgent**. See the etcd FAQ and this task list for more information.

6. Select the desired node for the Head Node using the corresponding radio button. This server will receive user requests and parcel them out to the other worker nodes of the system. The head node of the cluster (or only node in a single-node system) will also be used for the administration of the cluster, and by default, the hosting of Reveal and GAdmin and as such, will require special handling during the installation process.

   Note

   All services and privileges (Head, Graph, AAW, etc.) can exist on a single node if desired, assuming there are enough resources to handle it.

7. If the Graph package was selected for install in Cluster, select the desired node(s) to host the graph service using the corresponding radio button. The graph node does not need to have the Core package enabled. Consult Distributed Graph Servers for more information on leveraging multiple graph servers.

8. If the AAW package was selected for install in Cluster, optionally set the number of reserved GPUs for AAW to use for each node. The AAW service will co-exist with the head node. Note that the AAW package will be automatically installed on every node with the Core package enabled.

   Important

   Some features of AAW require GPUs to work or have increased performance. Review the AAW documentation for more information.

9. If the KAgent package was selected for install in Cluster, select the desired node to host the service. The KAgent node does not need to have the Core package enabled.

10. If the RabbitMQ package was selected for install in Cluster because a High Availability setup is required, select the desired node(s) to have RabbitMQ installed. Ensure at least one node will have RabbitMQ installed if enabling High Availability (HA) for the cluster; select additional nodes to have RabbitMQ installed for redundant queues. A node does not have to host any other services other than RabbitMQ if desired.

    Important

    In total, an odd number of nodes should be selected for RabbitMQ installation. Kinetica recommends installing RabbitMQ machines that will not have the Core package enabled.

11. Click Next.

12. Confirm which IP address KAgent should use to connect to the cluster: Internal or Public.

Credentials

1. For the Server SSH Credentials, enter the SSH username and password or upload the SSH private key that will be used to access the node(s).
2. Optionally, enter the sudo password.
3. Click Verify.

The console will appear showing the log of KAgent interactions as KAgent attempts to access the cluster with the provided credentials and also retrieve information on the hosts, including Kinetica version and configuration (if installed), hostname and IP addresses, OS type, and Nvidia information.

Installation

1. Review the Installation Summary to ensure there are no validation errors in the information. The highlighted IP address will be the one KAgent uses to connect to the cluster.

   Tip

   Click CLI Commands to view and/or copy the KAgent command line interface commands that will be run in the background (order is from top to bottom).

   

2. Click Install. KAgent will open a window displaying the progress of the installation.

   

   Tip

   Click Details next to a step to see stdout and stderr for that step. Click to copy the displayed text.

The installation may take a while as KAgent initializes each node in the cluster, verifies the cluster, adds a repository, downloads the package, installs the package to the directory /opt/gpudb, creates a group named gpudb, and creates two users (gpudb & gpudb_proc) whose home directories are located in /home/gpudb. This will also register two services: gpudb & gpudb_host_manager.

Important

If Automatic Kubernetes (K8) installation was selected and Kinetica is being installed on a RHEL-based system, KAgent will request permission to disable SELinux on the nodes. Kubernetes cannot be installed otherwise. Click I Agree to continue with the installation; click No to stop the installation and manually disable SELinux.

After a successful installation, if KAgent was also installed on a separate node, one can be redirected to the KAgent on that cluster node. If KAgent was not installed on a separate node, one can be redirected to Kinetica Administration Application (GAdmin).