Hybrid cloud environment
US-2015180949-A1 · Jun 25, 2015 · US
US9935825B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9935825-B2 |
| Application number | US-201514859851-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 21, 2015 |
| Priority date | Aug 3, 2015 |
| Publication date | Apr 3, 2018 |
| Grant date | Apr 3, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
This disclosure relates generally to computer resource management over multiple cloud platforms, and more particularly to a system and method for provisioning of application environment and deployment of application across hybrid cloud platform. In one embodiment, a method is provided for provisioning an application environment across a hybrid cloud platform. The method comprises generating a platform independent provisioning template based on at least one of a resource specification and a configuration data. The platform independent provisioning template is compatible with multiple cloud platforms. The method further comprises generating a plurality of target platform artifacts compatible with a corresponding plurality of target cloud platforms based on at least one of the resource specification and the configuration data, associating the plurality of target platform artifacts with the platform independent provisioning template, and provisioning the application environment across the hybrid cloud platform by executing the platform independent provisioning template on each of the plurality of target cloud platforms.
Opening claim text (preview).
What is claimed is: 1. A method for provisioning an application environment across a hybrid cloud platform, the method comprising: generating, via a processor, a platform independent provisioning template based on at least one of a resource specification and a configuration data, the platform independent provisioning template being compatible with multiple cloud platforms, wherein the platform independent provisioning template comprises a unified cloud deployment context (UCDC) template in XML format based on topology and orchestration specification for cloud application (TOSCA) standard; generating, via the processor, a plurality of target platform artefacts compatible with a corresponding plurality of target cloud platforms based on at least one of the resource specification and the configuration data; associating, via the processor, the plurality of target platform artefacts with the platform independent provisioning template; and provisioning, via the processor, the application environment across the hybrid cloud platform by executing the platform independent provisioning template on each of the plurality of target cloud platforms. 2. The method of claim 1 , further comprising acquiring the resource specification from a user. 3. The method of claim 1 , wherein the resource specification comprises at least one of an application specification (AS), a deployment specification (DS), a workflow specification (WS), a computing capacity, a storage capacity, a network requirement, an application executable, an application container, a middleware information, and a database information. 4. The method of claim 1 , further comprising acquiring the configuration data from a configuration database based on the resource specification or acquiring the configuration data from a user. 5. The method of claim 1 , wherein the configuration data comprises at least one of unified resource specifications (URS), target cloud platform specifications (TCPS), and a resource mapping (RM), and wherein the RM is a mapping between the URS and the TCPS. 6. The method of claim 1 , wherein generating the platform independent provisioning template comprises: retrieving an existing platform independent provisioning template based on at least one of the resource specification and the configuration data from a template repository; or creating a new platform independent provisioning template based on at least one of the resource specification and the configuration data, and storing the new platform independent provisioning template in the template repository. 7. The method of claim 1 , wherein the UCDC template comprises UCDC-Service Context (UCDC-SC) section and UCDC-Execution Context (UCDC-EC) section, and wherein UCDC-SC comprises UCDC-Topology Definition (UCDC-TD) and UCDC Workflow Definition (UCDC-WD) for the application environment. 8. The method of claim 1 , wherein each of the plurality of target platform artefacts comprises at least one of a target provisioning template and a target provisioning script. 9. The method of claim 1 , wherein associating the plurality of target platform artefacts comprises capturing information with respect to the plurality of target platform artefacts in the platform independent provisioning template. 10. The method of claim 1 , further comprising: displaying the platform independent provisioning template to a user for committing; and persisting the platform independent provisioning template committed by the user. 11. The method of claim 1 , wherein executing the platform independent provisioning template comprises registering each of the plurality of target platform artefacts with the corresponding plurality of target cloud platforms. 12. The method of claim 1 , wherein executing the platform independent provisioning template comprises: creating an executable platform independent provisioning object from the platform independent provisioning template; loading the executable platform independent provisioning object into a platform independent provisioning container; interpreting a provisioning flow (PF) construct in the executable platform independent provisioning object via the platform independent provisioning container; and executing a provisioning workflow on the plurality of target cloud platforms based on the interpretation using a workflow engine embedded in the platform independent provisioning object. 13. The method of claim 12 , further comprising: updating a provisioning flow status (PFS) construct in the executable platform independent provisioning object after execution of each step in the workflow; and storing the updated executable platform independent provisioning object with a deployment database. 14. The method of claim 1 , further comprising validating if the provisioning is in accordance to topology defined in the platform independent provisioning template. 15. The method of claim 1 , further comprising deploying an application on the application environment across the hybrid cloud platform based on the platform independent provisioning template. 16. The method of claim 15 , wherein deploying the application comprises deploying application components on the plurality of target cloud platforms by: executing a deployment workflow defined in a deployment flow (DF) construct in an executable platform independent provisioning object via a platform independent provisioning container; updating a deployment flow status (DFS) construct in the executable platform independent provisioning object after execution of each step in the workflow; and storing the updated executable platform independent provisioning object with a deployment database. 17. The method of claim 15 , further comprising validating the deployment using the platform independent provisioning template. 18. The method of claim 17 , wherein validating, for each of the plurality of target cloud platforms, comprises: executing a plurality of verification scripts on a target cloud platform, determining if the deployment is successfully completed by validating results of the execution; and triggering a roll back if the deployment is not successfully completed. 19. A system for provisioning an application environment across a hybrid cloud platform, the system comprising: at least one processor; and a computer-readable medium storing instructions that, when executed by the at least one processor, cause the at least one processor to perform operations comprising: generating a platform independent provisioning template based on at least one of a resource specification and a configuration data, the platform independent provisioning template being compatible with multiple cloud platforms, wherein the platform independent provisioning template comprises a unified cloud deployment context (UCDC) template in XML format based on topology and orchestration specification for cloud application (TOSCA) standard; generating a plurality of target platform artefacts compatible with a corresponding plurality of target cloud platforms based on at least one of the resource specification and the configuration data; associating the plurality of target platform artefacts with the platform independent provisioning template; and provisioning the application environment across the hybrid cloud platform by executing the platform independent provisioning template on each of the plurality of target cloud platforms. 20. The system of claim 19 , wherein generating the platform independent provisioning template comprises: retrieving an existin
Hypervisor-specific management and integration aspects · CPC title
for initial configuration or provisioning, e.g. plug-and-play · CPC title
in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title
based on generic templates · CPC title
Installation · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.