Back to Opsview FAQ

Install a Remote Collector Cluster from an Offline Repository

This guide explains how to have the Orchestrator host the package repository for remote collector cluster installation. These instructions were tested on a RHEL system, but OEL/Debian/Ubuntu systems would follow a similar process.

When you would need to do this Copied

• The collector cluster is located in a secure environment without external access to the official repository (downloads.opsview.com).
• The Opsview package versions required are not available in the official repository (eg: deprecated versions or custom builds.)

Procedure Copied

1. Obtain the tarball from ITRS Support, and extract it to a folder on the orchestrator (such as /var/tmp/repo)

2. Create a symlink to it in /opt/opsview/webapp/docroot

   cd /opt/opsview/webapp/docroot
   ln -s /var/tmp/repo repo
   

3. If your orchestrator has a CA-signed SSL certificate, create the file/opt/opsview/webserver/etc/opsview-site-customisations.d/repo.conf:

   location /repo {
           auth_request off;
           allow all;
           sendfile on;
           sendfile_max_chunk 1m;
           autoindex on;
           autoindex_exact_size off;
           autoindex_format html;
           autoindex_localtime on;
   }
   

   If your orchestrator used a self-signed SSL certificate, create the file /opt/opsview/webserver/etc/conf.d/repo.conf:

   server {
       listen PORT default_server;
       server_name _;
       root /opt/opsview/webapp/docroot;
       location /repo {
           auth_request off;
           allow all;
           sendfile on;
           sendfile_max_chunk 1m;
           autoindex on;
           autoindex_exact_size off;
           autoindex_format html;
           autoindex_localtime on;
           }
   }
   

   This serves the repo files as plain http content on port PORT (any available port will do), because package managers don’t allow insecure https connections by default.

4. Restart the webserver:

   /opt/opsview/watchdog/bin/opsview-monit restart opsview-webserver
   

5. Edit dataserver config files dataserver.yaml and user_vars.yml to change the repository from the online one to the new offline one. This will then be passed on to the collectors via the installation script. In /opt/opsview/dataserver/etc/dataserver.yaml:

   ---    repository_base_url: https://downloads.opsview.com/opsview-commercial/
   +++    repository_base_url: https://ORCHESTRATOR(:PORT)/repo/
   

   In /opt/opsview/dataserver/etc/user_vars.yml:

   ---opsview_repository_base_url: https://downloads.opsview.com/opsview-commercial/
   +++opsview_repository_base_url: https://ORCHESTRATOR(:PORT)/repo/
   

   Remember to include the custom port in the orchestrator’s hostname if you are using plain http, and to use the correct indentation.

6. Restart the dataserver:

   /opt/opsview/watchdog/bin/opsview-monit restart opsview-dataserver
   

7. Follow the instructions in the Remote Collector Management documentation up to the Registration section (creating the new cluster, creating the roles and users, granting permissions on the cluster).

8. If you have CA-signed SSL certificates, run the following command as root on the first new collector:

   curl -sSLo - https://ORCHESTRATOR/downloads/deploy-collector | sudo bash -s -- --username USERNAME --orchestrator ORCHESTRATOR --cluster "CLUSTER"
   

   Or if you have self-signed certificates, run:

   curl -k -sSLo - https://ORCHESTRATOR:PORT/downloads/deploy-collector | sudo bash -s -- --username USERNAME --orchestrator ORCHESTRATOR --cluster "CLUSTER" --insecure
   

9. The administrator user on the orchestrator can then run Apply Changes.

10. Repeat steps 8 and 9 for additional collectors.