This document describes the process used to deploy the FileFlex Enterprise solution on Azure using Docker. To achieve this, a Ubuntu Virtual Machine must be spooled up, with the Docker Engine running on it. Once that has been completed, the FileFlex Enterprise docker image can be deployed.
It's assumed that you already have a working Azure account, with a configured subscription and billing, and all rights necessary to access the features described used in this guide. |
We will create a resource group to house our VM components. If you already have one, you can skip this section. Use the services filter to quickly isolate that control panel by entering "resource" into the services filter under 'All services':
Select "resource groups" to enter that panel.
Click on "Add" to create a new resource group. You will see a section similar to:
Select an existing subscription. Here we've selected "pay as you go".
Enter a new name for the resource group. Here we're entering "docker.fileflexdemo.com"
Select the most appropriate region for your storage. Here we're selecting "East US".
Click "Review + create" at the bottom. Assuming that validation passes you'll have to click on Create immediately afterwards to complete this phase.
Before deploying a Virtual Machine we must configure some storage. Use the services filter to quickly isolate that control panel by entering "storage" into the services filter under 'All services':
Click on storage accounts to enter that panel.
Click "Add" to create a new storage account, and you will be presented with a panel containing controls including the following:
Under the "Basics" tab, ensure that a subscription plan has been selected. Here we have chosen "pay as you go".
Select the resource group you configured previously. Here we're selecting "docker.fileflexdemo.com".
Provide an account name. Here we're calling it "fileflexdockerdemo".
Select a region - here we are selecting "East US" again. Ensure the same region is selected in all panels used by this guide.
You can choose to override the performance settings, but here we're going with the defaults.
Click "Review + create", followed by "Create" when final validation complete.
The next step is to create the virtual machine itself, and we do that through the "resource groups" panel. Use the search bar to quickly isolate that control panel by entering "resource" into the search control at the top:
Click on resource groups to enter that panel.
Click on the resource group we created previously. In our case, it's "docker.fileflexdemo.com:
Click the Add button to add resources, and you'll see a marketplace listing similar to:
Enter "Ubuntu Server" into the search field to narrow the results, and hit enter.
From the provided list click on "Ubuntu Server 18.04 LTS" from "Canonical".
Click on the "Create" button, and you'll be presented with a virtual machine creation panel similar to:
Ensure that your subscription (here, it's "pay as you go", and your resource group (here, it's "docker.fileflexdemo.com) are selected.
Enter a virtual machine name. Here we're using "docker.fileflexdemo.com".
Ensure the same region is elected as in the other panels (here, we select "East US").
Under "size", click "change size" to select a capacity which best represents your needs. The default 2-core configuration (D2s_v3) is a good choice for many scenarios. If you're satisfied with the default you can skip this step. After making a VM size choice, click "select" to confirm it. You will see your chosen size in the "Create a virtual machine" panel:
Under authentication type, we will use "password". Select that radio button.
Under "username", enter "dadmin".
Under "password", enter a password of your choice. Here we will enter "Q!w2e3r4t5y6". Confirm the password in the "confirm password" box as well.
The next step is to configure the disks available to the machine. Click the "disks" tab at the top:
Under "OS disk type" select the performance that you need. It's recommended that an SSD is selected.
Ensure that under "Data disks", no "empty" disks are listed. It should look like:
Under "Advanced", ensure that "use managed disks" is selected.
The next step is to configure the networking. Click the "networking" tab at the top.
The default settings for "Virtual network", "subnet" and "Public IP" are fine for this deployment.
Under "NIC network security group" choose "Advanced".
Click "create new" under "Configure network security group":
This will open a new panel on the right allowing you to add inbound rules. Click the "Add an inbound rule" link:
Under "destination port ranges", enter the following list:
9443, 443, 80, 4007, 4010, 4011, 3310 |
Under "protocol" click "TCP".
Give the name a value such as "fileflex_ports"
Click the add button to add the rules, then click OK to commit the rule changes.
You will then be brought back to the prior Networking tab of "Create a virtual machine".
Under "load balancing" ensure "No" is selected.
We don't need to configure anything under the "Management", "Advanced", or "Tags" tabs. |
Click "Review + create" at the bottom.
Once validation is passed, you will be able to click on "Create" at the bottom. Do so now.
As your machine is being created you will see something similar to:
Wait for the deployment to complete. Once finished, you will see the screen change to the following:
When the deployment has completed, the machine will be booted up, so you can test a connection by SSH. Before we can do that we need to get our machine's public IP address.
Search for "virtual machines" at the top:
Click on "Virtual machines", then select your machine from the list. In this case:
After clicking the listed machine instance, you should be taken to your VM's control panel which looks something like this:
Take note of the public IP address listed on the right hand side. In this case, "46.76.221.24".
Open Putty, or an SSH client of your choice, and connect to the listed IP, over port 22:
Click "Open" in putty to initiate an SSH session to the new VM. You will be presented with a login promt.
Login using "dadmin" and the password you previously entered. In our case, it was "Q!w2e3r4t5y6".
You should be presented with an open terminal:
Congratulations, your VM is deployed! Now it's time to install Docker.