WHAT TO EXPECT
A virtual network must be created before deploying a cloudSwXtch EC2 instance.
It must contain at least one subnet that's used for both the control and data plane communication.
It is recommended that it is private facing and does not auto-assign public IPs.
This single subnet will be used for xNIC installation.
The subnets will also be used 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.
If using a single-subnet, name the subnet as "ctl." If using two subnets, name the second one "data" to distinguish between them when creating an VM instance. 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 in the same VNET and Availability zone as shown below:
Endpoint Connections Limit
Please be mindful of the number of endpoints (virtual machines) you are allowed to connect to your cloudSwXtch after creation. For more information about sizing, please see cloudSwXtch System Requirements.
NEXT STEP: Creating an Azure cloudSwXtch Template
After validating the subnets on Azure, continue on to the Create an Azure cloudSwXtch Template guide. This is in preparation for installing cloudSwXtch on Azure.