## Overview

An Advanced Automated Installation allows you to chose how you want to distribute the components, in order to achieve better scalability of the application for large deployments. For more information see [Distributing Functionality](🔗)

A number of previous considerations:

• By default, the automated installation method will always install the latest available version of Opsview Monitor, downloaded from our repositories.

• By default, the automated installation method **assumes you have a new operating system installation** since the Opsview Monitor installation may overwrite or remove some existing packages and configuration(s).

• You should configure a hostname which can be resolved by the host's DNS settings, for example `opsview.example.com` should resolve to the IP of the server.

## Pre-requisites:

• A deployment host running an OS supported by the desired version of Opsview

• Root access to the deployment host

• SSH access from the deployment host to all of the Opsview hosts:

  • Authentication must use SSH public keys

  • The remote user must be 'root' or have 'sudo' access without password and without TTY

• Firewall has been configured properly to allow [Opsview Ports](🔗)

• Python 2 installed on any server hosting distributed components such as collectors.

📘



We recommend you update all your hosts to the latest OS packages before installing Opsview.

### Installation checksum verification

Verify that you're running the correct install script by running:

You should see `OK` as a result.

## Installation

Run the following command to setup Opsview Monitor repositories on your server and install the `opsview-deploy` package:

## Configuration

Before configuring your deployment, review the example configuration files:

📘

YML Configuration files

**Tip:** YAML configuration files are sensitive to spacing. Do not use tabs when editing; use sequences of 2 spaces and ensure that the alignment is maintained.

The sizes associated with each of the example configuration files indicates the number of servers. For example, '01-xsmall' is an 'all-in-one' Opsview installation.

For examples of the components roles and distribution, see the following page [Distributing Functionality](🔗).

#### opsview_deploy-01-xsmall.yml

xsmall configuration is for the minimal installation where all components (orchestrator, database, datastore, messagequeue, collector) are kept on a single server.

#### opsview_deploy-02-small.yml

small configuration has 2 collector servers, a database server and orchestrator. The collector servers are configured under 2 different clusters.

#### opsview_deploy-04-large.yml

The large configuration files has:

• orchestrator

• remote database

• 3 collector clusters (1 with dedicated messagequeue and datastore cluster)

• external messagequeue, datastore and registry cluster with 3x servers

• external results-processing servers

• external timeseries servers

#### opsview_deploy-05-xlarge.yml

The xlarge configuration file has:

• orchestrator

• remote database

• 3 collector clusters (1 with dedicated messagequeue and datastore cluster)

• dedicated messagequeue cluster

• dedicated datastore cluster

• dedicated registry cluster

• dedicated results-processing servers

• dedicated timeseries servers

### Modifications

Once you are familiar with the configuration format, copy and edit the configuration file most similar to your environment:

📘

A note on YML File Spacing

**Tip:** The yml configuration files are sensitive to spacing. Do not use 'tabs' when editing, use sequences of 4 individual spaces and ensure that the alignment is retained.

Change the hostname, the IP and optionally the username. For example:

### Sudo

If using a sudo user to SSH to the collectors, you may use the ansible "become" method to do so.

• the user you specify will then need to be listed within the /etc/sudoers file of the server you are accessing

## Global overrides

You need to configure global overrides by dropping 'user_*.yml' configuration files in the '/opt/opsview/deploy/etc/' directory.

You can find examples in '/opt/opsview/deploy/etc/examples/'.

For example:

## InfluxDB

At this point, if you want to use InfluxDB, add this to your `/opt/opsview/deploy/etc/user_vars.yml`:

If you have not installed the InfluxDB packages then install them now before continuing with Opsview Deploy; you must separately install InfluxDB as, unlike RRD, it is _not_ bundled with Opsview Monitor. You can find information on how to do this for your platform in the InfluxDB documentation at https://docs.influxdata.com/influxdb/v1.8/introduction/installation

## Secrets and Credentials

When the `opsview-deploy` package is installed, the secrets and credentials for the deployment should have been generated automatically.

You can re-generate this file if necessary.

❗️



Regenerating the user_secrets for an _existing_ deployment is not currently supported

## Pre-Deployment Checks

Before running opsview-deploy, we recommend Opsview users to check the following list of items:

### Manual Checks

For example:

### Automated Checks

Opsview Deploy can also look for (and fix some) issues automatically. Before executing 'setup-hosts.yml' or 'setup-everything.yml', run:

If any potential issues are detected, a "REQUIRED ACTION RECAP" will be added to the output when the play finishes.

The automatic checks look for:

When a check is failed, an 'Action' is generated. Each of these actions is formatted and displayed when the play finishes and, at the end of the output, sorted by their severity.

The severity levels are:

By default, the check_deploy role will fail if any actions are generated MEDIUM or HIGH severity. To modify this behaviour, set the following in `user_vars.yml`:

The following example shows the 2 MEDIUM severity issues generated after executing check-deploy playbook

## STOP HERE IF YOU ARE USING THIS DOCUMENTATION AS PART OF A MIGRATION

Please note, if you are building new server/s for a migration deployment of 6.x as part of a migration, do not run the deployment steps below OR setup-everything yet. The below links will point you towards the appropriate migration pages for the version you are migrating from

• From version 5.x: https://knowledge.opsview.com/docs/migrating-from-opsview-monitor-5

• From version 6.x: https://knowledge.opsview.com/docs/migrating-opsview-6-to-new-hardware

## Deployment

To deploy Opsview on the target infrastructure:

### Webserver SSL Certificate

In Opsview 6 we now provide a location to drop in SSL Certificates for use in encrypting traffic between the users and the Web UI. To use your own trusted SSL key and certificate instead of the generated self-signed ones, you must copy your certificate and key file into `/opt/opsview/webapp/etc/ssl/`. The default name for these files is `server.key` and `server.crt`.

As `root`, move your SSL certificates into the correct location while backing up the generated self signed ones: Note: these steps assume you have just placed your server certificates into root's home directory, your location and filenames may be different, so change `~/myserver.crt` and `~/myserver.key` accordingly.

If you desire to change the SSL configuration such as the use of intermediate CA certificates, the use of `.pem` files or simply changing the location of the files then please see [opsview-web-app](🔗) for more information

## Logging in

During the installation, a single administrative user will have been created. The credentials for this user are:

The password for the admin user may be changed after logging into the UI by following the steps on [Changing Opsview Monitor Passwords](🔗).

After the system is activated, carry out a reload by navigating to `Configuration => [System] => Apply Changes` and pressing the Apply Changes button.

## Post-Installation

After the deployment process has ended, plugins need to be synced to collectors. This can be done by running:

If you are carrying out the installation as a user with sudo privileges, please refer to the known issues page at https://knowledge.opsview.com/docs/known-issues in order to complete the above step.

### Create New Hosts

By default, only the Orchestrator and any Collectors are added as Hosts. To monitor the other machines in the setup (such as database or timeseries servers), first [Create Hosts](🔗) for them. With the Host details set up, the appropriate Host Templates need to be added to the server. To see what components are running on the machine go to Configuration > My System and click the 'System Overview' tab. Add the matching Host Templates for each component listed for the Host currently being added.

Next, go to the Variables tab on the New Host modal and add Variables for the components added above. Load Balancers and MessageQueue Service checks need OPSVIEW_LOADBALANCER_CREDENTIALS and OPSVIEW_MESSAGEQUEUE_CREDENTIALS details to match their password (as generated in /opt/opsview/deploy/etc/user_secrets.yml).

• If OPSVIEW_DATASTORE_SETTINGS is configured, Node should be set to couchdb@hostname where hostname is the full hostname. This can be found with hostname -f on Linux machines. Password should also match the password found in user_secrets.yml.

• If OPSVIEW_MESSAGEQUEUE_CREDENTIALS is configured, the Node Name should be set to rabbit@hostname where hostname is the full hostname. This can be found with hostname -f on Linux machines.

• An OPSVIEW_LOADBALANCER_PROXY variable is needed for every proxy set up on the Machine. To find the names of the proxies registered, the following bash command will return the names. Note, only the names of the files should be added as variable values, omit the file extension.

Repeat the above steps for all machines used in the hosting of Opsview, then edit the hosts (orchestrator and registered clusters) that were generated by the install to remove all unnecessary service checks and setup the variables and host templates for the ones needed in the same way as above.

### Moving Database

If you wish to move your database to an infrastructure server after the installation is complete, refer to [Moving database](🔗).

## Problems with Installations

If you encounter any problems with the installation, it is safe to rerun the command again.

You are also able to continue the installation from a checkpoint for the following reasons:

• Cancelled installations, which can be done by pressing CTRL+C

• Failed installations, e.g. a network connection failure

The automated installation consists of 5 steps that can be partially executed:

With that in mind, we can then use the -A and -O flags to install up to a certain step or install only that step respectively. While the examples before would run all the five steps in order, this one would rerun all 5 steps:

This second example would just run the firewall step:

If you entered your software key incorrectly (which will fail at the _inst_ step), the command below will remove the incorrect key, re-create the configuration file and re-run the installation: