How to launch a Collibra DQ installation in Azure from an Image

Microsoft Azure allows us to create images. These images contain the configuration for creating instances. A managed image resource can be created from a generalized virtual machine (VM) that is stored as either a managed disk or an unmanaged disk in a storage account. You can launch multiple VMs from a single image when you need multiple VMs with the same configuration.

Prerequisites: Have a Azure image created with Collibra DQ installed. Follow these instructions to install Collibra DQ in Azure.

Follow these steps to configure an instance from a GCP image with DQ installed:

1. Within Azure, select the version of the image and click on “+ Create VM”.

2. Configure the image with the desired configuration. In this case, introduce a name, check that the desired image is correctly selected and configure the CPU and memory. (click on “See all sizes” if you want to change the configuration selecting by default)

3. Click on “Create”.
4. After the creation, click on the new VM and select “Networking”. Check if the ports 9000, 9001 and 8080 are open. If not, configure these ports clicking on “Add inbound security rule”

5. Once the instance is running, connect through ssh.

ssh -i “pemfile” user@ipaddress

Note: Keeping the configuration of the image, the credentials of the original instance will be configured in this new instance too.

6. Check that there isn’t any owl process working.

7. Start Postgres

#Postgres

export INSTALL_PATH=$(pwd)/owl

export PGPATH=/usr/pgsql-11/bin/

export PGDBPATH=$INSTALL_PATH/postgres/data

export LOG_PATH="$INSTALL_PATH/log"

sudo -u postgres $PGPATH/pg_ctl -D $PGDBPATH start >$LOG_PATH/postgres-start.log 2>$LOG_PATH/postgres-start-error.log & echo $! >/dev/null

Check Postgres is working:

8. Start Apache Spark

#Spark

$INSTALL_PATH/spark/sbin/start-master.sh

$INSTALL_PATH/spark/sbin/start-slave.sh spark://$(hostname -f):7077

Check Spark is up and running:

Also, connect using the browser: http://awsip:8080

9. Update the old Ip address with the new one. To do that, the following files have to be modified:

• $HOME/owl/config/owl-env.sh

Update export SPRING_DATASOURCE_URL= with the new private IP address.

• $HOME/owl/config/owl.properties

Update spring.datasource.url= and spring.agent.datasource.url= with the new private IP address.

10. Change the permission on the PID file.

sudo chmod 777 $HOME/owl/pids/owl-agent.pid

11. Start DQ Agent and Web app. The scripts are in $HOME/owl/bin

./owlmanage.sh start=owlagent

./owlmanage.sh start=owlweb

12. Check the agent and the web app are working properly.

Open your web browser and navigate to: http://ipaddress:9000

13. Go to Admin Console and Remote Agent. Make sure the agent number 2 appears in green:

Note: The name of the agent can be updated by clicking on the chain.

14. Click on the pencil icon to update the settings. In this case, the “Default Master” has to be updated with the new Spark IP address.

15. Once everything is changed, Collibra DQ is ready to be used.

Hope this helps!