The following topic outlines Parasoft's recommendations for a production-grade deployment of Parasoft Virtualize alongside Parasoft Data Repository and Parasoft Continuous Testing Platform (CTP). Sections in this topic include:
This document assumes that the deployment will include:
There are two deployment approaches: dynamic infrastructure (Docker image or Azure VM) or physical static infrastructure.
Dynamic infrastructures are designed for enabling dynamic, disposable test environments. This means that a test environment can be instantly provisioned from a golden template, used and dirtied, then simply destroyed. There is no need to share test environments or resources across teams or test phases; the exact environment you need is instantly spun up whenever you want it, then destroyed as soon as you’re done with it. Dynamic infrastructures provide advanced flexibility for extreme automation. Moreover, when you need to scale (for example, for performance testing), you can do that on demand.
With a physical static infrastructure, you have permanent (dedicated) servers. This is useful when long-term scaling is anticipated and hardware is designated ahead of time for heavy usage. Such an approach is designed for high availability and fault tolerance requirements. If you have such requirements and plan to configure a cluster of Parasoft Virtualize servers behind a load balancer, also see the recommendations at Setting Up a Cluster of Virtualize Servers Behind a Load Balancer.
Dynamic infrastructures use either Docker, Microsoft Azure, or Amazon Web Services (AWS).
For Docker, we recommend:
For Azure, we recommend:
For AWS, we recommend:
The following diagram shows the recommended architecture for a deployment with three Virtualize servers and CTP. Note that while three Virtualize servers are shown here, you can have as many as you need.
Desktop users should develop assets using their local Virtualize desktop, then connect to a Virtualize Staging Server to test the assets in the staging environment. They will be able to monitor events on the Staging Server and debug their assets then, when a virtual asset is ready, check in the changes to the source control management (SCM) system.
Assets on Production or Performance servers should be updated through the SCM. This ensures that the behavior and performance of assets running on those servers is not affected by development of virtual assets and helps keep the product/performance servers stable. Performance servers should be configured based on the principles outlined in Performance Tuning a Virtualize Server. Updates of assets from the SCM could be scheduled or on demand, based on what best fits the current needs. For example, deployments in Kubernetes might use an initContainer to pull from the SCM while those using a physical server might have a job that runs on demand from an automation server.
Using a single server for both staging and production has inherent risks. While it can be done, it is not recommended for several reasons. For example, a desktop user could redeploy an asset while a test is using the server, causing failures, or monitor an asset during a load test, causing a decrease in throughput. Without a separation of staging and production environments, it's possible that a desktop user's development of assets could negatively impact automated tests or load testing.
It is recommended to minimize the network latency between a Virtualize server and a Data Repository server as much as possible. Network latency between the processes can negatively impact the performance of the Virtualize server under load. The most common way this is done is to install them on the same machine, or two machines that are co-located as much as possible (for example, same data center region). The Data Repository server can consume a large amount of memory, so when installing it on the same machine as a Virtualize server, it is advised that the machine have at least 32GB RAM.
We recommend the following hardware for the Virtualize, Data Repository, and CTP server machines:
We recommend Linux over Windows for Parasoft deployments because:
CTP supports Oracle, HyperSQL, and MySQL, but we strongly recommend Oracle or HyperSQL over MySQL; in a nutshell, our recommendation is:
Oracle >= HyperSQL > MySQL |
Oracle and HSQLDB perform equally well, but MySQL is difficult and challenging to troubleshoot. If you do not plan on clustering the CTP database and you have sufficient space, we recommend HyperSQL.
When VMs are deployed in the cloud through cloud service providers, such as Microsoft Azure and Amazon AWS, machine IDs may change as the VM is shut down and restarted. Use the following flag when starting Parasoft products to ensure that the machine ID remains stable when VMs are restarted on cloud platforms:
-Dparasoft.cloudvm=true |