Abstract: Techniques for migrating virtual desktop sessions in a sticky session environment are disclosed. A load balancer can select a first server to service requests sent by a client, and select a second server to store session data associated with the requests. The load balancer can cause the first server to initiate a transmission of the session data to the second server. The load balancer can forward the requests to the second server in response to determining that a load-related event has occurred. A method, system, and computer-readable medium are provided.

Abstract: Techniques for managing session data in a computer system having a plurality of servers establishing sessions with clients. Communications from any particular client are forwarded to the server assigned to handle that client. A load balancer may determine that any particular session for any particular client should be moved between servers, based on load balancing criteria. In this case, the load balancer causes session data for the server assigned to the client to be transferred to a different server. Acknowledgment signals are sent between the servers and load balancer to indicate completion status. Load balancer maintains backup data at secondary servers which can be brought online when a primary server becomes unresponsive. A method, system, and computer-readable medium are provided.

Abstract: Systems and techniques are described for identifying test gaps. A described technique includes identifying production code paths for an application. Each production code path specifies a respective sequence of code of the application that was executed in a production environment. Test code paths are identified for the application. Each test code path specifies a respective sequence of the application that was tested in a test environment. The production code paths are compared to the test code paths to identify a set of test gaps for the application. Each test gap specifies a respective production code path that is not included in the test code paths. Test gap data specifying the test gaps for the application can be provided for presentation to a user.

Abstract: A recovery management system and recovery method uses dependency information between clients running in a distributed computer system to automatically determine logical fault domains for the clients. The logical fault domains are then prioritized for a recovery process.

Abstract: A resource management system and method for automatically creating affinity-type rules for resource management in a distributed computer system uses association inference information for at least one resource to determine resource association between resources, which is used to automatically create an affinity-type rule for the resources. The affinity-type rule is considered when executing a resource management operation.

Abstract: An example method is provided for virtual machine data placement on a distributed storage system accessible by a duster in a virtualized computing environment. The method may comprise, based on location data relating to the cluster, identifying a first fault domain and a second fault domain of the distributed storage system. The method may further comprise selecting a first host with a first storage resource from the first fault domain and a second host with a second storage resource from the second fault domain. The method may further comprise placing a first copy of the virtual machine data on the first storage resource and a second copy of the virtual machine data on the second storage resource.

Abstract: Test case priorities are automatically determined based on the execution path of a software application that includes priority tags. By embedding the priority tags in the source code of the software application, the consistency and reliability of the test case priorities is improved compared to conventional, primarily manual approaches to determining test case priorities. Further, efficiency is increased by providing run-time feedback regarding test cases that facilitates identification of the highest priority test cases and corresponding test suite optimizations.

Abstract: A computer implemented method for testing the resiliency of a software application. The computer implemented method can test the resiliency of a software application by monitoring the program state of the software application and trigger a shutdown request when the specified program state has been reached. The shutdown request can be transmitted to the application software and executed to shut down one or more functionalities of the software application. In some examples, the method can specify the functionality to shut down and the program state which the shutdown occurs can be specified in an application configuration file.

Abstract: Systems and techniques are described for identifying test gaps. A described technique includes identifying production code paths for an application. Each production code path specifies a respective sequence of code of the application that was executed in a production environment. Test code paths are identified for the application. Each test code path specifies a respective sequence of code of the application that was tested in a test environment. The production code paths are compared to the test code paths to identify a set of first test gaps for the application. Each first test gap specifies a respective production code path that is not included in the test code paths. Test gap data specifying the first test gaps for the application can be provided for presentation to a user.

Abstract: An example method is provided for virtual machine data placement on a distributed storage system accessible by a duster in a virtualized computing environment. The method may comprise, based on location data relating to the cluster, identifying a first fault domain and a second fault domain of the distributed storage system. The method may further comprise selecting a first host with a first storage resource from the first fault domain and a second host with a second storage resource from the second fault domain. The method may further comprise placing a first copy of the virtual machine data on the first storage resource and a second copy of the virtual machine data on the second storage resource.

Abstract: A recovery management system and recovery method uses dependency information between clients running in a distributed computer system to automatically determine logical fault domains for the clients. The logical fault domains are then prioritized for a recovery process.

Abstract: Techniques for managing session data in a computer system having a plurality of servers establishing sessions with clients. Communications from any particular client are forwarded to the server assigned to handle that client. A load balancer may determine that any particular session for any particular client should be moved between servers, based on load balancing criteria. In this case, the load balancer causes session data for the server assigned to the client to be transferred to a different server. Acknowledgment signals are sent between the servers and load balancer to indicate completion status. Load balancer maintains backup data at secondary servers which can be brought online when a primary server becomes unresponsive. A method, system, and computer-readable medium are provided.

Abstract: Systems and techniques are described for identifying test gaps. A described technique includes identifying production code paths for an application. Each production code path specifies a respective sequence of code of the application that was executed in a production environment. Test code paths are identified for the application. Each test code path specifies a respective sequence of code of the application that was tested in a test environment. The production code paths are compared to the test code paths to identify a set of first test gaps for the application. Each first test gap specifies a respective production code path that is not included in the test code paths. Test gap data specifying the first test gaps for the application can be provided for presentation to a user.

Abstract: Systems, computer readable mediums, and techniques are described for converting virtual machine input/output (I/O) requests. One of the techniques includes obtaining access request data for one or more virtual machines (VMs) executing on a physical machine, wherein the access request data characterizes data access requests received from the one or more VMs; classifying, using the access request data, each of the one or more VMs as having either a sequential data access pattern or a random data access pattern;receiving a first I/O request packet from a first VM of the one or more VMs; determining that the first VM has been classified as having a random data access pattern; andsplitting the first I/O request packet into a plurality of second I/O request packets based at least in part on determining that the first VM has been classified as having a random data access pattern.

Abstract: In one embodiment, a method determines a test case containing test code for testing a functionality of a computer system. The test case is associated with metadata. The metadata is parsed to determine a plurality of system test types and one or more parameters for the plurality of system test types wherein the one or more parameters indicate system conditions for the computer system. The method executes a set of tests using the test code with the computer system using the system conditions. Results of the executed set of tests are output for the plurality of system test types.

Abstract: A resource management system and method for automatically creating affinity-type rules for resource management in a distributed computer system uses association inference information for at least one resource to determine resource association between resources, which is used to automatically create an affinity-type rule for the resources. The affinity-type rule is considered when executing a resource management operation.

Abstract: A computer implemented method for testing the resiliency of a software application. The computer implemented method can test the resiliency of a software application by monitoring the program state of the software application and trigger a shutdown request when the specified program state has been reached. The shutdown request can be transmitted to the application software and executed to shut down one or more functionalities of the software application. In some examples, the method can specify the functionality to shut down and the program state which the shutdown occurs can be specified in an application configuration file.

Abstract: Techniques for assigning applications to datastores in a virtual machine environment are disclosed. In an embodiment, applications exhibiting different I/O data access patterns are assigned to datastores by collecting data related to the input-output operations performed by the applications, analyzing the collected data to identify corresponding data access patterns, and assigning applications to datastores based on the identified data access patterns. In this way, applications can be segregated by data access pattern onto separate datastores. For example, random I/O apps and sequential I/O apps can be assigned to different datastores. Additionally, if random I/O apps are found to be comingled with sequential I/O apps on the same datastore, then data associated with the applications can be migrated as necessary to achieve segregation. In an embodiment, random I/O apps and sequential I/O apps are segregated onto datastores that rotate independent of each other.

Abstract: In one embodiment, a method determines a test case containing test code for testing a functionality of a computer system. The test case is associated with metadata. The metadata is parsed to determine a plurality of system test types and one or more parameters for the plurality of system test types wherein the one or more parameters indicate system conditions for the computer system. The method executes a set of tests using the test code with the computer system using the system conditions. Results of the executed set of tests are output for the plurality of system test types.

Abstract: Test case priorities are automatically determined based on the execution path of a software application that includes priority tags. By embedding the priority tags in the source code of the software application, the consistency and reliability of the test case priorities is improved compared to conventional, primarily manual approaches to determining test case priorities. Further, efficiency is increased by providing run-time feedback regarding test cases that facilitates identification of the highest priority test cases and corresponding test suite optimizations.