Testing and Results of Cluster Master Shutdown as well as Tomcat

Testing and Results of Cluster Master Shutdown as well as Tomcat

Product Line:  VERDE

Testing was performed on a Clustered environment in order to obtain true behavior as a result of a Cluster Master failure and failover.

Given the following configuration:  
VERDE Cluster Configuration:
  • 1 server dedicated to Cluster Master (i.e., no VDI support)
  • 1 server dedicated to VDI only
  • 1 separate desktop to verify Remote Access feature
  • Client - Software Client.

Test 1:

  • Log in as user to VERDE Cluster Master.
  • Launch a VDI guest session.
  • While the client is connected to the guest VDI session - shutdown the Cluster Master.

What happens to the existing client connection to the guest VDI session? Is it maintained or broken?

 

  • After Shutting down Cluster Master Server, VDI session connection on Verde Client gets disconnected.

 

Test 2:

  • Log in as user to VERDE Cluster Master.
  • Launch a Remote Access session.
  • While the client is connected to the Remote Access session - shutdown the Cluster Master.

What happens to the existing client connection to the Remote Access session? Is it maintained or broken?

 

  • After Shutting down Cluster Master Server, Remote Access session connection on Verde Client gets disconnected.

Then the next Scenario was tested:

Instead of a complete shutdown of the CM - the following:









****NOTE*** Overall Synopsis:   The data traffic for all sessions - VDI and Remote - is routed through the connection broker using one of the VERDE services.  
It is also evident that Tomcat is not used for data traffic - just authentication and initial connection to the desktop.