Deploying the Azure Instance

This is the main instance configuration procedure. It includes a multi-dialog wizard that presents configuration options in the preferred sequence. The result of this wizard is an installed, operational OCSBC or two HA OCSBC instances with a management interface. You add media interfaces after deployment.

Important requirements, whether or not you are using HA, includes the following:

Management subnets should be public to allow access from outside the cloud. Addressing within these subnets should include Public IP addresses.
All Media interfaces addresses that must be reachable through the internet must reside on public subnets; all others can reside on private subnets.

In addition, if you are deploying HA instances, media interfaces must also use reserved public addressing.

The instance deployment wizard sequence includes:

Basics
Disks
Networking
Managment
Guest Config
Tags
Review and Create

Your Azure workspace may present dialogs and fields that differ from this procedure. For full information on deploying Azure instances, see the Azure documentation.

Basics

Azure instance deployment Basics configuration includes:

Entering a name as your Virtual machine name.
Select your Availability Option.
Specifying the Image to deploy.
Size the image.
Specifiying your Administrator Account information. The OCSBC image does not use this account, but you must set these fields or the platform does not allow the workflow to complete. You may either:
- Use the authentication type of Password. Create a null user and give it any password. During instantiation, the OCSBC ignores this password.
- Use the authentication type of SSH public key. Create a null user and paste in the SSH public key from the machine you'll use to log into the OCSBC. During instantiation, the OCSBC will load this key into the ssh-key configuration element as an authorized-key for the admin user.
Specifying your Inbound port rules external port access to interfaces.

The image below displays the initial instance deployment wizard dialog.

This image shows the initial instance deployment wizard dialog for Azure.

During deployment you choose a size for the OCSBC, based on pre-packaged Azure sizes. After deployment, you can change the detail of these sizes to, for example, add disks or interfaces. Azure presents multiple size options for multiple size types. These size types define architectural differences and cannot be changed after deployment. Azure size types include:

F(x)—Does not support premium storage
FS(x)—Supports premium storage
FS(x)_v2—Supports premium storage and hyperthreading.

See your software version's release notes for tables of supported machine sizing.

Disks

Azure instance deployment Disk configuration includes setting the OS disk type to Standard HDD.

Despite the initial boot disk size provided by Oracle, you are free to create a boot disk that is a different size, as supported by Azure. Specifically, consider whether you need a disk that is larger than the initial size to allow for storing log files and other data. When creating disks, refer to both Azure and this Installation Guide's instructions and guidelines on creating, formatting and mounting your disks.

Networking

Configure fields in the Networking dialog to establish the network used by wancom0. Azure instance deployment Networking configuration includes:

Select or create a new Virtual Network.
Select or create your Subnet.
Enter a name as your Public IP.
Select your NIC network security group.
Select your Select inbound ports.

Leave the Place this virtual machine behind an existing load balancing solution? field set to No.

Management

Azure instance deployment Management configuration includes:

Set Boot diagnostics to On.
Set OS guest diagnotics to On.
Set Diagnotics storage account to your account.

Leave all other fields set to Off.

Advanced

You do not need to configure anything on the Advanced dialog.