JP2014195174A - Virtual machine management device and virtual machine management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To assign a MAC address capable of improving retrieval efficiency to a virtual machine by preventing learning of a switch within a network from being disabled.SOLUTION: A management server 110 which manages MAC addresses to be assigned to virtual machines within a plurality of physical machines 101 inside of a job network uses information on the job network and information on a switch 105 within the job network to create an assignment schedule table 210 having table columns of learning numbers equal to a learning table of the switch 105 for assigning the MAC addresses. Hash functions of the switch 105 are used to register the MAC addresses while having a predetermined order in a scan direction A in the table columns of corresponding hash values in the assignment schedule table 210. The MAC addresses registered within a range of table columns are read out in the predetermined order in the scan direction A and assigned to the virtual machines.

Description

  The present invention relates to a virtual machine management apparatus and a virtual machine management method for managing a network address of a virtual machine.

  In a cloud environment or the like, server virtualization technology is used that operates a plurality of virtual machines (VMs) on a physical server (physical machine). For example, in a data center managed by an infrastructure as a service (IaaS) provider that provides a virtualized server as an infrastructure to a user, a plurality of VMs are operated per physical server.

  Since each VM has a virtual network interface card (virtual NIC: Network Interface Card), a large number of MAC addresses exist in the network.

  A switch is provided between the virtual NIC and the external network. The switch holds a learning table (a correspondence table of transfer destination MAC addresses and connection ports) for frame transfer received from the VM side. A management server that manages each physical machine manages creation, deletion, migration, and the like of VMs. The management server assigns a MAC address to the virtual NIC on the VM when creating the VM.

  The above switch holds a learning table, which is a correspondence table of transfer destination MAC addresses and connection ports, for transferring received frames. A switch generally uses a hash table to improve the search speed of a transfer target MAC address. This learning table includes a MAC address, a hash value obtained from the MAC address, and connection destination port information. In this learning table, there is an upper limit to the number that can be learned for the hash value.

  A technique for avoiding duplication of a virtual NIC when creating a VM in a virtual environment is disclosed as MAC address assignment. In this technique, a table for managing MAC addresses to be allocated is not managed centrally, but a shared table for MAC address management is provided in each physical server, and the usage status of the MAC address is shared between VMs (for example, the following patents) Reference 1).

JP 2010-147929 A

However, the conventional technique has the following problems.
1) Occurrence of MAC address learning impossibility in a switch In a virtual environment, the number of MAC addresses assigned to a VM increases, and the number of MAC addresses learned for one hash value may exceed the upper limit during switch learning. In this case, since the switch recognizes the received packet as an unlearned MAC address (hash collision), flooding that transfers the packet to all other ports occurs, resulting in network congestion. In this respect, the number of MAC addresses that can be learned can be increased by increasing the function of the switch, but the cost of equipment in the data center increases.

2) The switch cannot perform learning considering the MAC address search performance When the switch learns the same number of MAC addresses, if the learning number is biased for each hash value, the learning number for the hash value is uniform. In comparison, the number of searches increases and the MAC address search performance deteriorates.

  In the technique of Patent Document 1, duplication of MAC addresses can be avoided, but the problems 1) and 2) in each switch cannot be solved.

  In one aspect, an object is to assign a MAC address to a virtual machine that prevents learning failure of a switch in the network and can improve search efficiency.

  In one proposal, a virtual machine management device that manages MAC addresses assigned to a plurality of virtual machines in a network uses the network information and switch information in the network, and uses the same learning number as the learning table of the switch. And creating means for creating an allocation plan table for allocating the MAC address, and using the hash function of the switch, the MAC address of the corresponding hash value in the allocation plan table Registration means for registering the table columns in a predetermined order, and assigning means for reading out the MAC addresses registered within the range of the number of table columns in a predetermined order and allocating them to the virtual machine .

  According to one embodiment, it is possible to assign a MAC address to a virtual machine that can prevent learning of a switch in the network and can improve search efficiency.

FIG. 1 is a diagram illustrating an overall configuration of a data center including a virtual machine management apparatus according to an embodiment. FIG. 2 is a block diagram for explaining management of MAC addresses by the management server according to the embodiment. FIG. 3 is a diagram illustrating a hardware configuration example of the management server according to the embodiment. FIG. 4 is a block diagram of a functional configuration of the management server according to the embodiment. FIG. 5 is a diagram illustrating a configuration example with different switch types. FIG. 6 is a chart showing the contents of the network information table. FIG. 7 is a chart showing the contents of the switch information table. FIG. 8 is a chart showing the contents of the allocation plan table. FIG. 9 is a chart showing the contents of the non-priority table. FIG. 10 is a sequence diagram illustrating a processing procedure for creating a table according to the first embodiment. FIG. 11 is a flowchart illustrating a processing procedure for creating a table according to the first embodiment. FIG. 12 is a sequence diagram illustrating a processing procedure for assigning a MAC address to a virtual machine according to the first embodiment. FIG. 13 is a flowchart illustrating a processing procedure for assigning a MAC address to a virtual machine according to the first embodiment. FIG. 14 is a sequence diagram for explaining the learning procedure of the MAC address of each VM by the switch. FIG. 15 is a table showing priority table contents used in the second embodiment. FIG. 16 is a sequence diagram illustrating a processing procedure for creating a table according to the second embodiment. FIG. 17 is a flowchart illustrating a processing procedure for creating a table according to the second embodiment. FIG. 18 is a chart showing the contents of each table created in the second embodiment. FIG. 19 is a sequence diagram illustrating a procedure for assigning a MAC address to a virtual machine according to the second embodiment. FIG. 20 is a flowchart illustrating a processing procedure for assigning a MAC address to a virtual machine according to the second embodiment.

(Embodiment)
(Example of overall network configuration)
Hereinafter, preferred embodiments of the disclosed technology will be described in detail with reference to the accompanying drawings. FIG. 1 is a diagram illustrating an overall configuration of a data center including a virtual machine management apparatus according to an embodiment. The data center 100 is divided into a business network (NW) side 100a that provides services to the outside (user) and a maintenance network (NW) side 100b that manages the inside of the data center 100.

  The business NW side 100a has a plurality of physical machines A to D (101). Each of the physical machines A to D (101) includes a plurality of virtual machines (VM) 102 and a virtual network interface card (NIC) 103. Each physical machine 101 (virtual NIC 103) is connected to an external NW 107 via a switch (for example, a layer 2 switch) 105 and a router.

  On the maintenance NW 100b side, a management server (virtual machine management apparatus) 110 that manages the physical machines A to D (101) and a maintenance terminal 111 that operates the management server 110 by an operator are provided.

(About MAC address management)
FIG. 2 is a block diagram for explaining management of MAC addresses by the management server according to the embodiment. The management server 110 includes a control unit 201 and a memory 202.

  The control unit 201 creates assignment plan information and assigns a MAC address to the VM 102. The allocation plan information includes a hash value obtained from the MAC address, a MAC address corresponding to this hash value, and a status of whether to allocate to the VM 102. The control unit 201 stores the created allocation plan information in the memory 202 as an allocation plan table 210. This allocation plan table 210 is created corresponding to the learning table that the switch 105 has.

  The control unit 201 of the management server 110 uses a hash function that the switch 105 has when obtaining a hash value. The allocation plan table 210 includes a hash value (1 to N) and a MAC address corresponding to the hash value. In the example of FIG. 2, a plurality of MAC addresses (number of table columns 3) are assigned to one hash value (row). For example, the hash value 1 is assigned MAC1, MAC3, MAC9.

  Then, the control unit 201 selects MAC addresses sequentially with the scanning direction A indicated by the arrow in FIG. 2 starting from the smallest column (first column) and row (first row) of the allocation plan table 210. And assigned when the VM 102 is created. In the scanning direction A, MAC addresses are assigned to the hash values 1 to N in the first column, and then the process returns to the hash value 1 and MAC addresses are assigned to the hash values 1 to N in the second column.

  The control unit 201 sequentially assigns “unused” MAC addresses on the assignment plan table 210. Thereby, learning of the MAC address of the switch 105 is within the range of the learning number (number of table columns), and the switch 105 can assign the MAC address almost uniformly to the hash value.

  Based on the allocation plan table 210, the management server 110 (control unit 201) pays out MAC addresses in a predetermined order to the VMs 102 (virtual NICs 103) of the physical machines A to D (101). Here, the management server 110 does not perform allocation (payout) to the VM 102 for MAC addresses that are not registered in the allocation plan table 210. As a result, a MAC address at which learning failure of the switch 105 does not occur can be assigned to the VM 102.

  The switch 105 performs learning based on the MAC address assigned to each VM 102. The learning table of the switch 105 learns the same MAC address as the contents of the allocation plan table 210. At this time, as shown in FIG. 2, the switch 105 learns the MAC addresses of the VMs 102 assigned in order from the smallest column, and can efficiently perform a search performed when searching for the MAC address. . That is, since assignment along the search direction A is performed in the assignment plan table 210 and the learning table of the switch 105, the storage position of the assigned MAC address does not vary, and the MAC address search efficiency can be improved. become.

(Management server hardware configuration example)
FIG. 3 is a diagram illustrating a hardware configuration example of the management server according to the embodiment. The management server 110 includes a CPU (Central Processing Unit) 201 that is a control unit, a memory 202, and a NIC 303.

  The CPU 201 executes control related to MAC address allocation and payout based on a control program stored in a non-volatile area such as a ROM in the memory 202. The CPU 201 collects network (business NW 100a) information, collects switch information of the switch 105, creates various tables in the memory 202 (including the above allocation plan table 210), assigns (assigns) a MAC address to the VM 102, and the like. .

  The memory 202 includes a network information table that stores NW information of the switch 105, a switch information table that stores information of each switch 105, the above-described allocation plan table 210, and a plurality of priorities indicating the priority of MAC address allocation. A table (see Example 2) and the like are stored. For example, these pieces of information are stored in a rewritable nonvolatile area. Alternatively, the data may be temporarily stored in a volatile area such as a RAM and held in a nonvolatile area of the memory 202.

  The NIC 303 communicates with the physical machine 101, the maintenance terminal 111, and the like via the maintenance NW 100b. Information on the business NW 100a and information on the switch 105 are input from the outside via the maintenance terminal 111 or the like. From the maintenance terminal 111, a request for creating the allocation plan table 210 and a VM creation request are transmitted to the management server 110. The management server 110 assigns (dispenses) a MAC address to each VM 102, and returns a creation response of the assignment plan table 210 and a VM creation response to the maintenance terminal 111.

(Functional configuration of the management server)
FIG. 4 is a block diagram of a functional configuration of the management server according to the embodiment. The management server 110 includes a request receiving unit 401, a memory control unit 402, a VM control unit 403, a communication control unit 404, and the like.

  The request reception unit 401 receives a management instruction (such as a table creation request or a VM creation request) from an operator who operates the maintenance terminal 111 via the maintenance NW 100b, and returns a processing result to the maintenance terminal 111 (notification unit). The memory control unit 402 has a function of creating and deleting each table in the memory 202 (creating unit) and a function of registering a MAC address (registering unit). The VM control unit 403 performs creation / addition / deletion of the VM 102, assignment of a MAC address, and the like. The communication control unit 404 performs communication and connection with the physical machine 101 via the NIC 303 and the maintenance NW 100b. Each component in the management server 110 illustrated in FIG. 4 can be executed by the CPU 201 illustrated in FIG. 3 using a control program stored in the memory 202 or the like.

  Each embodiment corresponding to different switch types will be described below. FIG. 5 is a diagram illustrating a configuration example with different switch types. The basic configuration shown in FIG. 5 is the same as that in FIG. 1, but shows networks NW1 and NW2 with different types of switches 105.

  In the network NW1, all the switches 105 connected to the physical machine 101 are the same switch (SW1) 105a. In this configuration example (Example 1), all the switches SW1 (105a) have the same learning number (number of table columns), and the same hash value can be used.

  In the network NW2, the switch type of the switch (SW2) 105b connected to the pair of switches 105a is different from the pair of switches (SW1) 105a corresponding to the physical machines C and D, respectively. In this configuration example (embodiment 2), the number of learnings corresponding to the hash value (number of table columns) in the switches SW1 and SW2 and the method of calculating the hash value using the MAC address differ between the switches SW1 and SW2. .

Example 1
(Contents of each table used for MAC address management)
First, in the first embodiment, a MAC address assignment configuration applied to NW1 (all switch types are the same) in FIG. 5 will be described. 6 to 9 are tables showing the contents of each of the four tables stored in the memory. These four tables are used in common with the first and second embodiments.

  FIG. 6 is a chart showing the contents of the network information table. The network (NW) information table 601 holds information on the switch 105 existing in the business NW 100a. This network information table 601 includes information of an NW identifier for distinguishing business NWs and a switch (SW) identifier indicating a switch type existing in the NW for each NW identifier. The SW identifiers of NW1 and NW2 shown in FIG. 5 are held.

FIG. 7 is a chart showing the contents of the switch information table. The switch (SW) information table 701 holds internal information (SW information) of the switch 105 such as a hash function. As shown in the figure, for each SW identifier, information unique to each switch includes information on the hash function, the number of learnable MAC addresses, the number of hash values bits, and the number of table columns used in the switch. If the number of hash value bits is 2, it means 2 ² = 4.

  The contents of the NW information table 601 and the SW information table 701 are stored in advance in the memory 202 via the maintenance terminal 111 or the like.

  FIG. 8 is a chart showing the contents of the allocation plan table. The allocation plan table 210 holds MAC address candidates to be allocated to the VM 102 and usage status. As shown in the figure, the allocation plan table 210 includes a hash value obtained from the MAC address, a MAC address corresponding to the hash value, a use status of the MAC address, and the like. The usage status includes an identifier indicating “not used” or “in use” (indicating that the payout has been made to the VM 102). The number of columns of the MAC address usage status (horizontal axis) in the allocation plan table 210 matches the number of table columns in the switch information table 701. For example, the number of columns in FIG. Corresponding to).

  FIG. 9 is a chart showing the contents of the non-priority table. The non-priority table 901 holds MAC addresses that exceed the number of table columns of the allocation plan table 210 and could not be registered in the allocation plan table 210. Since the MAC address assigned to the non-priority table 901 causes flooding, the MAC address is not assigned (paid out) to the VM 102.

(Creation of allocation plan table and registration of MAC address)
FIG. 10 is a sequence diagram illustrating a processing procedure for creating a table according to the first embodiment. The creation of the allocation plan table 210 performed by the memory control unit 402 of the management server 110 will be described.

  First, the cloud operator designates a management target network by operating the maintenance terminal 111, and transmits a table creation request to the management server 110 (step S1001). At this time, in the first embodiment, the NW identifier (NW1) of the target NW and a predetermined assigned MAC address range (MAC1 to 12) are designated.

  In response to the table creation request, the memory control unit 402 of the management server 110 obtains an NW information acquisition request by inputting the NW identifier (NW1) to the NW information table 601 in order to obtain a switch type (switch identifier) existing in the NW1. Is transmitted (step S1002). The NW information table 601 returns a switch identifier SW1 to the memory control unit 402 (step S1003).

  Further, the memory control unit 402 receives the SW identifier SW1 as an input to the SW information table 701 and transmits a SW information acquisition request to obtain switch information (hash function, number of table columns) (step S1004). The SW information table 701 returns SW information (hash function A (x), number of table columns 3) to the memory control unit 402 (step S1005).

  Thereafter, the memory control unit 402 calculates a hash value from the acquired hash function and MAC address in order to create the allocation plan table 210 (step S1006). Then, the memory control unit 402 registers the allocation plan table with the calculated hash value and the corresponding MAC address as inputs to the allocation plan table 210 (step S1007). In the example of FIG. 8, a total of 12 (MAC1 to MAC12) MAC addresses can be registered with 4 hash values and 3 table columns. A certain MAC address is registered in one row position corresponding to this hash value by hash value calculation. For example, MAC1 is registered in the row of hash value 2.

  Then, if the MAC address to be registered is within the range of the number of table columns in the corresponding hash value (row), the memory control unit 402 registers the MAC address (MAC1 to MAC12) in the allocation plan table 210 (step S1008). ). At this time, the identifiers of the usage statuses of all the registered MAC addresses are “unused”. The allocation plan table 210 responds to the memory control unit 402 with a registration response (registration OK / or registration NG) (step S1009).

  The memory control unit 402 receives the registration response (step S1010: OK / NG), and repeatedly registers the MAC address in the allocation plan table 210 up to the MAC address range (MAC1 to MAC12) (step S1006). To Step S1010).

  Here, when the MAC address registration result for the allocation plan table 210 is NG (out of the range of the number of table columns in the corresponding hash value row) (step S1010: NG), the memory control unit 402 The MAC address is registered in the non-priority table 901 (step S1011). The memory control unit 402 receives a registration response from the non-priority table 901 (step S1012).

  In the example of FIG. 9, the MAC addresses 11 and 12 cannot be registered in the allocation plan table 210. In the allocation plan table 210 of FIG. 8, there is one space for each of the hash values 3 and 4, but these MAC addresses 11 and 12 cannot be registered in the allocation plan table 210 because the hash values correspond to 1 or 2. .

  Thereafter, the management server 110 (memory control unit 402) notifies the maintenance terminal 111 of the registration result of creation of the allocation plan table 210 (registration result of each MAC address 1 to 12 (OK / NG)) (step). S1013). If the MAC address is registered in the non-priority table 901, the cloud operator is also notified of information on the MAC address (MAC 11, 12) that failed to be registered in the allocation plan table 210. Through the above processing, in the allocation plan table 210, in the state immediately after creation, the identifiers of the usage statuses of the allocated MAC addresses are all “unused”.

  FIG. 11 is a flowchart illustrating a processing procedure for creating a table according to the first embodiment. The processing content concerning creation and registration of the allocation plan table 210 performed by the memory control unit 402 of the management server 110 is shown.

  First, the memory control unit 402 receives designation of the NW identifier (NW1) of the target NW and a predetermined assigned MAC address range (MAC1 to 12) from the maintenance terminal 111 (step S1101). As a result, the SW identifier SW1 corresponding to the NW identifier (NW1) is acquired from the NW information table 601 (step S1102). Also, SW information (hash function A (x), number of table columns 3) corresponding to the SW identifier SW1 is acquired from the SW information table 701 (step S1103). Thereafter, the memory control unit 402 calculates a hash value from the acquired hash function and the MAC address (step S1104).

  Next, the memory control unit 402 registers the MAC addresses one by one in the row corresponding to the hash value in the allocation plan table 210 (step S1105). The identifier of the usage status of the registered MAC address is “unused”.

  Then, the memory control unit 402 determines the registration result of the MAC address with respect to the allocation plan table 210 (step S1106), and if it can be registered (if it falls within the range of the table column number of the corresponding hash value) (step S1106: OK), the process proceeds to step S1108. If registration fails (out of the range of the number of table columns in the corresponding hash value row) (step S1106: NG), this MAC address is registered in the non-priority table 901 (step S1107).

  In step S1108, it is determined whether processing has been completed for the MAC addresses (MAC1 to MAC12) within the specified range. If there is an unprocessed portion (step S1108: No), the process returns to step S1104. If it has been processed (step S1108: Yes), the process proceeds to step S1109.

  In step S1109, it is determined whether the non-priority table 901 exists. If the MAC address is not registered in the non-priority table 901 (step S1109: No), the maintenance terminal is notified that the creation of the allocation plan table 210 has been normally completed, and the process ends. On the other hand, when the MAC address is registered in the non-priority table 901 (step S1109: Yes), the maintenance terminal 111 is notified of the information of the MAC address (MAC11, 12) that failed to be registered in the allocation plan table 210 ( Step S1110), the process ends.

(MAC address assignment for virtual machine)
Next, MAC address assignment processing for the virtual machine (VM) 102 will be described. Processing performed by the VM control unit 403 of the management server 110 will be described.

  FIG. 12 is a sequence diagram illustrating a procedure for assigning a MAC address to a virtual machine according to the first embodiment. First, when creating the VM 102, the cloud operator transmits a VM creation request (for example, VMs 1 to 10) from the maintenance terminal 111 to the management server 110 (step S1201).

  The VM control unit 403 of the management server 110 transmits a MAC address allocation request to the memory control unit 402 in order to acquire a MAC address to be allocated to each VM 102 (step S1202). The memory control unit 402 refers to the allocation plan table 210 and scans in the scanning direction A in order from the smallest number column in the allocation plan table 210 to search for a MAC address whose MAC address usage status is “unused”. If there is an “unused” MAC address (MAC 3 in the figure), the usage status of the MAC address is changed from “unused” to “in use”, and this MAC address is returned to the VM control unit 403 (step) S1203).

  For example, when assigning MAC addresses in the order of VM1 to VM10, based on the assignment plan table 210 shown in the figure, first, MAC2 is assigned to VM1, then MAC1 is assigned to the second VM2, and MAC3 is assigned to the sixth VM6. The assignment plan table 210 in the figure shows a state in which the assignment of MAC addresses up to the fifth VM 5 has been completed, and shows a state at the time of assignment of MAC 3 to the VM 6. Then, a MAC address (MAC3) is assigned to the VM 6, and the usage status is changed from “unused” to “in use”.

  Thereafter, the VM control unit 403 receives the VM identifier (VM6) and the acquired MAC address (MAC3) as inputs, and transmits a VM creation request to the physical machine 101 (step S1204). The physical machine 101 returns the execution result. It responds to the VM control unit 403 (step S1205). Thereafter, the VM control unit 403 returns a VM creation result to the maintenance terminal 111 (step S1206). As described above, an optimal MAC address can be paid out to the VM 102.

  FIG. 13 is a flowchart illustrating a processing procedure for assigning a MAC address to a virtual machine according to the first embodiment. The processing content of the MAC address allocation with respect to the virtual machine which the VM control part 403 of the management server 110 performs is shown. First, the VM control unit 403 receives a VM creation request (for example, VMs 1 to 10) of the VM 102 from the maintenance terminal 111 (step S1301).

  As a result, the VM control unit 403 transmits a MAC address assignment request to the memory control unit 402, and the memory control unit 402 searches the assignment plan table 210, and the MAC address usage status is “unused”. Is extracted (step S1302). Then, the VM control unit 403 determines whether there is a MAC address that can be assigned to the VM 102 (step S1303).

  If there is an assignable MAC address (step S1303: Yes), the VM control unit 403 changes the MAC address usage status from “unused” to “in use”, and creates the VM 102 with the extracted MAC address (step S1303: Yes). S1304). For example, the MAC 3 is assigned (paid out) to the VM 6 and the process is terminated. On the other hand, if there is no assignable MAC address (step S1303: No), the process is terminated. At the end of processing, the VM control unit 403 returns a VM creation result to the maintenance terminal 111.

(About switch learning after creating a virtual machine)
Next, switch learning after creating the virtual machine (VM) 102 will be described. FIG. 14 is a sequence diagram for explaining the learning procedure of the MAC address of each VM by the switch. The VMs 1 to 10 (102) created by the management server 110 communicate with the switch (switch 1) 105a, and the switch 1 (105a) learns the MAC address (steps S1401a to S1401n).

  As a result, the learning table 1410 of the switch 1 (105a) holds the MAC addresses having the same contents as the allocation plan table 210 (see FIGS. 8 and 12) created by the management server 110.

  According to the first embodiment, the management server 110 creates a table similar to the learning table included in the switch 105 in the network, for example, the allocation plan table 210 having a table size (number of columns for each hash function). Then, MAC addresses that can be allocated to a plurality of VMs 102 (virtual NICs 103) are registered in the allocation plan table 210 using the hash function of the switch 105. The registered MAC address is assigned (paid out) to the VM in response to the VM creation request.

  When the allocation plan table 210 is created, the learning number (number of table columns) of the switch 105 is used, and MAC addresses that cannot be registered for a predetermined MAC address range are treated as non-priority. As a result, even if the number of MAC addresses allocated to the VM 102 increases, the amount exceeding the learning number (number of table columns) of the switch 105 is not allocated to the VM 102. As a result, a MAC address at which learning failure of the switch 105 does not occur is assigned to the VM 102, and learning failure at the switch 105 and occurrence of flooding can be prevented.

  Further, the assignment plan table 210 is used for assigning the MAC address to the VM 102, and for the scanning direction A at the time of search, first, in the order of the hash values 1 to N in the row direction, the first column of the number of the young number of table columns Search for unused MAC addresses. Thereafter, the hash value 1 is returned again to search for an unused MAC address in the second column.

  At this time, an existing MAC address is not randomly issued, and unused MAC addresses are assigned to the VM 102 with regularity in order from the first column of the number of table columns. Thereby, the learning of the switch 105 can be kept within a predetermined learning number (table column number). Further, there is no bias in the number of MAC address learning with respect to one hash value, and it can be assigned uniformly. Further, it is possible to suppress the variation in the storage position of the MAC address in the learning table in each switch 105 and to efficiently search for the MAC address (frame transfer destination port).

(Example 2)
(Contents of each table used for MAC address management)
In the second embodiment, a MAC address allocation configuration applied to NW2 (different switch types) in FIG. 5 will be described. In the second embodiment, as in the first embodiment, the four tables (NW information table 601, SW information table 701, allocation plan table 210, and non-priority table 901) shown in FIGS. 6 to 9 are used.

  In the second embodiment, the switch SW1 (105a) and the switch SW2 (105b) have different switch types and different learning numbers (corresponding to the number of table columns). For this reason, two allocation plan tables 210 for SW1 and SW2 are created. In the second embodiment, in order to efficiently perform allocation (and search) of MAC addresses using a plurality of allocation plan tables 210 corresponding to different types of switches 105, three priority tables having priorities are provided. Use.

  FIG. 15 is a table showing priority table contents used in the second embodiment. The priority table 1501 is stored in the memory 202. These priority tables 1501 are created by the memory control unit 402 based on the allocation plan table 210 created for each switch 105 unit.

  FIG. 15A is a chart showing the contents of the highest priority table. The highest priority table 1501a is selected most preferentially at the time of MAC address assignment. FIG. 15B is a chart showing the contents of the priority table 1501b. The priority table 1501b is preferentially selected next to the highest priority table 1501a when assigning MAC addresses. FIG. 15C is a chart showing the contents of the non-priority table 1501c. The non-priority table 1501c is notified to the maintenance person (maintenance terminal 111) that the MAC address cannot be assigned to the VM 102. The plurality of tables 1501a to 1501c shown in (a) to (c) of FIG. 15 may be created as one priority table 1501 divided into areas by priority.

(Creation of allocation plan table and priority table and registration of MAC address)
FIG. 16 is a sequence diagram illustrating a processing procedure for creating a table according to the second embodiment. The creation of the allocation plan table 210 and the priority table 1501 performed by the memory control unit 402 of the management server 110 will be described. Among the processes in FIG. 16, the same reference numerals are assigned to the first embodiment (the process contents common to FIG. 10). For the sake of convenience, some processing contents, for example, hash value calculation (step S1006) and the like are not shown.

  Also in the second embodiment, the processes up to the creation of the allocation plan table 210 (steps S1001 to S1009) are the same processes as in the first embodiment. At this time, the processes in steps S1004 to S1009 are repeated for the number of switches 105 (105a, 105b).

  When the allocation plan table 210 is created (step S1009), the memory control unit 402 creates the priority table 1501 next. The memory control unit 402 assigns this MAC address to which priority table 1501 (the highest priority table 1501a) according to a response at the time of registration of the allocation plan table 210 (which column is registered in the assignment plan table 210 of each SW 105a and 105b). , Whether the priority table 1501b or non-priority table 1501c is to be registered is determined. Then, the memory control unit 402 registers the MAC address in the corresponding priority table 1501 based on the priority determination result (steps S1601a to S1601c).

The criteria for determining the priority are as follows.
Highest priority: MAC address registered in the first (first column) with respect to the hash value in all allocation plan tables 210 of SW1 and SW2.
Priority: MAC address registered after the second (second column) with respect to the hash value in the allocation plan table 210 of either SW1 or SW2. However, the number of table columns must not exceed the allocation plan table 210 of either SW1 or SW2.
Non-priority: MAC address exceeding the number of table columns in the allocation plan table 210 of SW1 or SW2.

  If the priority is determined to be the highest priority, the corresponding MAC address is registered in the highest priority table 1501a (step S1601a). If the determination result is prioritized, the corresponding MAC address is registered in the priority table 1501b (step S1601b). If the determination result is non-priority, the corresponding MAC address is registered in the non-priority table 1501c (step S1601c). Each priority table 1501 returns a response to the memory control unit 402 after registration (steps S1602a to S1602c). The processing from step S1007 to step S1602 is repeated for the MAC address range.

  FIG. 17 is a flowchart illustrating a processing procedure for creating a table according to the second embodiment. Processing contents related to creation and registration of the priority table 1501 performed by the memory control unit 402 of the management server 110 are mainly described. In FIG. 17, the processing (step S1101 to step S1105) related to the creation of the allocation plan table 210 as in the first embodiment (see FIG. 11) is the same as that in the first embodiment. For the sake of convenience, the description of part of the processing in the first embodiment is omitted.

  After creating the allocation plan table 210 in step S1105, the memory control unit 402 determines whether it is the first (first column) registered MAC address for the hash value in all the allocation plan tables 210 of SW1 and SW2. (Step S1705). If this MAC address is the first registration (step S1705: Yes), this MAC address is registered in the highest priority table 1501a (step S1706). On the other hand, if this MAC address is not the first registration (step S1705: No), the process proceeds to step S1707.

  In step S1707, it is determined whether there is a MAC address that exceeds the number of columns in the allocation plan table 210 of either SW1 or SW2 (step S1707). As a result of the determination, if the MAC address does not exceed the number of table columns in either SW1 or SW2 (step S1707: No), it corresponds to the MAC address registered after the second column number. Registration in the priority table 1501b (step S1708). On the other hand, if the MAC address exceeds the number of table columns of either SW1 or SW2 (step S1707: Yes), this MAC address is registered in the non-priority table 1501c (step S1709).

  After the processing of step S1706, step S1708, and step S1709, it is determined whether the processing has been completed for the MAC addresses (MAC1 to MAC10) within the specified range (step S1710), and if there is an unprocessed portion (step S1710: No), Returning to step S1105, if the processing is completed (step S1710: Yes), the above table creation processing is terminated.

(Example of creating each table)
FIG. 18 is a chart showing the contents of each table created in the second embodiment. A creation example of each table in the second embodiment will be specifically described. The MAC address designation range is MAC01-10, the SW identifier is SW1 (105a), SW2 (105b) (see FIG. 5), the number of columns (table column number) of SW1 (105a) is 3, and SW2 (105b) The number of columns is 2. Correspondingly, as the allocation plan table 210, an allocation plan table 210a having three columns for SW1 (105a) and an allocation plan table 210b having two columns for SW2 (105b) are created.

  The allocation plan table 210a has the same contents as the learning table of SW1 (105a), and the allocation plan table 210b has the same contents as the learning table of SW2 (105b).

  In the horizontal direction of the figure, an allocation plan table 210a for SW1, an allocation plan table 210b for SW2, a top priority table 1501a, a priority table 1501b, and a non-priority table 1501c are shown. The vertical axis of the figure shows an example of registration for each MAC address (MAC01 to 10).

  Since MAC address 1 (MAC01) is the first column in the SW1 allocation plan table 210a and the first column in the SW2 allocation plan table 210b, the MAC01 is allocated to the highest priority table 1501a.

  Since MAC address 3 (MAC03) is the second column in the SW1 allocation plan table 210a and the second column in the SW2 allocation plan table 210b, this MAC03 is allocated to the priority table 1501b.

  Since MAC address 4 (MAC04) is not registered in the SW1 allocation plan table 210a and in the SW2 allocation plan table 210b (exceeds the number of columns), this MAC04 is allocated to the non-priority table 1501c.

  The bottom line of FIG. 18 shows the registration status of all MAC addresses (MAC01 to 10). Since the MAC address assigned to the non-priority table 1501c causes flooding, the MAC address is not assigned (paid out) to the VM 102.

(MAC address assignment for virtual machine)
Next, MAC address assignment processing for the virtual machine (VM) 102 will be described. Processing performed by the VM control unit 403 of the management server 110 will be described.

  FIG. 19 is a sequence diagram illustrating a procedure for assigning a MAC address to a virtual machine according to the second embodiment. Each process shown in FIG. 19 is the same as the process in the first embodiment (FIG. 12), and the same reference numerals as those in the first embodiment are given.

  The second embodiment is different from the first embodiment in that the allocation plan table 210 is searched in the first embodiment when the VM 102 is created, whereas the priority table 1501 is searched in the second embodiment.

  After transmitting a VM creation request (for example, VM1 to VM10) from the maintenance terminal 111 to the management server 110 (step S1201), the VM control unit 403 of the management server 110 acquires a MAC address to be assigned to each VM 102. A MAC address assignment request is transmitted to the memory control unit 402 (step S1202).

  Then, the memory control unit 402 searches the priority table 1501 for MAC addresses in the order of the highest priority table 1501a and the priority table 1501b. First, the MAC address whose usage status is “unused” is searched in order from the smallest number column in the highest priority table 1501a. If the highest priority table 1501a is all “in use”, then MAC addresses whose MAC address usage status is “unused” are searched in order from the smallest number column in the priority table 1501b.

  If there is an “unused” MAC address (MAC07 in the figure), the usage status of this MAC address is changed from “unused” to “in use”, and this MAC address is returned to the VM control unit 403 ( Step S1203).

  Thereafter, the VM control unit 403 receives the VM identifier and the acquired MAC address (MAC07) as input, and transmits a VM creation request to the physical machine 101 (step S1204). The physical machine 101 sends the execution result to the VM control unit. It responds to 403 (step S1205). Thereafter, the VM control unit 403 returns a VM creation result to the maintenance terminal 111 (step S1206). As described above, an optimal MAC address can be paid out to the VM 102.

  FIG. 20 is a flowchart illustrating a processing procedure for assigning a MAC address to a virtual machine according to the second embodiment. The processing content of the MAC address allocation with respect to the virtual machine which the VM control part 403 of the management server 110 performs is shown. The processing shown in FIG. 20 of the second embodiment is basically the same as that of the first embodiment (FIG. 13), but the allocation plan table 210 is searched in the first embodiment, whereas the priority table is used in the second embodiment. The difference is that 1501 is searched.

  First, the VM control unit 403 receives a VM creation request (for example, VMs 1 to 10) of the VM 102 from the maintenance terminal 111 (step S2001).

  As a result, the VM control unit 403 transmits a MAC address assignment request to the memory control unit 402, and the memory control unit 402 first searches the highest priority table 1501a in the priority table 1501, and the usage status of the MAC address is determined. An “unused” MAC address is extracted (step S2002). Then, the VM control unit 403 determines whether there is a MAC address that can be assigned to the VM 102 (step S2003).

  If there is a MAC address that can be assigned to the highest priority table 1501a (step S2003: Yes), the MAC address usage status is changed from “unused” to “in use”, and the VM 102 is set with the MAC address extracted from the highest priority table 1501a. It is created (step S2004), the extracted MAC address is assigned (paid out) to the corresponding VM 102, and the process ends.

  On the other hand, if there is no assignable MAC address in the highest priority table 1501a (step S2003: No), the memory control unit 402 searches the priority table 1501b in the priority table 1501, and the usage status of the MAC address is determined. The “unused” MAC address is extracted (step S2005). Then, the VM control unit 403 determines whether there is a MAC address that can be assigned to the VM 102 (step S2006).

  If there is an assignable MAC address in the priority table 1501b (step S2006: Yes), the MAC address usage status is changed from “unused” to “in use”, and the VM 102 is created with the MAC address extracted from the priority table 1501b. (Step S2007). Then, the extracted MAC address is assigned (paid out) to the corresponding VM 102, and the process is terminated. If there is no assignable MAC address in the priority table 1501b (step S2006: No), the process is terminated.

  According to the second embodiment described above, the same effects as in the first embodiment are obtained. In addition, according to the second embodiment, it is possible to cope with a case where switches (SW1, 2) having different learning numbers (number of table columns) are mixed. In particular, using the priority table, the priority of each MAC address registered in the allocation plan table is determined in consideration of the learning number (number of table columns) that differs for each switch type. Accordingly, it is possible to efficiently search for a MAC address having a high priority, and since non-prioritized MAC addresses are not paid out, it is possible to prevent flooding due to a MAC address that cannot be registered in one of the switches (SW1, SW2).

  According to the embodiment described above, in a server virtualization technology such as a data center that operates a plurality of virtual machines on a physical server in a cloud environment, the MAC address for a plurality of virtual MICs provided for each virtual machine is set. Allocation can be performed efficiently. In particular, the number of MAC addresses that can be learned by the switch can be efficiently increased by the management process of the management server without increasing the performance of the switch in the network. In addition, the MAC address in the data center can be allocated at low cost, and the MAC address search performance can be improved.

  Further, an allocation plan table corresponding to the switch learning table is created in the management server, and MAC addresses that are not registered in the allocation plan table are not paid out to the VM. As a result, the VM is assigned a MAC address that does not prevent learning of the switch, thereby preventing the learning of the switch.

  Note that the virtual machine management method described in the present embodiment can be realized by executing a prepared program on a computer. The program is recorded on a computer-readable recording medium such as a hard disk, a flexible disk, a CD-ROM, an MO, and a DVD, and is executed by being read from the recording medium by the computer. Further, this program may be distributed through a network such as the Internet.

The following additional notes are disclosed with respect to the above-described embodiments.
(Additional remark 1) In the virtual machine management apparatus which manages the MAC address allocated to the some virtual machine in a network,
Creating means for creating an allocation plan table for allocating the MAC address having the same number of learning columns as the learning table of the switch, using the information of the network and the information of the switch in the network When,
Registration means for registering the MAC address using a hash function of the switch and having a predetermined order in the corresponding hash value table column of the allocation plan table;
An assigning unit that reads out the MAC addresses registered within the range of the number of table columns in a predetermined order and assigns them to the virtual machine;
A virtual machine management apparatus comprising:

(Appendix 2) The registration means
The virtual machine management device according to appendix 1, wherein the MAC address is not registered in the allocation plan table when the MAC address exceeds the number of table columns for a hash value included in the allocation plan table.

(Supplementary note 3)
As the switch information, the hash function information, the learning number, the number of bits of the hash value, and the number of table columns are collected, the allocation plan table, the hash function information, and the learning The virtual machine management device according to appendix 1 or 2, wherein the virtual machine management device is created with a table size based on the number, the number of bits of the hash value, and the number of table columns.

(Appendix 4) The registration means
The virtual machine management device according to any one of appendices 1 to 3, wherein the MAC addresses are registered in a predetermined order that matches a scanning direction when the MAC address of the switch is searched.

(Supplementary Note 5) The assigning means includes
For each MAC address in the allocation plan table, holds whether or not there is an allocation to the virtual machine,
Any one of appendices 1 to 4, wherein an unassigned MAC address having a predetermined order that matches a scanning direction when searching for the MAC address of the switch is assigned to the virtual machine requested to be assigned Or the virtual machine management device according to claim 1.

(Supplementary note 6) Any one of Supplementary notes 1 to 5, further comprising notification means for notifying that the MAC address assignment request cannot be made when the MAC address is not registered in the assignment plan table. The virtual machine management apparatus according to one.

(Appendix 7) The creation means includes
As the information of the network, collect the type of the switch provided in the network, create a number of allocation plan tables corresponding to the type of the switch,
If the switch type is plural,
Based on the position of the table column of the MAC address respectively registered in the allocation plan table that is created in a plurality of different table sizes, create an allocation priority table for each MAC address,
The assigning means includes
The virtual machine management device according to any one of appendices 1 to 6, wherein the virtual machine is assigned to the virtual machines in order from the MAC address having the highest priority.

(Appendix 8) The registration means
If the MAC address exceeds the number of table columns for the hash value included in the allocation plan table, the MAC address is registered in the non-priority table without registering the MAC address in the allocation plan table. Virtual machine management device.

(Supplementary Note 9) In a virtual machine management method for managing MAC addresses assigned to a plurality of virtual machines in a network,
A creation step of creating an assignment plan table for assigning the MAC address having the same number of learning rows as the learning table of the switch, using the information of the network and the information of the switch in the network When,
A registration step of registering the MAC address in a predetermined sequence in a table column of the corresponding hash value of the allocation plan table using a hash function of the switch;
An assignment step of reading out the MAC addresses registered within the range of the number of table columns in a predetermined order and allocating them to the virtual machine;
A virtual machine management method.

(Supplementary Note 10) The registration process includes
The virtual machine management method according to appendix 9, wherein the MAC address is not registered in the allocation plan table when the MAC address exceeds the number of table columns for the hash value included in the allocation plan table.

(Appendix 11) The registration process
The virtual machine management method according to appendix 9 or 10, wherein the MAC addresses are registered in a predetermined order that matches a scanning direction when the MAC address of the switch is searched.

(Supplementary Note 12) The assigning step includes
For each MAC address in the allocation plan table, holds whether or not there is an allocation to the virtual machine,
Any one of appendices 9 to 11, wherein an unassigned MAC address having a predetermined order matching the scanning direction when searching for the MAC address of the switch is assigned to the virtual machine requested to be assigned The virtual machine management method according to claim 1.

100 Data Center 101 Physical Machine 102 Virtual Machine (VM)
103 Virtual NIC
105 Switch (SW)
105a Switch (SW1)
105b Switch (SW2)
106 router 110 management server 111 maintenance terminal 201 control unit (CPU)
202 Memory 210 Allocation plan table 401 Request reception unit 402 Memory control unit 403 VM control unit 404 Communication control unit 601 Network information table 701 Switch information table 901 Non-priority table 1410 SW learning table 1501 Priority table 1501a Highest priority table 1501b Priority table 1501c Non-priority table

Claims (11)

In a virtual machine management apparatus that manages MAC addresses assigned to a plurality of virtual machines in a network,
Creating means for creating an allocation plan table for allocating the MAC address having the same number of learning columns as the learning table of the switch, using the information of the network and the information of the switch in the network When,
Registration means for registering the MAC address using a hash function of the switch and having a predetermined order in the corresponding hash value table column of the allocation plan table;
An assigning unit that reads out the MAC addresses registered within the range of the number of table columns in a predetermined order and assigns them to the virtual machine;
A virtual machine management apparatus comprising: The registration means includes
2. The virtual machine management device according to claim 1, wherein when the MAC address exceeds the number of table columns for a hash value included in the allocation plan table, the MAC address is not registered in the allocation plan table. The creating means includes
As the switch information, the hash function information, the learning number, the number of bits of the hash value, and the number of table columns are collected, the allocation plan table, the hash function information, and the learning The virtual machine management device according to claim 1, wherein the virtual machine management device is created with a table size based on the number, the number of bits of the hash value, and the number of table columns. The registration means includes
The virtual machine management apparatus according to claim 1, wherein the MAC addresses are registered in a predetermined order that matches a scanning direction when the MAC address of the switch is searched. . The assigning means includes
For each MAC address in the allocation plan table, holds whether or not there is an allocation to the virtual machine,
5. The MAC address in an unassigned state having a predetermined order that matches a scanning direction when searching for the MAC address of the switch is assigned to the virtual machine requested to be assigned. The virtual machine management apparatus according to any one of the above.   6. The information processing apparatus according to claim 1, further comprising a notification unit configured to notify the outside that the MAC address allocation request cannot be made when the MAC address is not registered in the allocation plan table. The virtual machine management device described. The creating means includes
As the information of the network, collect the type of the switch provided in the network, create a number of allocation plan tables corresponding to the type of the switch,
If the switch type is plural,
Based on the position of the table column of the MAC address respectively registered in the allocation plan table that is created in a plurality of different table sizes, create an allocation priority table for each MAC address,
The assigning means includes
The virtual machine management device according to any one of claims 1 to 6, wherein the virtual machines are assigned to the virtual machines in order from the MAC address having the highest priority. In a virtual machine management method for managing MAC addresses assigned to a plurality of virtual machines in a network,
A creation step of creating an assignment plan table for assigning the MAC address having the same number of learning rows as the learning table of the switch, using the information of the network and the information of the switch in the network When,
A registration step of registering the MAC address in a predetermined sequence in a table column of the corresponding hash value of the allocation plan table using a hash function of the switch;
An assignment step of reading out the MAC addresses registered within the range of the number of table columns in a predetermined order and allocating them to the virtual machine;
A virtual machine management method. The registration process includes:
9. The virtual machine management method according to claim 8, wherein when the MAC address exceeds the number of table columns for a hash value included in the allocation plan table, the MAC address is not registered in the allocation plan table. The registration process includes:
The virtual machine management method according to claim 8 or 9, wherein the MAC addresses are registered in a predetermined order that matches a scanning direction when the MAC address of the switch is searched. The assigning step includes
For each MAC address in the allocation plan table, holds whether or not there is an allocation to the virtual machine,
11. The MAC address that has an unassigned state and has a predetermined order that matches a scanning direction at the time of searching for the MAC address of the switch is assigned to the virtual machine requested to be assigned. The virtual machine management method according to any one of the above.

Images