1. Okera Installation - Prerequisites

Before installing Okera, the following AWS services must be set up. The AWS services include an S3 Bucket, RDS, and IAM credentials.

  • S3 Bucket

    Okera uses the S3 bucket to store log files and to stage intermediate configuration files. The S3 bucket is set to readable and writable by all instances running Okera components. The S3 bucket is referred to as OKERA_S3_STAGING_DIR later in this document.

  • RDS instance

    Okera is backed by a relational database, either MySQL 5.6, or newer, or Aurora (MySQL 5.6+ compatible), provisioned with the configuration of your choice. Okera instances require read and write access to the OKERA_DB_URL database.

  • IAM credentials

    Okera instances require read and write access to OKERA_S3_STAGING_DIR and OKERA_DB_URL. The Deployment Manager requires the ability to provision instances. The cluster nodes require read credentials to your data. These credentials can be one IAM profile with all the credentials, or two separate roles. If encryption is being used with keys in KMS, these roles will also need KMS access. The IAM role for the Deployment Manager (DM) is referred to as IAM_MANAGER and the IAM role for the cluster nodes is referred to as IAM_CLUSTER.

Deployment Manager Host Requirements

The Deployment Manager does not require a dedicated host, but its host must be separate from any clusters or nodes it manages.

  • Linux installed
  • Java 8 or higher installed (OpenJDK or Oracle JVM).
  • IAM_MANAGER credentials
  • Minimum instance type: t2.medium
  • awscli installed

Install the AWS CLI Tool

To install the awscli command-line tool on a newly provisioned Deployment Manager host, perform these commands.

sudo yum install wget
sudo wget https://bootstrap.pypa.io/get-pip.py
sudo python get-pip.py
sudo pip install awscli
aws configure

Cluster Node Requirements

The cluster nodes are created by the Deployment Manager based on a user-defined launch script. The cluster node requirements include:

  • CentOS 7/RHEL 7 Okera installs Java if not present. The AMI can be a stock RHEL image or one maintained by your enterprise with additional components pre-installed.
  • IAM_CLUSTER credentials
  • Minimum instance type: t2.large with a minimum of 40GB local storage

Network Requirements

There must be full network connectivity between the nodes in the cluster and the Deployment Manager.

CLI Requirements

Any machine running the Okera CLI, ocadm must have network access to the Deployment Manager and cluster machines. The CLI can be installed on the Deployment Manager host or any workstation or development environment with network access to the Deployment Manager and the cluster.

The CLI requirements include:

  • OS
    • RHEL 6 or later
    • Ubuntu 14.04 or later
    • OS X Darwin 10.11 (OS X El Capitan) or later
  • Network access to DM and cluster nodes

Supported Browsers

Okera’s Web UI is tested against the latest versions of the following browsers:

  • Google Chrome
  • Mozilla Firefox
  • Apple Safari
  • Microsoft Edge

Next

You’re now ready to install the DeploymentManager.