Downloadable cartridges for a multi-tenant platform-as-a-service (PaaS) system

• US 10,033,800 B2
• Filed: 01/28/2016
• Issued: 07/24/2018
• Est. Priority Date: 01/09/2014
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: McGrath, Michael, Honce, Jhon, Morie, Paul, Mace, Daniel
• Primary Examiner(s): Wasel, Mohamed A
• Application Number:
  US15/009,574
• Publication Number:
  US 20160149999A1
• Time in Patent Office: 908 Days
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 16/122 using management policies backup systems G06F11/1446; file migration policies for HSM systems G06F16/185
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 16/219 Managing data history or versioning querying versioned data G06F16/2474; querying temporal data G06F16/2477
• CPC Class Codes: G06F 16/2329 using versioning
• CPC Class Codes: G06F 2009/45595 Network integration; Enabling network access in virtual machine instances
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 8/656 while running
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

Implementations for downloadable cartridges for a multi-tenant Platform-as-a-Service (PaaS) system are disclosed. A method of the disclosure includes parsing a cartridge manifest corresponding to a cartridge to determine a source location of files of the cartridge and causing the files of the cartridge to be obtained from the determined source location for use by at least one node of a multi-tenant PaaS system.

Claims

1. A method, comprising:

receiving, by a processing device of a multi-tenant Platform-as-a-Service (PaaS) system comprising one or more components executed in a virtual environment, a request for a cartridge from an application of the multi-tenant PaaS, wherein the cartridge is created and maintained outside of the multi-tenant PaaS system;

parsing, by the processing device responsive to receiving the request, a cartridge manifest corresponding to the requested cartridge, wherein the cartridge manifest is maintained separate from the cartridge;

determining, based on parsing the cartridge manifest, a source location of files of the cartridge; and

causing, by the processing device, the files of the cartridge to be obtained from the determined source location for use by at least one node of the multi-tenant PaaS system, wherein the cartridge provides functionality to execute application on the at least one node of the multi-tenant PaaS system.

2. The method of claim 1, further comprising:

receiving, by the processing device of the multi-tenant PaaS system, a location of the cartridge manifest corresponding to the cartridge that is maintained outside of the multi-tenant PaaS system; and

downloading, by the processing device of the multi-tenant PaaS system, the cartridge manifest from the received location.

3. The method of claim 1, wherein the functionality comprising at least one of configuration templates, scripts, dependencies, or features to add to the applications.

4. The method of claim 1, wherein the cartridge manifest comprises:

a file detailing features of the cartridge; and

fields utilized by the multi-tenant PaaS system to deploy the cartridge to the at least one node.

5. The method of claim 1, wherein the location of the cartridge manifest is specified as a Uniform Resource Locator (URL).

6. The method of claim 1, wherein the parsing further comprises:

locating a source location field of the cartridge manifest; and

determining data of the source location field to indicate the source location of the files of the cartridge, wherein the source location of the files of the cartridge is separate from the multi-tenant PaaS system.

7. The method of claim 6, wherein the source location of the files of the cartridge is specified as a Uniform Resource Locator (URL).

8. The method of claim 1, wherein the node is a virtual machine (VM) of the virtual environment, the VM hosting the application that requested the cartridge, and wherein the cartridge is executed as part of a gear that comprises a resource-constrained processing space of the VM.

9. A system, comprising:

a memory; and

a processing device, communicably coupled to the memory, to;

receive a request for a cartridge from an application of a multi-tenant Platform-as-a-Service (PaaS) system comprising one or more components executed in a virtual environment, wherein the cartridge is created and maintained outside of the multi-tenant PaaS system;

parse, responsive to receiving the request, a cartridge manifest corresponding to the requested cartridge, wherein the cartridge manifest is maintained separate from the cartridge;

determine, based on parsing the cartridge manifest, a source location of files of the cartridge; and

cause the files of the cartridge to be obtained from the determined source location for use by at least one node of the multi-tenant PaaS system, wherein the cartridge provides functionality to execute application on the at least one node of the multi-tenant PaaS system.

10. The system of claim 9, the processing device further to:

receive a location of the cartridge manifest corresponding to the cartridge that is maintained outside of the multi-tenant PaaS system; and

download the cartridge manifest from the received location.

11. The system of claim 9, wherein the functionality comprising at least one of configuration templates, scripts, dependencies, or features to add to the applications.

12. The system of claim 9, wherein the cartridge manifest comprises:

a file detailing features of the cartridge; and

fields utilized by the multi-tenant PaaS system to deploy the cartridge to the at least one node.

13. The system of claim 9, wherein to parse the cartridge manifest the processing device is further to:

locate a source location field of the cartridge manifest; and

determine data of the source location field to indicate the source location of the files of the cartridge, wherein the source location of the files of the cartridge is separate from the multi-tenant PaaS system.

14. The system of claim 9, wherein the node is a virtual machine (VM) of the virtual environment, the VM hosting the application that requested the cartridge, and wherein the cartridge is executed as part of a gear that comprises a resource-constrained processing space of the VM.

15. A non-transitory machine-readable storage medium including instructions that, when accessed by a processing device, cause the processing device to:

receive, by the processing device of a multi-tenant Platform-as-a-Service (PaaS) system comprising one or more components executed in a virtual environment, a request for a cartridge from an application of the multi-tenant PaaS, wherein the cartridge is created and maintained outside of the multi-tenant PaaS system;

parse, by the processing device responsive to receiving the request, a cartridge manifest corresponding to the requested cartridge, wherein the cartridge manifest is maintained separate from the cartridge;

determine, based on parsing the cartridge manifest, a source location of files of the cartridge; and

cause, by the processing device, the files of the cartridge to be obtained from the determined source location for use by at least one node of the multi-tenant PaaS system, wherein the cartridge provides functionality to execute application on the at least one node of the multi-tenant PaaS system.

16. The non-transitory machine-readable storage medium of claim 15, wherein the processing device is further to:

receive a location of the cartridge manifest corresponding to the cartridge that is maintained outside of the multi-tenant PaaS system; and

download, by the processing device of the multi-tenant PaaS system, the cartridge manifest from the received location.

17. The non-transitory machine-readable storage medium of claim 15, wherein the functionality comprising at least one of configuration templates, scripts, dependencies, or features to add to the applications.

18. The non-transitory machine-readable storage medium of claim 15, wherein the cartridge manifest comprises:

a file detailing features of the cartridge; and

fields utilized by the multi-tenant PaaS system to deploy the cartridge to the at least one node.

19. The non-transitory machine-readable storage medium of claim 15, wherein to parse the cartridge manifest the processing device is further to:

locate a source location field of the cartridge manifest; and

determine data of the source location field to indicate the source location of the files of the cartridge, wherein the source location of the files of the cartridge is separate from the multi-tenant PaaS system.

20. The non-transitory machine-readable storage medium of claim 15, wherein the node is a virtual machine (VM) of the virtual environment, the VM hosting the application that requested the cartridge, and wherein the cartridge is executed as part of a gear that comprises a resource-constrained processing space of the VM.