Constraint-based upgrade and deployment

Patent metadata

Field	Value
Publication number	US-10558454-B2
Application number	US-201916269133-A
Country	US
Kind code	B2
Filing date	Feb 6, 2019
Priority date	Jun 4, 2018
Publication date	Feb 11, 2020
Grant date	Feb 11, 2020

Abstract

One or more software products/services may be installed on a cloud deployment. Product versions of such services can be upgraded (or rolled back) based on a deployment plan comprising tasks adapted to reach a target deployment state. A central upgrade server can forward tasks to an upgrade agent for execution, the tasks being based on a current operational state of the cloud deployment (obtained by the upgrade agent) and one or more constraints. In multiple node deployments, some nodes may be upgraded to a new product version, while other nodes are kept at a current product version until stability of the new product version is determined. Traffic across nodes can be shaped to ensure a deployment is healthy before upgrading other nodes/deployments. If the health of a node/deployment does not meet specified criteria, an upgrade can be stopped, an alert can be triggered, and the node/deployment can be rolled back.

First claim

What is claimed is:

1. A system comprising:
one or more processors; and
memory storing instructions that, when executed by the one or more processors, cause the system to:
capture logs reflecting operational characteristics of a cloud deployment;
obtain a current status of a cloud deployment based on captured logs reflecting operational characteristics of the cloud deployment;
transmit the current status to a central upgrade server; and
receive, from the central upgrade server, a task to be performed at the cloud deployment, the task comprising one of a plurality of tasks commensurate with a target deployment state, wherein the task has passed a constraint check associated with a plurality of release channels, and wherein one or more products installed on the cloud deployment subscribe to at least one of the plurality of release channels, the plurality of release channels controlling a product release rollout, and the plurality of release channels comprising product release rollouts associated with product releases having differing levels of stability.

2. The system of claim 1 , wherein the logs are formatted in accordance with a specification setting forth compliance criteria.

3. The system of claim 1 , wherein the operational characteristics of the cloud deployment comprise at least one of health status of the cloud deployment and performance metrics of the cloud deployment.

4. The system of claim 1 , wherein the current status of the cloud deployment includes at least one of a product version running on the cloud deployment and an indication of products installed on the cloud deployment.

5. The system of claim 4 , wherein the products installed on the cloud deployment comprise at least one of a software service, a software daemon, and a software asset.

6. The system of claim 1 , wherein the plurality of tasks maps to a deployment plan defined to arrive at the target deployment state.

7. The system of claim 1 , wherein the received task is associated with a first deployment plan that has passed the constraint check, the constraint check comprising a check for at least one of product version compatibility, minimum release channel conflict, maintenance constraints, and downtime constraints.

8. The system of claim 1 , wherein the central upgrade server obtains information regarding at least one of new products to be installed on the cloud deployment and new product versions of products already installed on the cloud deployment from a configuration repository.

9. The system of claim 1 , wherein the task comprises one of a stop task, a change version task, and a start task.

10. The system of claim 1 , wherein the plurality of tasks comprise tasks instructing the system to upgrade one or more nodes of the cloud deployment in accordance with target traffic ratio, the target traffic ratio reflecting a first subset of the one or more nodes being upgraded to a new product version and a second subset of the one or more nodes being maintained at a current product version.

11. The system of claim 10 , wherein the central upgrade server adapts the target traffic ratio depending on a monitored stability of the first subset of the one or more nodes.

12. The system of claim 10 , wherein the central upgrade server instructs the system to roll-back to a previous product version upon a determination that the health or stability of the first subset of the one or more nodes does not meet a determined threshold.

13. A computer-implemented method, comprising:
capturing logs reflecting operational characteristics of a cloud deployment;
obtaining a current status of a cloud deployment based on captured logs reflecting operational characteristics of the cloud deployment;
transmitting the current status to a central upgrade server; and
receiving, from the central upgrade server, a task to be performed at the cloud deployment, the task comprising one of a plurality of tasks commensurate with a target deployment state, wherein the task has passed a constraint check associated with a plurality of release channels, and wherein one or more products installed on the cloud deployment subscribe to at least one of the plurality of release channels, the plurality of release channels controlling a product release rollout, and the plurality of release channels comprising product release rollouts associated with product releases having differing levels of stability.

14. The computer-implemented method of claim 13 , wherein the operational characteristics of the cloud deployment comprise at least one of health status of the cloud deployment and performance metrics of the cloud deployment.

15. The computer-implemented method of claim 13 , wherein the current status of the cloud deployment includes at least one of a product version running on the cloud deployment and an indication of products installed on the cloud deployment.

16. The computer-implemented method of claim 13 , wherein obtaining the current status of the cloud deployment based on the captured logs comprises determining a current database schema version.

17. The computer-implemented method of claim 16 , wherein the task comprises an upgrade task for upgrading the current database schema version to a new database schema version.

18. The computer-implemented method of claim 17 further comprising, upon determining that a database migration is in progress, postponing the upgrade task for upgrading the current database schema version until the database migration has been completed.

Assignees

• Palantir Technologies Inc

Inventors

• Mair Ian
• Dearment Greg
• Avital Lee
• Elliot Mark
• Nazario Michael
• Biswal Punyashloka
• Hickman William

Classifications

• H04L67/34

  involving the movement of software or configuration parameters  (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title

• H04L67/10

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

• G06F8/65 Primary

  Updates (security arrangements therefor G06F21/57) · CPC title