Cloud application deployment
US-9923952-B2 · Mar 20, 2018 · US
US2016239290A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016239290-A1 |
| Application number | US-201615140142-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 technique for deploying an application in a cloud computing environment includes: collecting, 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 storing the collected metadata and instructions as a model for re-deploying the application.
Opening claim text (preview).
What is claimed is: 1 . A method for deploying an application in a cloud computing environment, the method comprising: collecting, 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 storing the collected metadata and instructions according to an operational order in which the user deploys the application as a model for re-deploying the application in the cloud computing environment. 2 . The method 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 method according to claim 1 , further comprising: preparing services used for deploying the application according to the service metadata and instructions in the model. 4 . The method according to claim 1 , wherein storing the collected metadata and instructions as the model for re-deploying the application comprises at least one of: analyzing the collected metadata and instructions to remove redundant metadata and instructions; storing, according to the operational order in which the user deploys the application, the redundancy-removed metadata and instructions to form the model for re-deploying the application; storing the collected metadata and instructions according to the operational order in which the user deploys the application; analyzing the stored metadata and instructions, and forming from redundancy-removed metadata and instructions the model for re-deploying the application; analyzing the collected metadata and instructions to combine invalid metadata and instructions; storing, 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; storing the collected metadata and instructions according to the operational order in which the user deploys the application; and analyzing the stored metadata and instructions, and combining invalid metadata and instructions to form the model for re-deploying the application. 5 . The method according to claim 1 , further comprising, in response to the user applying to the application which has been deployed a further operation related to the deploying, collecting metadata and instructions involved in the operation and updating 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 method according to claim 3 , further comprising binding the prepared services to the application according to the topology metadata and instructions in the model. 7 . The method according to claim 3 , wherein preparing services used for deploying the application according to the service metadata and instructions in the model comprises preparing 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 method according to claim 6 , wherein binding the prepared services to the application according to the topology metadata and instructions in the model comprises binding 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 method according to claim 3 , wherein preparing services used for deploying the application according to the service metadata and instructions in the model comprises one or a combination of: with respect to a dedicated service, creating a new dedicated service according to the service metadata and instructions in the model; with respect to a shared service, if the shared service already exists, using 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 with respect to an external service reference, creating a new external service reference according to the service metadata and instructions in the model.
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
Retargetable · CPC title
Installation · CPC title
Updates (security arrangements therefor G06F21/57) · CPC title
Software deployment · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.