How to Setup Ant Media Server Clustering on Azure

In this guide, I will explain how to set up Ant Media Server Clustering on Azure. When your load is high, one server instance is not enough for you and you can handle that load with a clustering solution.

For streaming applications, you will need a clustering solution when you have a high number of publishers and viewers. Especially when you require ultra-low latency and adaptive bitrate because they need more processing power. Ultra-low latency is achieved by WebRTC and it is a CPU-intensive protocol. Adaptive bitrating is downgrading video quality in bad networks if needed. It is also CPU intensive because there is video conversion. Luckily, Ant Media Server Enterprise Edition supports clustering, so that you can handle the high load in your streaming applications.

Requirements:

To set up the Ant Media Server, having an Azure account and a ready AntMedia Server Image are needed.

The architecture of the cluster setup can be found here. Introduction to clustering with AntMedia Server can be found here.

Step 1: Create a Resource Group

Each resource created must be in the same resource group. For this, we will first create a resource group. Named antmedia-cluster

Click Resource Groups in the portal which is on the left side then click +Add

Enter "Resource group" then choose your zone.

Proceed by clicking "Create" button

Step 2: Create a Virtual Network

We need to create a virtual network named antmedia-cluster-virtual-network, and then we will add gateway-subnet, origin-subnet, and edge-subnet.

Click Create a Resource in the portal which is on the upper left. Enter Virtual network in the Search the Marketplace box at the top of the New pane that appears. Click Virtual Network when it appears in the search results.

click "Create"

Select the resource group that we created before, enter antmedia-cluster-virtual-network in the name field, and click on the "Next: IP Address" button.

Click on the Add subnet button and create the antmedia-origin-subnet, antmedia-edge-subnet, and antmedia-gw-subnet as shown in the figure below.

The process is completed by clicking on the "Create" button.

Step 3: Create a MongoDB Virtual Machine

Click Virtual Machines on the left bar and then click "+Add"

Enter the following values and click "Next: Disks"

Resource group "antmedia-cluster" Image "Ubuntu 18.04 LTS"

Enter the following values and click "Next: Networking"

Select the Virtual Network that you created, click "Advanced" from "Nic network security group" and click "Create new"

Click the "Add an inbound rule" button in the windows that appear and click the "Add inbound security rule" button

Enter the following values and click "Next: Advanced"

Add the following lines to the "Custom data" area and click the "Review + Create" button to create a MongoDB instance.

#!/bin/bash
wget https://raw.githubusercontent.com/ant-media/Scripts/master/install_mongodb.sh && chmod +x install_mongodb.sh
./install_mongodb.sh

The process is completed by clicking on the "Create" button.

Step 4: Create Application Gateway

Click Create a Resource in the portal which is on the upper left. Enter Application Gateway in the Search the Marketplace box at the top of the New pane that appears. Click the "Application Gateway" when it appears in the search results.

Proceed by clicking "Create" button

Enter the Resource Group, Application Gateway Name, Region, and Virtual Network settings as follows and click "Next: Frontends"

Click on the "Add new" button and enter the public IP name then click "Next: Backends"

Click on "Add a backend pool", create pools for both origin and edge as shown in the screenshot, and click "Next: Configuration".

Click on "Add a routing rule" in the window that appears.

Enter the following values for Edge sides then click the "Add" button.

Select the "Edge" pool as the backend target and click "Add new" for HTTP settings.

Enter the following values. These values will be for both origin and edge.

If your settings are as follows, Edge configuration is finished.

Click on "Add a routing rule" again and set the HTTP settings for Origin. Make the settings as below and click "Backend target".

Select the Origin pool as the backend target and select the "BackendHttpSettings" that we created before as HTTP settings.

Now it's time to forward HTTPS requests to Origin. For this, make the settings as follows. You can use this link for a certificate.

Select "BackendHttpSetting" as HTTP Settings and Select "Origin" as Backend target.

Likewise, configure port 5443 for Edge as follows.

Select "BackendHttpSetting" as HTTP Settings and Select "Edge" as the Backend target.

Application gateway settings will look like the following. If everything is ok, click "Next: Tags"

The process is completed by clicking on the "Create" button.

 Step 4: Create Edge/Origin Scale Sets

We need to set up scale sets. Click Create a Resource in the portal which is on the upper left. Enter "Virtual Machine Scale Set" in the Search the Marketplace box at the top of the New pane that appears. Click "Virtual Machine Scale Set" when it appears in the search results.

Proceed by clicking "Create" button

First, we will create the Origin Scale Set. Select the Resource Group, enter the Virtual Machine scale set name, and choose Region settings as follows. Then click on "Browse all public and private images"

In the window that appears, search for Ant Media Server and select the "Ant Media Server Enterprise 2.2.1" version.

Enter the following values and click "Next: Networking"

Select the antmedia-cluster-virtual-network that we created before as a Virtual Network in this screen. Select the origin subnet as the Network interface and click “Yes” to Use a load balancer choice. Select the application gateway that we created before and select Origin as the Backend pool then click the "Next: Scaling"

Select Custom and set the CPU threshold to 60%. You can set other settings according to yourself.

Continue by clicking directly next to the "Management" and "Health" tabs and add the following lines to the "Custom data" area in the Advanced section.

    #!/bin/bash
    sudo sed -i '/org.apache.catalina.valves.RemoteIpValve/d' /usr/local/antmedia/conf/jee-container.xml
    cd /usr/local/antmedia/
    ./change_server_mode.sh cluster 10.0.2.4

10.0.2.4 IP address is the private IP address of the MongoDB instance I have set up before. Change according to your own MongoDB instance.

Click the "Create" button to create the Scale Set for the Origin.

 Edge

Create a new Scale Set again and repeat the above steps. Then edit the Network interface part as follows. There will be Edge Subnet as the Network Interface and Edge will be selected for the Application Gateway Backend pool.

Finally, your scale sets will look like the following.

 Test

If the following pages are responding then your edge/origin redirects are working correctly.

Edge URL Address https://application-gateway-ip:5443

Origin URL Address: https://application-gateway-ip

When you go to the Cluster Menu, you can see the joined nodes as below.

Test Fly

For publishing please visit the https://your-domain-name/WebRTCAppEE/ and click “Start Publishing” button. The default stream id is “stream1” For playing please visit the https://your-domain-name:5443/WebRTCAppEE/player.html and click “Start Playing” button. The default stream will be played

As you figure out, we connect default https port(443) for publishing and 5443 port for playing. Because we configure load balancer to forward default port(443) to origin group and 5443 to edge group.