Managing multi-single-tenant SaaS services

Patent metadata

Field	Value
Publication number	US-11221860-B2
Application number	US-202017099717-A
Country	US
Kind code	B2
Filing date	Nov 16, 2020
Priority date	Oct 27, 2017
Publication date	Jan 11, 2022
Grant date	Jan 11, 2022

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 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:
receiving, at a control plane manager executing on the data processing hardware, instance management configuration data for each of a plurality of single-tenant software-as-a-service (SaaS) applications, the instance management configuration data for each single-tenant SaaS application comprising (i) a plurality of parameters for executing N number of instances of the corresponding single-tenant SaaS application for N number of tenants and (ii) rules for generation and execution of a corresponding control plane;
receiving, at the control plane manager, an image of each of the plurality of single-tenant SaaS applications;

generating, by the control plane manager, a corresponding control plane for each single-tenant SaaS application based on the corresponding received instance management configuration data, each control plane configured to create the N number of instances of the corresponding single-tenant SaaS application based on the corresponding received image and manage the N number of instances of the corresponding single-tenant SaaS application based on the corresponding received instance management configuration data, each instance of the N number of instances executing for a respective one of the N number of tenants of the corresponding single-tenant SaaS application, and executing each control plane on the data processing hardware.

2. The system of claim 1 , wherein each control plane is configured for lifecycle management of each instance of the N number of instances of the corresponding single-tenant SaaS application, the lifecycle management comprising operations for creating, reading, updating, and deleting a given instance of the N number of instances of the corresponding single-tenant SaaS application.

3. The system of claim 2 , wherein the lifecycle management further comprises operations for backing up and restoring, restarting, and shutting down each instance of the N number of instances of the corresponding single-tenant SaaS application.

4. The system of claim 3 , wherein the instance management configuration data defines the operations of the lifecycle management of each instance of the N number of instances of the corresponding single-tenant SaaS application.

5. The system of claim 1 , wherein each control plane is configured to create and deploy each instance of the N number of instances of the corresponding single-tenant SaaS application on a virtual machine or a dedicated host device.

6. The system of claim 1 , wherein each control plane is configured to:
assess operating or usage metrics of each instance of the N number of instances of the corresponding single-tenant SaaS application; and
store the assessed operating or usage metrics in the memory hardware in communication with the data processing hardware.

7. The system of claim 1 , wherein the parameters include one or more of service rights, availability, security isolation, host location, and monitoring and support.

8. The system of claim 1 , wherein the instance management configuration data for each single-tenant SaaS application includes one or more instance templates including one or more predefined parameters.

9. The system of claim 1 , wherein generating the corresponding control plane for each single-tenant SaaS application comprises generating an executable script that defines creation and operation of the corresponding control plane.

10. The system of claim 1 , further comprising, in response to a lifecycle management command issued by a corresponding tenant of the N number of tenants of one of the plurality of single tenant SaaS applications to manage a lifecycle of a respective instance executing for the corresponding tenant, permitting, by the control plane manager, the corresponding control plane to manage the lifecycle of the respective instance.

11. The system of claim 10 , wherein the control plane manager is configured to, in response to the lifecycle management command issued by the corresponding tenant comprising a backup and restoration lifecycle management command, backup and restore the respective instance of the corresponding single-tenant SaaS application executing for the corresponding tenant.

12. The system of claim 10 , wherein the control plane manager is configured to, in response to the lifecycle management command executed by issued by the corresponding tenant comprising an update lifecycle management command, update the respective instance of the corresponding single-tenant SaaS application executing for the corresponding tenant.

13. The system of claim 1 , wherein the control plane manager is configured to publish a consumer application interface for each control plane through which each tenant of the N number of tenants accesses the corresponding control plane.

14. The system of claim 1 , wherein the plurality of parameters comprise one or more consumer parameters selectable by each tenant of the N number of tenants of the corresponding single tenant SaaS application and a deployment type, the deployment type comprising a direct deployment type, a single virtual machine deployment type, or a high availability deployment type.

15. A method comprising;
receiving, at a control plane manager executing on data processing hardware, instance management configuration data for each of a plurality of single-tenant software-as-a-service (SaaS) applications, the instance management configuration data for each single-tenant SaaS application comprising (i) a plurality of parameters for executing N number of instances of the corresponding single-tenant SaaS application for N number of tenants and (ii) rules for generation and execution of a corresponding control plane;
receiving, at the control plane manager, an image of each of the plurality of single-tenant SaaS applications;
generating, by the control plane manager, a corresponding control plane for each single-tenant SaaS application based on the corresponding received instance management configuration data, each control plane configured to create the N number of instances of the corresponding single-tenant SaaS application based on the corresponding received image and manage the N number of instances of the corresponding single-tenant SaaS application based on the corresponding received instance management configuration data, each instance of the N number of instances executing for a respective one of the N number of tenants of the corresponding single-tenant SaaS application, and
executing each control plane on the data processing hardware.

16. The method of claim 15 , wherein each control plane is configured for lifecycle management of each instance of the N number of instances of the corresponding single-tenant SaaS application, the lifecycle management comprising operations for creating, reading, updating, and deleting a given instance of the N number of instances of the corresponding single-tenant SaaS application.

17. The method of claim 16 , wherein the lifecycle management further comprises operations for backing up and restoring, restarting, and shutting down each instance of the N number of instances of the corresponding single-tenant SaaS application.

18. The method of claim 17 , wherein the instance management configuration data defines the operations of the lifecycle management of each instance of

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

• G06F2009/45575

  Starting, stopping, suspending or resuming virtual machine instances · CPC title

• G06F2009/45562

  Creating, deleting, cloning virtual machine instances · CPC title

• G06F9/45558

  Hypervisor-specific management and integration aspects · CPC title

• G06F9/5072

  Grid computing · CPC title

• G06F9/485 Primary

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