Skip to content

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.

There are two pathways you can take to install Kinetica for use with this guide:

Option 1: Local VM Installation

Important Credentials

  • VM Username: vagrant
  • VM Password: vagrant
  • Kinetica Username: admin
  • Kinetica Password: Qu1ckStart!

If you want to run Kinetica on your laptop, the easiest way to get started is to run a pre-configured VM image on VirtualBox. You will need VirtualBox in order to run the image below, so follow this link to install it before you continue. If you would rather run Kinetica on a server or in the cloud, see the next section to see how to use KAgent, the provisioning, installation, and monitoring tool.

Steps

  1. Install VirtualBox
  2. Download the VM Image
  3. Import the VM image and start the box
  4. Navigate to the GAdmin login screen at http://192.168.0.2:8080

To start the box, click on the kinetica-node image in VirtualBox and push the Start button. Kinetica will automatically begin running. Give it a few moments for the web server to start up.

 Log Into GAdmin

Then, log into GAdmin using admin for the username, and Qu1ckStart! for the password. You are now ready to move to the next section of the Quick Start guide.

Option 2: KAgent Installation

KAgent is a single pane of glass that provisions Kinetica to local and cloud hardware (AWS, Microsoft Azure, or Google Cloud Platform), and provides tools to help you monitor the health of your cluster. KAgent can install Kinetica on either already-provisioned cloud hosts, or it can provision new hosts and install Kinetica on them.

Before starting, ensure you have your license key ready.

Choose a Starting OS

Use the OS on the desired KAgent host machine to determine the how you should install KAgent. KAgent has two installation options:

  1. Windows/MacOS — Docker
  2. Linux — Package Managers

 

Install Docker

Visit the Docker documentation to learn how to install Docker on your system.

Download KAgent

Tip

KAgent requires port 8081, which will need to be open on your KAgent host machine in order to install Kinetica.

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

Install KAgent

KAgent can be installed through package managers for the following OS types.

Platform x86 ppc64le
Debian 9.x
Ubuntu 16.x LTS, 18.x LTS 16.x LTS
RHEL 6.6+, 7.1+ 7.2
CentOS 6.6+, 7.1+ 6.6+, 7.1+
SUSE 12, 12 SP1, 12 SP2

 

On Debian/Ubuntu:

Execute the below commands on your Ubuntu machine from a shell prompt, according to your server platform.

  1. Download the key file:
    Ubuntu 16.x

    curl http://repo.kinetica.com/debian/7.1/Ubuntu/xenial/binary-amd64/keyFile | sudo apt-key add -

    Ubuntu 18.x

    curl http://repo.kinetica.com/debian/7.1/Ubuntu/bionic/binary-amd64/keyFile | sudo apt-key add -
  2. Add the KAgent repo to the sources list:
    Ubuntu 16.x

    sudo sh -c 'echo "deb http://repo.kinetica.com/debian/7.1/Ubuntu/xenial/binary-amd64 ./" >> /etc/apt/sources.list'

    Ubuntu 18.x

    sudo sh -c 'echo "deb http://repo.kinetica.com/debian/7.1/Ubuntu/bionic/binary-amd64 ./" >> /etc/apt/sources.list'
  3. Update the package list:

    sudo apt update
  4. Install KAgent:

    sudo apt install kagent

  1. Download the key file:
    Ubuntu 16.x

    curl http://repo.kinetica.com/debian/7.1/Ubuntu/xenial/binary-ppc64el/keyFile | sudo apt-key add -

    Ubuntu 18.x

    curl http://repo.kinetica.com/debian/7.1/Ubuntu/bionic/binary-ppc64el/keyFile | sudo apt-key add -
  2. Add the KAgent repo to the sources list:
    Ubuntu 16.x

    sudo sh -c 'echo "deb http://repo.kinetica.com/debian/7.1/Ubuntu/xenial/binary-ppc64el ./" >> /etc/apt/sources.list'

    Ubuntu 18.x

    sudo sh -c 'echo "deb http://repo.kinetica.com/debian/7.1/Ubuntu/bionic/binary-ppc64el ./" >> /etc/apt/sources.list'
  3. Update the package list:

    sudo apt update
  4. Install KAgent:

    sudo apt install kagent

On RHEL/CentOS:

Execute the below commands on your RHEL/CentOS machine from a shell prompt, according to your server platform.

  1. Download the repo file:

    sudo wget -O /etc/yum.repos.d/kinetica-7.1.repo http://repo.kinetica.com/yum/7.1/CentOS/7/x86_64/kinetica-7.1.repo
  2. Update the package list:

    sudo yum update
  3. Install KAgent:

    sudo yum install kagent

  1. Download the repo file:

    sudo wget -O /etc/yum.repos.d/kinetica-7.1.repo http://repo.kinetica.com/yum/7.1/CentOS/7/ppc64le/kinetica-7.1.repo
  2. Update the package list:

    sudo yum update
  3. Install KAgent:

    sudo yum install kagent

Launch KAgent

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

KAgent will 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.


Install and Configure Kinetica

Configuration

  1. Enter kinetica for the Name.
  2. Select to install Core, Graph, AAW, and KAgent.
  3. For the Install Mode, select Online. This will download the appropriate packages from the public Kinetica repository on the internet.
  4. For the Version, select an install type: GPU (CUDA) or CPU-only (Intel).
  5. If the Version is CUDA, ensure the Automatically install Nvidia driver checkbox is selected.
  6. Provide your License Key.
  7. Select Automatic for the K8 Setup. This will automatically install Kubernetes for use with AAW.
  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.

KAgent will now install and configure Kinetica. It will alert you when it completes installation.

Kinetica Trial Feedback