Automated configuration conflict resolution and lightweight recovery

Through automated configuration verification and testing systems, dynamic matching sorting and tree structure databases are used to solve the problem of virtual machine configuration conflicts in cloud computing, efficient configuration management and lightweight recovery are achieved, and system restart and service losses are avoided.

CN118922815AInactive Publication Date: 2024-11-08MICROSOFT TECHNOLOGY LICENSING LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280093747.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-15
Filing Date
2022-12-23
Publication Date
2024-11-08
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

In a cloud computing environment, configuration conflicts of virtual machines often lead to system failures. Traditional methods to resolve conflicts through system restarts are time-consuming and expensive, and may lead to service losses during configuration changes and recovery.

Method used

Using an automated configuration verification and testing system, through dynamic matching sorting methods and tree structure databases, configuration conflicts are identified and resolved, lightweight recovery is achieved, manual intervention is reduced, and configuration loading and merging processes are optimized.

Benefits of technology

Improves the efficiency and accuracy of virtual machine configuration management, reduces configuration loading time, avoids system restarts, ensures service continuity, and reduces resource waste and recovery costs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118922815A_ABST
    Figure CN118922815A_ABST
Patent Text Reader

Abstract

An automation toolset performs configuration conflict resolution for virtual machines providing services in a networked cloud computing system through a series of automation actions by determining a set of changes to be submitted. The toolset resolves conflicts between multiple possible configurations that may result in erroneous VM states, and merges the configurations in consideration of inputs from the internal and external systems. The toolset operates to identify only varied subsets of differences between a current configuration and a new configuration loaded into the system to simplify configuration loading, and to provide lightweight recovery by rolling only these differences back. Further efficiency is achieved by using an automated test suite environment that is specifically adapted to test and validate the new configuration to ensure correct loading and avoid system failures.
Need to check novelty before this filing date? Find Prior Art

Description

Background Art

[0001] A cloud computing environment, also known as a "cloud computing network", "distributed computing system" or simply "the cloud", provides processing and storage resources on demand from virtual machines, typically over a communications network. The resources provided by a cloud computing network are generally available on demand from a shared pool of configurable computing resources (such as networks, services, storage devices, applications, software services), and the provided resources can generally be quickly provisioned and released with relatively little management input from the user. Services for computing, networking and storage from a cloud computing network give users a versatile and flexible ability to store, communicate and process their data in third-party data centers.

[0002] Virtual machines are typically configured using commands that are loaded to put the virtual machine into an appropriate operating state by maintaining, upgrading, or modifying various computing system parameters. Configurations can be provided by both internal and external parties and multiple different sources, but conflicting configurations for a given virtual machine are therefore possible, which can lead to system failures. Resolving configuration conflicts and restoring a computing system back to an original working state can be expensive and time consuming using traditional methods that typically require a system reboot. Summary of the invention

[0003] The automated configuration verification and testing system performs configuration conflict resolution for multiple virtual machines (VMs) providing services in a networked cloud computing system through a series of automated actions by determining a set of changes to be submitted. The system resolves conflicts between multiple possible configurations that may result in erroneous VM states, and considers input from internal and external systems to merge configurations. The system operates to identify only a subset of changes that are differences between the current configuration and the new configuration loaded into the system to simplify configuration loading, and the system provides lightweight recovery by rolling back only these differences. Further efficiencies can be achieved by using an automated test suite environment that is specifically adapted to test and verify new configurations to ensure correct loading and avoid system failures.

[0004] In an illustrative embodiment, a dynamic matching sorting method is used to provide fast configuration conflict resolution by using a database that organizes configuration options or components as nodes in a tree structure that provides a relationship graph with dependencies. Each configuration is divided into smaller configurations called "minors," which can be applied atomically and grouped by category. Microconfiguration matching sorting can be skipped or reordered based on dependencies in the relationship graph, and dynamic matching sorting priorities are assigned to each microconfiguration. For each category, the conflict type for the first microconfiguration is determined, and rejected microconfigurations and dependencies are discarded. This process is repeated for all microconfigurations, which are combined to create a complete configuration for each category with a submission order. All categories are combined to create a complete configuration.

[0005] Advantageously, an automated configuration validation and testing system provides technical improvements in VM configuration management. Such improvements are particularly beneficial in the following use case: a VM may be deployed in a cluster of multiple VMs, and each VM potentially runs multiple different configurations. Configuration changes requested by customers or other internal / external entities may be erroneous, include overlapping and / or conflicting requirements, or expose the VM to vulnerabilities of loading configurations in the wrong order. Implementation of an automated toolset for a test suite environment reduces the time-consuming manual intervention required to load VM configurations, while improving the accuracy of validating and merging configurations based on multiple input parameters (such as priority and timestamps).

[0006] The automated configuration validation and testing system further provides technical improvements in restoring the system state to the original configuration using a subset of changes identified between configurations that enables lightweight recovery. Compared to the traditional method of having to clear and reset the current configuration by gradually rolling back configuration commands, lightweight recovery is faster and easier to implement without requiring a system restart. In addition, the resources and active time of the VM cluster are not utilized, thereby preventing service loss during configuration changes and recovery.

[0007] The present invention content is provided to introduce the selection of concepts in a simplified form, which will be further described in the specific embodiments below. The present invention content is not intended to identify the key features or basic features of the technical solution claimed for protection, nor is it intended to be used as an aid to determine the scope of the technical solution claimed for protection. In addition, the technical solution claimed for protection is not limited to the implementation of solving any or all shortcomings mentioned in any part of the present disclosure. It should be understood that the technical solution described above can be implemented as a computer-controlled device, a computer process, a computing system, or a product such as one or more computer-readable storage media. These and other various features will become apparent by reading the following specific embodiments and reviewing the associated drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 An illustrative cloud computing environment is shown in which a host computing device supports a cluster of virtual machines (VMs) that The group is configured to work with the automation Verify and test system interoperability;

[0009] Figure 2 shows an illustrative VM configured to provide services by allocating resources based on various parameters;

[0010] Figure 3 Illustrative functional modules of an automated configuration verification and testing system are shown;

[0011] Figure 4 shows an illustrative timeline of an automated configuration verification and test system operated to restore VM state between test cases in a test suite environment;

[0012] Figure 5 shows an illustrative flow chart of a process that may be performed by a configuration verification module;

[0013] Figure 6 shows an illustrative flow chart of a process that may be performed by a load and restore module;

[0014] Figure 7 An illustrative flow chart showing processes that may be performed by internal and external input processing modules;

[0015] Figure 8 An illustrative flow chart showing a process that may be performed by a cancellation module;

[0016] Fig. 9 An illustrative flow chart showing a process that may be performed by a merge module;

[0017] Fig.10 An illustrative flow chart showing a process that may be performed by a flow verification module;

[0018] Fig.11 An illustrative configuration database that can be used with a dynamic match ordering method to implement configuration conflict resolution is shown;

[0019] Fig.12 , 13 and 14 show illustrative methods that may be performed when implementing the present automated configuration conflict resolution and lightweight recovery;

[0020] Fig.15 shows a block diagram of an illustrative computing device that may be used, at least in part, to implement the present automated configuration conflict resolution and lightweight recovery;

[0021] Fig.16 A block diagram showing an illustrative data center that may be used, at least in part, to implement the present automated configuration conflict resolution and lightweight recovery; and

[0022] Fig.17 shows a simplified block diagram of an illustrative computer system that may be used, at least in part, to implement the present automated configuration conflict resolution and lightweight recovery;

[0023] Like reference numerals refer to like elements in the drawings. Unless otherwise indicated, elements are not drawn to scale. DETAILED DESCRIPTION

[0024] Figure 1 A cloud computing environment 100 is shown in which one or more host computing devices 102 support a cluster 105 of multiple virtual machines (VMs) (representatively indicated by reference numeral 110) that is configured to interoperate with an automated configuration verification and testing system 115 via an appropriate interface 120, such as an application program interface (API). The host computing devices may be operated by a cloud service provider 125, such as part of a data center, to provide various services to customers, partners, or other third parties via a communication network 130.

[0025] The automated configuration verification and testing system 115 may be configured to run on one or more computing devices or on other infrastructure operated by a cloud service provider, a federated entity, or a third party. The system 115 is configured to expose a user interface (UI) 135, such as a command line interface (CLI) or a graphical user interface (GUI), and may be co-located with the VM in a data center or remotely operated. In some scenarios, the UI may be adapted to enable manual intervention and / or control of the test system, and may also be adapted to raise alarms and provide notifications, such as during system operation.

[0026] The VM cluster 105 shown in the figure is illustrative, and the cluster architecture may vary depending on the implementation. In this illustrated example, the VMs 110 are arranged into one or more network security groups (NSGs) representatively indicated by reference numeral 140. A load balancer representatively indicated by reference numeral 145 may be utilized with each group of VMs. The virtual machines may be organized as part of a virtual network (VNet) 150 and operated by a controller 155. It should be understood that the VMs may include containers or other virtualization constructs, and the principles described herein are equally applicable to these containers and constructs and / or other virtualization platforms.

[0027] Figure 2An illustrative VM 110 is shown configured to allocate resources 210 to provide a service 205 by taking into account applicable policies, rules, subscriptions, representatively indicated by reference numeral 215, for example. Resources may be further allocated based on various other parameters, which may include, for example, internal / external inputs, configuration change requests, changes in environment / state / conditions, etc., representatively indicated by reference numeral 220. Resources in this illustrative example may include system resources such as computing, networking, or storage.

[0028] A construct referred to as a "configuration" 225 for a VM 110 is used herein to refer to a collection of programming steps used to appropriately maintain, upgrade, and / or modify the computing system parameters of the VM as needed to place the VM in an operating state 230 to meet its design requirements in terms of providing services 205. Conventionally, VM configuration is accomplished by submitting internal or external configurations through a series of steps using a command line interface or other automated configuration script. Typically, in scenarios where there is more than one suitable configuration available, configuration conflict resolution and verification may result in lengthy wait times before a configuration is loaded. When multiple configurations are available, the system may also accept the wrong configuration or accept configurations in the wrong order. As discussed below, compared to conventional configuration management methods, the automated configuration verification and testing system 115 ( Figure 1 ) provides technical and efficiency improvements.

[0029] Figure 3 1 shows illustrative functional modules of the automated configuration verification and testing system 115, which can be used to perform configuration conflict resolution and lightweight recovery processes. The configuration verification module 305 interoperates with three modules including the load and restore module 310, the merge module 315, and the elimination module 320. The load and restore module interoperates with the traffic verification module 325, as shown. These modules and associated processes are described below. Figures 5 to 10 This will be discussed in more detail in the text.

[0030] Configuration verification module 305 is operated in response to input configuration 330 and input from internal and external input processing module 335. Input processing module 335 interfaces with internal input 340 and external input 345. For example, internal input may come from an automated configuration verification and testing system 115 and / or cloud service provider 125 ( Figure 1 ) is a source or entity that is part of or associated with a ). External input can be provided via interface 350, such as by an unrelated entity or a third party. In this illustrative example, the external input includes one or more of timestamp 355, priority 360, specification 365, or other appropriate external input 370.

[0031] Figure 4An illustrative timeline is shown in which the automated configuration verification and testing system 115 is operated in a test suite environment 400 using Figure 3 The functional modules shown in FIG. restore the VM state between test cases. The timeline indicates the operations between the automated configuration verification and testing system, the VM cluster 105, and the system memory 405. The test process begins at step 410, where the automated configuration verification and testing system loads the base configuration into the VM cluster 105. At step 420, the VM cluster stores the configuration state in the memory portion M1 415.

[0032] In step 425, the automated configuration verification and testing system 115 runs the test cases in the first set Set1 for the new configuration to introduce changes to the VM cluster 105. In step 435, the VM cluster stores the changed configuration state in the memory portion M2 430. In step 440, the memory 405 sends the two saved configurations, the base configuration in the memory M1 and the changed configuration in the memory M2, to the automated configuration verification and testing system. Then in step 445 the contents of the M2 memory are deleted.

[0033] At step 450, the automated configuration verification and testing system 115 runs a configuration conflict resolution and lightweight recovery process to resolve conflicts between the corresponding configurations in the M1 memory and the M2 memory. The result of the process is a set of changes between the base configuration and the new configuration associated with the Set1 test case. At step 455, the set of changes that can be used to roll back the VM cluster state to restore the base configuration is sent to the VM cluster 105. The above steps can then be repeated for another newly configured Set2 test case, as shown in step 460. It will be appreciated that the automated configuration verification and testing system can continue to run test cases in an appropriate number and manner to meet the needs of a given implementation.

[0034] Figure 5 An illustrative flow chart of a process that may be performed by the configuration verification module 305 is shown. In this illustrative example, at start block 505, a configuration containing configuration options or components "X" and "Y" (collectively "XY") is entered. It is emphasized that the configuration notations used herein are arbitrary and need not indicate any particular number, arrangement, or type of options that may be instantiated in a given configuration. At block 510, the configuration verification module accepts internal and external inputs to verify the configuration. At decision block 515, if the configuration is invalid, the configuration is discarded at block 520. In some cases, a notification is provided when the configuration verification module discards. If the configuration is valid, the configuration is stored at block 525. The verified configuration is indicated using a basic notation, such as X'Y' at end block 530.

[0035] Figure 6 An illustrative flow chart of the processing that may be performed by the load and restore module 310 is shown. At start block 605, two different configurations XY and AY are loaded from respective memories M1 and M2 ( Figure 4 415 and 430 in FIG. 4 are input to the module. At block 610, the load and restore module performs a difference function between configurations XY and AY. If the result is determined to be a child configuration at decision block 615, the parent configuration is found at block 620 and the child configuration is attached and sent to the VM cluster 105 for use in a lightweight restore ( Figure 4 As used herein and in Fig.11 As discussed in more detail in the text of , a parent configuration is a configuration in the database represented using a tree structure, where the parent configuration is a predecessor of one or more other configurations. A child configuration is a configuration further away from the root configuration in the tree structure and is related to the parent configuration.

[0036] continue Figure 6 , if the result of the difference function is not a sub-configuration, then at block 625, the changes between the base configuration (i.e., M1) and the new configuration (i.e., M2) are added to a change set, which is sent to the VM cluster for removal during lightweight recovery. At decision block 630, if the next configuration is available for processing (e.g., Set3 test case), the process is repeated at block 610. Otherwise, the process terminates at end block 635. Here, the acute accent mark, The A component used to indicate the new configuration includes changes that are removed during a lightweight restore to roll back to the base configuration.

[0037] Figure 7 An illustrative flow chart of the processing that may be performed by the internal and external input processing module 335 is shown. At start block 705, two different configurations XY and AY are retrieved from respective memories M1 and M2 ( Figure 4 415 and 430 in are input to the module. At block 710, the module verifies each configuration. At block 715, the internal and external input processing module processes the external input 345 ( Figure 3 ) determines which configuration to discard. Therefore, in this example, the processed configuration may include XY or AY, as shown in end block 720.

[0038] Figure 8 805, two different configurations XY and AY are retrieved from respective memories M1 and M2 ( Figure 4415 and 430 in M1 are input to the module. At decision box 810, if the configurations in M1 and M2 are not similar, then the process ends at box 835 with a configuration of XA, where the overlapping Y components are eliminated. If the configurations in M1 and M2 are similar, then at decision box 815, if it is a child configuration, the parent configuration is found at box 820, and the child configuration is attached and sent to the VM cluster to be added during lightweight recovery.

[0039] If it is not a sub-configuration at block 815, then at block 825, the configuration is appended to the new configuration. If at decision block 830 the next configuration is available for processing, then the process is repeated at decision block 810. Otherwise, the process terminates at end block 835.

[0040] Fig. 9 1 shows an illustrative flow chart of a process that may be performed by the merge module 315 to aggregate all input configurations into a complete set while also removing common configurations between the inputs. At start block 905, two different configurations XY and AY are retrieved from respective memories M1 and M2 ( Figure 4 415 and 430 in M1 are input to the module. At decision block 910, if the configurations in M1 and M2 are similar, control is passed to decision block 930. If the configuration is already part of the new set of changes, the configuration is discarded at block 935. Otherwise, control is passed to decision block 940. If the next configuration is available for processing, control is passed back to decision block 910. If not, the process terminates at end block 945.

[0041] Returning to the process at decision box 910, if there is no similar configuration between the configurations in M1 and M2, then at box 915, if it is a child configuration, the parent configuration is found at box 920, and the child configuration is attached and sent to the VM cluster to be added during lightweight recovery. If it is not a child configuration, the changes between the base configuration (i.e., M1) and the new configuration (i.e., M2) are added to the change set at box 925 and sent to the VM cluster to be added during lightweight recovery. If the next configuration is available for processing, control passes back to decision box 910 and the process repeats. Otherwise, the process terminates at end box 945. As shown, the merged configuration is AXY because the common configuration Y between the inputs is removed.

[0042] Fig.10 An illustrative flow chart of the processing that may be performed by the flow verification module 325 is shown. The module is arranged to verify a new set of changes and to verify the new set of changes by applying these changes to the test suite environment 400 ( Figure 4) in the device under test (DUT) to recover these changes. In addition, the module can be adapted to automatically set up a call for sending or receiving traffic at the VM to verify the configuration.

[0043] At start block 1005, configuration AY, representing a saved configuration or a configuration provided by a third party, is input to the traffic verification module 325. The module verifies the new configuration at block 1010, where A'Y' represents the verified configuration. At decision block 1015, if the configuration verification is unsuccessful, the verification is considered to have failed at block 1020. If the configuration verification is successful, the old configuration is cleared at block 1025. At block 1030, the verified configuration A'Y' is loaded. At block 1035, the module may call the VM cluster and send traffic to test the configuration. If the traffic flow is successful at decision block 1040, the verification of the new configuration is considered to have passed, and the process ends at block 1045. Otherwise, if the traffic flow is unsuccessful, the configuration verification is considered to have failed at block 1020.

[0044] Fig.11 An illustrative configuration database is shown with which the dynamic match ranking method can be used to implement configuration conflict resolution. The configuration database provides a collection of configuration options, which are expressed as nodes in a relationship graph including a tree structure 1100. Various types of configurations can be represented in the database tree, including, for example, switches, tri-states (i.e., polymorphic with and without levels), strings (e.g., rule names, filter names), hexadecimals (e.g., passwords), and integer values ​​(e.g., load levels).

[0045] As shown, policy data module 1105 is at the root of a tree structure, which can include a parent configuration and a child configuration. As described above, the parent configuration includes the pre-position of one or more other configurations. The child configuration is further away from the root node and is associated with the parent configuration. For example, policy module 1110 is a parent configuration and policy plan 1115 is a child configuration. Leaf configuration includes a node without a child configuration on the tree structure. In the illustrative configuration database tree structure 1100, packet filter 1120 includes leaf configuration. A construction including a smaller input configuration that can be applied atomically, which is referred to as a "micro configuration (minor)", can be utilized because the parent / child configuration has been submitted.

[0046] As indicated by reference numeral 1125, some configuration options in the figure may be completely mutually exclusive (XOR), such that only one can exist in a given configuration. In this illustrative example, either billing module 1130 or policy module 1110 may exist, but not both. Other configuration options in the figure do not have such properties.

[0047] Configuration conflict resolution can be performed by automated configuration verification and testing system 115 ( Figure 1) is performed using a method called "dynamic matching sorting" using a relationship diagram such as the illustrative tree structure 1100. The exemplary dynamic matching sorting method includes 10 steps that can be performed in an automated manner on a suitable computing device that supports an automated system.

[0048] In step 1, a configuration database is expressed using a tree diagram that shows the relationship between input configurations that can be utilized in a VM or VM cluster. In step 2, each input configuration is divided into micro-configurations, i.e., smaller atomic configurations. In step 3, micro-configurations are classified. In step 4, micro-configuration matching sorting is skipped or reordered based on other (multiple) micro-configurations and their dependencies with the micro-configuration. In step 5, a dynamic matching sorting priority is assigned to each micro-configuration.

[0049] In step 6, a conflict type is identified for the first micro-configuration in each category. The conflict type may include, for example, equality, superset, false superset, super-equality, or partial overlap. The equality type includes the same configuration but with different actions. This type of resolution may be based on predefined parameters. The superset type includes a configuration being utilized before another obsolete configuration without any issues. In this case, the conflict type is determined by the elimination module 320 ( Figure 3 ) can be utilized.

[0050] The error superset conflict type includes a configuration being used before another outdated configuration and having the expected problem. This may constitute a special case that requires user intervention. The super equality conflict type includes the same configuration performing the same action. In this case, the elimination module 320 ( Figure 3 ) can be utilized.

[0051] The partially overlapping conflict type includes configurations that may partially overlap in some way. In this case, the merge module 315 ( Figure 3 ) can be utilized.

[0052] Returning to the dynamic matching ordering method, in step 7, once a micro-configuration is selected from the identified conflict types, the rejected configuration and all its child dependent configurations are discarded. Step 8 includes returning to step 4 and continuing until all micro-configurations are processed. In step 9, the micro-configurations are joined to create a complete configuration for each category with a submission order. In step 10, the categories are joined to create a complete and complete configuration.

[0053] In some implementations of automated configuration verification and test systems, the execution of dynamic matching sorting may cause special circumstances.For multi-state configurations, conflicts within multi-state micro-configurations with a range of values ​​based on severity (e.g., warning, minor, major, critical, etc.) can be resolved using an upper limit.When integers are equal, configuration differences can be processed using a lower limit, an upper limit, or averaging, wherein all sub-configurations are run again by a dynamic matching sorting method. Integer types can include free range averaging (i.e., 0-N) or fixed range rigidity (N1, N2, N3 ...). For free range averaging, the conflict resolution process can use one or more of priority and timestamp, predefined lower limit or upper limit, or average. For fixed value rigidity, priority and timestamp can be utilized.For configurations with overlapping value ranges, conflicts can be resolved using a maximum range value.In a configuration arranged in a list form, conflicts within a list element are not considered.In this case, all elements from all configurations are accepted.

[0054] It is understood that the dynamic matching ordering method can be implemented in a manner that allows human intervention to be used to handle exceptions before or during the execution of the method. Where human intervention is utilized, the updated configuration can be utilized to improve the operation of the automated configuration verification and testing system in a fully automated manner.

[0055] Fig.12 1200 is a flowchart of an illustrative method 1200 that can be performed by a computing device. Unless otherwise specified, the methods or steps shown in the flowchart and described in the accompanying text are not constrained to a particular order or sequence. In addition, some methods or its steps may occur or be performed concurrently, and not all methods or steps must be performed in a given implementation, depending on the requirements of such implementation, and some methods or steps may be optionally utilized.

[0056] At block 1205 , a set of input configurations is received that are loadable onto a VM operating in a pristine state and define a corresponding updated operating state for the VM when the set of input configurations is loaded, wherein each input configuration includes a plurality of configuration options.

[0057] At block 1210, a difference function is executed to identify differences between the input configurations. At block 1215, the identified differences are stored in a memory. At block 1220, conflict resolution between the input configurations is implemented by performing at least one of: eliminating overlapping configuration options, merging options in the input configurations into one or more updated configurations.

[0058] At block 1225, the updated configuration is loaded into the VM to bring the VM into an updated operating state. And, at block 1230, the identified differences are provided from the memory to the VM to enable the updated operating state to be rolled back to the original state.

[0059] Fig.13 13 is a flow chart of an illustrative method 1300 that can be performed by a computing device. At block 1305, one or more input parameters applicable to a configuration for a VM are received. At block 1310, a set of configurations that can be loaded onto the VM is processed, wherein each input configuration in the set operates to place the VM in a unique corresponding state. At block 1315, a set of changes between the original configuration and the new configuration in the set is identified. At block 1320, the new configuration is validated based on the received one or more input parameters. And, at block 1325, in response to successful validation, only the identified changes are loaded into the VM to update the VM from the original state to the updated state.

[0060] Fig.14 is a flow chart of an illustrative method 1400 that may be performed by a computing device. At block 1405, a test environment interoperable with a VM cluster is implemented. At block 1410, a base configuration is loaded from the test environment into the VM cluster, wherein the base configuration determines a base configuration state for the VM cluster, and wherein the base configuration state is stored in a first memory. At block 1415, a set of test configuration options in a changed configuration is loaded from the test environment into the VM cluster to cause a change in the base configuration state of the VM cluster, wherein the changed configuration state for the VM cluster is stored in a second memory.

[0061] At block 1420, the base configuration state and the changed configuration state are obtained from the respective first and second memories. At block 1425, the changes between the base configuration state and the changed configuration state are identified. And, at block 1430, the changes are sent from the test environment to the VM cluster so that the changes can be rolled back at the VM cluster to enable lightweight recovery at the VM cluster.

[0062] Fig.15 An illustrative architecture 1500 is shown for a device, such as a server, capable of executing the various components described herein for automated configuration conflict resolution and lightweight recovery. Fig.15The architecture 1500 shown in FIG. 1 includes one or more processors 1502 (e.g., a central processing unit CPU, a dedicated AI chip, a graphics processing unit, etc.), a system memory 1504, including a RAM (random access memory) 1506 and a ROM (read-only memory) 1508, and a system bus 1510 that operatively and functionally couples the components in the architecture 1500. A basic input / output system containing basic routines that help transfer information between elements within the architecture 1500 (such as during startup) is typically stored in the ROM 1508. The architecture 1500 also includes a mass storage device 1512 for storing software code or other computer executable code utilized to implement applications, file systems, and operating systems. The mass storage device 1512 is connected to the processor 1502 through a mass storage controller (not shown) connected to the bus 1510. The mass storage device 1512 and its associated computer-readable storage media provide non-volatile storage for the architecture 1500. Although the descriptions of computer-readable storage media contained herein refer to mass storage devices, such as a hard disk or CD-ROM drive, those skilled in the art will appreciate that computer-readable storage media may be any available storage media that can be accessed through architecture 1500 .

[0063] By way of example and not limitation, computer-readable storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information (such as computer-readable instructions, data structures, program modules or other data). For example, computer-readable media include, but are not limited to, RAM, ROM, EPROM (erasable programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), flash memory or other solid-state memory technology, CD-ROM, DVD, HD-DVD (high-definition DVD), Blu-ray or other optical storage, cassettes, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by the architecture 1500.

[0064] According to various embodiments, the architecture 1500 can operate in a networked environment using logical connections to remote computers via a network. The architecture 1500 can be connected to the network via a network interface unit 1516 connected to the bus 1510. It is understood that the network interface unit 1516 can also be utilized to connect to other types of networks and remote computer systems. The architecture 1500 can also include an input / output controller 1518 for receiving and processing input from a number of other devices, including a keyboard, a mouse, a touch pad, a touch screen, control devices such as buttons and switches, or an electronic stylus (not shown). Fig.15 Similarly, input / output controller 1518 may provide signals to a display screen, user interface, printer, or other type of output device (also not shown). Fig.15 ) provides an output.

[0065] It will be appreciated that the software components described herein, when loaded into the processor 1502 and executed, convert the processor 1502 and the overall architecture 1500 from a general purpose computing system into a customized special purpose computing system to facilitate the functions described herein. The processor 1502 may be composed of any number of transistors or other discrete circuit elements, which may present any number of states individually or collectively. More specifically, the processor 1502 may operate as a finite state machine, in response to executable instructions contained in the software modules disclosed herein. These computer executable instructions may convert the processor 1502 by specifying how the processor 1502 transitions between states, thereby converting the transistors or other discrete hardware elements that constitute the processor 1502.

[0066] The software modules encoded herein presented may also convert the physical structure of the computer-readable storage medium presented herein. In different implementations of the present implementation method, the specific conversion of the physical structure may depend on various factors. Examples of such factors may include, but are not limited to, the technology used to implement the computer-readable storage medium, whether the computer-readable storage medium is characterized as primary storage or secondary storage, etc. For example, if the computer-readable storage medium is implemented as a semiconductor-based memory, the software disclosed herein may be encoded on the computer-readable storage medium by converting the physical state of the semiconductor memory. For example, the software may convert the state of transistors, capacitors, or other discrete circuit elements that constitute the semiconductor memory. The software may also convert the physical state of such components to store data thereon.

[0067] As another example, the computer-readable storage medium disclosed herein can be implemented using magnetic or optical technology. In such an implementation, when the software is encoded therein, the software presented herein can convert the physical state of magnetic or optical media. These conversions can include changing the magnetic properties of a specific location in a given magnetic medium. These conversions can also include changing the physical characteristics or characteristics of a specific location in a given optical medium to change the optical properties of those locations. Without departing from the scope and spirit of this implementation method, other conversions of physical media are possible, and the aforementioned examples are provided only to promote this discussion.

[0068] In view of the above, it can be appreciated that many types of physical transformations occur in architecture 1500 in order to store and execute the software components presented herein. It can also be appreciated that architecture 1500 can include other types of computing devices, including wearable devices, handheld computers, embedded computer systems, smart phones, PDAs, and other types of computing devices known to those skilled in the art. It is also contemplated that architecture 1500 may not include Fig.15All components shown may include those not shown in Fig.15 Other components explicitly shown in the Fig.15 A completely different architecture is shown in .

[0069] Fig.16 is a high-level block diagram of an illustrative data center 1600 that provides cloud computing services or distributed computing services that can be used to implement the present automated configuration conflict resolution and lightweight recovery. The data center 1600 may include Figures 1 to 11 The features disclosed in . Multiple servers 1601 are managed by a data center management controller 1602. Load balancer 1603 distributes requests and computing workloads across servers 1601 to avoid situations where a single server may become overloaded. Load balancer 1603 maximizes the available capacity and performance of resources in data center 1600. Routers / switches 1604 support data traffic between servers 1601 and between data center 1600 and external resources and users (not shown) via external network 1605 (e.g., a local area network (LAN) or the Internet).

[0070] The servers 1601 may be stand-alone computing devices, and / or they may be configured as separate blades in a rack of one or more server devices. The servers 1601 have input / output (I / O) connectors 1606 that manage communications with other database entities. One or more host processors 1607 on each server 1601 run a host operating system (OS) 1608 that supports multiple virtual machines (VMs) 1609. Each VM 1609 may run its own OS, such that each VM OS 1610 on a server is different, or the same, or a mixture of both. The VM OS 1610 may be different versions of the same OS (e.g., different VMs may run different versions of the same OS). Additionally or alternatively, VM OS 1610 may be provided by different manufacturers (e.g., some VMs run operating system, while other VMs run Each VM 1609 may also run one or more applications (Apps) 1611. Each server 1601 also includes a storage device 1612 (e.g., a hard disk drive (HDD)) and a memory 1613 (e.g., RAM), which may be accessed and used by the host processor 1607 and the VM 1609 for storing software code, data, etc. In one embodiment, the VM 1609 may employ a data plane API as disclosed herein.

[0071] The data center 1600 provides a pool of resources on which customers or tenants can dynamically provision and scale applications as needed without having to add servers or additional networking. This allows tenants to obtain the computing resources they need without having to acquire, provision, and manage infrastructure on a per-application, temporary basis. The cloud computing data center 1600 allows tenants to dynamically scale resources up or down to meet the current needs of their business. In addition, the data center operator can provide usage-based services to tenants, so that tenants only pay for the resources they use when they need to use them. For example, a tenant may initially use one VM 1609 on a server 16011 to run its application 1611. When the demand for the application 1611 increases, the data center 1600 can activate the same server 16011 and / or new servers 1601 as needed. N If the demand for the application decreases later, these additional VMs 1609 can be deactivated.

[0072] Data center 1600 can provide guaranteed availability, disaster recovery and backup services. For example, a data center can designate a VM 1609 on a server 16011 as the primary location for a tenant's application, and can activate a second VM 1609 on the same or different server as a standby or backup in case the first VM or server 16011 fails. Database manager 1602 automatically moves incoming user requests from the primary VM to the backup VM without tenant intervention. Although data center 1600 is illustrated as a single location, it should be understood that servers 1601 can be distributed to multiple locations around the world to provide additional redundancy and disaster recovery capabilities. In addition, data center 1600 can be a local, private system that provides services to a single enterprise user, or it can be a publicly accessible distributed system that provides services to multiple, unrelated customers and tenants, or it can be a combination of the two.

[0073] Domain Name System (DNS) server 1614 resolves domains and host names to IP addresses for all roles, applications, and services in data center 1600. DNS log 1615 maintains a record of which domain names have been resolved by roles. It will be understood that DNS is used as an example herein, and other name resolution services and domain name record services can be used to identify dependencies. For example, in other embodiments, IP or packet sniffing, code detection, or code tracking.

[0074] Datacenter health monitoring 1616 monitors the health of the physical systems, software, and environment in datacenter 1600. Health monitoring 1616 provides feedback to the datacenter manager when problems are detected with servers, blades, processors, or applications in datacenter 1600 or when network bandwidth or communication issues arise.

[0075] Access control services 1617 determine whether a user is allowed to access specific connections and services on cloud services 1600. Directory and identity management services 1618 authenticate user credentials for tenants on data center 1600.

[0076] Fig.17 17 is a simplified block diagram of an illustrative computer system 1700, such as a PC, client machine, or server, on which the present automated configuration conflict resolution and lightweight recovery can be implemented. The computer system 1700 includes a processor 1705, a system memory 1711, and a system bus 1714 that couples various system components including the system memory 1711 to the processor 1705. The system bus 1714 can be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, or a local bus using any of a variety of bus architectures. The system memory 1711 includes a read-only memory (ROM) 1717 and a random access memory (RAM) 1721. A basic input / output system (BIOS) 1725 is stored in ROM 1717 and contains basic routines that help transfer information between elements within the computer system 1700, such as during startup. The computer system 1700 may also include a hard disk drive 1728 for reading and writing to an internally set hard disk (not shown), a disk drive 1730 for reading or writing to a removable disk 1733 (e.g., a floppy disk), and an optical drive 1738 for reading or writing to a removable optical disk 1743 (such as a CD (compact disk), a DVD (digital versatile disk) or other optical media). The hard disk drive 1728, the disk drive 1730, and the optical drive 1738 are connected to the system bus 1714 via a hard disk drive interface 1746, a disk drive interface 1749, and an optical drive interface 1752, respectively. The drives and their associated computer-readable storage media provide non-volatile storage of computer-readable instructions, data structures, program modules, and other data for the computer system 1700. Although the illustrative example includes a hard disk, a removable disk 1733, and a removable optical disk 1743, other types of computer-readable storage media that can store computer-accessible data, such as magnetic tape cartridges, flash memory cards, digital video disks, data tapes, random access memory (RAM), read-only memory (ROM), etc., may also be used in some applications of the present automated configuration conflict resolution and lightweight recovery. In addition, as used herein, the term computer-readable storage medium includes one or more instances of a type of medium (e.g., one or more disks, one or more CDs, etc.). For the purposes of this specification and claims, the phrase "computer-readable storage medium" and its variations are intended to cover non-transitory embodiments and do not include waves, signals, and / or other transient and / or intangible communication media.

[0077] A number of program modules may be stored on a hard disk, disk 1733, optical disk 1743, ROM 1717, or RAM 1721, including an operating system 1755, one or more application programs 1757, other program modules 1760, and program data 1763. A user may enter commands and information into the computer system 1700 through input devices such as a keyboard 1766 and a pointing device 1768 such as a mouse. Other input devices (not shown) may include a microphone, a joystick, a game pad, a satellite dish, a scanner, a trackball, a touch pad, a touch screen, a touch-sensitive device, a voice command module or device, a user motion or user gesture capture device, and the like. These and other input devices are typically connected to the processor 1705 through a serial port interface 1771 coupled to the system bus 1714, but may be connected through other interfaces, such as a parallel port, a game port, or a universal serial bus (USB). A monitor 1773 or other type of display device is also connected to the system bus 1714 via an interface, such as a video adapter 1775. In addition to the monitor 1773, personal computers typically include other peripheral output devices (not shown), such as speakers and printers. Fig.17 The illustrative example shown in FIG. 1 also includes a host adapter 1778 , a small computer system interface (SCSI) bus 1783 , and an external storage device 1776 connected to the SCSI bus 1783 .

[0078] The computer system 1700 is operable in a networked environment using logical connections to one or more remote computers, such as remote computer 1788. Remote computer 1788 may be selected as another personal computer, a server, a router, a network PC, a peer device, or other common network node, and typically includes many or all of the above elements relative to computer system 1700, although in Fig.17 Only a single representative remote memory / storage device 1790 is shown. Fig.17 The logical connections depicted in 1790 include a local area network (LAN) 1793 and a wide area network (WAN) 1795. Such networking environments are commonly deployed, for example, in offices, enterprise-wide computer networks, intranets, and the Internet.

[0079] When used in a LAN networking environment, the computer system 1700 is connected to the local area network 1793 through a network interface or adapter 1796. When used in a WAN networking environment, the computer system 1700 typically includes a broadband modem 1798, a network gateway, or other components for establishing communications over a wide area network 1795 (such as the Internet). The broadband modem 1798 can be internal or external and is connected to the system bus 1714 via a serial port interface 1771. In a networking environment, program modules related to the computer system 1700, or portions thereof, may be stored in the remote memory storage device 1790. Note that Fig.17 The network connections shown are illustrative, and other means of establishing communications links between the computers may be used depending on the specific requirements of the application of the present automated configuration conflict resolution and lightweight recovery.

[0080] Various exemplary embodiments of the present automated configuration conflict resolution and lightweight recovery are now presented by way of illustration, and not as an exhaustive list of all embodiments. Examples include a computing device configured as a configuration verification and testing system, comprising: one or more processors; an interface arranged to interoperate with at least one virtual machine (VM); and at least one non-transitory computer-readable memory having computer-executable instructions stored thereon, which, when executed by the one or more processors, cause the computing device to: receive a set of input configurations loadable onto a VM operating in an original state, and define a corresponding updated operating state for the VM when the input configuration set is loaded, wherein each input configuration includes a plurality of configuration options; perform a difference function to identify differences between the input configurations; store the identified differences in a memory; implement conflict resolution between the input configurations by performing at least one of the following: eliminating overlapping configuration options, merging options in the input configurations into one or more updated configurations; loading the updated configuration into the VM to cause the VM to enter an updated operating state; and providing the identified differences from the memory to the VM so that the updated operating state can be rolled back to the original state.

[0081] In another example, the executed instructions also cause the computing device to verify the input configuration for correctness. In another example, the verification includes sending a call to the VM for sending or receiving network traffic to test the correctness of the updated configuration. In another example, the executed instructions also cause the computing device to receive input from one of the internal or external systems and utilize the input to perform one or more of the verification or conflict resolution. In another example, the input includes one of a timestamp, a priority, or a specification. In another instance, the updated configuration is determined by using a dynamic matching order of atomic configurations, and the atomic configurations are represented on a relationship diagram. In another example, the computing device also includes a user interface, which is adapted to one of the following: enabling manual intervention, triggering alarms, and providing notifications in the operation of the configuration verification and testing system.

[0082] Further examples include a method for managing configurations for a virtual machine (VM), comprising: receiving one or more input parameters that can be applied to a configuration for the VM; processing a collection of configurations that can be loaded onto the VM, wherein each input configuration in the collection operates to place the VM in a unique corresponding state; identifying a set of changes between an original configuration and a new configuration in the collection; validating the new configuration based on the received one or more input parameters; and in response to successful validation, loading only the identified changes into the VM to update the VM from an original state to an updated state.

[0083] In another example, the method also includes rolling back the identified changes in the VM to restore the VM from the updated state to the original state. In another example, the VM supports multiple different configurations and further includes performing conflict resolution for different configurations. In another example, conflict resolution is implemented in a series of automated actions performed by one of the following: a configuration verification module, a traffic verification module, a load and recovery module, a merge module, or an elimination module, wherein each of the configuration verification module, the traffic verification module, the load and recovery module, the merge module, or the elimination module is instantiated in a verification and test system operable on a computing device. In another example, the configuration is represented by a graph, the edges in the graph indicate dependencies and the nodes indicate configuration options. In another example, the configuration is verified by sending traffic to a device under test (DUT). In another example, the method is performed in a test suite environment.

[0084] Yet another example includes one or more non-transitory computer-readable memory devices storing computer-executable instructions that, when executed by one or more processors in a computing device, cause the computing device to: implement a test environment interoperable with a virtual machine (VM) cluster; load a base configuration from the test environment into the VM cluster, wherein the base configuration determines a base configuration state for the VM cluster, and wherein the base configuration state is stored in a first memory; load a set of test configuration options in a changed configuration from the test environment into the VM cluster to cause a change in the base configuration state of the VM cluster, wherein the changed configuration state for the VM cluster is stored in a second memory; obtain the base configuration state and the changed configuration state from the respective first and second memories; identify changes between the base configuration state and the changed configuration state; and send the changes from the test environment to the VM cluster so that the changes can be rolled back at the VM cluster to implement lightweight recovery at the VM cluster.

[0085] In another example, the instructions further cause the computing device to perform conflict resolution between the base configuration and the changed configuration. In another example, the instructions further cause the computing device to load a second set of test configuration options in the second changed configuration from the test environment into the VM cluster. In another example, the instructions further cause the computing device to obtain a base configuration state and a second changed configuration state from the corresponding first memory and second memory, identify changes between the base configuration state and the second configuration state, and send the changes to the VM cluster. In another example, the instructions further cause the computing device to iterate the following steps: load test configuration options for additional changed configurations, identify changes between the base configuration state and the additional changed configuration state, and send the changes to the VM cluster. In another example, lightweight recovery is achieved without restarting one or more VMs in the VM cluster.

[0086] Although the technical solution has been described in specific language of structural features and / or method actions, it is understood that the technical solution defined in the appended claims is not necessarily limited to the above specific features or actions. On the contrary, the above specific features and actions are disclosed as example forms of implementing the claims.

Claims

1. A computing device configured as a configuration verification and testing system, comprising: one or more processors; an interface arranged for interoperation with at least one virtual machine (VM); as well as at least one computer-readable memory having computer-executable instructions stored thereon that, when executed by the one or more processors, cause the computing device to: receiving a set of input configurations capable of being loaded onto the VM operating in a pristine state and defining a corresponding updated operating state for the VM when the set of input configurations is loaded, wherein each input configuration comprises a plurality of configuration options; performing a difference function to identify differences between input configurations; storing the identified differences in the memory; Conflict resolution between the input configurations is achieved by performing at least one of: eliminating overlapping configuration options, or merging options in the input configurations into one or more updated configurations; loading the updated configuration into the VM to bring the VM into an updated operational state; as well as The identified differences are provided from the memory to the VM to enable the updated operating state to be rolled back to the original state. 2 . The computing device of claim 1 , wherein the instructions executed further cause the computing device to validate the input configuration for correctness.

3. The computing device of claim 2, wherein the verifying comprises: A call to send or receive network traffic is sent to the VM to test the correctness of the updated configuration. 4 . The computing device of claim 2 , wherein the instructions executed further cause the computing device to receive input from one of an internal system or an external system and utilize the input for performing one or more of validation or conflict resolution. The computing device of claim 4 , wherein the input comprises one of a timestamp, a priority, or a specification. 6 . The computing device of claim 1 , wherein the updated configuration is determined by using a dynamic matching ordering of atomic configurations, the atomic configurations being represented on a relationship graph.

7. The computing device of claim 1, further comprising a user interface adapted to one of: enable manual intervention, raise an alarm, provide a notification in the operation of the configuration verification and testing system.

8. A method for managing configuration for a virtual machine (VM), comprising: receiving one or more input parameters, the one or more input parameters being applicable to configuration for the VM; processing a set of configurations that can be loaded into the VM, wherein each input configuration in the set operates to place the VM into a unique corresponding state; a set identifying changes between an original configuration and a new configuration in the set; validating the new configuration based on the received one or more input parameters; as well as In response to successful verification, only the identified changes are loaded to the VM to update the VM from an original state to an updated state. 9 . The method of claim 8 , further comprising rolling back the identified changes at the VM to restore the VM from the updated state back to the original state.

10. The method of claim 8, wherein the VM supports a plurality of different configurations, and the method further comprises performing conflict resolution for the different configurations.

11. The method of claim 10, wherein the conflict resolution is implemented as a series of automated actions performed by one of: a configuration verification module, a traffic verification module, a load and restore module, a merge module, or an elimination module, each of which is instantiated in a verification and testing system operable on a computing device.

12. The method of claim 8, wherein the configuration is represented by a graph, wherein edges in the graph indicate dependencies and nodes indicate configuration options.

13. The method of claim 8, wherein the configuration is verified by sending traffic to a device under test (DUT).

14. The method according to claim 13 is performed in a test suite environment.