CentOS 7

The following procedure is provided to guide EAM administrators in the installation of the solution on CentOS 7-based hosts. Please review carefully the pre-requisites section before starting with the procedure itself.

The inventory file provided by default with the EAM installation package (also available in the Example files section of the Generic Deployment Guidelines article) is intended to be used in AIO (All In One) deployments (all components running in a single server and communications using HOSTS file).

If you have specific requirements for your deployment scenario —full high-availability, for example—, refer to the Generic Deployment Guidelines section for specific instructions to address your needs.

Prerequisites

Make sure all these prerequisites are met. Otherwise, the installation procedure will fail:

Ensure the EAM host can connect to public URLs on the Internet.
Ensure you can access through SSH the host using its main service IP address. It should be also possible to open an SSH connection from the same host using that IP address.
If your deployment scenario includes using existing databases, make sure that the Devo EA Manager has connectivity to MySQL and Redis ports.
Download the Devo EAM software, copy it to your home folder and extract it using:
Download your Devo domain certificates:
- Connect to your Devo domain web interface
- Access Administration → Credentials in the left pane.
- Select X.509 certificates in the upper menu.
- Select your certificate, download them and rename them as:
  - Chain CA - Click the Chain CA button in the top right to download it. Rename it as chain.crt
  - Certificate - Click Certificate on the table to download it. Rename it as domain.crt
  - Click Private key on the table to download it. Rename it as domain.key
- Copy the files to $HOME/devo-ea-deployer/domain-certs

Installation procedure

Check that user configured can run sudo command without prompt. You can do so by running the following line in an SSH session where you did not previously run any sudo command:
If the previous command still asks for password, you can use the next command to avoid it:
> /etc/sudoers "]]>
Install the EPEL repository:
Install Ansible:
Change the working directory to the path where the installation package was extracted:
Install the Ansible playbooks' dependencies:
Edit the inventories/py2-1host-example.yaml file based the particular requirements of the installation. Refer to the Generic Deployment Guidelines to create a proper inventory for your environment in a production deployment. Minimal configuration for a standard lab and PoC deployment in a single server is depicted in steps 7 and 8.
Set the following properties under all.hosts.devo-ea-manager yaml section:
- ansible_host - Devo Endpoint Agent Manager IP
- ansible_user - User that will run Devo EAM. Same as the user that has been configured previously in sudoers
- ansible_password - Set the password
- Enable the packs that you want to deploy, for more info check Generic Deployment Guidelines.
- If you want to use a private key instead of user and password, check the Generic Deployment Guidelines.
Add the following properties under the section all.vars of the .yaml:
- deam_relay_entrypoint : tcp://FQDN_CENTRAL_RELAY:443. Where FQDN_CENTRAL_RELAY is the FQDN of your central Devo relay :
  - If your domain is deployed in the US Cloud (us.devo.com): tcp://us.elb.relay.logtrust.net:443
  - If your domain is deployed in the EU Cloud (eu.devo.com): tcp://eu.elb.relay.logtrust.net:443
  - If your domain is deployed in a different cloud, contact your Devo representative to know your entrypoint.
  - To send the data via a Devo Relay instead of sending it directly to Devo check here.
(Only from 1.2.1) Run the Deployment Inventory Checker Script and check that no errors or relevant warnings are showing by running python tools/checkinvt.py -i inventories/py2-1host-example.yaml. Deployment Inventory Checker Script will run validations on the inventory and report back if an issue is found. For more info on the Deployment Inventory Checker Script, see checkinvt.py - Deployment Inventory Checker Script
(Only from 1.2.1) Run the pre-requisites playbook to ensure that all external connectivity and requirements are in place. The playbook will output a summary with all the URLs connectivity that has been checked. If there is any error there, please fix it before moving ahead with the deployment. Deployment playbook will verify again this requirements and stop if they are not satisfied.
Create docker/user/config.json file with valid empty JSON body:
docker/user/config.json]]>
Run the Ansible playbook:

Once the installation process finishes, you can connect to server app using https://DEAM_IP:8080, where DEAM_IP is the Devo Endpoint Agent Manager IP. User and password were configured in your inventory file (More info)

Upon agent installation, all monitored endpoints (please refer to Endpoint Agent Deployment) should be automatically detected and listed as an active host. If the website was already opened before adding the host, a page refresh is required. This is an example screenshot:

Troubleshooting

Use the following commands to verify the status of all the services exposed by the EA Manager:

To check the status port 8080:
To check the status port 8081To check the status port 8080:

CentOS 8

CentOS 8 has been declared End Of Life on December 31st, 2021. As a result of that, official repositories have stopped working on January 31st and deployment playbooks in Centos 8 will not work as expected. Deployment of Endpoint Agent Manager in Centos 8 will not be supported. See official announcement in: https://www.centos.org/centos-linux-eol/

The following procedure is provided to guide EAM administrators in the installation of the solution on CentOS 8-based hosts. Please review carefully the pre-requisites section before starting with the procedure itself.