sam422 / ansible-role-imperva-appliance

This package is an Ansible playbook designed to install Imperva appliance updates. It can be used for update installation even if there isn’t already an existing Ansible infrastructure.

Overview

This project will help you upgrade a Imperva MXs and/or Gateways from a central Ansible workstation (or using your existing Ansible infrastructure).

Setup

If you don't have an existing Ansible infrastructure, you'll need to set up an Ansible workstation to run the playbook and push out the upgrades. This workstation is only used for the upgrade process, so you can run it on an existing management workstation. If you do have an Ansible Infrastructure, you will still need to set up the ansible user.

Ansible workstation installation:

1. Install python 3.6+
2. Configure python virtualenv (if you don't have a PATH_TO_VIRTUALENV and/or you don't have strong feelings on what it should be, you can add a pythonlocal directory in your home dir and path to it - it just keeps you from adding all the python modules to the general machine installation). (if you have problems with Vagrant finding it later after you logged off, you may need to rerun "source $PATH_TO_VIRTUALENV/bin/activate")

python3 -m venv $PATH_TO_VIRTUALENV
source $PATH_TO_VIRTUALENV/bin/activate

3. Install python modules

pip install -r ./extension/setup/python_requirements.txt

4. Install ansible external deps

ansible-galaxy collection install -r requirements.yml

5. (You need to do this step whether you are setting up a dedicated workstation or using an existing Ansible infrastructure) You will need to have an ansible user created on the Imperva appliance that has access to a standard shell. Your Imperva appliance will need to be unsealed to do this. You will need to do this once on each Imperva appliance, but then you will be able to keep using that user. Log in using admin, then type

admin

to exit the restricted shell. Then you can

useradd ansible
passwd ansible

Deployment

From the project directory, you can test by running:

ansible-playbook -i inventories/default/hosts -u ansible --extra-vars "ansible_sudo_pass=your_password ansible_password=your_password ansible_become_method=su ansible_become_pass=your_password" -vvv site.yml

Edit the inventories/default/hosts file to include the IP or name of your MX for testing.