Cloud services release orchestration with a reusable deployment pipeline

Patent metadata

Field	Value
Publication number	US-11507364-B2
Application number	US-202117225143-A
Country	US
Kind code	B2
Filing date	Apr 8, 2021
Priority date	Jan 29, 2019
Publication date	Nov 22, 2022
Grant date	Nov 22, 2022

Abstract

Cloud services release orchestration with a reusable deployment pipeline. According to some implementations, responsive to receiving from a COS controller parameters from configuration information provided to the COS controller while an app aware proxy routes production traffic to a first application (app) version that communicates with a database management system (DBMS) and that runs in container orchestration system (COS) pods having first app version containers, causing a validation of a second app version using COS pods having second app version containers that are now live after having been brought up by the COS controller responsive to the provision of the configuration information. After the validation, causing the transition to sending production traffic to the second app version containers that are determined to be live instead of to the first app version containers. Then causing post-release activities using DBMS connection information for the first app version that was in the configuration information and that was provided through the COS controller.

First claim

What is claimed is:

1. A method comprising:
responsive to receiving from a COS controller a set of parameters from configuration information provided to the COS controller while an app aware proxy routes production traffic to a first application (app) version that communicates with a database management system (DBMS) and that runs in container orchestration system (COS) pods having first app version containers, causing a validation of a second app version using COS pods having second app version containers that are now live after having been brought up by the COS controller responsive to the provision of the configuration information, wherein the configuration information is to cause a transition to the second app version which is an update to the first app version, wherein the causing a validation includes:
causing a proxy control plane to configure an app aware proxy with routing rules that distinguish between test traffic and production traffic and to send only the test traffic to those of the second app version containers determined to be live;
causing an engine to send the test traffic with a value in a header field that the app aware proxy can use to route that traffic to the second app version containers;
receiving from the engine an indication that a result of the test traffic reflects that the second app version is validated for production traffic; and

after the validation, causing the transition to sending production traffic to the second app version containers that are determined to be live instead of to the first app version containers; and
causing post-release activities using DBMS connection information for the first app version that was in the configuration information and that was provided through the COS controller.

2. The method of claim 1 , wherein the causing a validation also includes:
subscribing, using identification information in the set of parameters, to a proxy control plane to receive network information for the COS pods having the second app version containers;
receiving from the proxy control plane the network information regarding at least some of the COS pods having the second app version containers;
determining, using the network information, when a first threshold number of the COS pods having the second app version containers have been brought up by the COS controller;
determining when a second threshold number of the COS pods having the second app version containers are live; and
communicating with the engine to determine that the second app version is validated for production traffic.

3. The method of claim 2 , wherein the identification information includes a services collection identifier and a second app version identifier.

4. The method of claim 2 , wherein the causing a validation includes:
receiving, by the proxy control plane from a service discovery service, both:
the identification information provided through the COS controller receiving the configuration information and bringing up the COS pods having the second app version containers; and
the network information for the COS pods having the second app version containers.

5. The method of claim 2 , wherein the causing the transition includes:
causing the proxy control plane to,
change the routing rules in the app aware proxy to cause the transition to sending production traffic to the COS pods having the second app version containers that are live; and
cause the app aware proxy to reply affirmatively to requests whether the second app version containers are receiving production traffic.

6. The method of claim 5 , wherein the causing the proxy control plane to cause the app aware proxy to reply affirmatively to requests whether the second app version containers are receiving production traffic includes:
causing a URL derived from the identification information to affirmatively respond to pings requesting whether the second app version containers are receiving production traffic.

7. The method of claim 2 , wherein the determining when the second threshold number of the COS pods having the second app version containers are live includes:
sending liveness probe requests to each of the COS pods having the second app version containers until that COS pod having the second app version container responds with an indication that it is live.

8. The method of claim 2 , wherein the causing post-release activities is performed responsive to a notification from the proxy control plane that the COS pods having the first app version containers are all shut down.

9. The method of claim 8 , wherein the notification from the proxy control plane that the COS pods having the first app version containers are all shut down is responsive to the proxy control plane receiving from the service discovery service notifications reflecting that all of the COS pods having the first app version containers are shut down.

10. The method of claim 1 , wherein the causing post-release activities includes causing database cleanup activities related to the first app version that include deleting tables and dropping custom indices.

11. The method of claim 2 , wherein the network information includes internet protocol (IP) addresses and port numbers for the second app version containers.

12. A non-transitory machine-readable storage medium that provides instructions that, if executed by a machine, will cause said machine to perform operations comprising:
responsive to receiving from a COS controller a set of parameters from configuration information provided to the COS controller while an app aware proxy routes production traffic to a first application (app) version that communicates with a database management system (DBMS) and that runs in container orchestration system (COS) pods having first app version containers, causing a validation of a second app version using COS pods having second app version containers that are now live after having been brought up by the COS controller responsive to the provision of the configuration information, wherein the configuration information is to cause a transition to the second app version which is an update to the first app version, wherein the causing a validation includes:
causing a proxy control plane to configure an app aware proxy with routing rules that distinguish between test traffic and production traffic and to send only the test traffic to those of the second app version containers determined to be live;
causing an engine to send the test traffic with a value in a header field that the app aware proxy can use to route that traffic to the second app version containers; and
receiving from the engine an indication that a result of the test traffic reflects that the second app version is validated for production traffic;

after the validation, causing the transition to sending production traffic to the second app version containers that are determined to be live instead of to the first app version containers; and
causing post-release activities using DBMS connection information for the first app version that was in the configuration information and that was provided through the COS controller.

13. The non-transitory machine-readable storage medium of claim 12 , wherein the causing a validation also includes:
subscribing, using identification information in the set of parameters, to the proxy control plane to receive network information for the COS pods having the second app version containers;
receiving from the proxy control plane the network information regarding at least some of the COS pods having the second app version containers;
determining, using the network information, when a first threshold number of the COS pod

Assignees

• Salesforce Com Inc

Inventors

• Duvur Sreeram
• Devadhar Vijayanth
• Gainsborough Matthew
• Phong Kiet
• Santhanam Sathish
• Lopez Lawrence Thomas

Classifications

• G06F8/65 Primary

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

• G06F9/455

  Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines · CPC title