Multi-tenant upgrading

• US 10,338,910 B2
• Filed: 01/05/2015
• Issued: 07/02/2019
• Est. Priority Date: 01/05/2015
• Status: Active Grant

• Current Assignee: Micro Focus LLC (Open Text Corporation)
• Original Assignee: entIT Software LLC (Open Text Corporation)
• Inventors: Spieler, Orasio, Vizelman, Dmitry, Kopelevich, Adi
• Primary Examiner(s): Bui, Hanh Thi-Minh
• Application Number:
  US15/539,885
• Publication Number:
  US 20170371641A1
• Time in Patent Office: 1,639 Days
• CPC Class Codes: G06F 11/1433 during software upgrading
• CPC Class Codes: G06F 2009/45562 Creating, deleting, cloning virtual machine instances
• CPC Class Codes: G06F 8/433 Dependency analysis; Data or control flow analysis
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

Example implementations relate to multi-tenant upgrading. Some implementations may receive a request to upgrade a first tenant from an original version of an application to a new version of the application. The new version of the application may be backwards compatible with the original version. Some implementations may also upgrade the first tenant to the new version in response to the request while data according to the original version is simultaneously being provided to a second tenant. Additionally, some implementations may also provide data according to the new version for tenants that have completed the upgrade and provide data according to the original version of the application for tenants that have not upgraded.

Claims

1. A system comprising:

a processor; and

a non-transitory storage medium storing instructions executable on the processor to;

receive a request to upgrade a first tenant from an original version of an application to a new version of the application, the new version being backwards compatible with the original version;

upgrade the first tenant to the new version in response to the request while data according to the original version is simultaneously being provided to a second tenant, the upgrading of the first tenant to the new version comprising updating a data table by adding entries to the data table that are according to a new schema for the new version, the added entries including data copied from an entry according to the original version in the data table, wherein the new version is installed on a first physical resource while the original version is executing on a second physical resource; and

provide data according to the new version for tenants that have completed the upgrade and provide data according to the original version of the application for tenants that have not upgraded; and

a cloud controller to direct tenant traffic to the second physical resource while the new version of the application is being installed on the first physical resource.

2. The system of claim 1, wherein the data according to the new version and the data according to the original version are provided by a same physical resource.

3. The system of claim 1, wherein upgrading the first tenant to the new version comprises:

locating first data associated with the first tenant in the data table, wherein the data copied from the entry according to the original version in the data table comprises the first data; and

adding the entries according to the new version to the data table while maintaining the first data according to the original version unchanged in the data table.

4. The system of claim 3, further comprising:

parsing the first data according to the original version to determine if the first data includes data to be used for the new version; and

copying the data to be used for the new version into the added entries, the copying being performed only for the first tenant.

5. The system of claim 4, wherein the copying of the data to be used for the new version comprises reformatting the data to be used for the new version.

6. The system of claim 3, wherein adding the entries comprises:

changing a status of the first tenant in the data table to upgraded; and

associating the added entries with the first tenant.

7. The system of claim 6, wherein providing the data according to the new version and providing the data according to the original version comprises:

receiving a request from a third tenant to access the application;

determining whether the third tenant has been upgraded to the new version;

in response to the third tenant having been upgraded to the new version, pulling data according to the new schema for the new version associated with the third tenant from the data table; and

in response to the third tenant having not been upgraded to the new version, accessing original schema data from the data table, the original schema data comprising the data according to the original version.

8. The system of claim 1, wherein the data according to the new version and the data according to the original version are provided by the new version of the application.

9. The system of claim 1, wherein the added entries are columns added to the data table that are according to the new schema for the new version, and the entry according to the original version is another column in the data table.

10. A non-transitory machine-readable storage medium storing instructions that when executed cause a system to:

receive a request to upgrade a first tenant from an original version of an application to a new version of the application, the new version being backwards compatible with the original version and providing original version data according to the original version and new version data according to the new version;

upgrade the first tenant to the new version in response to the request by creating a new first tenant record, the new first tenant record;

indicating that the first tenant has upgraded to the new version; and

including the new version data,

wherein the new version is installed on a first physical resource while the original version is executing on a second physical resource;

store the new first tenant record in a data repository, the data repository containing an original first tenant record, the original first tenant record including the original version data that is associated with the first tenant;

provide the original version data to a second tenant by the new version of the application;

provide the new version data to the first tenant by the new version of the application, the new version data including the new first tenant record; and

direct, by a cloud controller, tenant traffic to the second physical resource while the new version of the application is being installed on the first physical resource.

11. The non-transitory machine-readable storage medium of claim 10, wherein the new first tenant record including the new version data is separate from the original first tenant record including the original version data in a data table that is part of the data repository.

12. The non-transitory machine-readable storage medium of claim 11, wherein creating the new first tenant record comprises:

locating data in the original first tenant record associated with the first tenant in the data table; and

adding the new first tenant record to the data table while maintaining the original first tenant record.

13. A method executed by a computer system, comprising:

determining, in response to receiving a request from a first tenant to upgrade from an original version of an application to a new version of the application that is backwards compatible with the original version, whether the first tenant has already been upgraded;

upgrading the first tenant to the new version in response to determining that the first tenant has not already been upgraded, the upgrading of the first tenant to the new version comprising updating a data table by adding entries to the data table that are according to a new schema for the new version, the added entries including data copied from an entry according to the original version in the data table, wherein the new version is installed on a first physical resource while the original version is executing on a second physical resource;

providing to the first tenant data according to the new version in response to determining that the first tenant has been upgraded, and providing to the first tenant data according to the original version in response to determining that the first tenant has not been upgraded;

providing to a second tenant data according to the original version during the upgrading of the first tenant, the second tenant having not been upgraded to the new version; and

directing, by a cloud controller, tenant traffic to the second physical resource while the new version of the application is being installed on the first physical resource.

14. The method of claim 13, wherein upgrading the first tenant to the new version comprises:

preventing, by the computer system, access to the data according to the original version by the first tenant while maintaining access to the data according to the original version by other tenants.

15. The method of claim 14, wherein the data according to the new version and the data according to the original version are provided by the new version of the application executing on a physical resource.

16. The method of claim 13, further comprising:

parsing first data according to the original version in the data table to determine if the first data includes data to be used for the new version; and

copying the data to be used for the new version into the added entries, the copying being performed only for the first tenant.

17. The method of claim 16, wherein the copying comprises reformatting the data to be used for the new version.

18. The method of claim 13, wherein the added entries are columns added to the data table that are according to the new schema for the new version, and the entry according to the original version is another column in the data table.