公开(公告)号：US20230087544A1

公开(公告)日：2023-03-23

申请号：US18049265

申请日：2022-10-24

Applicant: salesforce.com, inc.

Inventor： Sreeram Duvur ,  Vijayanth Devadhar ,  Matthew Gainsborough ,  Kiet Phong ,  Sathish Santhanam ,  Lawrence Thomas Lopez

IPC: G06F8/65

Abstract: According to some implementations, while a proxy routes production traffic to a first application (app) version that runs in a plurality of container orchestration system (cos) pods having first app version containers, configuration information is received including an identification of a second app version container image for a second app version. The second app version is an updated version of the first app version. Cos pods having second app version containers are brought up based on the second app version container image identified in the configuration information. Test and/or warmup traffic is caused to be routed to the second app version containers. Responsive to an indication regarding the routing of the test and/or warmup traffic to the second app version, causing a transition to sending production traffic to the second app version containers instead of to the first app version.

公开(公告)号：US20200241865A1

公开(公告)日：2020-07-30

申请号：US16261504

申请日：2019-01-29

Applicant: salesforce.com, inc.

Inventor： Kiet Phong ,  Sreeram Duvur ,  Matthew Gainsborough

IPC: G06F8/65 ,  H04L29/08

Abstract: A method for performing pre-release, version specific testing to validate application versions is described. Upon receiving instructions from a release orchestrator to validate a second application version prior to a transition to sending production traffic to the second application version instead of a first application version, a determination of an application version identifier for second application version is performed. Tests are selected based on the application version identifier and version rules. The tests are performed by sending test traffic to the second application version via a routing engine while the routing engine routes production traffic to the first application version. Based on the responses to the test traffic, a determination that any failure rules for any of the tests that failed indicate that on a failure the transition should not occur is performed. Responsive to that determination, a communication to the release orchestrator that the second application version is not validated for production traffic and the transition should not occur is performed.

公开(公告)号：US20200241864A1

公开(公告)日：2020-07-30

申请号：US16261501

申请日：2019-01-29

Applicant: salesforce.com, inc.

Inventor： Sreeram Duvur ,  Vijayanth Devadhar ,  Matthew Gainsborough ,  Kiet Phong ,  Sathish Santhanam ,  Lawrence Thomas Lopez

IPC: G06F8/65

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.

公开(公告)号：US20200241863A1

公开(公告)日：2020-07-30

申请号：US16261495

申请日：2019-01-29

Applicant: salesforce.com, inc.

Inventor： Sreeram Duvur ,  Vijayanth Devadhar ,  Matthew Gainsborough ,  Kiet Phong ,  Sathish Santhanam ,  Lawrence Thomas Lopez

IPC: G06F8/65

Abstract: A release orchestration mechanism for cloud services. According to some implementations, while an app aware proxy routes production traffic to a first application (app) version that runs in a plurality of container orchestration system (COS) pods having first app version containers, configuration information is received. When a threshold number of the COS pods having the second app version containers are live, a validation of the second app version is caused. Then a transition to sending production traffic to the second app version containers is performed. After causing the transition, timers are started based on a time period indicated in the configuration information and the first app version containers are instructed to gracefully shut down. Based on expiration of the timers, any of the COS pods having the first app version containers that are not yet shut down are forced to shut down.

公开(公告)号：US11003434B2

公开(公告)日：2021-05-11

申请号：US16261501

申请日：2019-01-29

Applicant: salesforce.com, inc.

Inventor： Sreeram Duvur ,  Vijayanth Devadhar ,  Matthew Gainsborough ,  Kiet Phong ,  Sathish Santhanam ,  Lawrence Thomas Lopez

IPC: G06F8/65

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.

公开(公告)号：US10768923B2

公开(公告)日：2020-09-08

申请号：US16261504

申请日：2019-01-29

Applicant: salesforce.com, inc.

Inventor： Kiet Phong ,  Sreeram Duvur ,  Matthew Gainsborough

IPC: G06F9/44 ,  G06F8/65 ,  H04L29/08

Abstract: Upon receiving instructions from a release orchestrator to validate a second application version prior to a transition to sending production traffic to the second application version instead of a first application version, a determination of an application version identifier for a second application version is performed. Tests are selected based on the application version identifier and version rules. The tests are performed by sending test traffic to the second application version via a routing engine while the routing engine routes production traffic to the first application version. Based on the responses to the test traffic, a determination that any failure rules for any of the tests that failed indicate that on a failure the transition should not occur is performed. Responsive to that determination, a communication to the release orchestrator that the second application version is not validated for production traffic and the transition should not occur is performed.

公开(公告)号：US11748090B2

公开(公告)日：2023-09-05

申请号：US18049265

申请日：2022-10-24

Applicant: Salesforce.com, Inc.

Inventor： Sreeram Duvur ,  Vijayanth Devadhar ,  Matthew Gainsborough ,  Kiet Phong ,  Sathish Santhanam ,  Lawrence Thomas Lopez

IPC: G06F8/65

CPC classification number: G06F8/65

Abstract: According to some implementations, while a proxy routes production traffic to a first application (app) version that runs in a plurality of container orchestration system (cos) pods having first app version containers, configuration information is received including an identification of a second app version container image for a second app version. The second app version is an updated version of the first app version. Cos pods having second app version containers are brought up based on the second app version container image identified in the configuration information. Test and/or warmup traffic is caused to be routed to the second app version containers. Responsive to an indication regarding the routing of the test and/or warmup traffic to the second app version, causing a transition to sending production traffic to the second app version containers instead of to the first app version.

公开(公告)号：US11507364B2

公开(公告)日：2022-11-22

申请号：US17225143

申请日：2021-04-08

Applicant: salesforce.com, inc.

Inventor： Sreeram Duvur ,  Vijayanth Devadhar ,  Matthew Gainsborough ,  Kiet Phong ,  Sathish Santhanam ,  Lawrence Thomas Lopez

IPC: G06F8/65

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.

公开(公告)号：US20210224059A1

公开(公告)日：2021-07-22

申请号：US17225143

申请日：2021-04-08

Applicant: salesforce.com, inc.

Inventor： Sreeram Duvur ,  Vijayanth Devadhar ,  Matthew Gainsborough ,  Kiet Phong ,  Sathish Santhanam ,  Lawrence Thomas Lopez

IPC: G06F8/65

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.

公开(公告)号：US10776099B2

公开(公告)日：2020-09-15

申请号：US16261495

申请日：2019-01-29

Applicant: salesforce.com, inc.

Inventor： Sreeram Duvur ,  Vijayanth Devadhar ,  Matthew Gainsborough ,  Kiet Phong ,  Sathish Santhanam ,  Lawrence Thomas Lopez

IPC: G06F8/65

Abstract: A release orchestration mechanism for cloud services. According to some implementations, while an app aware proxy routes production traffic to a first application (app) version that runs in a plurality of container orchestration system (COS) pods having first app version containers, configuration information is received. When a threshold number of the COS pods having the second app version containers are live, a validation of the second app version is caused. Then a transition to sending production traffic to the second app version containers is performed. After causing the transition, timers are started based on a time period indicated in the configuration information and the first app version containers are instructed to gracefully shut down. Based on expiration of the timers, any of the COS pods having the first app version containers that are not yet shut down are forced to shut down.