System and method of analyzing update readiness for distributed software systems

Patent metadata

Field	Value
Publication number	US-11907706-B2
Application number	US-202117320585-A
Country	US
Kind code	B2
Filing date	May 14, 2021
Priority date	May 14, 2021
Publication date	Feb 20, 2024
Grant date	Feb 20, 2024

Abstract

The disclosure provides for analyzing upgrade and migration readiness. Embodiments include receiving an indication to upgrade a software product and a selected upgrade path identifying a target-upgrade version. Embodiments include accessing an array of pre-upgrade procedures comprising code for identifying one or more conditions that must be met before the software product can be upgraded based on the accessed array being associated with the software product. Embodiments include executing one or more of the pre-upgrade procedures in advance of upgrading the software product. Embodiments include accessing one or more autonomous remediation scripts from the repository based on identification of one or more failed pre-upgrade procedures. Embodiments include executing the one or more autonomous remediation scripts to cure the one or more failed pre-upgrade procedures and initiating an upgrade of the software product based on identifying that the array of pre-upgrade procedures successfully completed execution.

First claim

We claim:

1. A method of updating a software component, comprising:
registering, with an update readiness system, a software product that is installed on a computing device by providing the update readiness system with a name of the software product and a version identifier of the software product; as a result of the registering, causing, by the update readiness system, an agent of the update readiness system to be installed on the computing device in association with the software product; receiving, by the update readiness system, an indication to upgrade the software product; receiving, by the update readiness system, a selected upgrade path for the software product, the selected upgrade path identifying a target for the software product; accessing, by the update readiness system, an array of pre-upgrade procedures from a repository based on the array being associated with the software product, the array of pre-upgrade procedures comprising code for identifying one or more conditions that must be met before the software product can be upgraded to the target; executing, by the update readiness system via the agent, one or more of the pre-upgrade procedures in advance of upgrading the software product to the target; accessing, by the update readiness system, one or more autonomous remediation scripts from the repository based on identification of one or more failed pre-upgrade procedures; executing, by the update readiness system via the agent, the one or more autonomous remediation scripts to cure the one or more failed pre-upgrade procedures; and initiating an upgrade of the software product to the target based on identifying, by the update readiness system, that the array of pre-upgrade procedures successfully completed execution.

2. The method of claim 1 , further comprising:
determining that the executed one or more autonomous remediation scripts do not cure all of the one or more failed pre-upgrade procedures; and initiating a semi-autonomous remediation procedure based on the determination that the executed one or more autonomous remediation scripts does not cure all of the one or more failed pre-upgrade procedures.

3. The method of claim 2 , wherein initiating the semi-autonomous remediation procedure comprises:
accessing one or more semi-autonomous remediation scripts from the repository; executing the one or more semi-autonomous remediation scripts; and determining whether the executed one or more semi-autonomous remediation scripts successfully caused the one or more failed pre-upgrade procedures to complete.

4. The method of claim 3 , further comprising:
determining that the executed one or more semi-autonomous remediation scripts do not cure all of the one or more failed pre-upgrade procedures; instructing a user to execute one or more manual remediation steps; and determining whether the executed one or more manual remediation steps successfully caused completion of the one or more failed pre-upgrade procedures.

5. The method of claim 1 , further comprising accessing an array of post-upgrade procedures from the repository, the array of post-upgrade procedures comprising corresponding code for identifying one or more conditions that must be met after the software product is upgraded to the target.

6. The method of claim 5 , wherein at least one pre-upgrade procedure of the array of pre-upgrade procedures accessed from the repository comprises at least one procedure defined by a user to be completed before the upgrade initiates or at least one post-upgrade procedure of the array of post-upgrade procedures access from the repository comprises at least one procedure defined by the user to be completed after the upgrade completes.

7. The method of claim 5 , wherein the array of pre-upgrade procedures accessed from the repository comprises an ordered arrangement of pre-upgrade procedures that controls an order in which the pre-upgrade procedures of the array of pre-upgrade procedures are to be successfully completed before the upgrade initiates or the array of post-upgrade procedures accessed from the repository comprises an ordered arrangement of post-upgrade procedures that controls an order in which the post-upgrade procedures are to be successfully completed after the upgrade completes.

8. The method of claim 1 , wherein upgrading the software product to the target comprises migrating the software product to a new software product.

9. The method of claim 1 , wherein upgrading the software product to the target comprises upgrading the software product from a first version to a second version of the software product.

10. A system, comprising one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the system to perform a method of updating a software component, the method comprising:
registering, with an update readiness system, a software product that is installed on a computing device by providing the update readiness system with a name of the software product and a version identifier of the software product; as a result of the registering, causing, by the update readiness system, an agent of the update readiness system to be installed on the computing device in association with the software product; receiving, by the update readiness system, an indication to upgrade the software product; receiving, by the update readiness system, a selected upgrade path for the software product, the selected upgrade path identifying a target for the software product; accessing, by the update readiness system, an array of pre-upgrade procedures from a repository based on the array being associated with the software product, the array of pre-upgrade procedures comprising code for identifying one or more conditions that must be met before the software product can be upgraded to the target; executing, by the update readiness system via the agent, one or more of the pre-upgrade procedures in advance of upgrading the software product to the target; accessing, by the update readiness system, one or more autonomous remediation scripts from the repository based on identification of one or more failed pre-upgrade procedures; executing, by the update readiness system via the agent, the one or more autonomous remediation scripts to cure the one or more failed pre-upgrade procedures; and initiating an upgrade of the software product to the target based on identifying, by the update readiness system, that the array of pre-upgrade procedures successfully completed execution.

11. The system of claim 10 , wherein the method further comprises: determining that the executed one or more autonomous remediation scripts do not cure all of the one or more failed pre-upgrade procedures; and initiating a semi-autonomous remediation procedure based on the determination that the executed one or more autonomous remediation scripts does not cure all of the one or more failed pre-upgrade procedures.

12. The system of claim 11 , wherein initiating the semi-autonomous remediation procedure comprises:
accessing one or more semi-autonomous remediation scripts from the repository; executing the one or more semi-autonomous remediation scripts; and determining whether the executed one or more semi-autonomous remediation scripts successfully caused the one or more failed pre-upgrade procedures to complete.

13. The system of claim 12 , wherein the method further comprises:
determining that the executed one or more semi-autonomous remediation scripts do not cure all of the one or more failed pre-upgrade procedures; instructing a user to execute one or more manual remediation steps; and determining whether the executed one or more manual remediation steps suc

Assignees

• VMware LLC
• Vmware Inc

Inventors

• Shelke Prashant
• Agrawal Ashish

Classifications

• G06F8/656 Primary

  while running · CPC title

• G06F8/61

  Installation · CPC title

• G06F9/45558

  Hypervisor-specific management and integration aspects · CPC title

• G06F11/0772

  Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers · CPC title

• G06F11/0793

  Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40) · CPC title