Managing multi-single-tenant SaaS services

Patent metadata

Field	Value
Publication number	US-11922182-B2
Application number	US-202117646479-A
Country	US
Kind code	B2
Filing date	Dec 29, 2021
Priority date	Oct 27, 2017
Publication date	Mar 5, 2024
Grant date	Mar 5, 2024

Abstract

A system comprises data processing hardware and memory hardware. The memory hardware is in communication with the data processing hardware, and stores instructions that, when executed on the data processing hardware, cause the data processing hardware to perform a plurality of operations. In some examples, one of the operations may include receiving instance management configuration data for a single-tenant software-as-a-service (SaaS) application. Another operation may include further include receiving an image of the single-tenant SaaS application. Yet another operation can include generating, by the control plane manager, a control plane based on the instance management configuration data. The control plane is configured to create multiple instances of the single-tenant SaaS application based on the received image, and to manage the instances of the single-tenant SaaS application based on the received instance management configuration data. Another operation may include executing the control plane on the data processing hardware.

First claim

What is claimed is:

1. A computer-implemented method when executed by data processing hardware causes the data processing hardware to perform operations comprising:
for each respective single-tenant software-as-a-service (SaaS) application of a plurality of single-tenant SaaS applications:
receiving instance management configuration data comprising rules for generation and execution of a corresponding control plane, the instance management configuration data comprising a consumer-selectable parameter selected by a user associated with the instance management configuration data, the consumer-selectable parameter comprising a multi-region availability configuration request;
receiving a container image of the respective single-tenant SaaS application;
generating the corresponding control plane based on the received instance management configuration data, the generated control plane configured to create one or more instances of the respective single-tenant SaaS application; and
while the generated control plane executes, creating one or more additional instances of the respective single-tenant SaaS application in a plurality of regions based on the received instance management configuration data,
wherein generating the corresponding control plane for the respective single-tenant SaaS application comprises generating an executable script that defines creation and operation of the corresponding control plane, the executable script comprising the consumer-selectable parameter.

2. The computer-implemented method of claim 1 , wherein the generated control plane is configured for lifecycle management of each instance of the one or more additional instances of the respective single-tenant SaaS application, the lifecycle management comprising operations for reading, updating, and deleting a given instance of the one or more additional instances of the respective single-tenant SaaS application.

3. The computer-implemented method of claim 2 , wherein the lifecycle management further comprises operations for backing up and restoring, restarting, and shutting down each instance of the one or more additional instances of the respective single-tenant SaaS application.

4. The computer-implemented method of claim 3 , wherein the instance management configuration data defines the operations of the lifecycle management of each instance of the one or more additional instances of the respective single-tenant SaaS application.

5. The computer-implemented method of claim 1 , wherein the generated control plane is configured to create and deploy each instance of the respective single-tenant SaaS application on a virtual machine or a dedicated host device.

6. The computer-implemented method of claim 1 , wherein the generated control plane is configured to:
assess operating or usage metrics of each instance of the one or more additional instances of the respective single-tenant SaaS application; and
store the assessed operating or usage metrics at memory hardware in communication with the data processing hardware.

7. The computer-implemented method of claim 1 , wherein the instance management configuration data for the respective single-tenant SaaS application further comprises a plurality of parameters for executing the one or more instances of the respective single-tenant SaaS application for one or more tenants.

8. The computer-implemented method of claim 7 , wherein the parameters include at least one of:
service rights;
availability;
security isolation;
host location; or
monitoring.

9. The computer-implemented method of claim 1 , wherein the instance management configuration data for the respective single-tenant SaaS application comprises one or more instance templates including one or more predefined parameters.

10. A system comprising:
data processing hardware; and
memory hardware in communication with the data processing hardware, the memory hardware storing instructions that when executed on the data processing hardware cause the data processing hardware to perform operations comprising:
for each respective single-tenant software-as-a-service (SaaS) application of a plurality of single-tenant SaaS applications:
receiving instance management configuration data comprising rules for generation and execution of a corresponding control plane, the instance management configuration data comprising a consumer-selectable parameter selected by a user associated with the instance management configuration data, the consumer-selectable parameter comprising a multi-region availability configuration request;
receiving a container image of the respective single-tenant SaaS application;
generating the corresponding control plane based on the received instance management configuration data, the generated control plane configured to create one or more instances of the respective single-tenant SaaS application; and
while the generated control plane executes, creating one or more additional instances of the respective single-tenant SaaS application in a plurality of regions based on the received instance management configuration data,
wherein generating the corresponding control plane for the respective single-tenant SaaS application comprises generating an executable script that defines creation and operation of the corresponding control plane, the executable script comprising the consumer-selectable parameter.

11. The system of claim 10 , wherein the generated control plane is configured for lifecycle management of each instance of the one or more additional instances of the respective single-tenant SaaS application, the lifecycle management comprising operations for reading, updating, and deleting a given instance of the one or more additional instances of the respective single-tenant SaaS application.

12. The system of claim 11 , wherein the lifecycle management further comprises operations for backing up and restoring, restarting, and shutting down each instance of the one or more additional instances of the respective single-tenant SaaS application.

13. The system of claim 12 , wherein the instance management configuration data defines the operations of the lifecycle management of each instance of the one or more additional instances of the respective single-tenant SaaS application.

14. The system of claim 10 , wherein the generated control plane is configured to create and deploy each instance of the respective single-tenant SaaS application on a virtual machine or a dedicated host device.

15. The system of claim 10 , wherein the generated control plane is configured to:
assess operating or usage metrics of each instance of the one or more additional instances of the respective single-tenant SaaS application; and
store the assessed operating or usage metrics at memory hardware in communication with the data processing hardware.

16. The system of claim 10 , wherein the instance management configuration data for the respective single-tenant SaaS application further comprises a plurality of parameters for executing the one or more instances of the respective single-tenant SaaS application for one or more tenants.

17. The system of claim 16 , wherein the parameters include at least one of:
service rights;
availability;
security isolation;
host location; or
monitoring.

18. The system of claim 10 , wherein the instance management configuration data for the respective single-tenant SaaS application comprises one or more instance templates including one or more predefined parameters.

Assignees

• Google Llc

Inventors

• Peterkofsky Roy
• Earl William
• Taillefer Martin
• Dahlin Michael
• Prasad Chandra
• Kowalski Jaroslaw
• Berenberg Anna
• Kennaway Kristian
• Mohr Alexander
• Haridas Jaidev

Classifications

• G06F9/44505 Primary

  Configuring for program initiating, e.g. using registry, configuration files · CPC title

• G06F8/71 Primary

  Version control (security arrangements therefor G06F21/57); Configuration management · CPC title

• G06F9/485 Primary

  Task life-cycle, e.g. stopping, restarting, resuming execution (G06F9/4881 takes precedence) · CPC title

• G06F9/5072

  Grid computing · CPC title

• G06F9/5077

  Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455) · CPC title