Method and system for deploying a production system in a virtualized environment

Abstract

Embodiments of the present invention provide methods and systems for deploying production systems in a virtualized environment. Example implementations relate to systems and methods for determining the readiness of a data center environment for deploying a production system in a virtualized environment within the data center environment. The method includes receiving parameter data of a device controller and first configuration data of computing devices from a device controller that manages the deployment and configuration of the virtualized environment, and receiving second configuration data of a networking switch. Furthermore, the method includes verifying the parameter data and the first and second configuration data by comparing them with predetermined data necessary for deploying the production system. The method also includes performing connectivity tests between the computing devices. Additionally, the method includes generating a report for deployment of the production system by the device controller, the report having the parameter data, the first and second configuration data, the results of the connectivity tests, and one of error or warning messages based on the verification results.

Description

Background Technology

[0001] Data centers can include computing devices used to host one or more workloads (applications) for customers. Increased demand for data center services leads to increased complexity and scale of data centers. Virtualizing computing devices in a data center simplifies data center operations, expands data center capacity to meet growing demands, and reduces the size of the data center. For example, virtualization software deployed on each computing device in a data center can allow the corresponding computing device to be virtualized as one or more virtual machines. Therefore, each virtual machine can operate like a physical computing device with its own operating system to host one or more workloads for customers in a virtualized environment within the data center. Attached Figure Description

[0002] These and other features, aspects, and advantages of this specification will be better understood when the following detailed description is read with reference to the accompanying drawings, in which the same characters denote the same parts throughout the drawings, wherein:

[0003] Figure 1 This is a block diagram depicting a readiness analyzer engine according to some examples of this disclosure, which is communicatively coupled to a data center environment and a networked switch;

[0004] Figure 2 This is a block diagram depicting a ready analyzer engine according to some examples of the present disclosure, the ready analyzer engine having processing resources operatively coupled to a machine-readable medium storing executable program instructions;

[0005] Figure 3 This is a block diagram depicting processing resources and machine-readable media and processing resources encoded with example instructions according to some examples of this disclosure, which are executable by a readiness analyzer engine to verify the readiness of computing devices and networking switches in a data center environment for deploying production systems in a virtualized environment of the data center environment.

[0006] Figure 4 This is a flowchart depicting some examples of methods according to this disclosure, methods for verifying the readiness of computing devices and networking switches for deploying production systems in a virtualized environment within a data center environment; and

[0007] Figure 5 This is a flowchart depicting some examples of methods according to the present disclosure for performing connectivity tests between computing devices via a networked switch for deploying production systems in a virtualized environment within a data center environment.

[0008] It should be emphasized that the features in the accompanying drawings are not drawn to scale. In fact, for clarity of discussion, the dimensions of the features have been arbitrarily increased or decreased in the accompanying drawings. Detailed Implementation

[0009] The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numerals are used in the drawings and the following description to refer to the same or similar parts. It should be clearly understood that the drawings are for illustrative and descriptive purposes only. Although several examples are described in this document, modifications, adaptations, and other implementations are possible. Therefore, the following detailed description does not limit the disclosed examples. Rather, the appropriate scope of the disclosed examples may be defined by the appended claims.

[0010] The terminology used herein is for the purpose of describing specific examples and is not intended to be limiting. As used herein, unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” are intended to also include the plural forms. As used herein, the term “another” is defined as at least a second or more. Unless otherwise stated, the term “coupled” as used herein is defined as “connected,” whether a direct connection without any intermediary element or an indirect connection with at least one intermediary element. For example, two elements may be connected mechanically, electrically, or communicatively via a communication channel, pathway, network, or system. As used herein, the term “and / or” refers to and covers any and all possible combinations of the associated listed items. It should also be understood that although the terms first, second, third, etc., may be used herein to describe various elements, these elements should not be limited by these terms, as these terms are used only to distinguish one element from another, unless otherwise stated or indicated by the context. As used herein, the term “comprising” means including but not limited to, and the term “including” means including but not limited to. The term “based on” means at least partially based on.

[0011] As used herein, the term "production system" refers to a mission-critical system deployed in a virtualized environment within a data center environment. This virtualization is configured to cluster multiple computing devices together using a high-speed architecture and integrate with storage devices and multiple networked switches. In other words, the term "mission-critical system" can refer to a fault-tolerant system configured to operate even when one or more of its components fail, thus providing an intermittent production platform for hosting one or more workloads (such as mission-critical workloads (or applications)). Therefore, mission-critical systems can utilize one or more backup components that can automatically replace one or more failed components, ensuring that the services provided by mission-critical workloads hosted on the mission-critical system are not lost.

[0012] As used herein, the term "mission-critical workload" can refer to an uninterrupted production workload (provided by a mission-critical system) designed to seamlessly deliver the expected services to one or more users connected to the mission-critical workload. Examples of mission-critical workloads can include stock market applications, navigation support applications for spacecraft, and so on.

[0013] As used herein, the term "virtualized environment" can refer to a computing environment deployed on each of multiple computing devices in a data center environment to create one or more virtual machines on the corresponding computing devices, where each virtual machine can exist independently by using the computing resources (physical resources) of the corresponding computing device. A virtualized environment can be deployed by implementing virtualization software on each of the multiple computing devices. As used herein, the term "device controller" can refer to a centralized management unit communicatively coupled to multiple computing devices for managing the virtualized environment and / or the process of deploying and configuring production systems within the virtualized environment.

[0014] For the purposes of explaining this disclosure, see reference to Figures 1 to 5 The components illustrated are used to describe certain examples. However, the functionality of the illustrated components may overlap and may exist in fewer or more elements and components. Furthermore, all or part of the functionality of the illustrated elements may coexist or be distributed across several geographically dispersed locations. Moreover, the disclosed examples can be implemented in various environments and are not limited to the illustrated examples. Furthermore, in conjunction with… Figure 1 and Figures 4-5 The described sequence of operations is exemplary and not restrictive. Additional or fewer operations or combinations of operations may be used or modified without departing from the scope of the disclosed examples. Therefore, this disclosure merely sets forth examples of implementations, and many variations and modifications can be made to the described examples. Such modifications and variations are intended to be included within the scope of this disclosure and protected by the following claims.

[0015] A data center environment comprises multiple computing devices used to host one or more workloads of a customer. Due to increased demand for data center services over a period of time, data center environments are virtualized to meet this increased demand and also to reduce the complexity and scale of the data center environment. For example, virtualization software such as a hypervisor can be deployed on each of the multiple computing devices to virtualize the data center environment into a virtualized environment. Furthermore, one or more virtual machines can be created on the virtualized environment deployed on each computing device. These one or more virtual machines can be customized based on the customer's needs for deploying production systems in the virtualized environment. In such an example, the production system can then host (or execute) one or more workloads (or applications) of the customer to meet the service requirements of the data center environment.

[0016] However, data center environments may require certain essential configurations to deploy specific types of production systems (e.g., mission-critical systems in a virtualized environment within a data center). These essential configurations may include specific hardware, software or firmware versions, networks, storage, connectivity between computing systems via networking switches, etc., to ensure that the mission-critical system is highly available (e.g., fault-tolerant) for hosting one or more workloads (such as mission-critical workloads (or applications)) to seamlessly serve connected users.

[0017] A data center environment lacking the necessary configuration may force data center administrators to perform additional tasks during the actual deployment of mission-critical systems in a virtualized environment. This delays the deployment of mission-critical systems and the hosting of one or more workloads on such systems. In some examples, these additional tasks may include performing troubleshooting activities on the data center environment to identify problems in the configuration of the data center environment and connectivity between computing devices via networking switches, and to fix the identified configuration and connectivity issues.

[0018] A feasible technical solution to the aforementioned problem may include determining the readiness of a data center environment for deploying a production environment, such as the readiness to deploy mission-critical systems in a virtualized environment within the data center. In other words, this technical solution may include performing pre-deployment activities, such as validating the data center environment for the necessary configurations required to deploy the mission-critical system, even before attempting to actually deploy the mission-critical system in the virtualized environment. Therefore, performing pre-deployment activities can result in pre-identifying configuration problems in the data center environment and fixing these identified configuration problems before actual deployment. Thus, pre-performed pre-deployment activities can reduce the complexity during the actual deployment of mission-critical systems and the total time spent on actual deployment. In some non-limiting examples, fixing identified configuration problems may include, for example, adding hardware, upgrading software or firmware versions, adding storage devices, fixing network problems, correcting network interfaces for connectivity issues between computing systems, etc.

[0019] Therefore, this disclosure describes an example implementation of a system and method for determining the readiness of a data center for deploying production systems, such as mission-critical systems deployed in a virtualized environment of multiple computing devices within a data center environment. The method includes receiving parameter data from a device controller and first configuration data from a plurality of computing devices, the device controller managing the deployment and configuration of the virtual environment. The method also includes receiving second configuration data from a plurality of networking switches connected to the plurality of computing devices. Furthermore, the method includes verifying the parameter data, the first and second configuration data by comparing them with predetermined data necessary for deploying the mission-critical system. The method also includes performing connectivity tests between the plurality of computing devices. Additionally, the method includes generating a report having the parameter data, the first and second configuration data, connectivity test results, and at least one of the following based on the verification results: error messages or warning messages, for use in deploying the production system via the device controller. The method also includes evaluating the report to determine the readiness of the plurality of computing devices and the plurality of networking switches for deploying the production system in the virtualized environment.

[0020] Figure 1A block diagram of a readiness analyzer engine 100 according to some examples of this disclosure is depicted. The readiness analyzer engine 100 is communicatively coupled to a data center environment 102 and multiple networking switches 108. The data center environment 102 includes a device controller 104 and multiple computing devices 106. In some examples, the data center environment 102 may additionally include external storage devices (not shown) connected to one or more of the multiple computing devices 106. In one or more examples, the multiple computing devices 106 may be clustered together and integrated via a high-speed structure 110 extending through the multiple networking switches 108 to create a dedicated network (production system) in the data center environment 102. In some examples, an administrator 114 of the data center environment 102 may select multiple computing devices 106 to deploy a production system. For example, the administrator 114 may select different types of hardware components manufactured from a particular vendor and select a specific number of hardware components in each computing device 106 to make the data center environment 102 compatible for deploying a production system. For example, administrator 114 can select network interface card (NIC) cards manufactured by a specific vendor "AAA", and can select to include at least two NIC cards in each computing device 106.

[0021] Device controller 104 is a centralized management unit implemented using hardware devices (e.g., electronic circuitry, logic, or processors), or any combination of hardware and programs (e.g., instructions stored on a machine-readable medium). In some examples, device controller 104 is connected to multiple computing devices 106 via high-speed architecture 110 and communicatively coupled to readiness analyzer engine 100 via network 112. In one or more examples, network 112 may be a TCP / IP (Transmission Control Protocol / Internet Protocol) network, a set of communication protocols for interconnecting network devices on the Internet.

[0022] Device controller 104 can manage i) the deployment of virtualization environment 150 on data center environment 102, ii) the configuration of multiple computing devices 106 within virtualization environment 150, and iii) enabling connectivity between the multiple computing devices 106 for deploying production systems within virtualization environment 150. The steps involved in i) deploying virtualization environment 150, ii) configuring multiple computing devices 106, and iii) interconnecting the multiple computing devices 106 are discussed in more detail below. In one or more examples, without departing from the scope of this disclosure, virtualization environment 150 may be a cloud infrastructure environment, a hyper-manager infrastructure environment, etc. In some examples, the hyper-manager infrastructure environment may be a VMware environment. In some other examples, the cloud infrastructure environment may be an Azure environment, an Amazon Web Services (AWS) environment, etc., without departing from the scope of this disclosure.

[0023] In some examples, device controller 104 may include a management unit and a workflow automation unit for managing the deployment and configuration of: i) virtualization environment 150 and ii) production systems within virtualization environment 150. In some examples, the management unit may be a vCenter server, and the workflow automation unit may be a vRealize orchestrator. In one or more examples, the production system is a mission-critical system. For example, a mission-critical system may refer to a fault-tolerant system (or uninterrupted production platform) deployed in virtualization environment 150 for hosting workloads to seamlessly provide the expected service to one or more users connected to the workloads.

[0024] Device controller 104 may have parameter data recorded in a management inventory list stored on the storage drive of device controller 104. In some examples, the parameter data may include resource information such as i) general attributes of device controller 104, ii) the type of deployment engine used to deploy mission-critical systems, and iii) user permissions within device controller 104. Sample parameter data for device controller 104 is shown in Table 1 below for reference.

[0025]

[0026] Table 1

[0027] Referring to Table 1, user permissions can refer to the details of a user and their roles defined in the device controller 104. For example, roles include administrator roles, user roles, etc., which are defined in the management unit of the device controller 104.

[0028] In some examples, device controller 104 may deploy virtualization software on each of the multiple computing devices 106 to virtualize data center environment 102 into virtualization environment 150. This allows each computing device 106 to act as host device 152 within virtualization environment 150. In some examples, the virtualization software is a super manager, such as EXSi, a Type 1 super manager. In one or more examples, each host device 152 may access multiple computing resources (or resource information) belonging to the corresponding computing device 106. In some non-limiting examples, multiple computing resources or resource information may include: i) general attributes of each host device 152, ii) network resources of each host device 152, iii) structure pairs in each host device 152 used for clustering with another host device 152, iv) protocol driver / software / firmware versions installed in each host device 152, v) storage drives mapped to each host device 152, vi) storage adapters of each host device 152, vii) basic input / output system (BIOS) of each host device 152, etc.

[0029] Furthermore, device controller 104 can configure multiple computing resources for each host device 152 (or each computing device 106) to enable each host device 152 to be used to deploy mission-critical systems in virtualization environment 150. Specifically, administrator 114 can use device controller 104 to configure each host device 152. In some examples, administrator 114 can exchange port groups and switch details for each host device 152 based on the specific port into which the NIC card is inserted. Similarly, administrator 114 can install firmware manufactured by a specific vendor and specific versions of firmware based on the requirements (recommended) for deploying production systems. Therefore, device controller 104 can store configuration data of resource information in each host device 152 in a management manifest list. It should be noted here that the configuration data of resource information in each host device 152 (or each computing device 106) can also be referred to as "first configuration data". In other words, as discussed herein, first configuration data may include resource information that can be grouped together as hardware configuration data, network configuration data, and storage configuration data for each computing device 106. Sample first configuration data for each computing device 106 (or host device 152) is shown in Table 2-8 below for reference.

[0030] For example, the general properties of each host device 152 configured by device controller 104 are shown in Table 2 below for reference.

[0031]

[0032]

[0033] Table 2

[0034] The network resources of each host device 152 configured by device controller 104 are shown in Table 3 below for reference.

[0035]

[0036] Table 3

[0037] The structural pairs configured in each host device 152 for clustering with other host devices 152 in the data center environment 102 are shown in Table 4 below for reference.

[0038] PCI devices; port groups 0000:37:00.0; RocEX 0000:37:00.1; RocEY 0000:86:00.0; RocEX 0000:86:00.1; RocEY

[0039] Table 4

[0040] The protocol driver / software / firmware versions required for communication with other host devices 152 and installed in each host device 152 are shown in Table 5 below for reference.

[0041] Manufacturer "BBB" OFED version: 4.17.70.1-1OEM.670.0.0.8169922 Manufacturer "BBB" MST version: 4.14.2.17-1OEM.650.0.0.4598673 Manufacturer "BBB" MFT version: 4.14.2.17-0

[0042] Table 5

[0043] The storage drives mapped by device controller 104 to each host device 152 are shown in Table 6 below for reference.

[0044]

[0045] Table 6

[0046] The storage adapters of host device 152, configured by device controller 104 in data center environment 102, are shown in Table 7 below for reference.

[0047]

[0048] Table 7

[0049] The BIOS of host device 152, configured by device controller 104, is shown in Table 8 below for reference.

[0050]

[0051]

[0052] Table 8

[0053] After completing the tasks related to deploying the virtualization environment 150 on each computing device 106 and configuring the host device 152 in the virtualization environment 150, the first configuration data corresponding to each computing device 106 stored in the device controller 104 can be accessed by (multiple) valid / authenticated users of the device controller 104.

[0054] The readiness analyzer engine 100 may be a utility engine implemented on a computing system 116 located outside the data center environment 102. For example, the readiness analyzer engine 100 may use hardware devices (e.g., electronic circuitry, logic, or processors) or any combination of hardware and programs (e.g., instructions stored on a machine-readable medium) to implement the various functionalities described herein.

[0055] The readiness analyzer engine 100 can be configured to determine the readiness of multiple computing devices 106 and multiple networking switches 108 in a data center environment 102 for deploying mission-critical systems in a virtualized environment 150. For example, the readiness analyzer engine 100 can retrieve configuration data from the computing devices 106 and networking switches 108, verify the retrieved configuration data, and generate a report containing a list of discrepancies (or mismatches) identified in the retrieved configuration data compared to predetermined configuration data. The steps involved in retrieving configuration data from the computing devices 106 and networking switches 108, verifying the retrieved configuration data, performing connectivity tests, and generating the report will be discussed in more detail below.

[0056] Furthermore, the readiness analyzer engine 100 can perform connectivity tests between multiple computing devices 106 and generate reports with the connectivity test results. The configuration data analysis and connectivity test results retrieved in the form of reports can help administrators 114 take proactive corrective actions, thereby reducing deployment complexity and total time. This can also enhance the overall customer experience of deploying mission-critical systems in the virtualized environment 150 and using them for their business needs.

[0057] The readiness analyzer engine 100 may have a command-line interface 118 or a graphical user interface (GUI) 120. Therefore, the administrator 114 can run specific commands through the command-line interface 118 or select options from the GUI 120 to retrieve and verify parameters and / or configuration data from the data center environment 102.

[0058] In some examples, administrator 124 can enter user credentials via command-line interface 118 or GUI 120 to allow readiness analyzer engine 100 to establish a connection with device controller 104. For example, readiness analyzer engine 100 can establish a connection with a management snap-in (e.g., vCenter server) of device controller 104. In such an example, device controller 104 can first verify user credentials and then allow readiness analyzer engine 100 to establish a connection with device controller 104 based on the verification of user credentials.

[0059] Furthermore, the readiness analyzer engine 100 can query the management unit of the device controller 104 to obtain parameter data of the device controller 104 and first configuration data of multiple computing devices 106 (or multiple host devices 152). It can be noted that the readiness analyzer engine 100 can receive parameter data as shown in Table 1 and first configuration data as shown in Tables 2-8 from the device controller 104. The readiness analyzer engine 100 can later create a list of functions containing i) parameter data and ii) first configuration data for each of the multiple computing devices 106. The list of functions can be stored in the memory of the readiness analyzer engine 100.

[0060] The readiness analyzer engine 100 can establish connections with multiple network switches 108 simultaneously. In some examples, the readiness analyzer engine 100 can use a secure shell to establish connections with multiple network switches 108. Subsequently, the readiness analyzer engine 100 can run specific commands based on an operating system (OS), such as Onyx or Comware running on each of the multiple network switches 108, to obtain second configuration data from each of the multiple network switches 108. In some examples, the second configuration data may include resource information for the multiple network switches, such as the network interface configuration status for one or more networking protocols in each of the multiple network switches 108. Sample second configuration data is shown in Table 9 for reference.

[0061]

[0062]

[0063] Table 9

[0064] In some examples, the second configuration data of each of the multiple network switches 108, as shown in Table 9, can be updated in a list of utility manifests stored in the memory of the readiness analyzer engine 100.

[0065] The readiness analyzer engine 100 can also obtain predefined data necessary (or recommended) for deploying the mission-critical system in the virtualization environment 150 from the manufacturer of the mission-critical system software. In such examples, the predefined data obtained from the manufacturer can be stored in the storage drive of the readiness analyzer engine 100. In some examples, the predefined data is a predefined inventory list. In some examples, the predefined data includes predefined resource information standards for deploying the mission-critical system. In some examples, the predefined resource information standards may include i) recommended parameter data and ii) recommended configuration data, such as recommended first configuration data and recommended second configuration data, suitable for deploying the mission-critical system in the virtualization environment 150.

[0066] In some examples, the recommended parameter data may include predetermined resource information corresponding to recommended device controllers and their configurations suitable for deploying mission-critical systems. Similarly, the recommended first configuration data may include predetermined resource information corresponding to multiple recommended computing devices and their configuration details suitable for deploying mission-critical systems. Furthermore, the recommended second configuration data may include predetermined resource information corresponding to multiple recommended networking switches and their configuration details suitable for deploying mission-critical systems.

[0067] Although the recommended parameter data and the recommended first and second configuration data discussed above are not shown, it can be noted that such data can be provided by the manufacturer of mission-critical system software in a data format / framework that is substantially similar to the data format / framework used to represent parameter data (see Table 1), first configuration data (see Tables 2-8), and second configuration data (see Table 9).

[0068] Then, by comparing the pre-defined data necessary (or recommended) for deploying a mission-critical system in the virtualization environment 150 (as discussed above), the readiness analyzer engine 100 can verify parameter data (as shown in Table 1), first configuration data (as shown in Tables 2-8), and second configuration data (as shown in Table 9). For example, the readiness analyzer engine 100 can retrieve a pre-defined list of inventory items from the storage drive and compare it with a list of utility inventory items stored in memory to determine error or warning messages based on the comparison of the two lists.

[0069] In one or more examples, verification may include processing resource information in parameter data and first and second configuration data to determine whether the resource information meets predetermined resource information criteria, thereby generating error messages and / or warning messages. In such examples, error messages may include indicators that the resource information does not meet predetermined resource information criteria.

[0070] In some examples, referring to the resource information in the parameter data (as shown in Table 1), the current version of the management unit is "111," and the current version of the workflow automation unit is "ABC." However, the predetermined resource information standard in the recommended parameter data might be that the recommended management unit version is "111" and the recommended workflow automation unit version is "XYZ." Furthermore, the predetermined resource information standard in the recommended parameter data could recommend that workflow automation unit versions "XYZ" or "AAA" be compatible with the management unit version "111" to ensure workflow operation for system deployment. In such examples, the readiness analyzer engine 100 can compare the parameter data and the recommended parameter data and determine error messages in the current version of the workflow automation unit, as well as compatibility mismatches / differences between the current version of the workflow automation unit and the current version of the management unit. For example, the error message might include an indicator that the current version of the workflow automation unit does not meet the predetermined workflow automation unit version standard. Additionally, the error message might include an indication that the compatibility between the current version of the workflow automation unit and the current version of the management unit does not meet the predetermined compatibility standard between the workflow automation unit and the management unit.

[0071] In some other examples, referring to the first configuration data shown in Table 3, the network resources (or resource information) of one computing device in computing device 106 may have a number of NIC cards of "1". However, the recommended first configuration data may recommend a number of NIC cards of "2" in each computing device. In such an example, the readiness analyzer engine 100 may compare the first configuration data and the recommended first configuration data and determine an error message indicating that one computing device in computing device 106 does not have the required number of NIC cards. For example, the error message may include an indicator that the network resources do not meet a predetermined network resource criterion.

[0072] In some other examples, referring to the first configuration data shown in Table 8, the BIOS in one of the computing devices 106 may not have logical drives. However, the recommended first configuration data may recommend that the BIOS of each computing device should have logical drives. In such an example, the readiness analyzer engine 100 can compare the first configuration data with the recommended first configuration data and determine an error message indicating that the BIOS of one of the computing devices 106 does not have logical drives. For example, the error message may include an indicator that the BIOS resource does not meet a predetermined BIOS resource standard.

[0073] In some examples, referring to the second configuration data shown in Table 9, the spanning tree protocol (STP) setting state is enabled. However, the recommended second configuration data may recommend disabling this STP setting state. In such an example, the readiness analyzer engine 100 can compare the second configuration data with the recommended second configuration data and determine an error message in one of the network switches 108 that enables the STP setting state, which might otherwise be disabled. For example, the error message may include an indicator that the network switch protocol settings do not meet predetermined protocol setting criteria.

[0074] In one or more examples, the warning message may represent resource information for multiple computing devices 106 that is not necessary for deploying a production system in the virtualization environment 150. In other words, the warning message may include another indicator that the resource information is not necessary for deploying a production system in the virtualization environment.

[0075] In some examples, referring to the first configuration data shown in Table 8, the BIOS in one of the computing devices 106 may not have a RAID value of "0". However, the recommended first configuration data may recommend that the BIOS of each computing device should have a RAID value set to "1". In such an example, the readiness analyzer engine 100 can compare the first configuration data and the recommended first configuration data, and determine a warning message in one of the computing devices 106 based on the current RAID value set to "0" (instead of the recommended value "1"). For example, the warning message may include an indicator that the BIOS RAID value set to "0" is not necessary for deploying a production system in a virtualized environment.

[0076] In some other examples, the network resources in one of the computing devices 106 may have a number of NICs of "3". However, recommended first configuration data may recommend a number of NICs of "2" in each computing device. In such an example, the readiness analyzer engine 100 may compare the first configuration data and the recommended first configuration data and determine a warning message indicating that one of the computing devices 106 has more than the required number of NICs. For example, the warning message may include an indication that a number of 3 NICs is not necessary for deploying a production system in a virtualized environment. In such an example, the administrator 114 may remove or deconfigure such resource information based on the warning message from the readiness analyzer engine 100.

[0077] Based on the verification results for the production system deployed by the device controller, the readiness analyzer engine 100 can generate a sub-report that includes parameter data, first configuration data and second configuration data, and at least one of the following: error messages and warning messages.

[0078] Furthermore, the readiness analyzer engine 100 can initiate connectivity tests between multiple computing devices 106. For example, the readiness analyzer engine 100 can perform interconnect verification between multiple computing devices 106 configured in a data center environment 102. In one or more examples, deploying a mission-critical system in a virtualization environment 140 may require clustering multiple computing devices 106 together using redundant high-speed architecture 110 and integrating them with storage devices and networking switches 108. To ensure that multiple computing devices 106 are clustered together, the readiness analyzer engine 100 can request the device controller 104 to deploy at least one virtual test computer machine 154 in the virtualization environment 150 on each computing device 106. For example, the device controller 104 can deploy at least one virtual test computer machine 154 for each architecture pair configured in the corresponding host device 152. Later, the device controller 104 can power on each virtual test computer machine 154.

[0079] Furthermore, the readiness analyzer engine 100 can request the device controller 104 to configure network interfaces on each of the multiple virtual test computers 154. For example, the device controller 104 can configure network interfaces such as "eth0", "ibx", and "iby" on each virtual test computer 154. In some examples, network interface "eth0" is configured to verify connectivity between host devices 152 via a maintenance network. Similarly, network interfaces "ibx" and "iby" are configured to verify connectivity between host devices 152 via a switched network. Since deploying mission-critical systems may require interconnecting host devices 152 via redundant networking switches 108 for fault tolerance, one networking switch 108 is configured for network interface "ibx", while another networking switch 108 is configured for network interface "iby".

[0080] Furthermore, the readiness analyzer engine 100 can perform connectivity tests between multiple virtual test computers 154 via multiple network switches 108. In some examples, ping tests are used to perform connectivity tests. For example, performing a ping test involves each network interface (“eth0”, “ibx”, and “iby”) of a virtual test computer 154A belonging to host device 152A pinging each network interface of another virtual test computer 154B belonging to another host device 152B in data center environment 102. The goal of the ping test is to verify connectivity between the virtual test computers 154 and detect any unintentional cross-connections between them. For example, the “ibx” network interface of a virtual test computer 154A should not be able to ping the “iby” interface of another virtual test computer 154B, while the “ibx” network interface of a virtual test computer 154A should be able to ping the “ibx” interface of another virtual test computer 154B. The readiness analyzer engine 100 can identify one or more failures or successes based on the ping test results. Therefore, for example, the readiness analyzer engine 100 can generate another sub-report based on the ping test, which includes the results of the connectivity test.

[0081] The results of the sample connectivity test are shown in Table 10 for reference.

[0082]

[0083]

[0084] Table 10

[0085] In one or more examples, as discussed above, the readiness analyzer engine 100 can merge the results obtained from the verification of parameter data, first configuration data, second configuration data, and connectivity test results, and generate a merged report. In some examples, the merged report may include parameter data, first configuration data, second configuration data, connectivity test results, and at least one of the following based on the verification results: error messages or warning messages. It should be noted that, for illustrative purposes, no sample merged report is shown, and this should not be construed as a limitation of this disclosure.

[0086] The readiness analyzer engine 100 can also determine the readiness of multiple computing devices 106 and multiple networking switches 108 for deploying production systems in a virtualized environment based on the merged report. For example, the readiness analyzer engine 100 can perform data analysis algorithms on the merged report and communicate error and warning messages, as well as connectivity test failure messages, to the administrator 114. In some other examples, the readiness analyzer engine 100 can make the merged report available for review and analysis by the administrator 114. In all such examples, the administrator 114 can refer to error messages and / or connectivity test failure messages and can easily fix errors in the multiple computing devices 106, the multiple networking switches 108, or connectivity problems between the multiple computing devices 106. After the administrator 114 fixes (or resolves) the errors and / or connectivity problems, the readiness analyzer engine 100 can re-verify at least one of the parameter data, first configuration data, and second configuration data, and verify the connectivity test results to determine the readiness of the data center environment 102 for deploying mission-critical systems in the virtualized environment 150.

[0087] After determining that data center environment 102 is ready for deploying mission-critical systems, device controller 104 can use virtualization software to deploy one or more virtual machines (not shown) on each host device 152 to deploy the mission-critical system in virtualization environment 150. In such an example, device controller 104 may also configure each virtual machine to deploy the mission-critical system in virtualization environment 150. In some examples, a mission-critical system is formed by clustering multiple computing devices 106 (or virtual machines) together using high-speed architecture 110 and integrating them with storage devices (not shown—connected to one or more computing devices 106) and multiple networking switches 108. The mission-critical system in virtualization environment 150 can then facilitate the hosting (execution or running) of one or more workloads (i.e., application software), such as mission-critical workloads for delivering expected services to connected users. In some non-limiting examples, mission-critical workloads may include stock market applications, navigation support applications for spacecraft, etc.

[0088] Figure 2 A block diagram of a readiness analyzer engine 200 is depicted, which includes processing resources 250 and a machine-readable medium 260 storing executable program instructions. It should be noted here that... Figure 2 The readiness analyzer engine 200 mentioned above can be used with... Figure 1 The readiness analyzer engine 100 described herein is the same as or similar to that described herein. In some examples, processing resource 250 is operatively coupled to machine-readable medium 260. Processing resource 250 may be a physical processor. In some examples, the physical processor may be adapted to perform operations related to... Figure 1 The described functional microprocessor. In some examples, the machine-readable medium 260 is non-transient and alternatively referred to as a non-transient machine-readable medium. The processing resource 250 executes one or more program instructions (e.g., processing resource executable program instructions) to perform... Figure 1 One or more functions described in the document.

[0089] Processing resource 250 can execute program instructions to receive parameter data from the device controller and first configuration data for multiple computing devices. In one or more examples, a readiness analyzer engine is communicatively coupled to the device controller. Furthermore, the device controller is connected to multiple computing devices in a data center environment. The device controller manages the deployment and configuration of the virtualization environment in the data center environment. In some examples, the parameter data includes at least one of the following: general attributes of the device controller, the type of deployment engine, or user permissions within the device controller. The first configuration data includes at least one of the following: hardware configuration data, network configuration data, or storage configuration data for each of the multiple computing devices.

[0090] Furthermore, processing resource 250 may later execute one or more program instructions to receive second configuration data from multiple networked switches connected to multiple computing devices. In one or more examples, the readiness analyzer engine may also be communicatively coupled to the multiple networked switches. The second configuration data includes the configuration status of network interfaces for one or more networking protocols in each of the multiple networked switches.

[0091] Processing resource 250 can also execute one or more program instructions to: verify parameter data, first configuration data, and second configuration data by comparing them with predetermined data necessary for deploying a production system in a virtualized environment. In some examples, the predetermined data may be provided by the manufacturer of the mission-critical system software. The predetermined data may include recommended parameter data, recommended first configuration data, and recommended second configuration data for deploying a mission-critical system in a virtualized system.

[0092] Processing resource 250 can also execute one or more program instructions to generate a sub-report for deployment of a production system by the device controller. This sub-report includes parameter data, first configuration data, second configuration data, and at least one of the following based on verification results: error messages and warning messages. In such an example, the readiness analyzer engine can then determine, based on analysis of the sub-report, whether the sub-report includes any error messages. If it is determined that the sub-report does not contain error messages, or in other words, if it is determined, based on analysis of the sub-report, that the parameter data, first configuration data, and second configuration data are configured according to the required (or recommended) configuration, the readiness analyzer engine can then proceed to execute one or more program instructions to perform connectivity tests between multiple computing devices. In some examples, performing connectivity tests includes executing program instructions to instruct the device controller to deploy virtual test computers in a virtualized environment on each of the multiple computing devices and to configure network interfaces on each of the multiple virtual test computers. Furthermore, performing connectivity tests includes executing program instructions to check connectivity between the multiple virtual test computers via multiple networked switches and to generate another sub-report including the connectivity test results.

[0093] Processing resource 250 can also execute one or more program instructions to generate a report (a combination of sub-reports and another sub-report) for deployment of a production system by the device controller. This report includes parameter data, first configuration data, second configuration data, connectivity test results, and at least one of the following based on the verification results: error messages or warning messages. In such an example, an administrator of the data center environment can review the report and fix errors in the data center environment to make it ready for deployment of mission-critical systems in a virtualized environment.

[0094] Figure 3 A block diagram 300 depicts processing resources 350 and machine-readable medium 360, the latter encoded with example instruction codes executed by a readiness analyzer engine for verifying the readiness of computing devices and networking switches in a data center environment for deploying production systems in a virtualized environment within the data center. It should be noted that... Figure 3 The readiness analyzer engines 100 and 200 mentioned above can be respectively connected with... Figures 1-2 The ready analyzer engines 100 and 200 described herein are the same as or similar to those in the description. The machine-readable medium 360 is non-transient and may alternatively be referred to as a non-transient machine-readable medium. In some examples, the machine-readable medium 360 can be accessed by processing resource 350. In some examples, the machine-readable medium 360 stores information such as... Figure 1-2The program instructions corresponding to the functionality of the readiness analyzer engine discussed herein. The machine-readable medium 360 may be encoded with example first, second, third, fourth, and fifth instructions 302, 304, 306, 308, and 310, respectively.

[0095] When executed by processing resource 350, the first instruction 302 can implement the aspect of receiving parameter data from the device controller and first configuration data from multiple computing devices. In one or more examples, the readiness analyzer engine is communicatively coupled to the device controller. Furthermore, the device controller is connected to multiple computing devices in a data center environment, where the device controller manages the deployment and configuration of virtualized environments within the data center environment. The steps of receiving parameter data and first configuration data are described in... Figure 1 It is described in detail in the text.

[0096] When executed by processing resource 350, the second instruction 304 can implement the aspect of receiving second configuration data from multiple networked switches connected to multiple computing devices. In one or more examples, the readiness analyzer engine is communicatively coupled to multiple networked switches. The step of receiving the second configuration data is... Figure 1 It is described in detail in the text.

[0097] When executed by processing resource 350, the third instruction 306 can implement the aspect of verifying parameter data, first configuration data, and second configuration data by comparing them with predetermined data necessary for deploying a production system in a virtualized environment. In some examples, the predetermined data may be provided by the manufacturer of the mission-critical system software. The predetermined data may include recommended parameter data, recommended first configuration data, and recommended second configuration data for deploying a mission-critical system in a virtualized system. The step of verifying the parameter data, first and second configuration data is described in... Figure 1 The details are described in detail. In some examples, the third instruction may also cause the generation of a sub-report for deployment of the production system by the device controller. This sub-report includes parameter data, first configuration data and second configuration data, and at least one of the following based on the verification results: error messages and warning messages.

[0098] When executed by processing resource 350, the fourth instruction 308 can implement aspects of performing connectivity tests between multiple computing devices. In some examples, performing connectivity tests includes executing program instructions to instruct the device controller to deploy virtual test computers in a virtualized environment on each of the multiple computing devices, and to configure network interfaces on each of the multiple virtual test computers. Furthermore, performing connectivity tests includes executing program instructions to check the connectivity between the multiple virtual test computers through multiple network switches and to generate another report including the connectivity test results. The steps of performing connectivity tests between multiple computing devices are described in... Figure 1 It is described in detail in the text.

[0099] When executed by processing resource 350, the fifth instruction 310 can generate a merged report (or consolidated report) for use by the device controller in deploying the production system. The merged report (or consolidated report) includes parameter data, first configuration data, second configuration data, connectivity test results, and at least one of the following based on the verification results: error messages or warning messages. In such an example, the administrator of the data center environment can review the merged report and fix errors in the data center environment to make it ready for deployment of mission-critical systems in a virtualized environment. The step of generating the report (or merged report) is described in... Figure 1 It is described in detail in the text.

[0100] Figure 4 This is a flowchart depicting method 400, which verifies the readiness of computing devices and networking switches for deploying production systems in a virtualized environment within a data center setting. It's important to note that method 400 combines... Figure 1 This is described in one or more examples. Several steps discussed in this paper in method 400 are performed by the readiness analyzer engine.

[0101] Method 400 begins at box 402 and continues to box 404. At box 404, method 400 includes receiving parameter data from a device controller and first configuration data of multiple computing devices in a data center environment, such as... Figure 1As shown in the diagram. In one or more examples, the device controller manages the deployment and configuration of the virtualized environment in the data center environment. In such an example, after the virtualized environment is deployed and configured in the data center environment, the device controller may store a management utility list of parameter data and first configuration data in the device controller's storage drive. In such an example, upon receiving a request from the readiness analyzer engine, the device controller may access the parameter data and first configuration data stored in the device controller's storage drive, and transfer a copy of the parameter data and first parameter data to the readiness analyzer engine. Method 400 continues to box 406.

[0102] At box 406, method 400 includes receiving second configuration data from multiple networked switches, such as Figure 1 As described above. In one or more examples, the network interfaces for one or more network protocols in each of the multiple network switches may have been configured by an administrator. In such an example, a second configuration file with such configuration details can be stored in the storage drive of the corresponding network switch. Therefore, when the multiple network switches receive a request for the second configuration data from the readiness analyzer engine, each network switch can send a copy of the second configuration file to the readiness analyzer engine. Method 400 continues to box 408.

[0103] At box 408, method 400 includes verifying parameter data by comparing it with predetermined data necessary for deploying a production system in a virtualized environment, first configuration data received from a device controller, and second configuration data received from multiple networked switches, such as... Figure 1 As shown in the diagram. For example, verification may include processing parameter data and resource information in the first and second configuration data to determine whether the resource information meets predetermined resource information criteria, thereby generating error messages and / or warning messages. In some examples, the predetermined data may be provided by the manufacturer of the mission-critical system software. The predetermined data may include recommended parameter data, recommended first configuration data, and recommended second configuration data, which are suitable (or recommended) for deploying a mission-critical system in a virtualized system. Method 400 continues to box 410.

[0104] At box 410, method 400 includes generating a report (sub-report) based on verification of parameter data, first configuration data, and second configuration data. This report (sub-report) includes parameter data, first and second configuration data, and at least one of the following: error messages or warning messages, such as... Figure 1As described above. In some examples, error messages may include indicators that resource information does not meet predetermined resource information criteria. Similarly, warning messages may include another indicator that the resource information is not necessary for deploying a production system in a virtualized environment.

[0105] At box 412, method 400 includes determining the readiness of the data center environment based on sub-reports, such as Figure 4 As described in [the document]. In some examples, the readiness analyzer engine can run data analysis algorithms to determine whether a sub-report includes error information. If the sub-report includes error information, the readiness analyzer engine can provide the error information details to the administrator of the data center environment to fix the error in the corresponding computing device and / or networking switch. In some other examples, the readiness analyzer engine can provide the sub-report to the administrator for analysis. After the administrator fixes the error in the corresponding computing device and / or networking switch, the administrator can instruct the readiness analyzer engine to re-verify the readiness of multiple computing devices and networking switches used to deploy mission-critical systems. Therefore, the readiness analyzer engine can re-initiate the readiness verification process for the computing system and networking switches, i.e., "No" at box 412. In particular, the readiness analyzer engine can repeat the steps described in boxes 404 to 410 to re-determine the readiness status of the computing devices and networking switches.

[0106] At box 412, if the readiness analyzer engine determines that the sub-report does not include error information (i.e., "Yes" at box 412), then method 400 continues to box 414, where the readiness analyzer engine can proceed to the following steps: performing connectivity tests between multiple computing devices to further determine the readiness of the data center environment for deploying mission-critical systems in a virtualized environment. Method 400 ends at box 416.

[0107] Figure 5 This is a flowchart depicting a method 500 according to an embodiment of the present disclosure, wherein method 500 performs connectivity tests between computing devices via a network switch for deployment of a production system in a virtualized environment within a data center environment. It should be noted here that method 500 is combined with... Figure 1 and Figure 4 The steps described herein are performed by a combination of a device controller and a readiness analyzer engine in one or more examples.

[0108] Method 500 begins at box 502 and continues to box 504. At box 504, method 500 includes a readiness analyzer engine instructing a device controller to deploy a virtual test computing machine in a virtual environment on each of a plurality of computing devices, such as... Figure 1As discussed in [the document]. In some examples, the device controller can create virtual test computing machines on each host device, which is part of the corresponding computing device portion deployed in a virtualized environment. The method of deploying and configuring the virtualized environment on each computing device to form a host device is [described in the document]. Figure 1 This will be discussed in more detail. Method 500 continues to box 506.

[0109] At box 506, method 500 includes the readiness analyzer engine instructing the device controller to further configure a network interface on each of the plurality of virtual test machines, such as Figure 1 As discussed herein. For example, the device controller can configure network interfaces such as "eth0", "ibx", and "iby" on each virtual test computer. In some examples, network interface "eth0" is configured to verify connectivity between host devices via a maintenance network. Similarly, network interfaces "ibx" and "iby" are configured to verify connectivity between host devices via a switching network. Method 500 continues to box 508.

[0110] At box 508, method 500 includes a readiness analyzer engine examining connectivity between multiple computing devices via multiple network switches, such as Figure 1 As discussed in [the document]. For example, the readiness analyzer engine can perform ping tests to verify connectivity and detect any unintentional cross-connections between them. Method 500 continues to box 510.

[0111] At box 510, method 500 includes the readiness analyzer engine generating another report (another sub-report) that includes the connectivity test results, such as Figure 1 As discussed in [the document]. This method continues to box 512.

[0112] Furthermore, at box 512, method 500 includes determining the readiness of the data center environment based on this other sub-report, such as Figure 1As described in [the document]. In some examples, the readiness analyzer engine can run data analysis algorithms to determine whether the other sub-report includes at least one test failure (as shown in Table 10). If the report includes details of the test failure, the readiness analyzer engine can provide these details to the administrator of the data center environment to repair the network interface, which resulted in a test failure in the corresponding network switch. In some other examples, the readiness analyzer engine can provide the administrator with the other sub-report, including connectivity test results, for analysis. After the administrator repairs the network interface based on the failed test results in the corresponding network switch, the administrator can instruct the readiness analyzer engine to re-verify the connectivity between multiple computing devices for deployment of mission-critical systems. Therefore, the readiness analyzer engine can re-initiate the connectivity test process between multiple computing devices, i.e., "No" at box 512. In particular, the readiness analyzer engine can repeat the steps described in boxes 504 to 510 to re-determine the readiness of the computing devices and network switches based on the connectivity between multiple computing devices via multiple network switches.

[0113] At box 512, if the readiness analyzer engine determines that the other sub-report does not include test failures (i.e., "Yes" at box 512), the method continues to box 514, where the readiness analyzer engine can generate a merged report (or a report—a combination of a sub-report and another sub-report) and provide the merged report based on the verification results and connectivity test results to the administrator. In such an example, the administrator can review the merged report and perform one or more steps to deploy a mission-critical system in a virtualized environment, such as... Figure 1 As discussed in [the document]. Method 500 ends at box 516.

[0114] The various features illustrated in the examples described in this paper can be implemented to perform pre-deployment activities, such as validating the data center environment for the necessary configurations to deploy a mission-critical system even before attempting to actually deploy it in a virtualized environment. Therefore, performing pre-deployment activities can pre-identify configuration issues in the data center environment and fix those issues before actual deployment. This reduces the complexity during the actual deployment of mission-critical systems and the total time spent on actually deploying them.

[0115] In the foregoing description, numerous details have been set forth to provide an understanding of the subject matter disclosed herein. However, these implementations may be practiced without some or all of these details. Other implementations may include modifications, combinations, and variations of the foregoing details. The following claims are intended to cover such modifications and variations.

Claims

1. A method performed by a system including a hardware processor, comprising: Receive parameter data from the device controller, wherein the device controller manages the deployment and configuration of the virtualization environment of the computing environment; Receive first configuration data from multiple computing devices in the computing environment; Receive second configuration data from multiple network switches connected to multiple computing devices, wherein any indication of incompatibility between the resources of the computing devices or the protocol settings of the network switches and a predetermined compatibility standard is based on the parameter data, the first configuration data, and the second configuration data, the predetermined compatibility standard being used to deploy a fault-tolerant production system in the virtualization environment; Deploy virtual test computing machines in the respective computing devices among the plurality of computing devices; Configure the network interface on the virtual test computer to provide fault tolerance through redundant connections of the respective network switches among the plurality of network switches; Connectivity tests between the plurality of computing devices are performed based on triggering communication from the network interface on the virtual test computer, the triggered communication including communication via the redundant connections; and Based on the instructions and the results of the connectivity test, the device controller is used to deploy the virtualized environment and the fault-tolerant production system within the virtualized environment.

2. The method of claim 1, wherein the triggered communication includes a ping from the network interface on the virtual test computer.

3. The method of claim 1, wherein the indication indicates any incompatibility of hardware resources or firmware resources of the computing device.

4. The method according to claim 1, wherein the device controller deploys virtualization software into the computing device of the fault-tolerant production system.

5. The method of claim 4, wherein the virtualization software deployed by the device controller to the computing device of the fault-tolerant production system includes a super manager.

6. The method of claim 1, wherein the first configuration data includes at least one of the following for each of the plurality of computing devices: hardware configuration data, network configuration data, or storage configuration data.

7. The method of claim 1, wherein the second configuration data includes configuration information of a network interface, the network interface being used for one or more networking protocols in each of the plurality of network switches.

8. The method of claim 1, wherein the parameter data includes attributes of the device controller.

9. The method according to claim 1, wherein: The deployment of the fault-tolerant production system in the virtualized environment is also based on a list of functions.

10. The method of claim 1, wherein the system comprises at least one of a command-line interface or a graphical user interface, and wherein the fault-tolerant production system comprises a mission-critical system.

11. A system comprising: processor; as well as A non-transient machine-readable medium storing instructions that can be performed on the processor: Receive parameter data from the device controller, wherein the device controller manages the deployment and configuration of the virtualization environment of the computing environment; Receive first configuration data from multiple computing devices in the computing environment; Receive second configuration data from multiple network switches connected to multiple computing devices, wherein any indication of incompatibility between the resources of the computing devices or the protocol settings of the network switches and a predetermined compatibility standard is based on the parameter data, the first configuration data, and the second configuration data, the predetermined compatibility standard being used to deploy a fault-tolerant production system in the virtualization environment; Deploy virtual test computing machines in the respective computing devices among the plurality of computing devices; Configure the network interface on the virtual test computer to provide fault tolerance through redundant connections of the respective network switches among the plurality of network switches; Connectivity tests between the plurality of computing devices are performed based on triggering communication from the network interface on the virtual test computer, the triggered communication including communication via the redundant connections; and Based on the instructions and the results of the connectivity test, the deployment of the virtualized environment and the fault-tolerant production system within the virtualized environment using the device controller is initiated.

12. The system of claim 11, wherein the triggered communication includes a ping from the network interface on the virtual test computer.

13. The system of claim 11, wherein the indication indicates any incompatibility of hardware resources or firmware resources of the computing device.

14. The system of claim 11, wherein the device controller deploys virtualization software into the computing device of the fault-tolerant production system.

15. The system of claim 14, wherein the virtualization software deployed by the device controller to the computing device of the fault-tolerant production system includes a super manager.

16. The system of claim 11, wherein the first configuration data includes at least one of the following for each of the plurality of computing devices: hardware configuration data, network configuration data, or storage configuration data.

17. A non-transient machine-readable medium comprising instructions that, when executed, cause the system to: Receive parameter data from the device controller, wherein the device controller manages the deployment and configuration of the virtualization environment of the computing environment; Receive first configuration data from multiple computing devices in the computing environment; Receive second configuration data from multiple network switches connected to multiple computing devices, wherein any indication of incompatibility between the resources of the computing devices or the protocol settings of the network switches and a predetermined compatibility standard is based on the parameter data, the first configuration data, and the second configuration data, the predetermined compatibility standard being used to deploy a fault-tolerant production system in the virtualization environment; Deploy virtual test computing machines in the respective computing devices among the plurality of computing devices; Configure the network interface on the virtual test computer to provide fault tolerance through redundant connections of the respective network switches among the plurality of network switches; Connectivity tests between the plurality of computing devices are performed based on triggering communication from the network interface on the virtual test computer, the triggered communication including communication via the redundant connections; and Based on the instructions and the results of the connectivity test, the deployment of the virtualized environment and the fault-tolerant production system within the virtualized environment using the device controller is initiated.

18. The non-transient machine-readable medium of claim 17, wherein the triggered communication includes a ping from the network interface on the virtual test computer.

19. The non-transient machine-readable medium of claim 17, wherein the device controller deploys virtualization software into the computing device of the fault-tolerant production system.

20. The non-transient machine-readable medium of claim 19, wherein the virtualization software deployed by the device controller to the computing device of the fault-tolerant production system includes a super manager.

Images