Azure

We provide a fully installed USP AMI in the Azure Marketplace.

Choosing an Azure instance

There many Azure Instance Types, choosing depends on the following:

  • is the content SD or HD?
  • what is the expected dominant output (HLS, Smooth, etc)?
  • is DRM needed?
  • is the output Live or VOD?
  • if Live, what are the bitrates ingested?
  • if Live what is the DVR window size (and would you plan a RAM disk for that)?

In short, ingest is IO bound, and egress first IO bound, then network and lastly CPU.

With AWS you have the option to use a few high performance instances or many small instances, the benefit of the latter is that spreading the ingest over more nodes will make it easier to cope with errors, if at all they occur.

Setup

When you start the instance you need to use a security group where port 80 and port 22 are enabled. The image user name is 'ubuntu' and has sudo access.

To login you need to use ssh (or similar like putty on Windows):

#!/bin/bash

ssh -i your-ssh-key ubuntu@your-azure-instance

Verify

Once the instance has launched and is marked online you should be able to direct your browser to the instance's public DNS name; such a name looks like this:

your-hostname.cloudapp.net

The instance can be tested as described in Verifying Your Setup.

On startup the instance tries to set it's external hostname as ServerName for Apache and set the same hostname in the 'index.html' file to address all files and links (the 'index.html' file you can find in /var/www/usp-evaluation).