METHOD, SYSTEM, COMPUTER PROGRAM AND COMPUTER PROGRAM PRODUCT FOR MONITORING DATA PACKET FLOWS BETWEEN VIRTUAL MACHINES, VMS, WITHIN A DATA CENTRE

• US 20160216994A1
• Filed: 10/03/2013
• Published: 07/28/2016
• Est. Priority Date: 10/03/2013
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: SEFIDCON, Azimeh, YADHAV, Vinay
• Application Number:
  US15/026,306
• Publication Number:
  US 20160216994A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3433 for load management allocation of a server based on load conditions G06F9/505; load rebalancing G06F9/5083; redistributing the load in a network by a load balancer H04L67/1029
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 2009/45591 Monitoring or debugging support
• CPC Class Codes: G06F 2009/45595 Network integration; Enabling network access in virtual machine instances
• CPC Class Codes: G06F 2201/81 Threshold
• CPC Class Codes: G06F 2201/815 Virtual middleware or OS functionality using virtual machines to implement generic software techniques for error detection or fault masking G06F11/1484
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: H04L 49/70 Virtual switches

Abstract

The following invention relates to methods, systems, computer programs and computer program products for supporting said method, and different embodiments thereof, for monitoring data packet flows between Virtual Machines, VMs, within a data centre. The method comprises collecting flow data for data packet flows between VMs in the data centre, and mapping the flow data of data packet flows between VMs onto data centre topology to establish flow costs for said data packet flows. The method further comprises calculating an aggregated flow cost for all the flows associated with a VM for each VM within the data centre, and determining whether to reschedule any VM, or not, based on the aggregated flow cost.

Claims

1. A method for monitoring data packet flows between at least a portion of Virtual Machines, VMs, within a data centre, said method comprises:

collecting flow data for data packet flows between the at least a portion of VMs in the data centre;

mapping, based on the collected flow data, flow data of data packet flows between the at least a portion of VMs onto data centre topology to establish flow costs for said data packet flows;

calculating, based on the established flow costs, an aggregated flow cost for all the flows associated with a VM for each of the at least a portion of VMs within the data centre; and

determining whether to reschedule any of the at least a portion of VMs, or not, based on the aggregated flow cost.

2. The method according to claim 1, wherein the determining whether to reschedule any of the at least a portion of VMs, or not, comprises:

selecting a not tested optional location for a first one of the at least a portion of VMs.

3. The method according to claim 2, wherein the determining whether to reschedule any VM, or not, further comprises:

mapping flow data of data packet flows between the at least a portion of VMs onto data centre topology to establish flow costs for said data packet flows if the first VM were to be situated in the not tested optional location.

4. The method according to claim 3, wherein the determining whether to reschedule any VM, or not, further comprises:

calculating, based on the established flow costs for the first VM being situated in the not tested optional location, another aggregated flow cost for all the flows associated with the first VM within the data centre.

5. The method according to claim 4, wherein the determining whether to reschedule any VM, or not, further comprises:

for a plurality of other not tested optional locations that the first VM could be situated in, repeating the mapping and calculating to produce a plurality of aggregated flow costs;

selecting the optional location of the first VM that corresponds to a lowest one of the aggregated flow costs.

6. The method according to claim 5, wherein the determining whether to reschedule any VM, or not, further comprises:

rescheduling the first VM according to the selected optional location.

7. The method according to claim 1, wherein the collecting of flow data comprises:

collecting flow statistics from one or more virtual switches regarding data packet flows handled by the one or more virtual switches.

8. A flow monitoring system for monitoring data packet flows between at least a portion of Virtual Machines, VMs, within a data centre, said flow monitoring system comprising:

a processor; and

a memory, said memory containing instructions executable by said processor, whereby said flow monitoring system is operative to;

collect flow data for data packet flows between the at least a portion of VMs in the data centre;

map, based on the collected flow data, flow data of data packet flows between VMs onto data centre topology to establish flow costs for said data packet flows;

calculate, based on the established flow costs, an aggregated flow cost for all the flows associated with a VM for each of the at least a portion of VMs within the data centre; and

determine whether to reschedule any of the at least a portion of VMs, or not, based on the aggregated flow cost.

9. The system according to claim 8, wherein the flow monitoring system is further operative to select a not tested optional location for a first one of the at least a portion of VMs.

10. The system according to claim 8, wherein the flow monitoring system is further operative to map flow data of data packet flows between the at least a portion of VMs onto data centre topology to establish flow costs for said data packet flows if the first VM were to be situated in the not tested optional location.

11. The system according to claim 8, wherein the flow monitoring system is further operative to calculate, based on the established flow costs if the first VM were to be situated in the not tested optional location, another aggregated flow cost for all the flows associated with the first VM within the data centre.

12. The system according to claim 8, wherein the flow monitoring system is further operative to:

repeat, for a plurality of other not tested optional locations that the first VM could be situated in, the mapping and calculating to produce a plurality of aggregated flow costs, and

select the optional location of the first VM that corresponds to a lowest one of the aggregated flow costs.

13. The system according to claim 8, wherein the flow monitoring system is further operative to reschedule the first VM according to the selected optional location.

14. The system according to claim 8, wherein the flow monitoring system is further operative to collect flow statistics from one or more virtual switches regarding data packet flows handled by the one or more virtual switches.

15. A computer readable media containing computer program code which, when run in a processor of a system, causes the system to perform a method of monitoring data packet flows between at least a portion of Virtual Machines, VMs, within a data centre, the method comprising:

collecting flow data for data packet flows between the at least a portion of VMs in the data centre;

mapping, based on the collected flow data, flow data of data packet flows between the at least a portion of VMs onto data centre topology to establish flow costs for said data packet flows;

calculating, based on the established flow costs, an aggregated flow cost for all the flows associated with a VM for each of the at least a portion of VMs within the data centre; and

determining whether to reschedule any of the at least a portion of VMs, or not, based on the aggregated flow cost.

16. (canceled)

17. (canceled)