Multi-tenant platform-as-a-service (PaaS) system implemented in a cloud computing environment

Patent metadata

Field	Value
Publication number	US-9330102-B2
Application number	US-201414474694-A
Country	US
Kind code	B2
Filing date	Sep 2, 2014
Priority date	May 1, 2012
Publication date	May 3, 2016
Grant date	May 3, 2016

Abstract

Implementations for providing cartridges in a multi-tenant PaaS system of a cloud computing environment is disclosed. An example method includes maintaining a repository of a plurality of packages that provide functionality for multi-tenant applications executed by a node, each package of the plurality of packages comprising a software and a configuration information specifying a plurality of hooks, receiving a request to configure a first package from the plurality of packages, wherein the first package is to provide functionality for one of the multi-tenant applications, establishing a container to provide process space for the functionality of the first package, calling a configure hook from the plurality of hooks specified in the configuration information of the first package, and in response to calling the configure hook, embedding an instance of the software of the first package in the container, the instance of the software of the first package copied from the repository.

First claim

What is claimed is:

1. A method, comprising:
maintaining, by a processing device of a node, a repository of a plurality of packages that provide functionality for multi-tenant applications executed by the node, each package of the plurality of packages comprised of a software and a configuration information specifying a plurality of hooks;
receiving, by the node, a request to configure a first package from the plurality of packages, wherein the first package is to provide functionality for one of the multi-tenant applications executed by the node;
establishing, by the node, a container to provide process space for the functionality of the first package;
calling, by the node, a configure hook from the plurality of hooks specified in the configuration information of the first package; and
in response to calling the configure hook, embedding, by the node, an instance of the software of the first package in the container, the instance of the software of the first package copied from the repository of the plurality of packages.

2. The method of claim 1 , wherein the plurality of hooks comprise at least one of configure, start, stop, or deconfigure hooks.

3. The method of claim 1 , wherein the establishing the container further comprises:
establishing a unique local user identifier (ID) corresponding to the container;
establishing resource boundaries for the container; and
applying security labels to the container to prevent access to processes of the container from other containers on the node.

4. The method of claim 3 , wherein the establishing the resource boundaries comprises creating at least one of directories and file system locations associated with the container.

5. The method of claim 1 , further comprising calling a deconfigure hook from the plurality of hooks specified in the configuration information of the first package, the deconfigure hook to remove the instance of the software from the container.

6. The method of claim 1 , further comprising calling a start hook from the plurality of hooks specified in the configuration information of the first package, the start hook to start execution of the instance of the software in the container.

7. The method of claim 1 , further comprising calling a stop hook from the plurality of hooks specified in the configuration information of the first package, the stop hook to stop execution of the instance of the software in the container.

8. The method of claim 1 , further comprising:
receiving, by the node, a request to configure a second package from the plurality of packages, wherein the second package is to provide different functionality for the one of the multi-tenant applications executed by the node;
calling, by the node, a configure hook from the plurality of hooks specified in the configuration information of the second package; and
in response to calling the configure hook, embedding, by the node, an instance of the software of the second package in the container, the instance of the software of the second package copied from the repository of the plurality of packages.

9. A system, comprising:
a memory;
a processing device operatively coupled to the memory, wherein the processing device is to:
maintain a repository of a plurality of packages that provide functionality for multi-tenant applications executed by the node, each package of the plurality of packages comprised of a software and a configuration information specifying a plurality of hooks;
receive a request to configure a first package from the plurality of packages, wherein the first package is to provide functionality for one of the multi-tenant applications executed by the node;
establish a container to provide process space for the functionality of the first package;
call a configure hook from the plurality of hooks specified in the configuration information of the first package; and
in response to calling the configure hook, embed an instance of the software of the first package in the container, the instance of the software of the first package copied from the repository of the plurality of packages.

10. The system of claim 9 , wherein the plurality of hooks comprise at least one of configure, start, stop, or deconfigure hooks.

11. The system of claim 9 , wherein the processing device to establish the container further comprises the processing device to:
establish a unique local user identifier (ID) corresponding to the container;
establish resource boundaries for the container; and
apply security labels to the container to prevent access to processes of the container from other containers on the node.

12. The system of claim 11 , wherein the processing device to establish the resource boundaries further comprises the processing device to create at least one of directories and file system locations associated with the container.

13. The system of claim 9 , wherein the processing device is further to call a deconfigure hook from the plurality of hooks specified in the configuration information of the first package, the deconfigure hook to remove the instance of the software from the container.

14. The system of claim 9 , wherein the processing device is further to:
call a start hook from the plurality of hooks specified in the configuration information of the first package, the start hook to start execution of the instance of the software in the container; and
call a stop hook from the plurality of hooks specified in the configuration information of the first package, the stop hook to stop execution of the instance of the software in the container.

15. The system of claim 9 , wherein the processing device is further to:
receive a request to configure a second package from the plurality of packages, wherein the second package is to provide different functionality for the one of the multi-tenant applications executed by the node;
call a configure hook from the plurality of hooks specified in the configuration information of the second package; and
in response to calling the configure hook, embed an instance of the software of the second package in the container, the instance of the software of the second package copied from the repository of the plurality of packages.

16. A non-transitory machine-readable storage medium including instructions that, when accessed by a processing device, cause the processing device to:
maintain, by the processing device of a node, a repository of a plurality of packages that provide functionality for multi-tenant applications executed by the node, each package of the plurality of packages comprised of a software and a configuration information specifying a plurality of hooks;
receive, by the node, a request to configure a first package from the plurality of packages, wherein the first package is to provide functionality for one of the multi-tenant applications executed by the node;
establish, by the node, a container to provide process space for the functionality of the first package;
call, by the node, a configure hook from the plurality of hooks specified in the configuration information of the first package; and
in response to calling the configure hook, embed, by the node, an instance of the software of the first package in the container, the instance of the software of the first package copied from the repository of the plurality of packages.

17. The non-transitory machine -readable storage medium of claim 16 , wherein the plurality of hooks comprise at least one of configure, start, stop, or deconfigure hooks.

18. The non-transitory machine -readable storage mediu

Assignees

• Red Hat Inc

Inventors

• Mcgrath Michael P
• Hicks Matthew

Classifications

• G06F21/53

  by executing in a restricted environment, e.g. sandbox or secure virtual machine · CPC title

• G06F16/116 Primary

  Details of conversion of file system types or formats · CPC title

• H04L63/10

  for controlling access to devices or network resources · CPC title

• G06F9/455 Primary

  Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines · CPC title

• G06F16/13

  File access structures, e.g. distributed indices (arrangements of input from, or output to, record carriers G06F3/06) · CPC title