Template-based configuration architecture
US-9038023-B2 · May 19, 2015 · US
US9934013B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9934013-B2 |
| Application number | US-201414230176-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 31, 2014 |
| Priority date | Mar 31, 2014 |
| 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.
Extension patterns are deployed to core deployment patterns stored in a first software repository. An event relating to registration of a component is detected. In response to detecting the event, a tool registry can be queried to identify one or more extension deployment patterns for use with one or more core deployment patterns. Based upon the query, one or more extension deployment components can be retrieved from a second software repository. The one or more extension deployment components can be deployed on top of one or more instances of the one or more core deployment patterns.
Opening claim text (preview).
What is claimed is: 1. A system for deploying extensions to core deployment patterns stored in a first software repository, the system comprising: at least one computer processor circuit; and at least one computer readable medium storing executable instructions that, when executed, cause the at least one processor circuit to: identify, automatically by a management tool handler, one or more deployed instances of one or more core deployment patterns; detect, automatically by the management tool handler, an event relating to a registration of a component; query, automatically by the management tool handler and in response to the event, a tool registry to identify one or more extension deployment patterns for use with the one or more core deployment patterns; retrieve, automatically by the management tool handler and based upon the query, one or more extension deployment components from a second software repository; access, automatically by the management tool handler, for each of the one or more core deployment patterns, environmental information, the environmental information indicating an environment in which each instance of the one or more core deployment patterns is deployed; filter, automatically by the management tool handler, the one or more extension deployment components based, at least in part, upon the environmental information and metadata of the one or more extension deployment components, wherein the metadata of the one or more extension deployment components indicates one or more environments in which the one or more extension deployment components are configured to be deployed; and deploy, automatically by the management tool handler and in response to the filtering of the extension deployment components, at least one of the one or more extension deployment components on top of one or more instances of the one or more core deployment patterns, causing management agents to be installed on the respective instances. 2. The system of claim 1 , wherein the event is the deployment of a core deployment pattern. 3. The system of claim 1 , wherein the event is the registration of a new extension deployment pattern. 4. The system of claim 1 , wherein the event is the registration of a new management tool corresponding to an extension deployment pattern. 5. The system of claim 1 , wherein the executable instructions, when executed, further cause the at least one processor circuit to access a core deployment pattern from the first software repository using a first interface and accessing an extension deployment pattern from the second software repository using the first interface. 6. The system of claim 1 wherein the executable instructions, when executed, further cause the at least one processor circuit to retrieve, for each of the one or more instances of the one or more core deployment patterns, an Internet Protocol (IP) address and configuration information for ports associated with the IP address. 7. The system of claim 1 , wherein deploying the one or more extension deployment components on top of the one or more deployed instances does not modify an original core deployment patterns. 8. The system of claim 1 , wherein the environment in which each instance of the one or more core deployment patterns is deployed is one of the group consisting of a test environment, a development environment, and a production environment. 9. The system of claim 1 , wherein the one or more deployed instances of one or more core deployment patterns includes a first instance, the first instance being deployed in a test environment, and wherein the filtering the one or more extension deployment components based upon the environmental information and metadata of the one or more extension deployment components includes: identifying a first extension deployment component; determining, based on metadata for the first extension deployment component, that the first extension deployment component should not be deployed in test environments; and removing the first extension deployment component from the one or more extension deployment components to be deployed on top of the first instance. 10. A computer program product for deploying extensions to core deployment patterns stored in a first software repository, the computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions readable by a processor circuit to cause the processor circuit to: identify, automatically by a management tool handler, one or more deployed instances of one or more core deployment patterns; detect, automatically by the management tool handler, an event relating to a registration of a component; query, automatically by the management tool handler and in response to the event, a tool registry to identify one or more extension deployment patterns for use with the one or more core deployment patterns; retrieve, automatically by the management tool handler and based upon the query, one or more extension deployment components from a second software repository; access, automatically by the management tool handler, for each of the one or more core deployment patterns, environmental information, the environmental information indicating an environment in which each instance of the one or more core deployment patterns is deployed; filter, automatically by the management tool handler, the one or more extension deployment components based, at least in part, upon the environmental information and metadata of the one or more extension deployment components, wherein the metadata of the one or more extension deployment components indicates one or more environments in which the one or more extension deployment components are configured to be deployed; and deploy, automatically by the management tool handler and in response to the filtering of the extension deployment components, at least one of the one or more extension deployment components on top of at least one instance of the one or more core deployment patterns, causing management agents to be installed on the respective instances. 11. The computer program product of claim 10 , wherein the event is the deployment of a core deployment pattern. 12. The computer program product of claim 10 , wherein the event is the registration of a new extension deployment pattern. 13. The computer program product of claim 10 , wherein the event is the registration of a new management tool corresponding to an extension deployment pattern. 14. The computer program product of claim 10 , wherein the environment in which each instance of the one or more core deployment patterns is deployed is one of the group consisting of a test environment, a development environment, and a production environment. 15. The computer program product of claim 10 , wherein the one or more deployed instances of one or more core deployment patterns includes a first instance, the first instance being deployed in a test environment, and wherein the filtering the one or more extension deployment components based upon the environmental information and metadata of the one or more extension deployment components includes: identifying a first extension deployment component; determining, based on metadata for the first extension deployment component, that the first extension deployment component should not be deployed in test environments; and removing the first extension deployment component from the one or more extension deployment components to be deployed on top of the first instance. 16. The computer program product of claim 10 , wherein the extension d
Software deployment · CPC title
Search customisation based on user profiles and personalisation · CPC title
Software maintenance or management · CPC title
Version control (security arrangements therefor G06F21/57); Configuration management · CPC title
Physics · mapped topic
Related publications grouped by family.
Answers are generated from the same data shown on this page.