docker-compose-rabbitmq-postgresql

Synopsis

Using docker-compose, bring up a Senzing stack using RabbitMQ and a PostgreSQL database.

Overview

This repository illustrates a reference implementation of Senzing using RabbitMQ as the queue and PostgreSQL as the underlying database.

The instructions show how to set up a system that:

Reads JSON lines from a file on the internet and sends each JSON line to a message queue via the Senzing stream-producer.
1. In this implementation, the queue is RabbitMQ.
Reads messages from the queue and inserts into Senzing via the Senzing stream-loader.
1. In this implementation, Senzing keeps its data in a PostgreSQL database.
Reads information from Senzing via Senzing API Server server.
Views resolved entities in a web app.

The following diagram shows the relationship of the docker containers in this docker composition. Arrows represent data flow.

Preamble

At Senzing, we strive to create GitHub documentation in a "don't make me think" style. For the most part, instructions are copy and paste. Whenever thinking is needed, it's marked with a "thinking" icon 🤔. Whenever customization is needed, it's marked with a "pencil" icon ✏️. If the instructions are not clear, please let us know by opening a new Documentation issue describing where we can improve. Now on with the show...

Legend

🤔 - A "thinker" icon means that a little extra thinking may be required. Perhaps you'll need to make some choices. Perhaps it's an optional step.
✏️ - A "pencil" icon means that the instructions may need modification before performing.
⚠️ - A "warning" icon means that something tricky is happening, so pay attention.

Related artifacts

DockerHub

Expectations

Space: This repository and demonstration require 7 GB free disk space.
Time: Budget 2 hours to get the demonstration up-and-running, depending on CPU and network speeds.
Background knowledge: This repository assumes a working knowledge of:
- Docker
- Docker-compose

Prerequisites

Prerequisite software

docker
docker-compose
git

Clone repository

The Git repository has files that will be used in the docker-compose command.

Using these environment variable values:

export GIT_ACCOUNT=senzing
export GIT_REPOSITORY=docker-compose-demo
export GIT_ACCOUNT_DIR=~/${GIT_ACCOUNT}.git
export GIT_REPOSITORY_DIR="${GIT_ACCOUNT_DIR}/${GIT_REPOSITORY}"

Follow steps in clone-repository to install the Git repository.

Demonstrate

Volumes

✏️ Specify the directory where Senzing should be installed on the local host. Example:
```
export SENZING_VOLUME=~/my-senzing
```
1. ⚠️ macOS - File sharing must be enabled for SENZING_VOLUME.
2. ⚠️ Windows - File sharing must be enabled for SENZING_VOLUME.

Identify directories on the local host. Example:

export SENZING_DATA_DIR=${SENZING_VOLUME}/data
export SENZING_DATA_VERSION_DIR=${SENZING_DATA_DIR}/2.0.0
export SENZING_ETC_DIR=${SENZING_VOLUME}/etc
export SENZING_G2_DIR=${SENZING_VOLUME}/g2
export SENZING_VAR_DIR=${SENZING_VOLUME}/var

export POSTGRES_DIR=${SENZING_VAR_DIR}/postgres
export RABBITMQ_DIR=${SENZING_VAR_DIR}/rabbitmq

Create directory for RabbitMQ persistence. Note: Although the RABBITMQ_DIR directory will have open permissions, the directories created within RABBITMQ_DIR will be restricted. Example:
```
sudo mkdir -p ${RABBITMQ_DIR}
sudo chmod 770 ${RABBITMQ_DIR}
```

SSH port

🤔 Optional: If you do not plan on using the senzing/sshd container then these ssh sections can be ignored. Normally port 22 is already in use for ssh. So a different port may be needed by the running docker container.

🤔 See if port 22 is already in use. If it is not in use, the next 2 steps are optional. Example:
```
sudo lsof -i -P -n | grep LISTEN | grep :22
```
✏️ Choose port for docker container. Example:
```
export SENZING_SSHD_PORT=9181
```

Construct parameter for docker run. Example:

export SENZING_SSHD_PORT_PARAMETER="--publish ${SENZING_SSHD_PORT:-9181}:22"

Set sshd password

🤔 Optional: The default password set for the sshd containers is senzingsshdpassword. However, this can be changed.

✏️ Set the SENZING_SSHD_PASSWORD variable to change the password to access the sshd container. Example:
```
export SENZING_SSHD_PASSWORD=<Pass_You_Want>
```

EULA

To use the Senzing code, you must agree to the End User License Agreement (EULA).

⚠️ This step is intentionally tricky and not simply copy/paste. This ensures that you make a conscious effort to accept the EULA. Example:
```
export SENZING_ACCEPT_EULA="<the value from this link>"
```

Pull docker images

"latest" or "pinned" versions of containers can be used in the docker-compose formation. The following will be used to pull the pinned or most recent latest versions.

🤔 Optional: Pin versions of docker images by setting environment variables. Example:

source <(curl -X GET https://raw.githubusercontent.com/Senzing/knowledge-base/master/lists/docker-versions-latest.sh)

Pull docker images. Example:

cd ${GIT_REPOSITORY_DIR}

sudo \
  --preserve-env \
  docker-compose --file resources/senzing/docker-compose-senzing-installation.yaml pull

sudo \
  --preserve-env \
  docker-compose --file resources/postgresql/docker-compose-rabbitmq-postgresql.yaml pull

Install Senzing

If Senzing has not been installed, install Senzing. Example:
```
cd ${GIT_REPOSITORY_DIR}
sudo \
  --preserve-env \
  docker-compose --file resources/senzing/docker-compose-senzing-installation.yaml up
```
1. This will download and extract a 3GB file. It may take 5-15 minutes, depending on network speeds.

Install Senzing license

Senzing comes with a trial license that supports 100,000 records.

🤔 Optional: If more than 100,000 records are desired, see Senzing license.

Run docker formation

Launch docker-compose formation. Example:

cd ${GIT_REPOSITORY_DIR}
sudo \
  --preserve-env \
  docker-compose --file resources/postgresql/docker-compose-rabbitmq-postgresql.yaml up

Allow time for the components to come up and initialize.
1. There will be errors in some docker logs as they wait for dependent services to become available. docker-compose isn't the best at orchestrating docker container dependencies.

View data

Once the docker-compose formation is running, different aspects of the formation can be viewed.

Username and password for the following sites were either passed in as environment variables or are the default values seen in docker-compose-rabbitmq-postgresql.yaml.

View docker containers

A good tool to monitor individual docker logs is Portainer. When running, Portainer is viewable at localhost:9170.

Use SSH

Instructions to use the senzing/sshd container are viewable in the senzing/docker-sshd repository

View RabbitMQ

RabbitMQ is viewable at localhost:15672.
1. Defaults: username: user password: bitnami
See additional tips for working with RabbitMQ.

View PostgreSQL

PostgreSQL is viewable at localhost:9171.
1. Defaults: username: postgres password: postgres
See additional tips for working with PostgreSQL.

View Senzing API Server

View results from Senzing REST API server. The server supports the Senzing REST API.

OpenApi Editor is viewable at localhost:9180.
Example Senzing REST API request: localhost:8250/heartbeat
See additional tips for working with Senzing API server.

View Senzing Entity Search WebApp

Senzing Entity Search WebApp is viewable at localhost:8251.
See additional tips for working with Senzing Entity Search WebApp.

View Jupyter notebooks

Change file permissions on PostgreSQL database. Example:
```
sudo chmod 777 -R ${SENZING_VAR_DIR}/postgres
```
Jupyter Notebooks are viewable at localhost:9178.
See additional tips for working with Jupyter Notebooks.

View X-Term

The web-based Senzing X-term can be used to run Senzing command-line programs.

Senzing X-term is viewable at localhost:8254.
See additional tips for working with Senzing X-Term.

Cleanup

When the docker-compose formation is no longer needed, it can be brought down and directories can be deleted.

Bring down docker formation. Example:

cd ${GIT_REPOSITORY_DIR}
sudo docker-compose --file resources/senzing/docker-compose-senzing-installation.yaml down
sudo docker-compose --file resources/postgresql/docker-compose-rabbitmq-postgresql.yaml down
sudo docker-compose --file resources/postgresql/docker-compose-rabbitmq-postgresql-again.yaml down

Remove directories from host system. The following directories were created during the demonstration:
1. ${SENZING_VOLUME}
2. ${GIT_REPOSITORY_DIR}
They may be safely deleted.

Advanced

The following topics discuss variations to the basic docker-compose demonstration.

Re-run docker formation

🤔 Optional: After the launch and shutdown of the original docker formation, the docker formation can be brought up again without requiring initialization steps. The following shows how to bring up the prior docker formation again without initialization.