System and method for providing a clone service for use with a cloud platform environment

• US 10,452,374 B2
• Filed: 10/15/2014
• Issued: 10/22/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: Sapaliga, Bhavanishankara, Mordani, Rajiv, Islam, Nazrul, Thyagarajan, Sivakumar, Subramanian, Prasad, Evani, Madhavi
• Primary Examiner(s): Bates, Kevin T
• Assistant Examiner(s): McCray, Clarence D
• Application Number:
  US14/515,355
• Publication Number:
  US 20150120889A1
• Time in Patent Office: 1,833 Days
• Field of Search: 709221
• CPC Class Codes: G06F 11/07 Responding to the occurrence of a fault, e.g. fault tolerance
• CPC Class Codes: G06F 11/14 Error detection or correction of the data by redundancy in operation G06F11/16 takes precedence
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/2094 Redundant storage or storage space G06F11/2056 takes precedence
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: H04L 41/0813 characterised by the conditions triggering a change of settings
• CPC Class Codes: H04L 41/0846 based on copy from other elements
• CPC Class Codes: H04L 41/0853 by actively collecting configuration information or by backing up configuration information
• CPC Class Codes: H04L 41/0856 by backing up or archiving configuration information
• CPC Class Codes: H04L 41/5041 characterised by the time relationship between creation and deployment of a service
• CPC Class Codes: H04L 41/5096 wherein the managed service relates to distributed or central networked applications
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

In accordance with an embodiment, described herein is a system and method for providing a clone a service in a cloud platform environment. The system can clone a source service within a service domain or across service domains, by creating a new service from a same service definition package used for creating the source service, extracting post-provision changes from the source service, e.g., user applications and post-provision configurations, and applying the changes to the new service.

Claims

1. A system for providing a clone service in a cloud computing environment, comprising:

one or more computers including a cloud computing environment executing thereon;

a platform component provided within the cloud computing environment, that supports provisioning of applications, including

providing, for each service type of a plurality of service types, a service definition package that is registered by a service definition package manager and enables the cloud computing environment to provide the service type, whereupon the service definition package being installed to the platform component, the service definition package is processed by the service definition package manager that maintains a list of installed service definition packages, and

providing a plurality of service management engines, including, for each service type of the plurality of service types, a service management engine associated with the service type that enables provisioning of a service instance of the service type, wherein the service management engine is incorporated into the platform component by installation and registration of a corresponding service definition package by the service definition package manager; and

a service provider interface that is implemented by one or more service management engines associated with one or more services in the cloud computing environment, to provide service backup and restore functionalities for cloning the one or more services;

wherein during creation of a clone service from a source service associated with a particular service definition package, a service management engine that implements the service provider interface and is associated with the source service creates a service backup of the source service, including post-provision changes made to the source service; and

wherein the service backup is applied to a target service created using the particular service definition package associated with the source service, and the post-provision changes made to the source service, to create the clone service.

2. The system of claim 1, wherein the service backup of the source service includes data and configurations added to the source service after the source service is provisioned, and wherein post-provision changes made to the source service are extracted to a service backup file.

3. The system of claim 1, wherein the target service is in one of a same service domain with the source service, or a different service domain.

4. The system of claim 1, wherein the target service runs on a different virtualization pool from the source service and uses different provider types for various provider dependencies.

5. The system of claim 1, wherein each of the source service and the target service is associated with a service management engine that implements the service provider interface for determining configuration and application changes made to a service after the service is provisioned.

6. The system of claim 1, wherein applying the service backup of the source service includes computing differences between move plans associated with the source service and the target service.

19. The system of claim 1, wherein creation of the clone service includes extracting, from the service backup of the source service, post-provision changes made to the source service within its service domain, which post-provision changes are applied to the target service.

20. The system of claim 1, wherein the service management engine that is associated with the source service is invoked to create the service backup, create the target service, and apply the service backup to the target service.

7. A method for providing a clone service in a cloud computing platform environment, comprising:

providing, at one or more computers including a cloud computing environment executing thereon, a platform component that supports provisioning of applications within the cloud computing environment, including

providing, for each service type of a plurality of service types, a service definition package that is registered by a service definition package manager and enables the cloud computing environment to provide the service type, whereupon the service definition package being installed to the platform component, the service definition package is processed by the service definition package manager that maintains a list of installed service definition packages, and

providing a plurality of service management engines, including, for each service type of the plurality of service types, a service management engine associated with the service type that enables provisioning of a service instance of the service type, wherein the service management engine is incorporated into the platform component by installation and registration of a corresponding service definition package by the service definition package manager; and

providing a service provider interface that is implemented by one or more service management engines associated with one or more services in the cloud computing environment, to provide service backup and restore functionalities for cloning the one or more services;

wherein during creation of a clone service from a source service associated with a particular service definition package, a service management engine that implements the service provider interface and is associated with the source service creates a service backup of the source service, including post-provision changes made to the source service; and

wherein the service backup is applied to a target service created using the particular service definition package associated with the source service, and the post-provision changes made to the source service, to create the clone service.

8. The method of claim 7, wherein the service backup of the source service includes data and configurations added to the source service after the source service is provisioned, and wherein post-provision changes made to the source service are extracted to a service backup file.

9. The method of claim 7, wherein the target service is in one of a same service domain with the source service, or a different service domain.

10. The method of claim 7, wherein the target service runs on a different virtualization pool from the source service and uses different provider types for various provider dependencies.

11. The method of claim 7, wherein each of the source service and the target service is associated with a service management engine that implements the service provider interface for determining configuration and application changes made to a service after the service is provisioned.

12. The method of claim 7, wherein applying the service backup of the source service includes computing differences between move plans associated with the source service and the target service.

13. 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, at one or more computers including a cloud computing environment executing thereon, a platform component that supports provisioning of applications within the cloud computing environment, including

providing, for each service type of a plurality of service types, a service definition package that is registered by a service definition package manager and enables the cloud computing environment to provide the service type, whereupon the service definition package being installed to the platform component, the service definition package is processed by the service definition package manager that maintains a list of installed service definition packages, and

providing a plurality of service management engines, including, for each service type of the plurality of service types, a service management engine associated with the service type that enables provisioning of a service instance of the service type, wherein the service management engine is incorporated into the platform component by installation and registration of a corresponding service definition package by the service definition package manager; and

providing a service provider interface that is implemented by one or more service management engines associated with one or more services in the cloud computing environment, to provide service backup and restore functionalities for cloning the one or more services;

wherein during creation of a clone service from a source service associated with a particular service definition package, a service management engine that implements the service provider interface and is associated with the source service creates a service backup of the source service, including post-provision changes made to the source service; and

wherein the service backup is applied to a target service created using the particular service definition package associated with the source service, and the post-provision changes made to the source service, to create the clone service.

14. The non-transitory computer readable storage medium of claim 13, wherein the service backup of the source service includes data and configurations added to the source service after the source service is provisioned, and wherein post-provision changes made to the source service are extracted to a service backup file.

15. The non-transitory computer readable storage medium of claim 13, wherein the target service is in one of a same service domain with the source service, or a different service domain.

16. The non-transitory computer readable storage medium of claim 13, wherein the target service runs on a different virtualization pool from the source service and uses different provider types for various provider dependencies.

17. The non-transitory computer readable storage medium of claim 13, wherein each of the source service and the target service is associated with a service management engine that implements the service provider interface for determining configuration and application changes made to a service after the service is provisioned.

18. The non-transitory computer readable storage medium of claim 13, wherein applying the service backup of the source service includes computing differences between move plans associated with the source service and the target service.