Connect public, paid and private patent data with Google Patents Public Datasets

Virtual machine migration in a network

Info

Publication number
WO2014141007A1
WO2014141007A1 PCT/IB2014/059460 IB2014059460W WO2014141007A1 WO 2014141007 A1 WO2014141007 A1 WO 2014141007A1 IB 2014059460 W IB2014059460 W IB 2014059460W WO 2014141007 A1 WO2014141007 A1 WO 2014141007A1
Authority
WO
Grant status
Application
Patent type
Prior art keywords
network
controller
switch
storage
server
Prior art date
Application number
PCT/IB2014/059460
Other languages
French (fr)
Inventor
Casimer Decusatis
Rajaram Krishnamurthy
Original Assignee
International Business Machines Corporation
Ibm United Kingdom Limited
Ibm (China) Investment Company Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/34Network-specific arrangements or communication protocols supporting networked applications involving the movement of software or configuration parameters
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for programme control, e.g. control unit
    • G06F9/06Arrangements for programme control, e.g. control unit using stored programme, i.e. using internal store of processing equipment to receive and retain programme
    • G06F9/44Arrangements for executing specific programmes
    • G06F9/455Emulation; Software simulation, i.e. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/10Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for programme control, e.g. control unit
    • G06F9/06Arrangements for programme control, e.g. control unit using stored programme, i.e. using internal store of processing equipment to receive and retain programme
    • G06F9/44Arrangements for executing specific programmes
    • G06F9/455Emulation; Software simulation, i.e. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/4557Distribution of virtual machine instances; Migration and load balancing aspects

Abstract

A method for migrating virtual machines (VMs) that includes creating a temporary storage area. The temporary storage area is created by a controller in a network that is in a first state. The configuration data for a VM is stored in the temporary storage area. The network is provisioned from the first state to a second state. The provisioning is by the controller and based on network locations of a source server and a target server. A message is transmitted to the target server. The message includes a request to migrate the VM from the source server to the target server, and an address of the temporary storage area. It is determined that the migration has completed and the temporary storage area is removed based on the determining that the migrant has completed.

Description

VIRTUAL MACHINE MIGRATION IN A NETWORK

TECHNICAL FIELD

[0001] The present invention relates generally to computer networks and, more specifically, to migrating virtual machines in a network.

BACKGROUND

[0002] Ethernet networks are typically employed in local area networks (LANs) that include a plurality of network switches. A number of communication protocols have been developed and continue to evolve to enhance Ethernet network performance for various environments. For example, an enhancement to Ethernet, called data center bridging (DCB), converged enhanced Ethernet (CEE) or data center Ethernet (DCE), supports the

convergence of LANs with storage area networks (SANs). Other protocols that can be used in a data center environment in conjunction with Ethernet include, for instance, Fibre Channel over Ethernet (FCoE), Internet Wide Area Remote direct memory access Protocol (iWARP), Remote direct memory access over Converged Ethernet (RoCE).

[0003] Virtual machines (VMs) are often migrated within a data center from one processor to another processor in order, for example, to take advantage of unused processing cycles or other resources.

SUMMARY

[0004] Aspects of the invention include a method, computer program product and system for migrating virtual machines (VMs). The method includes creating a temporary storage area. The temporary storage area is created by a controller in a network that is in a first state. The configuration data for a VM is stored in the temporary storage area. The network is provisioned from the first state to a second state. The provisioning is by the controller and based on network locations of a source server and a target server. A message is transmitted to the target server. The message includes a request to migrate the VM from the source server to the target server, and an address of the temporary storage area. It is determined that the migration has completed and the temporary storage area is removed based on the determining that the migrant has completed.

[0005] Additional features and advantages are realized through the techniques of the present invention. Other embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed invention. For a better understanding of the invention with the advantages and the features, refer to the description and to the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Embodiment s) of the invention will now be described, by way of example only, with reference to the accompanying drawings in which:

FIG. 1 depicts a block diagram of a system including a network with OpenFlow-capable switches that may be implemented according to an embodiment;

FIG. 2 depicts a block diagram of an OpenFlow-capable switch according to an

embodiment;

FIG. 3 depicts an example of an OpenFlow flow switching definition that can be used in embodiments;

FIG. 4 depicts an exemplary embodiment of a portion of a network including a network switch, a network controller, and two servers; and

FIG. 5 is a flow diagram showing a virtual machine migration in a network in accordance with an embodiment.

DETAILED DESCRIPTION

[0007] Exemplary embodiments relate to migrating virtual machines (VMs) in a network. Embodiments described herein are directed to a process in an OpenFlow network for migrating a VM between a first host machine on which the VM is running and a second host machine. The process may include an OpenFlow controller within the OpenFlow network creating a mobility storage area within the OpenFlow controller for storing configuration data of the VM. The OpenFlow network may be provisioned from a first state to a second state, for migration of the VM to a second host. The provisioning may include determining the minimum number of paths (and identifying them by path identifiers) between the VM and the second host machine and reserving switch resources having the highest quality of service (QoS) and lowest available latency along those paths for the VM. A migration request with the identifiers of the paths from the first host machine to the second host machine may be transmitted. Responsive to receiving the migration request, the second host machine may read the configuration data of the VM. The migration of the VM to the second host machine may be completed by returning the network provisioning to its first state and destroying the mobility storage area in the controller.

[0008] Embodiments described herein are contrasted with contemporary methods of performing VM migration which include storing configuration data to a storage device, such as a direct access storage device (DASD) which is shared by multiple users. Reading and writing to storage devices requires more resources than reading and writing to the mobility storage area described herein. Storage devices are not located within the network (e.g., on the controller, on a switch) and therefore standard input/output (I/O) operations (e.g., via a storage controller on a processor) are required to access the configuration data; this takes longer than accessing the mobility storage area which is in the network. In addition, having the storage devices shared by multiple users may have an adverse impact on the speed that the configuration data may be accessed (e.g., written, read). In general, because of the storage capacity of a typical storage device and the relatively small size of configuration data for a VM it is not cost effective to have an entire storage device or channel dedicated to a VM migration. Embodiments described herein may be utilized to perform a VM migration that uses a dedicated (i.e., not shared with other users) temporary storage area located on a network element that is sized based on a current VM being migrated in order to provide an efficient and cost effective VM migration process.

[0009] Turning now to FIG. 1, an example of a system 100 including a network 101 that supports OpenFlow will now be described in greater detail. In the example depicted in FIG. 1, the system 100 is a data center environment including a plurality of servers 102 and client systems 104 configured to communicate over the network 101 using switches 106 that are OpenFlow-capable. In exemplary embodiments, the servers 102, also referred as hosts or host systems, are high-speed processing devices (e.g., mainframe computers, desktop computers, laptop computers, hand-held devices, embedded computing devices, or the like) including at least one processing circuit (e.g., a computer processor/CPU) capable of reading and executing instructions, and handling interactions with various components of the system 100. The servers 102 may be storage system servers configured to access and store large amounts of data to one or more data storage systems 108. In an embodiment, a VM is migrated from one server 102 (referred to herein as a "source server") to another server 102 (referred to herein as a "target server").

[0010] The client systems 104 can include a variety of desktop, laptop, general-purpose computer devices, mobile computing devices, and/or networked devices with processing circuits and input/output (I/O) interfaces, such as keys/buttons, a touch screen, audio input, a display device and audio output. The client systems 104 can be linked directly to one or more of the switches 106 or wirelessly through one or more wireless access points 110.

[0011] The data storage systems 108 refer to any type of computer readable storage media and may include one or more secondary storage elements, e.g., hard disk drive (HDD), solid-state memory, tape, or a storage subsystem that is internal or external to the servers 102. Types of data that may be stored in the data storage systems 108 include, for example, various files and databases. There may be multiple data storage systems 108 utilized by each of the servers 102, which can be distributed in various locations of the system 100.

[0012] The system 100 also includes a network controller 112 that is a central software defined network controller configured to make routing decisions within the network 101. The network controller 112 establishes one or more secure links 103 to configure the switches 106 and establish communication properties of links 105 between the switches 106. For example, the network controller 112 can configure the switches 106 to control packet routing paths for data flows between the servers 102 and client systems 104, as well as one or more firewalls 114 and one or more load balancers 116. The one or more firewalls 114 restrict access and the flow of network traffic between the network 101 and one or more external networks 118. The one or more load balancers 116 can distribute workloads across multiple computers, such as between the servers 102.

[0013] The servers 102, client systems 104, and network controller 112 can include various computer/communication hardware and software technology known in the art, such as one or more processing units or circuits, volatile and non- volatile memory including removable media, power supplies, network interfaces, support circuitry, operating systems, and the like. Although the network controller 112 is depicted as a separate component, it will be understood that network configuration functionality can alternatively be implemented in one or more of the servers 102 or client systems 104 in a standalone or distributed format.

[0014] The network 101 can include a combination of wireless, wired, and/or fiber optic links. The network 101 as depicted in FIG. 1 represents a simplified example for purposes of explanation. Embodiments of the network 101 can include numerous switches 106 (e.g., hundreds) with dozens of ports and links per switch 106. The network 101 may support a variety of known communication standards that allow data to be transmitted between the servers 102, client systems 104, switches 106, network controller 112, firewalls(s) 114, and load balancer(s) 116. Communication protocols are typically implemented in one or more layers, such as a physical layer (layer-1), a link layer (layer-2), a network layer (layer-3), a transport layer (layer-4), and an application layer (layer-5). In exemplary embodiments, the network 101 supports OpenFlow as a layer-2 protocol. The switches 106 can be dedicated OpenFlow switches or OpenFlow-enabled general purpose switches that also support layer-2 and layer-3 Ethernet.

[0015] FIG. 2 depicts a block diagram of the switch 106 of FIG. 1 that supports

OpenFlow. The switch 106 includes switch logic 202, secure channel 204, protocol support 205, flow table 206, input/output buffers 208a-208n, port queues 209a-209n and ports 210a- 21 On. The switch logic 202 may be implemented in one or more processing circuits, where a computer readable storage medium is configured to hold instructions for the switch logic 202, as well as various variables and constants to support operation of the switch 106. The switch logic 202 forwards packets between the ports 210a-210n as flows defined by the network controller 112 of FIG. 1. [0016] The secure channel 204 connects the switch 106 to the network controller 112 of FIG. 1. The secure channel 204 allows commands and packets to be communicated between the network controller 112 and the switch 106 via the OpenFlow protocol. The secure channel 204 can be implemented in software as executable instructions stored within the switch 106. Protocol details to establish a protocol definition for an implementation of OpenFlow and other protocols can be stored in the protocol support 205. The protocol support 205 may be software that defines one or more supported protocol formats. The protocol support 205 can be embodied in a computer readable storage medium, for instance, flash memory, which is configured to hold instructions for execution by the switch logic 202. Implementing the protocol support 205 as software enables updates in the field for new versions or variations of protocols and can provide OpenFlow as an enhancement to existing conventional routers or switches.

[0017] The flow table 206 defines supported connection types associated with particular addresses, virtual local area networks or switch ports, and is used by the switch to process data flows received at the switch. A data flow is a sequence of data packets grouped in some manner, e.g., by source and/or destination, or otherwise defined by selected criteria. Each data flow may be mapped to a port and associated queue based on the flow table 206. For example, a data flow is defined as all packets that match a particular header format.

[0018] Each entry 211 in the flow table 206 can include one or more rules 212, actions 214, and statistics 216 associated with a particular flow. The rules 212 define each flow, i.e., the packets that are part of the flow, and can be determined by packet headers. The actions 214 define how packets are processed. The statistics 216 track information such as the size of each flow (e.g., number of bytes), the number of packets for each flow, and time since the last matching packet of the flow or connection time. Examples of actions include

instructions for forwarding packets of a flow to one or more specific ports 210a-210n (e.g., unicast or multicast), encapsulating and forwarding packets of a flow to the network controller 112 of FIG. 1, and dropping packets of the flow. Entries 211 in the flow table 206 can be added and removed by the network controller 112 of FIG. 1 via the secure channel 204. The network controller 112 of FIG. 1 can pre-populate the entries 211 in the flow table 206. Additionally, the switch 106 can request creation of an entry 211 from the network controller 112 upon receiving a flow without a corresponding entry 211 in the flow table 206.

[0019] The buffers 208a-208n provide temporary storage in respective queues 209a- 209n for flows as packets are sent between the ports 210a-210n. In a lossless configuration, rather than dropping packets when network congestion is present, the buffers 208a-208n temporarily store packets in the respective queues 209a-209n until the associated ports 210a- 21 On and links 105 of FIG. 1 are available. Each of the buffers 208a-208n may be associated with a particular port, flow, or sub-network. Each of the buffers 208a-208n is logically separate but need not be physically independent. Accordingly, when one of the buffers 208a-208n is full, it does not adversely impact the performance of the other buffers 208a-208n within the switch 106. Counters may be maintained for each queue and port.

[0020] For example, in an OpenFlow switch, each port 210a-210n is attached to a respective queue 209a-209n. In operation, when the switch 106 receives a packet, the switch 106 attempts to match the packet by comparing fields (referred to as "match fields") to corresponding fields in flow entries of each flow table 206. Exemplary match fields include ingress port and metadata fields, as well as header fields such as those described below in reference to FIG. 3. In one embodiment, matching starts at the first flow table and may continue to additional flow tables.

[0021] If no match is found, the switch 106 may perform an action based on the switch configuration, e.g., the packet may be forwarded to the controller or dropped. If the packet matches a flow entry in a flow table, the corresponding instruction set is executed based on the flow entry, e.g., the actions field 214. For example, when a packet is matched to a flow entry including an output action, the packet is forwarded to one of ports 210a-210n specified in the flow entry.

[0022] In one embodiment, forwarding the packet to a port includes mapping packets in a flow to a queue attached to the port. Such flows are treated according to the queue's configuration (e.g., minimum rate). [0023] FIG. 3 depicts an example of an OpenFlow flow switching definition 300 that can be used in embodiments. The OpenFlow flow switching definition 300 is a packet header that defines the flow and includes a number of fields. In this example, the switching definition 300 is a flow header that includes up to eleven tuples or fields; however, not all tuples need to be defined depending upon particular flows. In the example of FIG. 3, the OpenFlow flow switching definition 300 includes tuples for identifying an ingress port 302, an Ethernet destination address 304, an Ethernet source address 306, an Ethernet type 308, a virtual local area network (VLAN) priority 310, a VLAN identifier 312, an Internet protocol (IP) source address 314, an IP destination address 316, an IP protocol 318, a transmission control protocol (TCP) / user datagram protocol (UDP) source port 320, and a TCP/UDP destination port 322. The Ethernet destination address 304 may represent a layer-2 Ethernet hardware address or media access control (MAC) address used in legacy switching and routing. The IP destination address 316 may represent a layer-3 IP address used in legacy switching and routing. Flow switching can be defined for any combination of tuples in the OpenFlow flow switching definition 300, with a particular combination of tuples serving as a key. For example, flows can be defined in a rule 212 of FIG. 2 by exact matching or wildcard matching for aggregated MAC-subnets, IP-subnets, ports, VLAN identifiers, and the like.

[0024] FIG. 4 depicts a block diagram of a network portion 400. In the embodiment shown in FIG. 4, a source server 402a is coupled by a link 404a to a switch 406, and a target server 402b in coupled by a link 404b to the switch 406. An exemplary source server 402a and target server 402b is a server 102 of FIG. 1, and an exemplary switch 406 is a switch 106 of FIG. 1. A controller 408 (e.g., a network controller) is linked to the switch 406 by, e.g., a secure link 410. In one embodiment, in OpenFlow-capable environments, the controller is a network controller such as network controller 112 of FIG. 1. In other embodiments, for non-OpenFlow environments, functions of the controller 408 can be integrated into other network entities such as the source server 402a, the target server 402b, or server 102. Although only a single switch 406 is shown in the embodiment of FIG. 4, it is to be understood that the switch 406 may be a plurality of switches connected, e.g., to a central controller 408. [0025] As shown in FIG. 4, the switch 406 is connected to the source server 402a and target server 402b, which both include at least one port 412a 412b and various logical components such as mode selection logic 414a 414b, wait pulse repetition time 416a 416b, and protocol and mode of operation configuration 418a 418b. Logical components described herein can be implemented in instructions stored in a computer readable storage medium for execution by a processing circuit or in hardware circuitry, and can be configured to send frames such as link initialization frames and data packets. The switch 406, source server 402a, target server 402b, and controller 408 may support a number of modes of operation including, but not limited to, Ethernet, Fibre Channel, Fibre Channel over Ethernet (FCoE), Internet Wide Area Remote direct memory access Protocol (iWARP), and Remote direct memory access over Converged Ethernet (RoCE).

[0026] The switch 406 includes switch logic 420, flow table 422, protocol support 424, port configuration and reset logic 425 and multiple ports, such as port 426 for

communicating with the source server 402a and port 428 for communicating with the target server 402b, as well as other ports for communication with other network entities such as other switches or servers. The ports may be physical ports, virtual ports defined by the switch, and/or a virtual port defined by the OpenFlow protocol. Each port is attached or connected to a queue that holds data packets for a data flow when there is an imbalance between input rates and output rates of the data flow through the switch. For example, port 26 is attached to a queue 427 and port 428 is attached to a queue 429. When implemented as an OpenFlow switch, the switch 406 also includes a secure channel 430 for communicating with the network controller 408 on secure link 410.

[0027] The network controller 408 includes an action table 432 that holds port and protocol information for one or more switches, such as the switch 406 and/or the switches 106, as well as rules, actions, and statistics for flows through the switch 406 and other switches, such as switches 106 of FIG. 1. The network controller 408 also includes flow control logic including VM migration logic 434 that can be implemented in instructions stored in a computer readable storage medium for execution by a processing circuit or in hardware circuitry. The network controller 408 can manage updates of the flow table 422 in the switch 406. Based on the updating of the flow table 422, the port and protocol information in the action table 432 of the network controller 408 is updated to reflect the changes.

[0028] As indicated above, the network controller 408 communicates with the switch 406 via a secure link 410 established using a specified port, such as a port in a physical network controller 112 or a controller implemented in other processors, such as a server 102 or client system 104. The network controller 408 communicates with the switch 406 to configure and manage the switch, receive events from the switch and send packets out the switch. Various message types can be sent between the switch and the controller to accomplish such functions, including controller-to-switch, asynchronous and symmetric messages.

[0029] Controller-to-switch messages are initiated by the controller 408 and may or may not require a response from the switch 406. Features messages are used to request the capabilities of the switch 406 (e.g., upon establishment of the secure link), in response to which the switch 406 should return a features reply that specifies the capabilities of the switch 406. Configuration messages are sent by the controller 408 to set and query configuration parameters in the switch 406. The switch 406 only responds to a query from the controller 408. Modify- State messages are sent by the controller 408 to manage state on the switches, e.g., to add/delete and/or modify flows/groups in the flow table 422 and to set switch port properties. Read-State messages are used by the controller to collect statistics from the switch. Packet-out messages are used by the controller to send packets out of a specified port on the switch, and to forward packets received via Packet-in messages.

Packet-out messages contain a full packet or a buffer ID referencing a packet stored in the switch. Packet-out messages also contain a list of actions to be applied in the order they are specified; an empty action list drops the packet.

[0030] Asynchronous messages are sent without the controller 408 soliciting them from the switch 406. The switch 406 sends asynchronous messages to the controller 408 to, e.g., denote a packet arrival, switch state change, or error. A packet-in event message may be sent to the controller 408 from the switch 406 for packets that do not have a matching flow entry, and may be sent from the controller 408 to the switch 406 for packets forwarded to the controller 408. Flow-removed messages are used to indicate that a flow entry has been removed due to, e.g., inactivity or expiration of the flow entry. Port-status messages are sent in response to changes in port configuration state and port status events. Error messages may be used by the switch 406 to notify the controller 408 of problems.

[0031] Symmetric messages are sent without solicitation, in either direction. Hello messages may be exchanged between the switch 406 and controller 408 upon connection startup. Echo request/reply messages can be sent from either the switch 406 or the controller 408, and can be used to measure the latency or bandwidth of a controller-switch connection, as well as verify its liveness. Experimenter messages provide a way for the switch 406 to offer additional functionality within the OpenFlow message type space.

[0032] An embodiment of the controller 408 includes VM migration logic 434 and a mobility storage area (MSA) 436 for implementing the VM migration process described herein. The MSA 436 is also referred to herein as a "temporary storage area." In an embodiment, the VM 440 in the source server 402a is migrated to the target server 402b. Though shown in FIG. 4 as being located on the controller 408, the MSA 436 may alternatively be located in the network on other network elements, such as the switch 406. In addition, the MSA 436 may be implemented by physical and/or virtual computer storage or memory. In an embodiment, the MSA 436 is created in response to instructions from the controller 408. The controller 408 may determine the size of the MSA based on the amount of space required to store the configuration data for the VM 440 being migrated. The controller 408 may perform the VM migration functions described herein in parallel for a plurality of switches.

[0033] The VM configuration data includes a set of attributes that defines the VM 440. Configuration data may include, but is not limited to: a number of dedicated processing cycles required, storage requirements, virtual I/O IP addresses (e.g., of an Ethernet card), shared storage location addresses, and information about applications to be executed on the VM 404, and/or applications to be executed on the VM 404. [0034] In an embodiment, the controller 408 initiates a migration of the VM 440 from the source server 402a to the target server 402b. The VM migration logic 434 builds the MSA 436, determines a path from the source server 402a to the target server 402b, provisions the network based on the path, and the instructs the target server 402b to complete the migration. Once the migration is complete, the VM migration logic deletes the MSA 436 and un-provisions the network (e.g., breaks down the provisioned path from the source server 402a to the target server 402b, and returns to the network to a prior state).

[0035] FIG. 5 is a flow diagram showing a VM migration in a network in accordance with an embodiment. The processing shown in FIG. 5 may be performed by the VM migration logic 434 on the controller 408. At the start of the process shown in FIG. 5, the network is provisioned in a first state and a request to migrate a VM 440 from a source server 402a to a target server 402b is received. At block 502, a MSA 436 is created for storing configuration data related to the VM 440 being migrated. The MSA 436 is a temporary storage area dedicated to the migration of the VM 440 and it may be sized based on the amount of space required to store the configuration data for the VM 440. In an embodiment, the network is a software defined network such as an OpenFlow network. The MSA 436 may be located on any network element such as a controller 112 408 (as shown in FIG. 4) or a switch 106 406 in the network.

[0036] Referring now to block 504, the configuration data for the VM 440 is stored into the MSA 436. The network is provisioned by the controller 408 at block 506, going from the first state (prior to the migration) to a second state to support the migration. The network provisioning may be based on a variety of factors such as, but not limited to, the network locations of the source server 402a and the target server 402b, the size of the MSA 436, available bandwidth in the network, capacity of switches, and a specified quality of service. At block 508, a message is transmitted to the target server 402b telling the target server 402b of the planned migration of the VM 440. The message may include the address of the MSA 436 and network path identifiers (e.g., identifying switches) corresponding to the network provisioned at block 506. The processing at block 510 may be performed by software located on (or accessed by) the target server 402b and it includes reading the configuration data for the VM 440 from the MSA 436. The target server 402b may use the provisioned network path as defined by the network path identifiers to access the configuration data in the MSA 436. In an embodiment, the configuration data includes enough information for the target server 402b to execute the VM 440.

[0037] Once the target server 402b is executing the VM, the target server 402b may send a message back to the controller 408 indicting that the migration is complete. In response to receiving the notification, the VM migration logic 434 on the controller may remove (destroy) the MSA 436 and break down the network path built at block 506. The network may then move from the second state built at block 506 back to the first state or to some other state. Block 512 may also be performed if the controller 408 is notified that the migration has failed. In an embodiment, a retry of the migration would start at block 502.

[0038] As described herein, an OpenFlow controller may own the MSA 436 including such functions as create, resize, destroy, set time to live, and purge on link failure. The VM migration logic 434 is an example of a new OpenFlow primitive that may: provision the network for VM transfer, including functions such as reserving switch resources with a highest QoS and lowest available latency; send a VM mobility request to a recipient (e.g., target server 402b) including network path identifiers; provision the network to carry the VM to the destination (e.g., the target server 402b) to allow it to read the VM 440 directly from the MSA 436; and return the network to its prior state.

[0039] As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit," "module" or "system." Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.

[0040] Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible and non-transitory storage medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0041] A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

[0042] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0043] Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0044] Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[0045] These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

[0046] The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[0047] The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

[0048] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms

"comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one more other features, integers, steps, operations, element components, and/or groups thereof.

[0049] The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated [0050] The flow diagrams depicted herein are just one example. There may be many variations to this diagram or the steps (or operations) described therein without departing from the spirit of the invention. For instance, the steps may be performed in a differing order or steps may be added, deleted or modified. All of these variations are considered a part of the claimed invention.

[0051] While the preferred embodiment to the invention had been described, it will be understood that those skilled in the art, both now and in the future, may make various improvements and enhancements which fall within the scope of the claims which follow. These claims should be construed to maintain the proper protection for the invention first described.

Claims

1. A method for migrating virtual machines ' VMs', the method comprising:
creating, by a controller in a network, a temporary storage area, the network in a first state;
storing, in a temporary storage area, configuration data for a VM;
provisioning, by the controller, the network from the first state to a second state, based on network locations of a source server and a target server;
transmitting a message to the target server, the message including:
a request to migrate the VM from the source server to the target server; and an address of the temporary storage area;
determining that the migration has completed; and
removing the temporary storage area based on the determining.
2. The method of claim 1, further comprising provisioning the network from the second state back to the first state based on the determining.
3. The method of claim 1 or claim 2, wherein the migration includes reading, by the target server, the configuration data stored in the temporary storage area.
4. The method of any preceding claim, wherein the network is an OpenFlow network.
5. The method of any preceding claim, wherein the temporary storage area is located on the controller.
6. The method of any of claims 1 to 4, wherein the temporary storage area is located on a switch in the network.
7. The method of any preceding claim, wherein the provisioning is further based on at least one of a size of the configuration data, available bandwidth in the network, and a specified quality of service.
8. The method of any preceding claim, wherein application information associated with the VM is also stored in the temporary storage area and migrated to the target server.
9. A computer program product for migrating virtual machines 'VMs', the computer program product comprising a storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing the method of any preceding claim.
10. A system for migrating virtual machines 'VMs' in a network, the system comprising:
a controller configured to connect to the network, the controller comprising:
a memory having computer readable computer instructions; and
a processor for executing the computer readable instructions to:
create a temporary storage area, wherein the network is in a first state;
store configuration data for a VM, the storing in the temporary storage area;
provision the network from the first state to a second state, the provisioning based on network locations of a source server and a target server;
transmit a message to the target server, the message including:
a request to migrate the VM from the source server to the target server; and an address of the temporary storage area;
determine that the migration has completed; and
remove the temporary storage area based on the determining.
11. The system of claim 10, further executing instructions to provision the network from the second state back to the first state based on the determining.
12. The system of claim 10 or claim 11, wherein the migration includes reading, by the target server, the configuration data stored in the temporary storage area.
13. The system of any of claims 10 to 12, wherein the network is an OpenFlow network.
14. The system of any of claims 10 to 13, wherein the temporary storage area is located on the controller.
15. The system of any of claims 10 to 13, wherein the temporary storage area is located on a switch in the network.
16. The system of any of claims 10 to 15, wherein the provisioning is further based on at least one of a size of the configuration data, available bandwidth in the network, and a specified quality of service.
17. The system of any of claims 10 to 16, wherein application information associated with the VM is also stored in the temporary storage area and migrated to the target server.
PCT/IB2014/059460 2013-03-15 2014-03-05 Virtual machine migration in a network WO2014141007A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US13834502 US9609086B2 (en) 2013-03-15 2013-03-15 Virtual machine mobility using OpenFlow
US13/834,502 2013-03-15

Publications (1)

Publication Number Publication Date
WO2014141007A1 true true WO2014141007A1 (en) 2014-09-18

Family

ID=51533431

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2014/059460 WO2014141007A1 (en) 2013-03-15 2014-03-05 Virtual machine migration in a network

Country Status (2)

Country Link
US (2) US9609086B2 (en)
WO (1) WO2014141007A1 (en)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8863141B2 (en) 2011-12-14 2014-10-14 International Business Machines Corporation Estimating migration costs for migrating logical partitions within a virtualized computing environment based on a migration cost history
US9712431B2 (en) * 2013-07-17 2017-07-18 Kt Corporation Methods for managing transaction in software defined network
CN104572274A (en) * 2013-10-18 2015-04-29 宇宙互联有限公司 Cross-cloud-node migration system and cross-cloud-node migration method
US9491031B2 (en) * 2014-05-06 2016-11-08 At&T Intellectual Property I, L.P. Devices, methods, and computer readable storage devices for collecting information and sharing information associated with session flows between communication devices and servers
JP2015215799A (en) * 2014-05-12 2015-12-03 富士通株式会社 Control device, communication device and communication method
US20150326425A1 (en) * 2014-05-12 2015-11-12 Ntt Innovation Institute, Inc. Recording, analyzing, and restoring network states in software-defined networks
US20160142648A1 (en) * 2014-11-18 2016-05-19 Branch Media Labs, Inc. Seamless setup and control for home entertainment devices and content
US20160196158A1 (en) * 2014-12-31 2016-07-07 Vmware, Inc. Live migration of virtual machines across virtual switches in virtual infrastructure
EP3046028A1 (en) * 2015-01-15 2016-07-20 Alcatel Lucent Load-balancing and scaling of cloud resources by migrating a data session
CN104954261B (en) * 2015-05-26 2018-01-16 上海斐讯数据通信技术有限公司 Flow table using the method and system for forwarding data
US9438478B1 (en) * 2015-11-13 2016-09-06 International Business Machines Corporation Using an SDN controller to automatically test cloud performance

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070204266A1 (en) * 2006-02-28 2007-08-30 International Business Machines Corporation Systems and methods for dynamically managing virtual machines
CN101313278A (en) * 2005-12-02 2008-11-26 国际商业机器公司 Maintaining session states within virtual machine environments
CN101398770A (en) * 2007-09-30 2009-04-01 赛门铁克公司 System for and method of migrating one or more virtual machines
CN101677321A (en) * 2008-09-16 2010-03-24 株式会社日立制作所 Method and apparatus for storage migration

Family Cites Families (163)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3187230B2 (en) 1993-09-06 2001-07-11 株式会社東芝 Congestion control method and congestion control device
JP3686493B2 (en) 1996-03-07 2005-08-24 富士通株式会社 Feedback control method and apparatus in Atm exchanger
US5905711A (en) 1996-03-28 1999-05-18 Lucent Technologies Inc. Method and apparatus for controlling data transfer rates using marking threshold in asynchronous transfer mode networks
GB9610337D0 (en) 1996-05-17 1996-07-24 Motorola Ltd Method and apparatus for transmitting data
US6504821B2 (en) 1996-06-12 2003-01-07 At&T Corp. Flexible bandwidth negotiation for the block transfer of data
US5966546A (en) 1996-09-12 1999-10-12 Cabletron Systems, Inc. Method and apparatus for performing TX raw cell status report frequency and interrupt frequency mitigation in a network node
JPH10271132A (en) 1997-03-27 1998-10-09 Toshiba Corp Flow control system for packet exchange network
US6356944B1 (en) 1997-03-31 2002-03-12 Compaq Information Technologies Group, L.P. System and method for increasing write performance in a fibre channel environment
EP0876023A1 (en) 1997-04-30 1998-11-04 Sony Corporation Transmitter and transmitting method, receiver and receiving method, and transceiver and transmitting/receiving method
WO1999030462A3 (en) 1997-12-12 1999-09-02 3Com Corp A forward error correction system for packet based real-time media
US6570876B1 (en) 1998-04-01 2003-05-27 Hitachi, Ltd. Packet switch and switching method for switching variable length packets
FR2782218B1 (en) 1998-08-06 2002-05-17 Alsthom Cge Alkatel Call routing with overflows in a private network
WO2000013379A1 (en) 1998-08-31 2000-03-09 Fujitsu Limited Service assigning apparatus
US6795399B1 (en) 1998-11-24 2004-09-21 Lucent Technologies Inc. Link capacity computation methods and apparatus for designing IP networks with performance guarantees
US6504818B1 (en) 1998-12-03 2003-01-07 At&T Corp. Fair share egress queuing scheme for data networks
US6529301B1 (en) 1999-07-29 2003-03-04 Nortel Networks Limited Optical switch and protocols for use therewith
US6990606B2 (en) 2000-07-28 2006-01-24 International Business Machines Corporation Cascading failover of a data management application for shared disk file systems in loosely coupled node clusters
US6975592B1 (en) 2000-11-22 2005-12-13 Nortel Networks Limited Configurable rule-engine for layer-7 and traffic characteristic-based classification
US6947380B1 (en) 2000-12-01 2005-09-20 Cisco Technology, Inc. Guaranteed bandwidth mechanism for a terabit multiservice switch
US7072297B2 (en) 2001-04-30 2006-07-04 Networks Physics, Inc. Method for dynamical identification of network congestion characteristics
US8160020B2 (en) 2001-06-25 2012-04-17 Airvana Network Solutions, Inc. Radio network control
US7305492B2 (en) 2001-07-06 2007-12-04 Juniper Networks, Inc. Content service aggregation system
US7171124B2 (en) 2001-07-19 2007-01-30 Lucent Technologies Inc. Wavelength routing and switching mechanism for a photonic transport network
US6922791B2 (en) 2001-08-09 2005-07-26 Dell Products L.P. Failover system and method for cluster environment
EP1324628B1 (en) 2001-12-13 2009-11-11 Sony Deutschland GmbH Adaptive quality-of-service reservation and pre-allocation for mobile systems
US7187652B2 (en) 2001-12-26 2007-03-06 Tropic Networks Inc. Multi-constraint routing system and method
US7408876B1 (en) 2002-07-02 2008-08-05 Extreme Networks Method and apparatus for providing quality of service across a switched backplane between egress queue managers
US7024580B2 (en) 2002-11-15 2006-04-04 Microsoft Corporation Markov model of availability for clustered systems
US8161145B2 (en) 2003-02-27 2012-04-17 International Business Machines Corporation Method for managing of denial of service attacks using bandwidth allocation technology
US20040179476A1 (en) 2003-03-10 2004-09-16 Sung-Ha Kim Apparatus and method for controlling a traffic switching operation based on a service class in an ethernet-based network
US7746816B2 (en) 2003-03-13 2010-06-29 Qualcomm Incorporated Method and system for a power control in a communication system
US7379996B2 (en) * 2003-04-07 2008-05-27 Microsoft Corporation System and method for web server migration
US7336605B2 (en) 2003-05-13 2008-02-26 Corrigent Systems, Inc. Bandwidth allocation for link aggregation
US7234073B1 (en) 2003-09-30 2007-06-19 Emc Corporation System and methods for failover management of manageable entity agents
JP4556592B2 (en) 2003-10-02 2010-10-06 パナソニック株式会社 Router selection method and router device
WO2005106546A3 (en) 2004-04-15 2006-05-11 Infinera Corp COOLERLESS AND FLOATING WAVELENGTH GRID PHOTONIC INTEGRATED CIRCUITS (PICs) FOR WDM TRANSMISSION NETWORKS
US7460468B2 (en) 2004-04-22 2008-12-02 At&T Intellectual Property I, L.P. Method and system for automatically tracking the rerouting of logical circuit data in a data network
JP4353005B2 (en) 2004-06-29 2009-10-28 株式会社日立製作所 System switching method of cluster configuration computer system
US20060209695A1 (en) 2005-03-15 2006-09-21 Archer Shafford R Jr Load balancing in a distributed telecommunications platform
DE102004057496B4 (en) 2004-11-29 2006-08-24 Siemens Ag Method and device for the automatic readjustment of limits for access controls for restricting the traffic in a communication network
US7626926B2 (en) 2004-12-09 2009-12-01 Airvana, Inc. Traffic management in a wireless data network
US20060187874A1 (en) 2005-02-24 2006-08-24 Interdigital Technology Corporation Method and apparatus for supporting data flow control in a wireless mesh network
US9185036B2 (en) 2005-03-23 2015-11-10 Alcatel Lucent Method and apparatus for flow control of data in a network
US7961621B2 (en) 2005-10-11 2011-06-14 Cisco Technology, Inc. Methods and devices for backward congestion notification
KR100757872B1 (en) 2006-02-06 2007-09-11 삼성전자주식회사 Apparatus and method of backward congestion notification on network
US8042108B2 (en) * 2006-03-18 2011-10-18 International Business Machines Corporation Virtual machine migration between servers
US7496579B2 (en) 2006-03-30 2009-02-24 International Business Machines Corporation Transitioning of database service responsibility responsive to server failure in a partially clustered computing environment
US8509077B2 (en) 2006-04-05 2013-08-13 Xyratex Technology Limited Method for congestion management of a network, a switch, and a network
US7843831B2 (en) 2006-08-22 2010-11-30 Embarq Holdings Company Llc System and method for routing data on a packet network
US8369821B2 (en) 2006-09-08 2013-02-05 Logicmark, Llc List-based emergency calling device
US20080137669A1 (en) 2006-12-12 2008-06-12 Nokia Corporation Network of nodes
EP1936880A1 (en) 2006-12-18 2008-06-25 British Telecommunications Public Limited Company Method and system for congestion marking
JP5168699B2 (en) 2007-02-06 2013-03-21 エントロピック・コミュニケーションズ・インコーポレイテッドEntropic Communications, Inc. Parameterized quality of service architecture in the network
US8116200B2 (en) 2007-03-16 2012-02-14 Cisco Technology, Inc. Source routing approach for network performance and availability measurement of specific paths
US7864771B2 (en) 2007-04-20 2011-01-04 Cisco Technology, Inc. Parsing out of order data packets at a content gateway of a network
US20080298248A1 (en) 2007-05-28 2008-12-04 Guenter Roeck Method and Apparatus For Computer Network Bandwidth Control and Congestion Management
US8400912B2 (en) 2007-06-27 2013-03-19 World Wide Packets, Inc. Activating a tunnel upon receiving a control packet
US8121038B2 (en) 2007-08-21 2012-02-21 Cisco Technology, Inc. Backward congestion notification
EP2028798B1 (en) 2007-08-22 2012-05-02 Telefonaktiebolaget L M Ericsson (publ) Data transmission control methods and devices
US20100214970A1 (en) 2007-09-28 2010-08-26 Nec Europe Ltd Method and system for transmitting data packets from a source to multiple receivers via a network
CN101849391B (en) 2007-11-01 2012-10-10 艾利森电话股份有限公司 Efficient flow control in a radio network controller (RNC)
US7773519B2 (en) 2008-01-10 2010-08-10 Nuova Systems, Inc. Method and system to manage network traffic congestion
US7876751B2 (en) 2008-02-21 2011-01-25 International Business Machines Corporation Reliable link layer packet retry
GB0803788D0 (en) 2008-02-29 2008-04-09 Kelly Francis P Network communication
US7843817B2 (en) 2008-03-11 2010-11-30 Cisco Technology, Inc. Congestion control in wireless mesh networks
CN101534519B (en) 2008-03-14 2014-03-12 摩托罗拉移动公司 Method for displaying package switching congestion state of wireless communication network
US7949893B1 (en) 2008-04-30 2011-05-24 Netapp, Inc. Virtual user interface failover
GB2461132B (en) 2008-06-27 2013-02-13 Gnodal Ltd Method of data delivery across a network
US8045463B2 (en) 2008-07-30 2011-10-25 Microsoft Corporation Path estimation in a wireless mesh network
US8102781B2 (en) * 2008-07-31 2012-01-24 Cisco Technology, Inc. Dynamic distribution of virtual machines in a communication network
ES2332397B1 (en) 2008-08-01 2011-02-09 Telefonica, S.A. Access point sends information geographic positioning access point to mobile terminals and mobile terminal receiving said information and estimates its position based on it.
US7978607B1 (en) 2008-08-29 2011-07-12 Brocade Communications Systems, Inc. Source-based congestion detection and control
JP5232602B2 (en) 2008-10-30 2013-07-10 株式会社日立製作所 Storage device, and data paths of the storage controller internal network failover method
JP4648447B2 (en) 2008-11-26 2011-03-09 株式会社日立製作所 Failure recovery method, program and management server
JP4727714B2 (en) 2008-12-05 2011-07-20 株式会社日立製作所 Control method and apparatus for server failover, as well as the computer system unit
US8897139B2 (en) 2008-12-05 2014-11-25 Hewlett-Packard Development Company, L.P. Packet processing indication
EP2200229B1 (en) 2008-12-18 2012-03-07 Alcatel Lucent Method and apparatus for delivering error-critical traffic through a packet-switched network
US8990801B2 (en) * 2009-01-30 2015-03-24 Hewlett-Packard Development Company, L.P. Server switch integration in a virtualized system
US8285900B2 (en) 2009-02-17 2012-10-09 The Board Of Regents Of The University Of Texas System Method and apparatus for congestion-aware routing in a computer interconnection network
WO2010107350A1 (en) 2009-03-20 2010-09-23 Telefonaktiebolaget Lm Ericsson (Publ) Method and devices for automatic tuning in wdm-pon
US20120030306A1 (en) * 2009-04-28 2012-02-02 Nobuharu Kami Rapid movement system for virtual devices in a computing system, management device, and method and program therefor
US8429287B2 (en) 2009-04-29 2013-04-23 Rangecast Technologies, Llc Network audio distribution system and method
WO2010138545A1 (en) 2009-05-27 2010-12-02 Yin Zhang Method and system for resilient routing reconfiguration
US8774411B2 (en) 2009-05-29 2014-07-08 Alcatel Lucent Session key generation and distribution with multiple security associations per protocol instance
US8238234B2 (en) 2009-06-03 2012-08-07 Qualcomm Incorporated Switching between MIMO and receiver beam forming in a peer-to-peer network
US8385231B2 (en) 2009-07-30 2013-02-26 Roberto Rojas-Cessa Disseminating link state information to nodes of a network
US20110031082A1 (en) 2009-08-06 2011-02-10 Chen-Lung Chi Wheeled luggage device with brake
WO2011019992A1 (en) 2009-08-13 2011-02-17 New Jersey Institute Of Technology Scheduling wdm pon with tunable lasers with different tuning times
CN101997644A (en) 2009-08-24 2011-03-30 华为技术有限公司 Speed adjusting method, system and coding scheme selection method and system thereof
CN104065555A (en) 2009-09-24 2014-09-24 日本电气株式会社 Identification System For Inter-virtual-server Communication And Identification Method For Inter-virtual-server Communication
JP5446040B2 (en) 2009-09-28 2014-03-19 日本電気株式会社 Computer system, and the migration process of the virtual machine
WO2011040511A1 (en) 2009-09-30 2011-04-07 日本電気株式会社 Billing processing system, network switch, network management server, billing processing method, and billing processing program
EP2484146B1 (en) 2009-10-01 2017-12-06 LG Electronics Inc. Method of controlling data flow in wireless communication system
US8780721B2 (en) 2009-10-06 2014-07-15 Nec Corporation Network system, controller, method, and program
US20110085444A1 (en) 2009-10-13 2011-04-14 Brocade Communications Systems, Inc. Flow autodetermination
WO2011049135A1 (en) 2009-10-23 2011-04-28 日本電気株式会社 Network system, control method thereof, and controller
US20120250496A1 (en) 2009-11-26 2012-10-04 Takeshi Kato Load distribution system, load distribution method, and program
US20110299389A1 (en) 2009-12-04 2011-12-08 Telcordia Technologies, Inc. Real Time Monitoring, Onset Detection And Control Of Congestive Phase-Transitions in Communication Networks
US20110137772A1 (en) 2009-12-07 2011-06-09 At&T Mobility Ii Llc Devices, Systems and Methods for SLA-Based Billing
US20110135301A1 (en) 2009-12-08 2011-06-09 Vello Systems, Inc. Wavelocker for Improving Laser Wavelength Accuracy in WDM Networks
US8270831B2 (en) 2009-12-11 2012-09-18 Cisco Technology, Inc. Use of pre-validated paths in a WDM network
WO2011074630A1 (en) 2009-12-17 2011-06-23 日本電気株式会社 Load distribution system, load distribution method, device and program constituting load distribution system
WO2011080870A1 (en) 2009-12-28 2011-07-07 日本電気株式会社 Communications system and port information collection method
WO2011083682A1 (en) 2010-01-05 2011-07-14 日本電気株式会社 Switch network system, controller, and control method
WO2011087085A1 (en) 2010-01-14 2011-07-21 日本電気株式会社 Calculator, network connection switching method, and program
US8429651B2 (en) * 2010-01-20 2013-04-23 International Business Machines Corporation Enablement and acceleration of live and near-live migration of virtual machines and their associated storage across networks
JP5521614B2 (en) 2010-02-15 2014-06-18 日本電気株式会社 Network system, and the packet speculative transfer method
EP2466823A3 (en) 2010-12-15 2013-10-02 Juniper Networks, Inc. Methods and apparatus for automatically provisioning resources within a distributed control plane of a switch
WO2011118575A1 (en) 2010-03-24 2011-09-29 日本電気株式会社 Communication system, control device and traffic monitoring method
US8538327B2 (en) 2010-04-15 2013-09-17 Alcatel Lucent User equipment adjustment of uplink satellite communications
US20110261696A1 (en) 2010-04-22 2011-10-27 International Business Machines Corporation Network data congestion management probe system
DE102010017935A1 (en) 2010-04-22 2011-10-27 Siemens Aktiengesellschaft Apparatus and method for stabilizing an electricity purchases
US8537846B2 (en) 2010-04-27 2013-09-17 Hewlett-Packard Development Company, L.P. Dynamic priority queue level assignment for a network flow
US8504718B2 (en) 2010-04-28 2013-08-06 Futurewei Technologies, Inc. System and method for a context layer switch
US8503307B2 (en) 2010-05-10 2013-08-06 Hewlett-Packard Development Company, L.P. Distributing decision making in a centralized flow routing system
EP2572473B1 (en) 2010-05-19 2014-02-26 Telefonaktiebolaget L M Ericsson (PUBL) Methods and apparatus for use in an openflow network
US8224957B2 (en) 2010-05-20 2012-07-17 International Business Machines Corporation Migrating virtual machines among networked servers upon detection of degrading network link operation
US8559332B2 (en) 2010-05-25 2013-10-15 Telefonaktiebolaget L M Ericsson (Publ) Method for enhancing table lookups with exact and wildcards matching for parallel environments
US9535762B2 (en) 2010-05-28 2017-01-03 At&T Intellectual Property I, L.P. Methods to improve overload protection for a home subscriber server (HSS)
WO2011155392A1 (en) 2010-06-07 2011-12-15 日本電気株式会社 Congestion control system, congestion control method and signalling device
US8737405B2 (en) 2010-06-11 2014-05-27 Marvell World Trade Ltd. Method and apparatus for determining channel bandwidth
US8995836B2 (en) 2010-07-13 2015-03-31 Futurewei Technologies, Inc. Passive optical network with adaptive filters for upstream transmission management
US8456984B2 (en) 2010-07-19 2013-06-04 Ciena Corporation Virtualized shared protection capacity
WO2012011467A1 (en) 2010-07-20 2012-01-26 シャープ株式会社 Data distribution system, data distribution method, data relay device on distribution side, and data relay device on reception side
JP5846199B2 (en) 2010-09-03 2016-01-20 日本電気株式会社 Controller, a communication system, a communication method, and communication program
US8929218B2 (en) 2010-09-10 2015-01-06 Brocade Communication Systems, Inc. Congestion notification across multiple layer-2 domains
RU2576480C2 (en) 2010-10-28 2016-03-10 Нек Корпорейшн Network system and communication traffic control method
US20120155468A1 (en) 2010-12-21 2012-06-21 Microsoft Corporation Multi-path communications in a data center environment
US8842536B2 (en) 2010-12-23 2014-09-23 Brocade Communications Systems, Inc. Ingress rate limiting
JP5538257B2 (en) 2011-02-02 2014-07-02 アラクサラネットワークス株式会社 Bandwidth monitoring device, and the packet relay apparatus
US8467294B2 (en) 2011-02-11 2013-06-18 Cisco Technology, Inc. Dynamic load balancing for port groups
WO2012127894A1 (en) 2011-03-18 2012-09-27 日本電気株式会社 Network system, and switching method
US8429282B1 (en) 2011-03-22 2013-04-23 Amazon Technologies, Inc. System and method for avoiding system overload by maintaining an ideal request rate
EP2689562B1 (en) 2011-03-24 2017-05-03 Nec Corporation Method for operating a flow-based switching system and switching system
US9608908B2 (en) 2011-03-29 2017-03-28 Nec Corporation Network system and VLAN tag data acquiring method
US9231876B2 (en) 2011-03-29 2016-01-05 Nec Europe Ltd. User traffic accountability under congestion in flow-based multi-layer switches
US9590922B2 (en) 2011-05-12 2017-03-07 Microsoft Technology Licensing, Llc Programmable and high performance switch for data center networks
US8923294B2 (en) 2011-06-28 2014-12-30 Polytechnic Institute Of New York University Dynamically provisioning middleboxes
US8964563B2 (en) 2011-07-08 2015-02-24 Telefonaktiebolaget L M Ericsson (Publ) Controller driven OAM for OpenFlow
CN102291389A (en) 2011-07-14 2011-12-21 南京邮电大学 A satellite network congestion control method of cross-layer
US8762501B2 (en) 2011-08-29 2014-06-24 Telefonaktiebolaget L M Ericsson (Publ) Implementing a 3G packet core in a cloud computer with openflow data and control planes
JP5915454B2 (en) 2011-09-01 2016-05-11 富士通株式会社 Network system
US8630307B2 (en) 2011-09-13 2014-01-14 Qualcomm Incorporated Methods and apparatus for traffic contention resource allocation
JP5937806B2 (en) 2011-11-10 2016-06-22 株式会社Nttドコモ Mobile communication method, the policy and charging rules server apparatus and a mobile management node
US8953453B1 (en) 2011-12-15 2015-02-10 Amazon Technologies, Inc. System and method for throttling service requests using work-based tokens
US8971338B2 (en) 2012-01-09 2015-03-03 Telefonaktiebolaget L M Ericsson (Publ) Expanding network functionalities for openflow based split-architecture networks
US8868735B2 (en) 2012-02-02 2014-10-21 Cisco Technology, Inc. Wide area network optimization
US8862744B2 (en) 2012-02-14 2014-10-14 Telefonaktiebolaget L M Ericsson (Publ) Optimizing traffic load in a communications network
WO2013134937A1 (en) 2012-03-14 2013-09-19 华为技术有限公司 Method, switch, server, and system for transmitting an establish connection request
US9350671B2 (en) 2012-03-22 2016-05-24 Futurewei Technologies, Inc. Supporting software defined networking with application layer traffic optimization
JP2013207748A (en) 2012-03-29 2013-10-07 Fujitsu Ltd Network system ad node device
US8730806B2 (en) 2012-04-03 2014-05-20 Telefonaktiebolaget L M Ericsson (Publ) Congestion control and resource allocation in split architecture networks
US9013995B2 (en) 2012-05-04 2015-04-21 Telefonaktiebolaget L M Ericsson (Publ) Congestion control in packet data networking
US20140006630A1 (en) 2012-06-28 2014-01-02 Yigang Cai Session initiation protocol (sip) for message throttling
US20140040526A1 (en) 2012-07-31 2014-02-06 Bruce J. Chang Coherent data forwarding when link congestion occurs in a multi-node coherent system
US9210079B2 (en) * 2012-08-14 2015-12-08 Vmware, Inc. Method and system for virtual and physical network integration
US9548920B2 (en) 2012-10-15 2017-01-17 Cisco Technology, Inc. System and method for efficient use of flow table space in a network environment
US8995277B2 (en) 2012-10-30 2015-03-31 Telefonaktiebolaget L M Ericsson (Publ) Method for dynamic load balancing of network flows on LAG interfaces
US9301029B2 (en) 2012-11-05 2016-03-29 Broadcom Corporation Data rate control in an optical line terminal
US9094126B2 (en) 2012-11-07 2015-07-28 Nec Laboratories America, Inc. QoS-aware united control protocol for optical burst switching in software defined optical networks
US8976697B2 (en) 2012-12-17 2015-03-10 Broadcom Corporation Network status mapping
US20140198648A1 (en) 2013-01-15 2014-07-17 Cisco Technology, Inc. Identification of data flows based on actions of quality of service policies
US9769074B2 (en) 2013-03-15 2017-09-19 International Business Machines Corporation Network per-flow rate limiting

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101313278A (en) * 2005-12-02 2008-11-26 国际商业机器公司 Maintaining session states within virtual machine environments
US20070204266A1 (en) * 2006-02-28 2007-08-30 International Business Machines Corporation Systems and methods for dynamically managing virtual machines
CN101398770A (en) * 2007-09-30 2009-04-01 赛门铁克公司 System for and method of migrating one or more virtual machines
CN101677321A (en) * 2008-09-16 2010-03-24 株式会社日立制作所 Method and apparatus for storage migration

Also Published As

Publication number Publication date Type
US9614930B2 (en) 2017-04-04 grant
US20140280547A1 (en) 2014-09-18 application
US20150019741A1 (en) 2015-01-15 application
US9609086B2 (en) 2017-03-28 grant

Similar Documents

Publication Publication Date Title
US20070208820A1 (en) Apparatus and method for out-of-order placement and in-order completion reporting of remote direct memory access operations
US20090150529A1 (en) Method and system for enforcing resource constraints for virtual machines across migration
US20140115578A1 (en) Providing a virtual security appliance architecture to a virtual cloud infrastructure
US20080005441A1 (en) Bridging network components
US20090150527A1 (en) Method and system for reconfiguring a virtual network path
US20090327392A1 (en) Method and system for creating a virtual router in a blade chassis to maintain connectivity
US20080002683A1 (en) Virtual switch
US20120278804A1 (en) Virtual machine and application movement over a wide area network
US20110134761A1 (en) Dynamically provisioning virtual machines
US20060221961A1 (en) Network communications for operating system partitions
US20130329584A1 (en) Finding latency through a physical network in a virtualized network
US20130148546A1 (en) Support for converged traffic over ethernet link aggregation (lag)
US20130138836A1 (en) Remote Shared Server Peripherals Over an Ethernet Network For Resource Virtualization
US8750288B2 (en) Physical path determination for virtual network packet flows
US20100095020A1 (en) Method and system for scalable ethernet
WO2013136213A1 (en) Scalable virtual appliance cloud
US20090150883A1 (en) Method and system for controlling network traffic in a blade chassis
US20080168471A1 (en) System and Method for Collective Send Operations on a System Area Network
US20110087774A1 (en) Switching api
US20100333189A1 (en) Method and system for enforcing security policies on network traffic
US20130235870A1 (en) Methods, Systems, and Fabrics Implementing a Distributed Network Operating System
US20150063364A1 (en) Multiple Active L3 Gateways for Logical Networks
US20130254766A1 (en) Offloading packet processing for networking device virtualization
US20130223440A1 (en) Disjoint multi-pathing for a data center network
US20130275592A1 (en) Adaptive session forwarding following virtual machine migration detection

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14762706

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14762706

Country of ref document: EP

Kind code of ref document: A1