Management infrastructure analysis for cloud migration

Patent metadata

Field	Value
Publication number	US-9282166-B2
Application number	US-201213689500-A
Country	US
Kind code	B2
Filing date	Nov 29, 2012
Priority date	Nov 29, 2012
Publication date	Mar 8, 2016
Grant date	Mar 8, 2016

Abstract

In a source computing system having a source management infrastructure, at least one source infrastructure management component is discovered. A description of a target cloud infrastructure having a target management infrastructure is obtained. The description includes at least one mandatory target infrastructure management component. The at least one source infrastructure management component is analyzed to determine whether at least one conflict exists with the at least one mandatory target infrastructure management component.

First claim

What is claimed is:

1. A method comprising:
discovering, in a source computing system having a source management infrastructure, at least one source infrastructure management component, wherein said at least one source infrastructure management component is an instance of an image, and wherein said at least one source infrastructure management component is running in a customer environment;
querying a database to obtain a description of a target cloud infrastructure;
analyzing said at least one source infrastructure management component using said description of said target cloud infrastructure to determine that said at least one source infrastructure management component is appropriate for infrastructure configuration mapping to said target cloud infrastructure;
stopping an application executing on said at least one source infrastructure management component determined appropriate for infrastructure configuration mapping; and
capturing said at least one source infrastructure management component determined appropriate for infrastructure configuration mapping for migration to said target cloud infrastructure.

2. The method of claim 1 , wherein, in said discovering step, said at least one source infrastructure management component comprises at least one of:
at least one source infrastructure management client;
at least one source infrastructure management server;
at least one source infrastructure management configuration; and
at least one source infrastructure management log.

3. The method of claim 2 , further comprising deriving a description of non-functional requirements of said source management infrastructure.

4. The method of claim 3 , wherein:
in said discovering step, said at least one source infrastructure management component comprises at least:
said at least one source infrastructure management configuration; and
said at least one source infrastructure management log;

in said querying step, said description of said target cloud infrastructure comprises at least one of:
cloud infrastructure software standards;
cloud infrastructure software configurations; and
a description of non-functional requirements of a target management infrastructure of said target cloud infrastructure;

said analyzing comprises:
matching said cloud infrastructure software standards with at least a corresponding one of:
said at least one source infrastructure management client; and
said at least one source infrastructure management server;

mapping said description of said non-functional requirements of said source management infrastructure with said description of said non-functional requirements of said target management infrastructure; and
mapping said cloud infrastructure software configurations with said at least one source infrastructure management configuration and said at least one source infrastructure management log.

5. The method of claim 4 , wherein said mapping of said cloud infrastructure software configurations with said at least one source infrastructure management configuration and said at least one source infrastructure management log is at least partially based on:
said matching of said cloud infrastructure software standards with said at least one source infrastructure management client and said at least one source infrastructure management server; and
said mapping of said description of said non-functional requirements of said source management infrastructure with said description of said non-functional requirements of said target management infrastructure.

6. The method of claim 5 , wherein:
in said discovering step, said at least one source infrastructure management component further comprises at least one source infrastructure management process;
in said querying step, said description of said target cloud infrastructure further comprises at least one target infrastructure management process; and
said analyzing further comprises mapping said at least one source infrastructure management process with said at least one target infrastructure management process.

7. The method of claim 6 , wherein said mapping of said at least one source infrastructure management process with said at least one target infrastructure management process is at least partially based on said mapping of said description of said non-functional requirements of said source management infrastructure with said description of said non-functional requirements of said target management infrastructure.

8. The method of claim 2 , wherein:
in said querying step, said description of said target cloud infrastructure comprises at least one of:
cloud infrastructure software standards; and
cloud infrastructure software configurations;

said analyzing comprises:
matching said cloud infrastructure software standards with at least a corresponding one of:
said at least one source infrastructure management client; and
said at least one source infrastructure management server; and

mapping said cloud infrastructure software configurations with said at least one source infrastructure management configuration.

9. The method of claim 8 , wherein said mapping of said cloud infrastructure software configurations with said at least one source infrastructure management configuration is at least partially based on said matching of said cloud infrastructure software standards with said at least one source infrastructure management client and said at least one source infrastructure management server.

10. The method of claim 9 , wherein:
in said discovering step, said at least one source infrastructure management component further comprises at least one source infrastructure management process;
in said querying step, said description of said target cloud infrastructure further comprises at least one target infrastructure management process; and
said analyzing further comprises mapping said at least one source infrastructure management process with said at least one target infrastructure management process.

11. The method of claim 1 , wherein said analyzing step further comprises determining that at least one conflict exists with said at least one mandatory target infrastructure management component, wherein said at least one conflict comprises said at least one source infrastructure management component managing at least one object that said at least one mandatory target infrastructure management component will manage in said target cloud infrastructure.

12. The method of claim 1 , wherein said analyzing step further comprises determining that at least one conflict exists with said at least one mandatory target infrastructure management component, wherein said at least one conflict comprises said at least one source infrastructure management component using at least one resource that said at least one mandatory target infrastructure management component will use in said target cloud infrastructure.

13. The method of claim 1 , wherein said analyzing step further comprises determining that at least one conflict exists with said at least one mandatory target infrastructure management component, wherein said at least one conflict comprises at least one of:
current lack of a mandatory target infrastructure component on a client,
existence of a mandatory target infrastructure component in a different version, and
existence of a mandatory target infrastructure component with different configurations.

14. The method of claim 1 , wherein said analyzing comprises at least one of:
recommending un-installation of a source infrastructure component;
recommending installation of a target infrastructure component;
recommending modifying con

Assignees

• IBM

Inventors

• Markley Matthew A
• Paradkar Amitkumar M
• Parisa Venkata Vinay
• Pfitzmann Birgit M

Classifications

• H04L41/12

  Discovery or management of network topologies · CPC title

• H04L41/045

  comprising client-server management architectures · CPC title

• H04L67/34 Primary

  involving the movement of software or configuration parameters  (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title

• H04W4/003

  Electricity · mapped topic

• H04L67/1002

  Electricity · mapped topic