Configure dynamic infrastructure providers

In order to ensure the use of dynamic infrastructure runs properly in NeoLoad Web, the provider(s) to use must be configured beforehand during the platform setup.

For more information about how to add an infrastructure provider, see Add a Provider.

OpenShift

Configuring OpenShift for use with NeoLoad Web is a mandatory step that must be carried out prior to defining OpenShift as an Infrastructure Provider to run tests from NeoLoad Web.

NeoLoad Web is compatible with OpenShift versions 3.9 and above.

To Configure OpenShift for NeoLoad Web, follow these steps:

  1. Login onto OpenShift:
    user@host:~$ oc login xxxxxxxxxxxxxxxxxxxxxxxxxxx

  2. Create a project for NeoLoad Web:
    user@host:~$ oc new-project my-project
    For more information, see the OpenShift Documentation.

  3. Use project:
    user@host:~$ oc project my-project

  4. Create a service account for NeoLoad Web:
    user@host:~$ oc create serviceaccount nlweb
    For more information, see OpenShift Developer Guide and the OpenShift Admin Guide.

  5. Give "Edit" role to the NeoLoad Web user on theNeoLoad Web project. The "Edit" role is the minimum role required.
    user@host:~$ oc policy add-role-to-user edit system:serviceaccount:my-project:nlweb

  6. Generate the token for the NeoLoad Web user:
    user@host:~$ oc serviceaccounts get-token nlweb

  7. Copy and paste the token in the API Token field of the Infrastructure Provider dialog box in NeoLoad Web. For more information, see Add a Provider.

For more information about how to add an infrastructure provider, see Add a Provider.

Kubernetes

NeoLoad Web is compatible with Kubernetes cluster in versions 1.9 and above. It has been tested with versions 1.9.0 to 1.18.0.

For more information, see NeoLoad Web dynamic infrastructure user access.

User access

For more information about how to set NeoLoad Web dynamic infrastructure user access for Kubernetes, see the NeoLoad Web dynamic infrastructure user access documentation.

The section below describes how to create a user access for NeoLoad Web to communicate with Kubernetes.

The procedure described includes executing a helm chart to create a namespace, a role, a role binding and a service account on the Kubernetes cluster.

Prerequisites:

  • kubectl must be installed and configured to control Kubernetes clusters.

  • Helm must be installed. It is available here.

  • For more information about compatibilities of Helm with Kubernetes distributions,visit this page.

Procedure with Helm commands

  1. Add Neotys helm repository:

    helm repo add {repo-name} https://github.com/Neotys-Labs/helm-dynamic-infrastructure

  2. Deploy credentials:

    helm install {release-name} {repo-name}/nlweb-dynamic-infrastructure-user

  3. After executing the helm commands follow the indications in the logs.