MANAGEMENT AND ORCHESTRATION SERVER

• US 20150222515A1
• Filed: 12/22/2014
• Published: 08/06/2015
• Est. Priority Date: 02/06/2014
• Status: Abandoned Application

• Current Assignee: Hitachi, Ltd.
• Original Assignee: Hitachi, Ltd.
• Inventors: MIMURA, Nodoka, YANO, Masashi, OKUNO, Michitaka, MUTO, Yuta, ISHII, Daisuke
• Application Number:
  US14/578,520
• Publication Number:
  US 20150222515A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 2009/4557 Distribution of virtual machine instances; Migration and load balancing
• CPC Class Codes: G06F 2009/45583 Memory management, e.g. access or allocation
• CPC Class Codes: G06F 2009/45595 Network integration; Enabling network access in virtual machine instances
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: H04L 43/0876 Network utilisation, e.g. volume of load or congestion level

Abstract

A management and orchestration server which manages a plurality of types of virtualized nodes included in server group includes a scaling executing unit configured to command the server group to scale virtual machines included in each of the plurality of types of virtualized nodes, a traffic load measuring unit configured to manage a traffic load of each of the virtual machines, and a scaling amount determining unit configured to determine a number of the virtual machines to be scaled. In this case, the traffic load measuring unit acquires a traffic load for each of the traffic types to be processed by each of the plurality of types of virtualized nodes, and the scaling amount determining unit determines the type of virtualized node for which virtual machines are to be scaled and a number of machines to be scaled based on the traffic loads of the traffic types.

Claims

1. A management and orchestration server which manages a plurality of types of virtualized nodes included in server group, the management and orchestration server comprising:

a scaling executing unit configured to command the server group to scale virtual machines included in each of the plurality of types of virtualized nodes;

a traffic load measuring unit configured to manage a traffic load of each of the virtual machines; and

a scaling amount determining unit configured to determine a number of the virtual machines to be scaled, wherein

the traffic load measuring unit acquires a traffic load for each of the traffic types to be processed by each of the plurality of types of virtualized nodes; and

the scaling amount determining unit determines the type of virtualized node for which virtual machines are to be scaled and a number of virtual machines to be scaled based on the traffic loads of the traffic types.

2. The management and orchestration server according to claim 1, wherein

each of the plurality of types of virtualized nodes processes a plurality of traffic types;

and

the scaling amount determining unit calculates a traffic load normalized by applying weights to traffic loads of the traffic types in accordance with the throughputs of the traffic type and determines a type of virtualized node having the virtual machines to be scaled and the number of machines to be scaled based on the normalized traffic load.

3. The management and orchestration server according to claim 2, wherein the traffic load measuring unit manages a traffic load of each of the virtual machines based on the traffic type;

and

the scaling amount determining unit calculates the normalized traffic load for each of the virtual machines and determines to scale out virtual machines included in a predetermined type of virtualized node if the normalized traffic load of at least one virtual machine of virtual machines included in the predetermined type of virtualized node is higher than a first threshold.

4. The management and orchestration server according to claim 3, wherein the scaling amount determining unit determines to scale in virtual machines included in the predetermined type of virtualized node if an average value of the normalized traffic loads of the virtual machines included in the predetermined type of virtualized node is lower than a second threshold.

5. The management and orchestration server according to claim 2, wherein when the type of virtualized node is vS-GW (Virtulized Serving Gateway) or vP-GW (Virtulized Packet Data Network Gateway) in a mobile communication core network, the scaling amount determining unit calculates the normalized traffic loads by applying a larger weight to a call control signaling traffic than a user data traffic among traffic types to be processed by the vS-GW or the vP-GW.

6. The management and orchestration server according to claim 2, wherein when the type of virtualized node is vMME (Virtualized Mobility Management Entity) in a mobile communication core network, the scaling amount determining unit calculates the normalized traffic loads by applying a larger weight to a call control signaling traffic for attach or detach than a call control signaling traffic for handover or connection establishment or connection release among traffic types to be processed by the vMME.

7. The management and orchestration server according to claim 2, wherein the scaling amount determining unit includes an interface usable by an administrator for submitting a definition setting for the plurality of traffic types and a definition setting for the plurality of types of virtualized node.

8. The management and orchestration server according to claim 2, wherein

if the scaling amount determining unit determines to scale out virtual machines, the scaling amount determining unit instructs the traffic load measuring unit to start acquisition of the plurality of traffic types for the virtual machines to be scaled out;

and

the traffic load measuring unit sets other apparatuses that measure traffic loads of the corresponding virtual machines to notify the plurality of traffic types to the virtual machines to be scaled out.

9. The management and orchestration server according to claim 8,

if the scaling amount determining unit determines to scale in virtual machines, the scaling amount determining unit instructs the traffic load measuring unit to finish acquisition of the plurality of traffic types for the virtual machines to be scaled in;

and

the traffic load measuring unit sets the other apparatuses not to notify the plurality of traffic types to the virtual machines to be scaled in.

10. The management and orchestration server according to claim 2, wherein the scaling amount determining unit forecasts a future traffic load based on a transition of past traffic loads for each of the virtualized nodes and includes an interface usable for notifying an administrator of scale-out of physical resources in the server group for scaling out virtual machines if it is determined that shortage of the physical resources will occur within a predetermined period.