Multiprocessor Programming Toolkit for Design Reuse
US-2024394048-A1 · Nov 28, 2024 · US
US2016124734A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016124734-A1 |
| Application number | US-201414529476-A |
| Country | US |
| Kind code | A1 |
| Filing date | Oct 31, 2014 |
| Priority date | Oct 31, 2014 |
| Publication date | May 5, 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.
In one implementation, a system for a common deployment model includes a content engine to embrace content from a number of deployment tools, a properties engine to associate a number of properties from the content to generate a component model for the number of deployment tools, a cost engine to associate the component model with a cost model, and a fulfillment engine to instantiate the component model with the associated cost model.
Opening claim text (preview).
What is claimed is: 1 . A system for a common deployment model, comprising: a content engine to embrace content from a number of deployment tools; a properties engine to associate a number of properties from the content to generate a component model for the number of deployment tools; a cost engine to associate the component model with a cost model; and a fulfillment engine to instantiate the component model with the associated cost model. 2 . The system of claim 1 , wherein the number of deployment tools comprise deployment tools of platform as a service (PaaS) and software as a service (SaaS). 3 . The system of claim 1 , wherein the fulfillment engine executes a number of services associated with the number of deployment tools utilizing the component model. 4 . The system of claim 3 , wherein the fulfillment engine executes the number of services utilizing a corresponding deployment tool that is associated with the number of services. 5 . The system of claim 1 , wherein the component model is a mapping of execution logic to perform each of a number of services associated with each of the number of deployment tools. 6 . The system of claim 1 , wherein the fulfillment engine retrieves a number of values from a database based on the component model to execute a number of services associated with the number of deployment tools. 7 . The system of claim 1 , wherein the deployment model utilizes a single deployment tool format for the component model. 8 . A non-transitory computer readable medium storing instructions executable by a processing resource to: embrace content from a number of different deployment tools; determine a number of properties from each of the number of different deployment tools; generate a component model for a single deployment tool by associating the number of properties for a number of services; instantiate the component model for the single deployment tool; and execute the number of services via the single deployment tool based on the component model. 9 . The medium of claim 8 , comprising instructions to determine content that corresponds to each of the number of services. 10 . The medium of claim 8 , wherein the content from the number of different deployment tools comprises information for executing the number of services including: a port, a user name, and a password. 11 . The medium of claim 8 , wherein the content from the number of different deployment tools comprises information for executing the number of services including: a corresponding service component, a corresponding platform component, and a corresponding application. 12 . A method for generating a common deployment model, comprising: embracing content from a number of different deployment tools by monitoring a number of services executed by each of the number of different deployment tools; determining a number of properties from each of the number of different deployment tools based on the monitored number of services; generating a component model by associating the number of properties to each of the number of services, wherein the component model is generated for a single deployment tool; and executing the number of services via the single deployment tool based on the component model. 13 . The method of claim 12 , wherein the component model is stored in a database and instantiated to a number of users. 14 . The method of claim 12 , wherein generating the component model comprises generating a component model for a two-tier application with a number of services. 15 . The method of claim 12 , wherein executing the number of services includes executing the number of different deployment tools from the single deployment tool based on the component model.
CAD in a network environment, e.g. collaborative CAD or distributed simulation · CPC title
Software deployment · CPC title
Computer-aided design [CAD] · CPC title
Physics · mapped topic
Related publications grouped by family.
Answers are generated from the same data shown on this page.