On-Premises Installation

This article is designed to assist in the preparation and installation of the OverOps installation on customer premises. This deployment provides companies with all the OverOps functionalities within their internal environment.

Contents

Prerequisites

Installation Process

 - Server Installation - Docker

 - Server Installation - Non-Docker

 - Server Upgrade

 - Remote Collector Installation

 

Prerequisites

Hardware Requirements

The On-Premises installation requires the following hardware attributes:

  • CPU: modern 8 Core
  • RAM: 16 GB
  • Storage: 200 GB

Software Requirements - Docker Installation

  1. Modern Linux (minimum kernel: 3.10): RedHat 6.5 or above or Debian
  2. Java Development Kit -  Version 6 or above (either OpenJDK or Oracle JDK)
  3. Wget and Tar installed.
  4. Docker binaries:
    1. Docker engine 1.11+: https://docs.docker.com/install/
    2. Docker compose 1.7+: https://docs.docker.com/compose/install/
      Note: docker-compose file needs execute permissions.
    3. Network access:
      - Two HTTP ports open (default: 8080, 9090) to access the Dashboard
      - When using a Remote Collector, an extra TCP port open for a Remote Collector (default: 6060).

Note: Production requires a more robust Docker configuration. Choose an optimal Docker configuration for the Linux and the environment workloads. See recommendations from the Docker blog here

Software Requirements - Non-Docker Installation

OverOps servers require the following software attributes:

  1. Modern Linux (minimum kernel: 3.10): RedHat 6.5 or above or Debian
  2. Java Development Kit -  Version 6 or above (either OpenJDK or Oracle JDK)
  3. wget and tar installed.
  4. Network access:
    1. One HTTP port (default: 8080) open to access both Dashboard and Storage.
    2. One TCP ports for key value storage (default: 4567)
    3. Three additional TCP ports if using the internal H2 Database Engine (default: 5000, 5001, 5002)
    4. When using a Remote Collector, an extra TCP port open for a Remote Collector (default: 6060).

Storage Requirements

  1. OverOps server is installed under /opt/takipi-server: at least 200 GB of free disk space.
  2. Docker Installation only: Docker working folder is /var/lib/docker - it should contain at least 10 GB of free disk space.

 

Installation Process

This section describes how to install OverOps on Docker or non-Docker environments. Unless stated otherwise, instructions concern both installations.

With non-Docker installations, you can use the internal database with a built-in non-Docker binary (default) or you can add an external MySQL database server.

Server Installation - Docker

To install the OverOps server - on Docker:

  1. Via terminal, login to the designated On-Premises server as a root/sudo user.
  2. From the link provided by OverOps, download the latest OverOps server tarball:
    takipi-server-latest.tar.gz.
  3. Extract files to the /opt directory
    tar xvf <PATH_TO_TAR_FILE> -C /opt
  4. From the terminal, run setup:
    /opt/takipi-server/bin/takipi-server.sh start -u <HOSTNAME>

Server Installation - Non-Docker

To install the OverOps Server:

  1. Via terminal, login to the designated On-Prem server.
  2. From the link provided by OverOps, download the latest OverOps server tarball: takipi-server-latest.tar.gz.
  3. Extract files to the /opt directory:
    opt
  4. If using the internal database (default): From the terminal, run setup:
    /opt/takipi-server/bin/takipi-server.sh start -u <HOSTNAME>OR
    If using an external DB, configure the following:
    From the terminal, run setup:
    /opt/takipi-server/bin/takipi-server.sh start -u <HOSTNAME>
    --db-type mysql
    --db-url <JDBC_URL_of_MYSQL_SERVER>
    --db-user <USER_for_MYSQL_SERVER> 
    --db-password <PW_for_MYSQL_SERVER>

For a complete list of options, type:
/opt/takipi-server/bin/takipi-server.sh --help

Activating OverOps

  1. Activate OverOps - send the license ID to OverOps to receive your license key.
    • Browse to: http://<HOSTNAME>:8080/activate
    • Follow the Wizard and enter the license key provided by OverOps.
  2. Sign up for OverOps to generate an agent installation key.
    • Browse to: http://<HOSTNAME>:8080/?signup
  3. Create an agent installation script by replacing the <HOSTNAME> and <AGENT_INSTALLATION_KEY> placeholders:
    wget -O - -o /dev/null "http://<HOSTNAME>:8080/app/download?t=inst" | bash /dev/stdin -i --sk=<AGENT_INSTALLATION_KEY> --s3_url http://<HOSTNAME>:8080/service/png --installer_url "http://<HOSTNAME>:8080/app/download?t=tgz" --base_url http://<HOSTNAME>:8080
    The one-liner can be found in the web application under Add Servers.

Server Upgrade

To upgrade the server:

  1. From the link provided by OverOps, download the latest OverOps server tarball: takipi-server-latest.tar.gz.
  2. From the terminal, login as user root and run upgrade: 
    /opt/takipi-server/bin/takipi-upgrade.sh <PATH_TO_NEW_TARBALL>

 Remote Collector Installation

The Remote Collector listens on a TCP port provided with the --listen_port=<PORT_TO_LISTEN-ON> parameter.

To install a Remote Collector:

  1. Add the --listen_port=<PORT_TO_LISTEN-ON> parameter to the one-liner to install the client as a remote collector. Verify that the hostname is resolvable the location of the OverOps agents (the application server, the JVMs):
    wget -O - -o /dev/null "http://<HOSTNAME>:8080/app/download?t=inst" | bash /dev/stdin -i --sk=<AGENT_INSTALLATION_KEY> --s3_url http://<HOSTNAME>:8080/service/png --installer_url "http://<HOSTNAME>:8080/app/download?t=tgz" --base_url http://<HOSTNAME>:8080 --listen_port=<PORT_TO_LISTEN-ON>
  2. To install the Agent and pair it with a Remote Collector, add the following parameters to the one-liner from above:
    --collector_host=<REMOTE_COLLECTOR_HOSTNAME>
    --collector_port=<REMOTE_COLLECTOR_PORT>

    wget -O - -o /dev/null "http://<SERVER_HOSTNAME>:8080/app/download?t=inst" | bash /dev/stdin -i --sk=<AGENT_INSTALLATION_KEY> --s3_url http://<SERVER_HOSTNAME>:8080/service/png --installer_url "http://<SERVER_HOSTNAME>:8080/app/download?t=tgz" --base_url http://<SERVER_HOSTNAME>:8080--collector_host=<REMOTE_COLLECTOR_HOSTNAME> --collector_port=<REMOTE_COLLECTOR_PORT>
  3. Add the following OverOps agent argument to the JVMs: -agentlib:TakipiAgent

For more information about OverOps Remote Collector, click here.

To download the comprehensive On-Premises Installation Guide, see the link below.

Have more questions? Submit a request