System and method for placement logic in a cloud platform environment

• US 10,476,760 B2
• Filed: 09/03/2014
• Issued: 11/12/2019
• Est. Priority Date: 10/30/2013
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Mordani, Rajiv, Islam, Nazrul, Saxena, Kshitiz, Thyagarajan, Sivakumar
• Primary Examiner(s): Mundur, Padma
• Application Number:
  US14/476,561
• Publication Number:
  US 20150120937A1
• Time in Patent Office: 1,896 Days
• Field of Search: None
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5041 characterised by the time relationship between creation and deployment of a service
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components

Abstract

In accordance with an embodiment, described herein is a system and method for providing multitenancy support in a platform as a service or cloud computing environment. A platform component enables a service runtime to be shared by multiple tenants, by providing each tenant with a dedicated share or slice of a runtime instance. Each share/slice can be isolated from other shares/slices with respect to factors such as, for example, configuration, or quality of service. In accordance with an embodiment, during provisioning of a particular service runtime, a runtime definition associated with the service runtime can be utilized, for example by a service management engine, to configure the platform component to install one or more services within the service runtime. A particular service and its service runtimes can also be provisioned, within one or more runtime pools, according to a service runtime definition and placement configuration.

Claims

1. A system for providing support in a platform as a service or cloud computing environment for placement logic, comprising:

one or more computers including a processor and memory, and a cloud computing environment executing thereon; and

a platform component, which determines provisioning of enterprise software applications, within the cloud computing environment, including

providing, for each service type of a plurality of service types, a service definition package that provides a definition of the service type,

providing a plurality of service management engines, including for each service type of the plurality of service types, a service management engine that receives placement configurations and provisions service instances of the service type, and

associating each of the plurality of service types, and a plurality of service runtimes, with one or more tags;

wherein a particular service type is associated with a placement configuration that determines a service runtime placement during provisioning of a particular service instance, including

associating a service runtime definition with the particular service instance, as provided by at least one of an administration interface, service management engine associated with the particular service instance, or an external environment configuration,

receiving the placement configuration to be associated with the service management engine associated with the particular service instance,

determining, by the service management engine associated with the particular service instance and the particular service type, which particular service runtime of the plurality of service runtimes is to be used to provision the particular service instance, based on a matching of tags associated with the particular service type and tags associated with the plurality of service runtimes, and

provisioning, by the service management engine associated with the service type, the particular service instance at the particular service runtime, according to the service runtime definition and the placement configuration associated with the particular service instance.

2. The system of claim 1, wherein the placement configuration is associated with the particular service instance, and is used to configure the service management engine (SME) with service runtime placement information, which is then used by the SME to determine which of one or more runtime pools or service runtimes should be used when provisioning the particular service instance.

3. The system of claim 1, wherein a service runtime includes a configurable capacity, which depends on one or more of the hardware capabilities associated with the service runtime, or how many service or provider instances it is capable of holding, and wherein the capacity is considered in creating a service or provider instance.

4. The system of claim 1, wherein services are provisioned for use by tenants, wherein each tenant is associated with at least one of a quota or restrictions with respect to how many service or provider instances they are allowed to create, and wherein such quota or restrictions are taken into account when creating a service or provider instance.

5. The system of claim 1, wherein a service lifecycle manager provides a runtime manager interface that is used to provide configuration of the service runtime definition associated with the particular service type.

6. The system of claim 1, wherein during service type creation, an orchestration engine validates supplied configuration parameters, and invokes a configure type method to enable the service management engine (SME) associated with the particular service type to perform initialization of the service type.

7. The system of claim 1, wherein, based on a configuration associated with the service management engine (SME) associated with the particular service type, the SME determines to create a service instance that has at least one or many runtimes.

8. The system of claim 1,

wherein each particular service management engine, of the plurality of service management engines, is associated with a particular service type, and handles service-related activities for its associated service type;

and

wherein a service management engine is created upon installation of a service definition package for its associated service type.

9. The system of claim 1,

wherein for each service type, of the plurality of service types, the service management engine that is associated with that service type is adapted to receive a placement configuration that configures the service management engine with service runtime placement information;

and

wherein the service runtime placement information determines one or more service runtimes, or service runtime pools, for provisioning instances of the service type.

10. A method of providing support in a platform as a service or cloud computing environment for placement logic, comprising:

providing, at one or more computers, a cloud computing environment executing thereon;

providing, for each service type of a plurality of service types, a service definition package that provides a definition of the service type;

providing a plurality of service management engines, including for each service type of the plurality of service types, a service management engine that receives placement configurations and provisions service instances of the service type;

associating each of the plurality of service types, and a plurality of service runtimes, with one or more tags; and

provisioning enterprise software applications, within the cloud computing environment, including, during provisioning of a particular service instance,

associating a service runtime definition with the particular service instance, as provided by at least one of an administration interface, service management engine associated with the particular service instance, or an external environment configuration,

receiving a placement configuration to be associated with the service management engine associated with the particular service instance,

determining, by the service management engine associated with the particular service instance and a particular service type, which particular service runtime of the plurality of service runtimes is to be used to provision the particular service instance, based on a matching of tags associated with the particular service type and tags associated with the plurality of service runtimes, and

provisioning, by the service management engine associated with the service type, the particular service instance at the particular service runtime, according to the service runtime definition and the placement configuration associated with the particular service instance.

11. The method of claim 10, wherein the placement configuration is associated with the particular service instance, and is used to configure the service management engine (SME) with service runtime placement information, which is then used by the SME to determine which of one or more runtime pools or service runtimes should be used when provisioning the particular service instance.

12. The method of claim 10, wherein a service runtime includes a configurable capacity, which depends on one or more of the hardware capabilities associated with the service runtime, or how many service or provider instances it is capable of holding, and wherein the capacity is considered in creating a service or provider instance.

13. The method of claim 10, wherein services are provisioned for use by tenants, wherein each tenant is associated with at least one of a quota or restrictions with respect to how many service or provider instances they are allowed to create, and wherein such quota or restrictions are taken into account when creating a service or provider instance.

14. The method of claim 10, wherein a service lifecycle manager provides a runtime manager interface that is used to provide configuration of the service runtime definition associated with the particular service type.

15. The method of claim 10, wherein during service type creation, an orchestration engine validates supplied configuration parameters, and invokes a configure type method to enable the service management engine (SME) associated with the particular service type to perform initialization of the service type.

16. The method of claim 10, wherein, based on a configuration associated with the service management engine (SME), the SME determines to create a service that has one runtime, many runtimes, or zero runtimes.

17. A non-transitory computer readable storage medium, including instructions stored thereon which when read and executed by one or more computers cause the one or more computers to perform the steps comprising:

providing a cloud computing environment executing on the one or more computers;

providing, for each service type of a plurality of service types, a service definition package that provides a definition of the service type;

providing a plurality of service management engines, including for each service type of the plurality of service types, a service management engine that receives placement configurations and provisions service instances of the service type;

associating each of the plurality of service types, and a plurality of service runtimes, with one or more tags; and

provisioning enterprise software applications, within the cloud computing environment, including, during provisioning of a particular service instance,

associating a service runtime definition with the particular service instance, as provided by at least one of an administration interface, service management engine associated with the particular service instance, or an external environment configuration,

receiving a placement configuration to be associated with the service management engine associated with the particular service instance,

determining, by the service management engine associated with the particular service instance and a particular service type, which particular service runtime of the plurality of service runtimes is to be used to provision the particular service instance, based on a matching of tags associated with the particular service type and tags associated with the plurality of service runtimes, and

provisioning, by the service management engine associated with the service type, the particular service instance at the particular service runtime, according to the service runtime definition and the placement configuration associated with the particular service instance.

18. The non-transitory computer readable storage medium of claim 17, wherein the placement configuration is associated with the particular service instance, and is used to configure the service management engine (SME) with service runtime placement information, which is then used by the SME to determine which of one or more runtime pools or service runtimes should be used when provisioning the particular service instance.

19. The non-transitory computer readable storage medium of claim 17, wherein a service runtime includes a configurable capacity, which depends on one or more of the hardware capabilities associated with the service runtime, or how many service or provider instances it is capable of holding, and wherein the capacity is considered in creating a service or provider instance.

20. The non-transitory computer readable storage medium of claim 17, wherein services are provisioned for use by tenants, wherein each tenant is associated with at least one of a quota or restrictions with respect to how many service or provider instances they are allowed to create, and wherein such quota or restrictions are taken into account when creating a service or provider instance.