WHAT TO EXPECT
A virtual network must be created before deploying a cloudSwXtch instance.
It must contain at least one subnet that's used for both the control and data plane communication, but it can use two, one subnet for each.
It is recommended that it be private-facing and not auto-assign public IPs.
This single subnet will be used for xNIC installation.
The subnets will also be used for xNIC installations.
In this section, users will learn how to validate whether a subnet exists to be used as both the control and the data plane for their virtual network. This is in preparation for cloudSwXtch installation on Azure. We will also walk through an alternative method of using 2 subnets, separating the control and data plane.
To validate:
Go to the Azure Console.
Search for "vnet".
Select Virtual Networks.
Select the vnet to be used for cloudSwXtch.
Name the subnet as "ctrl" if using a single subnet.
If a second subnet is needed:
Name the second one "data" to distinguish between them when creating a VM. Using two subnets will require them to be in the same Region (for example, East US). This enables a single VM instance to have two NICs connected to both subnets at the same time.
In the event that the second subnet does not exist:
Create it by selecting "+ Subnet."
Enter data as shown below, making sure the subnet is in the same VNET and Availability zone as the control subnet:
NEXT STEP: Creating an Azure cloudSwXtch Template
After validating the subnets on Azure, continue to the Create an Azure cloudSwXtch Template guide. This is in preparation for installing cloudSwXtch on Azure.