Page Comparison

1. Download the package to your $HOME folder and extract it:

   Code Block
   tar -xzvf devo-ea-deployer-1.3.0.2.tgz

2. Change the working directory to the path where the installation package was extracted:

   Code Block
   cd $HOME/devo-ea-deployer

3. Run the preparation script:

   Code Block
   curl -L -u dea-repo:Th3R3p0! https://d2ur64jmn3k7yt.cloudfront.net/gtls/getansible-venv.sh | /bin/bash

4. Activate the virtual environment with the command displayed at the end of the execution of the previous command. Typically it will be something like:

   Code Block
   source "/opt/ansible-2.9/venv/bin/activate"

5. Install the Ansible playbooks' dependencies:

   Code Block
   ansible-galaxy install -r playbooks/roles/requirements.yaml

The inventory is the base of the deployment process and will define the topology of the deployment. For more information on the ansible inventory, check this article.

The inventory file can be created using the inventory creation wizard or using the example files provided with the packages and editing them manually. Remember to have the virtual environment activated (step 4 in “Requirements Installation”).

Inventory creation (using wizard)

1. Execute the inventory creation wizard specifying the inventory output file. The wizard will create the inventory file based on your inputs to a series of questions.

   Code Block
   python tools/cookiecutinvt.py -o inventories/deployment_inventory.yaml

2. For security reasons, we strongly recommend that you change the default password of root user for MySQL service. It is only needed when the MySQL service is deployed in a docker container.
   To configure the password for the MySQL root user, edit the inventory file inventories/deployment_inventory.yaml

   Code Block
   vim inventories/deployment_inventory.yaml

   and add deam_mysql_root_password variable with a strong password in its value.

   Code Block
   all: vars: deam_mysql_root_password: <<ROOT PASSWORD HERE>>

   Replace <<ROOT PASSWORD HERE>> by the password value of your choice.

Inventory creation (using example file)

1. Copy the example inventories/1host-example.yaml and save it as inventories/deployment_inventory.yaml

2. Edit the file based in the particular requirements of the installation. Refer to this article 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.

3. 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_ssh_password: User SSH Password that runs Devo EAM User (ansible_user)

   • Enable the packs that you want to deploy, for more info check this article.

   • If you want to use a private key instead of user and password, please check this article.

4. Set the property ansible_python_interpreter according to your python interpreter:

   1. For Red Hat 7 / Centos 7: /usr/bin/python

   2. For other distros: /usr/bin/python3

5. Set the following properties under all.vars yaml section:

   • 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 entry point.

     • To send the data via a Devo Relay instead of sending it directly to Devo check here.

1. Run the Deployment Inventory Checker Script and check that no errors or relevant warnings are showing by running:

   Code Block
   python tools/checkinvt.py -i inventories/deployment_inventory.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 this article.

2. 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 these requirements and stop if they are not satisfied.

   Code Block
   ansible-playbook -i inventories/deployment_inventory.yaml playbooks/dea-pre-checks.yaml