Extensions for deployment patterns

Patent metadata

Field	Value
Publication number	US-10983774-B2
Application number	US-201916536917-A
Country	US
Kind code	B2
Filing date	Aug 9, 2019
Priority date	Mar 31, 2014
Publication date	Apr 20, 2021
Grant date	Apr 20, 2021

Abstract

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.

First claim

What is claimed is:

1. A method comprising:
detecting an event relating to registration of a component in a deployment pattern;
querying, in response to the event, a tool registry to identify one or more extension deployment patterns for use with one or more core deployment patterns;
retrieving, based upon the query, one or more extension deployment components from a second software repository; and
deploying at least one of the one or more extension deployment components on top of at least one deployed instance of the one or more core deployment patterns, causing monitoring agents to be installed on the respective instances, the monitoring agents being configured to monitor one or more components of the respective instances.

2. The method of claim 1 , the method further comprising:
identifying, automatically, one or more deployed instances of one or more core deployment patterns;
updating, automatically, the tool registry with agent installable files;
accessing, automatically, 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; and
filtering, automatically, 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.

3. The method of claim 2 , 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.

4. The method of claim 2 , 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.

5. The method of claim 1 , wherein the event is the deployment of a core deployment pattern.

6. The method of claim 1 , wherein the event is the registration of a new extension deployment pattern.

7. The method of claim 1 , wherein the event is the registration of a new management tool corresponding to an extension deployment pattern.

8. The method of claim 1 , wherein the extension deployment components include one or more selected from the group consisting of: a virtual machine, a web server, a software application, a software service, a database, and a database management system.

9. A method comprising:
detecting an event relating to a core deployment pattern;
querying, in response to the event, a tool registry to identify one or more extension deployment patterns for use with the core deployment pattern;
retrieving, based upon the query, one or more extension deployment components, the one or more extension deployment components including at least one monitoring component that is configured to monitor a component of the core deployment pattern;
identifying one or more instances of the core deployment pattern that are executing on a computing system; and
deploying 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 the at least one monitoring component to be installed on the respective instances.

10. The method of claim 9 , the method further comprising:
identifying, automatically, one or more deployed instances of one or more core deployment patterns;
updating, automatically, the tool registry with agent installable files;
accessing, automatically, 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; and
filtering, automatically, 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.

11. The method 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.

12. The method 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.

13. The method of claim 9 , wherein the event is the deployment of a core deployment pattern.

14. The method of claim 9 , wherein the event is a registration of a new extension deployment pattern.

15. The method of claim 9 , wherein the event is a registration of a new management tool corresponding to an extension deployment pattern.

16. The method of claim 9 , wherein the extension deployment components include one or more selected from the group consisting of: a virtual machine, a web server, a software application, a software service, a database, and a database management system.

Assignees

• IBM

Inventors

• Giammaria Alberto
• Peters Christopher A
• Spatzier Thomas

Classifications

• G06F9/5061

  Partitioning or combining of resources · CPC title

• G06F9/45558

  Hypervisor-specific management and integration aspects · CPC title

• G06F9/45533

  Hypervisors; Virtual machine monitors · CPC title

• G06F8/75

  Structural analysis for program understanding · CPC title

• G06F8/61

  Installation · CPC title