Performance monitoring of system version releases
US-2020012493-A1 · Jan 9, 2020 · US
US10853046B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10853046-B2 |
| Application number | US-201816219784-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 13, 2018 |
| Priority date | Dec 13, 2018 |
| Publication date | Dec 1, 2020 |
| Grant date | Dec 1, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Disclosed are some implementations of systems, apparatus, methods and computer program products for deploying software applications on server clusters. Characteristics of the server clusters are used to generate a deployment plan indicating an order in which the server clusters are to be updated and a timing with which the server clusters are to be updated. The characteristics of a server cluster can include a risk rating associated with the server cluster, an amount of traffic processed by the server cluster, and/or a size of the server cluster.
Opening claim text (preview).
What is claimed is: 1. A system comprising: a database system implemented using a server system, the database system configurable to cause: identifying a plurality of server clusters on which to deploy software including a set of computer-readable instructions, each of the server clusters including a plurality of servers; retrieving a plurality of risk ratings, each of the risk ratings being associated with a corresponding one of the plurality of server clusters; ascertaining, for each server cluster of the plurality of server clusters, an amount of traffic processed by the server cluster and a size of the server cluster, the size of the server cluster indicating a number of servers in the server cluster; generating a deployment plan indicating a deployment order and a deployment timing based, at least in part, on the plurality of risk ratings, the amount of traffic processed by each of the server clusters, and the size of each of the server clusters, the deployment order indicating an order in which deployment is to proceed on the server clusters, the deployment timing indicating a timing with which the software is to be deployed on the server clusters; and deploying the software on the server clusters based, at least in part, on the deployment plan, wherein deploying the software includes: installing the software on at least a first one of the server clusters according to the deployment plan; dynamically updating the deployment plan based, at least in part, on 1) a minimum confidence measure threshold associated with the risk rating of a server cluster of a first subset of the server clusters on which the software has not been deployed and 2) a confidence measure of a status of deployment of the software on at least a second subset of the server clusters on which the software has been deployed; and installing the software on at least a second one of the server clusters according to the updated deployment plan. 2. The system as recited in claim 1 , the server cluster of the first subset of the server clusters being the second one of the server clusters. 3. The system as recited in claim 1 , the database system further configurable to cause: identifying the second subset of the server clusters on which the software has been deployed; ascertaining, for each server cluster in the second subset of the server clusters, a time that has elapsed since deployment of the software on the server cluster; updating the confidence measure of the status of deployment of the software on the second subset of the server clusters based, at least in part, on the time that has elapsed since deployment of the software on each server cluster in the second subset of the server clusters, the amount of traffic processed by each server cluster in the second subset of the server clusters, and the size of each server cluster in the second subset of the server clusters; and updating the deployment plan based, at least in part, on the confidence measure and a minimum confidence measure threshold associated with at least one of the first subset of the server clusters on which the software has not been deployed. 4. The system as recited in claim 1 , wherein the software comprises a software update to a first software version running on the server clusters. 5. The system as recited in claim 1 , the database system further configurable to cause determining the deployment order based, at least in part, on the risk ratings. 6. The system as recited in claim 1 , the database system further configurable to cause generating the deployment plan further based, at least in part, on at least one of a) a total deployment time in which the deployment of the software on the server clusters is to be completed or b) a type of the traffic processed by each of the server clusters. 7. A computer program product comprising one or more non-transitory computer-readable media having computer-readable program code stored therein, the program code capable of being executed by one or more processors, the program code comprising computer-readable instructions configurable to cause: identifying a plurality of server clusters on which to deploy software including a set of computer-readable instructions, each of the server clusters including a plurality of servers; retrieving a plurality of risk ratings, each of the risk ratings being associated with a corresponding one of the plurality of server clusters; ascertaining, for each server cluster of the plurality of server clusters, an amount of traffic processed by the server cluster and a size of the server cluster, the size of the server cluster indicating a number of servers in the server cluster; generating a deployment plan indicating a deployment order and a deployment timing based, at least in part, on the plurality of risk ratings, the amount of traffic processed by each of the server clusters, and the size of each of the server clusters, the deployment order indicating an order in which deployment is to proceed on the server clusters, the deployment timing indicating a timing with which the software is to be deployed on the server clusters; and deploying the software on the server clusters based, at least in part, on the deployment plan, wherein deploying the software includes: installing the software on at least a first one of the server clusters according to the deployment plan; dynamically updating the deployment plan based, at least in part, on 1) a minimum confidence measure threshold associated with the risk rating of a server cluster of a first subset of the server clusters on which the software has not been deployed and 2) a confidence measure of a status of deployment of the software on at least a second subset of the server clusters on which the software has been deployed; and installing the software on at least a second one of the server clusters according to the updated deployment plan. 8. The computer program product as recited in claim 7 , the server cluster of the first subset of the server clusters being the second one of the server clusters. 9. The computer program product as recited in claim 7 , the program code comprising instructions further configurable to cause: identifying the second subset of the server clusters on which the software has been deployed; ascertaining, for each server cluster in the second subset of the server clusters, a time that has elapsed since deployment of the software on the server cluster; updating the confidence measure of the status of deployment of the software on the second subset of the server clusters based, at least in part, on the time that has elapsed since deployment of the software on each server cluster in the second subset of the server clusters, the amount of traffic processed by each server cluster in the second subset of the server clusters, and the size of each server cluster in the second subset of the server clusters; and updating the deployment plan based, at least in part, on the confidence measure and a minimum confidence measure threshold associated with at least one of the first subset of the server clusters on which the software has not been deployed. 10. The computer program product as recited in claim 7 , the program code comprising instructions further configurable to cause: determining the deployment order based, at least in part, on the risk ratings. 11. The computer program product as recited in claim 7 , the program code comprising instructions further configured to cause generating the deployment plan further based, at least in part, on at least one of a) a total deployment time in which the deployment of the software on the server clusters is to be completed or b) a type of the traffic processed by each of the server clusters. 12. A me
for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
Assignment of logical groups to network elements · CPC title
Installation · CPC title
the condition being updates or upgrades of network functionality · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.