JP2016085664A - License management system, communication system, method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce communication traffic between network segments.SOLUTION: A license management system comprises a plurality of nodes (node 100-1 to node 100-3) that belong to the same network segment and each hold license information. Each node includes: information collection means for collecting license information held by other nodes in the same network segment; and information transmission means for transmitting part or all of the license information collected by the information collection means to a manager machine 200 belonging to a network segment different from the same network segment.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a license management system, a license management method, and a license management program for managing license information held by a node on a network. The present invention also relates to a communication system, a communication method, and a communication program for managing information held by nodes on a network.

  There is a technology for virtualizing IT resources (resources) such as servers, storages and networks, and a technology for automatically deploying virtualized resources, generally called cloud or cloud computing. In general, a computing environment realized by cloud computing, that is, an IT resource environment required by a user that is dynamically created and made available is called a cloud environment.

  By the way, as one type of cloud environment, there is a so-called hybrid cloud environment in which two or more types of cloud environments having different usage forms such as a public cloud environment and a private cloud environment are combined. The public cloud environment is a cloud environment in which an unspecified number of users share a cloud platform. The private cloud environment is a cloud environment in which only a specific user uses the cloud platform. In addition, as a type of private cloud environment, a cloud infrastructure is built in a site prepared by a service provider (vendor), and only a service is provided to the user. There is a possession type in which a cloud platform is built in a company where the user is present and the cloud platform is provided to the user. Owned private cloud environments are also called on-premises environments.

  When using a hybrid cloud environment, users can dynamically use available resources, for example, when they normally work only in a private cloud environment, but when the load increases, they also use a public cloud environment. Can be combined.

  In recent years, various cloud environments have been examined in accordance with usage purposes, but the current situation is that it is left to the user to manage licenses necessary for applications operating in the cloud environment.

  As technologies related to the license management method in the cloud environment, for example, there are technologies described in Patent Literature 1 and Patent Literature 2.

  Patent Document 1 describes a license management system that detects a software license violation when the software is operated and used on a virtual server. The license management system described in Patent Literature 1 monitors the status of a virtual server and determines whether the status after redeployment violates a license condition when receiving a notification that a failure of the virtual server has been detected. The software license violation is detected by inquiring the management means.

  Patent Document 2 describes an automatic information collection system for safely and automatically performing an operation of collecting various information from each computer provided on a network. In the automatic information collection system described in Patent Document 2, an authentication management server is provided in one of a plurality of computers connected to be communicable with each other, a moving object management server is provided in the other, and each of the remaining computers is provided. A mobility management server is provided. The moving object management server generates a moving object that moves autonomously between the respective movement management servers. Each movement management server collects various information from its own computer based on the movement object when the movement object is input.

JP 2012-137554 A JP 2003-196248 A

  However, the methods described in Patent Document 1 and Patent Document 2 do not take into consideration the cost of communication for license management. For example, when a plurality of cloud environments are used in combination as in a hybrid cloud environment, communication costs may be incurred for each communication across the cloud environment.

  For example, if you want to manage the license of each machine in a hybrid cloud environment, the license management server provided in the on-premises environment periodically inquires each virtual machine in the public cloud to obtain information about the license (for example, each resource It is conceivable to collect license status and operating status. However, when a communication cost corresponding to the amount of communication is generated for communication between the on-premises environment and the public cloud environment, the above method is not preferable because a lot of communication cost is generated. Therefore, it is desired to reduce the communication amount on a communication path that costs depending on the communication amount.

  In addition, even in a public cloud environment, it is conceivable that a cost corresponding to the amount of communication is incurred for communication between cloud platforms constructed at different locations.

  The communication cost problem described above can occur not only in a cloud environment but also in a system that periodically collects and notifies information between nodes belonging to different network segments.

  Therefore, an object of the present invention is to provide a license management system, a communication system, a license management method, a communication method, a license management program, and a communication program that can reduce the communication amount between network segments.

  A license management system according to the present invention includes a plurality of nodes belonging to the same network segment, each having a plurality of license information, and each node stores license information held by another node in the same network segment. Information collecting means for collecting, and information transmitting means for transmitting a part or all of the license information collected by the information collecting means to a manager machine belonging to a network segment different from the same network segment.

  The communication system according to the present invention includes a plurality of nodes belonging to the same network segment, each node collecting information held by other nodes in the same network segment, and information collected by the information collecting means. Information transmission means for transmitting a part or all of the information to an external node belonging to a network segment different from the same network segment.

  In the license management method according to the present invention, a plurality of nodes belonging to the same network segment, each of the plurality of nodes each holding license information, collects license information of other nodes in the same network segment. One node transmits part or all of the collected license information to a manager machine belonging to a network segment different from the same network segment.

  In the communication method according to the present invention, one node among a plurality of nodes belonging to the same network segment collects information held by other nodes in the same network segment, and one node collects one of the collected information. A part or all of them are transmitted to an external node belonging to a network segment different from the same network segment.

  The program for license management according to the present invention is a process for collecting license information held by other nodes in the same network segment in a computer connected to a network and operating as a node holding license information, and the collected license information. A process of transmitting a part or all of the above to a manager machine belonging to a network segment different from the network segment to which the own node belongs is executed.

  The communication program according to the present invention automatically collects information held by other nodes in the same network segment and a part or all of the collected information in a computer connected to a network and operating as a node. A process of transmitting to an external node belonging to a network segment different from the network segment to which the node belongs is executed.

  ADVANTAGE OF THE INVENTION According to this invention, in the system which communicates between the nodes which belong to a different network segment zone | band, the communication amount between network segments can be reduced.

It is a block diagram which shows the structural example of the license management system of 1st Embodiment. It is a block diagram which shows the other structural example of the license management system of 1st Embodiment. It is a block diagram which shows the structural example of the node 100-1 of 1st Embodiment. It is explanatory drawing which shows an example of the message flow of the license management system of 1st Embodiment. It is explanatory drawing which shows the example of the information recorded on a token in 1st Embodiment. It is explanatory drawing which shows the example of the token which the node 100-1 of 1st Embodiment receives. It is a flowchart which shows an example of operation | movement of each node of 1st Embodiment. It is a flowchart which shows an example of operation | movement of each node of 1st Embodiment. It is a block diagram which shows the structural example of the node 100-1 of 2nd Embodiment. It is explanatory drawing which shows the example of the information recorded on a token in 2nd Embodiment. It is explanatory drawing which shows the example of the token which the node 100-1 of 2nd Embodiment receives. It is a flowchart which shows an example of operation | movement of each node of 2nd Embodiment. It is a flowchart which shows an example of operation | movement of each node of 2nd Embodiment. It is a block diagram which shows the structural example of the computer system 1000 of a 1st Example. It is explanatory drawing which shows an example of the flow of the message in a 1st Example. It is explanatory drawing which shows the example of the token which the virtual machine 300-1 of a 1st Example receives. It is explanatory drawing which shows the example of the token which the virtual machine 300-1 of a 1st Example transmits. It is explanatory drawing which shows the example of the token which the virtual machine 300-1 of a 1st Example receives. It is explanatory drawing which shows the other example of the flow of the message in a 1st Example. It is explanatory drawing which shows the example of the token which the virtual machine 300-1 of a 1st Example receives. It is explanatory drawing which shows the other example of the flow of the message in a 1st Example. It is explanatory drawing which shows the example of the token which the virtual machine 300-1 of a 1st Example receives. It is a block diagram which shows the structural example of the communication system of this invention.

Embodiment 1. FIG.
Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram illustrating a configuration example of a license management system according to the present embodiment. The license management system shown in FIG. 1 includes a plurality of nodes 100 (in this example, nodes 100-1 to 100-3) that hold license information that is information related to licenses, and license information that each node 100 has. A manager machine 200 that centrally manages

  In the present embodiment, each of the nodes 100 belongs to the same network segment 110. On the other hand, the manager machine 200 belongs to a network segment different from the network segment 110 to which the node 100 belongs.

  FIG. 2 is a block diagram showing another configuration example of the license management system of the present embodiment. As shown in FIG. 2, the node 100 from which license information is collected may be divided into two or more network segments (in this example, the network segment 110A and the network segment 110B). In such a case, the manager machine 200 may collect and manage license information of nodes belonging to the network segment for each network segment to which the node to be collected belongs.

  For example, in the example illustrated in FIG. 2, the manager machine 200 performs two collection processes such as a process of collecting license information of nodes belonging to the network segment 110A and a process of collecting license information of nodes belonging to the network segment 110B. Divide into times.

  FIG. 3 is a block diagram illustrating a configuration example of the node 100-1. FIG. 3 shows a configuration example of the node 100-1 as an example of the node 100 that holds the license information, but the configurations of the other nodes are the same.

  As illustrated in FIG. 3, the node 100-1 includes a network I / F unit 101, an information collection unit 102, an information transmission unit 103, and a service application unit 104.

  The network I / F unit 101 is a group of interfaces and protocol stacks for communicating with other nodes and the manager machine 200 via a network.

  The information collection unit 102 communicates with other nodes in the same network segment via the network I / F unit 101, and collects license information held by other nodes in the same network segment.

  For example, the information collecting unit 102 may collect license information held by other nodes belonging to the same network segment by using a token that circulates within the network segment 110 to which the own node belongs. More specifically, the information collecting means 102 of each node that holds the license information sequentially receives tokens that are issued at a predetermined timing and circulates within the network segment 110 to which the own node belongs, and the received tokens are The license information held by the node is recorded and transmitted to the next node. In this way, when the token has been circulated in the network segment 110, the license information of all nodes in the same network segment can be collected in at least one node.

  For example, the token may be issued by one node that directly receives a request from the manager machine 200, or may be periodically issued by any node belonging to the same network segment.

  Further, the number of tokens circulating in the network segment 110 to which the own node belongs is not limited to one. For example, one node that receives a request from the manager machine 200 may issue a token in the opposite direction to the token that periodically rotates while each node periodically rotates the token. If two tokens having different circulation directions are used, the time required for collection can be shortened. In this case, the time when two tokens having different circulation directions overlap (collision) in the network segment 110 is when the token has completed circulation in the network segment 110.

  For example, each node may determine whether or not two tokens having different circulation directions overlap each other based on an update time that is a time when each node recorded in the received token updates the information of the token. . In addition, each node may determine whether two tokens having different circulation directions overlap each other based on, for example, a reception time difference between a previously received token and a newly received token.

  The information transmission unit 103 collectively transmits a part or all of the license information of the nodes in the same network segment collected by the information collection unit 102 to the manager machine 200. For example, the information transmission unit 103 may select only the license information of the designated node from the collected license information and transmit it to the manager machine 200. Further, for example, the information transmission unit 103 may select only the license information that has changed from the collected license information and transmit it to the manager machine 200.

  The service application unit 104 is an application group for its own node to perform a predetermined service and its operating environment. The service application unit 104 can include an arbitrary application for each user.

  In the present embodiment, the network I / F unit 101 is realized by a communication device such as a network card and an information processing apparatus such as a CPU that controls the communication device. The information collecting unit 102 and the information transmitting unit 103 are realized by an information processing apparatus such as a CPU that operates according to a program, for example. The service application unit 104 is realized by a storage device that stores an application and an information processing device such as a CPU that reads the application and operates according to the application program.

  Next, the operation of this embodiment will be described. FIG. 4 is an explanatory diagram showing an example of a message flow of the license management system of the present embodiment.

  In the example shown in FIG. 4, the manager machine 200 first sends license information to any node belonging to the network segment 110, for example, the node 100-1 having the youngest IP address among the nodes 100 belonging to the network segment 110. Is acquired (see (1) in FIG. 4).

  Upon receiving the license information acquisition request from the manager machine 200, the node 100-1 issues a token for collecting license information of other nodes in the network segment 110 to which the node 100-1 belongs ((2) in FIG. 4). reference). Specifically, the information collecting unit 102 of the node 100-1 generates a token including at least the license information of the own node, and transmits the token to the node 100-2 that is the next node in the network segment 110 to which the own node belongs. .

  Here, each node may recognize the range of the same network segment by using, for example, a subnet mask. In addition, each node may determine the next node in accordance with, for example, a predetermined rule (for example, turn tokens in ascending order of IP address within the same network segment). In addition, a timeout occurs when each node transmits a token toward a node that is the next destination of the token according to the rule (for example, a node having an IP address obtained by raising the IP address of its own node by one). In this case, it is assumed that the node does not exist in the same network segment, and a token is transmitted to a node which is the next transmission destination (for example, a node having an IP address obtained by raising the IP address of the own node by two). That's fine. Such transmission processing is repeated until the next node is found. Each node, when the token destination reaches the last node in the cyclic order (for example, the node with the highest IP address in the same network segment), becomes the first node (for example, the node with the lowest IP address). return. In that way, the token goes around all nodes in the same network segment.

  The method for determining the next node is not limited to the above method. For example, each node may maintain a circulation list indicating the circulation order of the nodes in the network segment 110. For example, each node may turn tokens in the order of the nodes described in the circulation list.

  When the node 100-2 receives the token from the node 100-1, the node 100-2 appends the license information of the own node to the received token and transmits it to the next node 100-3 (see (3) in FIG. 4). .

  When the node 100-3 receives the token from the node 100-2, it adds the license information of its own node to the received token and transmits it to the node 100-1 as the next node (see (4) in FIG. 4). .

  When the node 100-1 receives the token from the node 100-3, the node 100-1 determines that the token according to the request from the manager machine 200 has finished circulating in the network segment 110, and the license of each node obtained from the received token. A part or all of the information is transmitted to the manager machine 200 (see (5) in FIG. 4).

  For example, after receiving a request from the manager machine 200, the node 100-1 determines that the token related to the request from the manager machine 200 has finished circulating in the network segment 110 when the node receives the token again. Also good.

  FIG. 5 is an explanatory diagram illustrating an example of information recorded in a token. As shown in FIG. 5, the token may include not only the license information of each node but also information such as the machine name, update time, and IP address of each node. In addition, the token may include information necessary for issuing a license (physical server information or the like) if necessary.

  The license information is, for example, information (application name, model number, etc.) that uniquely identifies the application for each application that operates on the own node and requires license management, and is currently set in the application. It may be license key information. Note that the example shown in FIG. 5 is merely an example, and the information recorded in the token is not limited to this.

  FIG. 6 is an explanatory diagram illustrating an example of a token received by the node 100-1. For example, the node 100-1 can acquire the license information of all nodes in the same network segment by receiving the token as shown in FIG. 6 in (4) of FIG. In FIG. 6, “machine1” is the machine name of the node 100-1. “Machine2” is the machine name of the node 100-2. “Machine3” is the machine name of the node 100-3.

  7 and 8 are flowcharts showing an example of the operation of each node. FIG. 7 is a flowchart showing an example of the operation of each node when a license information acquisition request is received from the manager machine 200. FIG. 8 is a flowchart showing an example of the operation of each node when a token is received from another node in the same network segment.

  First, the operation of each node when a license information acquisition request is received from the manager machine 200 will be described. As shown in FIG. 7, when each node receives a license information acquisition request from the manager machine 200 (step S111), the information collecting unit 102 acquires the license information of the own node (step S112). The information collecting unit 102 may acquire the license information of the own node by, for example, reading it from a predetermined address, or may acquire the license information of the own node by calling an API of each application of the own node.

  Next, the information collecting unit 102 generates a token including at least the acquired license information of the own node, and transmits it to the next node in the same network segment (steps S113 and S114).

  Next, the operation of each node when a token is received from another node in the same network segment will be described. As shown in FIG. 8, when each node receives a token from another node in the network segment 110 to which the own node belongs (step S121), first, the information collecting means 102 receives the token to which the own node belongs. It is determined whether or not the circulation in 110 has been completed (step S122).

  If it is determined in step S122 that the token has been circulated in the network segment 110 to which the own node belongs (Yes in step S122), the information transmitting unit 103 reads the information recorded in the received token, and the manager machine 200 (step S123, step S124).

  On the other hand, if it is determined that the token has not been circulated in the network segment 110 to which the own node belongs (No in step S122), the process proceeds to step S125.

  In step S125, the information collection unit 102 acquires the license information of the own node. Next, the information collecting unit 102 appends the license information of the own node to the received token and transmits it to the next node in the same network segment (step S126, step S127). When the received token includes information on the own node, the information collecting unit 102 may record the latest information on the own node by overwriting the information. The latest local node information may be recorded while remaining. The information collecting unit 102 transmits a token including at least the information of the other node included in the received token and the latest information of the own node to the next node.

  As described above, according to the present embodiment, the manager machine 200 does not transmit a license information acquisition request to each of the nodes belonging to the network segment 110 different from the network segment to which the node belongs. Since the license information of all nodes belonging to can be obtained, the amount of communication between network segments can be reduced.

  In the above description, an example is shown in which a node that has received a license information acquisition request from the manager machine 200 issues a token, and transmits information to the manager machine 200 when the token has been circulated. The timing, the token circulation method, and the transmission timing of information to the manager machine 200 are not limited to this.

  For example, one of the nodes may periodically issue a token so that the token periodically rotates in the network segment 110 during system operation. At this time, the token may include a collection result (license information of each node, etc.) for a predetermined number of times as a collection history. Further, when the token periodically goes around the network segment 110, for example, the node that has received a request from the manager machine 200 is acquired from the token at the timing when the token has come to the own node after receiving the request. Information may be transmitted to the manager machine 200.

  Further, for example, one node belonging to the same network segment can spontaneously transmit information of each node to the manager machine 200. For example, each node periodically circulates tokens, and at the timing when a predetermined time comes, any node (for example, the node having the smallest IP address recorded in the most recently received token information) Node) may send the latest information to the manager machine 200. In addition, for example, every time one of the nodes (for example, the node having the smallest IP address in the node information recorded in the most recently received token) makes a round of the token, the node that received the token A difference from the license information recorded in the received token may be taken, and the latest information may be transmitted to the manager machine 200 when the license information of any node changes.

  The information collecting unit 102 may collect license information of other nodes in the same network segment using a method other than a token. For example, the information collecting unit 102 of the first node that has received the request from the manager machine 200 transmits a message requesting license information to all other nodes in the same network segment, and collects information on each other node. When the means 102 receives the above message from the first node in the same network segment, the means 102 may return a message including the license information of the own node to the first node.

Embodiment 2. FIG.
Next, a second embodiment of the present invention will be described. In this embodiment, a license information setting function is provided in each node. FIG. 9 is a block diagram illustrating a configuration example of the node 100-1 according to the second embodiment. FIG. 9 shows an example of the configuration of the node 100-1 as an example of a node that holds license information, but the configuration of other nodes is the same.

  As shown in FIG. 9, the node 100-1 of this embodiment is different from the configuration of the first embodiment shown in FIG. 3 in that an information setting unit 105 is further provided. Further, the information collecting means 102 is different from the information collection notifying means 102A.

  The information collection notifying unit 102A communicates with other nodes in the same network segment via the network I / F unit 101, and transmits the setting information of the license information from the manager machine 200 to the other nodes in the same network segment. Notify

  For example, the information collection notification unit 102A may notify the other nodes belonging to the same network segment of the license information setting request content from the manager machine 200 using a token that circulates within the same network segment. The token may be obtained by adding license information setting request contents from the manager machine 200 to the license information collecting token of the first embodiment.

  The information setting unit 105 sets the license information in the own node according to the content of the license information setting request notified from the other node or the manager machine 200.

  In the present embodiment, the information collection notification unit 102A and the information setting unit 105 are realized by an information processing apparatus such as a CPU that operates according to a program, for example.

  Next, the operation of this embodiment will be described. The message flow in this embodiment is basically the same as the message flow in the first embodiment shown in FIG. However, the information recorded in the message (token) is different from that in the first embodiment.

  In this embodiment, first, the manager machine 200 sets license information in any node belonging to the network segment 110, for example, the node 100-1 that is the node having the youngest IP address among the nodes 100 belonging to the network segment 110. A license information setting request including the target node and the license information to be set is transmitted (see (1) in FIG. 4).

  When the node 100-1 receives the license information setting request from the manager machine 200, the node 100-1 performs setting processing according to the request contents if the license information setting request for the own node is included, and then the node 100-1 belongs. A token for notifying other nodes in the network segment 110 of a request content from the manager machine 200 (information included in the license information setting request) is issued (see (2) in FIG. 4). Specifically, the node 100-1 generates a token including at least the request content from the manager machine 200, and transmits the token to the node 100-2 that is the next node in the network segment 110 to which the node 1001 belongs.

  Here, the generated token may also serve as a token for collecting license information of other nodes. By doing so, the latest license information of each node can also be collected. For example, the node 100-1 generates a token including at least the request content from the manager machine 200 and the license information of the own node, and sends it to the node 100-2 that is the next node in the network segment 110 to which the own node belongs. Send.

  Specifically, the node 100-1 performs the token transmission process toward the next transmission destination of the token in accordance with a predetermined rule, and as a result, the node 100-2 that has reached the token first is the next node. recognize. The recognition method of the next node in other nodes is the same as that of the node 100-1.

  When the node 100-2 receives the token from the node 100-1, if the received token includes a license information setting request for the own node, the node 100-2 receives the token after performing setting processing according to the request content. The token is directly added or the license information of the own node is added and transmitted to the next node 100-3 (see (3) in FIG. 4).

  When the node 100-3 receives the token from the node 100-2, if the received token includes a license information setting request for the node 100-2, the node 100-3 receives the token after performing setting processing according to the request content. The token information is sent as it is or the license information of the own node is added to the node 100-1 as the next node (see (4) in FIG. 4).

  When the node 100-1 receives the token from the node 100-3, the node 100-1 transmits a notification of the completion of setting to the manager machine 200, assuming that the token related to the request from the manager machine 200 has circulated in the network segment 110 (see FIG. 4 (5)). At this time, if the received token includes the license information of each node, the node 100-1 reads the license information of each node recorded in the received token, along with the completion of setting. You may transmit to the manager machine 200.

  FIG. 10 is an explanatory diagram illustrating an example of information recorded in a token. As illustrated in FIG. 10, the token may include the target node and license information as a setting request from the manager machine 200 (see “set-list” in the drawing). FIG. 10 shows an example in which the license information collected from each node is included in the information recorded in the token (see “read-list” in the figure). Note that the example shown in FIG. 10 is merely an example, and the information recorded in the token is not limited to this.

  FIG. 11 is an explanatory diagram illustrating an example of a token received by the node 100-1. For example, the node 100-1 receives the token as shown in FIG. 11 in (4) of FIG. 4, and sets the license information of each node recorded in the received token to the manager machine 200 together with the completion of setting. May be sent to. By doing so, the manager machine 200 can confirm the setting result. FIG. 11 shows a token including license information indicating that the license key: “eeeeee” designated by the manager machine 200 is set in the application: “App1” of the machine name: “machine3”. (See (*) mark in FIG. 11).

  In the example illustrated in FIG. 11, the request content from the manager machine 200 is left in the token. However, when the target node reads the request content, the corresponding information in the token may be deleted.

  12 and 13 are flowcharts showing an example of the operation of each node according to this embodiment. FIG. 12 is a flowchart illustrating an example of the operation of each node when a license information setting request is received from the manager machine 200. FIG. 13 is a flowchart showing an example of the operation of each node when a token is received from another node in the same network segment.

  First, the operation of each node when a license information setting request is received from the manager machine 200 will be described. As shown in FIG. 12, when each node receives a license information setting request from the manager machine 200 (step S211), the information collection notification means 102A includes a license information setting request for its own node in the received message. It is determined whether or not (step S212).

  If a license information setting request for the own node is included (Yes in step S212), the information setting unit 105 performs setting processing according to the request content (step S213). The information setting unit 105 may set the specified license information, for example, by writing the specified license information at a predetermined address or calling the API of the specified application.

  If the license information setting request for the own node is not included (No in step S212), the process directly proceeds to step S214.

  In step S214, the information collection notification unit 102A acquires the license information of the own node.

  Next, the information collection notification unit 102A generates a token including at least the request contents from the manager machine 200 and the acquired license information of the own node, and transmits the token to the next node in the same network segment (step S215, step S215). S216).

  Next, the operation of each node when a token is received from another node in the same network segment will be described. As shown in FIG. 13, when each node receives a token from another node in the same network segment (step S221), first, the information collection setting unit 102A issues a request for setting license information for the own node to the received token. It is determined whether it is included (step S222).

  If a license information setting request for the own node is included (Yes in step S222), the information setting unit 105 performs setting processing according to the request content (step S223). The operation in step S223 is the same as that in step S212.

  If the license information setting request for the own node is not included (No in step S222), the process directly proceeds to step S224.

  In step S224, the information collection setting unit 102A determines whether or not the received token has finished circulating in the network segment 110 to which the own node belongs.

  When it is determined that the token has been circulated in the network segment 110 to which the own node belongs (Yes in step S224), the information transmission unit 103 reads the information recorded in the received token and transmits it to the manager machine 200. (Step S225, Step S226).

  On the other hand, if it is determined that the token has not been circulated within the network segment 110 to which the own node belongs (No in step S224), the process proceeds to step S227.

  In step S227, the information collection notification unit 102A acquires the license information of the own node. Next, the information collection notification unit 102A appends the license information of the own node to the received token and transmits it to the next node in the network segment 110 (steps S228 and S229).

  As described above, according to the present embodiment, the manager machine 200 does not transmit a license information setting request to each of the nodes belonging to the network segment 110 different from the network segment to which the node belongs. Since the license information setting request content can be notified to all nodes belonging to the network, the traffic between the network segments can be reduced.

  Also in this embodiment, a setting request from the manager machine 200 can be notified to other nodes in the same network segment using a method other than a token.

  Next, the operation of the second embodiment will be described using a specific example. FIG. 14 is a block diagram illustrating a configuration example of a computer system 1000 in a hybrid cloud environment to which the license management system according to the second embodiment is applied.

  A computer system 1000 illustrated in FIG. 14 includes a manager machine 200, a server 400-1, and a server 400-2 that operate on the on-premises environment 2, and a plurality of virtual machines 300 that operate on the public cloud environment 1 (in this example, virtual machines 300). Machine 300-1 to virtual machine 300-5).

  In this example, each virtual machine operating on the public cloud environment 1 belongs to the network segment 110A. Each machine operating on the on-premises environment 2 belongs to the network segment 110B.

  Hereinafter, a network connecting virtual machines in the network segment 110A is referred to as a network 30-A. A network connecting the machines in the network segment 110B is referred to as a network 30-B. A network connecting the network segment 110A and the network segment 110B is referred to as a network 30-C. Note that the network 30-A and the network 30-C are connected via a HUB 330A. Further, the network 30-B and the network 30-C are connected via a HUB 330B.

  In this example, the network 30-A and the network 30-B are local area networks (LANs), and there is no cost corresponding to the amount of communication for communication using the network. On the other hand, the network 30-C is a WAN (Wide Area Network), and a cost corresponding to the amount of communication is generated for communication using the network.

  The virtual machines 300-1 to 300-5 correspond to the plurality of nodes 100 in each of the above embodiments.

  Consider a case in which the manager machine 200 operating on the on-premises environment 2 manages the license information of each virtual machine 300 operating on the public cloud environment 1 in such a configuration.

  FIG. 15 is an explanatory diagram illustrating an example of a message flow in the present embodiment. In the example illustrated in FIG. 15, the manager machine 200 first transmits a license information acquisition request to the virtual machine 300-1 operating on the public cloud environment 1 (see (1) in FIG. 15). The transmission destination of the license information acquisition request may be other than the virtual machine 300-1.

  Upon receiving the license information acquisition request from the manager machine 200, the virtual machine 300-1 acquires the license information of the own machine and transmits a token including the acquired license information to the virtual machine 300-2 that is the next node. (See (2) in FIG. 15).

  In this example, it is assumed that a rule is set for each node so that tokens are turned in ascending order of IP addresses in the range specified by the subnet mask of the network segment 110A.

  In (2) of FIG. 15, the virtual machine 300-1 uses the token IP address of the next node in the network segment 110 </ b> A that is incremented by one as the IP address of the next transmission destination of the token. I do. As a result, the token is received by the virtual machine 300-2 having the next largest IP address of the virtual machine 300-1 in the network segment 110A at that time (when transmission processing is performed).

  The virtual machine 300-2 that has received the token from the virtual machine 300-1 acquires the license information of the own machine, adds the acquired license information to the received token, and then adds the acquired license information to the virtual machine 300-3 that is the next node. Transmit (see (3) in FIG. 15).

  The tokens are then licensed for each virtual machine from the virtual machine 300-3 to the virtual machine 300-4, from the virtual machine 300-4 to the virtual machine 300-5, and from the virtual machine 300-5 to the virtual machine 300-1. It goes around while information is added (see (4), (5), (6) in FIG. 15).

  The virtual machine 300-1 that has received the token from the virtual machine 300-5 has a network obtained from the received token, assuming that the token related to the license information acquisition request from the manager machine 200 has finished circulating in the network segment 110A. A message including the license information of all the virtual machines in the segment 110A is transmitted to the manager machine 200 (see (7) in FIG. 15).

  FIG. 16 is an explanatory diagram illustrating an example of a token received by the virtual machine 300-1. For example, the virtual machine 300-1 receives a token as illustrated in FIG. 16 in (6) of FIG. FIG. 16 shows a token including license information indicating that the license key is not set in the application: “App2” running on the machine name: “machine2” (marked with (*) in FIG. 16). reference).

  The manager machine 200 receives a message including license information of all virtual machines (virtual machine 300-1 to virtual machine 300-5) included in the token illustrated in FIG. 16 from the virtual machine 300-1.

  Based on the message received from the virtual machine 300-1, the manager machine 200 checks whether there is an application with an insufficient license in the public cloud environment 1. In this example, the manager machine 200 detects that a license key is not set for an application running on the machine name: “machine2”: “App2”, and acquires a license key to be set for the application. . For example, the manager machine 200 may request a predetermined server to issue a license key for the application. For example, if information on a virtual machine that is an application operating environment is necessary, the manager machine 200 may include such information in the request.

  Next, when the manager machine 200 acquires the license key of the application: “App2” operating on the machine name: “machine2” in this way, the manager machine 200 receives the license information for setting the acquired license key in the application. A setting request is transmitted to the virtual machine 300-1 (see (8) in FIG. 15). For example, the manager machine 200 transmits a license information setting request including a machine name, an application name, and a license key of the target virtual machine to the virtual machine 300-1. The transmission destination of the license information setting request may be other than the virtual machine 300-1.

  Upon receiving the license information setting request from the manager machine 200, the virtual machine 300-1 confirms that the setting request for the own machine is not included, and acquires the license information of the own machine. Then, the virtual machine 300-1 generates a token including the request content from the manager machine 200 and the license information of the own machine, and transmits the token to the virtual machine 300-2 that is the next node ((9) in FIG. 15). reference).

  FIG. 17 is an explanatory diagram illustrating an example of a token transmitted by the virtual machine 300-1. For example, the virtual machine 300-1 may generate a token as illustrated in FIG. 17 in (9) of FIG. 15 and transmit the token to the virtual machine 300-2. FIG. 17 shows a token including the machine name: machine2 of the target virtual machine, the application name: App2, and the license key: fffff as the request contents from the manager machine 200 (FIG. 17). (See the (*) mark of 17).

  When the virtual machine 300-2 that has received the token from the virtual machine 300-1 confirms that the received token includes a setting request for the own machine, the license key specified by the specified application: App2: fffff Set. Then, the virtual machine 300-2 acquires the license information of the own machine, adds the acquired license information to the received token, and transmits it to the virtual machine 300-3 that is the next node ((10 in FIG. 15). )reference).

  The tokens are then licensed for each virtual machine from the virtual machine 300-3 to the virtual machine 300-4, from the virtual machine 300-4 to the virtual machine 300-5, and from the virtual machine 300-5 to the virtual machine 300-1. It goes around while information is added (see (11), (12), (13) in FIG. 15).

  The virtual machine 300-1 that has received the token from the virtual machine 300-5 has a network obtained from the received token, assuming that the token related to the license information setting request from the manager machine 200 has circulated in the network segment 110A. A message including license information of all the virtual machines in the segment 110A is transmitted to the manager machine 200 (see (14) in FIG. 15).

  FIG. 18 is an explanatory diagram illustrating an example of a token received by the virtual machine 300-1. For example, in (13) of FIG. 15, the virtual machine 300-1 receives a token as illustrated in FIG. FIG. 18 shows a token including license information indicating that a license key: “fffff” is set for an application: “App2” with a machine name: “machine2” (FIG. 18). (See (*) sign).

  FIG. 19 is an explanatory diagram showing another example of the message flow in this embodiment. The example shown in FIG. 19 is an example of a message flow when a new virtual machine 300-6 is added to the public cloud environment 1 due to scale-out or the like during operation. In the following, it is assumed that the virtual machine 300-6 is added as a machine name: “machine6” and an IP address in the network segment 110A: 192.168.11.3.

  In the example illustrated in FIG. 19, the manager machine 200 first transmits a license information acquisition request to the virtual machine 300-1 operating in the public cloud environment 1 (see (1) in FIG. 19). The transmission destination of the license information acquisition request may be other than the virtual machine 300-1.

  Upon receiving the license information acquisition request from the manager machine 200, the virtual machine 300-1 acquires the license information of the own machine and generates a token including the acquired license information, as in the example illustrated in FIG. Then, it is transmitted to the virtual machine 300-6 as the next node (see (2) in FIG. 19).

  In (2) of FIG. 19, as a result of the token transmission process by the virtual machine 300-1, the token is received by the virtual machine 300-6 having the next largest IP address of the virtual machine 300-1 in the network segment 110A. .

  The virtual machine 300-6 that has received the token from the virtual machine 300-1 acquires the license information of the own machine, adds the acquired license information to the received token, and then adds the acquired license information to the virtual machine 300-2 that is the next node. Transmit (see (3) in FIG. 19).

  The subsequent steps are the same as in FIG. That is, the token is then transferred from the virtual machine 300-2 to the virtual machine 300-3, from the virtual machine 300-3 to the virtual machine 300-4, from the virtual machine 300-4 to the virtual machine 300-5, and from the virtual machine 300-. The license information of each virtual machine is added from 5 to the virtual machine 300-1 (see (4), (5), (6), and (7) in FIG. 19).

  FIG. 20 is an explanatory diagram illustrating an example of a token received by the virtual machine 300-1. The virtual machine 300-1 receives a token as shown in FIG. 20, for example, in (7) of FIG. FIG. 20 shows a token including license information indicating that a license key is not set in an application: “App1” running on the newly added virtual machine 300-6 (machine name: “machine6”). Is shown (see (*) mark in FIG. 20).

  For example, the virtual machine 300-1 may transmit a message including license information of all the virtual machines (virtual machine 300-1 to virtual machine 300-6) included in the token illustrated in FIG. .

  The manager machine 200 can detect that there is an application for which no license key is set in the public cloud environment 1 based on the message received from the virtual machine 300-1.

  In the above description, the virtual machine 300-1 issues a collection token in response to receiving a license information acquisition request from the manager machine 200 via the network 30-C. May issue tokens periodically, for example. Note that the virtual machine that issues periodic tokens is not limited to the virtual machine 300-1.

  In such a case, for example, the virtual machine 300-1 may determine whether or not there is a change in the license information of the virtual machines belonging to the same network segment 110A at the timing when the currently circulating token has finished circulating. . When the virtual machine 300-1 determines that the license information of the virtual machine belonging to the same network segment 110A has changed, the virtual machine 300-1 transmits a message including at least the license information of the changed machine to the manager machine 200. May be.

  For example, the virtual machine 300-1 may detect whether or not the license information has changed by comparing the information recorded in the token received this time with the information recorded in the previously received token. Further, for example, when the token includes a collection result for the past predetermined number of times as the collection history, the virtual machine 300-1 may detect whether there is a change in the license information using the information of the collection history. .

  FIG. 21 is an explanatory diagram showing another example of the message flow in this embodiment. The example illustrated in FIG. 21 is an example of a message flow when the virtual machine 300-6 is deleted from the public cloud environment 1 during operation.

  In the example shown in FIG. 21, the virtual machine 300-1 issues a new token including the contents of the token after a predetermined time has elapsed after it is determined that the token received in (7) of FIG. Suppose that

  For example, the virtual machine 300-1 may generate a token in which the license information of the own machine is added to the content of the token received last time and transmit the token to the next node. At this time, the virtual machine 300-1 may set a flag indicating that the token is a token by the regular processing in the token.

  In the example illustrated in FIG. 21, the virtual machine 300-1 first sends a token toward the IP address (192.168.11.3) next to the IP address (192.168.11.2) of its own machine. Transmit (see (9) in FIG. 21). In this example, since the virtual machine 300-6 having the IP address: 192.168.11.3 at this time is deleted, the transmission of the token fails. Next, the virtual machine 300-1 transmits a token toward the next largest IP address (192.168.11.4). As described above, as a result of the virtual machine 300-1 performing the token transmission process while increasing the destination IP address by one, the token is the next to the virtual machine 300-1 in the network segment 110A at that time. Is received by the virtual machine 300-2 having a larger IP address (see (10) in FIG. 21).

  The virtual machine 300-2 that has received the token from the virtual machine 300-1 acquires the license information of the own machine, adds the acquired license information to the received token, and then adds the acquired license information to the virtual machine 300-3 that is the next node. Transmit (see (11) in FIG. 21).

  The tokens are then licensed for each virtual machine from the virtual machine 300-3 to the virtual machine 300-4, from the virtual machine 300-4 to the virtual machine 300-5, and from the virtual machine 300-5 to the virtual machine 300-1. It goes around as information is added (see (12), (13), and (14) in FIG. 21).

  FIG. 22 is an explanatory diagram illustrating an example of a token received by the virtual machine 300-1. The virtual machine 300-1 receives a token as shown in FIG. 22, for example, in (14) of FIG. The token shown in FIG. 22 is an example in which each virtual machine adds information on its own machine in the form of overwriting past information on its own machine included in the received token. Note that each virtual machine may record information of its own machine in a new area while leaving information of each past virtual machine in the token as a collection history.

  For example, the virtual machine 300-1 transmits a message including the license information of all the virtual machines included in the latest token to the manager machine 200 at a predetermined timing (on time or when the presence or absence of a change is detected). .

  The manager machine 200 receives a message including license information of all virtual machines (virtual machine 300-1 to virtual machine 300-6) included in the token shown in FIG. 22, for example, from the virtual machine 300-1.

  According to this example, the manager machine 200 has the machine name: “machine6” on the network 30-A at least when the latest token is circulated based on the update time of information by each machine included in the received message. You can see that it was not. For example, since the update time of the information of the machine name: “machine6” is older than the update time of the information of other virtual machines, the manager machine 200 has at least the latest machine name: “machine6” in the received message. It can be determined that the token 30 was not present on the network 30-A during the circulation of the token. Further, for example, the manager machine 200 compares the latest collection result with the previous collection result and the information of the machine name: “machine6” is not updated, so that the machine name: “machine6” is at least It can be determined that the network 30-A did not exist when the latest token was visited.

  As described above, according to the present embodiment, even when an application whose license is not registered is added due to scale-out or the virtual machine is no longer on the network during operation, the manager machine 200 is in such a situation. Can be detected.

  Also, for example, if each virtual machine records license information including information indicating the license usage conditions and the usage status related to the usage conditions, such as the number of operating resources and the maximum number of resources in the current license key, The manager machine 200 can also detect a situation where the license usage conditions are not satisfied due to scale-up or the like.

  For example, when the manager machine 200 recognizes that the license is insufficient, the manager machine 200 may perform a process such as issuing a new license key. Note that a license shortage may be notified to the user, and a new license key may be acquired via the user.

  In the above description, as an example of the license authentication method, an authentication method using a license key has been described as an example. However, the authentication method is not limited to the above method. For example, an authentication method using a license key that requires information capable of uniquely identifying a machine or network authentication may be used. In the case of network authentication, the manager machine 200 may perform network authentication instead of the virtual machine, and notify the virtual machine of the authentication information obtained as a result.

  The operation of the manager machine 200 related to license authentication is roughly divided into the following three steps. For example, as a first step, the manager machine 200 acquires current license information of a virtual machine belonging to a network segment different from that of the manager machine 200, so that any one of the network segments to which the virtual machine having the license information belongs belongs. Request acquisition of license information to the virtual machine.

  For example, the manager machine 200 performs a new license authentication process as a second step. For example, if there are applications whose licenses are insufficient as a result of the first step, a license authentication process is performed on these applications.

  In addition, for example, as a third step, the manager machine 200, if there is information to be set in the virtual machine as a result of the license authentication process, is assigned to any virtual machine in the network segment to which the target virtual machine belongs. Request for setting license information.

  In this way, it is possible to realize license management with reduced communication volume between network segments. In addition, according to the present embodiment, it is possible to suitably cope with automatic deployment, and it is possible to suitably cope with scale-up and scale-out.

  Further, in each of the above-described embodiments and examples, the manager machine 200 has shown an example for acquiring license information from a node in a different network segment, or notifying the node of license information. Is not limited to license information.

  For example, the present invention can be suitably applied to a communication system in which a plurality of nodes belonging to the same network segment communicate with an external node that is a node on an external network.

  FIG. 23 is a block diagram showing a configuration example of a communication system according to the present invention. The communication system shown in FIG. 23 includes nodes 500-1 and 500-2 belonging to the same network segment 510, and an external node 520 belonging to a network segment different from the network segment 510.

  In such a case, each of the node 500-1 and the node 500-2 may include an information collection unit 501 and an information transmission unit 502.

  The information collecting unit 501 collects information held by other nodes in the same network segment. The information collecting unit 501 corresponds to the information collecting unit 102 and the information collection setting unit 102A in the above embodiment. However, the information collected by the information collecting unit 501 is not limited to license information.

  The information transmitting unit 502 transmits part or all of the information collected by the information collecting unit 501 to the external node 520 belonging to a network segment different from the network segment to which the own node belongs. The information transmission unit 502 corresponds to the information transmission unit 103 in the above embodiment. However, the information transmitted by the information transmitting unit 502 is not limited to license information.

  According to such a configuration, it is possible to reduce the amount of communication between network segments even in a communication system in which a plurality of nodes belonging to the same network segment communicate with an external node that is a node on the external network.

  Moreover, although a part or all of said embodiment can be described also as the following additional remarks, it is not restricted to the following.

  (Supplementary Note 1) A plurality of nodes belonging to the same network segment, each node collecting information held by other nodes in the same network segment, and a part of the information collected by the information collecting means Or an information transmission means for transmitting all to an external node belonging to a network segment different from the same network segment.

  (Supplementary note 2) The information collecting means receives a token that circulates within the same network segment, appends the information held by the own node to the received token and transmits it to other nodes, and the information transmitting means uses the token. The communication system according to supplementary note 1, wherein a part or all of the information of nodes in the same network segment collected in step S1 is transmitted to an external node.

  (Appendix 3) The information collection means issues a token that circulates in the opposite direction to the token that periodically circulates within the same network segment when the local node receives an information acquisition request from an external node, When the token that is periodically circulated and the token that circulates in the opposite direction overlap, the information transmission means is a part of the node information in the same network segment collected using the two overlapping tokens Alternatively, the communication system according to attachment 2, wherein the whole is transmitted to an external node.

  (Supplementary note 4) The communication system according to supplementary note 2 or supplementary note 3, wherein the token includes information indicating an update time when the information of the token is updated in each node.

  (Supplementary Note 5) The communication system according to any one of Supplementary Note 2 to Supplementary Note 4, wherein the information collecting unit determines a token transmission destination based on an IP address in a range specified by a subnet mask of a network segment.

  (Additional remark 6) Each node notifies the other node in the same network segment of the information notification means for notifying the content of the information setting request from the external node, and the request content notified by the information notification means. The communication system according to any one of appendix 1 to appendix 5, including information setting means for setting information according to the request content when a setting request is included.

  The information notification unit may be a part of the information collection unit.

  (Supplementary note 7) The communication system according to supplementary note 6, wherein the information notification means notifies the other node in the same network segment of the content of the information setting request from the external node using a token that circulates in the same network segment. .

  (Supplementary note 8) The communication system according to supplementary note 7, wherein the information notification unit issues a token including the content of the received setting request when the local node receives the information setting request from the external node.

  (Supplementary note 9) One node out of a plurality of nodes belonging to the same network segment issues a token that circulates within the same network segment at a predetermined timing, and each node other than the one node sequentially receives the token. Then, add the information held by the own node to the received token and send it to other nodes. When the token finishes circulating in the same network segment, either node collects the same information collected using the token. A communication method characterized by transmitting a part or all of node information in a network segment to a manager machine.

  (Supplementary Note 10) When one of a plurality of nodes belonging to the same network segment receives an information setting request from the manager machine, it is a token that circulates within the same network segment, and the received request content is Each token other than one node sequentially receives the token, determines whether the received token contains a setting request addressed to itself, and passes the received token to another A communication method characterized by transmitting to a node.

  (Supplementary Note 11) The own node belongs to a computer connected to the network and operating as a node, collecting processing for collecting information held by other nodes in the same network segment, and part or all of the collected information Execute a transmission process to send to a node belonging to a network segment different from the network segment, receive a token that circulates within the same network segment in the collection process, and add the information held by the node to the received token. A communication program characterized by causing a manager machine to transmit part or all of node information in the same network segment collected by using a token in a transmission process by transmitting to another node.

  Although the present invention has been described with reference to the exemplary embodiments and examples, the present invention is not limited to the above exemplary embodiments. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

  The present invention is preferably applicable to any system that performs communication between nodes belonging to different network segment bands.

100, 100-1 to 100-6 Node 200 Manager machine 110, 110A, 110B Network segment 101 Network I / F unit 102 Information collection unit 102A Information collection notification unit 103 Information transmission unit 104 Service application unit 105 Information setting unit 1000 Computer system 300, 300-1 to 300-6 Virtual machine 400, 400-1, 400-2 Server 330A, 330B HUB
30, 30-A, 30-B, 30-C Network 1 Public cloud environment 2 On-premises environment 500, 500-1, 500-2 Node 501 Information collection means 502 Information transmission means 510 Network segment 520 External node

Claims (12)

A plurality of nodes belonging to the same network segment, each having a plurality of nodes each holding license information,
Each of the nodes
Information collecting means for collecting license information held by other nodes in the same network segment;
A license management system comprising: information transmission means for transmitting a part or all of the license information collected by the information collection means to a manager machine belonging to a network segment different from the same network segment. The information collection means receives a token that circulates within the same network segment, adds the license information held by the own node to the received token, and transmits it to other nodes,
The license management system according to claim 1, wherein the information transmission unit transmits a part or all of license information of the nodes in the same network segment collected using the token to a manager machine. The information collection means issues a token that circulates in the opposite direction to the token that periodically circulates within the same network segment when the own node receives a license information acquisition request from the manager machine,
The information transmitting means is configured to collect license information of nodes in the same network segment collected using two overlapping tokens when a token periodically circulating and a token circulating in the opposite direction overlap. The license management system according to claim 2, wherein a part or all of is transmitted to the manager machine. The license management system according to claim 2 or 3, wherein the token includes information indicating an update time when the information of the token is updated in each node. The license management system according to any one of claims 2 to 4, wherein the information collection means determines a token transmission destination based on an IP address in a range specified by a subnet mask of a network segment. Each node
Information notifying means for notifying other nodes in the same network segment of the contents of the license information setting request from the manager machine;
The information setting means for setting license information according to the request content when the request content notified by the information notification means includes a setting request addressed to the own node. The license management system according to any one of the above. 7. The license management system according to claim 6, wherein the information notification means notifies the content of the license information setting request from the manager machine to another node in the same network segment using a token that circulates in the same network segment. . With multiple nodes belonging to the same network segment,
Each of the nodes
Information collecting means for collecting information held by other nodes in the same network segment;
A communication system, comprising: information transmission means for transmitting a part or all of the information collected by the information collection means to an external node belonging to a network segment different from the same network segment. A plurality of nodes belonging to the same network segment, wherein one of the plurality of nodes each holding license information collects license information of other nodes in the same network segment;
The license management method, wherein the one node transmits part or all of the collected license information to a manager machine belonging to a network segment different from the same network segment. One node of a plurality of nodes belonging to the same network segment collects information held by other nodes in the same network segment,
The one node transmits part or all of the collected information to an external node belonging to a network segment different from the same network segment. To a computer that is connected to the network and operates as a node that holds license information,
Processing to collect license information held by other nodes in the same network segment, and processing to send part or all of the collected license information to a manager machine belonging to a network segment different from the network segment to which the node belongs License management program for executing To a computer connected to the network and acting as a node,
Processing to collect information held by other nodes in the same network segment, and processing to transmit part or all of the collected information to an external node belonging to a network segment different from the network segment to which the own node belongs Program for communication.

Images