JP2015135547A - Application arrangement system, application arrangement method, and program of the same - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an arrangement system of an application capable of reducing the number of work hours required for the arrangement of the application having no need to register information regarding a node deploying the application and information regarding a load distribution device.SOLUTION: An application arrangement system includes: one or more AP server nodes for transmitting an update notification of application arrangement information in own node when the application archive held by an own node is made distributable to other nodes; and one or more load distribution processing nodes for registering the AP server node having transmitted the update notification as a distribution destination of a request for the application based on the update notification. The AP server node and the load distribution node have the application arrangement information common to each other by updating the application arrangement information owned by each other based on the update notification.

Description

  The present invention relates to an application deployment system that deploys an application to each node in a distributed environment in which a plurality of nodes are connected via a network.

  In recent years, distributed computing environments (hereinafter sometimes simply referred to as “distributed environments”) in which nodes having a plurality of servers and the like are connected to each other via a communication network have become widespread. In such a distributed environment, for example, an application is deployed to servers included in a plurality of nodes. Requests to the application from users and other systems are distributed according to the load of each server, etc., thereby realizing load distribution to each server.

  When deploying an application to each server device that constitutes such a distributed environment, the administrator needs to register information regarding each server to be deployed in, for example, a deployment device that deploys the application. Alternatively, the administrator needs to register the acquisition destination of the application for each server, for example. When the number of servers on which the application is deployed increases, the registration work itself may require a long time or a large man-hour that is proportional to the number of servers.

  In addition, in order to realize load balancing as described above, information related to a server that can receive a request while the application is deployed in a load balancer that distributes a request for the application to each server. Need to be notified.

  For example, when each server executes this notification, for example, the administrator needs to register information on the load balancer as a notification destination in each server. Further, when the administrator or the like performs this notification collectively, the administrator needs to collect information on each server and register it in the load balancer. In any case, such a registration work may require a long time or a large man-hour that is proportional to the number of servers.

  Furthermore, in order to distribute the load of the load balancer itself, a plurality of such load balancers may be arranged. In this case, the man-hour and time of the registration work described above may be proportional to the product of the number of servers and the number of load distribution devices.

  For this reason, a method for reducing the man-hours and time related to the application deployment as described above is required.

  In a cloud computing environment that has become widespread in recent years, a virtual computer (virtual machine) that realizes a server on which the application is deployed may be dynamically generated.

  In such an environment, information relating to a server that is dynamically generated in advance cannot be specified. Therefore, it is difficult to previously register information relating to each deployment target server in the application deployment device as described above.

  In a cloud computing environment, a virtual computer or the like that realizes the distributed device value may be dynamically generated. Even in such a case, for example, it is difficult to register in advance information related to the load balancer dynamically generated as described above in each server. Furthermore, it is also difficult to register information regarding the dynamically generated server as described above with respect to the load distribution apparatus that is dynamically generated as described above.

  For this reason, even in the cloud computing environment as described above, there is a need for a method capable of appropriately registering information related to application deployment in the server and the load balancer as described above.

  As described above, for example, there are the following patent documents as related techniques for deploying applications and the like to devices such as a plurality of servers.

  Patent Document 1 discloses a technology related to a system for updating software in a plurality of video devices connected to a network. According to the technology disclosed in Patent Literature 1, management of software installed in a reference destination device based on reference destination information in which a specific video device connected to a network is associated with another video device. Check the information. When there is a difference in management information between the specific video device and the reference destination device, the specific video device acquires necessary software and installs the software.

  According to the technique disclosed in Patent Document 1, for example, it is not necessary for an administrator or the like to install software individually for each video device. The device software is automatically updated.

    Patent Document 2 discloses a technique related to a system that distributes data including a program to each node in a network system in which a plurality of nodes are connected. According to the technique disclosed in Patent Document 2, a node connected to a network broadcasts software and version information of the node itself to other nodes. If the other node determines that the software of the other node itself needs to be updated based on the received information, the other node searches for a node that can distribute the software.

  According to the technique disclosed in Patent Document 2, each node connected to a network can know a node having a required version of software based on the broadcast information, and the software can be downloaded from the node. It can be obtained.

  Patent Document 3 discloses a technology related to a system that deploys an application for a necessary number among a plurality of application servers connected to a network. In the technique disclosed in Patent Literature 3, an application server that has received an application deployment request deploys the application to the application server itself, and transmits the deployment request to another application server. In the technique disclosed in Patent Document 3, the deployment request includes an archive of the application itself and information on the number of servers on which the application is deployed.

  According to the technique disclosed in Patent Document 3, application deployment between application servers is performed in parallel and automatically, so the management man-hour for the administrator to deploy the application individually for all servers is reduced. Is possible.

  In addition, in the update of a program (computer program) or the like in a device connected to a network, techniques for broadcasting update information are disclosed in the following Patent Documents 4 to 6.

  Patent Literature 4 discloses a technique related to an automatic program update method in an air conditioning management system. According to the technology disclosed in Patent Literature 4, a specific air conditioning controller broadcasts version information related to the program of the air conditioning controller itself to other controllers. The other air conditioning controller that has received such information determines whether or not a program update in the other air conditioning controller is necessary, and updates the program as necessary.

  Patent Document 5 discloses a technique related to patch distribution and patch application to an end user terminal. According to the technique disclosed in Patent Literature 5, a patch application program deployed in a terminal applies a patch in the terminal, and then instructs other terminals to apply the patch. In the technique disclosed in Patent Document 5, information about patches to be applied is notified all at once by broadcasting.

  Patent Document 6 discloses a technique related to a system that distributes a program from a management apparatus to a plurality of information processing apparatuses (such as an application server). In the technique disclosed in Patent Document 6, a fragment of a program is distributed by broadcast from a management device to a plurality of information processing devices. According to the technique disclosed in Patent Document 6, when there is an unreceived program fragment in a certain information processing apparatus, the information processing apparatus can receive the unreceived program fragment from another information processing apparatus. it can.

JP 2003-348515 A JP 09-073424 A JP 2012-098880 A JP 2007-079764 A JP 2008-225933 A JP 2005-222200 A

  Here, as described above, regarding the deployment of an application in a distributed environment, it is necessary to reduce the man-hours and time related to the deployment of the application.

  In addition, even when the distributed environment is configured using, for example, a dynamically generated virtual computer or the like, information regarding the deployment of the application is transmitted to a server or a load distribution device configured by the virtual computer. It is necessary to register properly.

  Each of the technologies disclosed in Patent Document 1 and Patent Document 3 described above needs to hold in advance reference destination information for acquiring software and deployment destination information for deploying an application. Therefore, when the reference destinations and the deployment destinations increase, the man-hours necessary for registering information related to them increase.

  In addition, the techniques disclosed in Patent Document 2 and Patent Documents 4 to 6 described above all distribute information necessary for updating a program or the like (including the program itself) to the update target by broadcasting. For this reason, it is not necessary to register in advance information related to the distribution source or distribution destination of the program. However, these techniques only distribute a program or the like, and do not consider the distribution of requests by the load distribution device described above.

  The present invention has been made in view of the above circumstances. That is, the present invention provides an application deployment system and the like for sharing information between nodes without registering in advance information about the nodes on which the application is deployed, for each node that constructs a distributed environment. This is the main purpose.

  In order to achieve the above object, an application deployment system according to the present invention has the following configuration. That is, the application deployment system according to the present invention includes application deployment information that associates application identification information that can uniquely identify an application with information that can identify a node that holds the application, and the application identification information and attributes related to the application. A plurality of nodes having application attribute information associated with the information are connected to each other via a communication network, and the plurality of nodes store an archive of a specific application held by the own node. When it becomes possible to distribute to other nodes included in the node, the update notification is sent based on the one or more first nodes that transmit the update notification of the application deployment information in the own node and the update notification. Sent above And the one or more second nodes that distribute the processing load according to the request by registering the node as a request distribution destination for the application, and the one or more first nodes, The one or more second nodes have the application deployment information in common by updating the application deployment information based on the update notification.

  The application deployment method according to the present invention is characterized by comprising the following configuration. That is, the application deployment method according to the present invention includes application deployment information that associates application identification information that can uniquely identify an application with information that can identify a node that holds the application, and the application identification information and attributes related to the application. A plurality of nodes having application attribute information associated with the information are connected to each other via a communication network so that the first node, which is the node, stores an archive of a specific application held by the own node When distribution to other nodes included in a plurality of nodes becomes possible, the update notification of the application deployment information in the own node is transmitted, and the second node as the node is based on the update notification. , The above update notification The received first node is registered as a request distribution destination for the application, and the one or more first nodes and the one or more second nodes are configured to deploy the application based on the update notification. It is characterized by having the above-mentioned application deployment information in common by updating the information.

  The object is also achieved by an application deployment system having the above-described configuration and a corresponding application deployment method by a computer program that realizes the computer, and a computer-readable storage medium that stores the computer program. Is done.

  According to the present invention, information related to a server on which an application is deployed is shared between nodes that construct a distributed environment by an update notification regarding the deployment status of the application. For this reason, it is not necessary to register information related to the server and information related to the load balancer in advance in the node, and the man-hours required for application deployment can be reduced.

FIG. 1 is a diagram illustrating a network configuration of an application deployment system in the first embodiment of the present invention. FIG. 2 is a block diagram illustrating a functional configuration of the application server node in the first embodiment of the present invention. FIG. 3 is a block diagram illustrating a functional configuration of the load balancer node according to the first embodiment of the present invention. FIG. 4 is a diagram illustrating a configuration of application deployment information (AP deployment information) in the first embodiment of the present invention. FIG. 5 is a diagram illustrating a configuration of application attribute information (AP attribute information) in the first embodiment of the present invention. FIG. 6 is a diagram illustrating a configuration of application archive correspondence information (AP archive correspondence information) in the first embodiment of the present invention. FIG. 7 is a diagram illustrating a configuration of request distribution destination information for an application in the first embodiment of the present invention. FIG. 8 is a flowchart showing the operation of the application deployment system in the first embodiment of the present invention. FIG. 9 is a flowchart showing the operation of the application deployment system in the first embodiment of the present invention. FIG. 10 is a diagram illustrating a specific example of the update notification transmitted by the deployment information holding unit configuring each node in the first embodiment of the present invention. FIG. 11 is a flowchart showing the operation of the application deployment system in the first embodiment of the present invention. FIG. 12 is a flowchart showing the operation of the application deployment system in the first embodiment of the present invention. FIG. 13 is a flowchart showing the operation of the application deployment system in the first embodiment of the present invention. FIG. 14 is a diagram illustrating a specific example of the update notification transmitted by the deployment information holding unit configuring each node in the first embodiment of the present invention. FIG. 15 is a flowchart showing the operation of the application deployment system in the first embodiment of the present invention. FIG. 16 is a diagram illustrating a network configuration of the application deployment system in the second embodiment of the present invention. FIG. 17 is a diagram illustrating a configuration of application attribute information (AP attribute information) in the second embodiment of the present invention. FIG. 18 is a diagram illustrating a specific example of the update notification transmitted by the deployment information holding unit constituting each node in the second embodiment of the present invention. FIG. 19 is a diagram illustrating a network configuration of the application deployment system in the fourth embodiment of the present invention. FIG. 20 is a diagram illustrating the configuration of application deployment information (AP deployment information) in the fourth embodiment of the present invention. FIG. 21 is a flowchart showing the operation of the application deployment system in the fourth exemplary embodiment of the present invention. FIG. 22 is a flowchart showing the operation of the application deployment system in the fourth embodiment of the present invention. FIG. 23 is a diagram illustrating a specific example of the update notification transmitted by the deployment information holding unit configuring each node in the fourth embodiment of the present invention. FIG. 24 is a diagram illustrating a network configuration of the application deployment system in the fifth embodiment of the present invention. FIG. 25 is a flowchart showing the operation of the application deployment system in the fifth exemplary embodiment of the present invention. FIG. 26 is a diagram illustrating a network configuration of the application deployment system in the sixth embodiment of the present invention. FIG. 27 is a block diagram illustrating a hardware configuration of an information processing apparatus capable of realizing each node constituting the application deployment system according to each embodiment of the present invention.

  Next, embodiments of the present invention will be described in detail with reference to the drawings. The configurations described in the following embodiments are merely examples, and the technical scope of the present invention is not limited thereto.

<First Embodiment>
A first embodiment of the present invention will be described with reference to FIG. FIG. 1 is a diagram illustrating a network configuration of an application deployment system according to the first embodiment of the present invention.

  As illustrated in FIG. 1, the application deployment system 100 according to the present embodiment includes one or more arbitrary application (AP) server nodes 101 (hereinafter may be referred to as “AP server nodes”) and one or more arbitrary applications. Load balancer node 102. In the present embodiment, these nodes are connected to each other via the communication network 103 so as to be communicable with each other, thereby constituting a distributed environment.

  The application deployment system in the present embodiment may further include an operation management terminal 104 and a client terminal 105, which may be connected to the communication network 103.

  In the application deployment system in the present embodiment, by deploying an application to an application server included in a specific AP server node 101 (reference numeral 204 illustrated in FIG. 2, hereinafter sometimes referred to as “AP server”), The application is also deployed on the AP server 204 included in another AP server node 101 connected to the communication network 103. A request for an application provided by the AP server 204 is received by the load balancer node 102, and the load balancer (reference numeral 303 in FIG. 3) of the load balancer node 102 distributes the request to each AP server 204. .

  Hereinafter, each component will be described.

  Next, the “node” (the AP server node 101, the load playing device node 102, or the like) in the present embodiment is configured by an information processing device such as a computer that is communicably connected to the communication network 103, for example. It may be a processing device that provides a function, or a collection of such processing devices.

  Such a node may be constituted by, for example, a plurality of information processing apparatuses connected to be communicable with each other, or may be constituted by a single information processing apparatus. Moreover, you may comprise all or one part of the information processing apparatus which comprises the said node with a virtual computer (virtual machine).

  Part or all of the constituent elements of each node described below may be configured by a software program (computer program) executed in the information processing apparatus.

  Next, the configuration of the AP server node 101 will be described with reference to FIG.

  The AP server node 101 in this embodiment includes a deployment status management unit 201, a deployment control unit 202, an application management unit (hereinafter also referred to as “AP management unit”) 203, and an AP server 204. Hereinafter, the above may be collectively referred to as “components of the AP server node 101”.

  The components of the AP server node 101 are communicably connected to each other, and are also communicably connected to the communication network 103 as necessary.

  The components of the AP server node 101 may be realized by using information processing apparatuses such as independent computers, or may be realized by using a single information processing apparatus that is integrated in whole or in part. May be. In this case, the information processing apparatus may be a computer having a physical entity or a virtual machine constructed in a virtual machine environment.

  Next, each component of the AP server node 101 will be described.

  The deployment status management unit 201 includes a deployment status holding unit 201a and a deployment status transmission / reception unit 201d. In the present embodiment, the deployment status holding unit 201a and the deployment status transmission / reception unit 201d are communicably connected.

  As illustrated in FIG. 4, the deployment status holding unit 201a includes an application ID (Identifier) that is identification information that can uniquely identify an application (reference numeral 401 in FIG. 4), and an AP server node on which the application is deployed. AP deployment information 201b that associates the address 101 (reference numeral 402 in FIG. 4).

  Note that the AP deployment information 201b may include information that associates an address of an AP server 204 (described later) with an application ID instead of the address of the AP server node 101.

  Here, the application ID in the present embodiment is identification information assigned to an application so that applications having the same application ID become the same application. The application ID may be a unique ID for all nodes.

  The address of the AP server node 101 is a network address that can be connected to the AP server node in the communication network 103 described later. For example, when the IP protocol is adopted in the communication network 103 described later, an IP address may be adopted as the network address.

  Further, as illustrated in FIG. 5, the deployment status management unit 201 uses the application ID (reference numeral 501 in FIG. 5) and a resource path (in the AP server on which the application is deployed) for accessing the application ( AP attribute information 201c is associated with the reference numeral 502) in FIG.

  As such a resource path, for example, URI (Uniform Resource Identifier) or URL (Uniform Resource Locator) may be adopted as identification information that can uniquely identify a specific resource. In this case, it is possible to access the application by accessing the resource path (URL or the like). Note that the information on the resource path may be included in an application archive to be described later.

  Here, the deployment information holding unit 201a in the present embodiment may store the AP deployment information 201b and the AP attribute information 201c described above in an arbitrary format. That is, the deployment information holding unit 201a may store these pieces of information using an arbitrary database or the like, or may store them in a format such as a simple correspondence table.

  Next, the deployment status transmission / reception unit 201b uses the deployment status transmission / reception unit 201d to update all other nodes connected to the communication network 103 when the AP deployment information 201b or the AP attribute information 201c is updated. In response, a deployment status update notification is sent.

  Further, the deployment status transmission / reception unit 201d receives the update notification transmitted from another node, and updates the AP deployment information 201b or the AP attribute information 201c as necessary.

  The deployment status management unit 201 instructs other components of the AP server node 101 to execute necessary processing when the distribution status transmission / reception unit 201d transmits / receives the update information. For example, when the update notification is received from another node, the deployment management unit 202 described later may be instructed to execute the deployment of the application related to the update notification. The specific operation of the deployment status management unit 201 in this embodiment will be described later.

  Next, the AP management unit 203 will be described. The AP management unit 203 in the present embodiment includes an application holding unit (hereinafter also referred to as “AP holding unit”) 203a and an application transmission / reception unit (hereinafter also referred to as “AP transmission / reception unit”) 203d. Have.

  As illustrated in FIG. 6, the AP holding unit 203 a is application archive correspondence information that is information that associates the application ID (reference numeral 601 in FIG. 6) described above with the archive file (reference numeral 602 in FIG. 6) of the application. (Hereinafter referred to as “AP archive correspondence information”) 203b.

Here, the information on the archive file of the application (reference numeral 602 in FIG. 6) may be any information that can identify the archive file of the application held by the AP management unit 203, for example. As such information, for example, a path on a file system where the archive file is arranged may be used, or an index (key) of a database in which the archive file is registered may be used.

  The AP holding unit 203a holds an archive file (hereinafter also referred to as “AP archive”) 203c of an application deployed in the own node.

  Here, the AP holding unit 203a may hold the AP archive 203c and the AP archive correspondence information 203b in an arbitrary format. That is, the AP holding unit 203a may hold such information using, for example, an arbitrary database.

  Next, the AP transmitting / receiving unit 203d transmits / receives an application archive file between the other AP server node 101 and the own node. The AP transmission / reception unit 203d may pass the archive file of the application received from another AP server node 101 to the AP holding unit 203a, and the AP holding unit 203a may hold the archive concerned.

  Next, the deployment management unit 202 will be described. The deployment management unit 202 in the present embodiment includes a deployment control unit 202a, a deployment determination unit 202b, and a deployment execution unit 202c. In the present embodiment, the deployment control unit 202a, the deployment determination unit 202b, and the deployment execution unit 202c are connected so as to communicate with each other. The specific operation of the deployment management unit 202 will be described later.

  When the information (AP deployment information 201b or AP attribute information 201c) held by the deployment status holding unit 201a is updated, the deployment control unit 202a acquires an application related to the update from another node. In addition, the deployment control unit 202a inquires of the deployment determination unit 202b whether or not to deploy the acquired application to the application server 204 of its own node to be described later. Furthermore, when it is determined that the application is to be deployed as a result of the inquiry, the deployment control unit 202a instructs the deployment execution unit 202c to deploy the application.

  In response to the inquiry from the deployment control unit 202a, the deployment determination unit 202b determines whether to deploy a specific application to the AP server 204 in the own node. For example, the deployment determination unit 202b checks the deployment status of the specific application inquired from the deployment control unit 202a in its own node, and determines whether to deploy the application based on the deployment status. Good.

  The deployment execution unit 202c deploys the application instructed from the deployment control unit 202a to the application server 204 in its own node. Specifically, the deployment execution unit 202c performs necessary settings by appropriately expanding an archive of the instructed application by an appropriate method so that the application server 204 can execute the archive.

  Next, the AP server 204 in this embodiment will be described. The AP server 204 executes the application deployed on the AP server 204 and provides a service by the application. For example, the AP server 204 may provide a service to the client terminal 105 by executing an application in response to a request transmitted from the client terminal 105.

  Here, a specific method for deploying a specific application on the AP server 204, a specific method for confirming the deployment status of the application, and the like differ depending on the type of the application or the type of the AP server 204. There is.

  For this reason, in the present embodiment, for the AP server node 101, the deployment determination unit 202b and the deployment execution unit 202c are appropriately and appropriately set for each type of AP server 204 and each type of application deployed on the AP server 204. It may be changed or adjusted. That is, when there are a plurality of AP server nodes 101 having different types of AP servers 204, the preparation determination unit 202 b and the deployment execution unit 202 c may be different in each AP server node 101. In this case, the components other than the above-described preparation determination unit 202b and the deployment execution unit 202c may be common to the AP server nodes 101.

  The specific operation of the AP server node 101 in the present embodiment described above will be described later.

  Next, the load balancer node 102 in this embodiment will be described with reference to FIG.

  The load balancer node 102 in this embodiment includes a deployment status management unit 201, a load distribution target management unit 302, and a load balancer 303. Hereinafter, the above may be collectively referred to as “components of the load balancer node 102”.

    The components of the load balancer node 102 are communicably connected to each other, and are also communicably connected to the communication network 103 as necessary.

  The components of the load balancer node 102 may be realized by using information processing apparatuses such as independent computers, or may be realized by using a single information processing apparatus in which all or part of them are integrated. May be. In this case, the information processing apparatus may be a computer having a physical entity or a virtual machine constructed in a virtual machine environment.

  Next, each component of the load balancer node 102 will be described.

  First, the deployment status management unit 201 may have the same configuration as the deployment status management unit 201 in the AP server node 101 described above. That is, the deployment status transmission / reception unit 201d and the deployment status holding unit 201a included in the deployment status management unit 102 configuring the load balancer node 102 are respectively arranged in the deployment status transmission / reception unit 201d included in the deployment status management unit 201 configuring the AP server node 101. And it may be equivalent to the deployment status holding unit 201a.

  When the deployment status transmission / reception unit 201d in the deployment status management unit 201 constituting the load balancer node 102 receives the deployment status update notification from another node, similar to the deployment status transmission / reception unit 201d in the AP server node 101, The AP deployment information 201b or the AP attribute information 201c is updated as necessary.

  Here, the AP deployment location information 201b and the AP attribute information 201c in the deployment status holding unit 201a configuring the load distribution processing node 102 are respectively the AP deployment information 201b and the AP deployment information 201b in the distribution status holding unit 201a configuring the AP server node 101. , Information equivalent to the AP attribute information 201c is held.

  Further, the deployment status management unit 201 configuring the load balancer node 102 executes necessary processing on other components of the load balancer node 102 when the distribution status transmission / reception unit 201d transmits / receives the update information. Instruct. For example, when the update notification is received from another node, the load distribution target management unit 302 described later may be instructed to execute a load distribution destination registration process. A specific operation of the load distribution target management unit 302 will be described later.

  Next, the load distribution target management unit 302 will be described. The load distribution target management unit 302 according to the present exemplary embodiment is configured such that when information (AP deployment information 201b, AP attribute information 201c, etc.) held by the deployment status management unit 201 is updated, Register the distribution destination (request distribution destination) or cancel the registration. The load distribution target management unit 302 may execute the load distribution destination registration process based on the instruction from the deployment status management unit 201 described above.

  Next, the load balancer 303 will be described. The load balancer 303 is connected to the communication network 103 and receives a request for a specific application transmitted from the client terminal 105 or the like. The load balancer 303 holds request distribution information 303a in which information related to the load distribution destination is registered.

  As illustrated in FIG. 7, the request distribution information 303 a includes a resource path for accessing a specific application (reference numeral 701 in FIG. 7) and a request distribution destination for the resource path (reference numeral 702 in FIG. 7). Corresponding information is held in association.

  The information indicating the request distribution destination (reference numeral 702 in FIG. 7) may use the address of the AP server node 101 in which the application that is the target of the request is deployed, as illustrated in FIG. .

  Here, the load distribution apparatus 303 may store the request distribution information 303a in an arbitrary format. That is, the load distribution apparatus 303 may store the request distribution information 303a using an arbitrary database or the like, or may store the request distribution information 303a in a format such as a simple correspondence table. The specific format of the request distribution information 303a may be different for each load distribution processing device 303, for example.

  Here, when there are a plurality of types of the load distribution device 303, a specific registration method of a distribution destination for the request distribution information 303 a may be different for each type of the load distribution device 303.

  Therefore, in the present embodiment, the load distribution target management unit 302 may be appropriately changed or adjusted for each type of the load distribution device 303 for the load distribution device node 102. That is, when there are a plurality of load distribution apparatus nodes 102 having different types of load distribution apparatuses 303, the load distribution target management units 302 may be different in each load distribution apparatus node 102. In this case, components other than the load distribution target management unit 302 may be common to the load distribution apparatus nodes 102.

  The specific operation of the load balancer node 102 in the present embodiment described above will be described later.

  Next, the communication network 103 in this embodiment will be described. The communication network 103 in the present embodiment has a configuration capable of communicating between the above-described nodes and capable of transmitting information with all nodes connected to the communication network 103 as destinations. Any communication network.

  In the communication network 103 according to this embodiment, by assigning an address to a specific node, the address can be accessed by using the address as destination information.

  On the other hand, in the communication network 103 according to the present embodiment, destination information (such as the above address) relating to a specific destination node is not required when information is transmitted to all the nodes.

  As such a communication network 103, for example, a LAN (Local Area Network) that is a local communication network adopting IP (Internet Protocol), a virtual LAN (Virtual LAN: VLAN), the Internet that is a wide area communication network, or the like is adopted. May be.

  When the LAN or the like is adopted as the communication network 103, for example, information is transmitted to all nodes connected to the communication network 103 by transmitting a multicast packet (IP multicast) or a broadcast packet. Is possible. In this case, it is possible to transmit information to all nodes without specifying destination information (such as a network address) regarding a specific node.

  Next, the operation terminal 104 in this embodiment will be described. The operation terminal 104 in the present embodiment is communicably connected to the communication network 103. An operation manager (not shown) may execute application deployment (or deployment instruction) to a specific AP server node 101 via the operation terminal 104, for example. In the present embodiment, whether or not the operation terminal 104 is provided is arbitrary.

  Next, the operation of the application deployment system in this embodiment will be described with reference to the drawings. In the following description, as illustrated in FIG. 1, m AP server nodes 101 may be identified as AS100, AS200,... ASm00. Further, the n load balancer nodes 102 may be identified as LB100, LB200,..., LBn00.

  First, an operation manager (not shown) responsible for application deployment deploys a specific application to one of the m AP server nodes 101. In the following description, as a specific example, a case will be described in which the operation manager deploys a specific application A to the AS 100 that is the AP server node 101. Hereinafter, the operation of the AP server node 101 (AS 100) in this case will be described with reference to the flowchart illustrated in FIG.

  First, an operation manager (not shown) instructs the AP server node 101 (AS 100) to deploy a specific application A (step S801).

  In this case, the operation manager (not shown) transmits, for example, the archive body of the specific application A and information necessary for deployment of the application to the AP server node 101 (AS 100) via the operation terminal 104, Deployment of the application A may be instructed. Note that the information necessary for deployment of the application A may include, for example, the ID of the application A, the resource path of the deployment destination, and the like.

  Next, the deployment execution unit 202c in the AP server node 101 (AS100) receives an archive of application A from the operation manager (step S802). Specifically, the deployment execution unit 202 c may receive the archive of the application A transmitted by the operation manager via the communication network 103.

  Next, the deployment execution unit 202c stores the archive of the application A in the AP holding unit 203a in the AP management unit 203 (Step S803). The deployment execution unit 202c may, for example, pass the ID of the application A and the archive body to the AP management unit 203 and instruct to hold the archive.

  Here, the AP holding unit 203a stores the delivered application A archive as the AP archive 203a, and updates the AP archive correspondence information 203b using the archive main body information and the application A ID.

  Next, the deployment execution unit 202c deploys application A on the AP server 204 (step S804). Here, the specific deployment method of the application A may be appropriately selected according to the type of the application A and the type of the AP server 204.

  Next, the deployment execution unit 202c notifies the application ID of the application A deployed in step S804, the resource path, the address of the own AP server node 101 (AS100), and the deployment status management unit 201 (step S805). .

  Here, the application ID and the resource path related to the application A may be delivered together with the archive of the application A from an administrator (not shown) in step S801, or may be delivered as a part of the archive.

  As another example, for example, the deployment management unit 202, the deployment status management unit 201, and the like may generate an application ID and a resource path related to the application A.

  Next, the deployment status management unit 201 updates the AP deployment information 201b and the AP attribute information 201c, and transmits an update notification related to the update (step S806).

  Hereinafter, the details of the processing in step S806 will be described with reference to the flowchart illustrated in FIG.

  The deployment status holding unit 201a associates the application ID notified in step S805 with the address of the own AP server node 101 (AS 100) and registers it in the AP deployment information 201b (step S901).

  Next, the deployment status holding unit 201a creates an update notification including update information of the AP deployment information 201b (step S902). The created update notification is transmitted to another node in a process described later.

  Next, the deployment status holding unit 201a confirms the AP attribute information 201c, and confirms whether the information of the same application ID as that of the application (application A) notified in step S805 has been registered (step S903, step S903). S904).

  If the information of the same application ID is registered as a result of the confirmation in step S903 (YES in step S904), the deployment status holding unit 201a executes step S907 described later.

  On the other hand, as a result of the confirmation in step S903, if the same application ID information is not registered (NO in step S904), the deployment status holding unit 201a determines the application ID, the resource path, and the information notified in step S805. Are registered in the AP attribute information 201c (step S905).

  Next, the deployment status holding unit 201a creates update information of the AP attribute information 201c in step S902 and adds it to the update notification (step S906).

  Next, the deployment status holding unit 201a instructs the deployment status transmission / reception unit 201d to transmit the update notification to all the nodes connected to the communication network 103 (step S907). The deployment status transmission / reception unit 201d transmits the update notification by an appropriate method according to the specifications of the communication network 103. Specifically, the deployment status transmission / reception unit 201d may transmit the update notification by, for example, a multicast packet or a broadcast packet.

  A specific example of the update notification is illustrated in FIG. In the specific example illustrated in FIG. 10, the content of the update notification is represented in a comma-separated format. The expression format of the update notification is limited to this, and any format that can be interpreted on the side of transmitting and receiving the update notification may be adopted. For example, a notation such as XML may be adopted.

  The flowcharts illustrated in FIGS. 8 and 9 described above represent the operation of the application deployment system in the present embodiment when the application A is deployed to a specific AP server node 101 (AS 100).

  Next, the operation of another AP server node 101 (AS200 to ASm00) that has received the update notification transmitted from the AP server node 101 (AS100) in step S907 will be described. Hereinafter, as a representative example of the other AP server node 101, a case where the AP server node 101 (AS 200) receives the update notification from the AP server node 101 (AS 100) will be described.

  FIG. 11 is a flowchart illustrating the operation of the AP server node 101 (AS 200) that has received the update notification.

  First, the deployment status management unit 201 of the AP server node 101 (AS 200) receives the update notification transmitted from the AP server node 101 (AS 100), and updates information related to the deployment status based on the update notification (step S1). S1101). Details of the processing in step S1101 will be described using the flowchart illustrated in FIG.

  First, the deployment status transmission / reception unit 201d constituting the deployment status management unit 201 of the AP server node 101 (AS200) receives the update notification transmitted in step S907 illustrated in FIG. 9 by the AP server node 101 (AS100) described above. (Step S1201). The deployment status transmission / reception unit 201d may notify the received update notification to the deployment status holding unit 201a.

  The deployment status holding unit 201a constituting the deployment status management unit 201 of the AP server node 101 (AS 200) analyzes the notified update notification and updates the AP deployment information 201b (step S1202). Specifically, the deployment status holding unit 201a associates the application ID of the application A and the address of the AP server node 101 (AS 100) included in the update notification and registers them in the AP deployment information 201b.

  Next, the deployment status holding unit 201a in the AP server node 101 (AS200) confirms whether or not the received update notification includes update information regarding the AP attribute information 201c (steps S1203 and S1204).

  As a result of the confirmation in step S1203, when the received update notification does not include update information related to the AP attribute information 201c (NO in step S1204), the deployment status holding unit 201a is described later in step S1102 (reference numeral S1102 in FIG. 11). Continue processing from.

  On the other hand, when the received update notification includes update information related to the AP attribute information 201c (YES in step S1204), the deployment status holding unit 201a updates the AP attribute information 201c based on the received update notification. . Specifically, the deployment status holding unit 201a associates the ID of the application A included in the update notification with the resource path of the application A and registers it in the AP attribute information 201c (step S1205).

  After the process in step S1205 is completed, the deployment status holding unit 201a in the AP server node 101 (AS200) continues the process from step S1102 illustrated in FIG.

  Referring to the flowchart of FIG. 11 again, the deployment status holding unit 201a in the AP server node 101 (AS200) deploys the ID of the application A added to the AP deployment information 201b and the address of the AP server node 101 (AS100). The control unit 202a is notified (step S1102). At this time, the deployment status holding unit 201a may instruct the deployment control unit 202a to execute the deployment process of the application A.

  The deployment control unit 202a in the AP server node 101 (AS 200) determines whether or not the deployment process has already been performed for the application having the same ID as the application ID notified in step S1102 (steps S1103 and S1104).

  If the result of determination in step 1103 is that application deployment processing is being executed with the same ID (YES in step S1104), the deployment control unit 202a ends the processing.

  On the other hand, if the result of determination in step 1103 is that application deployment processing is not being executed with the same ID, the deployment control unit 202a sends the deployment determination unit 202b to the AP server 204 of its own node (AS200). It is requested to determine whether the application (application A) needs to be deployed. (Step S1105).

  The deployment determination unit 202b in the AP server node 101 (AS200) determines whether application A needs to be deployed based on the status of the AP server 204 in the own node (AS200) (step S1106).

  Specifically, when the same application as application A has already been deployed on AP server 204, deployment determining unit 202b determines that further deployment of application A is not necessary (NO in step S1107). If NO in step S1107, the deployment control unit 202a ends the process.

  On the other hand, if the same application as application A is not already deployed on AP server 204, deployment determining unit 202b determines that deployment of application A is necessary (YES in step S1107).

  If YES in step S1107, the deployment control unit 202a acquires application A from the node where application A has already been deployed (step S1108).

  Hereinafter, the process in step S1108 will be described with reference to the flowchart illustrated in FIG.

  First, the deployment control unit 202a acquires address information of all nodes from which the target application (in this case, application A) can be acquired from the deployment status holding unit 201a (step S1301).

  Specifically, the deployment control unit 202a notifies, for example, the ID of the application (in this case, application A) to be acquired to the deployment information holding unit 201a. Upon receiving the notification, the deployment information holding unit 201a refers to the AP deployment information, extracts the address information of the other AP server node 101 associated with the ID of the application, and notifies the deployment control unit 202a.

  Next, the deployment control unit 202a repeats the following steps S1303 to S1307 for all node addresses acquired in step S1301 (steps S1302 to S1308).

  In the following, it is assumed that the AP server node from which the application A is acquired is Ask00.

  The deployment control unit 202a in the AP server node 101 (AS200) notifies the AP transmission / reception unit 203d in the AP server node 101 (AS200) of the application ID of the application A to be acquired and the address of the AP server node 101 (ASk00). The application A is instructed to be acquired (step S1303).

  Next, the AP transmission / reception unit 203d in the AP server node 101 (AS200) transmits the application ID to the application transmission / reception unit 203d in the AP server node 101 (ASk00) notified in step S1303, and archives the application. Is requested to be transmitted (step S1304).

  Specifically, the AP transmission / reception unit 203d in the AP server node 101 (AS200) transmits data representing the request, a command, or the like to the application transmission / reception unit 203d in the AP server node 101 (ASk00).

  The AP transmission / reception unit 203d in the AP server node 101 (ASk00) receives the request transmitted from the AP transmission / reception unit 203d in the AP server node 101 (AS200), and determines whether or not the requested application archive can be distributed ( Step S1305).

  In this case, the AP transmission / reception unit 203d in the AP server node 101 (ASk00) may determine whether or not the application can be archived based on, for example, the load status of the AP management unit 203 in the AP server node 101 (ASk00).

  More specifically, for example, the AP transmission / reception unit 203d in the AP server node 101 (ASk00) determines that distribution is possible when there are not too many archive distribution requests (requests) to the AP management unit 203 in the own node (ASk00). (YES in step S1306).

  In this case, the AP transmission / reception unit 203d in the AP server node 101 (ASk00) ends the repeating process of steps S1302 to S1308, and continues the process from step S1310. The processing after step S1310 will be described later.

  On the other hand, the AP transmission / reception unit 203d in the AP server node 101 (ASk00) may determine that the distribution is impossible when there are too many requests (requests) for archive distribution to the AP management unit 203 in the own node (ASk00) ( In step S1306, NO).

  In this case, the AP transmission / reception unit 203d in the AP server node 101 (ASk00) rejects the application A archive transmission request received from the AP transmission / reception unit 203d in the AP server node 101 (AS200) in step S1305 (step S1307). ).

  If the address information of all the nodes acquired in step S1301 includes an address for which the application A archive acquisition processing has not been executed, the deployment control unit 202a in the AP server node 101 (AS200) The processing is repeated from step S1303 (step S1308).

  When the archive acquisition process of application A is executed for all addresses included in the address information of all nodes acquired in step S1301, the deployment control unit 202a in the AP server node 101 (AS200) The request is rejected from the server node. In this case, the deployment control unit 202a in the AP server node 101 (AS 200) waits for processing until a new update notification is received from the deployment status management unit 201 of another node or a certain time has elapsed (step S1309).

  After the process in step S1309, the deployment control unit 202a in the AP server node 101 (AS200) continues the process from step S1301.

  In step S1305, the application archive distribution may be determined based on an arbitrary criterion without being limited to the above-described example.

  Next, processing after step S1310 will be described.

  The AP transmission / reception unit 203d in the AP server node 101 (ASk00) acquires the archive of the application A requested in step S1305 from the AP holding unit 203a in the own node (ASk00) (step S1310).

  Next, the AP transmission / reception unit 203d in the AP server node 101 (ASk00) transmits the application archive acquired in step S1310 to the AP transmission / reception unit 203a in the AP server node 101 (AS200) (step S1311). Here, as described above, the AP transmission / reception unit 203a in the AP server node 101 (AS 200) is a request source that has requested transmission of the archive of the application A.

  Next, the AP transmission / reception unit 203a in the AP server node 101 (AS200) stores the application ID and the application archive in the AP holding unit 203a of the own node (AS200) (step S1312).

  In this case, the AP holding unit 203a stores the archive file main body of the application, and updates the AP archive correspondence information 203b using the information on the archive main body and the ID of the application A.

  Next, the AP transmission / reception unit 203a in the AP server node 101 (AS200) passes the application archive to the deployment control unit 202a in the AP server node 101 (AS200) (step S1313).

  Hereinafter, the deployment control unit 202a in the AP server node 101 (AS 200) continues the process from step S1109 illustrated in FIG.

  Referring to the flowchart illustrated in FIG. 11 again, the deployment control unit 202a in the AP server node 101 (AS 200) deploys the archive of application A acquired in step S1108 (steps S1301 to S1313 illustrated in FIG. 13). The data is transferred to the execution unit 202c (step S1109).

  The deployment execution unit 202c in the AP server node 101 (AS200) deploys application A to the AP server 204 using the archive of application A (step S1110). Here, the specific deployment method of the application A may be appropriately selected according to the type of the application A and the type of the AP server 204.

  The deployment execution unit 202c in the AP server node 101 (AS200) notifies the application ID of the application A deployed in step S1110, the resource path, the address of the own AP server node 101 (AS200), and the deployment status management unit 201. (Step S1111).

  Next, the deployment status management unit 201 in the AP server node 101 (AS 200) updates the AP deployment information 201b and the AP attribute information 201c, and transmits an update notification related to the update (step S1112).

  The process in step S1112 may be the same as the process in steps S901 to S907 in FIG. 9 described above, and thus the description thereof is omitted. However, since the same application information already exists in the AP attribute information 201c in the AP server node 101 (AS200), only the AP deployment information 201b is updated. Therefore, the update notification has, for example, the content illustrated in FIG. 14, and only the update of the AP deployment information is notified.

  Next, the operation of the load balancer node 102 in this embodiment will be described with reference to FIG. FIG. 15 is a flowchart illustrating the operation of the load balancer node 102 in this embodiment.

  In the following, the AP server node 101 (AS100) transmits an update notification of the AP deployment information 201b or AP attribute information 201c in the node to all other nodes, and the load balancer node 102 (LB100). ) Will be described as a specific example. Further, in the following specific example, a case will be described in which the AP server node 101 (AS 100) transmits an update notification indicating that the application A has been deployed.

  First, the deployment status management unit 201 in the load balancer node 102 (LB 100) receives the update notification transmitted from the deployment status management unit 201 in the AP server node 101 (AS 100), and updates the information held by itself ( Step S1501).

  More specifically, the deployment status transmission / reception unit 201d in the load balancer node 102 (LB100) receives the update information transmitted from the deployment status transmission / reception unit 201d in the AP server node 101 (AS100). Then, the deployment status transmission / reception unit 201d in the load balancer node 102 (LB100) notifies the received update information to the deployment status holding unit 201a in the load balancer node 102 (LB100). Based on the notification, the deployment status holding unit 201a in the load balancer node 102 (LB 100) updates the AP deployment information 201b and the AP attribute information 201c held by itself, as necessary.

  The process described above may be the same as the process described in steps S1201 to S1205 in FIG.

  Next, the deployment status holding unit 201a in the load balancer node 102 (LB100) sends the application ID and node address registered in the AP deployment information 201b in step S1501 to the load balancing target management unit 302 in the own node (LB100). Notice. In this specific example, the application ID is the ID of application A, and the node address is the address of the AP server node 101 (AS100).

  The deployment status holding unit 201a in the load balancer node 102 (LB 100) further instructs the load balancing target management unit 302 to execute the load balancing destination node registration process (step S1502).

  Next, the load distribution target management unit 302 in the load balancer node 102 (LB100) associates with the application ID of the application A registered in the AP attribute information 201c from the deployment status holding unit 201a in the own node (LB100). The obtained resource path is acquired (step S1503).

  In this case, for example, the load distribution target management unit 302 may notify the deployment status holding unit 201a of the application ID and acquire the resource path associated with the ID. Further, the load distribution target management unit 302 may acquire the resource path associated with the application ID by directly referring to the AP attribute information 201c.

  Next, the load distribution target management unit 302 acquires the address of the AP server node 101 notified in step S1502 to the load distribution device 303 of the local node (load distribution device node 102 (LB200)) and the acquisition in step S1502. The resource path thus registered is registered as a request distribution destination for the application (step S1504).

  In this specific example, the load distribution target management unit 302 notifies the load distribution apparatus 303 of the resource path of application A and the address of the AP server node 101 (AS 100) to the load distribution apparatus 303. Then, the load balancer 303 associates the resource path with the address of the AP server node 101 and registers it in the request distribution information 303a.

  As described above, according to the application deployment system in the present embodiment, when a specific application (for example, application A) is first arranged in a specific AP server node 101 (for example, AS 100), the AP server node 101 (AS 100) is arranged. ) Notify all nodes of updates related to application placement information.

  The other AP server node 101 (for example, AS 200) acquires the application archive from the other node based on the notification, and deploys the application to the AP server 204 of its own node.

  Further, the load balancer node 102 (for example, BL100) registers the address and resource path of the AP server node on which the application is deployed in the load balancer 303 based on the notification.

  For this reason, it is possible to deploy an application without having to register in advance information related to the AP server node 101 (for example, AS100) that is the distribution source in the AP server node 101 (for example, AS200) that is the deployment destination of the application.

Similarly, it is not necessary to register in advance information regarding the AP server node 101 (for example, AS 200) that is the application deployment destination in the distribution source AP server node 101 (for example, AS 100), and the application can be deployed. According to the application deployment system in the present embodiment, the information on the AP server node 101 (for example, AS100 or AS200) on which the application is deployed is registered in advance in each load balancer node 102 (for example, LB100), and these load distributions are performed. The device node 102 can add information related to a request distribution destination. Similarly, it is not necessary to register in advance the information of each load balancer node 102 (for example, LB100) in the AP server node 101 where the application is deployed.

  As described above, according to the application deployment system in the present embodiment, by deploying an application to one AP server node 101, the same application is automatically deployed to all other AP server nodes 101. Request distribution targets are automatically registered in the load balancer node 102.

  Therefore, according to the application deployment system in the present embodiment, since it is not necessary to register in advance information regarding other AP server nodes 101 in each AP server node 101, the man-hour required for registering these information can be reduced. Further, since it is not necessary to register the information of the load balancer node 102 in each AP server node 101 in advance, and it is not necessary to register the information of each AP server node 101 in the load balancer node 102 in advance. Man-hours required for registration can be reduced.

  Further, according to the application deployment system in the present embodiment, even when the AP server node 101 and the load balancer node 102 are dynamically generated by a virtual machine or the like, the update notification is transmitted to these nodes. The Therefore, even when the AP server node 101 and the load balancer node 102 are dynamically generated, it is possible to deploy applications and distribute requests for load balancing without registering each other's information in advance. It is.

  Furthermore, according to the application deployment system in the present embodiment, the AP server node 101 to which the application is deployed becomes a new distribution source of the application, and therefore the time required to deploy the application to all the AP server nodes 101. Can be shortened. In addition, such an operation can prevent requests for acquiring an application archive from being concentrated on a specific AP server node.

<Second Embodiment>
Next, a second embodiment of the present invention will be described. In the following description, the characteristic parts according to the present embodiment will be mainly described, and the same reference numerals will be given to the same configurations as those in the first embodiment described above, and the redundant description will be omitted. To do.

  The application deployment system 100 according to the present embodiment is different from the first embodiment in that it includes a plurality of AP server nodes 101 having AP servers 204 that provide different functions. Hereinafter, the difference will be mainly described.

  First, in the present embodiment, the function provided by the AP server 204 in each of the m AP server nodes 101 illustrated in FIG. 1 may be different for each AP server 204. In this case, the applications that can be deployed to each AP server differ depending on the function provided by each AP server 204.

  Therefore, in the present embodiment, as illustrated in FIG. 16, the AP attribute information 1601 held by the deployment status holding unit 201 a configuring each node (the AP server node 101 and the load balancer node 102) is included in the AP attribute information 1601. An item related to the function of the AP server 204 required by a specific application is added.

  In the item regarding such a function, for example, a web server function, a specific program (computer program) or script execution function, a database function, or the like may be specified. That is, any function that needs to be provided in order for the AP server 204 to execute a specific application may be designated.

  As illustrated in FIG. 17, the AP attribute information 1601 in the present embodiment requires an application corresponding to a specific application ID (reference numeral 501 in FIG. 17) compared to the AP attribute information 201 c in the first embodiment. And a request function (reference numeral 1701 in FIG. 17).

  The operation of the application deployment system according to this embodiment configured as described above will be described below.

  First, when the AP attribute information 1601c is updated, the deployment status transmission / reception unit 201d in each AP server node 101 creates an update notification including information on the requested function registered in the AP attribute information 1601. Send to. A specific example of the update notification in this case is illustrated in FIG. In this case, an item “requirement” corresponding to the requested function is added to the update notification.

  Next, the other AP server node 101 that has received the update notification deploys an application related to the update notification to its own node as necessary, as in the first embodiment.

  Here, in the present embodiment, the deployment control unit 202a and the deployment determination unit 202b in the other AP server node 101 confirm the request function 1701 in the AP attribute status 1601 updated by the update notification.

  As a result of the confirmation, if the AP server 204 in the own node can provide the function described in the request function 1701, the deployment control unit 202a executes the deployment so as to deploy the application to the AP server 204 in the own node. You may instruct | indicate to the part 202c.

  The other operations of the application deployment system in the present embodiment are the same as those in the first embodiment.

  As described above, in this embodiment, whether the AP server 204 in the own node satisfies the required function by adding the required function required by a specific application to the AP attribute information 1601 of each node. Can be determined.

  For this reason, by controlling the application to be deployed when the required function is satisfied, the application can be appropriately deployed even when a plurality of AP servers 204 having different functions to be provided are mixed.

<Third Embodiment>
Next, a third embodiment of the present invention will be described. In the following description, characteristic portions according to the present embodiment will be mainly described, and the same configurations as those in the above-described embodiments will be denoted by the same reference numerals, and redundant description will be omitted.

  The application deployment system 100 according to the present embodiment is the same as the first embodiment except for the operations of the deployment control unit 202a and the deployment determination unit 202b in the deployment management unit 202 configuring the AP server node 101. Only such differences will be described below.

  In the present embodiment, the deployment determination unit 202b inquires from the deployment control apparatus 202a whether the application needs to be deployed. If the application cannot be immediately deployed to the AP server 204 in the own node (AP server node 101), “deployment pending” is set. Notify the deployment control device 202a.

  The deployment control apparatus 202a suspends the application ID of the application determined to be “deployment pending” and ends the process. For example, the deployment control apparatus 202a may register the ID in a hold queue (not shown).

  After a certain period of time, the deployment control apparatus 202a takes out the application ID of the application that has been put on hold, and requests the deployment determination apparatus 202b again to determine whether deployment is necessary.

  The other operations of the application deployment system in the present embodiment are the same as those in the first embodiment.

  As described above, in the application deployment system (particularly, the AP server node 101) in the present embodiment, the deployment of the application to the AP server 204 can be temporarily suspended.

  For this reason, in the present embodiment, for example, when the specific AP server 204 is in a high load state, it is possible to avoid further increase in load by performing the deployment process.

<Fourth Embodiment>
Next, a fourth embodiment of the present invention will be described. In the following description, characteristic portions according to the present embodiment will be mainly described, and the same configurations as those in the above-described embodiments will be denoted by the same reference numerals, and redundant description will be omitted.

  The application deployment system 100 according to the present embodiment is different from the application deployment system according to the first embodiment in that it further includes a management server node. Hereinafter, the difference will be mainly described.

  FIG. 19 is a diagram illustrating a network configuration of the application deployment system in the present embodiment.

  In the application deployment system according to the present embodiment, in addition to one or more AP server nodes 101 and one or more load distribution nodes 102, one or more management server nodes 1901 are connected to each other via a communication network 103 so that they can communicate with each other. Has been. In the present embodiment, the operation terminal 104 may be connected to the communication network 103.

  In the AP server node 101 according to the present embodiment, information regarding “type” indicating whether the application archive is held or the application is deployed is added to the AP deployment information 1903 in the deployment status holding unit 201a. Except for this, it is equivalent to the AP server node 201 in each of the above embodiments. This type will be described later.

  The load balancer node 102 in this embodiment is the same as the load balancer node 102 in each of the above embodiments, except that information regarding the type is added to the AP deployment information 1903 in the deployment status holding unit 201a.

  The management server node 1901 in this embodiment includes a deployment status management unit 201, an AP management unit 203, and a deployment reception unit 1902. In this embodiment, these components constituting the management server node are connected so as to communicate with each other. Further, these components may be communicably connected to the communication network 103 as necessary.

  The management server node 1901 in this embodiment receives an application archive from an operation manager (not shown) and distributes the application archive to other nodes (such as the AP server node 101). In other words, the management server node 1901 in this embodiment does not deploy an application to itself, but only distributes an application archive.

  Hereinafter, the configuration of the management server node 1901 in this embodiment will be described.

  First, the deployment status management unit 201 and the AP management unit 203 in the management server node 1901 may be equivalent to the deployment status management unit 201 and the AP management unit 203 in the AP server node 101 of the present embodiment, respectively. That is, the AP deployment information 1903 in the deployment status management unit 201 constituting the management server node 1901 has information on the type.

  Next, the deployment reception unit 1902 in the management server node 1901 receives an application archive from the operation manager, and stores the application archive in the AP management unit 203.

  The deployment acceptance unit 1902 notifies the deployment status management unit 201 of the application ID, the resource path, and the address of the own node (management server node 1901) for the application.

  At this time, similarly to the deployment status management unit 201 in the AP server node 101, the deployment status management unit 201 in the management server node 1901 updates the AP deployment information 1903 and the AP attribute information 201c, and sends the update notification to other nodes. Send.

  Next, the configuration of the AP deployment information 1903 in the AP server node 101, the load distribution node 102, and the management server node 1901 will be described with reference to FIG.

  As described above, in the application deployment system according to the present embodiment, an application is deployed to the own node, the AP server node 101 that can process a request for the application, and the application is archived without deploying the application to the own node. Management server nodes 1901 to be distributed are mixed.

  Therefore, as information that can identify whether an application is deployed and a node can process a request, as illustrated in FIG. 20, the AP deployment information 1903 in each node relates to a type (reference numeral 2001 in FIG. 20). Set the information.

  In the specific example illustrated in FIG. 20, for example, when an application archive is held but not deployed (for example, the management server node 1901), the type is “uploaded” and the application archive is held. If the application is deployed (for example, the AP server node 101), the type is set to “deployed”.

  Further, in the AP server node 101 and the management server node 1901, information regarding the type is added to update information transmitted to other nodes when the AP deployment information 1903 is updated.

  A specific example of the update notification in this case is illustrated in FIG. As illustrated in FIG. 23, “type = uploaded” is added to the update notification of the AP deployment information 1903 as information about the type.

  Next, the operation terminal 104 in this embodiment will be described. The operation terminal 104 in the present embodiment is communicably connected to the communication network 103 in the same manner as the operation terminal 104 in the first embodiment.

  In the present embodiment, an operation manager (not shown) may execute application deployment (or deployment instruction) to a specific management server node 1901 via the operation terminal 104, for example. In the present embodiment, whether or not the operation terminal 104 is provided is arbitrary.

  The operation of the application deployment system according to this embodiment configured as described above will be described below.

  First, the operation of the management server node 1901 in this embodiment will be described with reference to the flowchart illustrated in FIG.

  The deployment reception unit 1902 in the management server node 1901 receives an archive of the application to be deployed from an operation manager (not shown) (step S2101).

  In this case, an operation manager (not shown) may transmit an archive of the application to the management server node 1901 using the operation terminal 104. At this time, an operation manager (not shown) may transmit an application ID of the application and information on a resource path for deploying the application to the management server node 1901 together with the application archive.

  The deployment acceptance unit 1902 in the management server node 1901 stores the application archive received in step 1901 in the AP holding unit 203a (step S2102).

  The deployment acceptance unit 1902 in the management server node 1901 notifies the deployment status management unit 201 of information regarding the application ID, resource path, address of the own node, and type received in step 1901 (step S2103).

  In this case, since the management server node 1901 only distributes the application archive, the deployment reception unit 1902 sets the information regarding the above type as “uploaded”.

  The deployment status holding unit 201a in the deployment status management unit 201 configuring the management server node 1901 updates the AP deployment information 1903 and the AP attribute information 201c based on the information notified in step S2103.

  Then, the deployment status transmission / reception unit 201d in the management server node 1901 creates update information associated with the update, and transmits the created update notification to another node connected to the communication network 103 (step S2104).

  Note that the processing in step S2104 is the same as the flowchart illustrated in FIG. 9 described above.

  The deployment status management unit 201 and the AP management unit 203 in the management server node 2401 may be equivalent to the deployment status management unit 201 and the AP management unit 203 in the AP server node 101 of the present embodiment, respectively. Detailed description regarding the processing is omitted.

  Next, the operation of the load balancer node 102 in this embodiment when the management server node 1901 as described above is added will be described using the flowchart illustrated in FIG.

  The deployment status transmission / reception unit 201d in the deployment status management unit 201 configuring the load balancer node 102 receives the update notification transmitted by the deployment status management unit 201 (particularly, the deployment status transmission / reception unit 201d) in another node, and the update The notification is notified to the deployment status holding unit 201a in the own node. The deployment status holding unit 201a that has received the notification updates the AP deployment information 1903 (step S2201).

  Here, in the present embodiment, the information regarding the type described above is included in the update notification. Therefore, the deployment status holding unit 201a registers information regarding the type included in the notification in the AP deployment information 1903.

  The other processing in step S2201 may be the same processing as the flowchart illustrated in FIG. 12 described in the first embodiment, and detailed description thereof is omitted.

  Next, the deployment status holding unit 201a in the load balancer node 102 notifies the load balancing target management unit 302 of the own node of the information related to the application ID, node address, and type added to the AP deployment information 1903, and load balancing is performed. An instruction is given to execute the previous registration process (step S2202).

  Next, the load distribution target management unit 302 confirms information regarding the type notified in step S2202 (step S2203). More specifically, the load distribution target management unit 302 determines whether or not the information regarding the type is “deployed”.

  As a result of the confirmation in step S2203, if the information regarding the type is not “deployed” (NO in step S2204), the load distribution target management unit 302 ends the process. In this case, since the node that transmitted the update notification received in step S2201 only holds the application and is not deployed, it does not become a distribution destination of requests for load distribution.

  On the other hand, as a result of the confirmation in step S2203, if the information related to the type is “deployed” (YES in step S2204), the load distribution target management unit 302 continues processing from step S2205 described below.

  In step S2205, the load distribution target management unit 302 acquires information on the resource path associated with the application ID registered in the AP deployment information 1903 in step S2201 from the AP attribute information 201c in the deployment status holding unit 201a (step S2205). S2205).

  Next, the load distribution target management unit 302 registers the node address and resource path associated with the application ID in the load distribution apparatus 303 of the own node as a distribution destination of requests for the application (step S2206).

  The deployment status management unit 201 and the AP management unit 203 in the management server node 1901 may be equivalent to the deployment status management unit 201 and the AP management unit 203 in the AP server node 101 of the present embodiment, respectively. Detailed description is omitted.

  Note that the operation of the AP server node 101 in this embodiment is the same as that in each of the above-described embodiments, and thus the description thereof is omitted.

  According to the application deployment system in the present embodiment described above, the same effects as those in the above embodiments can be obtained.

  Further, as described above, in the present embodiment, by deploying a specific application to the management server node 1901, the management server node 1901 transmits an update notification to another node. Further, the management server node 1901 can distribute the application archive to other nodes in the same manner as the AP server node 101 described in the above embodiments.

  Therefore, according to the application deployment system in the present embodiment, by introducing the management server node 1901, for example, it is possible for the operation manager to aggregate terminals for deploying applications.

  For this reason, according to the application deployment system in this embodiment, the man-hour regarding application deployment by the operation manager can be further reduced.

<Fifth Embodiment>
Next, a fifth embodiment of the present invention will be described. In the following description, characteristic portions according to the present embodiment will be mainly described, and the same configurations as those in the above-described embodiments will be denoted by the same reference numerals, and redundant description will be omitted.

  The application deployment system 100 according to this embodiment is different from the application deployment system according to each of the above embodiments in that it further includes a relay server node. Hereinafter, the difference will be mainly described.

    FIG. 24 is a diagram illustrating a network configuration of the application deployment system in the present embodiment.

  In the application deployment system according to the present embodiment, one or more AP server nodes 101 and one or more load distribution nodes 102 and one or more relay server nodes 2401 are connected to each other via the communication network 103 so that they can communicate with each other. Has been. In the present embodiment, the operation terminal 104 may be connected to the communication network 103.

  The AP server node 101 in the present embodiment may adopt the same configuration as that of the AP server node 101 in the fourth embodiment, and thus detailed description thereof is omitted.

  Since the load balancer node 102 in the present embodiment may adopt the same configuration as the load balancer node 102 in the fourth embodiment, similar to the AP server node 101 in the present embodiment, a detailed description will be given. Omitted.

  Next, the relay server node 2401 in this embodiment includes a deployment status management unit 201, an AP management unit 203, and a relay control unit 2402. These components constituting the relay server node 2401 are connected so as to communicate with each other.

  Further, these components may be communicably connected to the communication network 103 as necessary.

  In this embodiment, the relay server node 2401 copies an application archive held by another node to its own node, and becomes a new distribution source of the application archive. The relay server node 2401 according to the present embodiment may relay only the application archive without deploying the application to itself.

    Hereinafter, the configuration of the relay server node 2401 in the present embodiment will be described.

  First, the deployment status management unit 201 and the AP management unit 203 in the relay server node 2401 may be equivalent to the deployment status management unit 201 and the AP management unit 203 in the AP server node 101 of the present embodiment, respectively.

  Next, when the information held by the deployment status holding unit 201a in the own node is updated based on the update notification from another node, the relay control unit 2402 in the relay server node 2401 displays an application related to the update notification. Get the application archive file from the deployed or uploaded node.

  Next, the operation of the application deployment system in the present embodiment configured as described above will be described.

  First, the operation of the relay server node 2401 will be described using the flowchart illustrated in FIG. In the following, the relay server node 2401 receives the update notification transmitted by the deployment status management unit 201 (particularly, the deployment status transmission / reception unit 201d) in another node, and copies (relays) the application archive to the own node. The operation will be described.

  The deployment status transmission / reception unit 201d in the deployment status management unit 201 configuring the relay server node 2401 receives the update notification transmitted by the deployment status management unit 201 (particularly, the deployment status transmission / reception unit 201d) in another node, and the update notification To the deployment status holding unit 201a in the own node. Upon receiving the notification, the deployment status holding unit 201a updates the AP deployment information 1903 (step S2501). The other processing in step S2501 may be the same processing as the flowchart illustrated in FIG. 12 described in the first embodiment, and detailed description thereof is omitted.

  Next, the deployment status holding unit 201a in the relay server node 2401 notifies the relay control unit 2402 in its own node of the information regarding the application ID, node address, and type registered in the AP deployment information 1903, and executes the copy process. (Step S2502).

  Next, the relay control unit 2402 in the relay server node 401 determines whether copy processing is already being executed for the application having the same ID as the application ID specified in step S2502 (step S2503).

  If the result of determination in step S2503 is that copy processing is already being executed for the application with the same ID (YES in step S2504), relay control unit 2402 ends the process. This is to avoid duplicating the same application.

  On the other hand, if the result of determination in step S2503 is that copy processing is not already being executed for the application with the same ID (NO in step S2504), relay control unit 2402 continues processing from step S2505 below.

  In step S2505, the relay control unit 2402 inquires of the AP holding unit 203a in the AP management unit 203 whether the archive of the application having the same application ID has been saved (step S2505).

As a result of the inquiry in step S2505, when the archive of the application having the same ID has already been saved (YES in step S2506), the relay control unit 2402 ends the process. This is to avoid duplicating the same application. On the other hand, as a result of the inquiry in step S2505, if the archive of the application having the same ID has not been saved (NO in step S2506), the relay control unit 2402 Continues the process from step S2507 below.

  In step S2507, the relay control unit 2402 acquires an archive of the application from a node that can distribute the application corresponding to the application ID specified in step S2502 (step S2507). Since this process may be the same process as the flowchart illustrated in FIG. 13, detailed description thereof is omitted.

  In this case, the nodes that can distribute the application may include the AP server node 101, the management server node 1901 in the fourth embodiment, and the (other) relay server node 2401 in the present embodiment.

  The relay control unit 2402 notifies the deployment status management unit 201 in the local node of the application ID, resource path, local node address, and type information of the application acquired (copied) in step S2505 (step S2508). Note that the relay control unit 2402 only distributes the application archive, and the application may not be deployed to the own node. In this case, it is assumed that the information regarding the relay control unit 2402 and the type is “uploaded”.

  The deployment status holding unit 201a in the relay server node 2401 updates the AP deployment information 1903 and the AP attribute information 201c based on the information notified in step S2508. Then, the deployment status transmission / reception unit 201d in the relay server node 2401 creates update information associated with the update, and transmits the created update notification to another node connected to the communication network 103 (step S2509). Note that the processing in step S2509 is the same as the flowchart illustrated in FIG. 9 described above.

  The deployment status management unit 201 and the AP management unit 203 in the relay server node 2401 may be equivalent to the deployment status management unit 201 and the AP management unit 203 in the AP server node 101 of the present embodiment, respectively. Detailed description is omitted.

  Here, the operations of the AP server node 101 and the load balancer node 102 in this embodiment may be the same as those in the fourth embodiment, and thus detailed description thereof is omitted.

  According to the application deployment system in the present embodiment described above, the same effects as those in the above embodiments can be obtained.

  In addition, as described above, in the present embodiment, the relay server node 2401 acquires a specific application based on an update notification from another node, and the other node holds the acquired application. To the update node as an update notification. Further, the relay server node 2401 can distribute the application archive to other nodes as in the AP server node 101 described in the above embodiments.

  Therefore, according to the application deployment system in the present embodiment, it is possible to distribute the load when the application archive is transmitted and received by the AP server node 101 and the relay server node 2401. Further, by adjusting the number of relay server nodes 2401, it is possible to adjust the application transmission load of each node.

  The following configuration is also included in the present embodiment as one application example of the present embodiment.

  In the present embodiment described above, by introducing the relay server node 2401, other nodes (AP server node 101 and other relay server node 101) can acquire the application archive from the relay server node.

  Therefore, the AP server node 101 may be configured such that only the relay server node 2401 distributes the application archive without distributing the application archive.

  In this case, for example, in the flowchart illustrated in FIG. 13, the deployment control unit 202a in each node refers to the AP deployment information 1903 held by the deployment status holding unit 201a.

  The deployment control unit 202a sets, in the AP deployment information 1903, a node whose information related to the type associated with the application ID of the application to be acquired is “uploaded” as the node from which the application is acquired.

  Since the information regarding the type of deployment status of the AP server node 101 is “deployed”, the AP server node 101 is excluded from candidates for acquisition sources of applications. In such a configuration, it is desirable to introduce the management server node 1901 described in the fourth embodiment.

  According to the application example of the present embodiment described above, the AP server node 101 does not need to distribute the application archive to other nodes.

  For this reason, it is possible to prevent the load for transmitting and receiving the application archive from affecting the AP server node 101.

<Sixth Embodiment>
Next, a configuration common to the above-described embodiments will be described as a sixth embodiment of the present invention with reference to FIG. FIG. 26 is a diagram illustrating a network configuration of the application deployment system according to the first embodiment of the present invention.

  The application deployment system 2600 according to the present embodiment includes one or more first nodes 2601 and one or more load balancer nodes 2602, which are communicably connected via the communication network 103. The application deployment system may further include one or more other nodes 2603. In the following description, the first node 2601, the load balancer node 2602, and the node 2603 may be collectively referred to as “nodes”.

  Each node in the application deployment system 2600 according to the present embodiment has application deployment information 2604 that associates application identification information that can uniquely identify a deployed application with information that can identify a node that holds the application.

  Each node has application attribute information 2605 that associates the application identification information with attribute information related to the application.

  The first node 2601 in this embodiment transmits an update notification of the application deployment information 2604 in its own node when it becomes possible to distribute the archive of the application held by that node to other nodes.

  Note that the first node 2601 in this embodiment, for example, archives the application included in the update notification from the plurality of nodes based on the update notification received from the other first node 2601. May be selected to obtain an archive of the application.

  In this case, the first node 2601 updates the application deployment information in its own node based on the update notification received from the other first node 2601, and based on the updated application deployment information. The update notification of the application deployment information in the own node may be created. Then, the first node 2601 may transmit the created update notification to the other nodes.

  Based on the update notification, the load distribution node 2602 in the present embodiment registers the first node node 2601 that has transmitted the update notification as a distribution destination of requests to the application.

  In the present embodiment, the first node node 2601 and the load distribution node node 2602 have the common application deployment information by updating the application deployment information based on the update notification. .

  Since the communication network 103 in the present embodiment may be the same as the communication network 103 in each of the above embodiments, detailed description thereof is omitted.

  According to the application deployment system 2600 in the present embodiment configured as described above, information on a node (for example, the first node 2601) on which the application is deployed is distributed by an update notification on the deployment status of the application. It is shared among a plurality of nodes (for example, the first node 2601 and the load distribution node 2602) that construct the environment.

  For this reason, it is not necessary to register information related to the node and information related to the load balancer in advance in the node, and the man-hours required for application deployment can be reduced.

<Configuration of hardware and software program (computer program)>
Hereinafter, a hardware configuration capable of realizing each of the above-described embodiments will be described.

  The AP server node 101 (FIG. 1), the load balancer node 102 (FIG. 1), the management server node 1901 (FIG. 19), the relay server node 2401 (FIG. 24), etc. described in each of the above embodiments have their respective functions. You may comprise by the hardware apparatus for exclusive use implement | achieved. In the following description, the AP server node 101, the load balancer node 102, the management server node 1901, the relay server node 2401, and the like may be simply referred to as “nodes”.

  In that case, the components constituting each of the above nodes may be realized as hardware that is partly or entirely integrated (such as an integrated circuit in which processing logic is mounted), and is configured by individual hardware. Also good.

  Each node described above may be configured by hardware as illustrated in FIG. 27 and various software programs (computer programs) executed by the hardware. In this case, the components constituting each node may be realized as a software program executed on a single hardware. Moreover, you may implement | achieve as a software program executed in a plurality of hardware.

  In the following description, the hardware illustrated in FIG. 27 may be simply referred to as information processing hardware.

  An arithmetic device 2701 in FIG. 27 is an arithmetic processing device such as a general-purpose CPU (Central Processing Unit) or a microprocessor. For example, the arithmetic device 2701 may read various software programs stored in a nonvolatile storage device 2703, which will be described later, into the storage device 2702, and execute processing according to the software programs.

  The storage device 2702 is a memory device such as a RAM (Random Access Memory) that can be referred to from the arithmetic device 2701, and stores software programs, various data, and the like. Note that the storage device 2702 may be a volatile memory device.

  The nonvolatile storage device 2703 is a nonvolatile storage device such as a magnetic disk drive or a semiconductor storage device using a flash memory, and may record various software programs, data, and the like.

  The network interface 2706 is an interface device that connects to a communication network. For example, a wired and wireless LAN (Local Area Network) connection interface device or the like may be employed. In the embodiment described above, for example, each of the nodes described above may be connected to the communication network 103 via the network interface 2706.

  The external storage device 2704 is, for example, a device that processes reading and writing of data with respect to an external storage medium 2705 described later.

  The external recording medium 2705 is an arbitrary recording medium capable of recording data, such as an optical disk, a magneto-optical disk, and a semiconductor flash memory.

  The input / output interface 2707 is a device that controls input / output between an external input device (such as a keyboard and a mouse) and an external output device (such as a display device and a printer).

  For example, in the fourth embodiment, an operation manager (not shown) deploys to the information processing hardware configuring the management server node 1901 via the input / output interface provided in the information processing hardware. You may input the information regarding the application to do.

  In the present invention described with the above-described embodiments as an example, each node (or a component of each node) is configured by the information processing hardware illustrated in FIG. After a software program capable of realizing the functions of the flowcharts referred to in the description of each embodiment is supplied, the software program may be executed by the arithmetic device 2701 executing the software program.

  In each embodiment described above, each unit illustrated in each of the above drawings can be realized as a software module, which is a function (processing) unit of a software program executed by the hardware described above. However, the division of each software module shown in these drawings is a configuration for convenience of explanation, and various configurations can be assumed for implementation.

  For example, when the units shown in FIG. 1, FIG. 19, and FIG. 24 are realized as software modules, these software modules are stored in the nonvolatile storage device 2703, and the arithmetic device 2701 executes each process. In addition, these software modules may be read out to the storage device 2702.

  In addition, these software modules may be configured to transmit various data to each other by an appropriate method such as shared memory or interprocess communication. With such a configuration, these software modules can be connected so as to communicate with each other.

  Further, each software program is recorded in the external storage medium 2705, and the software program is stored in the nonvolatile memory 2703 through the external storage device 2704 as appropriate at the shipping stage or the operation stage of the communication device. You may comprise.

  When the components in each node are realized as a software program, AP deployment information (reference numeral 201b, reference numeral 1903), AP attribute information (reference numeral 201c, reference numeral 1601), AP archive 203c described in the above embodiments. The AP archive correspondence information 203b, the request distribution destination information 303a, and the like may be stored in the storage device 2702 or the nonvolatile storage device 2703 using an appropriate data structure or the like as appropriate. These pieces of information may be stored in the nonvolatile storage device 2703 by storing them in an arbitrary database or the like.

  In the above case, the method of supplying various software programs to each node is installed in the device using an appropriate jig in the manufacturing stage before shipment or the maintenance stage after shipment. A general procedure can be adopted at present, such as a method of downloading from the outside via a communication line such as the Internet. In such a case, the present invention can be understood to be constituted by a code constituting the software program or a computer-readable storage medium in which the code is recorded.

  In the above, this invention was demonstrated as an example applied to exemplary embodiment mentioned above. However, the technical scope of the present invention is not limited to the scope described in the above embodiments. It will be apparent to those skilled in the art that various modifications or improvements can be made to such embodiments. In such a case, a new embodiment to which such changes or improvements are added can also be included in the technical scope of the present invention. This is clear from the matters described in the claims.

  Note that part or all of the above-described embodiment and its modifications may be described as in the following supplementary notes. However, the present invention described by way of example with the above-described embodiment and its modifications is not limited to the following.

(Appendix 1)
Application deployment information that associates application identification information that can uniquely identify an application with information that can identify a node that holds the application, and
Application attribute information associating the application identification information with attribute information related to the application;
A plurality of nodes connected to each other via a communication network,
The plurality of nodes are
When the archive of the specific application held by the own node can be distributed to other nodes included in the plurality of nodes, the one or more first notifications for transmitting the update notification of the application deployment information in the own node are transmitted. 1 node,
Based on the update notification, registering the first node that has transmitted the update notification as a request distribution destination for the application, thereby distributing one or more second processing loads according to the request Nodes, and
The one or more first nodes and the one or more second nodes have the application deployment information in common by updating the application deployment information based on the update notification. ,
Application deployment system.

(Appendix 2)
The first node is
Based on the update notification received from the other first node, obtain the application archive from the node capable of delivering the application archive among the plurality of nodes,
Based on the update notification, update the application deployment information in the own node,
Based on the updated application deployment information, create an update notification of the application deployment information in its own node,
The created update notification is transmitted to other nodes included in the plurality of nodes,
The application deployment system according to attachment 1.

(Appendix 3)
The first node is
Based on the update notification, update the application attribute information in the own node,
Based on the updated application attribute information, create an update notification of the application attribute information in its own node,
The created update notification is transmitted to other nodes included in the plurality of nodes,
The application deployment system according to appendix 1 or appendix 2.

(Appendix 4)
The first node is
Keep the archive of the acquired application on the own node,
In response to a request from another node included in the plurality of nodes, the archive of the held application is distributed to the other node.
The application deployment system according to Supplementary Note 2 or Supplementary Note 3.

(Appendix 5)
The first node is an application server node capable of deploying the application included in the acquired archive of the application to the own node and processing a request for the deployed application.
The application deployment system according to appendix 3 or appendix 4.

(Appendix 6)
The application attribute information includes information on a requested function required for the application server node to provide a service by the specific application,
The first node creates the update notification including information on the requested function, transmits the created update notification to other nodes included in the plurality of nodes,
The application server node confirms the update notification transmitted from the first node, and acquires the application and deploys to the own node when the own node satisfies the request function. To
The application deployment system according to attachment 5.

(Appendix 7)
The application deployment information includes type information that is information that can identify whether the first node that provides an archive of the specific application can process a request for the specific application,
The first node creates the update notification including the type information, transmits the created update notification to other nodes included in the plurality of nodes,
The second node is
Check the type information included in the above update notification,
When the first node that created the update notification can process a request for the specific application included in the update notification, the first node is registered as a distribution destination of the request for the specific application. It is characterized by
The application deployment system according to any one of appendix 1 to appendix 6.

(Appendix 8)
The first node is a relay server node that generates the type information indicating that the request for the acquired application cannot be processed, and creates the update knowledge including the type information.
The application deployment system according to attachment 7.

(Appendix 9)
Connected to the management means,
Updating the application deployment information and the application attribute information based on the application identification information provided from the management means and the information on the attribute of the application;
Holds an archive of applications provided by the management means,
When it becomes possible to distribute the archive of the held application to other nodes included in the plurality of nodes, the update notification of the application deployment status of the own node is transmitted,
The management server node further distributes the archive of the held application to the other nodes in response to a request from the other nodes included in the plurality of nodes.
The application deployment system according to any one of appendix 1 to appendix 8.

(Appendix 10)
Application deployment information that associates application identification information that can uniquely identify an application with information that can identify a node that holds the application, and
Application attribute information associating the application identification information with attribute information related to the application;
A plurality of nodes connected to each other via a communication network,
When the first node, which is the node, can distribute an archive of a specific application held by the node to other nodes included in the plurality of nodes, the application deployment information of the node Send an update notification,
Based on the update notification, the second node, which is the node, registers the first node that has transmitted the update notification as a request distribution destination for the application,
The one or more first nodes and the one or more second nodes have the application deployment information in common by updating the application deployment information based on the update notification. ,
How to deploy the application.

(Appendix 11)
Application deployment information that associates application identification information that can uniquely identify an application with information that can identify a node that holds the application, and
Application attribute information associating the application identification information with attribute information related to the application;
In a computer network in which a plurality of nodes having the following functions are connected to each other via a communication network,
When it becomes possible to distribute an archive of a specific application held by the first node to other nodes included in the plurality of nodes, to the computer functioning as the first node that is the node, Based on the update notification of the application deployment information, the first node that has transmitted the update notification is registered as a request distribution destination for the application, thereby distributing the processing load according to the request to the second node. On the other hand, the function of transmitting the update notification is realized.
program.

(Appendix 12)
Application deployment information that associates application identification information that can uniquely identify an application with information that can identify a node that holds the application, and
Application attribute information associating the application identification information with attribute information related to the application;
In a computer network in which a plurality of nodes having the following functions are connected to each other via a communication network,
The computer functioning as the second node as the node allows the first node as the node to store an archive of a specific application held by the first node with respect to other nodes included in the plurality of nodes. A function of receiving an update notification of the application deployment information to be transmitted when the distribution becomes possible,
Based on the received update notification, registering the first node that transmitted the update notification as a request distribution destination for the application realizes a function of distributing the processing load according to the request Characterized by
program.

  The present invention is applicable to a system that deploys an application to each node in a distributed processing environment in which a plurality of nodes are connected. For example, the present invention can be applied to a system in which the same application needs to be deployed on a large number of application servers, or a system in which information on the deployment destination application server cannot be known in advance.

DESCRIPTION OF SYMBOLS 100 Application deployment system 101 AP server node 102 Load distribution apparatus node 103 Communication network 104 Operation terminal 105 Client terminal 201 Deployment status management part 202 Deployment management part 203 AP management part 204 AP server 302 Load distribution object management part 303 Load distribution apparatus 1901 Management Server node 1902 Deployment acceptance unit 2401 Relay server node 2402 Relay control unit 2600 Application deployment system 2601 First node 2602 Load balancer node 2603 Node 2701 Arithmetic unit 2702 Storage device 2703 Non-volatile storage device 2704 External storage device 2705 External recording medium 2706 Network interface 2707 I / O interface

Claims (10)

Application deployment information that associates application identification information that can uniquely identify an application with information that can identify a node that holds the application, and
Application attribute information associating the application identification information with attribute information related to the application;
A plurality of nodes connected to each other via a communication network,
The plurality of nodes are
One or more first applications that transmit an update notification of the application deployment information in the own node when the archive of the specific application held by the own node can be distributed to other nodes included in the plurality of nodes. 1 node,
Based on the update notification, registering the first node that has transmitted the update notification as a request distribution destination for the application, thereby distributing one or more second processing loads according to the request Nodes, and
The one or more first nodes and the one or more second nodes have the application deployment information in common by updating the application deployment information based on the update notification. ,
Application deployment system. The first node is:
Based on the update notification received from the other first node, the archive of the application is acquired from the node capable of delivering the archive of the application among the plurality of nodes.
Based on the update notification, update the application deployment information in its own node,
Create an update notification of the application deployment information in its own node based on the updated application deployment information,
The created update notification is transmitted to other nodes included in the plurality of nodes,
The application deployment system according to claim 1. The first node is:
Based on the update notification, update the application attribute information in its own node,
Create an update notification of the application attribute information in its own node based on the updated application attribute information,
The created update notification is transmitted to other nodes included in the plurality of nodes,
The application deployment system according to claim 1 or 2. The first node is:
Hold the acquired application archive in its own node,
In response to a request from another node included in the plurality of nodes, the archive of the held application is distributed to the other node.
The application deployment system according to claim 2 or claim 3. The first node is an application server node that deploys the application included in the acquired archive of the application to its own node and can process a request for the deployed application.
The application deployment system according to claim 3 or 4. The application attribute information includes information on a requested function required of the application server node in order to provide a service by the specific application,
The first node creates the update notification including information related to the requested function, and transmits the created update notification to other nodes included in the plurality of nodes.
The application server node confirms the update notification transmitted from the first node, and when the own node satisfies the request function, obtains the application and deploys to the own node. To
The application deployment system according to claim 5. The application deployment information includes type information that is information that can identify whether the first node that provides an archive of the specific application can process a request for the specific application,
The first node creates the update notification including the type information, and transmits the created update notification to other nodes included in the plurality of nodes.
The second node is
Check the type information included in the update notification,
When the first node that created the update notification can process a request for the specific application included in the update notification, the first node is registered as a distribution destination of the request for the specific application. It is characterized by
The application deployment system according to any one of claims 1 to 6. Application deployment information that associates application identification information that can uniquely identify an application with information that can identify a node that holds the application, and
Application attribute information associating the application identification information with attribute information related to the application;
A plurality of nodes connected to each other via a communication network,
When the first node, which is the node, can distribute the archive of the specific application held by the own node to other nodes included in the plurality of nodes, the application deployment information of the own node Send an update notification,
The second node that is the node registers, based on the update notification, the first node that has transmitted the update notification as a distribution destination of requests to the application,
The one or more first nodes and the one or more second nodes have the application deployment information in common by updating the application deployment information based on the update notification. ,
How to deploy the application. Application deployment information that associates application identification information that can uniquely identify an application with information that can identify a node that holds the application, and
Application attribute information associating the application identification information with attribute information related to the application;
In a computer network in which a plurality of nodes having the following functions are connected to each other via a communication network,
When it becomes possible to distribute an archive of a specific application held by the first node to other nodes included in the plurality of nodes, to the computer functioning as the first node that is the node, Based on the update notification of the application deployment information, the first node that has transmitted the update notification is registered as a request distribution destination for the application, thereby distributing the processing load according to the request to the second node. On the other hand, the function of transmitting the update notification is realized.
program. Application deployment information that associates application identification information that can uniquely identify an application with information that can identify a node that holds the application, and
Application attribute information associating the application identification information with attribute information related to the application;
In a computer network in which a plurality of nodes having the following functions are connected to each other via a communication network,
The computer functioning as the second node as the node allows the first node as the node to store an archive of a specific application held by the first node with respect to other nodes included in the plurality of nodes. A function of receiving an update notification of the application deployment information to be transmitted when the distribution becomes possible,
Based on the received update notification, registering the first node that transmitted the update notification as a request distribution destination for the application realizes a function of distributing the processing load according to the request Characterized by
program.

Images