You can deploy the SOAtest and Virtualize server (or SOAVirt server) manually or using a Helm chart.

Deploying the SOAVirt Server in Kubernetes Manually

To To deploy the SOAVirt server in Kubernetes, follow the process outlined below.toc

Prerequisites

First, create a namespace for the SOAVirt server to run in:

...

1. Open a shell to the running container:

   Code Block
   kubectl exec --stdin --tty soavirt-0 -n parasoft-sv-namespace -- /bin/bash

2. Make a curl call to the SOAVirt REST API to retrieve the machine ID:

   Code Block
   curl http://localhost:9080/soavirt/api/v6/status?fields=machineId

3. Note the machine ID in the response and provide it to your Parasoft representative, who will send you a license password.
4. Once you've received your license password, apply it in the soavirt-config.yaml.

5. Apply the updated soavirt-config.yaml to the running container:

   Code Block
   kubectl apply -f soavirt-config.yaml

6. The license will be applied when the pod is restarted automatically. Alternatively, you can delete and recreate the pod for the changes to take effect.

   Code Block
   kubectl delete -f soavirt.yaml kubectl create -f soavirt.yaml

Deploying SOAVirt Server in Kubernetes with a Helm Chart

You can take advantage of Helm charts to simplify the deployment of SOAVirt server. Helm is a client-side package that uses Helm charts to orchestrate Kubernetes deployments. Using a Helm chart lets you group and coordinate your yaml files so they can be created or deleted with a single command. For more information about using Helm, see Helm Documentation.

Anchor
HelmPrerequisites HelmPrerequisites

Prerequisites

Docker, Kubernetes, and Helm should be installed before you begin.

First, create a namespace for the SOAVirt server to run in:

kubectl create namespace parasoft-sv-namespace

Next, a Persistent Volume and a Persistent Volume claim are needed. Create a Persistent Volume that can be shared by multiple nodes. It should be provisioned with 300GB of space and must have the ReadWriteMany access mode. This space will be used for the workspace of the SOAVirt server and will store configuration settings as well as Virtual Assets.

Warning: The volume must have permissions for the Parasoft user to be able to read and write to the volume. For example, execute the command chown 1000:1000 <shared_path>.

Anchor
HelmSettingUpSOAVirt HelmSettingUpSOAVirt

SOAVirt Setup

1. Download and extract parasoft_soavirt_server_2023.1.1_helm_chart.zip. This zip file contains all the yaml files you will need for this process.

2. Update the values.yaml found in the soavirt-server directory extracted above. At a minimum, the persistence value must be changed to match the name of the Persistent Volume claim configured in Prerequisites above.
   

   Code Block
   persistence: name: soavirt-pvc

   Other values, such as the replica count and namespace, can be changed if necessary.

3. Update the config.yaml found in the soavirt-server/templates directory extracted above. At the minimum, the parasoft.eula.accepted value must be updated to true to accept the EULA:
   

   Code Block
   parasoft.eula.accepted: false

   Other values can be changed if necessary. For example, if you are using a network license, update these fields:
   

   Code Block

   # === PRODUCT LICENSING === # Enables virtualize functionality #virtualize.license.enabled: true # Enables soatest functionality #soatest.license.enabled: true # === NETWORK LICENSE === # Enables network licensing for virtualize #virtualize.license.use_network: true # Specifies the type of network license for virtualize ['performance_server_edition', 'runtime_server_edition', 'custom_edition'] #virtualize.license.network.edition: custom_edition # Specifies features for virtualize 'custom_edition' license #virtualize.license.custom_edition_features: Service Enabled, Performance, Extension Pack, Validate, Message Packs, Extension Framework, Developer Sandbox 1000 Hits/Day, 10000 Hits/Day, 25000 Hits/Day, 50000 Hits/Day, 100000 Hits/Day, 500000 Hits/Day, 1 Million Hits/Day, Unlimited Hits/Day, 30 HPS, 100 HPS # Enables network licensing for soatest #soatest.license.use_network: true # Specifies the type of network license for soatest ['server_edition', 'custom_edition'] #soatest.license.network.edition: custom_edition # Specifies features for soatest 'custom_edition' license #soatest.license.custom_edition_features: RuleWizard, Command Line, SOA, Web, Server API Enabled, Message Packs, Advanced Test Generation Desktop, Advanced Test Generation 5 Users, Advanced Test Generation 25 Users, Advanced Test Generation 100 Users, Requirements Traceability, API Security Testing, Extension Framework # === LICENSE SERVER === # Enables using a specific license server # If true, the license network properties below will be used to retrieve a license # If false, the DTP server properties will be used to retrieve a license #license.network.use.specified.server: false # Specifies license server URL, e.g., https://host[:port][/context-path] #license.network.url: https\://[License Server Host]\:8443 # Enables http authentication for the license server #license.network.auth.enabled: false # Specifies username for license server authentication #license.network.user: [License Server Username] # Specifies password for license server authentication #license.network.password: [License Server Password]

4. Install a helm chart:
   

   Code Block
   helm install my-release soavirt-server/

5. Verify SOAVirt started correctly:
   

   Code Block
   kubectl get pods -n parasoft-sv-namespace kubectl get events -n parasoft-sv-namespace

   
   

Using a Local License: To use a node-lock license, you will need to retrieve the machine ID from the deployed server in order to procure your license from Parasoft and update the config.yaml.

1. Open a shell to the running container:

   Code Block
   kubectl exec --stdin --tty my-release-soavirt-server-0 -n parasoft-sv-namespace -- /bin/bash

2. Make a curl call to the SOAVirt REST API to retrieve the machine ID:

   Code Block
   curl http://localhost:9080/soavirt/api/v6/status?fields=machineId

3. Note the machine ID in the response and provide it to your Parasoft representative, who will send you a license password.

4. Once you've received your license password, update the config.yaml found in the soavirt-server/templates directory extracted earlier to accept a machine-locked license:

   Code Block

   # === NODE-LOCK LICENSE === # Specifies password for virtualize local license #virtualize.license.local.password: [Virtualize License Password] # Specifies password for soatest local license #soatest.license.local.password: [Soatest License Password] # === NETWORK LICENSE === # Enables network licensing for virtualize #virtualize.license.use_network: true # Enables network licensing for soatest #soatest.license.use_network: true

5. Bring down the Helm chart.

   Code Block
   helm uninstall my-release soavirt-server kubectl get pods -n parasoft-sv-namespace kubectl get events -n parasoft-sv-namespace

6. Restart the Helm chart:

   Code Block
   helm install my-release soavirt-server/ kubectl get pods -n parasoft-sv-namespace kubectl get events -n parasoft-sv-namespace

7. Verify that SOAVirt started successfully:

   Code Block
   kubectl get pods -n parasoft-sv-namespace kubectl get events -n parasoft-sv-namespace