Migration of network entities to a cloud infrastructure

US9678803B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9678803-B2
Application numberUS-90564510-A
CountryUS
Kind codeB2
Filing dateOct 15, 2010
Priority dateJun 22, 2007
Publication dateJun 13, 2017
Grant dateJun 13, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A network ontology can be determined for at least one node indicated for migration. The network ontology can describe nodes with which the indicated node has a communication relationship. These nodes and the indicated node can be added to a migration group, and each node of the migration group can be migrated to a cloud infrastructure.

First claim

Opening claim text (preview).

What is claimed is: 1. A method comprising: receiving an indication of at least one node of a plurality of nodes to migrate from an enterprise network to a cloud computing infrastructure, the indicated node comprising a first virtual machine; determining, by a processing device, a network ontology for the indicated node, the network ontology being created for the indicated node using a data collection agent deployed to the indicated node to identify related nodes of the plurality of nodes that have direct and indirect communication relationships with the indicated node, the related nodes comprising the network ontology describing current state of the plurality of nodes and the related nodes, the related nodes comprising a second virtual machine, the network ontology being updated using data collection agents comprised by the plurality of nodes; adding the indicated node and at least one node of the related nodes for the indicated node to a migration group; preparing a migration-configuration file for each node of the migration group, the migration-configuration file comprising service level agreement (SLA) information; deploying a migration agent to each node of the migration group; and migrating the migration group to the cloud computing infrastructure, wherein each node of the migration group is migrated using a corresponding migration-configuration file to generate an SLA for each node of the migration group with a provider of the cloud computing infrastructure in view of SLA information from the corresponding migration configuration file. 2. The method of claim 1 wherein the SLA information in the migration-configuration file specifies a service tier for the respective node. 3. The method of claim 1 wherein the migration-configuration file specifies a network configuration to other nodes of the migration group. 4. The method of claim 1 wherein the migration-configuration file specifies a network configuration to non-migrated members of the network ontology of the indicated node. 5. The method of claim 1 further comprising providing the migration-configuration file to a cloud migration module of a migration agent at the node. 6. The method of claim 1 further comprising determining the migratable components of the ontology of the indicated node. 7. A computer-implemented method comprising: identifying a network ontology describing current state of a plurality of nodes of a network and one or more related nodes with which the plurality of nodes have direct and indirect communication relationships, the network ontology being created by monitoring network connections of the plurality of nodes; determining, based on the network ontology, candidates for migration together to a cloud computing infrastructure, the candidates being one or more of the plurality of nodes and the related nodes and including a first virtual machine and a second virtual machine; displaying the candidates for migration to a user; receiving confirmation that at least one of the candidates is to be added to a migration group; and preparing, by a processing device, a migration-configuration file for each confirmed candidate, the migration-configuration file comprising service level agreement (SLA) information to be used by a migration agent to generate an SLA for each node of the migration group with a provider of the cloud computing infrastructure. 8. The method of claim 7 further comprising: applying one or more criteria to the candidates for migration; ranking the candidates for migration according to the criteria; and displaying the ranking of the candidates for migration to the user. 9. The method of claim 8 wherein the criteria comprise at least one performance parameter. 10. The method of claim 7 wherein the candidates for migration comprise virtual machines of the enterprise network, the method comprising ranking the virtual machines according to at least one performance parameter. 11. The method of claim 7 wherein determining candidates for migration comprises processing the network ontology to determine one or more service groups that comprise virtual machines and no physical machines. 12. The method of claim 7 wherein determining candidates for migration comprises processing the network ontology to determine one or more service groups that comprise virtual machines and physical machines that can be converted to virtual machines. 13. The method of claim 7 wherein determining candidates for migration comprises processing the network ontology to determine one or more service groups that comprise an unreliable network device. 14. The method of claim 7 wherein determining candidates for migration comprises processing the network ontology to determine one or more service groups that comprise devices that have not achieved a configuration drift for a predetermined period. 15. The method of claim 7 further comprising: determining a plurality of service groups of the enterprise network, each service group comprising a plurality of nodes that have a communication relationship; determining a state of the plurality of service groups; ranking the service groups by state; and displaying the ranking of the service groups to a user. 16. The method of claim 15 comprising determining the migratable components of the service group. 17. A system for migration of one or more nodes of an enterprise to a cloud infrastructure, the system comprising: an administration console comprising a memory; and a processor, coupled to the memory, to: receive an indication of at least one node of a plurality of nodes to migrate from an enterprise network to a cloud computing infrastructure, the indicated node comprising a first virtual machine; determine a network ontology for the indicated node of the enterprise network, the network ontology being created for the indicated node using a data collection agent deployed to the indicated node to identify related nodes of the plurality of nodes that have direct and indirect communication relationships with the indicated node, the related nodes comprising the network ontology describing current state of the plurality of nodes and the related nodes, the related nodes comprising a second virtual machine, the network ontology being updated using data collection agents comprised by the plurality of nodes; generate, in view of the network ontology, a migration group comprising the indicated node and at least one node of the related nodes for the indicated node; generate a migration configuration file for each node of the migration group, the migration-configuration file comprising service level agreement (SLA) information; deploy a migration agent to each node of the migration group; migrate the migration group to a cloud infrastructure, wherein each node of the migration group is migrated using a corresponding migration-configuration file to generate an SLA for each node of the migration group with a provider of the cloud computing infrastructure in view of SLA information from the corresponding migration configuration file. 18. The system of claim 17 wherein the network ontology is determined from one or more source-to-destination communication relationships during execution of one or more executables on the at least one node. 19. A non-transitory computer readable medium including instructions that, when executed by a computing device, cause the computing device to perform a method comprising: receiving an indication of at least one node of a plurality of nodes to migrate from an enterprise network to a cloud

Assignees

Inventors

Classifications

  • Assignment of logical groups to network elements · CPC title

  • Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements · CPC title

  • by actively collecting configuration information or by backing up configuration information · CPC title

  • the condition being an adaptation, e.g. in response to network events · CPC title

  • involving task migration · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9678803B2 cover?
A network ontology can be determined for at least one node indicated for migration. The network ontology can describe nodes with which the indicated node has a communication relationship. These nodes and the indicated node can be added to a migration group, and each node of the migration group can be migrated to a cloud infrastructure.
Who is the assignee on this patent?
Suit John M, Red Hat Inc
What technology area does this patent fall under?
Primary CPC classification G06F9/5072. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Jun 13 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).