Common deployment model

Patent metadata

Field	Value
Publication number	US-9971583-B2
Application number	US-201414529476-A
Country	US
Kind code	B2
Filing date	Oct 31, 2014
Priority date	Oct 31, 2014
Publication date	May 15, 2018
Grant date	May 15, 2018

Abstract

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.

First claim

What is claimed is:

1. A system for a common deployment model, comprising:
a physical processor;
a memory storing machine readable instructions that, when executed by the physical processor, cause the processor to:
embrace content from a number of different deployment tools by monitoring a number of services executed by each of the number of different deployment tools;
determine a number of properties from each of the number of different deployment tools based on the monitored number of services and associate the number of properties to each of the number of services to generate a component model for the number of different deployment tools;
associate the component model with a cost model; and
instantiate the component model with the associated cost model; and
execute the number of services based on the component model.

2. The system of claim 1 , wherein the number of different deployment tools comprises deployment tools of platform as a service (PaaS) and software as a service (SaaS).

3. The system of claim 1 , wherein the number of services is executed utilizing a corresponding deployment tool that is associated with the number of services.

4. The system of claim 1 , wherein the component model is a mapping of execution logic to perform each of the number of services.

5. The system of claim 1 , wherein the number of values is retrieved from a database based on the component model to execute the number of services.

6. The system of claim 1 , wherein the deployment model utilizes a single deployment tool format for the component model.

7. The system of claim 1 , wherein the number of services is executed via a single deployment tool based on 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 by monitoring a number of services executed by each of the number of different deployment tools;
determine a number of properties from each of the number of different deployment tools based on the monitored number of services;
generate a component model for a single deployment tool by associating the number of properties for a number of services;
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. The medium of claim 8 , comprising instructions to instantiate the component model for the single deployment tool.

13. The medium of claim 8 , wherein the number of services is executed by retrieving a number of values from a database based on the component model.

14. 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.

15. The method of claim 14 , wherein the component model is stored in a database and instantiated to a number of users.

16. The method of claim 14 , wherein generating the component model comprises generating a component model for a two-tier application with a number of services.

17. The method of claim 14 , wherein executing the number of services includes executing the number of different deployment tools from the single deployment tool based on the component model.

18. The method of claim 14 , wherein the component model is a mapping of execution logic to perform each of the number of services.

19. The method of claim 14 , 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.

20. The method of claim 14 , wherein the number of services is executed by retrieving a number of values from a database based on the component model.

Assignees

• Hewlett Packard Development Co
• Hewlett Packard Entpr Dev Lp

Inventors

• Dvorak Martin
• Jagannath Kishore
• Suparna Adarsh

Classifications

• G06F2111/02

  CAD in a network environment, e.g. collaborative CAD or distributed simulation · CPC title

• G06F8/60 Primary

  Software deployment · CPC title

• G06F30/00

  Computer-aided design [CAD] · CPC title

• G06F2217/04

  Physics · mapped topic

• G06F17/50

  Physics · mapped topic