Initial cloud settings

This task describes the initial steps required for setting up communication with the cloud.

Initial cloud settings overview

To initially set up communication with a cloud provider, you must establish an account with the cloud provider and obtain the cloud provider credentials. You must then set up communication from LoadRunner Enterprise to your cloud provider, and define network settings for communicating with your cloud-based load generators.

Tip: Alternatively, you can use LoadRunner Enterprise CloudBurst load generators. This provides the benefit of being able to use dynamically provisioned cloud-based hosts without having to maintain subscriptions with cloud providers. For details, see LoadRunner Enterprise CloudBurst load generators.

Initial settings workflow

  1. Create a cloud provider account

    You must first sign up and create a cloud provider account for using the cloud provider.

    For details about creating cloud provider accounts, see the documentation provided by your cloud provider.

    Note: LoadRunner Enterprise currently integrates with Amazon Web Services (EC2) and Microsoft Azure cloud accounts only.

  2. Configure communication to the cloud provider

    When communicating with your cloud provider, you can choose to communicate directly or via a proxy.

    Direct Communication

    The following diagram illustrates direct communication to a cloud provider:

    The communication is initiated from the LoadRunner Enterprise server over the organization's firewall to the cloud provider. The ports on the LoadRunner Enterprise server should be opened for outgoing requests.

    Proxy Server

    The following diagram illustrates communication to a cloud provider through a proxy server:

    The communication is initiated from the LoadRunner Enterprise server to the defined proxy server using HTTP tunneling. The proxy server then runs over the organization's firewall and transfers outgoing requests to the cloud provider.

    For details, see Configure cloud network settings below.

  3. Configure communication to your cloud-based load generators

    When communicating with your cloud-based load generators, you can choose to communicate directly or via a proxy.

    Note:  

    • When the communication is through a proxy, SSL (Secure Socket Layer) is required. SSL is supported between the Controller and the cloud-based load generator.

    • LoadRunner Enterprise supports provisioning of load generators only.

    Direct Communication

    The following diagram illustrates direct communication to a cloud-based load generator:

    The communication is initiated from the LoadRunner Enterprise server and the Controller over a firewall to the cloud-based load generator. Data is transmitted through TCP (Transmission Control Protocol). The Load Generator should allow incoming requests on ports 8080 and 443. LoadRunner Enterprise and the Controller should allow outgoing requests.

    Proxy Server

    The following diagram illustrates communication to a cloud-based load generator through a proxy server:

    The communication is initiated from the LoadRunner Enterprise server and the Controller to the defined proxy server. An HTTP Tunnel is used as a means for communicating from the LoadRunner Enterprise server and the Controller to the proxy server. The proxy server then runs over the firewall and transfers the data to the cloud-based load generator.

    For details, see Configure cloud network settings below.

  4. Configure security settings

    For details on additional security features related to your cloud provider, see Security group rules.

Back to top

Configure cloud network settings

Define cloud network settings for communicating from LoadRunner Enterprise to your cloud provider (define the proxy settings if your organization uses a proxy server for communicating with an outside network), and for communicating with your cloud-based load generators.

  1. Prerequisites

    To enable SSL for your cloud-based load generator, you must create a Certification Authority (CA) and a Digital Certificate and store the files on the LoadRunner Enterprise server and the Controller. For more details on creating the certificates, see Create digital certificates.

  2. In LoadRunner Enterprise Administration, select Configuration > Cloud. In the Accounts tab, click Cloud Network Settings to open the Cloud Network Settings dialog box.

  3. Enable communication from LoadRunner Enterprise to your cloud provider

    1. In the Proxy section, enter the Proxy Server URL (format: http[s]://server[:8080]).

    2. Enter the User Name (format: Domain\username) and Password of a user with connection rights to the proxy server.

    Note: Port 8182 from load generators to the LoadRunner Enterprise server should be opened when running NV emulation for viewing NV related graphs during online. If the port is closed, graphs are still available in the offline results.

  4. Enable communication for a cloud-based load generator

    1. In the LoadRunner Enterprise Communication section, define the communication mode. By default, Use SSL for Load Generator communication is selected. Note that if the communication is through a proxy, SSL is required. The default port value for the proxy server is 443.

    2. If you are using SSL communication, define the following:

      LoadRunner Agent Service Port

      The port used for running Vusers on the load generator. Make sure this port is opened for incoming communication. The default port value is 54345.

      Remote Management Agent Service Port

      The port used for Lab Management operations. Make sure this port is opened for incoming communication. The default port value is 54245.

      Note: If you are using LoadRunner Enterprise CloudBurst load generators with SSL, check with your IT to ensure the required ports are opened on the LoadRunner Enterprise server and on the Controllers. For details, see Add a LoadRunner Enterprise CloudBurst account.

  5. Click Save to save your settings.

Back to top

Define security settings for Amazon EC2 cloud accounts

To define security settings on the cloud provider side for Amazon EC2 cloud accounts, perform the following:

  1. From your cloud provider console, create a security group. The ports defined for communicating with the cloud-based load generator must be opened.

    For details about security groups, see the documentation provided by your cloud provider.

  2. Create a key pair.

  3. If you plan on working with elastic IP addresses, allocate elastic IP addresses and make sure they are opened on your organization's firewall for outgoing communication.

Back to top

Define security settings for Microsoft Azure cloud accounts

To define security settings on the cloud provider side for Microsoft Azure cloud accounts, perform the following:

  1. You must increase your JDK’s strength to Unlimited. Download the appropriate version of the Java Cryptography Extension from java.sun.com. Replace the local_policy.jar, and US_export_policy.jar files in the JRE. The jar files are located by default in C:\Program Files\Micro Focus\ALM\java\jre\lib\security.

  2. Create Windows Azure service certificates in Personal Information Exchange (.pfx) format for use in LoadRunner Enterprise.

  3. Create Windows Azure management certificates in X.509 (.cer) format and upload them to Azure.

Back to top

Next steps: