.HA deployment v13.0
Solution Prerequisites
Following are the solution setup prerequisites.
For HA deployment, we will be using two VMs, each machine in the cluster should have the following hardware specifications. The twoVMs will be referred by VM1 and VM2 in this guide.
Minimum requirement | |
|---|---|
CPU | 4 cores on each VM |
RAM | 4 GB on each VM |
Disk | 300 GB on VM |
NICs | 1 NIC per VM |
Software requirements
Minimum requirement | |
|---|---|
OS (2) | CentOS 7 |
MySQL (2) | 5.5+ |
Docker CE | 18+ |
Docker compose | 1.21 |
On this page
Installation Steps
Internet should be available on the machine where the application is being installed and connections on port 9242 should be allowed in the network firewall to carry out the installation steps. All the commands start with a # indicating that root user privileges are required to execute these commands. Trailing # is not a part of the command.
Allow ports in the firewall
For internal communication of docker swarm, you'll need to allow the communication (both inbound and outbound) on the ports: 2376/tcp, 2377/tcp, 7946/tcp, 7946/udp, 4789/udp, 80/tcp and 443/tcp.
To start the firewall on CentOS (if it isn't started already), execute the following commands:
# systemctl enable firewalld
# systemctl start firewalldTo allow the ports on CentOS firewall, you can execute the following commands. You'll have to execute these commands on all the cluster machines.
# firewall-cmd --add-port=2376/tcp --permanent
# firewall-cmd --add-port=2377/tcp --permanent
# firewall-cmd --add-port=7946/tcp --permanent
# firewall-cmd --add-port=7946/udp --permanent
# firewall-cmd --add-port=4789/udp --permanent
# firewall-cmd --add-port=80/tcp --permanent
# firewall-cmd --add-port=443/tcp --permanent
# firewall-cmd --reload
On VM1 and VM2, execute below additional commands,
# firewall-cmd --add-port=5060/tcp --permanent
# firewall-cmd --add-port=16386-32768/udp --permanent
# firewall-cmd --add-port=9092/tcp --permanent
# firewall-cmd --reloadConfigure Log Rotation
Add the following lines in /etc/docker/daemon.json file (create the file if not there already) and restart the docker daemon using systemctl restart docker. Perform this step on all the machines in the cluster..
|
Installation Steps
Run below command to log in to Expertflow docker registry
docker login gitlab.expertflow.com:9242 --username deployment --password xWb8WafM8ZvdwBHNxLm3Download the deployment script deployment.sh and place it in the user home or any desired directory. This script will:
delete the recording-solution directory if it exists.
To execute the script, give it the execute permissions and execute it.
$ chmod 755 deployment.sh $ ./deployment.shChange to newly created directory with name recording-solution. This directory contains all the required files.
Run SQL script in MySQL to create database and tables. (recording-solution/db_schema.sql).
Update environment variables in the following files inside
/root/recording-solution/docker/environment_variablesfolder.general-environment.env
recorder-environment.env
apis-environment.env
mixer-environment.env
archival-environment.env
Having environment configurations done, copy the recording-solution directory on VM2 in
/rootdirectory using the following command.# scp -r /root/recording-solution root@<vm-ip>:/root/Navigate to /root/recording-solution/activemq/conf and open activemq.xml file. Uncomment the "networkConnectors" tag by removing the START and END comment tags as shown in below picture. This should be uncommented on VM1 only. There are two child tags inside networkConnectors called "networkConnector", put VM1 IP in "uri" property of first child tag and VM2 IP in "uri" property of second tag.
Execute the following commands inside /root/recording-solution directory.
# chmod 755 install.sh # ./install.shRun the following command to ensure that all the components are up and running.
# docker psThis will show services status as shown below image
(HA Only) Now go to VM2, update LOCAL_MACHINE_IP variable to VM2 IP in root/recording/solution/docker/environment variables/recorder-environment.env file and run below command inside /root/recording-solution to start recorder and activemq services. The two activemq services on VM1 and VM2 will now act as master/slave to provide HA. The two recorder services on VM1 and VM2 will be configured in Cisco Call Manager (CUCM) to provide HA.
# chmod 755 install.sh # ./install.shThe directory "/root/recording-solution/recordings" mounted in /root/recording-solution/docker/docker-compose.yml file should also be mounted on network shared file system on both VMs. In this way, all services on two VMs will have a shared directory for recording files reading or writing. See this tutorial to mount a shared directory on multiple machines.