Reducing downtime due to incompatibility problems of upgrading firmware and software
By identifying the update requirements of the virtualized computing system, comparing with the benchmark system, predicting update time and risks, the compatibility issues before and after updates in the virtualized environment are solved, and an efficient and accurate upgrade process is achieved, reducing downtime and errors are caused. .
Patent Information
- Application Number
- CN202380029052.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-22
- Filing Date
- 2023-02-07
- Publication Date
- 2024-11-08
AI Technical Summary
In virtualized computing systems, when firmware and operating systems are updated, it is difficult to ensure compatibility before and after the update, resulting in downtime that may be required, and update time is difficult to accurately plan, affecting the stability and efficiency of the system.
By identifying the updates required by the virtualized computing system, comparing similarities with the benchmark system, estimating update times, and identifying errors during the update process, pre-applying configuration changes to ensure compatibility before and after updates and reducing errors, leveraging machine learning and artificial intelligence algorithms predict upgrade time and risks.
It ensures compatibility before and after updates in a virtualized environment, reduces downtime, improves update accuracy and efficiency, and reduces upgrade risks.
Smart Images

Figure CN118922812A_ABST
Abstract
Description
Background Art
[0001] The present invention relates generally to the field of virtualized computing systems, and more particularly to maintaining and operating virtualized computing systems in order to properly execute enterprise solutions.
[0002] The Wikipedia entry for "Hypervisor" (as of February 13, 2022) states the following: "A hypervisor (or virtual machine monitor (VMM) virtualizer) is similar to an emulator; it is computer software, firmware, or hardware that creates and runs virtual machines. The computer on which the hypervisor runs one or more virtual machines is called a host, and each virtual machine is called a client. The hypervisor provides a virtual operating platform to guest operating systems and manages the execution of the guest operating systems. Multiple instances of various operating systems can share virtualized hardware resources... This is in contrast to operating system-level virtualization, in which all instances (often called containers) must share a single kernel, whereas guest operating systems can be different in user space... with the same kernel." Summary of the invention
[0003] According to one aspect of the invention, there is a method, computer program product, and / or system for performing the following operations (not necessarily in the following order): (i) identifying a first plurality of updates required for a first virtualized computing system; (ii) comparing the first virtualized computing system to a set of benchmark virtualized computing systems to determine a set of similar virtualized computing systems that have undergone updates comparable to the first plurality of updates required for the first virtualized computing system; (iii) in response to the comparison, determining an estimated time to complete the first plurality of updates based at least in part on a set of performance characteristics of the first virtualized computing system; (iv) identifying a first plurality of errors that occurred during the updating of the set of similar virtualized computing systems; and (v) in response to the identification of the first plurality of errors, pre-applying configuration changes to the first virtualized computing system. BRIEF DESCRIPTION OF THE DRAWINGS
[0004] Figure 1 is a block diagram of a first embodiment of a system according to the present invention;
[0005] Figure 2 is a flow chart illustrating a first embodiment method at least partially performed by a first embodiment system;
[0006] Figure 3 is a block diagram illustrating the machine logic (e.g., software) portion of the first embodiment system;
[0007] Figure 4 is a block diagram of a first embodiment of a system according to the present invention;
[0008] Figure 5 is a flow chart showing a first embodiment of a method according to the present invention;
[0009] Figure 6 is a flow chart showing a second embodiment of the method according to the present invention;
[0010] Figure 7 is a flow chart showing a third embodiment of the method according to the present invention;
[0011] Figure 8 is a flow chart showing a fourth embodiment of a method according to the present invention; and
[0012] Fig. 9 is a block diagram illustrating a second embodiment of a system according to the present invention. DETAILED DESCRIPTION
[0013] This detailed description section is divided into the following subsections: (i) Hardware and Software Environment; (ii) Example Embodiments; (iii) Further Discussions and / or Embodiments; and (iv) Definitions.
[0014] I. Hardware and Software Environment
[0015] The present invention may be a system, method and / or computer program product. The computer program product may include a computer-readable storage medium (or multiple media) having computer-readable program instructions thereon, the computer-readable program instructions being used to cause a processor to perform various aspects of the present invention.
[0016] A computer-readable storage medium may be a tangible device capable of retaining and storing instructions used by an instruction execution device. A computer-readable storage medium may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of computer-readable storage media includes the following: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device such as a punch card or a raised structure in a groove on which instructions are recorded, and any suitable combination of the foregoing. As used herein, a computer-readable storage medium should not be interpreted as a temporary signal itself, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagated by a waveguide or other transmission medium (e.g., a light pulse by an optical fiber cable), or an electrical signal transmitted by a wire.
[0017] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to a corresponding computing / processing device, or downloaded to an external computer or external storage device via a network (e.g., the Internet, a local area network, a wide area network, and / or a wireless network). The network can include copper transmission cables, optical transmission fibers, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions to be stored in a computer-readable storage medium in the corresponding computing / processing device.
[0018] The computer-readable program instructions for performing the operation of the present invention can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages (such as Smalltalk, C++, etc.) and conventional procedural programming languages (such as "C" programming language or similar programming languages). The computer-readable program instructions can be executed completely on the user's computer, partially on the user's computer, executed as an independent software package, partially on the user's computer and partially on a remote computer, or completely on a remote computer or server. In the latter case, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (for example, using an Internet service provider through the Internet). In some embodiments, in order to perform various aspects of the present invention, the electronic circuit including, for example, a programmable logic circuit, a field programmable gate array (FPGA) or a programmable logic array (PLA) can execute the computer-readable program instructions by utilizing the state information of the computer-readable program instructions to personalize the electronic circuit.
[0019] Various aspects of the present invention are described herein with reference to the flow chart and / or block diagram of the method, device (system) and computer program product according to embodiments of the present invention. It will be understood that each frame of the flow chart and / or block diagram and the combination of frames in the flow chart and / or block diagram can be implemented by computer-readable program instructions.
[0020] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create a device for implementing the functions / actions specified in one or more boxes of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, which can guide the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable storage medium having the instructions stored therein includes an article of manufacture, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes of the flowchart and / or block diagram.
[0021] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other device to produce a computer-implemented process, so that the instructions executed on the computer, other programmable apparatus, or other device implement the functions / actions specified in one or more boxes of the flowchart and / or block diagram.
[0022] Flowchart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention.In this regard, each frame in flow chart or block diagram can represent the module, segment or part of instruction, and it comprises one or more executable instructions for realizing the logical function of appointment.In some alternative embodiments, the function mentioned in the frame may not occur in the order mentioned in the figure.For example, two frames shown continuously can actually be performed substantially at the same time, or these frames can sometimes be performed in reverse order, depending on the function involved.It will also be noted that the combination of the frame in each frame of block diagram and / or flow chart illustration and block diagram and / or flow chart illustration can be realized by the dedicated hardware-based system of performing a specified function or action or performing a combination of special hardware and computer instruction.
[0023] Embodiments of possible hardware and software environments of the software and / or method according to the present invention will now be described in detail with reference to the accompanying drawings. Figure 1 1 is a functional block diagram showing various parts of the networked computer system 100, including: server subsystem 102; client subsystems 104, 106, 108, 110, 112; communication network 114; server computer 200; communication unit 202; processor group 204; input / output (I / O) interface group 206; memory device 208; persistent storage 210; display device 212; external device set 214; random access memory (RAM) device 230; cache memory device 232; and program 300.
[0024] Subsystem 102 is representative in many respects of various computer subsystems in the present invention. Accordingly, several portions of subsystem 102 will now be discussed in the following paragraphs.
[0025] Subsystem 102 may be a laptop computer, a tablet computer, a netbook computer, a personal computer (PC), a desktop computer, a personal digital assistant (PDA), a smart phone, or any programmable electronic device capable of communicating with a client subsystem via network 114. Program 300 is a collection of machine-readable instructions and / or data for creating, managing, and controlling certain software functions, which are discussed in detail below in the Exemplary Embodiments subsection of this Detailed Description section.
[0026] Subsystem 102 can communicate with other computer subsystems via network 114. Network 114 can be, for example, a local area network (LAN), a wide area network (WAN) such as the Internet, or a combination of both, and can include wired, wireless, or fiber optic connections. In general, network 114 can be any combination of connections and protocols that support communication between server and client subsystems.
[0027] Subsystem 102 is shown as a block diagram with many double arrows. These double arrows (without separate reference numerals) represent a communication structure that provides communication between the various components of subsystem 102. The communication structure can be implemented with any architecture designed to transfer data and / or control information between processors (such as microprocessors, communication and network processors, etc.), system memory, peripheral devices, and any other hardware components within the system. For example, the communication structure can be implemented at least in part with one or more buses.
[0028] Memory 208 and persistent storage 210 are computer-readable storage media. In general, memory 208 may include any suitable volatile or non-volatile computer-readable storage media. It should also be noted that now and / or in the near future: (i) (one or more) external devices 214 can provide some or all of the memory for subsystem 102; and / or (ii) devices external to subsystem 102 can provide memory for subsystem 102.
[0029] Program 300 is stored in persistent storage 210 for access and / or execution by one or more corresponding computer processors 204, typically through one or more memories of memory 208. Persistent storage 210: (i) is at least more permanent than a signal in transit; (ii) stores the program (including its soft logic and / or data) on a tangible medium (such as a magnetic or optical domain); and (iii) is much less permanent than permanent storage. Alternatively, data storage may be more permanent and / or permanent than the type of storage provided by persistent storage 210.
[0030] Program 300 may include machine-readable and executable instructions and / or substantive data (i.e., the type of data stored in a database). In this particular embodiment, persistent storage 210 includes a magnetic hard drive. To name some possible variations, persistent storage 210 may include a solid-state hard drive, a semiconductor memory device, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), flash memory, or any other computer-readable storage medium capable of storing program instructions or digital information.
[0031] The media used by persistent storage 210 may also be removable. For example, a removable hard drive may be used for persistent storage 210. Other examples include optical and magnetic disks, thumb drives, and smart cards that are inserted into a drive for transfer to another computer-readable storage medium that is also part of persistent storage 210.
[0032] In these examples, communications unit 202 provides communications with other data processing systems or devices external to subsystem 102. In these examples, communications unit 202 includes one or more network interface cards. Communications unit 202 can provide communications using one or both of physical and wireless communications links. Any software modules discussed herein can be downloaded to a persistent storage device such as persistent storage 210 via a communications unit such as communications unit 202.
[0033] The I / O interface group 206 allows data to be input and output from other devices that can be locally connected in a manner that can communicate data with the server computer 200. For example, the I / O interface group 206 provides a connection to an external device set 214. The external device set 214 typically includes devices such as a keyboard, a keypad, a touch screen, and / or some other suitable input device. The external device set 214 can also include a portable computer readable storage medium, such as, for example, a thumb drive, a portable optical disk or disk, and a memory card. Software and data (e.g., program 300) for implementing embodiments of the present invention can be stored on such a portable computer readable storage medium. In these embodiments, the relevant software may (or may not) be loaded into the persistent storage 210 in whole or in part via the I / O interface group 206. The I / O interface group 206 is also connected to the display device 212 in data communication.
[0034] Display device 212 provides a mechanism for displaying data to a user and may be, for example, a computer monitor or a smartphone display screen.
[0035] The programs described herein are identified based on the applications implemented in the specific embodiments of the present invention. However, it is to be understood that any specific program terminology herein is used only for convenience, and thus the present invention should not be limited to use only in any specific application identified and / or implied by such terminology.
[0036] The description of various embodiments of the present invention is given for the purpose of illustration, but it is not intended to be exhaustive or limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope of the described embodiments. The terms used herein are selected to best explain the principles of the embodiments, practical applications, or technical improvements existing in the market, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.
[0037] II. Example Embodiments
[0038] Figure 2 A flow chart 250 describing a method according to the present invention is shown. Figure 3 A procedure 300 is shown for performing at least some of the method operations of flowchart 250. In the course of the following paragraphs, reference will now be made extensively to Figure 2 (for method action blocks) and Figure 3 (for software blocks) to discuss the method and the associated software.
[0039] Processing begins at operation S255 where an update identification module ("block") 305 identifies a set of updates required for the virtualized computing system.
[0040] Processing proceeds to operation S260, where the compare virtualized computing systems block 310 compares the virtualized computing system (discussed above in conjunction with operation S255) to a set of previously utilized and / or previously identified virtualized computing systems (sometimes referred to herein as a set of baseline virtualized computing systems). In some embodiments of the invention, the comparison is performed to determine a set of virtualized computing systems that have undergone updates similar to the updates identified as needing to be performed by the virtualized computing system (discussed above in conjunction with operation S255).
[0041] Processing proceeds to operation S265, where the update time estimation block 315 determines an estimated amount of time to complete the identified update. In some embodiments of the present invention, the update time estimation block 315 records the first estimated amount of time so that it can be used as a baseline time for future updates. For example, if the second virtualized computing system requires a future update that is substantially similar to the original update performed on the first virtualized computing system, the baseline amount of time can be used to determine whether the update performed on the second virtualized computing system is performed in an efficient manner.
[0042] Processing proceeds to operation S270, where the error identification block 320 identifies a set of errors that occurred during the update process of a set of benchmark virtualized computing systems. In some embodiments of the present invention, when the number of errors that occurred during the update process is recorded, the identification block 320 is additionally used to determine whether the number of errors is below an error threshold or exceeds an error threshold. In some embodiments, the error threshold is used to determine the accuracy of the update process. That is, if more errors are identified, future updates with error counts greater than the original error count may be considered less accurate than future updates with error counts less than the original error count.
[0043] The process eventually proceeds to operation S275 , where the configure virtualized computing system block 325 pre-applies configuration changes to the virtualized computing system (discussed above in conjunction with operations S255 and S260 ).
[0044] III. Further Discussion and / or Examples
[0045] Embodiments of the present invention generally relate to updating system firmware and operating systems in a virtualized environment of a data center. Servers / systems are virtualized using a hypervisor and are assisted by a special type of virtual machine called a virtual IO server (VIOS). A hypervisor is a computer software or firmware that allows the creation of multiple virtual machines (VMs) running a given operating system and allows the sharing of resources allocated to the server between VMs. In a virtualized setting, the sharing (or virtualization) of I / O resources is delegated to the VIOS. The VIOS operates like any other VM running on a server, but plays the role of a hosted VM and is responsible for sharing physical I / O resources, i.e., storage and network adapters, as well as other client VMs on the system. This is achieved by the VIOS owning the I / O resources and connecting them to virtual (or software equivalent) I / O resources. The virtual machine then uses the virtual I / O resources to perform I / O operations. Against the above background, we will use the following terms to further explain embodiments of the present invention.
[0046] When performing firmware updates, VIOS updates, or OS updates in a virtualized environment as described above, there is often a possibility that the newer update or level or feature is incompatible with the existing configuration of the virtualized environment. In such a scenario, there may be cross-stack incompatibilities after the update, and downtime may be required to change settings and make configuration changes. In addition, the time it takes to update varies depending on: (i) the number of subsystems in the stack that need to be updated; (ii) the total time it takes to calculate all of these updates; and (iii) planning maintenance windows for the exact total time required or longer becomes a problem.
[0047] By adding the VIOS, the complexity of compatibility across the stack is further complicated, and any changes to the VIOS may result in incompatibilities and may affect workloads running on the operating system in such a virtualized environment. Embodiments of the present invention provide a mechanism for performing stack compatibility checks before the actual update and ensuring that the configuration of the virtualized environment remains compatible after the update as well.
[0048] Embodiments of the present invention provide an algorithm that parses README files and certain specific command outputs associated with corresponding components or subsystems and checks for prerequisites. The algorithm also checks for compatibility between different levels of these subsystems. While a management console may be able to perform this check for firmware updates, OS updates and VIOS updates, if initiated via a management console, will require an additional mechanism for the OS / VIOS to talk to the management console via a hypervisor to perform a validation operation before proceeding with the update or upgrade.
[0049] The compatibility stack based on the README / command output should be considered a baseline level, but will be improved by adopting specific known configurations. These systems can currently upload existing configurations as part of call home updates. These updates are configured to report the current configuration at regular intervals, and in some embodiments, these updates are completed on a weekly basis.
[0050] The solution includes recording the number of systems reporting a particular configuration. Additionally, when a system has a problem, the configuration of the system reporting the problem can be recorded and stored. When a system with a certain configuration has a problem, a negative value should be noted for that configuration when calculating the best configuration to recommend. Information on the time taken to update or upgrade needs to be sent with the call home data, which will be used to improve the baseline data for the time taken to update / upgrade each subsystem. This baseline data will further be used to improve the accuracy of the update time calculation.
[0051] In some embodiments, the management console will extract the necessary information for the existing configuration and also the necessary information for the newer version and perform the appropriate validations. These validations and results will be input into the learning model and data will also be collected after updates for any failures to feed back into the model so that the validations can be continuously improved. When suggesting a configuration, the management console can base the selection of the configuration on the number of systems that report a particular configuration that also matches the extracted valid configuration.
[0052] In some embodiments, data collected as part of call attribution or telemetry will be enhanced to send information about configuration levels, problems seen in the environment, SRCs indicating problems, time taken to update and / or upgrade, and the like.
[0053] The components involved can be broadly divided into the following categories:
[0054] (1) Management console:
[0055] For management console updates, in addition to checking the prerequisites at the management console level, you can also check firmware, VIOS, OS, and any management console in the HA configuration or pool model.
[0056] (2) Firmware / Hypervisor:
[0057] The management console performs a check of the configuration's compatibility with the newer level.
[0058] (3) Virtual IO Server:
[0059] When a VIOS update is initiated, the VIOS may initiate communication to a management console via the hypervisor to check for compatibility.
[0060] (4) Operating system:
[0061] When an OS update or upgrade is initiated, the OS will check compatibility with the management console through the hypervisor. In some embodiments, the management console will check the configuration of the different subsystems in the system and stack, and use the readme / command output information and the learning obtained from the call home information to determine the best configuration before performing the update.
[0062] Embodiments of the present invention provide a method for estimating upgrade time and reducing errors when updating a computing system. The operations of the method include, but are not necessarily limited to, the following (and not necessarily in the following order): (i) identifying updates required for a system; (ii) comparing the system to be updated with other systems to determine similar systems that have undergone similar updates; (iii) planning the time to complete the update based on the performance characteristics of the system to be updated, the performance characteristics of similar systems that have been updated, and the time it takes to update similar systems; (iv) identifying errors that occur when updating similar systems and corresponding error solutions; and (v) applying configuration changes or other error solutions to the system to be updated in advance.
[0063] Embodiments of the present invention provide a cognitive upgrade process that estimates and adjusts upgrade time and upgrade risk. In some embodiments, the upgrade process includes N updates, each of which may take a certain amount of time and is associated with a certain amount of failure risk that causes meaningful interruption and downtime.
[0064] To make appropriate estimates, embodiments of the present invention utilize a collection of algorithms using machine learning and artificial intelligence (AI) techniques.
[0065] The key elements of the algorithm include the following operations (not necessarily in the following order):
[0066] (1) Determine the complete set of software and firmware packages involved in the stack that are candidates for upgrade;
[0067] (2) For the stack being upgraded, consider the complete set to determine the “gap” between the current state and the desired state;
[0068] (3) For each gap, identify a peer group that has similar characteristics to the attention stack except for the gap that is filled. A nearest neighbor algorithm will be used to identify the peer group at each step. Similarity is based on the complete set of packets.
[0069] For example, if the "gap" being addressed is the upgrade of the TCP component from version 1 to version 2, the peer group consists of all other known stacks where the rest of the SW and FW packages are identical or very close to the stack being upgraded, except that the TCP component has been upgraded to version 2.
[0070] (4) For the peer group, collect the time it takes to upgrade TCP to version 2;
[0071] (5) collecting factors that determine performance characteristics, such as computing performance, storage read / write performance to be used as input features for machine learning algorithms;
[0072] (6) A supervised machine learning approach is used to construct an ensemble of ML algorithms to predict the time and interval that TCP is expected to take to upgrade from version 1 to version 2 (e.g., it will take 30 minutes + / - 2 minutes). The features used for supervised learning consist of the performance characteristics of each stack in the peer group and the upgrade time of each stack for each interval;
[0073] (7) Repeat the above steps for each of the gaps, and generate an upgrade time prediction for each of the steps;
[0074] (8) Use a similar approach, but consider all gaps at once and predict the total time. In this case, the peer group can successfully undergo a total stack upgrade;
[0075] (9) creating an overall forecast based on the individual gaps; and
[0076] (10) Utilize a collection of ML algorithms to predict the upgrade time of each step and the time of the entire upgrade process.
[0077] Some embodiments of the present invention determine the probability of success for each step with respect to estimating upgrade time and upgrade risk (described above).
[0078] Using methods similar to the algorithms described above, some embodiments of the present invention determine the probability of success for estimating upgrade time and upgrade risk and steps that can improve that probability. To do so, some embodiments utilize historical data available to the peer group in the form of system logs and customer support ticket information that is available to the relevant proprietary entity. In some embodiments, text mining methods are used to determine the cause of the failure and recommend mitigation measures. In addition, some embodiments of the present invention utilize collaborative filtering algorithms to predict the probability of success.
[0079] The entire upgrade process includes the following operations (not necessarily in the following order): (i) providing an expected summary, including total estimated time and possible suggestions for improving time (e.g., temporarily purchasing more computing resources via Capacity on Demand (COD), risk assessment and risk reduction suggestions, and a detailed breakdown of each step including upgrade time and risk; (ii) performing each operation based on user confirmation; and (iii) adjusting the upgrade time forecast for each operation and the entire process after each operation is completed.
[0080] To reduce downtime, some embodiments of the present invention use a cognitive upgrade assistant. The cognitive upgrade assistant includes: (i) a chatbot that guides an administrator through the upgrade process; and (ii) input to the chatbot. The input to the chatbot includes: (a) a README file created using a template for inputting dependencies; (b) command line output (for a chatbot running on a server); (c) historical service data for a stack; and (d) service data for other clients that have similar configurations and have performed upgrades.
[0081] In some embodiments of the invention, the cognitive upgrade process includes using the cognitive upgrade assistant to perform the following operations (not necessarily in the following order): (i) collect necessary contextual data stored locally on the stack; (ii) contextually integrate relevant external information from the "peer group" and information for the stack; (iii) display any missing prerequisites and risks; (iv) display estimated time and confidence level; and (v) use the information that has been collected and through interaction with the administrator to guide the administrator through the upgrade process, where each step is confirmed. In some embodiments, the administrator is the user who is prompted for confirmation by displaying what the cognitive upgrade assistant is doing and relevant supporting evidence for the actions the upgrade assistant is taking.
[0082] Figure 4 The virtualization environment diagram 400 provides a graphical representation of a virtualization environment used by an embodiment of the present invention. The diagram 400 includes the following components: management console 402, system / server 404, hypervisor 406, virtual machine 1 (VM1) 408, virtual machine 2 (VM2) 410, and VIOS 412.
[0083] Figure 5 Flowchart 500 shows a first graphical representation of an upgrade model for stack-level recommendations. Diagram 500 includes inputs such as: a readme file (502) with a specific template format and version, historical service data (504) for a given stack, and service data (506) from different clients with similar virtualization environments. These inputs are fed to an upgrade assistant module 508, which then outputs stack-level recommendations 510.
[0084] Figure 6 Flowchart 600 provides a graphical representation of an upgrade assistant model for stack-level recommendations. Diagram 600 includes input 602, upgrade assistant 604, and stack-level recommendations 608. With respect to input 602, there are two types of input: static input 608 and dynamic input 610. Static input (608) includes a readme file (612) having a specific template format and version and test results (614) including information indicating version compatibility. Dynamic input (610) includes: SRC, call attribution data, configuration information from instances and issues related to configuration (616), service data from different clients with similar virtualization environments (618), and historical service data (620) of the stack. Stack-level recommendations (606) include the level (or layer) to be updated (622), recommendations for N, N-1, N-2, etc. (624), time estimates for updates (626), the order of updates (628), the number of customers using the stack in the field (630), and the time period during which the level (or layer) is used in the environment.
[0085] Figure 7 Flowchart 700 provides a graphical representation of the upgrade and / or update process. This process includes a user initiating and updating or upgrading (702), which is sent to an upgrade assistant (704). The upgrade assistant initiates a communication request to the management console and collects necessary context information from the stack (706). This context information is then bound to relevant external information from a peer group designed to be used with the stack (708). Through this context information, recommendations and prerequisites for the upgrade / update are obtained (710). Next, an estimated time for the update or upgrade is provided (712). The estimated time for the update / upgrade guides the administrator through the update / upgrade process (714). Finally, the stack is continuously monitored for issues / SRCs and this data is sent back to the upgrade assistant (716).
[0086] Figure 8Flowchart 800 of FIG. 1 provides a graphical representation of alerts and notifications for the update / upgrade process. The user sets up a scheduler to check for problems in the current configuration and known issues in the level (or tier) to which the user wants to move (802). Information received from the scheduler is sent to the upgrade assistant (804). The upgrade assistant uses a machine learning model to continuously collect static and dynamic input (combined with the above Figure 6 The static and dynamic inputs discussed are similar or identical)(806).
[0087] In some embodiments, the alert scheduling module sends an alert: (i) if a known issue exists in the current configuration and information about how to fix or otherwise address the known issue (808); (ii) if a known issue exists in a planned update level (810); and / or (iii) when a fix is available for the known issue (either in the current configuration or in a planned update level) (812).
[0088] Fig. 9 The block diagram 900 provides a graphical representation of the power virtualization and management model. The block diagram 900 includes: a dynamic AI model 902, an upgrade assistant 904, an MC domain 906, a power server 908, a logical partition 910, a power management program 912, a management console 914, a storage controller 916, a SAN switch 918, an OS1 (operating system 1) 920, an OS2 (operating system 2) 922, an OS 3 (operating system 3) 924, a VIOS 926, a FSP 928, a PSU 930, a SAS 932, a FC adapter 934, a network adapter 936, an LFT adapter 938, a firmware platform 940, and a virtual L2 switch 942. In some embodiments of the present invention, the operating system used may include a proprietary operating system (e.g., OS1 920, OS2 922, and / or OS 3 924).
[0089] IV. Definitions
[0090] The present invention: should not be taken as an absolute indication that the subject matter described by the term "the present invention" is covered by the claims as filed, or by claims that may eventually issue subsequent to a patent application; while the term "the present invention" is used to help the reader gain a general sense for which the disclosure herein is believed to be potentially new, as indicated by the use of the term "the present invention", that understanding is tentative and provisional and is subject to change during the course of patent prosecution as relevant information develops and the claims are potentially amended.
[0091] Example: See above for the definition of "the present invention" Similar caveats apply to the term "example".
[0092] And / or: inclusive or; for example, A, B, and / or C means at least one of A or B or C is true and applicable.
[0093] Include / Contain / Include: Means “including but not necessarily limited to” unless expressly stated otherwise.
[0094] User / Subscriber: includes but is not necessarily limited to: (i) a single individual person; (ii) an artificial intelligence entity with sufficient intelligence to act as a user or subscriber; and / or (iii) a group of related users or subscribers.
[0095] Data Communications: Any type of data communications scheme now known or developed in the future, including wireless communications, wired communications, and communications routes having both wireless and wired portions; data communications are not necessarily limited to: (i) direct data communications; (ii) indirect data communications; and / or (iii) data communications in which the format, packetization state, medium, encryption state, and / or protocol remain constant throughout the data communications.
[0096] Receive / Provide / Send / Input / Output / Report: Unless expressly specified otherwise, these words should not be taken to imply: (i) any particular degree of directness regarding the relationship between their object and subject; and / or (ii) the absence of intervening components, actions and / or things between their object and subject.
[0097] No substantial human intervention: A process that occurs automatically (typically through the operation of machine logic, such as software) with little or no human input; some examples of "no substantial human intervention" include: (i) a computer performs complex processing, and due to a power outage in the grid, a human switches the computer to an alternate power source so that processing continues uninterrupted; (ii) a computer performs resource-intensive processing, and a human confirms that the resource-intensive processing should indeed be performed (in this case, the confirmation process considered in isolation is with substantial human intervention, but the resource-intensive processing does not include any substantial human intervention, although a simple yes-no style confirmation by a human is required); and (iii) using machine logic, a computer makes a weighted decision (e.g., a decision to ground all aircraft in anticipation of severe weather), but the computer must obtain a simple yes-no style confirmation from a human source before implementing the weighted decision.
[0098] Automatically: without any human intervention.
[0099] Module / Sub-module: Any collection of hardware, firmware, and / or software that works operatively to perform a function, regardless of whether the module is: (i) in a single local proximity; (ii) distributed over a wide area; (iii) in a single proximity within a larger software code segment; (iv) located within a single software code segment; (v) located in a single storage device, memory, or medium; (vi) mechanically connected; (vii) electrically connected; and / or (viii) connected in a data communication manner.
[0100] Computer: Any device with significant data processing and / or machine-readable instruction reading capabilities, including but not limited to: desktop computers, mainframe computers, laptop computers, field programmable gate array (FPGA) based devices, smart phones, personal digital assistants (PDAs), body mounted or embedded computers, embedded device type computers, and application specific integrated circuit (ASIC) based devices.
Claims
1. A computer implemented method (CIM), include: identifying a first plurality of updates required for a first virtualized computing system; comparing the first virtualized computing system to a set of benchmark virtualized computing systems to determine a set of similar virtualized computing systems that have undergone updates comparable to the first plurality of updates required by the first virtualized computing system; responsive to the comparing, determining an estimated time to complete the first plurality of updates based at least in part on a set of performance characteristics of the first virtualized computing system; identifying a first plurality of errors occurring during an update of the set of similar virtualized computing systems; as well as Responsive to the identification of the first plurality of errors, a configuration change is pre-applied to the first virtualized computing system.
2. The CIM according to claim 1, further comprising: include: Responsive to identifying the first plurality of errors occurring during the update of the group of similar virtualized computing systems, it is determined that the first plurality of errors does not exceed a first error threshold.
3. The CIM according to claim 1, in, The set of performance characteristics of the first virtualized computing system includes information indicative of computing performance of the first virtualized computing system.
4. The CIM according to claim 1, in, The set of performance characteristics of the first virtualized computing system includes information indicative of storage read and / or write performance data of the first virtualized computing system.
5. The CIM according to claim 1, further comprising: include: A first amount of time taken to pre-apply the configuration change to the first virtualized system is determined.
6. The CIM according to claim 5, further comprising: include: In response to the determination, the first amount of time taken to previously apply the configuration change is used to determine baseline update data for future applications of the configuration change to the first virtualized system.
7. A computer program product (CPP), include: a machine-readable storage device; as well as Computer code stored on the machine-readable storage device, wherein the computer code includes instructions and data for causing a processor group to perform operations including: identifying a first plurality of updates required for a first virtualized computing system; comparing the first virtualized computing system to a set of benchmark virtualized computing systems to determine a set of similar virtualized computing systems that have undergone updates comparable to the first plurality of updates required by the first virtualized computing system; responsive to the comparing, determining an estimated time to complete the first plurality of updates based at least in part on a set of performance characteristics of the first virtualized computing system; identifying a first plurality of errors that occurred during an update of the set of similar virtualized computing systems; and Responsive to the identification of the first plurality of errors, a configuration change is pre-applied to the first virtualized computing system.
8. The CPP according to claim 7, further comprising include: Responsive to identifying the first plurality of errors occurring during the update of the group of similar virtualized computing systems, it is determined that the first plurality of errors does not exceed a first error threshold.
9. The CPP according to claim 7, in, The set of performance characteristics of the first virtualized computing system includes information indicative of computing performance of the first virtualized computing system.
10. The CPP according to claim 7, in, The set of performance characteristics of the first virtualized computing system includes information indicative of storage read and / or write performance data of the first virtualized computing system.
11. The CPP according to claim 7, further comprising include: A first amount of time taken to pre-apply the configuration change to the first virtualized system is determined.
12. The CPP according to claim 11, further comprising include: In response to the determination, the first amount of time taken to previously apply the configuration change is used to determine baseline update data for future applications of the configuration change to the first virtualized system.
13. A computer system (CS), include: Processor Group; a machine-readable storage device; as well as Computer code stored on the machine-readable storage device, wherein the computer code includes instructions and data for causing the processor group to perform operations including: identifying a first plurality of updates required for a first virtualized computing system; comparing the first virtualized computing system to a set of benchmark virtualized computing systems to determine a set of similar virtualized computing systems that have undergone updates comparable to the first plurality of updates required by the first virtualized computing system; responsive to the comparing, determining an estimated time to complete the first plurality of updates based at least in part on a set of performance characteristics of the first virtualized computing system; identifying a first plurality of errors that occurred during an update of the set of similar virtualized computing systems; and Responsive to the identification of the first plurality of errors, a configuration change is pre-applied to the first virtualized computing system.
14. The CS according to claim 13, further comprising: include: Responsive to identifying the first plurality of errors occurring during the update of the group of similar virtualized computing systems, it is determined that the first plurality of errors does not exceed a first error threshold.
15. The CS according to claim 13, in, The set of performance characteristics of the first virtualized computing system includes information indicative of computing performance of the first virtualized computing system.
16. The CS according to claim 13, in, The set of performance characteristics of the first virtualized computing system includes information indicative of storage read and / or write performance data of the first virtualized computing system.
17. The CS according to claim 13, further comprising: include: A first amount of time taken to pre-apply the configuration change to the first virtualized system is determined.
18. The CS according to claim 17, further comprising: include: In response to the determination, the first amount of time taken to previously apply the configuration change is used to determine baseline update data for future applications of the configuration change to the first virtualized system.
