Share this page

# Manage elastic cloud hosts

This section describes how to set up and manage elastic load generators on the cloud for performance tests. This enables load generators to be provisioned and de-provisioned on demand in response to dynamic workloads.

In this topic:

## Cloud hosts overview

Load generators can be hosted on local machines or in a cloud account. To host a load generator on the cloud, you must have access to a cloud account that hosts the load generator, and your cloud account must be set up for provisioning load generators.

Supported cloud providers

- Amazon EC2

- Microsoft Azure cloud accounts

- Google Cloud Platform

Tip: See the Video gallery for a video on how to run tests on load generators that are dynamically provisioned on AWS.

Back to top

## Benefits of elastic cloud-based hosts

Advantages of using elastic hosts include:

- Automates the testing process by provisioning load generators only when you need them, and seamlessly adding them to performance tests. Once a test is finished, cloud load generators are automatically de-provisioned.

- Reduces costs because you no longer need to maintain dedicated load generator machines.

- Efficient allocation of resources on demand in response to dynamic workloads, without having to rely on load generators defined in the lab, or to reserve load generators in advance.

- Enables managing cloud provisioning on a per-project basis, with each project having access only to the cloud resources it needs.

Back to top

## Elastic cloud hosts workflow

Using elastic cloud hosts requires the following steps.

1. Defining initial cloud settings

   Tip: If you have existing load generators in the cloud that you want to add to the lab, you can add them directly from the Hosts module in Administration. For details, see Add cloud-provisioned hosts to your lab.

   Set up an account with a cloud provider, obtain the cloud provider credentials, and define network settings for communicating from OpenText Enterprise Performance Engineering to your cloud provider and with your cloud-based load generators. For details, see Initial cloud settings.

2. Adding cloud accounts

   Define a cloud account in OpenText Enterprise Performance Engineering by entering your cloud provider credentials and associating projects to the account. For details, see Cloud accounts.

3. Defining host templates

   Host templates are used for defining provisioning-related details, such as instance types, regions, and hardware specifications. You create your own templates, and OpenText Enterprise Performance Engineering uses the details of the selected template to provision your host. For details, see Host templates.

   If OpenText images don’t suit your needs, you can specify in a host template an image that includes custom configuration. For details on how to create such an image, see Create custom image for cloud hosts.

4. Configuring a performance test with elastic cloud-based load generators

   Configure your performance test to use Elastic Cloud load generators. For details, see Provision elastic cloud load generators.

5. Monitoring resource consumption

   After provisioning your cloud hosts, you can analyze and monitor your cloud resource consumption by looking at the relevant usage reports. For details, see Monitor cloud resources.

Back to top

## Configure cloud environment settings

You can configure the following cloud environment settings for host templates in the appsettings.json configuration file:

- ActiveRegions

- UnavailableRegions (Azure cloud hosts only)

- Public IP address SKU type (Azure cloud hosts only)

- Load balancer support (Azure cloud hosts only)

- Storage Settings (AWS cloud hosts only)

ActiveRegions

If you want to provision hosts on specified regions only, you can define a list of regions from the configuration file.

1. Go to <Server_installdir>\LRE_BACKEND\ and open the appsettings.defaults.json file.

2. Add an ActiveRegions section under the relevant cloud provider, and define a list of specified regions that are available for creating templates. If you leave an empty list, all regions are considered available.

   Example - Active regions (AWS):

   Copy code

       “AWS”: {
         “ActiveRegions”:
           [
            “us-east-1”,
            “ca-central-1”
           ]
       }

   Example - Active regions (Azure):

   Copy code

       “Azure”: {
         “ActiveRegions”:
           [
            “australiacentral2”,
            “swedencentral”
           ]
       }

UnavailableRegions (Azure cloud hosts only)

If you encounter the following error in the LRECoreApi log ".......Microsoft.Rest.Azure.CloudException: No registered resource provider found for location 'xxxxxxxxxxxxx' and API version 'yyyy-mm-dd' for type 'locations/.......", perform the following:

1. Go to <Server_installdir>\LRE_BACKEND and open the appsettings.defaults.json file.

2. Search for "UnavailableRegions" in the Azure section, and add the relevant regions based on the log "No registered resource provider found for location 'xxxxxxxxxxxxx'".

   Example - Unavailable regions:

   Copy code

       “Azure”: {
         "UnavailableRegions": "123456789123456789", "987654321123456789"
       }

Public IP address SKU type (Azure cloud hosts only)

You can configure the SKU type for Azure public IP addresses.

1. Go to <Server_installdir>\LRE_BACKEND\ and open the appsettings.defaults.json file.

2. Add a PublicIPSkuType subsection to the Azure section, and specify "Standard" or "Basic" SKU type ("Basic" is the default type). Refer to the Microsoft documentation for differences between SKU types.

   Example - Azure public IP address SKU type:

   Copy code

       “Azure”: {
         "PublicIPSkuType": "Standard"
       }

Load balancer support (Azure cloud hosts only)

You can configure cloud environment settings so that provisioned load generators are automatically assigned to an Azure Load Balancer backend pool.

1. Go to <Server_installdir>\LRE_BACKEND\ and open the appsettings.defaults.json file.

2. Add a LoadBalancers section, and specify the following.

   Setting | Description
   --- | ---
   templateId | The template from which all load generators are provisioned.
   loadBalancerId | The Azure Load Balancer to which load generators are assigned.
   backendPoolId | ID of the backend pool to which load generators are assigned.

   Example - Load balancer support:

   Copy code

       "LoadBalancers": {
       "templateId": "loadBalancerId:backendPoolId",
       }

Storage Settings (AWS cloud hosts only)

You can configure cloud environment settings so that provisioned AWS load generators have specified volume size and volume type.

1. Go to <Server_installdir>\LRE_BACKEND\ and open the appsettings.defaults.json file.

2. Uncomment the Storage section, and specify the following.

   Setting | Description
   --- | ---
   templateId | The template from which all load generators are provisioned.
   VolumeType | Amazon volume type. For example, gp2, gp3, or other AWS volume types.
   VolumeSize | Amazon Elastic Block Store (EBS) disk size, measured in gigabytes (GB).

   Example - Storage support:

   Copy code

       Storage": {
               "<template ID>": {
                 "DeviceName": "/dev/sda1",
                 "VolumeType": "gp3",
                 "VolumeSize": 100
               }
             }

Back to top

https://admhelp.microfocus.com Enterprise Performance Engineering,LoadRunner Enterprise 8942
Tips to improve your search results...OpenText™ Enterprise Performance Engineering Help Center OpenText™ Enterprise Performance Engineering Help 26.1 All View Local Help Center View Online Help Center Version: