Azure Deployment

Overview

An initial Qarbine deployment has a primary Qarbine node which provides the web application support and core service interactions. This node has an internal database containing your Qarbine configuration information and the catalog components used to retrieve data, analyze it, and present it. You can configure Qarbine to access multiple data endpoints which can span technologies, cloud providers, and geo-locations. The basic deployment is depicted below.

  

Multi-node and multi-endpoint hosts can be deployed based on Qarbine feature level. Please see the Administration Tool’s “Topology and Port Considerations”document within the Help tab for more information.

DNS and IP Association

SSL is used for browser and endpoint interactions. The host name must resolve to the desired public IP address.To avoid having your instance’s public IP address change after a reboot and break the DNS resolution, allocate a Static Public IP address.An Azure Static Public IP is equivalent to Elastic IP in AWS.

Azure Powershell details can be found at https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-network-deploy-static-pip-arm-cli?context=%2Fazure%2Fvirtual-machines%2Fcontext%2Fcontext

Alternatively, within the Azure Portal navigate to

  

Click

  

Enter the resource group and other settings.

Verify that Static is checked.

  

Click

  

You can later refer to this Static IP address when creating the VM.

Creating the Qarbine VM

In a browser, navigate to the Azure Marketplace at

https://portal.azure.com/

Search for Qarbine.
Select the desired Qarbine version and review the offer information.
Once satisfied, click

  .

The Azure “Create a Virtual Machine” wizard page is opened.
In “Project details” adjust these values for your environment.

  

Provide a meaningful VM name such as shown below. Note that an Azure VM’s name may not be changed later.

  

Verify the image value.

  

If desired, increase the size of the VM for one with more resources.

  

Change the user name as shown below so that /home/qarbine is easily accessible.

  

Set your values for

  

Adjust any other values on the page per your policies.
Click

  

One setting to consider adjusting is.

   Adjust any other values on the page per your policies.
Click

  

The initial port settings have ports 22 SSH, 80 HTTP, 443 HTTPS, and 4000 Qarbine endpoint open.

  

You may want to consider checking this option

  

Adjust any other values on the page per your policies.
Click

  

Adjust any other values on the page per your policies.
Click

  

Adjust any other values on the page per your policies.
Click

  

Adjust any other values on the page per your policies.
Click

  

Adjust any other values on the page per your policies.
Click

  

The top of the next page should show

  

Review the settings.
Once satisfied, click

  

Wait to soon see

  

Wait a bit to then see

  

Navigate to the VM by clicking

  

To access your VM console, copy the public IP address.

  

Use your preferred SSH tool with your host public key to access that IP address using the “qarbine” account name as set above.

Deployment Wizard Preparation

Qarbine operation requires a consistent public IP address and DNS resolution. Some certificate services like Let’s Encrypt do not accept AWS host names for example. You can use your own certificates or have the Qarbine Deployment Wizard create Let’s Encrypt ones with a non-Azure DNS host name. Services like no-ip.com let you create DNS names associated with your elastic IP.

1. Decide on a new host name such as myhost.ddns.net for which you can set a public DNS entry for.

2. Adjust your noip.com settings or other DNS registration as necessary to map the DNS name to the public elastic IP address.

At this point you have a consistent public IP address and associated DNS resolution.
You are ready to run the Deployment Wizard. Instructions for that are available here.

You can now run the Qarbine Deployment Wizard as described in this document.

Changing the SSH Public Key

If you need to change the VM account and\or the SSH public key settings then see the detailed instructions at
https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/troubleshoot-ssh-connection#use-the-azure-portal

You basically navigate to the running VM’s properties page.
Scroll down to the Help section
Click Reset password.
Choose and enter the information shown below.

  

Enter the SSH public key

  

Click

  

You may need to run puttygen, load your PPK, then click Save Public Key into a new file.
Copy that file’s contents for use in the Azure Reset world.