Cloud application deployment
US-9923952-B2 · Mar 20, 2018 · US
US2016239294A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016239294-A1 |
| Application number | US-201615140102-A |
| Country | US |
| Kind code | A1 |
| Filing date | Apr 27, 2016 |
| Priority date | Jun 26, 2013 |
| Publication date | Aug 18, 2016 |
| Grant date | — |
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.
A system and technique for deploying an application in a cloud computing environment includes: a collecting module executable by a processor unit to collect, while a user is deploying an application, metadata and instructions issued by the user on deploying the application, the metadata comprising service metadata, application metadata and topology metadata, wherein the service metadata comprise metadata on a service required for deploying the application, the application metadata comprise metadata on the application, and the topology metadata comprise metadata indicative of a relationship between the service and the application; and a storing module executable by the processor unit to store the collected metadata and instructions as a model for re-deploying the application.
Opening claim text (preview).
What is claimed is: 1 . A system for deploying an application in a cloud computing environment, the system comprising: a collecting module executable by a processor of the system to collect, while a user is deploying an application in the cloud computing environment, metadata and instructions issued by the user on deploying the application, the metadata comprising service metadata, application metadata and topology metadata, wherein the service metadata comprise metadata on a service required for deploying the application, the application metadata comprise metadata on the application, and the topology metadata comprise metadata indicative of a relationship between the service and the application; and a storing module executable by the processor to store, according to an operational order in which the user deploys the application, the collected metadata and instructions as a model for re-deploying the application in the cloud computing environment. 2 . The system according to claim 1 , wherein: the service metadata comprise one or a combination of: a type of the service, a name of the service, an ID of the service, a version of the service and a configuration of the service; the application metadata comprise one or a combination of: a type of the application, a name of the application, an ID of the application and a configuration of the application; and the topology metadata comprise one or a combination of: an ID of the application, an ID of the service, a name of the application, a name of the service, a binding configuration and a binding policy. 3 . The system according to claim 1 , wherein the storing module is operable to store, according to an operational order in which the user deploys the application, the collected metadata and instructions to form the model for re-deploying the application. 4 . The system according to claim 1 , wherein the storing module comprises: a first removing sub-module operable to analyze the collected metadata and instructions, remove redundant metadata and instructions, and store, according to an operational order in which the user deploys the application, the redundancy-removed metadata and instructions to form the model for re-deploying the application; a second removing sub-module operable to store the collected metadata and instructions according to the operational order in which the user deploys the application, analyze the stored metadata and instructions, and form from redundancy-removed metadata and instructions the model for re-deploying the application; a first combining sub-module operable to analyze the collected metadata and instructions, combine invalid metadata and instructions, and store, according to the operational order in which the user deploys the application, the combined metadata and instructions to form the model for re-deploying the application; and a second combining sub-module operable to store the collected metadata and instructions according to the operational order in which the user deploys the application, analyze the stored metadata and instructions, and combine invalid metadata and instructions to form the model for re-deploying the application. 5 . The system according to claim 1 , further comprising an updating module executable by the processor unit to, in response to the user applying to the application which has been deployed a further operation related to the deploying, collect metadata and instructions involved in the operation and update to the model the metadata and instructions involved in the operation, wherein the metadata involved in the operation comprise at least one of service metadata involved in the operation, application metadata involved in the operation and topology metadata involved in the operation. 6 . The system according to claim 1 , further comprising a serving module executable by the processor unit to prepare services used for deploying the application according to the service metadata and instructions in the model. 7 . The system according to claim 6 , wherein the serving module is further operable to prepare services used for deploying the application according to the service metadata and instructions in the model and in an order of the instructions in the model. 8 . The system according to claim 7 , further comprising a binding module executable by the processor unit to: bind the prepared services to the application according to the topology metadata and instructions in the model; and bind the prepared services to the application according to the topology metadata and instructions in the model and in an order of the instructions in the model. 9 . The system according to claim 6 , wherein the serving module comprises one or a combination of: a dedicated sub-module operable to, with respect to a dedicated service, create a new dedicated service according to the service metadata and instructions in the model; a shared sub-module operable to, with respect to a shared service, if the shared service already exists, use the existing shared service, if the shared service does not exist, creating a new shared service according to the service metadata and instructions in the model; and an external sub-module operable to, with respect to an external service reference, create a new external service reference according to the service metadata and instructions in the model. 10 . A computer program product for deploying an application in a cloud computing environment, the computer program product comprising: a non-transitory computer readable medium having computer readable program code embodied therewith, the computer readable program code comprising computer readable program code configured to: collect, while a user is deploying an application in the cloud computing environment, metadata and instructions issued by the user on deploying the application, the metadata comprising service metadata, application metadata and topology metadata, wherein the service metadata comprise metadata on a service required for deploying the application, the application metadata comprise metadata on the application, and the topology metadata comprise metadata indicative of a relationship between the service and the application; and store, according to an operational order in which the user deploys the application, the collected metadata and instructions as a model for re-deploying the application in the cloud computing environment. 11 . The computer program product of claim 10 , wherein: the service metadata comprise one or a combination of: a type of the service, a name of the service, an ID of the service, a version of the service and a configuration of the service; the application metadata comprise one or a combination of: a type of the application, a name of the application, an ID of the application and a configuration of the application; and the topology metadata comprise one or a combination of: an ID of the application, an ID of the service, a name of the application, a name of the service, a binding configuration and a binding policy. 12 . The computer program product of claim 10 , wherein the computer readable program code is configured to store, according to an operational order in which the user deploys the application, the collected metadata and instructions to form the model for re-deploying the application. 13 . The computer program product of claim 10 , wherein the computer readable program code is configured to: analyze the collected metadata and instructions, remove redundant metadata and instructions, and store, according to an operational order in which the user deploys the application, the redundancy-removed metadata and instruct
for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title
in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title
Software deployment · CPC title
Retargetable · CPC title
Installation · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.