You are here:

Configuring Microsoft Azure Injector Families

When you create a Public Cloud injector family in the Create an Injector Family wizard, Eggplant Performance Studio requires specific details about the virtual environment. Because you've already stored your access credentials, when you select your Credentials on the Cloud settings tab, Studio is able to connect to your cloud provider and read much of the necessary information.

The information specific to the cloud provider appears in the right-hand column of the Cloud settings tab. For Microsoft Azure, those settings are as follows:

Service name: The name of the Azure Cloud service that you want your injectors to run in.
Deployment name: The name of the Azure deployment that you want your injectors to run in.
Storage name: The name of the Azure storage area that will be used to store your injector's virtual hard disks.
Role size: The role size specifies the amount of memory and CPU of each instance, as well as the hourly cost. Keep in mind that the larger and more powerful an instance is, the more expensive it is to run. Select the appropriate instance type from the drop-down list.
Admin name: An administrator user account will be created on each instance. If you want to open a Remote Desktop Connection to an instance, then you will need to log on using the administrator account specified here.
Password: An administrator user account will be created on each instance. If you want to open a Remote Desktop Connection to an instance, then you will need to log on using the administrator account specified here.
Virtual Net name: The name of the Azure Virtual Network that your instances will run in.
Subnet name: The name of the subnet within the Azure Virtual Network.
Location: The geographical region in which you want your instances to run.

None of the cloud-provider-specific settings are editable as long as the Public Cloud injector family has any injectors in it. However, if you delete all injectors from the family, you can edit these settings.

Connecting to Azure Instances using a VPN

Unlike Amazon EC2, Virtual Machines within Azure only have a private IP address. In order to connect to them from the outside world, you need to setup a virtual private network (VPN). Azure provides various options for setting up a VPN. For more details, see how to point to site resource manager portal on the Azure website.

This topic was last updated on January 13, 2022, at 02:42:23 PM.