Download and Install Kinetica

This tutorial will walk you through how to download and install Kinetica either as a single node instance for simple testing purposes or as a performance-oriented cluster.

Step 1: Install Docker

The Quick Start Guide utilizes Docker to get a single node or cluster up-and-running (you’ll choose in Step 2). Visit the Docker documentation to learn how to install Docker on your system.

Step 2: Choose an Installation Path

As mentioned previously, there are two installation paths:

  1. Single Node (via Kinetica Docker Container) — Simpler and quicker setup than a cluster but does not scale nor include access to KAgent or the Active Analytics Workbench. Great for quick testing and portability.

    Important

    Remember that parts of the Importing Data, parts of the Querying with SQL section, and the entire ML-Powered Analytics section require access to the Active Analytics Workbench, so won’t be able to experience the entire Quick Start Guide if you choose this installation path.

  2. Cluster (via KAgent Docker Container) — Longer setup than a single node but provides access to everything Kinetica has to offer with scaling and better performance and utility.

    Tip

    KAgent can provision Kinetica to local hardware or the cloud (AWS, Microsoft Azure, or Google Cloud Platform). KAgent can install Kinetica on either already-provisioned cloud hosts or can provision new hosts and install Kinetica on them.

Before starting, ensure you have your license key ready.

License Key

No Key, No account
Kinetica requires a license key to activate the product.  Please register for your key.

 

 

Important

The single node installation path using the Kinetica Docker container will not include access to KAgent or the Active Analytics Workbench. This installation path is strictly for light testing and development.

Step 3: Download and Initialize Kinetica

After opening some ports and using a simple docker run command, your single node Kinetica instance will be available for initialization and then testing.

Tip

For best results with the Kinetica Docker container, we recommend at least 8GB of memory.

Network Configuration

The Kinetica Docker Container requires several ports be made available on the host:

  • 8080 – GAdmin
  • 8088 – Reveal
  • 9191 – Database API Service

Install

Execute the below command on the Docker host from a shell prompt. This will download the latest Kinetica Intel Docker image to your machine and run it.

sudo docker run -d -p 8080:8080 -p 8088:8088 -p 9191:9191 kinetica/kinetica-intel:latest

Initialization

The database will have to be initialized before it can be started. This will be accomplished using GAdmin.

  1. Navigate to GAdmin (http://<localhost>:8080/
  2. Login to GAdmin:
    1. Enter Username: admin
    2. Enter Password: admin
    3. Click Login
  3. Provide your License Key.

    License Key

    No Key, No account
    Kinetica requires a license key to activate the product.  Please register for your key.
  4. Click Activate.
  5. Start the system. This will start all database processes.
    1. Click Admin on the left menu.
    2. Click Start.

Your single-node Kinetica installation is now ready for testing.

Important

It is highly recommended you change the administrator password at this point. Consult Changing the Administrator Password for more information.

Step 3: Download and Launch KAgent

After opening a port and using a simple docker run command, KAgent will be available.

Tip

If you plan on installing Kinetica on local hardware or on already-provisioned cloud hosts, the machine(s) should meet the minimum hardware requirements.

Networking Configuration

The KAgent Docker Container requires that one port be made available on the host:

  • 8081 – KAgent

Download

Execute the below command on the Docker host from a shell prompt. This will download the latest KAgent Docker image to your machine and run it.

sudo docker run -d -p 8081:8081 kinetica/kagent

Launch

Now that KAgent has been installed, you should be able to access the KAgent user interface to configure and start the service.

Note that this tutorial skips SSL and External Authentication setup in the Security section, but both are strongly recommended in a production environment. Additional security configuration can be made at any time using KAgent. Consult the KAgent documentation for more information.

KAgent should be running on port 8081. Open a browser and enter the following URL, making sure to insert the correct hostname or IP.

  1. Navigate to KAgent (http://<kagent-host>:8081/)
  2. Click Add New or Existing Cluster to begin the installation process.

Step 4: Install and Configure Kinetica

Configuration

  1. Enter kinetica for the Name.
  2. For the Variant, select an install type: CPU-only (Intel) or GPU (CUDA).
  3. For the Install Mode, select Online. This will download the appropriate packages from the public Kinetica repository on the internet.
  4. Provide your License Key.

    License Key

    No Key, No account
    Kinetica requires a license key to activate the product.  Please register for your key.
  5. Select to install AAW (the Active Analytics Workbench) and KAgent.
  6. Select Automatic for the K8 Setup. This will automatically install Kubernetes for use with AAW.
  7. If the Variant is CUDA, ensure the Automatically install Nvidia driver checkbox is selected.
  8. Click Next.

Deployment

Select a deployment provider.

Use the On Premise instructions if deploying to already-provisioned cloud hosts.

 


On premise requires no additional setup for the Deployment tab. KAgent will automatically open required ports for Kinetica services and functionality. Click Next.

Security

  1. Provide and confirm an Admin Password.

    This password will be used to access the administration account for each component in Kinetica (GAdmin, KAgent, AAW, and Reveal)

  2. Leave the default settings for SSL Mode and Authentication. Additional security configuration can be made post-installation using KAgent. Consult the KAgent documentation for more information.
  3. Click Next.

Nodes

Important

If using a trial license of Kinetica, note that a cluster of at most three nodes can be created.

  1. Click + Add New Node until the amount of desired nodes for your cluster is reached.
  2. Provide the Hostname, Internal IP address, and Public IP address for each node.
  3. Click Next.
  4. Select if KAgent should attempt to connect to your cluster via Internal or Public IP. KAgent must be able to connect to your cluster to install Kinetica and its components. This is typically done via the Public IP address but in some network environments, the Internal IP address may be required.

Credentials

  1. Provide an SSH Username and SSH Password OR SSH Private Key. These credentials will be verified to provide KAgent access to the machine(s). If uploading an SSH Private Key, KAgent will use it to set-up and configure the nodes on your behalf; KAgent will also be uploading public keys to those nodes.
  2. Leave the Sudo Password blank.
  3. Click Verify.

  1. Provide your AWS account’s Access Key and Secret key. If you do not have one, create one in your AWS IAM console.
  2. Provide your AWS account’s SSH Key Name. KAgent will use this key for authorization when provisioning instances.
  3. Select an AWS Region.
  4. Click Next.

Security

  1. Provide and confirm an Admin Password.

    This password will be used to access the administration account for each component in Kinetica (GAdmin, KAgent, AAW, and Reveal)

  2. Leave the default settings for SSL Mode and Authentication. Additional security configuration can be made post-installation using KAgent. Consult the KAgent documentation for more information.
  3. Click Next.

Nodes

Important

If using a trial license of Kinetica, note that a cluster of at most three nodes can be created.

  1. Click + Add New Node until the amount of desired nodes for your cluster is reached.
  2. Select an AWS Instance Type for each node. If you selected a CPU-only variant in Configuration, we recommend selecting a General Purpose instance type.
  3. Select the Data Size (in GB) for each node. The size must be at least 32GB per node.
  4. Click Next.

Credentials

  1. Upload the SSH Private Key (AWS PEM) that matches the SSH Key Name you provided in Deployment. KAgent will use this key to set-up and configure the nodes on your behalf; KAgent will also be uploading public keys to those nodes.
  2. Leave the Sudo Password blank.
  3. Click Next.

  1. Provide the GCP Project name.
  2. Upload a GCP Service Account File (typically a JSON file).

    The service account selected must have several compute network and firewalls permissions. We recommend assigning the Compute Admin role to the service account.

  3. Select a GCP Zone.
  4. Provide an SSH User name and SSH Public Key. The user and key will be added to the new cluster.
  5. Click Next.

Security

  1. Provide and confirm an Admin Password.

    This password will be used to access the administration account for each component in Kinetica (GAdmin, KAgent, AAW, and Reveal)

  2. Leave the default settings for SSL Mode and Authentication. Additional security configuration can be made post-installation using KAgent. Consult the KAgent documentation for more information.
  3. Click Next.

Nodes

Important

If using a trial license of Kinetica, note that a cluster of at most three nodes can be created.

  1. Click + Add New Node until the amount of desired nodes for your cluster is reached.
  2. Select a GCP Instance Type for each node.
  3. If you selected a GPU variant in Configuration, select a GPU Card for each node. If you selected a CPU-only variant, we recommend selecting no-gpu for the GPU Card on each node.

    For CUDA installations, we recommend selecting one of the officially supported cards, but note that the region you selected in Deployment can determine which cards are available.

  4. Select the Data Size (in GB) for each node. The size must be at least 32GB per node.
  5. Click Next.

Credentials

  1. Upload the SSH Private Key that matches the SSH Public Key you provided in Deployment. KAgent will use this key to set-up and configure the nodes on your behalf; KAgent will also be uploading public keys to those nodes.
  2. Leave the Sudo Password blank.
  3. Click Next.

  1. Provide an Azure application’s Client ID, Secret, Subscription ID, and Tenant.

    For assistance in finding these values and prepping the application for Kinetica installation, refer to the Azure documentation. We recommend assigning the application to the Contributor role.

  2. Select an Azure Region.
  3. Provide an SSH User name and SSH Public Key. The user and key will be added to the new cluster.
  4. Click Next.

Security

  1. Provide and confirm an Admin Password.

    This password will be used to access the administration account for each component in Kinetica (GAdmin, KAgent, AAW, and Reveal)

  2. Leave the default settings for SSL Mode and Authentication. Additional security configuration can be made post-installation using KAgent. Consult the KAgent documentation for more information.
  3. Click Next.

Nodes

Important

If using a trial license of Kinetica, note that a cluster of at most three nodes can be created.

  1. Click + Add New Node until the amount of desired nodes for your cluster is reached.
  2. Select an Azure Instance Type for each node.
  3. Select the Data Size (in GB) for each node. The size must be at least 32GB per node.
  4. Click Next.

Credentials

  1. Upload the SSH Private Key that matches the SSH Public Key you provided in Deployment. KAgent will use this key to set-up and configure the nodes on your behalf; KAgent will also be uploading public keys to those nodes.
  2. Leave the Sudo Password blank.
  3. Click Next.

Installation

Review the summary information, then click Install. Depending on the deployment and OS type, KAgent will ask permission to disable SELinux on the nodes. Kubernetes cannot be automatically installed if SELinux is not disabled. Click I Agree to continue with the installation.

It’s important that the browser window open with KAgent installing Kinetica remain open. If the browser closes at any point, the installation process will be cancelled but can be restarted later by reopening a browser window to KAgent.

A status window will appear, displaying the progress of each job KAgent performs to install and provision Kinetica. The installation may take a while as KAgent adds a repository, downloads the package, installs the package to the directory /opt/gpudb, creates a group named gpudb, and two users (gpudb & gpudb_proc) whose home directories are located in /home/gpudb. This will also register four services on the new Kinetica instances: gpudb, gpudb_host_manager, kagent_ui, and kml (for AAW).

 

Further Learning

 

 

Kinetica Trial Feedback