JP2010282667A - Method and system for leasing resource - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a hosting service that copes with the temporary shortage of resource at a low cost. <P>SOLUTION: The method for leasing a computer resource from a lending side center to a borrowing side center comprises: a procedure allowing the borrowing side center to receive resource information related to the resource to be leased from the lending side center and register the information in a management table 24; a procedure for detecting shortage of resource and specifying a bottleneck; a procedure for retrieving the resource for eliminating the bottleneck from the management table 24 and preparing a center list 22 of the center having the retrieved resource; and a procedure for making a request to lease the resource from the lending side center in the center list 22. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a resource lending method and a resource lending system in a computer.

  A form in which a computer connected to the Internet or the like provides business such as online shopping has become widespread. Providers of services such as online shopping merchandise companies often take the form of renting (renting) from specialized vendors instead of preparing the computers (server devices) that perform the services themselves. . A service that lends a computer that transmits information to the Internet as described above is generally called hosting.

  The resource is a computer resource to be rented for hosting. Computer resources include, for example, hardware resources for executing application software (application-specific server device, CPU (Central Processing Unit), memory, HDD (Hard Disk Drive), load balancer, etc.), application software, etc. Other software resources.

  Note that the definition of Web service expression of resources (Management Using Web Services) and the management method of Web services (Management Of Web Services) are described in Web Services Distributed Management (WSDM) (see Non-Patent Document 1). Has been.

  A center device of a hosting company (hereinafter, the center device is simply referred to as a center) has a resource to be lent out and provides a user with a business based on the resource. For example, based on a resource called a Web server, a business of presenting a product catalog for online shopping is provided to the user terminal. Therefore, the center secures necessary resources for each business and performs hosting. As an allocation method for providing necessary resources to a user, for example, there is a distributed computer processing method and system (Patent Document 1) by the applicant of the present application.

  Note that general modeling and access method specifications for resources having a state using a Web service are defined in WSRF (Web Services Resource Framework) (Non-Patent Document 2) and WSRP (Web Services Resource Properties) ( Non-patent document 3).

  Here, resources that have already been hosted may temporarily become insufficient due to the inability to use resources due to failures such as device failures or the occurrence of business processing that exceeds resource processing capacity due to access concentration, etc. Sometimes. For this reason, conventionally, before a temporary shortage of resources occurs, a resource shortage factor is predicted, and a contract for borrowing spare resources from another center is made.

  Note that the contract for borrowing resources is performed in accordance with, for example, WS-Agreement (see Non-Patent Document 4), which is a rule for exchange of contract information between resource providers and consumers. When a shortage of resources occurs, it is possible to avoid a business stop by using this spare resource.

Japanese Patent Laying-Open No. 2004-240671 (paragraph [0013])

OASIS (Organization for the Advancement of Structured Information Standards), “WSDM (Web Services Distributed Management)”, [online], [Search February 15, 2005], Internet <URL: http: //docs.oasis-open .org / wsdm / 2004/12 / wsdm-1.0.zip> OASIS, “WSRF (Web Services Resource Framework)”, [online], [Search February 15, 2005], Internet <URL: http://docs.oasis-open.org/wsrf/2004/11/wsrf -WS-Resource-1.2-draft-02.pdf> OASIS, “WSRP (Web Services Resource Properties)”, [online], [searched on February 15, 2005], Internet <URL: http://docs.oasis-open.org/wsrf/2004/11/wsrf -WS-ResourceProperties-1.2-draft-05.pdf> GGF (Global grid forum) GRAP-WG, “WS-Agment”, [online], [Search February 15, 2005], Internet <URL: http://www.gridforum.org/Public#Comment#Docs /Documents/Public#Comment#2004/WS-AgreementSpecification#v2.pdf>

  However, the contract for borrowing spare resources is a fixed one that is made before a temporary shortage of resources occurs, and is not flexible. Therefore, even if there is no temporary shortage of resources, there is a cost of continuing to borrow resources from other centers. This spare resource is a useless resource that is not used during normal hosting. Therefore, in the fixed contract that borrows spare resources, the cost performance of the center is deteriorated.

  In addition, if a contract is made with a condition that a resource is borrowed when a temporary shortage of resources occurs, no rental fee is charged until the temporary shortage of resources occurs. However, the time when a conditional contract is made is before the time when a temporary shortage of resources occurs. Therefore, even though there are centers that provide resources at low rental costs due to price competition for resource parts, etc., it is necessary to rent expensive resources provided by a center that has a conditional contract. Therefore, the cost performance will deteriorate.

  Accordingly, the main object of the present invention is to realize hosting that can solve the above-described problems and cope with a temporary shortage of resources at a low cost.

In order to solve the above problems, the present invention is a resource lending method for lending a computer resource from a plurality of lending side center devices to a lending side side device,
The borrower center device is
In order from the request source of processing, a global load balancer, a load balancer, a Web server, an AP server, and a business system configured by connecting a DB server,
A procedure for receiving resource information on resources to be lent from the plurality of lending center devices and registering them in a management table;
A procedure for detecting a resource shortage of the borrower center device and identifying a bottleneck as the Web server;
A procedure for searching for resources including the load balancer and the Web server for eliminating bottlenecks from the management table, and creating a center list of the lending center device having the searched resources;
A procedure for requesting resource lending to each of the plurality of lending center devices of the center list;
The global load balancer and the load balancer that is lent by the request are connected, and the AP server and the Web server that is the resource lent by the request are connected and lent by the request A procedure for making a request to deploy an application to a resource to the plurality of lending center devices;
It is characterized by performing.
Other means will be described later.

  The present invention makes it possible to realize hosting that can cope with a temporary shortage of resources at a low cost by requesting the resources after the shortage of resources occurs.

It is explanatory drawing which shows the virtualization of the resource regarding one Embodiment of this invention. It is explanatory drawing which shows the management of the resource regarding one Embodiment of this invention. It is a block diagram which shows the resource rental system regarding one Embodiment of this invention. It is explanatory drawing which shows deployment of the resource regarding one Embodiment of this invention. It is a block diagram which shows the business system regarding one Embodiment of this invention. It is a block diagram which shows the business system regarding one Embodiment of this invention. It is a block diagram which shows the business system regarding one Embodiment of this invention. It is a block diagram which shows the memory | storage means to manage the resource regarding one Embodiment of this invention. It is a flowchart which shows the process which manages the resource regarding one Embodiment of this invention. It is a flowchart which shows the process which copes with temporary shortage of the resource regarding one Embodiment of this invention. It is a flowchart which shows the process which searches the center which requests | requires the resource regarding one Embodiment of this invention.

  Hereinafter, an embodiment of a resource rental system to which the present invention is applied will be described in detail with reference to the drawings. First, the configuration of the resource rental system of this embodiment will be described with reference to FIGS.

  FIG. 1 is an explanatory diagram showing resource virtualization. Resources can be classified into real resources that actually exist in the own center or virtual resources that explain the contents of real resources in other centers. For example, the center SX has nine real resources (RX1 to RX9), and the center SB has three real resources (RB1 to RB3). Then, the center SX makes two real resources (RX3, RX6) it has open to the center SB as virtual resources (RX3, RX6).

  In this way, opening a real resource owned by a predetermined center to another center as an object (virtual resource) is called resource virtualization. For example, in addition to the center SB, the center SX publishes real resources (RX1, RX2, RX3) for lending to a center SA (not shown), and publishes real resources (RX5, RX6) for lending to a center SC (not shown). To do.

  The resource RX3 is open to both the center SA and the center SB, but only one of the centers can be lent out at a predetermined time. Therefore, the released resource may have already been lent out by another center, and at that time, the resource is not lent out.

  FIG. 2 is an explanatory diagram showing resource management. FIG. 2A is a diagram illustrating an example of resources managed by the center SB. In addition to the real resources (RB1, RB2, RB3) that the center SB has, virtual resources (RX3, RX6) published from the center SX and virtual resources (RY1, RY2) published from the center SY to manage.

  FIG. 2B is a diagram in which resource management is hierarchized. All resources are classified according to the center to which they belong, and the resources of each center are classified according to usage such as for Web and DB.

  FIG. 3 is a configuration diagram showing a resource rental system. Each device of the resource lease system is configured as a computer including at least a memory as a storage unit 20 used when performing arithmetic processing and an arithmetic processing device that performs the arithmetic processing. The memory is constituted by a RAM (Random Access Memory) or the like. Arithmetic processing is realized by an arithmetic processing unit configured by a CPU (Central Processing Unit) executing a program on a memory.

  The center SB (borrowing center) provides a hosting service based on the resources it owns and the resources borrowed from the center SX (renting center). The user terminal 1 is a terminal that uses a hosting service provided by the center SX.

  The center SB includes an operation control unit 10B, a business system 12B, a FW / NAT 14B, a user side FW / NAT 16B, and a storage unit 20. The center SX includes an operation control unit 10X, a business system 12X, and a FW / NAT 14X. FW (firewall) indicates a firewall that prevents unauthorized intrusion from an external network, and NAT (Network Address Translation) indicates address translation used to share one global address among a plurality of computers.

  Note that the relationship between the center SB and the center SX is a relative relationship regarding resource leasing. That is, when the center SX provides another hosting service (that is, when it becomes a borrowing center), the center SX has the same configuration as the center SB. Each component will be specifically described below.

  FIG. 4 is an explanatory diagram showing resource deployment. The term “deployment” is a general term for preparations for enabling execution of applications that realize business, and is also referred to as “deploy”. For example, the preparation includes not only installation of an application but also setting processing for changing the setting of an application and an OS (Operating System) on which the application operates from a default (initial setting) to a setting suitable for business.

  FIG. 4A illustrates the roles of the operation control unit 10B and the operation control unit 10X. The operation control unit 10B of the center SB instructs the operation control unit 10X of the center SX to deploy based on the resources borrowed from the center SX. Receiving the instruction, the operation control unit 10X executes deployment for the resources lent to the center SB.

  FIG. 4B is a diagram for explaining network setting processing performed in conjunction with deployment. This setting is performed in the FW / NAT 14B, the FW / NAT 14X, and the user side FW / NAT 16B. The NAT converts a local address (LIP: Local IP Address) in the center and a global address (GIP: Global IP Address) for Internet connection.

  First, for example, as shown in FIG. 4B, the NAT may allocate a global address for each resource (GIP “X” -LIP “A”, GIP “Y” -LIP “B”, GIP “ Z "-LIP" C "). The notation GIP “X” -LIP “A” means that “X” in the global address corresponds to “A” in the local address.

  On the other hand, NAT may have a fixed number (for example, 1) of GIPs allocated to business (GIP “Y” & Port “Y1” -LIP “A” & Port “α”, GIP “Y” & Port “Y2” -LIP “ B ”& Port“ α ”, GIP“ Y ”& Port“ Y3 ”−LIP“ C ”& Port“ α ”). The notation of GIP “Y” & Port “Y1” -LIP “A” & Port “α” indicates that the global address is “Y” and the port number is “Y1”, the local address is “A” and the port number is This corresponds to the entry “α”.

  5 to 7 are configuration diagrams showing a business system. The business system is a computer environment that executes the business of the hosting service. FIG. 5A shows the business system 12B before borrowing resources. FIGS. 5B, 6 and 7 respectively show the business system 12B and the business system 12X after borrowing resources.

  LB (load balancer) distributes received transactions to Web servers to distribute the load. The Web server provides a UI (User Interface) and calls an AP (Application) server as a CGI (Common Gateway Interface) according to the input content. The AP server calls a DB (database) server when performing data access.

  The data request from the AP server to the DB server is performed, for example, by transferring an SQL (Structured Query Language) message on the SOAP (Simple Object Access Protocol) protocol. Thereby, the firewall (FW / NAT14B, FW / NAT14X) can be exceeded via the Internet.

  A GLB (Global load balancer) is further added to the business system 12X (FIG. 5B, FIG. 6 and FIG. 7) after borrowing resources. The GLB bundles a plurality of LBs and allocates the received transaction to any LB. As a result, requests (transactions) from the end users are distributed and the processing becomes independent. Therefore, it is only necessary for the end user to know one window called GLB for transactions distributed to a plurality of centers, which is convenient.

  Next, a method for determining which of the three business systems 12X (FIG. 5B, FIG. 6 and FIG. 7) is adopted will be described. A criterion for selecting one business system 12X from a plurality of business system 12X candidates is the position of a bottleneck, which is a factor that causes a temporary shortage of resources. The bottleneck may be a Web server, AP server, or DB server.

  First, when the Web server is a bottleneck, as shown in FIG. 5B, a method for adding an LB and a Web server is selected. Alternatively, when the AP server is a bottleneck, a method for adding an LB, a Web server, and an AP server is selected as shown in FIG. Alternatively, when the DB server is a bottleneck, a method of adding an LB, a Web server, an AP server, and a DB server is selected as shown in FIG. The added DB server in FIG. 7 performs data replication (synchronization processing) with the DB server before the addition, and mirrors the data to each other.

  Thus, online shopping is given as an example of selecting the business system 12X to be adopted depending on the position of the bottleneck. For example, if there are many users who are viewing a product without placing an order for shopping, the load on the Web server that presents the product catalog increases. On the other hand, when there are many users who place orders in a shopping cart, the load on the AP server or DB server increases.

  FIG. 8 is a configuration diagram showing the storage means 20 for managing resources (real resources held by the own center, virtual resources released from other centers). The center list 22 is a list of center candidates that are partners to rent resources.

  The management table 24 presents, for each center, resources that each center discloses for rental. The resources to be disclosed are classified according to usage (for Web, DB, and AP), and are a set of the total number and the vacant number that can be rented therefrom. The location indicates the communication delay time between the own center and the center of each record. The smaller the value, the closer the center of each record is to the center.

  The detail table 26 is a table prepared for each center, and stores detailed information about resources disclosed by each center. One record corresponds to one resource. For example, the resource of item number 1 is a resource used for the Web server, the specification is “Pen4, 2 [GHz]”, and the rentable period is “05 / 01/01 to 06/02/28 "and the rental price is" 5000 yen / h ".

  The configuration of the resource rental system has been described above. Next, among the operations of the resource rental system according to the present embodiment, processing in user registration will be described with reference to FIGS. 9 to 11 with reference to FIGS.

  FIG. 9 is a flowchart illustrating processing for managing resources.

  First, the center SB makes a contract with the center SX (S101). Note that the contract is not a resource consumption lease contract, but a contract that the center SX provides the center SB with information about resources to be lent. Based on this contract, each center communicates with each other resources that can be temporarily accommodated. The contract processing may be performed online via a network or may be performed offline such as an FD (flexible disk) medium.

  Next, the center SX issues a certificate (electronic data) indicating that the contract of S101 has been made to the center SB (S102). Then, the center SB requests resource information from the center SX according to the contract of S101 (S103). Further, the center SX checks whether the certificate of the contract included in the request in S103 has been issued in S102 (S104). The center SX returns the resource information to the center SB when the confirmation is obtained in S104 (S105). Further, the center SB registers the received resource information in a table (management table 24, detail table 26) (S106).

Here, the content of the resource information transmitted in S105 includes, for example, the following.
・ Resource specifications ・ Free information ・ Rental price ・ Network configuration (network to which the resource belongs. Address that can be deployed to the resource)
・ Operating results (idle time)
・ Manufacturer of resources ・ Lifetime ・ Operational years

  In S105, the resource information published by the center SX does not show all the resources held by the center SX, but at least some of the resources of the center SX based on a contract with the center SB. Is open to the center SB. For example, if the center SX and the center SC have a contract different from S101, the information shown by the center SX to the center SB and the information shown to the center SC are basically different (as a result. It may be the same).

  In S105, the center SX provides resource status information that changes from moment to moment through a Web service interface. The published information is snapshot information (for example, every hour or every 30 minutes). When the center SB determines to use the resource of the center SX, there is a possibility that the resource is already used in another center, and the resource status information becomes old. Therefore, when the resource information is taken in and the information is changed, the center SB requests to notify the center SX. As a result, the center SB can fetch the latest resource information from the center SX every time the resource information of the center SX is changed.

  Further, the reply (S105) of the resource information and the registration (S106) of the table (management table 24, detail table 26) may be in an offline format such as direct mailing as well as online. When offline, registration (S106) of the table (management table 24, detail table 26) is performed manually based on the paper (direct mail).

  Here, the center SB and the center SX measure location information (S111). Then, the center SX responds to the measurement of the location information to the center SB (S112). Specifically, the location information is a communication delay between the own center and the partner center. The own center measures the response time by accessing the end point of the partner center. The average time of the measurement results is obtained several times, and this information is used as location information. Therefore, the smaller the time value is, the closer the network distance is. Further, the center SB stores the location information measured in S111 and S112 in the management table 24 (S113).

  Here, the center SX detects a change in the resource state (S121). The change in the resource state is, for example, a resource failure or a change in the resource usage status (lending to another center, etc.). Then, the center SX notifies the center SB of the change of the detected resource state (S122). Further, the center SB registers the received resource information in the table (management table 24, detail table 26) (S123).

  FIG. 10 is a flowchart illustrating processing for dealing with a temporary shortage of resources. The operation of FIG. 10 is performed after the operation of FIG.

  First, the center SB detects a temporary shortage of resources that are already provided as hosting, and identifies a bottleneck that is the cause (S201). The cause is, for example, a high CPU load due to resource failure or temporary congestion, and the bottleneck is, for example, an event where only the Web server is crowded.

  Note that the number of transactions generally changes over time, and bottlenecks can occur constantly. However, dealing with all small bottlenecks will be costly. Therefore, as a method for selecting a bottleneck to be dealt with from among the generated bottlenecks, a bottleneck that has occurred may be compared with a predetermined threshold that is determined to be that business continuation is impossible unless resources are added. . This predetermined threshold may be calculated based on past statistical data.

  The center SB searches the local center for a resource that eliminates the bottleneck according to the characteristics of the bottleneck. If the center SB finds it, it allocates the resource of the local center instead of requesting the lending of the resource to another center. On the other hand, when there is no resource allocated in the own center, the center SB searches for a center that can lend a resource for eliminating the bottleneck (S202).

  The center search process (S202) will be described in detail with reference to FIG. As an outline, the center SB acquires the resource information published by other centers based on the contract of S101. Then, the center SB compares the business bottleneck due to the temporary shortage of resources in S201 with the acquired resource information, and selects the center most suitable for eliminating the bottleneck.

  Then, the center SB requests resource lending to the center SX searched in S202 (S203). Here, there may be a situation where there is no resource at the stage where the resource is acquired. Therefore, the center SB determines the priority at the time of comparison in S202, and creates the center list 22 for collecting resources. The center SB sequentially rewrites the priority between centers in the center list 22 by changing the resource information (S122), and increases the possibility that an optimal resource can be selected.

  Further, the center SX notifies the center SB of the result of resource lending (S204). Resource lending results include lending approval or lending rejection. When the lending is rejected, a resource lending is requested to the next candidate center in the center list 22 to collect resources (S203).

  In this way, resource consumption rental contracts are performed online in conjunction with resource shortages (S201) (S202, S203), thereby collecting information on resources that are available manually and making resource consumption rental contracts on paper. Compared to the work to be performed, the resource shortage can be solved quickly.

  Then, the center SB requests the center SX to deploy the business application to the resource lent by the rent approval (S205). Furthermore, the center SX receives a deployment request from the center SB (S206). Then, the center SX performs business application deployment (S207). Further, the center SX notifies the center SB of completion of deployment (S208).

  Here, the center SB performs network setting processing (FW setting, NAT setting, etc.) with the deployment of the business application (S207). The network setting process includes settings for causing the user terminal to use the deployed business application in addition to the settings for deploying the business application.

  FIG. 11 is a flowchart showing a process (S202 in FIG. 10) for searching for a center requesting a resource.

  First, the center SB checks all entries in the management table 24 that stores information related to the center contracted in S101 (S301). Next, the center SB extracts an entry satisfying the vacant number suitable for the use required for the bottleneck in S201, and creates the center list 22 (S302).

  The center SB refers to the detailed information of all the centers in the center list 22 from the detailed table 26 (S303). Further, the center SB excludes from the center list 22 centers that do not have available resources from the detailed information (S304). The resources that can be used are, for example, resources that are vacant during the period of borrowing and resources that satisfy the required specifications.

  Then, the center SB refers to the rental price in the detailed table 26 for all entries in the center list 22 and calculates the cost for each center (S305). Furthermore, the center SB sorts the center list 22 in ascending order of location value and in ascending order of cost value (S306). Note that the centers may be sorted in ascending order of location values, and the centers may be sorted in ascending order of cost values when the location values are the same. On the other hand, the centers may be sorted in ascending order of cost values, and the centers may be sorted in ascending order of location values when the cost values are the same.

  By renting resources from a center with a small location value, hosting can be provided with low delay, which is advantageous for accessing user terminals. On the other hand, by renting resources from a center with a low cost value, it is possible to procure hosting equipment at a low cost, which is advantageous for the center.

  Then, the center SB requests the resources in order from the upper center in the sort order in the center list until the resources can be secured (S307). If the cost exceeds a certain level, resource rental may be given up.

  According to the present embodiment described above, the service level of the business hosting for the center can be maintained by flexibly receiving the loan from the center selected based on the contract. Furthermore, since there are multiple contract centers that provide resources, the opportunity to lend optimal resources increases. Note that the resource shortage is basically temporary, but if it is considered that there will be a shortage in the future, the resource may be purchased in S307.

  The present invention described above can be widely modified without departing from the spirit thereof as follows.

  For example, in the creation of the center list 22 (S302), in principle, a centralized type in which necessary resources are rented from one center. This is for simplifying the labor for requesting resources to one time. However, when there are a plurality of necessary resources, a distributed type in which each resource is rented from a plurality of centers may be used. Thereby, each resource can be rented at the lowest cost.

SB, SX Center 10B, 10X Operation Control Unit 12B, 12X Business System 14B, 14X FW / NAT
16B User side FW / NAT
20 Storage Means 22 Center List 24 Management Table 26 Detail Table

Claims (11)

A resource lending method for lending computer resources from a plurality of lending center devices to a lending center device,
The borrower center device is
In order from the request source of processing, a global load balancer, a load balancer, a Web server, an AP server, and a business system configured by connecting a DB server,
A procedure for receiving resource information on resources to be lent from the plurality of lending center devices and registering them in a management table;
A procedure for detecting a resource shortage of the borrower center device and identifying a bottleneck as the Web server;
A procedure for searching for resources including the load balancer and the Web server for eliminating bottlenecks from the management table, and creating a center list of the lending center device having the searched resources;
A procedure for requesting resource lending to each of the plurality of lending center devices of the center list;
The global load balancer and the load balancer that is lent by the request are connected, and the AP server and the Web server that is the resource lent by the request are connected and lent by the request A procedure for making a request to deploy an application to a resource to the plurality of lending center devices;
A resource borrowing method characterized by executing A resource lending method for lending computer resources from a plurality of lending center devices to a lending center device,
The borrower center device is
In order from the request source of processing, a global load balancer, a load balancer, a Web server, an AP server, and a business system configured by connecting a DB server,
A procedure for receiving resource information on resources to be lent from the plurality of lending center devices and registering them in a management table;
A procedure for detecting a resource shortage of the borrower center device and identifying a bottleneck as the AP server;
A procedure for searching the management table for resources including the load balancer, the Web server, and the AP server for eliminating a bottleneck, and creating a center list of the lending center device having the searched resources; ,
A procedure for requesting resource lending to each of the plurality of lending center devices of the center list;
The global load balancer and the load balancer that is lent by the request are connected, and the DB server and the AP server that is the resource lent by the request are connected, and the loaned by the request A procedure for making a request to deploy an application to a resource to the plurality of lending center devices;
A resource borrowing method characterized by executing A resource lending method for lending computer resources from a plurality of lending center devices to a lending center device,
The borrower center device is
In order from the request source of processing, a global load balancer, a load balancer, a Web server, an AP server, and a business system configured by connecting a DB server,
A procedure for receiving resource information on resources to be lent from the plurality of lending center devices and registering them in a management table;
A procedure for detecting a resource shortage of the borrower center device and identifying a bottleneck as the DB server;
A resource list including the load balancer, the Web server, the AP server, and the DB server for eliminating a bottleneck is searched from the management table, and a center list of the lending center device having the searched resources is obtained. The steps to create,
A procedure for requesting resource lending to each of the plurality of lending center devices of the center list;
A process of connecting the global load balancer to the load balancer that is a resource lent by a request, and performing replication between the DB server of the business system and the DB server that is a resource lent by a request Including a procedure for requesting the plurality of lending center devices to deploy an application to the resource lent by the request,
A resource borrowing method characterized by executing   The resource information includes a cost, the procedure for creating the center list is created in the order of center devices having candidates with the lowest costs, and the procedure for requesting the lending of resources requests the lending in the order of the center list. The resource lending method according to any one of claims 1 to 3, characterized in that:   The borrowing center device and the lending center device measure a communication delay with respect to each other's communication, and the procedure of creating the center list is a procedure of creating the center devices in order of increasing communication delay and requesting lending of the resource The resource lending method according to claim 1, wherein lending is requested in the order of the center list.   The request for deploying the application includes a request for setting a firewall of the lending side center device and the borrowing side center device, according to any one of claims 1 to 5. Resource borrowing method.   The request for deploying the application includes a request for setting NAT of the lending center device and the borrowing center device, according to any one of claims 1 to 5. Resource borrowing method. A resource lending system that lends computer resources from a plurality of lending center devices to a lending center device,
The borrower center apparatus has a business system configured by connecting a global load balancer, a load balancer, a Web server, an AP server, and a DB server in order from a processing request source,
Each of the plurality of lending center devices transmits resource information related to resources to be lent to the borrowing center device,
Receiving a resource lending request for the resource information from the borrower center device, and lending the resource;
The borrower center device is
A management table for registering the resource information related to the resource to be lent received from the plurality of lending center devices;
Detecting the resource shortage of the borrower center device and identifying the bottleneck as the Web server,
The load balancer for resolving the bottleneck and the resources including the web server are searched from the management table, and a center list of the lending center device having the searched resources is created,
Requesting the lending of resources to each of the plurality of lending center devices of the center list,
The global load balancer and the load balancer that is lent by the request are connected, and the AP server and the Web server that is the resource lent by the request are connected and lent by the request A resource lending system comprising: an operation control unit configured to request the plurality of lending center devices to deploy an application to a resource. A resource lending system that lends computer resources from a plurality of lending center devices to a lending center device,
The borrower center apparatus has a business system configured by connecting a global load balancer, a load balancer, a Web server, an AP server, and a DB server in order from a processing request source,
Each of the plurality of lending center devices transmits resource information related to resources to be lent to the borrowing center device,
Receiving a resource lending request for the resource information from the borrower center device, and lending the resource;
The borrower center device is
A management table for registering the resource information related to the resource to be lent received from the plurality of lending center devices;
Detects resource shortage of the borrower center device and identifies a bottleneck as the AP server,
Search the resource including the load balancer, the Web server, and the AP server for resolving the bottleneck from the management table, create a center list of the lending center device having the searched resource,
Requesting the lending of resources to each of the plurality of lending center devices of the center list,
The global load balancer and the load balancer that is lent by the request are connected, and the DB server and the AP server that is the resource lent by the request are connected, and the loaned by the request A resource lending system comprising: an operation control unit configured to request the plurality of lending center devices to deploy an application to a resource. A resource lending system that lends computer resources from a plurality of lending center devices to a lending center device,
The borrower center apparatus has a business system configured by connecting a global load balancer, a load balancer, a Web server, an AP server, and a DB server in order from a processing request source,
Each of the plurality of lending center devices transmits resource information related to resources to be lent to the borrowing center device,
Receiving a resource lending request for the resource information from the borrower center device, and lending the resource;
The borrower center device is
A management table for registering the resource information related to the resource to be lent received from the plurality of lending center devices;
Detect the resource shortage of the borrower center device and identify the bottleneck as the DB server,
A resource list including the load balancer, the Web server, the AP server, and the DB server for eliminating a bottleneck is searched from the management table, and a center list of the lending center device having the searched resources is obtained. make,
Requesting the lending of resources to each of the plurality of lending center devices of the center list,
A process of connecting the global load balancer to the load balancer that is a resource lent by a request, and performing replication between the DB server of the business system and the DB server that is a resource lent by a request A resource lending system comprising: an operation control unit configured to request the plurality of lending center devices to deploy an application to a resource lent by the request. The resource information includes a cost.When creating the center list, create in order of center devices having candidates with a low cost.When requesting resource lending, request lending in the order of the center list.
When the borrowing center device and the lending center device measure communication delays related to each other's communication and create the center list, when creating the center devices in order of decreasing communication delay, and requesting resource lending The resource lending system according to any one of claims 8 to 10, wherein lending is requested in the order of the center list.

Images