Qyrus Connect HLD
Qyrus Connect High Level Representation
The QloudBridge system includes the following components:
QloudBridge client (GUI)
QloudBridge Server
QloudBridge REST API server
Qyrus identity provider (QIdp)
An overview of how these components interact with the user environment
QloudBridge Client (GUI)
QloudBridge app is a desktop application, which is built to run on Windows, and MacOS, it issues requests to the QloudBridge API Server, starts all the components, and ensures that everything is working as expected.
DERP is the client side component that is responsible for ensuring the connection is established between the QloudBridge Client and Server.
HTTP Proxy: this contains a non-caching HTTP proxy that sends HTTP requests coming from tests that run on virtual machines (VMs) or devices on the Qyrus infrastructure to the website or app that is hosted inside the user’s firewall (either on an intranet or a local machine).
QloudBridge Server
The server is a VM (or container) running in Qyrus data centers and it includes the following components:
Control Plane (Tunnel Controller): this is the logic that is responsible for configuring the connection for the QloudBridge Client request, and also communication with the other internal components like custom hosted DERP Servers.
STUN Server: This component is responsible to identify the application under test behind a firewall and the type of firewall, and configuring the appropriate NAT (DNAT, SNAT) type.
TURN (Relay Server): while performing application performance tests it's important to keep the connection alive to complete the test. This component ensures the QloudBridge client doesn’t break at scale testing.
Qyrus identity provider (QIdp)
QIdp is an authentication server running in Qyrus data centers, and is responsible to secure the connection between QloudBridge client and server by using SAML, oAuth2, SSO configuration methods.
System and Network Requirements:
QloudBridge requirements vary, depending on the number of parallel tests you plan to run.
Keep in mind that these are guidelines. Most environments have their own workload requirements for optimal performance. Test and profile your own environment using these recommendations as a baseline.
Transport Layer Security (TLS) Requirements:
TLS version 1.2 or higher
TLS/SSL library (e.g., OpenSSL)
Network port 443, through which all traffic between your site and a QloudBridge tunnel endpoint must pass.
Configuring Your Network to Use QloudBridge:
Outbound
REST API tunnel endpoint
To validate the REST API certificate
To establish the tunnel:
When your tests are running through a QloudBridge tunnel, the client on your network needs to make two types of outbound connections:
To pass status information: Communication to the Qyrus REST API tunnels endpoint.
To connect with the site or app under test: Communication to the sites or apps you specify in your tests.
Allowlisting for Restricted Networks
As an important step prior to downloading QloudBridge, you or your systems administrator will need to verify that QloudBridge can make the required network requests.
Log into the machine that will be hosting your QloudBridge application. This is the machine where you’ll eventually be placing and running the downloaded QloudBridge GUI app.
Use cURL (or equivalent tool) to check the connectivity between the machine and
REST API Endpoints
https://localtesting.qyrus.com https://locatesting-wrapper.qyrus.com
Last updated