JP6200080B2 - Managing client access to multiple computing systems - Google Patents

Description

RELATED APPLICATIONS This application includes the following applications: US Patent Application No. 13 / 927,892 entitled “MANAGING CLIENT ACCESS TO A PLULARITY OF COMPUTING SYSTEMS” filed June 26, 2013, June 2013 US Patent Application No. 13 / 927,929 entitled “PRODUCER SYSTEM PARTIONING AMONG LEASING AGENT SYSTEMS” filed on the 26th, and US Patent Application No. 13 entitled “PRODUCER SYSTEM SELECTION” filed on June 26, 2013 No./927,933 and “PRODUCER SYSTEM PARTITIONING AMONG LEASING AGENT SY” filed on June 26, 2013. Related to the U.S. patent application Ser. No. 13 / 927,995, entitled TEMS ", the disclosures of these patents are entirely incorporated herein by reference.

  In many cases, computing resources and services are provided by several computing systems. These computational resources and / or services can be consumed by several additional computing systems. In many cases, several computing systems will provide access to the same resources or services. Each computing system that provides a resource or service is typically limited in the number of requests that the system can process during a period of time.

US Patent Publication No. 2013/0073703

  To help provision services to requesting computer systems, some companies utilize a centralized system that can track the use of each system that provides services or resources. By using a centralized system, the load on each of the provisioning systems can be distributed among several computing systems that provide services or resources. One such centralized system is a hardware load balancer. A hardware load balancer can help distribute requests among computing systems that provide services or resources so that the load is distributed throughout the enterprise provisioning system.

  Throughout the drawings, reference numbers are reused to indicate correspondence between referenced elements. The drawings are presented to illustrate the embodiments of the invention described herein and are not intended to limit the scope of the invention.

FIG. 3 illustrates an embodiment of a network environment that provides a consumer system with access to services hosted by a producer system. FIG. 6 illustrates an embodiment of a network environment that provides a consumer system with access to services hosted by a producer system and provides producer system health information to one or more lease agents. FIG. 6 is an alternative diagram of an embodiment of a network environment that provides a consumer system with access to services hosted by a producer system. FIG. 6 illustrates an embodiment of a process for accessing a service at a producer system. FIG. 6 illustrates an embodiment of a process for providing a producer system lease to a consumer system. FIG. 6 illustrates an embodiment of a producer system update process. FIG. 4 illustrates an embodiment of a splitting process that splits a set of producer systems. FIG. 6 illustrates an embodiment of a producer system registration process from a producer system perspective. FIG. 6 illustrates an embodiment of a producer system registration process from the perspective of a lease agent. FIG. 6 illustrates an embodiment of a lease agent subdivision process. FIG. 6 illustrates an embodiment of a producer selection process based on hysteresis. FIG. 3 illustrates an embodiment of an overlay network environment that provides a consumer system with access to services hosted by a reducer system. FIG. 6 illustrates an embodiment of a process for accessing a service at a producer virtual machine. FIG. 6 illustrates an embodiment of a process for processing a request to access a service on a producer virtual machine. FIG. 6 illustrates an embodiment of a process for leasing access to a producer virtual machine. FIG. 6 illustrates an example of a current state management table that can be used to facilitate communication in an overlay network environment.

A hardware load balancer can be referred to as a producer system, a computing system that provides access to a service or resource, and a computing system that requires access to a service or resource that can be referred to as a consumer system Although it can be used to help prevent overloading with requests from hardware, a hardware load balancer can have several drawbacks. For example, a hardware load balancer provides a single point of failure. In other words, if a hardware load balancer malfunctions, the associated enterprise system may become inaccessible because it can no longer forward service requests to the producer system. In addition, hardware load balancers can be costly and opaque hardware, making them an unattractive solution for load balancing enterprise systems.

  One solution to the problem associated with hardware load balancers is to use a distributed load balancer. However, a distributed load balancer will address some of the problems associated with using a hardware load balancer, but a distributed load balancer tends to be less than optimal. Decentralized load balancers do not have a global view of enterprise systems, and each load balancer is typically limited to supporting a defined subset of consumer and producer systems Because.

  This disclosure describes an embodiment of a system and process that uses a set of lease agents to allocate service requests from multiple consumer systems among multiple producer systems. Lease agents can monitor and allocate access or leases to a subset of producer systems, most often while recognizing multiple producer systems as a whole. Further, for each service request, a single consumer system can interact with several lease agents, and possibly multiple producer systems. This set of lease agents, in certain embodiments, can distribute the load balancing process among a set of isolated hardware-based systems, each lease agent providing a load for a subset of producer systems. It can serve as an amalgam load distribution device in terms of dispersion.

  Advantageously, in certain embodiments, the hardware load balancer and distributed are divided by dividing the producer system among the lease agents while maintaining at least a subset of information about each producer system at each lease agent. The advantages of the load balancer can be achieved without the aforementioned drawbacks. Further, in certain embodiments, by not assigning a consumer system to a particular lease agent and / or producer system, the load handled by each of the multiple producer systems isolates the producer system to an isolated subsystem. Compared to a system that does this, it can be more dispersed over time.

  In some cases, systems and applications implemented on producer and / or consumer systems are modified to work with lease agents. For example, as described further below, the consumer system can be modified to lease access to the producer system and maintain the current status information of the producer system.

  In some embodiments, the systems and methods of the present disclosure are used with one or more overlay networks implemented on a set of computing hosts that can host consumer virtual machines and producer virtual machines. Can do. Advantageously, in certain embodiments, the systems and methods of the present disclosure can be performed within the networking infrastructure of consumer hosts and producer hosts, so that the leasing process is performed by the consumer and / or producer virtual machine. Can be done without any involvement.

  When embodiments of the present disclosure are implemented in an overlay network, the producer virtual machine associated with each overlay network can be split separately between lease agents instead of splitting the producer system between lease agents. Further, when leasing a producer virtual machine to a consumer virtual machine, the lease agent can select a producer virtual machine that is assigned to the same overlay network as the consumer virtual machine that is being leased.

Network Environment Overview FIG. 1A illustrates an embodiment of a network environment 100 that provides consumer systems 104A-C access to services hosted by producer systems 106A-D. In general, the network environment 100 represents a single data center. However, in some cases, the system of network environment 100 may be distributed among multiple data centers.

  The network environment 100 may include a number of producer systems 106A-D (which may be referred to herein as “producer system 106” in the singular or may be pluralized as “producer systems 106”). , Consumer systems 104A-C (which may be referred to herein as "consumer systems 104" in the singular or may be pluralized as "consumer systems 104"). Although four producer systems 106 and three consumer systems 104 are illustrated, the network environment 100 may include any number of producer systems 106 and consumer systems 104. Further, although network environment 100 has been described above as representing one or more data centers, in some embodiments, at least some of consumer systems 104 may be independent of the data centers. For example, in some embodiments, the network environment 100 may be associated with a particular business entity or organization. In such embodiments, at least a portion of the consumer system 104 can communicate with the network environment 100, but is under the control of individual or separate entities rather than the rest of the system associated with the network environment 100. May represent a user or customer computing system to obtain.

  In general, each producer system 106 may provide services and / or computer resources to the consumer system 104. In some cases, producer systems 106 may each be able to provide the same services and / or resources to consumer system 104. In other cases, at least a portion of the producer system 106 may be able to provide different services and / or resources than the others of the producer system 106. These services and / or resources provided by the producer system 106 may include any type of service and / or computational resource. For example, services and computer resources include data storage access, external network access (eg, access to the Internet), internal resource access (eg, access to a database managed by the same entity as the network environment 100), catalog service Access to a directory service, access to an application, access to an information processing service (eg, relating to distributed processing of commands or requests), a routing service (eg, network routing service), and the like. To simplify the content discussed, in the remainder of this disclosure, in addition to the term “service” having its ordinary meaning herein, a service, computer that may be provided by or via the producer system 106 We will use the term “service” to refer to a resource, or any other resource.

  The producer system 106 can include any form of computing system. For example, the producer system 106 can include a client system, server (eg, application server, web server, etc.), laptop, desktop, database system, backup system, directory system, deduplication system, storage system, and the like. . Similarly, the consumer system 104 can include any form of computing system. For example, the consumer system 104 can include a client system, a server, a laptop, a desktop, a tablet, a mobile phone, a game machine, a television, and the like. In some embodiments, the consumer system 104 can also serve as a producer system and vice versa. For example, one consumer system 104 can access a producer system 106 (eg, a database system or a producer system acting as a storage system) to obtain data. For example, the same consumer system 104 may also act as a producer system by providing application access to another consumer system 104. In some cases, consumer system 104 and producer system 106 may be considered a client and server system, respectively. However, as discussed above, consumer system 104 and producer system 106 are not limited to such.

  Each time consumer system 104 desires or needs access to the services provided by producer system 106, consumer system 104 may be referred to in the singular form as “lease agent 102” or One or more lease agents 102A-102D (which may be pluralized as "lease agents 102") can be requested to access a producer system 106 that can provide services. In general, the consumer system 104 accesses some subset of the lease agent 102 to obtain the identity of the producer system 106 that it should access in order to fulfill the service request. The subset of lease agents 102 can be randomly selected from the available lease agents 102 and includes some of the available lease agents 102. For example, requests to access producer system 106 may be provided to three of the four available lease agents illustrated in FIG. 1A. However, in some cases, consumer system 104 may be assigned to a particular lease agent 102. Further, in some cases, consumer system 104 may provide a request to access producer system 106 to a single lease agent 102 or to each existing lease agent 102 in network environment 100.

  FIG. 1A illustrates one embodiment of communication between the lease agent 102, the consumer system 104, and the producer system 106. As can be seen in FIG. 1A, each consumer system 104 communicates with three of the four available lease agents 102. As indicated by the dashed arrows, this communication may include control information including, for example, requests to access services provided by the producer system 106 and / or control information related to requests to access the producer system 106. Further, as indicated by the solid arrows connecting consumer system 104 to a subset of producer system 106, the communication may include data related to producer system 106 that corresponds to a service request by consumer 104. Further, the lease agents 102 may communicate between the lease agents 102 to provide current status information relating to, for example, the lease agents 102 and / or the producer system 106. The illustrated intercommunication between the various systems of the network environment 100 of FIG. 1A is only one example of communication between the consumer system 104, the producer system 106, and the lease agent 102 and is restrictive. Note that this is not intended. Communication between various systems in the network environment 100 is described in further detail with respect to the processes described herein with respect to FIGS.

  FIG. 1B illustrates an embodiment of a network environment 100 that provides a consumer system 104 with access to services hosted by the producer system 106 and provides producer system health information to one or more lease agents 102. As illustrated in FIG. 1B, in some cases, data may be provided from producer system 106 to consumer system 104 and from consumer system 104 to producer system 106. In other words, in some cases, data communication may be bidirectional.

  In addition, the producer system 106 can provide health information to the lease agent 102 so that the lease agent 102 assigns which producer system 106 is functioning and which producer system 106 is assigned to the consumer system 104. You can keep track of whether you have available resources. In some cases, the producer system 106 can provide health information at a scheduled time. In other cases, the leasing agent 102 can request health information from the producer system 106 or send a ping to the producer system 106 for health information. Often, each producer system 106 is assigned to a single lease agent 102, as illustrated by producer systems 106A-106C. However, in some embodiments, the producer system 106 may be assigned to multiple lease agents 102, as in the case of the producer system 106D.

  Although FIGS. 1A and 1B illustrate different data and control channels, it is possible for the network environment 100 to implement some or all of the data and control channels illustrated in FIGS. 1A and 1B. Thus, FIG. 1B does not illustrate the channel between the consumer system 104 and the lease agent 102, but typically a control channel exists between the consumer system 104 and the lease agent 102 as illustrated in FIG. 1A. To do. Further, some or all of the channels can be unidirectional, with one system requesting data or control information and the other system providing data or control information. Alternatively or additionally, some or all of the channels may be bidirectional, and the two systems in communication may request data or control information and provide data or control information.

  FIG. 2 illustrates an alternative view of an embodiment of a network environment 100 that provides a consumer system 104 with access to services hosted by the producer system 106. As illustrated in FIG. 2, each of the systems in the network environment 100 can communicate with each other via the network 202. The network 202 can include any type of wired or wireless network and combinations thereof. For example, the network 202 can include a local area network (LAN), a wide area network (WAN), a cellular network, an Ethernet-based network, a WiFi network, a WiLAN network, and the like. Further, in some cases, the network 202 can include the Internet.

  As illustrated in FIG. 2, each of the systems described in FIG. 1A may include several subsystems that may be implemented in hardware or software. For example, the consumer system 104 may include a lease requester 240, a current status module 242, a connection module 244, and a resource requester 246. Lease requester 240 may be configured to request one or more lease agents 102 for a lease for one or more producer systems 106. In some cases, lease requester 240 may specifically request access to producer system 106. In other cases, the lease requester 240 may request access to the service with or without explicitly requesting access to the producer system 106.

  Once the lease requester 240 obtains identification information for one or more producer systems 106, the connection module 244 may attempt to establish communication with some or all of the producer systems 106 identified by the lease agent 102. After the connection with the producer system 106 is established, the resource requester 246 can request resources or services from the producer system 106 that the consumer system 104 has established without failing the connection.

  The current status module 242 can obtain current status information related to the producer system 106. This information can then be provided to the lease agent to facilitate the lease agent 102 for access to the producer system in response to a request from the consumer system 104 for access to the producer system 106. This information may be provided to the corresponding current status module 228 of the lease agent 102. In some cases, status module 242 obtains status information based on the success or failure of establishing a connection with producer system 106. In other cases, the current status information is obtained by querying the producer system 106 and / or the corresponding current status module 262 included as part of the producer system 106. The current status information may include any information regarding connection with the producer system 106 and / or provisioning of services by the producer system 106. For example, the current status information may include information related to the success or failure of establishing communication between the consumer system 104 and the producer system 106. As another example, the current status information may include the number of consumer systems 104 accessing the producer system 106 during a given period. Further examples can include information related to resources available at the producer system 106, the responsiveness of the producer system 106, the capabilities of the producer system 106, the producer system, and the like.

  As illustrated in FIG. 2, the producer system 106 may include a registration module 260 and a status module 262. As described above, the current status module 262 may provide current status information related to the producer system 106 to the consumer system 104 that requests current status information related to the producer system 106. Further, in some cases, status module 262 may provide status information to lease agent 102 either independently or in response to a request from lease agent 102.

  Registration module 260 is configured to register producer system 106 with lease agent 102. In certain embodiments, the registration module 260 may automatically register the producer system 106 as part of an initialization routine when the producer system 106 is first started. In other embodiments, the registration module 260 may register the producer system 106 in response to commands from a user or application. In some cases, registration module 260 may re-register producer system 106 when producer system 106 determines that the assigned lease agent is no longer available.

  As previously described, the lease agent 102 may also include a status module 228. The current status 228 module can receive current status information from one or both of the consumer system 104 and the producer system 106 regarding the current status of the producer system 106. Further, the status module 228 may provide status information associated with the producer system 106 to another lease agent 102. Further, in some cases, the current status module 228 may perform health checks on other lease agents 102 by requesting current status information from other lease agents 102. For example, status module 228 may determine whether lease agent 102 is no longer available based on whether a health check request is answered by lease agent 102. In some cases, status module 228 can perform a health check of producer system 106 by requesting status information from producer system 106.

  In addition to the current status module 228, the lease agent 102 can include a producer repository 220, a split system 222, a lease system 224, and a registration module 226. The producer repository 220 can include any form of database, repository, or storage device that stores information related to the producer system 106. For example, the producer repository 220 may include current status information associated with the producer system 106, identification information of the producer system 106, and information related to the allocation or partition of the producer system 106 between the lease agents 102. In some embodiments, some or all of the information stored in the producer repository 220 may be stored in the agent repository 206 instead of or in addition to the producer repository 220.

  The partitioning system 222 can include any system that can partition the available producer system 106 among the lease agents 102 of the network environment 100. In general, the splitting system 222 divides the available producer system 106 into non-overlapping or non-equivalent subsets, and then assigns one subset to each lease agent 102. Thus, if there are four lease agents 102, producer system 106 may divide one subset into four subsets associated with each lease agent 102. However, in some cases, the subsets can overlap. In such cases, producer system 106 may be assigned to multiple lease agents 102 or may be associated with multiple lease agents 102. The process of dividing the producer system 106 among the lease agents 102 can occur when the network environment 100 is first initialized. Furthermore, the process can be regenerated periodically. For example, there is a change in the number of available producer systems 106, whether the process of dividing the producer system 106 is through the addition or removal of available producer systems 106. It can occur every time or when there is a threshold change in the available producer system 106.

  Each time the consumer system 104 requests the lease agent 102 to access the producer system 106, the lease system 224 may, for example, include the producer system 106 location (producer system 106 (eg, geographic location, data center, server rack). , Etc.) and the producer system 106 to lease to the consumer system 104 based on several factors including whether the producer system 106 has access to the resources that the consumer system 104 is seeking access to Once the lease system 224 has identified the producer system, the lease system 224 can request that the consumer system requesting the producer system 106 identification information. 104. In addition, in some cases, the lease system 224 may provide the consumer system 104 with a lease time that allows the consumer system 104 to access the producer system 106. Alternatively, or additionally The system 224 may provide a large amount of some other consumable resource or metric to the consumer system 104. For example, the consumable resource may be a calculation cycle, money, disk storage, a connection request, etc. .

  Registration module 226 may serve as a counterpart to registration module 260 of producer system 106. Upon receiving a request from the producer system 106 to register with the lease agent 102, the registration module 260 of the lease agent 102 may determine whether the producer system 106 is assigned to the lease agent 102. If assigned, the registration module 226 can register the producer system 106, which is the availability status of the producer system 106, as well as current status information associated with the producer system 106, eg, in the producer repository 220. Can be stored. On the other hand, if registration module 226 determines that producer system 106 is not assigned to lease agent 102, registration module 226 can identify another lease agent 102 assigned to producer system 106, and The producer system 106 can be informed of the identification information of the lease agent 102 assigned to the producer system 106.

  In certain embodiments, the network environment 100 may include an agent repository 206 and / or a split system 204. Agent repository 206 may include information regarding lease agent 102 and / or producer system 106 included within network environment 100. Information stored in agent repository 206 may be used by one or more of lease agent 102, consumer system 104, and producer system 106. For example, in some cases, the lease agent 102 may use the agent repository 206 to determine the number and / or identification information of the producer system 106 in the network environment 100. Using this information, the lease agent 102 can determine how to partition the producer system 106. In some cases, consumer system 104 may use agent repository 206 to determine where producer system 106 is located after producer system 106 has been identified by lease agent 102 for access by consumer system 104. As another example of using the agent repository 206, in some cases, the producer system 106 accesses the agent repository, eg, identifying the lease agent 102 to access when the producer system 106 is first started. Information can be determined.

  In some embodiments, the splitting system 204 may perform a process of splitting the producer system 106 among the lease agents 102. In such an embodiment, the lease agent 102 may not include the split system 222 itself.

  In some embodiments, at least some of the modules included in the exemplary system of FIG. 2 may be integrated with applications and / or resources provided by the system. For example, the current state module 262 of the producer system 106 may be integrated with applications and / or resources provided by the producer system 106. Similarly, the current state module 242 can be integrated with applications or services hosted by the consumer system 104.

Exemplary Process for Accessing Services at a Producer System FIG. 3 illustrates an embodiment of a process 300 for accessing services at a producer system 106. Process 300 may be implemented by any system that can access services or computer resources at producer system 106 by obtaining a lease or temporary authorization to access producer system 106 from lease agent 102. . For example, process 300 may be implemented in whole or in part by consumer system 104, lease requester 240, connection module 244, resource requester 246, and status module 242 to name a few. Although any number of systems may perform process 300 in whole or in part, to simplify the discussion, each part of process 300 will be described with reference to a particular system.

  Process 300 begins at block 302, for example, lease requester 240 generates a lease request for access to producer system 106. In some cases, the lease request may include identification information of a computer resource or service that the consumer system 104 or application user on the consumer system 104 desires to access. In other cases, the lease request includes a request to access the producer system 106 without specifying a service at the producer system 106 that is to be accessed by the consumer system 104.

  At block 304, lease requester 240 provides the lease request to a subset of lease agents 102 included in network environment 100. In some cases, lease requester 240 may provide a lease request to some or all available lease agents 102. The lease requester 240 may identify available lease agents 102 by accessing an agent repository 206 that may include identification information for each lease agent 102 in the network environment 100. In other cases, the consumer system 104 may each be configured with the identification information of the lease agent 102 at initialization or startup, or at any other time during operation of the consumer system 104. For example, a user (eg, an administrator) may provide lease system 102 identification information to consumer system 104. The identification of the lease agent 102 is for identifying the name of the lease agent 102, the address of the lease agent 102 (eg, an Internet Protocol (IP) address or other network address), and / or the lease agent 102 in the network environment 100. Can include any other information that can be used. In some embodiments, providing the lease request to the lease agent 102 provides the lease agent 102 with current status information related to one or more producer systems 106 with which the consumer system 104 has previously communicated. Can be included.

  At block 306, the consumer system 104 receives an identification of the producer system 106 from each of the subsets of lease agents 102 that were provided a lease request at block 304. In some cases, consumer system 104 receives an indication of producer system 106 from a subset of lease agent 102. For example, consumer system 104 may receive an identification of producer system 106 from one or two lease agents 102, or an entire subset of lease agents 102. If the consumer system 104 does not receive any producer system 106 identification information, the process 300 may end, the operations associated with blocks 302 and / or 304 may be repeated, and / or a user (eg, an administrator). A warning can be issued. In some cases, receiving the identification of producer system 106 receives the length of time that consumer system 104 is allowed to access producer system 106 or lease access to producer system 106. Including doing. Each lease agent 102 in the subset of lease agents 102 can provide identification information for a single producer system 106. However, in some cases, each lease agent 102 in the subset of lease agents may provide identification information for multiple producer systems 106. As with the lease agent 102 identification information, the producer system 106 identification information may be any information that identifies the producer system 106 to the consumer system 104 or provides a way to access the producer system 106. Can be included. For example, the identification information of the producer system 106 may be, for example, a name, address (eg, IP address) that can be used to identify the location of the producer system 106 in a table or data structure stored in the agent repository 206. Or an identifier can be included.

  In some cases, block 306 may include receiving current status information for the producer system 106 identified by each of the subsets of lease agents 102. This current status information can be used to help determine which producer system 106 the consumer system 104 should access. In some cases, current status information may be obtained by a lease agent 102 that communicates with the producer system 106. Alternatively or additionally, current status information may be obtained from the consumer system 104 that previously communicated with the producer system 106. The received current status information may include an independent set or subset of current status information available to the lease agent 102. In some cases, the received current status information may or may not intersect with current status information available to the lease agent 102.

  The connection module 244 attempts to initiate a connection with each of the producer systems 106 identified at block 306 at block 308. In some cases, connection module 244 may attempt to initiate a connection with a subset of producer system 106 identified at block 306. Attempting to initiate a connection can include any process that attempts to open a communication channel with the producer system 106. For example, attempting to initiate a connection can include sending a connection request packet to the producer system 106. In general, the connection module 244 may attempt to establish a connection with the producer system 106 when the consumer system 104 receives the producer system 106 identification information. For example, the lease agent 102 may be located at a different distance from the consumer system 104, or may have different loads, so it is rare if the consumer system 104 receives responses from multiple lease agents 102 at the same time. Module 244 rarely initiates connections with multiple producer systems 106 simultaneously. Instead, attempts to initiate a connection with the producer system 106 may be staggered, even to a small degree. However, in some embodiments, the connection module 244 may attempt to initiate connections with multiple producer systems 106 at the same time. For example, in some cases, consumer module 104 may wait until each of a subset of lease agents 102 responds, or in some circumstances responses may be received from multiple lease agents 102 simultaneously.

  At block 310, the resource requester 246 accesses the service or computer resource of the first producer system 106 that establishes the connection without failure, or the access to the service or computer resource. Request. In some cases, establishing the connection with the producer system 106 without failure may include receiving an acknowledgment (“ack”) packet or the like from the producer system 106. For similar reasons as described above with respect to block 308, the connection with the producer system 106 may be staggered. However, in cases where the connection module 244 establishes a connection with more than one producer system 106 at the same time or substantially at the same time, the resource requester 246 may request the producer system to request access to the service. 106 can be selected at random. Alternatively, resource requester 246 can use a selection algorithm to determine which producer system 106 should request the service. The selection algorithm is not limited and can include, for example, round robin, least time unreferenced (LRU), or any other type of selection algorithm. In some embodiments, the consumer system 104 may request access to some or all services of the producer system 106 with which a communication connection or channel has been established. In some cases, the services may be in the same format. In other cases, consumer system 104 may request access to different services of each producer system 106.

  Further, if the connection is established without failure with more producer systems that the consumer system 104 requires at a particular point in time, the consumer system 104 abandons the lease to one or more additional producer systems 106. Can do. Alternatively, the consumer system 104 may maintain a lease to a further producer system 106 on a lease pool to maintain a connection with the further producer system 106. In such a case, if the consumer system 104 needs access to additional services at some time during the lease period with the additional producer system 106, the consumer system 104 has maintained the lease in the lease pool. One service of the further producer system 106 can be used.

  At block 312, the status module 242 receives status metadata from the first connected producer system 106. In some cases, the current status module 242 may receive current status metadata from each producer system 106 that establishes a communication channel without the connection module 244 failing. Further, the current status module 242 may obtain current status metadata from the producer system 106 that the connection module 244 was unable to establish a communication channel. For example, the fact that the connection module 244 was unable to establish a communication channel with a particular producer system 106 may be included as current metadata associated with the producer system 106. The current metadata is not limited and includes information relating to establishing a connection with the producer system 106, information relating to maintaining a connection with the producer system 106, information relating to the responsiveness of the producer system 106, In addition, information related to services available in the producer system 106 can be cited. For example, the current metadata includes the amount of time that has elapsed when connecting to the producer system 106, the waiting time for connecting to the producer system 106, the processing resources available in the producer system 106, and requests (eg, lost There may be the number of times (for packets) that must be retransmitted to the producer system 106 and any other type of data that can be associated with the current state of the producer system 106.

  In some embodiments, block 312 may be performed before block 310. In such a case, current status module 242 may receive current status information from each connected producer system 106. The consumer system 104 in such a case can select the producer system 106 that should access the service based on the received current status information.

  At decision block 314, for example, the consumer system 104 using the resource requester 246 determines whether access to another service is desired. The other service may be a different service or may be the same type of service. For example, in some cases, one service may be for accessing a network application, and another service is for download network resources (eg, images or videos hosted by a network page, such as a web page). Can be. Alternatively, both services can be used to download network resources. For example, a user may download two network pages or resources from two network pages. If so, the connection module 244 initiates a connection with the producer system 106 identified at block 308. In some cases, the connection module 244 initiates a connection with the producer system 106 identified in the lease pool associated with the consumer system 244. The lease pool may include identification information for the producer system 106 that is currently leased to the consumer system 104 that provides access to the resource. In some cases, the lease pool includes a producer system 106 that is leased to the consumer system 104 but is not currently accessed by the consumer system 104. If the lease pool does not include any leases, consumer system 104 may perform process 300 again using, for example, lease requester 240. In some embodiments, the decision block 314 is optional. For example, if the producer system 106 is not leased to the consumer system 104, the process 300 may be repeated starting at block 302.

  In some embodiments, process 300 can be used to renew a previous lease with producer system 106. In such a case, the lease request generated at block 302 may include identification information of the producer system 106 that the consumer system 104 has previously accessed. In addition, the lease request can include an indication that the request is an update request. The renewal lease request can then be provided to the lease agent 102 that initially identified the producer system 106 to the consumer system 104. Assuming that the lease agent 102 determines that the producer system 106 is still available and / or has the ability to service the consumer system 104, the lease agent 102 indicates that the renewal request has been approved. And a length of time for the renewal lease to the consumer system 104 can be provided as part of the block 306. The consumer system 104 maintains a lease with one or more additional producer systems 106 in the lease pool, and the lease period does not require the consumer system 104 to use the services at the additional producer system 106, so that the additional producer system 106. If so, the consumer system 104 may allow the lease to be invalidated without sending the lease renewal request 106 corresponding to the further producer system to the lease agent 102.

  In some cases, the process of requesting a lease renewal can occur at the expiration of an existing lease. In other cases, for example, consumer system 104 using resource requester 246 may determine the probability that an existing service request to access a service at one or more producer systems 106 will not be completed before the lease time expires. . If the probability meets the renewal threshold, the consumer system 104 may request that the producer system 106 resume the lease at some point prior to the expiration of the existing lease, thereby reducing or preventing service outages due to lease expiration. Is done.

  In certain embodiments, lease access to producer system 106 may include making payments to an organization or entity associated with one or more of producer system 106 and / or lease agent 102. For example, the producer system 106 may be provided as part of an access fee service. Alternatively, lease access to the producer system 106 may not require any type of payment. In such an embodiment, a lease refers to the temporary nature 106 of access to the producer system and not a financial lease.

Exemplary Process for Providing a Producer System Leasing to a Consumer System FIG. 4 illustrates an embodiment of a process 400 for providing a producer system 106 lease to a consumer system 104. Process 400 may be implemented by any system capable of providing producer system 106 identification information to consumer system 104. Further, process 400 may be implemented by any system that can lease access to producer system 106 to consumer system 104. For example, process 400 may be implemented in whole or in part by lease agent 102, lease system 224, and status module 228, to name a few. Although any number of systems may implement process 400 in whole or in part, to simplify the discussion, each part of process 400 will be described with reference to a particular system.

  Process 400 begins at block 402, for example, lease system 224 of lease agent 102 receives a request from consumer system 104 to lease access to producer system 106. In some instances, the request may include identification information for a particular service or computing resource that consumer system 104 is seeking to access at producer system 106. As described in the previous section, in some cases, the lease request may include a request to renew an existing lease by the consumer 104 of the producer system 106.

  At block 404, status module 228 may receive status metadata for one or more producer systems 106 from consumer system 104. This received current metadata may include data associated with a previous attempt by the consumer system 104 to communicate with or access one or more producer system 106 services. For example, the received current metadata may include latency information, data related to the responsiveness of the request by the consumer system 104 to the producer system 106, or any other information previously described with respect to block 312. Further, the received current metadata may include data received from the producer system 106 and / or data current metadata generated by the consumer system 104 based on interaction with the producer system 106. In some embodiments, block 404 may be optional. For example, if the request is the first request received from consumer system 104, consumer system 104 may not have any current metadata to provide to lease agent 102.

  At block 406, the current status module 228 updates the producer system current status information based on the current status metadata received at block 404. In some cases, updating the producer system status information may include updating an entry associated with the producer system 106 in the producer repository 220. In some embodiments, block 406 may be optional.

  Further, at block 408, the current status module 228 provides at least a portion of the current status metadata received at block 404 to the second lease agent. For example, the lease agent 102 executing the process 400 may determine that some of the current metadata is that of the producer system 106 assigned to a different lease agent 102. In such a case, the lease agent 102 may provide current status information to the lease agent 102 assigned to the producer system 106. In other cases, the lease agent 102 may provide current metadata to all lease agents 102 with which the lease agent 102 communicates, such that all lease agents are part or all of the lease agents 102 in the network environment 100. possible. Any form of data transmission, reproduction and / or synchronization process may be implemented in the network environment 100 to share current metadata between the lease agents 102. For example, a flood fill algorithm or a Prim algorithm may be used to share data between lease agents 102. A further system and method for sharing data between lease agents 102 that may be used herein is described in US patent application Ser. No. 12 / 980,133, filed Dec. 28, 2010, entitled “DATA REPLICATION FRAMEWORK”. US Patent Application No. 12 / 980,153 entitled “DATA REPLICATION FRAMEWORK” filed on Dec. 28, 2010 and United States of America, filed on Dec. 28, 2010, named “DATA REPLICATION FRAMEWORK”. No. 12 / 980,193 and US patent application Ser. No. 12 / 980,258, filed Dec. 28, 2010, entitled “DATA REPLICATION FRAMEWORK”. Each of these aforementioned applications is incorporated in their entirety from this specification.

  In some embodiments, block 408 is optional. For example, in some embodiments, only the consumer system 104 provides the lease agent 102 with current metadata of the producer system 106 that is assigned to the lease agent 102 that received the request at block 402.

  At block 410, the lease system 224 selects a producer system based on producer status information associated with each producer system 106 allocated or assigned to the lease agent 102. In some cases, the producer current state information is based on information provided by consumer system 104 (eg, current state metadata received at block 404). In other cases, the producer status information may be based on information obtained by the lease agent 102 in communication with the producer system 106. For example, the lease agent 102 may perform a health or status check of each producer system 106 assigned to the lease agent 102. These health checks may include confirming communication of the producer system 106, requesting the producer system 106 to update resource availability, or any other information that obtains information relating to the current state of the producer system 106. List the processes. In addition, producer status information may be based on information received from other lease agents 102.

  In certain embodiments, selecting a producer system 106 may be based at least in part on weights associated with different producer systems 106. These weights can be generated based on producer status information. For example, producer status information indicating that producer system 106 has a low latency and a low error rate when communicating with consumer system 104 causes producer system 106 to be weighted higher and consequently selected at block 410. Can be more likely. Conversely, a producer system 106 that often breaks the connection with the consumer system 104 may be less weighted and consequently less likely to be selected at block 410.

  In some cases, the selection of producer system 106 may be based on any number of additional factors, such as the location of producer system 106 with respect to consumer system 104. The location information can include, for example, whether the producer system 106 is located in the same data center as the consumer system 104 or in the same server rack. Selecting the producer system 106 may be based on the service requested by the consumer system 104 in some cases. In yet other cases, the selection of the producer system 106 may be based in part on the amount of lease time requested and / or previously allocated by the consumer system 104. In some cases, leasing system 224 may select the least loaded producer system 106. In other cases, the leasing system 224 may select the producer system 106 from a set of producer systems 106 that have a load below a threshold. In some embodiments, the load on the selected producer system 106 is determined to have increased at the time of selection, regardless of whether the consumer system 104 has established a connection with the selected producer system 106. Advantageously, in certain embodiments, the same producer system 106 can threshold the number of times in the time period by recording increased load for the selected producer system 106 regardless of the established consumer connection with the producer system. The probability that more will be selected is reduced, although the actual load on the producer system 106 may be low, but the predicted load of future connections with the consumer system 104 is in selecting the producer system. It is because it is considered.

  In some cases, selecting the producer system 106 at block 410 may include selecting the producer system 106 having the lowest load with respect to one or more load metrics (eg, connection, processor utilization, etc.). Alternatively, selecting the producer system 106 may include selecting the producer system 106 that is one of a set of producer systems 106 having a load below a threshold load. Selection of a producer system 106 among a set of producer systems 106 having a load below a load threshold may be based on random, pseudo-random, or selection algorithms (eg, minimum time unreferenced, median load, etc.). Advantageously, in some embodiments, instead of always selecting the producer system 106 with the lowest load, by selecting the producer system 106 from a set of producer systems 106, the probability of load fluctuations and / or Occurrence is reduced. In addition, a load bubble or load hotspot occurs, such as the occurrence of a subset of the system that passes through the network environment 100 and is associated with a high load compared to the rest of the network environment 100. Is reduced.

  At block 412, the lease system 224 provides lease information to the consumer system 104 for the producer system 106 selected at block 410. This lease information can include the identification information of the producer system 106 and, in some cases, the amount of lease time that the consumer system 104 is allowed to access the producer system 106. As noted above, the producer system 106 identification information can include any information that can facilitate locating and accessing the producer system 106, such as a network address. In some embodiments, providing the identification information of the producer system 106 can include providing a certificate or public key to facilitate communication with the producer system 106.

  As indicated above, in some cases, the process 400 can be used for lease renewal requests. In such a case, block 410 may include determining whether the producer system 106 for which the consumer system 104 requested a lease renewal is still available for lease. Determining whether the producer system 106 is still available for lease may include determining whether the producer system 106 has a resource capacity that continues to correspond to the consumer system 104. Further, determining whether the producer system 106 is still available for lease includes determining whether one or more metrics of the producer status information associated with the producer system 106 meet an availability threshold. Can do. For example, the determination can include checking whether the error rate associated with the producer system 106 is below a threshold error rate. If producer system 106 is available for lease renewal, lease agent 102 can send the updated lease of producer system 106 to consumer system 104. If the lease agent 102 determines that the producer system 106 is not available for lease renewal, the lease agent 102 can report to that effect and / or provide lease information for the alternative producer system 106.

Exemplary Producer System Update Process FIG. 5 illustrates an embodiment of a producer system update process 500. Process 500 may be implemented by any system that can update the availability of producer system 106 and that can subdivide producer system 106 among lease agents 102. For example, process 500 may be implemented in whole or in part by lease agent 102, split system 222, split system 204, registration module 226, and status module 228, to name a few. Any number of systems may perform the process 500, in whole or in part, but to simplify the discussion, the portions of the process 500 are referred to a particular system and a particular system. explain.

  The process 500 begins at decision block 502, for example, the status module 228 of the lease agent 102 determines whether a status update has been received from the producer system 106. A current update may be anticipated by the lease agent 102 in response to a request sent by the lease agent 102 to the producer system 106. Alternatively, the current status module 228 can anticipate current status updates for an update schedule associated with each producer system 106. For example, in some cases, each producer system 106 may be configured to automatically communicate current updates or provide current updates to assigned lease agents 102 hourly or daily. If a status update is received, the process 500 returns to decision block 502 and waits for the next status update. Further, the current status module 228 may update the producer current status information associated with the producer system 106 in the producer repository 220 and / or the agent repository 206.

  On the other hand, if a current status update is not received at decision block 502, current status module 228 updates the current status of producer system 106 to indicate that producer system 106 is unavailable at block 504. Updating the current status of the producer system 106 may include storing an indication in the producer repository 220 and / or the agent repository 206 that the producer system 106 is leased to the consumer system 104 and is not available. . In some cases, even when a current status update is received at decision block 502, current status module 228 may update the current status of the producer system at block 504 to indicate that producer system 106 is not available. For example, if the current status information received indicates that the producer system 106 is malfunctioning, responding to a request at a threshold speed, or generating an error that exceeds a threshold error rate, the current status module 228. May update the producer repository 220 and / or the agent repository 206 to indicate that the producer system 106 is no longer available. In some embodiments, updating the producer status information of the producer system 106 to indicate its loss of availability may include alerting the administrator that the producer system 106 is no longer available. The update of the producer system 106 current information is described in more detail with respect to FIG.

  At decision block 506, partitioning system 222 determines whether the threshold amount of producer system 106 has become unavailable. If not, process 500 returns to decision block 502 and waits for the next status update. If split system 222 determines at decision block 506 that the threshold amount of producer system 106 has become unavailable, split system 222 performs a producer sub-partition process at block 508. This producer system subdivision process is described in more detail below with respect to FIG. In some embodiments, one or both of decision block 506 and block 508 is performed by partitioning system 204.

Exemplary Split Process FIG. 6 illustrates an embodiment of a split process 600 that splits a set of producer systems 106. Process 600 can be implemented by any system that can track changes in the number of available producer systems 106 and that can subdivide producer systems 106 among lease agents 102. For example, process 600 may be implemented in whole or in part by lease agent 102, split system 222, split system 204, registration module 226, and status module 228, to name a few. Any number of systems may implement process 600, in whole or in part, but to simplify the discussion, parts of process 600 are referred to a particular system and a particular system. explain.

  Process 600 begins at block 602, for example, status module 228 tracks available producer system 106 differences. In some cases, status module 228 tracks absolute changes in the number of available producer systems 106. Alternatively or additionally, status module 228 tracks the rate of change in the number of available producer systems 106. Differences or changes in the available producer system 106 may be based on the addition of a new producer system 106 or a loss of availability of the producer system 106. In some embodiments, process 500 may be used to identify a loss of availability of producer system 106. Further, the determination of the available producer system 106 may be based on user updates that indicate the loss or addition of the producer system 106. Further, the addition of producer system 106 may be tracked based on registration attempts by producer system 106. In some cases, the availability of producer system 106 may be determined based on information provided by consumer system 104. Further, available producer differences or changes may be tracked in terms of actual numbers or in terms of percentage changes in availability of the producer system 106.

  In some embodiments, differences between producer system 106 and / or available producer system 106 are tracked by each lease agent 102. Alternatively, each lease agent 102 tracks available producer systems assigned to the lease agent 102. Additionally or alternatively, available producer system 106 counts and / or differences are tracked by an independent system, such as splitting system 204.

  At decision block 604, the partitioning system 222 determines whether the available producer system 106 differences meet a threshold. This difference can be an absolute value. In other words, the addition or deduction of the producer system 106 can be tracked. In certain embodiments, producer system 106 additions and subtractions may be independently tracked with separate thresholds associated with each. Thus, in some cases, one or both thresholds can be met even though the total change in available producer system is zero or does not meet the combined threshold. In some cases, the difference may represent a percentage change and / or a rate of change. In such cases, the threshold may be a percentage threshold and / or a rate of change threshold.

  If the difference does not meet the threshold, or if any of the differences do not meet the corresponding threshold, then the current state module 228 changes the available producer system 106 or the available producer system 106 at block 602. Keep track. On the other hand, if the difference meets the threshold, or if the difference meets the corresponding threshold, the splitting system 222 causes the lease agent 102 executing the process 600 to perform the splitting or subdividing process of the producer system 106 at block 606. When it has started, it notifies other lease agents 102. Advantageously, in certain embodiments, the process 600 notifies multiple lease agents 102 by notifying other lease agents 102 that the lease agent 102 executing the process 600 has begun a split process. While avoiding having the split process run at the same time, doing so may cause non-optimal results due to race conditions in the counting and splitting of the producer system 106, for example. In some embodiments, block 606 may be optional. For example, in some embodiments, a splitting system 204 that is separate from the lease agent 102 may perform a splitting or subdividing process.

  At block 608, the partitioning system 222 obtains identification information for the available producer system 106. The splitting system 222 may obtain the identification information of the producer system 106 that is available by accessing the producer repository 220 and / or by accessing the agent repository 206. In some cases, splitting system 222 may obtain identification information for available producer system 106 by contacting other lease agents 102.

  At block 610, split system 222 splits available producer system 106 between lease agents 102. The partitioning system 222 can partition the producer system 106 using any type of partitioning algorithm. In general, the partition of the producer system 106 between the lease agents 102 creates a non-overlapping or non-equivalent set of producer systems 106 that can be assigned to the lease agent 102. However, in some cases, the splits can overlap. Further, in some cases, the subset may be unbalanced. In other words, some lease agents 102 may be assigned more producer systems 106 than other lease agents 102. If the subset is imbalanced, the number or percentage of producer systems 106 assigned to a particular lease agent 102 is at least partially processed by the lease agent 102 and / or producer system 106 assigned to the lease agent 102. Based on the number of requests that can be made. For example, if a first lease agent 102 is assigned a producer system 106 that allows the first lease agent to handle more consumer system 104 requests than other producer systems 106, another lease agent 102. Fewer producer systems can be assigned.

  Further, in embodiments where some producer systems 106 can provide different services than other producer systems, the producer systems 106 can be assigned a producer system that allows each lease agent to provide a particular service. Can be divided. Alternatively, a producer system 106 that can provide a particular service can be divided between selected subsets of lease agents 102.

  At block 612, the split system 222 of the lease agent 102 executing the process 600 updates each of the other lease agents 102 in the network environment 100, and the producer system 106 identification information is displayed upon completion of block 610. Assigned to each lease agent 102. In some embodiments, block 612 may include updating the lease agent 102 performing the process 600 with the identity of the producer system 106 assigned to the lease agent 102 itself. Updating the lease agent 102 with the identification information of the producer system 106 may include updating a table or database in the producer repository 220. In some cases, since lease agent 102 is performing process 600, block 612 is optional for lease agent 102 and is performed only for other lease agents 102 included within network environment 100. The

  In some embodiments, process 600 may be used to perform an initial partition of producer system 106 between lease agents 102. For example, when the network environment 100 is initially configured, the difference of available producer systems 106 is likely to meet the threshold of decision block 604 when the available producer system 106 is activated. Alternatively or additionally, the user may manually initiate the split process when the network environment 100 is first configured, or at any other time.

  Process 600 has been described as partitioning producer system 106 among lease agents 102. However, process 600 is not limited as such. In some cases, process 600 may be used to split a lease that may be provided to consumer system 104 for accessing producer system 106 between lease agents 102. For example, the lease agent 102 or split system 222 can identify a set of available producer systems and determine the number of leases available to each producer system of the set of available producer systems. . The lease agent 102 performing the process 600 may be the first lease agent 102 that detects a changed threshold in available leases, or is a lease agent 102 designated to perform lease splitting. possible. The lease agent 102 may identify the number of available leases based on current status information received from each producer system 106 (eg, during registration of the producer system 106). Alternatively or additionally, the number of available leases may be determined based on the type of producer system 106 or configuration information received from the producer system 106 or a user (eg, an administrator).

  The lease agent 102 assigns a number of leases available to each producer system 106 by assigning each lease agent 102 of the plurality of lease agents 102 a subset of leases belonging to the number of leases available to each producer system 106. Can be divided among the leasing agents 102. The number of leases may be equally or substantially equally divided among the lease agents 102. In some cases, at least some of the lease agents 102 may be assigned one more or one less lease because the number of leases is not a multiple of the number of lease agents 102. Further, in some cases, leases may not be equally divided due to, for example, configuration differences between some lease agents 102 and / or some producer systems 106. In some cases, each lease agent 102 is assigned a non-overlapping set of leases. Alternatively, at least some of the leases can be assigned to multiple lease agents 102. In some embodiments, the plurality of lease agents 102 whose leases to the producer system 106 will be split may be a subset of the lease agents 102. For example, in some cases, a subset of lease agents 102 may be assigned to a subset of producer system 106.

  After splitting some leases or while splitting, the lease agent 102 performing the process 600 assigns the lease agent 102 to the lease agent 102 for each lease agent 102 of the plurality of lease agents 102 May provide a subset of leases to be provided. Providing a lease to each of the lease agents 102 may include providing each of the lease agents 102 with a number of leases for each producer system 106 assigned to each lease agent 102. Alternatively or additionally, providing a lease to each of the lease agents 102 may include providing the lease agent 102 with identification information for each assigned lease. Further, providing a lease may include communicating connection with the producer system 106 and / or providing connection information utilizing the producer system 106 lease.

  Advantageously, in some embodiments, dividing the number of leases available to each producer system 106 among the plurality of lease agents 102 can reduce the workload distribution among the plurality of lease agents 102. to enable. In some cases, it is unnecessary for the lease agent 102 executing the process 600 to provide a subset of leases that are assigned to itself when the lease agent is executing the process 600. However, in some cases, lease agent 102 may provide a lease to itself. For example, the lease agent 102 that performs the process 600 when the subsystem of the lease agent 102 that performs the split (eg, the split system 222) and the subsystem that receives and / or tracks leases assigned to the lease agent 102 are different. May provide the identification information of the assigned lease to itself.

  In some cases, process 600 may be used to split both producer system 106 and the lease associated with each of producer system 106 between lease agents 102.

Exemplary Producer System Registration Process FIG. 7 illustrates an embodiment of a producer system registration process 700 from the producer system 106 perspective. Process 700 may be implemented by any system that can register producer system 106 with lease agent 102. For example, process 700 may be implemented in whole or in part by producer system 106, registration module 260, and status module 262, to name a few. Any number of systems may implement process 700, in whole or in part, but to simplify the discussion, parts of process 700 may be referred to a particular system and a particular system. explain.

  Process 700 may occur each time producer system 106 is first started or initialized, or restarted or reinitialized after, for example, an inactive state or period of system restart. In some cases, process 700 may occur or reoccur each time producer system 106 determines that assigned lease agent 102 is no longer available. The determination that the assigned lease agent 102 is no longer available is after providing a current update, for example, information obtained from the agent repository 206 or received from a user, or the current update described with respect to FIG. This may be based on the case where the producer system 106 has not received an ACK from the assigned lease agent 102.

  Process 700 begins at block 702, where, for example, registration module 260 accesses a set of lease agent 102 identification information, eg, from agent repository 206. In some cases, the producer system 106 may access the identification information for the set of lease agents 102 from internal storage. For example, the producer system 106 may be preconfigured with identification information for a set of lease agents 102. In other cases, the user may specify the lease agent 102 to access.

  At block 704, registration module 260 selects lease agent 102 from the set of lease agents 102 identified at block 702. Registration module 260 may select lease agent 102 randomly or by using any other selection method, such as round robin or least recently used method. When a set of lease agents 102 is sorted, registration module 260 may select the first lease agent 102 in the sorted set. In certain embodiments, block 704 may be optional. For example, block 704 is unnecessary if the user specifies the lease agent 102.

  At block 706, registration module 260 initiates or attempts to initiate a connection with lease agent 102 selected at block 704. In some cases, attempting to initiate a connection with lease agent 102 includes an attempt to register with lease agent 102.

  At block 708, registration module 260 receives a connection response from lease agent 102. The registration module 260 determines at decision block 710 whether the connection response confirms registration of the producer system 106 or indicates identification information of the second lease agent 102. If the registration module 260 determines that the connection response confirms registration of the producer system 106 at decision block 710, the current state module 262 provides status information related to the producer system 106 to the lease agent 102 at block 712. This status information may include any information related to the status or current status of one or more metrics associated with the producer system 106. For example, the status information may include the availability of one or more computational resources (eg, memory, processor, network bandwidth, applications, etc.), the number of consumer systems 104 that a service request will be processed by the producer system, and Any other information related to the state of the producer system 106 can be included.

  The process associated with block 712 may occur when the registration module 260 determines that the connection response confirms registration of the producer system 106. Alternatively or additionally, the process associated with block 712 may occur at some later time. Further, in some embodiments, the process associated with block 712 may occur continuously, intermittently, or in response to a request from the lease agent 102 for the current update of the producer system 106. Can occur. In other embodiments, the process associated with block 712 may occur whenever there is a change in the state or current threshold of the producer system 106. For example, the process associated with block 712 may occur when the availability of processing resources of the producer system 106 falls to a threshold level.

  If registration module 260 determines at decision block 710 that the connection response received at block 708 includes an indication of the second lease agent, registration module 260 connects to the second lease agent at block 714. To start. As described with respect to process 800, the second lease agent may include a first lease agent determined to be associated with producer system 106 (eg, the lease agent identified at block 704).

  At block 716, status module 262 provides status information to the second lease agent. In certain embodiments, block 716 may include one or more of the previous embodiments with respect to block 712. In certain embodiments, the connection response received at block 708 indicates whether registration by the producer system 106 was successful without identifying additional lease agents. In such a case, if registration of the producer system 106 is not successful, the producer system 106 may register another lease agent of the set of lease agents identified at block 702 or with the other lease agent. And, alternatively, blocks 704, 706, 708 and 710 may be repeated until the lease agent 102 confirms registration of the producer system 106.

  In some embodiments, the second lease agent identified at decision block 710 is not randomly selected and / or necessarily associated with the producer system 106. In such cases, block 714 can include performing one or more embodiments with respect to blocks 708 and 710, but with respect to the second lease agent. In other words, a loop can be formed from block 714 to block 708. In such a case, decision block 710 may identify the third lease agent instead of confirming the registration of producer system 106 if the connection response from the second lease agent identifies the third lease agent. This loop may be repeated continuously until the producer system 106 registers with the lease agent 102 without failure. Alternatively, the loop can be executed a threshold number of times. An alert may be generated if the threshold is met without the producer system 106 registering without fail. For example, the administrator may be notified (eg, via email or pop-up alert) that the producer system 106 could not register with the lease agent 102. In some cases, such as an unexpected system failure, the producer system 106 may not be able to register with the set of lease agents 102 or renew the registration with the lease agent. In such cases, consumer system 104 may access connection information or a lease cache to attempt to access producer system 106. Advantageously, in certain embodiments, by using cache information that may be expired, pause times for resource access may be reduced or eliminated in some cases.

Exemplary Producer System Registration Process FIG. 8 illustrates an embodiment of a producer system registration process 800 from the perspective of the lease agent 102. Process 800 may be implemented by any system that can register producer system 106 with lease agent 102. For example, process 800 may be implemented in whole or in part by lease agent 102, registration module 226, and status module 228, to name a few. Any number of systems, all or in part, can perform process 800, but to simplify the discussion, parts of process 800 are described with reference to a particular system. To do.

  Process 800 begins at block 802, for example, registration module 226 receives a registration request from producer system 106. In some embodiments, the registration request can include a certificate or encryption key associated with the producer system 106. Registration module 226 determines at decision block 804 whether producer system 106 is assigned to lease agent 102. Determining whether the producer system 106 is assigned to the lease agent 102 includes accessing the producer repository 220 and / or the agent repository 206 to determine whether the producer system 106 is assigned to the lease agent 102. be able to. Further, in some cases, determining whether the producer system 106 is assigned to the lease agent 102 may be based on a received identifier, certificate, or encryption key associated with the producer system 106, for example. Changing the identification information of 106 may be included.

  If registration module 226 determines that producer system 106 is assigned to lease agent 102, registration module 226 verifies registration of producer system 106 at block 806. Confirming registration of the producer system 106 may include notifying the producer system 106 that the producer system 106 is registered with the lease agent 102. Further, in some cases, block 806 may include updating the producer repository 220 and / or agent repository 206 to indicate that the producer system 106 is available and registered with the lease agent 102. Further, in some embodiments, block 806 provides the producer system 106 with access to a certificate and / or encryption key associated with the lease agent 102 and / or assigned to the producer system 106. Can be included. This certificate and / or encryption key can be used for further communication between the producer system 106 and the lease agent 102. In addition, the certificate and / or encryption key can be used to verify the identity of the producer system 106, or to secure data communicated between the two systems, such as the producer system 106 and the consumer system 104. It can be used for communication with.

  At block 808, current status module 228 receives status information from producer system 106. This state information may include some or all of the embodiments described with respect to the state information in block 712. The status module 228 may update the producer status information of the producer system 106 at block 810 based at least in part on the status information received at block 808. Updating the producer status information may include updating an entry or one or more metrics in the producer repository 220 and / or agent repository 206 to reflect the current status of the producer system 106.

  If registration module 226 determines at decision block 804 that producer system 106 is not assigned to lease agent 102, registration module 226 identifies another lease agent to which producer system 106 is assigned at block 812. To do. At block 814, the registration module 226 can provide the producer system 106 with identification information for the lease agent 102 to which the producer system 106 is assigned, and the producer system 106 has identified the lease agent 102 identified at block 812. To be able to contact. In certain embodiments, block 812 and block 814 may be optional. For example, in some cases, the registration module 226 may not be associated with the producer system 106 and the producer system 106 may be associated with the lease agent 102, so that a registration request received at block 802 may be sent to the producer system 106. Can be informed of the failure without notifying the alternate lease agent 102 to which it is assigned.

Lease Agent Subdivision Process FIG. 9 illustrates an embodiment of the lease agent subdivision process 900. Process 900 may be implemented by any system that can reassign a set of producer systems 106 assigned to lease agent 102. For example, process 900 may be implemented in whole or in part by lease agent 102, split system 222, and split system 204, to name a few. Any number of systems, whether in whole or in part, can implement process 900, but to simplify the discussion, parts of process 900 are referred to a particular system and a particular system. explain.

  Process 900 begins at block 902, for example, the splitting system 222 associated with the first lease agent 102 receives an indication that another, that is, the second lease agent 102 is no longer available. For example, an indication that the second lease agent 102 is no longer available may be determined based on a ping or status check. In other cases, splitting system 222 may determine that lease agent 102 is no longer available when the message is not acknowledged by second lease agent 102. In yet other embodiments, the user may specify that the second lease agent is no longer available. In some examples, process 900 may be performed by partitioning system 204.

  At block 904, the splitting system 222 identifies the producer system 106 assigned to the lease agent 102 that is no longer available. Producer system 106 may be identified by accessing producer repository 220 and / or agent repository 206. At block 906, the split system 222 splits the producer system 106 identified at block 904 among the remaining lease agents 102. In some cases, block 906 may include informing the remaining lease agents 102 that a splitting process is occurring so that multiple lease agents are identified as described above with respect to block 610. Dividing 106 simultaneously is prevented.

  In some embodiments, block 906 may include subdividing all available producer systems 106, not just those assigned to lease agents 102 that are no longer available. In such an embodiment, block 904 may include identifying all available producer systems 106. As described above, the division of the producer system 106 may be overlapping, non-overlapping, equivalent, non-equivalent, and / or based on the type of producer. Accordingly, in some embodiments, block 906 may include some or all of the previous embodiments with respect to block 610. Further, in some cases, the division of the producer system 106 assigned to the second lease agent 102 may be based at least in part on the type of the second lease agent 102. For example, if a second lease agent is assigned a producer system 106 for which 102 is exclusively providing storage services, the producer system 106 assigned to the second lease agent 102 is also exclusively for storage services or resources. Can be subdivided among the subset of lease agents 102 assigned to the producer system 106 that provides

  At block 908, partitioning system 222 updates the remaining lease agents 102 with the identification information of the producer system 106 newly assigned to each of the lease agents 102 that are still available.

  In some embodiments, process 900 may be used to add lease agent 102 or replace lease agent 102. In such a case, at block 904, all available producer systems 106 may be identified for partitioning at block 906. In some cases, the available producer system 106 may be the same producer system 106 that was available in the past period. In other cases, the set of producer systems 106 may have changed due to the loss of the producer system 106 or the addition of the producer system 106. In the case of a one-to-one replacement of the lease agent 102, the new lease agent may be assigned the producer system 106 of the lease agent that it is replacing. In such a case, block 906 may be optional and block 908 may include informing other lease agents that a new lease agent is now assigned the producer system 106 of the lease agent.

Exemplary Hysteresis Base Based Producer Selection Process FIG. 10 illustrates an embodiment of a hysteresis based producer selection process 1000. Process 1000 can be performed by any system that can modify the selection weight associated with producer system 106 to modify the selection of the producer system 106, such as the selection of producer system 106 as part of block 410. . For example, the process 1000 may be implemented in whole or in part by the lease agent 102, the current state module 228, and the lease system 224, to name a few. Any number of systems, whether in whole or in part, can implement process 1000, but to simplify the discussion, parts of process 1000 are referred to a particular system and a particular system. explain.

  Process 1000 begins at block 1002, for example, status module 228 receives status metadata associated with producer system 106 from consumer system 104. This current metadata may include information provided to the consumer system 104 by the producer system 106 as well as information determined by the consumer system 104 based on interactions with the producer system 106. For example, the current metadata includes information related to the response time of the producer system 106, the amount of the consumer system 104 that the producer system 106 corresponds to at a given time, and the consumer system 104 that the producer system 106 corresponds to on average over time. May include amounts and the like. In some embodiments, block 1002 can include some or all of the embodiments described above with respect to block 404.

  Further, in some cases, status module 228 may receive status metadata associated with a set of producer systems 106 with which consumer system 104 has communicated since the last time consumer system 104 communicated with lease agent 102. The current metadata can be received from the consumer system 104 as part of an update request for updated access to the producer system 106. In other cases, the current metadata may be received from the consumer system 104 as part of a new lease request.

  At block 1004, status module 228 updates the producer system 106 one or more producer status information based on the corresponding status metadata received at block 1002. Alternatively or additionally, the status module 228 may determine that at least some of the received status metadata is related to a producer system 106 associated with another leasing system 102, and thus status information has been assigned to the producer system 106. The lease agent 102 may be provided. In some cases, the processes associated with blocks 1002 and 1004 may cause the consumer system 104 to send to the lease agent 102 several producers regardless of whether the lease agent 102 is assigned to each of several producer systems 106. It can act as a kind of “gossip algorithm” in that it provides information about the interaction of the consumer system 104 with each of the systems 106. In other words, a lease agent 102 may obtain a “gossip” for a producer system 106 that is assigned to another lease agent 102. The lease agent 102 can then spread the “gossip” to the lease agent 102 assigned to the producer system 106. Advantageously, in certain embodiments, by using this “gossip algorithm”, the lease agent 102 obtains the current metadata from the producer system 106 between the scheduled current update and the next current update. can do. By obtaining the current metadata from the consumer system 104 as well as the producer system 106, the choice of the producer system 106 for leasing can be further optimized compared to a system that does not use a “gossip algorithm”. A further embodiment of a system and method for obtaining feedback information for selecting a “gossip” or computing system to provide a service is disclosed in US, filed Aug. 20, 2009, entitled “DECENTRALIZED REQUEST ROUTING”. No. 12 / 544,517, which is hereby incorporated by reference in its entirety. In some embodiments, block 1002 can include some or all of the embodiments described above with respect to block 406 and / or block 408.

  At decision block 1006, the current status module 228 determines whether the updated producer current status information indicates a change in load metrics associated with the producer system 106. The load metric can include any characteristic of the producer system 106 selected for monitoring. This load metric can relate to the load that can be handled by the producer system 106. In some cases, the load metric can include any metric related to the health of the producer system. Some non-limiting examples of load metrics can include error rate, memory utilization, count of connections with consumer systems, and the like. If at decision block 1006 the updated producer status information does not indicate a change in load metric, process 1000 returns to block 1002 to wait for new status metadata from consumer system 104.

  In some embodiments, the decision block 1006 may involve determining whether there is a change in value associated with one or more other metrics associated with the producer system 106. For example, the status module 228 may determine whether the updated producer status information indicates a change in response time by the producer system 106 or a change in available resources by the producer system 106. In some cases, decision block 1006 compares the updated load metric measurement result of producer system 106 with the average load metric measurement result of the producer system 106 in the network environment 100 or the producer system assigned to lease agent 102. Can include.

  If the updated producer status information indicates that there is a change in the load metric of the producer system 106, the status module 228 is associated with the producer system 106 based at least in part on the changed load metric measurement at block 1008. Correct the selected weight. Modifying the selection weight can include increasing or decreasing the selection weight based on whether a change in the error rate indicates an increase in the error rate or a decrease in the error rate. In some embodiments, the producer system 106 is not associated with a selection weight. In such embodiments, if the change in load metric or other tracked metric detected at decision block 1006 meets or exceeds a corresponding threshold, current module 228 may malfunction the producer system or not use it. Can be identified as possible. In such a case, a user, such as an administrator, may be alerted if a threshold associated with identifying the producer system 106 that the load metric is no longer available or malfunctioning. Further, in some cases, the user may be warned if the load metric or selection weight changes the threshold regardless of the availability of the producer system 106.

  In certain embodiments, the selection weight associated with the producer system 106 facilitates selecting the producer system 106 available as part of the block 410 associated with the process 400 described above for lease to the consumer system. Can be used for. The current status of selection weights and / or availability of the producer system 106 may be stored in the producer repository 220 and / or the agent repository 206.

Overlay Network Environment Overview FIG. 11 illustrates an embodiment of an overlay network environment 1100 that provides consumer systems with access to services hosted by a producer system. Overlay network environment 1100 can include any type of system that can provide one or more overlay networks or virtual networks to one or more organizations or entities. These overlay networks can be implemented by computing hardware that can form physical or non-virtual networks. Some examples of overlay or virtual networks that can be used with this disclosure are described in US patent application Ser. No. 12 / 827,268 filed Jun. 30, 2010 (currently US Pat. No. 8,296,459). The entirety of this patent is hereby incorporated by reference.

  Overlay network environment 1100 includes lease agent 102, consumer host 1104, and producer host 1106, each of which can communicate with each other over network 202. Each lease agent 102 may include some or all of the subsystems illustrated and described with respect to FIG. Thus, for example, the lease agent 102 may include a producer repository 220, a split system 222, a lease system 224, a registration module 226, and a status module 228. Each of these subsystems of lease agent 102 may include the same functionality as described above with respect to FIG. 2, but in some cases, these subsystems may have been modified or include additional capabilities. . For example, in addition to or instead of receiving current status information related to the consumer system 104 and the producer system 106, the current status module 228 includes the consumer host 1104, the producer host 1106, the consumer virtual machine 1142, and the producer virtual machine 1162. Current status information related to one or more of them can be received. Similarly, producer repository 220 may include information related to one or more of consumer host 1104, producer host 1106, consumer virtual machine 1142, and producer virtual machine 1162.

  In some cases, the splitting system 222 can be used to split the producer virtual machine 1162 among the lease agents 102 of the overlay network environment 1100. Further, a producer virtual machine 1162 associated with a particular overlay network can be partitioned independently of producer virtual machines 1162 associated with other overlay networks. Thus, for example, the producer virtual machine B ′ can be split to the lease agent 102 independently of the producer virtual machine B ″. In some cases, a subset of available lease agents 102 may be associated with a particular overlay network. In such cases, the producer virtual machine 1162 and consumer virtual machine 1142 associated with a particular overlay network may limit communication to a subset of available lease agents 102.

  Further, the leasing system 224 may select the producer virtual machine 1162 to lease to the consumer virtual machine 1142 based on the overlay network with which the producer virtual machine 1162 and the consumer virtual machine 1142 are associated. In some cases, selecting the producer virtual machine 1162 based on the overlay network may be added to the elements described above with respect to selecting the producer system 106 to be minimized to the consumer system 104. Further, the registration module 226 can be used to register the producer virtual machine 1162 with the lease agent 102.

  Although only a single consumer host 1104 is illustrated in FIG. 11, an overlay network environment may include multiple consumer hosts 1104. Each consumer host 1104 may include a number of consumer virtual machines 1142. Some of the consumer virtual machines 1142 may be associated with a different overlay network than other consumer virtual machines 1142 hosted by the consumer host 1104. For example, consumer host 1104 includes two consumer virtual machines 1142, each associated with a different overlay network. Consumer virtual machine A ′ may be associated with a first overlay network that may also include a producer virtual machine B ′, and consumer virtual machine A ″ may be associated with a second overlay network that may also include a producer virtual machine B ″. obtain.

  In addition to the consumer virtual machine 1142, the consumer host 1104 can include an overlay network proxy 1114, a lease requester 1130, a virtual machine mapping repository 1150, and a current state module 1132. The overlay network proxy 1114 can process any service request from the consumer virtual machine 1142 and can provide any service request for processing to the producer host 1106 hosting the producer virtual machine 1162. Can be included. In some embodiments, a service request received from a consumer virtual machine 1142 includes a virtual address associated with a producer virtual machine 1162 or a non-existent system that the consumer virtual machine 1142 believes can service the service request. obtain. Upon receiving a service request with a virtual address, overlay network proxy 1114 can identify a producer virtual machine 1162 that processes the service request in the same overlay network as the consumer virtual machine 1142 that provided the service request. The overlay network proxy 1114 can then replace the virtual address with the address of the identified producer virtual machine 1162. As described in more detail below, producer virtual machine 1162 may be identified from a pool of leased producer virtual machines 1162 associated with the consumer virtual machine 1142 that provided the service request. Further, the overlay network proxy 1114 can identify the producer host 1106 hosting the identified producer virtual machine 1162 and wrap or encapsulate the service request with a header or outer header that identifies the consumer host 1104.

  Virtual machine mapping repository 1150 may store a pool of producer virtual machines 1162 that are leased for consumer virtual machines 1142. Further, the virtual machine mapping repository 1150 can store identification information of the corresponding producer host 1106 that hosts the producer virtual machine 1162. Storing the identification information of the producer virtual machine 1162 and the producer host 1106 can include storing addressing information for accessing the producer virtual machine 1162 and the producer host 1106.

  To obtain a lease for the consumer virtual machine 1142, the consumer host 1104 can include a lease requester 1118 that can generate a lease request for the consumer virtual machine 1142 hosted by the consumer host 1104. The lease requester 1118 can identify a particular overlay network and / or a particular consumer virtual machine 1142 from which a producer virtual machine 1162 is being leased.

  The current state module 1132 may include some or all of the above-described embodiments with respect to the current state module 242. Further, the current status module 1132 can provide current status information for the producer virtual machine 1162 and / or the producer host 1106 based on communication with the producer virtual machine 1162 and the producer host 1106.

  As with the consumer host 1104, the overlay network environment 1100 may include any number of producer hosts 1106 that can each include one or more producer virtual machines 1162 associated with one or more overlay networks. it can. In addition, each producer host 1106 can include an overlay network proxy 1116, a virtual machine mapping repository 1152, and a status module 1134.

  Similar to overlay network proxy 1114, overlay network proxy 1116 may include any system that processes service requests received from consumer host 1104 and processes responses to received service requests. Upon receiving the service request, the overlay network proxy 1116 can determine the producer virtual machine 1162 that processes the service request based on information included in the header of the service request. Further, in some cases, the service request may identify a particular overlay network that may be used to facilitate identifying the producer virtual machine 1162 to process the service request.

  The virtual machine mapping repository 1152 can store information identifying which producer virtual machine 1162 is associated with which overlay network. Further, the virtual machine mapping repository 1152 can store information that facilitates identifying which consumer host 1104 is hosting a particular consumer virtual machine 1142. This information can be used to determine the consumer host 1104 that provides the response to the service request.

  As with the current module 1132, the current module 1134 can include one or more of the previous embodiments with respect to the current module 262. Further, the current status module 1134 can provide current status information related to the producer virtual machine 1162 to the lease agent 102.

  As indicated by the dashed lines of the consumer host 1104 and the producer host 1106, the underlying system that enables the process disclosed herein is one of a consumer (eg, a client) and a producer (eg, a server or service provider). It can be separated from the virtual machine forming the above overlay network. In some cases, underlying systems (eg, overlay network proxies 1114 and 1116) may be implemented as part of the networking infrastructure of consumer host 1104 and producer host 1106. Advantageously, in certain embodiments, by separating the underlying system from the virtual machine, the lease structure can be implemented, maintained, and modified without affecting the overlay network.

  In some embodiments, the consumer host 104 can host both a consumer virtual machine 1142 and a producer virtual machine 1162. Further, in some cases, the producer host 1106 can host both a consumer virtual machine 1142 and a producer virtual machine 1162. Furthermore, although the consumer virtual machine 1142 and the producer virtual machine 1162 have been described as virtual machines, they are not limited to such. In some embodiments, the overlay network may be part of the consumer host 1104 and producer host 1106, or may be allocated hardware and / or software resources executed by the consumer host 1104 and producer host 1106. . These resources can be used placed within the virtual machine to run producer and consumer systems as part of the overlay network.

  In some cases, one or more of the processes described above with respect to network environment 100 may be performed with respect to overlay network environment 1100 or modified to be performed. Thus, for example, process 900 can be performed to subdivide lease agents in overlay network environment 1100. As a second example, processes 700 and 800 may be performed to register producer virtual machine 1162 with lease agent 102 in overlay network environment 1100.

Exemplary Process for Accessing Producer Virtual Machine Services FIG. 12 illustrates an embodiment of a process 1200 for accessing services on a producer virtual machine. Process 1200 may be performed by any system capable of processing requests from consumer virtual machines that access services provided by the producer virtual machine. For example, process 1200 may be implemented in whole or in part by consumer host 1104, lease agent 102, overlay network proxy 1114, and lease requester 1118, to name a few. Any number of systems, whether in whole or in part, can implement process 1200, but to simplify the discussion, parts of process 1200 are referred to a particular system and a particular system. explain.

  In some cases, process 1200 may be used to allow a consumer virtual machine to access services provided by a producer system. Similarly, in some embodiments, process 1200 may be used to allow a consumer system to access services provided by a producer virtual machine. However, to simplify the discussion, the process 1200 will be described with respect to a consumer virtual machine attempting to access a producer virtual machine service.

  The process 1200 begins at block 1202, for example, the overlay network proxy 1114 of the consumer host 1104 (eg, consumer host A) requests a request to access the service at the producer consumer 1142 (eg, consumer virtual machine A ′). ) Alternatively or additionally, the request received at block 1202 may be a data packet provided to the producer. For example, a data packet may be data that is used in connection with a service or that facilitates the use of a service with a producer to which a consumer virtual machine has already established access. In some embodiments, the request may include a packet having a header indicating that the request or packet is addressed from address A associated with consumer virtual machine 1142 to virtual address X. For example, the received packet may be as follows: {A ′, X, data} indicating that data is being sent from Α ′ to X. The data field of the packet may include the request and / or data that facilitates performing the request or action at the producer virtual machine 1162. In certain embodiments, consumer virtual machine 1142 may not be aware that address X is a virtual address, but instead may consider address X to refer to a physical producer system. Further, as described above, in some embodiments, the overlay network may include consumer systems other than or in addition to consumer virtual machines. In such an embodiment, block 1202 may include receiving from a consumer system a request to access a service at a producer implemented on or hosted by consumer host 1104. . Similarly, a producer host may include a producer system other than or in addition to a producer virtual machine that may be configured to provide services to a consumer system.

  At decision block 1204, overlay network proxy 1114 determines whether there is an unused producer virtual machine lease associated with consumer virtual machine 1142. Determining whether there is an unused producer virtual machine lease associated with the consumer virtual machine 1142 includes accessing the virtual machine mapping repository 1150 to determine whether there is a lease pool associated with the consumer virtual machine 1142. obtain. Further, in some cases, decision block 1204 may include determining whether the lease pool includes an unused lease for the producer virtual machine associated with consumer virtual machine 1142.

  If the overlay network proxy 1114 determines at decision block 1204 that there is no unused producer virtual machine release associated with the consumer virtual machine 1142, the lease requester 1130 accesses the producer virtual machine at block 1206. Acquire multiple leases. An example of a process for obtaining one or more leases to access one or more producer virtual machines is described in further detail below with respect to FIG.

  At block 1208, overlay network proxy 1114 attempts to establish a connection with the leased producer virtual machine 1162 obtained at block 1206. In some cases, block 1208 may include storing lease information associated with each leased producer virtual machine with which the overlay network proxy 1114 establishes a connection without failure.

  An unused producer virtual machine release associated with the consumer virtual machine 1142 after the overlay network proxy 1114 establishes a connection with the leased producer virtual machine at block 1208 or the overlay network proxy 1114 determines at decision block 1204 If it is determined that there is, process 1200 proceeds to block 1210. At block 1210, overlay network proxy 1114 selects a leased producer virtual machine 1162 that accesses the service requested by consumer virtual machine 1142. Producer virtual machine 1162 may be selected using any type of selection algorithm, such as round robin or minimum time unreferenced. In other cases, the producer virtual machine 1162 may be selected based on the order in which connections were established with the producer virtual machine 1162. In yet other cases, the producer virtual machine 1162 may be selected randomly and / or based on that block 1202 received service request. Alternatively, in some cases, overlay network proxy 1114 may facilitate accessing virtual machine mapping repository 1150 to select producer virtual machine 1142. For example, the overlay network proxy 1114 may access the lease pool, which may be stored as a table identifying the available producer virtual machines 1162 stored in the virtual machine mapping repository 1150.

  In some cases, overlay network proxy 1114 may select a leased producer virtual machine 1162 that has a load below a threshold. In such a case, the overlay network proxy 1114 may select a virtual machine 1162 having a load that is randomly below the threshold from the producer. This load may refer to any measurable metric related to utilization of the producer virtual machine 1162. For example, the load may refer to processor load, network connection load, some consumer connection with the producer virtual machine 1162, minimum latency in connection, a measure of the performance of the producer virtual machine 1162, and so on.

  Further, in some cases, each lease may be associated with an expense. For example, a consumer or an entity associated with a consumer may be charged for usage in seconds, for communications in mega or bytes of processed data, or for producer virtual machine 1162 in compute cycle time. In such a case, overlay network proxy 1114 may select leased producer virtual machine 1162 based on the cost of available leased producer virtual machine 1162.

  At block 1212, overlay network proxy 1114 selects the address of the leased producer virtual machine 1162 selected at block 1210 with the producer's address (eg, virtual address X) included in the request header (eg, inner header). And replace. Thus, for example, the packet received at block 1202 can now be as follows: {A ', B', data}. In some embodiments, block 1212 may be optional. For example, in some embodiments, each leased producer virtual machine 1162 may be associated with a port. Thus, instead of replacing virtual address X with the address of leased producer virtual machine 1162, the packet can be communicated to the hosting producer via the port associated with leased producer virtual machine 1162. As a second example, the packet may be communicated to a producer host, which may determine a leased producer virtual machine 1162 that receives the packet based on virtual address X, for example.

  At block 1214, the overlay network proxy 1114 identifies the producer host 1106 associated with the leased producer virtual machine. The producer host 1106 can be identified by accessing a state table stored in the virtual machine mapping repository 1150.

  Overlay network proxy 1114 encapsulates the request at block 1216 with an outer header identifying the producer host 1106 and consumer host 1104 associated with consumer virtual machine 1142 identified at block 1214. Thus, for example, the packet is now as follows: {A, B {A ′, B ′, data}}, which is the packet being sent from consumer host A to producer host B It shows that. Alternatively, in some cases, identification information of the producer host 1106 and consumer host 1104 can be included with the request received at block 1202 or can be added to the request header of the request, and the packet is as follows: , Ie, {A, B, A ′, B ′, data}, which indicates that a packet is being sent from consumer host A to producer host B. In such a case, after the process associated with block 1216 is complete, the request includes a single header instead of two headers including an inner header and an outer header. In some embodiments, block 1216 may include identification information for the overlay network associated with the consumer virtual machine 1142 that provided the request at block 1202 and the producer virtual machine 1162 identified at block 1210. Thus, for example, the packet indicates that the request is related to the first overlay network, i.e., not the second overlay network, as follows: {A, B , ', A', B ', data}, where a packet is being sent from consumer host A to producer host B, and the service request is included in the overlay network from the consumer virtual machine. Producer to show virtual machine. Advantageously, in some embodiments, the address can be reused between different overlay networks by including the overlay network identification along with the service request and response to the service request. However, in the case where each virtual machine and each system is associated with a unique address, it may be optional to provide overlay network identification information.

  In some embodiments, the overlay network proxy 1114 can determine address information for accessing the producer virtual machine from a state management table stored in the virtual machine mapping repository 1150. This state management table may include connection information for accessing the leased producer virtual machine 1162 selected at block 1210. In addition, the state management table may include a mapping of virtual addresses to producer virtual machine addresses. In addition, the state management table may include a mapping of the producer virtual machine 1162 to the respective producer host. An example of such a state management table that maps virtual addresses to producer virtual machines is illustrated in FIG.

  At block 1218, overlay network proxy 1114 provides the request to the producer host identified at block 1214. This request may be provided to producer host 1106 via network 202.

Exemplary Process for Processing Requests to Access Services on a Producer Virtual Machine FIG. 13 illustrates an embodiment of a process 1300 for processing requests to access services on a producer virtual machine. Process 1300 may be implemented by any system that can process a request received from a consumer host to access a service on a producer virtual machine. For example, process 1300 may be implemented in whole or in part by producer host 1106, overlay network proxy 1116, and producer virtual machine 1162, to name a few. Any number of systems, whether in whole or in part, can implement process 1300, but to simplify what is discussed, parts of process 1300 are referred to specific systems and specific systems. explain.

  In some cases, process 1300 may be used to allow a producer virtual machine to provide a service requested by a consumer system. Similarly, in some embodiments, process 1300 may be used to allow a producer system to provide a service requested by a consumer virtual machine. However, to simplify the discussion, the process 1300 will be described with respect to a producer virtual machine that provides access to the service requested by the consumer virtual machine.

  Process 1300 begins at block 1302, for example, overlay network proxy 1116 of producer host 1106 (eg, producer host B) receives a request from consumer host 1104. The request can be formalized, for example, as follows: {A, B, ', A', B ', data}, where a packet is received from consumer host A and the producer host Target B and indicate that the service request is from the consumer virtual machine to the producer virtual machine contained within the overlay network. In many cases, the received request is a request to access a service hosted by producer virtual machine 1162 mailed by producer host 1106. However, in some cases, the received request may instead provide data to producer virtual machine 1162 that facilitates access to services already established by consumer virtual machine 1142 hosted by consumer host 1104. It may be a data packet configured to provide.

  At block 1304, the overlay network proxy 1116 determines a producer virtual machine 1162 (eg, producer virtual machine B ') that receives the request. In some embodiments, block 1304 may include deencapsulating the outer header from the request received at block 1302. In such a case, the packet may be as follows: {A ′, B ′, data}, because the packet has been received from consumer virtual machine A ′, and producer virtual machine B ′. Indicates that it is targeted. In such cases, the overlay network proxy 1116 may access the inner header to identify the producer virtual machine 1162. Alternatively or additionally, the overlay network proxy 1116 may identify the producer virtual machine 1162 that receives the request by accessing the outer header.

  In some cases, overlay network proxy 1116 provides the request without the outer header to producer virtual machine 1162 identified at block 1304. Thus, the packet can be as follows: {A ', B', data}. However, in other cases, the request may be provided as received from the consumer host 1104, including with an outer header if included with the received request. Thus, the packet may be as received at block 1302 (eg, {A, B, ', A', B ', data}).

  At block 1308, overlay network proxy 1116 receives from producer virtual machine 1162 a response addressed to consumer virtual machine 1142 that caused the request received at block 1302 to be generated. In some embodiments, the response may be addressed to a different consumer virtual machine. For example, a request from a consumer virtual machine can be a request to transfer a file from a producer virtual machine to another consumer virtual machine. This packet may be similar to the packet received at block 1202 and may be as follows: {B ′, A ′, data}, where producer virtual machine B ′ has data ( For example, it indicates that a response to the service request is being sent to the consumer virtual machine A ′. At block 1310, overlay network proxy 1116 identifies the consumer host 1104 associated with consumer virtual machine 1142. The consumer host 1104 can be identified by accessing the mapping table at the virtual machine mapping repository 1152. This mapping table may map the consumer virtual machine 1142 to the consumer host 1104 that hosts the consumer virtual machine 1142. Each consumer host 1104 may typically host multiple consumer virtual machines 1142. However, in some cases, one or more consumer hosts 1104 may host a single consumer virtual machine 1142.

  Overlay network proxy 1116 encapsulates the response with an outer header that identifies producer host 1106 associated with consumer host 1104 and producer virtual machine 1162 at block 1312. Thus, the packet may be as follows: {B, A {Β ', A', data}}. As described with respect to block 1216, in some cases, identification information of the consumer host 1104 and producer host 1106 may be included with or added to the existing header of the response received at block 1308. Thus, the packet may be as follows: {B, A, B ', A', data}. Similarly, as described with respect to block 1216, the outer header, or the header of the response if only one header is present, includes the overlay network identification information associated with the producer virtual machine 1162 and consumer virtual machine 1142. obtain. Thus, the packet may be as follows: {B, A, ', B', A ', data}.

  Producer host 1106 provides a response to consumer host 1104 at block 1314. In some embodiments, producer host 1106 may provide a response over network 202.

  In some embodiments, the consumer host 1104 may execute a process 1300 or similar process to provide the response received at block 1308 to the corresponding consumer virtual machine 1142. Further, in some cases, the overlay network proxy 1114 of the consumer host 1104 may identify the virtual address (eg, virtual address X) that was used to create the initial request provided by the consumer virtual machine 1142. Using this identified virtual address, overlay network proxy 1114 was used to create the initial request provided by consumer virtual machine 1142 with the address in the received response identifying producer virtual machine 1162. Can be replaced with a virtual address. Thus, for example, before the packet is provided to the consumer virtual machine A ′, the packet can be reconstructed as follows: {X, A ′, data}, which means that the response is in the packet Indicates that it was received from system X rather than from producer virtual machine B ′ that may have actually generated the included data.

Exemplary Process for Leasing Access to a Producer Virtual Machine FIG. 14 illustrates an embodiment of a process 1400 for leasing access to a producer virtual machine. Process 1400 may be implemented by any system that can obtain a lease to access producer virtual machine 1162 (eg, producer virtual machine B ′). For example, process 1400 may be performed in whole or in part by consumer host 1104 lease requester 1130, lease agent 102, overlay network proxy 1114, and lease system 224, to name a few. Any number of systems, whether in whole or in part, can implement process 1400, but to simplify the discussion, parts of process 1400 are referred to a particular system and a particular system. explain.

  Process 1400 begins at block 1402, for example, lease requester 1130 generates a request to obtain a lease to producer virtual machine 1162 for consumer virtual machine 1142 associated with the overlay network. The process associated with block 1402 may occur when the consumer virtual machine 1142 is initialized. Alternatively or additionally, block 1402 occurs in response to determining that there is no unused producer virtual machine lease associated with consumer virtual machine 1142 (eg, as determined at decision block 1204 associated with process 1200). obtain.

  At block 1404, the lease requester 1130 provides the request to the plurality of lease agents 102. In some embodiments, the plurality of lease agents 102 may include a subset of lease agents 102 included within the overlay network environment 1100. Further, in some cases, the request may be provided to a single lease agent 102.

  At block 1406, the lease requester 1130 receives from each of the plurality of lease agents 102 identification information for the producer virtual machine 1162 associated with the same overlay network as the consumer virtual machine 1142 for which the request was generated at block 1402. Typically, each of the plurality of lease agents 102 provides identification information for a single producer virtual machine 1162. However, in some cases, one or more of the lease agents 102 may provide identification information for multiple producer virtual machines 1162. Further, the lease agent 102 can provide identification information for the zero producer virtual machine 1162. For example, if each producer virtual machine 1162 associated with a particular lease agent 102 is utilized beyond a threshold utilization rate, the lease agent 102 may not provide producer virtual machine 1162 identification information. In such a case, the lease agent 102 may alert a user, such as an administrator, that each producer virtual machine 1162 associated with the lease agent 102 will be used beyond a threshold utilization.

  In some embodiments, in addition to receiving identification information for the producer virtual machine 1162, lease information associated with leasing the producer virtual machine 1162 may be received at block 1406. This lease information includes the address to access the producer virtual machine 1162, the identification information and / or address of the producer host 1106 that hosts the producer virtual machine 1162, and / or the consumer virtual machine 1142 for lease of the producer virtual machine 1162. Consumable resource identification information regarding the amount of allocated consumable resources may be included. This consumable resource may include any type of resource that measures the lease period of the producer virtual machine 1162. For example, the consumable resource can be a duration, some operation, the amount of data processed by and / or received from producer virtual machine 1162, or use of producer virtual machine 1162 by consumer virtual machine 1142. Any other metric that measures can be included.

  At block 1408, overlay network proxy 1114 attempts to access each of the producer virtual machines 1162 identified at block 1406 for consumer virtual machines 1142. In some embodiments, block 1408 can include attempting to establish a connection with each of the producer virtual machines 1162. In other embodiments, block 1408 can include attempting to communicate with the established connection with producer virtual machine 1162. At block 1410, the overlay network proxy 1114 stores connection information relating to each established connection in a lease pool. This connection information may include information identifying the connection and how to use the connection to access the service. For example, the connection information may include any of the information received as part of block 1406, such as the consumable resource identification information for the identification information of the producer host 1106 that hosts the producer virtual machine 1162. In some embodiments, lease pool and / or connection information may be stored in the virtual machine mapping repository 1150.

  Similar to process 300, in some embodiments, process 1400 may be used to renew the producer virtual machine 1162 lease. In such an embodiment, block 1402 may include generating a request to renew an existing or previously existing lease of the producer virtual machine. The renewal request may include identification information of an existing producer virtual machine lease. Further, block 1406 includes receiving an indication of whether the update request has been granted and, in some cases, lease information (eg, lease time or processor usage) related to further grants of consumable resources. obtain.

Example State Management Table FIG. 15 illustrates one non-limiting example of a state management table 1500 that can be used to facilitate communication in the overlay network environment 1100. The state management table 1500 can include some information that facilitates communication between the consumer virtual machine 1142 and the producer virtual machine 1162. For example, the state management table 1500 may include columns of a source overlay address 1502, a source overlay port 1504, a virtual address 1506, and a destination overlay address 1508. As indicated by some of the table headings (eg, source overlay address 1502) in state management table 1500, the address may be an Internet Protocol (IP) address. However, the address is not limited as such and may take other forms or follow other protocols.

  In the example of FIG. 15, the illustrated portion of the state management table 1500 is associated with the consumer virtual machine A '. As shown in the virtual address 1506 column, the consumer virtual machine A 'may use multiple virtual addresses X and Y. Further, each virtual address may be associated with a plurality of destination overlay addresses associated with a plurality of producer virtual machines. For example, virtual address Y may be associated with a producer virtual machine having address K 'and a producer virtual machine having address M'. Since multiple destination addresses may be mapped to virtual addresses, overlay network proxy 1114 may also identify the port that directs the data packet to the correct destination, as shown in the source overlay port 1504 column. Therefore, to send a service request to the producer virtual machine K ', the overlay network proxy 1114 will use port P1 replacing the virtual address Y with the address of K'. Similarly, to send a service request to producer virtual machine M ', overlay network proxy 1114 will use port P2 replacing virtual address Y with the address of M'.

  In many cases, the overlay network may be implemented using Layer 3 and / or Layer 4 of the Open Systems Interconnection (OSI) model. Typically, for overlay networks implemented using Layer 3 and / or Layer 4, the networking infrastructure is unaware of applications communicating across the network. This can make load balancing more difficult because it is more difficult to speculatively predict how much data will be sent between the consumer virtual machine and the producer virtual machine. .

  One solution is to create a load balancing system that at least partially recognizes protocols implemented using Layer 7 of the OSI model. In such a system, the overlay network proxy 1114, in some embodiments, examines the packets being sent by the consumer virtual machine 1142 to determine the type of service or service request that the consumer virtual machine 1142 is trying to access. And the type of protocol associated with the service request and whether the service request is for a single service or multiple services of the same or different types. Thus, for example, the overlay network proxy 1114 determines that the consumer virtual machine is requesting access to a website using HTTP requests, and each HTTP request is for a different web page or a different feature of a web page. If so, the overlay network proxy 1114 can send different requests to different producer virtual machines 1162 for processing without the consumer virtual machine 1142 being aware that the request is being processed by a different system. Thus, in some cases, a single connection can be demultiplexed with a set of connections. Overlay network proxy 1114 may divide a series of requests into multiple producer virtual machines 1162 to increase the efficiency or speed at which the requests are processed. Further, if the overlay network proxy 1114 determines that the consumer virtual machine 1142 is generating a lot of load on the producer virtual machine 1162, the overlay network proxy 1114 is responsible for the producer virtual processing request and / or split request. Machine 1162 can be exchanged between multiple producer virtual machines 1162. Replacing the producer virtual machine 1162 can be accomplished in some cases by associating a request identifier with a service request. For example, as illustrated in the request identifier 1510 column of FIG. 15, the packet having the request identifier I1 may have a virtual address X that is exchanged with the address of the producer virtual machine B '. Similarly, a packet with a request identifier 12 can have a virtual address X that is exchanged with the address of the producer virtual machine D '.

Embodiments of the present disclosure can be described in the light of the following clauses.
Article 1
A method of leasing access to a producer system and leasing access to a service hosted by the producer system,
By a consumer system containing one or more processors
Generating a lease request to access one service of multiple producer systems;
Providing a lease request to multiple lease agents;
Receiving one or more identification information of a producer system from an individual lease agent;
Attempting to initiate a connection with at least some of the producer systems identified by multiple lease agents;
Accessing a service provided by the first producer system in response to establishing without failure the connection of the producer system with at least some of the first producer systems.
Article 2
Receiving one or more identification information of a producer system from an individual lease agent includes receiving identification information of a different producer system from at least two lease agents of the plurality of lease agents. the method of.
Article 3
The method of clause 1-2, wherein at least some of the individual lease agents of the plurality of lease agents are associated with a non-equivalent set of producer systems.
Article 4
Receiving one or more identification information of a producer system from an individual lease agent includes receiving at least some consumable resources of the identified producer system. the method of.
Article 5
Consumable resources can include lease times, a set of calculation cycles, financial budgets associated with the use of identified producer systems or disk storage, and lease times can be consumed by a consumer system to service a producer system. 5. The method of clause 4, comprising a certain period of time permitted to access.
Article 6
In response to the amount of consumable resources remaining from the consumable resources of the first producer system that meet the lease threshold, the method includes:
Determining the probability that an existing service request to access a service at the first producer will not be completed before the consumable resource expires;
In response to determining that the probability satisfies the renewal threshold, generating an renewal lease request to access a service at the first producer system;
6. The method of clause 5, further comprising providing the renewed lease request to a plurality of lease agents that provided the identification information of the first producer system.
Article 7
7. The method of clause 6, wherein in response to providing the renewal lease request to the lease agent, the method further comprises receiving an update amount of the consumable resource of the first producer system.
Article 8
In response to providing the renewal lease request to the lease agent, the method further includes receiving a new amount of consumable resources of the new producer system, the new producer system being different from the first producer system. The method according to clause 6 to clause 7.
Article 9
Responsive to establishing without failure the connection of the producer system with at least some of the first producer systems, the method further comprises obtaining metadata from the first producer system, 9. The method of clauses 1-8, wherein at least a portion of the includes current status information relating to the first producer system.
Article 10
10. The method of clause 9, further comprising providing at least a portion of the metadata to a lease agent of a plurality of lease agents that provided identification information for the first producer system.
Article 11
The method of clauses 9-10, further comprising providing at least a portion of the metadata to a plurality of lease agents;
Article 12
Clause 1 to Clause 11 accessing a second service in the second producer system in response to establishing without failure a connection with at least some second producer system of the producer systems. The method described in 1.
Article 13
13. The method of clause 12, wherein the service and the second service are the same service.
Article 14
14. The method of clauses 12-13, wherein data accessed using the service and data accessed using the second service are different.
Article 15
A system that leases access to a producer system to obtain access to a service hosted by the producer system,
Consumer system that includes one or more processors
The consumer system includes
Generate a lease request to access the producer system service,
Providing lease requests to multiple lease agents;
A lease requester configured to receive the producer system identification information from at least some of the plurality of lease agents;
The consumer system further includes a connection module configured to attempt to initiate a connection with at least some of the producer systems identified by the plurality of lease agents,
The consumer system is configured to access services on at least some of the first producer systems in response to the connection module establishing without failure the connection with the first producer system. The system further comprising a resource requestor.
Article 16
The lease requester is further configured to receive a lease time for at least some of the identified producer systems, the lease time being a period of time that the consumer system is allowed to access services at the producer system. 16. The system of clause 15, comprising:
Article 17
The system of clause 16, wherein the connection module is further configured to provide a lease time associated with the first producer system to the first producer system.
Article 18
The resource requester also has an existing service request to access the service at the first producer before the lease time expires in response to the amount of time remaining from the lease time for the first producer system that meets the lease threshold. Configured to determine the probability of not being completed,
Lease Requester
In response to determining that the probability satisfies the renewal threshold, generate an renewal lease request to access the service at the first producer system;
18. The system of clauses 16-17, wherein the system is configured to provide a lease request to a lease agent of a plurality of lease agents that provided identification information for the first producer system.
Article 19
Obtaining metadata from the first producer system, including at least a portion of current information relating to the first producer system;
19. The system of clauses 15-18, further comprising a current status module configured to provide at least a portion of the current status information to lease agents of a plurality of lease agents that provided identification information of the first producer system.
Article 20
A system that leases access to a producer system to obtain access to a service hosted by the producer system,
A first lease agent comprising a first lease system implemented in a computer system comprising computer hardware;
The first leasing system includes
Receiving a first request from a consumer system that leases access to a service provided by some producer system;
A first plurality of producer systems configured to identify a first producer system of the first plurality of producer systems based at least in part on producer status information associated with individual producer systems of the first plurality of producer systems; The producer system includes a first subset of several producer systems,
Responsive to identifying the first producer system, configured to provide identification information of the first producer system to the consumer system;
This system further
:
A second leasing agent including a second leasing system;
Including
The second lease agent
Receiving a second request from the consumer system to lease access to the service;
A second plurality of producer systems configured to identify a second producer system of the second plurality of producer systems based at least in part on producer status information associated with individual producer systems of the second plurality of producer systems; The producer system includes a second subset of some producer systems, and the second subset of some producer systems is not the same as the first subset of some producer systems
The second lease agent
Responsive to identifying the second producer system, providing identification information of the second producer system to the consumer system so that the consumer system is at least from the first producer system and the second producer system. Configured to allow requesting access to a service, the producer system identification is at least a distributed process distributed between the first lease agent and the second lease agent. ,system.
Article 21
The first leasing system is further configured to provide a first lease time to the consumer system, the first lease time being a period of time that the consumer system is allowed to access the first producer system. And the second lease system is further configured to provide a second lease time to the consumer system, the second lease time being allowed for the consumer system to access the second producer system. 21. The system of clause 20, including a certain period of time.
Article 22
The first lease agent further includes a first current module, wherein the first current module is:
Receiving the first updated status information of the first producer system;
Configured to update the producer status information of the first producer system based at least in part on the first updated status information;
The second lease agent further includes a second current status module, wherein the second current status module includes:
Receiving second updated status information of the second producer system;
22. The system of clauses 20-21, configured to update the producer status information of the second producer system based at least in part on the second updated status information.
Article 23
23. The system of clause 22, wherein the first updated current status information and the second updated current status information are received from a consumer system.
Article 24
23. The system of clause 22, wherein the first updated current status information is received from the first producer system and the second updated current status information is received from the second producer system.
Article 25
The first lease agent is
Receiving a first lease renewal request from the consumer system to obtain further lease time of the first producer system;
Determining whether to accept the first lease renewal request based at least in part on the producer status information of the first producer system;
In clauses 20-24, further configured to provide a first lease renewal time of the first producer system to the consumer system in response to determining to accept the first lease renewal request The described system.
Article 26
In response to determining not to accept the first lease renewal request, the first lease agent
Identifying a third producer system of the first plurality of producer systems based at least in part on producer status information associated with each producer system of the first plurality of producer systems;
26. The system of clause 25, further configured to provide identification information of the third producer system to the consumer system in response to identifying the third producer system.
Article 27
A method of dividing a producer system among a plurality of lease agent systems,
Determining a first set of producer systems that are available in a first time period by a first lease agent system that includes one or more processors;
Identifying a second set of producer systems that are available in a second period that occurs before the first period;
Calculating the number difference between the first set of producer systems and the second set of producer systems;
Determining whether the difference meets a threshold;
In response to determining that the difference meets the threshold,
Partitioning the first set of producer systems among a plurality of lease agent systems by assigning different subsets of the first set of producer systems to individual lease agent systems;
For individual lease agent systems of a plurality of lease agent systems other than the first lease agent system, the producer system to allow a producer system different from the first set of producer systems to provide services to different consumer systems Providing each lease agent system with identification information of a subset of the producer systems assigned to the lease agent system from the first set of
And thereby
The division of the first set of producer systems among a plurality of lease agent systems is adapted to allow distribution of the allocation of services provided by the first set of producer systems among different consumer systems. Method.
Article 28
Informing a set of lease agent systems to a set of lease agent systems that the first lease agent system is dividing the first set of producer systems, 28. The method of clause 27, further comprising refraining from attempting to split the first set of producer systems while the agent system splits the first set of producer systems.
Article 29
Clause 27, wherein the second set of available producer systems and the second period includes a value that ensures that the difference meets a threshold when the first lease agent system is activated after a period of inactivity. -Method according to clause 28.
Article 30
The first set of producer systems includes the total number of producer systems that are available in the first period, and the second set of producer systems is the total number of producer systems that are available in the second period. 30. A method according to clause 27 to clause 29, comprising:
Article 31
At least one of the plurality of lease agent systems receives an indication that it is not available in the third period;
Identifying a third set of producer systems that are available in a third period;
Identifying a set of lease agent systems available in the third period;
Splitting a third set of producer systems between a set of lease agent systems available in a third period;
Providing the lease agent system with identification information of a subset of the third set of producer systems of the producer system for the individual lease agent systems of the set of lease agent systems that are available in the third time period. 31. The method of clauses 27-30, wherein the subset of producer systems is determined based at least in part on the above division of the second set of producer systems.
Article 32
32. The method of clause 31, wherein the third set of producer systems and the first set of producer systems are the same system.
Article 33
Dividing the first set of producer systems that are available in the first time period among the plurality of lease agent systems includes dividing the first set of producer systems into non-overlapping subsets of the producer systems. A method according to clause 27 to clause 32, comprising:
Article 34
Determining that the producer systems of the first subset of producer systems assigned to the first lease agent system are no longer available;
Updating a count of available producer systems to reflect that the producer system is no longer available, and determining a first set of producer systems that are available in the first time period 34. The method of clause 27 to clause 33, based at least in part on a count of available producer systems.
Article 35
35. The method of clause 34, wherein determining that the producer system is no longer available includes receiving a notification from the consumer system that the producer system is unresponsive.
Article 36
36. The method of clauses 34-35, wherein determining that the producer system is no longer available includes determining that the producer system is unresponsive to a current request provided by the first lease agent system. .
Article 37
Receiving a request from the producer system to register with the first lease agent system;
Determining whether the producer system is included in the subset of producer systems assigned to the first lease agent system;
Clause 27, further comprising registering the producer system at the first lease agent system in response to determining that the producer system is included in the subset of producer systems assigned to the first lease agent system. -Method according to clause 36.
Article 38
In response to determining that the producer system is not included in the subset of producer systems assigned to the first lease agent system, the method includes:
Identifying a second lease agent system of a plurality of lease agent systems assigned to the producer system;
38. The method of clause 37, further comprising providing identification information of the second lease agent system to the producer system.
Article 39
39. The method of clauses 27-38, wherein consumer systems of different consumer systems access different producer systems of the plurality of producer systems at different times over time.
Article 40
A system that divides a producer system among multiple lease agent systems,
A plurality of lease agents including a first lease agent;
And each lease agent of the plurality of lease agents includes one or more processors, wherein the first lease agent is a set of available producer systems in the first period and in the second period. Further comprising a splitting system configured to determine whether a difference in the set of available producer systems meets a threshold;
In response to determining that the difference meets the threshold, the split system
A set of producer systems based on the counts of several lease agents contained in multiple lease agents in order to distribute access to the multiple producer systems by the different user systems almost evenly among the multiple producer systems. Split into multiple subsets of the producer system,
A system further configured to provide, for an individual lease agent of a plurality of lease agents, the identity of the producer system included in one of the producer system subsets to the lease agent.
Article 41
41. The system of clause 40, wherein the number of producer system subsets corresponds to a count of the number of lease agents included in the plurality of lease agents.
Article 42
42. The system of clauses 40-41, wherein the splitting system is further configured to provide individual lease agents with identification information for a producer system included in a subset of the producer system that is different from the subset of the producer system.
Article 43
The split system further warns one or more lease agents of a plurality of lease agents not included in the first lease agent when the split system of the first lease agent splits the set of producer systems. 43. The system according to clause 40 to clause 42, configured as follows.
Article 44
In response to receiving a warning that the second lease agent of the plurality of lease agents is splitting the set of producer systems, the split system of the first lease agent further sets the set of producer systems. 44. The system of clauses 40-43, configured to refrain from splitting.
Article 45
The first lease agent is
Receiving a request from the producer system to register with the first lease agent;
Determining whether the producer system is included in the subset of producer systems assigned to the first lease agent;
Responsive to determining that the producer system is included in the subset of producer systems assigned to the first lease agent, registering the producer system with the first lease agent system;
In response to determining that the producer system is not included in the subset of producer systems assigned to the first lease agent, the second lease agent of the plurality of lease agents assigned to the producer system is identified. 45. The system of clauses 40-44, further comprising a status module configured to provide identification information of the second lease agent to the producer system.
Article 46
A method of splitting a lease among multiple lease agent systems,
Identifying a set of available producer systems by a first lease agent system that includes one or more processors;
Determining a number of leases available to individual producer systems of a set of available producer systems;
Assign several leases available to individual producer systems among multiple lease agent systems by assigning a subset of the leases available to individual producer systems to individual lease agent systems of multiple lease agent systems Splitting,
Providing the lease agent system with a subset of leases assigned to the lease agent system for individual lease agent systems of the plurality of lease agent systems;
And thereby
A method, wherein the division of several leases available to individual producer systems among multiple lease agent systems is adapted to allow for the distribution of workload among multiple lease agent systems.
Article 47
47. The method of clause 46, wherein individual lease agent systems are assigned non-overlapping subsets of leases.
Article 48
48. The method of clauses 46-47, wherein providing the lease subset to the lease agent system excludes providing the first lease agent system with the lease subset assigned to the lease agent system.
Article 49
Providing a lease agent system with a subset of leases assigned to a lease agent system provides the lease agent system with several leases assigned to the lease agent system for individual producer systems of multiple producer systems. 49. The method of clauses 46-48, comprising.
Article 50
50. Providing the lease agent system with a subset of leases assigned to the lease agent system includes providing the lease agent system with an identifier of an individual lease assigned to the lease agent system. the method of.
Article 51
Splitting several leases available for an individual producer system among multiple lease agent systems means that several leases available for an individual producer system are substantially equal between multiple lease agent systems. 51. A method according to clause 46 to clause 50, comprising dividing.
Article 52
52. The method of clause 46 to clause 51, wherein the plurality of lease agent systems includes a subset of a set of lease agent systems.
Article 53
53. The method of clause 52, wherein the plurality of lease agent systems includes a first lease agent system.
Article 54
54. The method of clauses 46-53, wherein the set of available producer systems includes a subset of available producer systems.
Article 55
The above splitting several leases available for individual producer systems among multiple lease agent systems means that the total number of leases available between a set of available producer systems in the first period is 55. The method of clause 46 to clause 54, wherein the method occurs in response to changing the threshold number compared to the second period.
Article 56
A method of selecting a producer system from a plurality of producer systems to provide access to a service, comprising:
Receiving status information of a plurality of producer systems by a first lease agent system including one or more processors;
Individual producer systems of multiple producer systems with a selection weight,
At least some of the current status information reflects a determination of the current status of at least one producer system by at least one consumer system;
This method further includes
Modifying the producer status information including a set of metrics related to the performance of the plurality of producer systems for interacting with the consumer system for the plurality of producer systems based at least in part on the received status information;
Modifying selection weights associated with a plurality of producer systems based at least in part on a first metric of a set of metrics;
Receiving a request from a consumer system to lease access to one of a plurality of producer systems;
In response to receiving a request to lease access to one of the multiple producer systems,
Selecting a producer system of the multiple producer systems based at least in part on a corresponding selection weight associated with an individual producer system of the multiple producer systems to accommodate the consumer system;
Providing identification information of the selected producer system to the consumer system that provided the request to lease access to one of the plurality of producer systems;
Providing producer systems with producer status information related to the selected producer system;
And at least some of the producer status information is obtained from a second consumer system.
Article 57
57. The method of clause 56, wherein the plurality of producer systems includes a subset of the producer systems.
Article 58
58. The method of clauses 56-57, wherein modifying selection weights associated with multiple producer systems changes the probability that the above selecting a producer system selects a particular producer system.
Article 59
59. The method of clauses 56-58, wherein the current status information is received from at least one consumer system.
Article 60
60. The method of clause 59, wherein the at least one consumer system includes a consumer system that provided a request to lease access to one of the plurality of producer systems.
Article 61
61. The method of clauses 56-60, wherein current status information is received from a plurality of producer systems.
Article 62
61. The method of clauses 56-60, wherein the current status information is received from a second lease agent system.
Article 63
Determining whether a corresponding modified selection weight satisfies a removal threshold for a first producer system of the plurality of producer systems;
In response to the modified selection weight satisfying the removal threshold, removing the first producer system identity from the list of available producer systems, wherein the list of available producer systems is selected 64. The method of clause 56 to clause 63, comprising identifying information for an available producer system corresponding to a producer system of a plurality of producer systems that is available.
Article 64
64. The method of clause 63, wherein selecting a producer system from a plurality of producer systems includes selecting a producer system from a list of available producer systems.
Article 65
Tracking the count of producer systems removed from the list of available producer systems;
Clause 63, further comprising subdividing the available producer system among the plurality of lease agent systems in response to a count that satisfies the reduction threshold, wherein the plurality of lease agent systems includes a first lease agent system. -Method according to clause 64.
Article 66
64. The method of clause 63, wherein the removal threshold is based on an average value of a first metric of a plurality of producer systems.
Article 67
The producer status information provided to the consumer system includes an independent set of producer status information available to the first lease agent system, and the independent set of producer status information indicates that the consumer system has another leased producer. 67. The method of clauses 56-66 that allows a producer system that is less utilized compared to the system to be selected from a plurality of leased producer systems.
Article 68
Clause 56 to Clause 67, wherein selecting a producer system of the plurality of producer systems further comprises selecting one of the first set of producer systems having a lower load than the second set of producer systems. the method of.
Article 69
69. The method of clause 68, wherein the selected producer system is not associated with a minimum load and, as a result, the frequency of load fluctuations is reduced.
Article 70
A system for selecting a producer system of multiple producer systems to provide access to a service,
A first lease agent of a plurality of lease agents, comprising a current module and one or more processors configured to execute the lease system;
Including
The current module is
Each producer system receives current status information of a first producer system of a plurality of producer systems related to the selection weight;
Configured to modify a selection weight associated with the first producer system based at least in part on the received current status information;
The leasing agent
Receive a request to access one of multiple producer systems;
Selecting a producer system of a plurality of producer systems, including the first producer system, based at least in part on a corresponding selection weight associated with an individual producer system of the plurality of producer systems to accommodate the request Configured system.
Article 71
71. The system of clause 70, wherein the current status information is received at the first lease agent by the lease system, the lease system further configured to provide the current status information to the current status module.
Article 72
The current module is
Further configured to determine whether the first producer system is assigned to the first lease agent.
In response to determining that the first producer is not assigned to the first lease agent, the current module is
Identifying a second lease agent assigned to the first producer;
72. The system of clauses 70-71, further configured to provide received status information to a second lease agent.
Article 73
The current module is
Determine whether the modified selection weight meets the removal threshold;
73. The system of clauses 70-72, further configured to disconnect the first producer system from the plurality of producer systems in response to the modified selection weight that meets the removal threshold.
Article 74
The first lease agent is configured to subdivide the plurality of producer systems among the plurality of lease agents in response to the number of producer systems disconnected from the plurality of producer systems meeting a reduction threshold. The system of clause 73, further comprising a system.
Article 75
75. The system of clauses 70-74, wherein the leasing system is further configured to provide the producer system identification information to the consumer system that provided the request to access one of the plurality of producer systems.
Article 76
76. The system of clauses 70-75, wherein the selected producer system includes a first producer system.
Article 77
A fixed physical computer storage that includes computer-executable instructions that, when executed on one or more processors, direct a computing system to select from among a plurality of producer systems that provide at least access to a service. And access is at least
In response to receiving at the first lease agent the current information of the first producer system of the plurality of producer systems, wherein the individual producer systems are associated with the selection weights and are divided into several subsets of the producer systems. Determining whether the first producer is an element of the first subset of the producer system associated with the first lease agent;
Responsive to determining that the first producer system is an element of the first subset of the producer system, modifying the selection weight associated with the first producer system;
In response to receiving the request to access the producer system, the first subset of the producer system based at least in part on a selection weight associated with the producer system of the producer system subset to accommodate the provider of the request Fixed physical computer storage provided by selecting a second producer system.
Article 78
78. Fixed physical computer storage according to clause 77, wherein the second producer system and the first producer system are the same.
Article 79
In response to determining that the first producer system is not an element of the first subset of the producer system, the method includes:
Identifying a second subset of the producer system including the first producer system;
Identifying a second lease agent associated with the second subset of the producer system;
79. The fixed physical computer storage of clauses 77-78, further comprising providing current status information to a second lease agent.
Article 80
A method of accessing a service provided by a producer virtual machine in an overlay network, comprising:
A consumer system host including one or more processors configures the consumer system host to host one or more consumer virtual machines, at least one of the consumer virtual machines being associated with the first overlay network And
Receiving requests to access services on the producer system from a consumer virtual machine hosted by the consumer system host
The request includes an inner header, the inner header includes a consumer virtual machine address associated with the consumer virtual machine and the target virtual address;
This method further
Accessing a spool that is associated with the consumer virtual machine and that includes a set of leased producer virtual machines leased for the consumer virtual machine;
Selecting a leased producer virtual machine from the lease pool to access the service from the pool;
Replacing the target virtual address in the inner header with the producer virtual machine address associated with the leased producer virtual machine;
Identifying the producer system host associated with the leased producer virtual machine;
And the producer system host is configured to host one or more producer virtual machines, at least one of the producer virtual machines is associated with the first overlay network;
This method further
Encapsulating the request with an outer header that includes a producer system host address associated with the producer system host and a consumer system host address associated with the consumer system host;
Providing a request over a network to a producer system host, thereby enabling the producer system host to process the request.
Article 81
Choosing a leased producer virtual machine
Determining whether the lease pool includes at least one available leased producer virtual machine;
Responsive to determining that the lease pool includes at least one available leased producer virtual machine, selecting one of the available leased producer virtual machines to select the available lease in the selection 81. The method of clause 80, comprising removing the created producer virtual machine from the lease pool.
Article 82
In response to determining that the lease pool does not contain an available leased producer virtual machine, the method includes:
Obtaining a lease for a set of producer virtual machines included in a first overlay network for a consumer virtual machine;
Initiating a connection of a set of leased producer virtual machines with individual producer virtual machines;
Adding a corresponding producer virtual machine to the lease pool for each connection established without failure, and selecting the leased producer virtual machine is added to the lease pool. 82. The method of clause 81, further comprising: selecting one of the selected virtual machine from the lease pool.
Article 83
Obtaining a lease for a set of producer virtual machines
Generating a request to obtain a lease to the producer virtual machine included in the first overlay network for the consumer virtual machine;
Providing a set of lease agents with a request to obtain a lease to the producer virtual machine;
83. The clause 82, comprising enabling at least some of the lease agents in the set of lease agents to initiate a connection with the producer virtual machine by receiving the producer virtual machine lease information. the method of.
Article 84
84. The method of clause 83, wherein the set of lease agents includes a subset of lease agents in the network.
Article 85
Receiving a response to the service request from the producer system host;
De-encapsulating the service response by removing the outer header of the response to gain access to the inner header of the response;
Determining one recipient consumer virtual machine of the consumer virtual machines hosted by the consumer system host based on the inner header of the response;
85. The method of clauses 80-84, further comprising providing an unencapsulated service response to the recipient consumer virtual machine.
Article 86
86. The method of clause 85, wherein the recipient consumer virtual machine and the consumer virtual machine are the same.
Article 87
Identifying the source virtual address associated with the source producer virtual machine associated with the response based on the inner header of the response;
90. The method of clauses 85-86, further comprising replacing an address contained in an inner header associated with the source producer virtual machine with a source virtual address.
Article 88
90. The source producer virtual machine corresponds to the selected leased producer virtual machine, the source virtual address corresponds to the target virtual address, and the recipient consumer virtual machine corresponds to the consumer virtual machine. Method.
Article 89
90. The method of clauses 80-88, wherein at least one of the consumer virtual machines is associated with a second overlay network.
Article 90
90. The method of clauses 80-89, wherein at least one of the producer virtual machines is associated with a second overlay network.
Article 91
Receiving a second request to access the service;
Determining whether the load of the leased producer virtual machine meets the load threshold;
In response to determining that the load of the leased producer virtual machine meets the load threshold
Selecting a second leased producer virtual machine from the lease pool to access the service;
Providing a second request to a second producer system host hosting a second leased producer virtual machine; The method according to clause 80 to clause 90, further comprising:
Article 92
92. The method of clause 91, wherein in response to determining that the load of the leased producer virtual machine meets a load threshold, the method further includes terminating the connection to the leased producer virtual machine.
Article 93
A system for accessing a service provided by a producer virtual machine in an overlay network,
Consumer system that includes one or more processors
And the consumer system host is configured to host one or more consumers, the consumer system host
A mapping repository configured to store producer mappings to producer system hosts;
Receives a request to access the service at the producer from a consumer hosted by the consumer system host,
Select leased producers that are leased on behalf of consumers to access the service,
Identify a producer system host configured to host one or more producers associated with the leased producer;
A system comprising an overlay network proxy configured to send a request to a producer system host.
Article 94
The mapping repository is further configured to store a leasepool associated with the consumer, the leasepool includes a set of leased producers leased for the consumer, and the overlay network proxy further includes:
Determine if the lease pool includes at least one available leased producer;
Responsive to determining that the lease pool includes at least one available leased producer, configured to select a leased producer to access the service from the available leased producers; The system described in clause 93.
Article 95
In response to determining that the lease pool does not include at least one available leased producer, the overlay network proxy further includes:
Generate a request for the consumer to get a lease to the producer,
Providing a set of lease agents with a request to obtain a lease to the producer;
95. The system of clause 94, configured to receive producer lease information for at least some of the lease agents in a set of lease agents.
Article 96
96. The system of clause 95, wherein the mapping repository is further configured to store lease information in a lease pool associated with the consumer.
Article 97
The overlay network proxy
Receive a response to the request from the producer host system,
Determine the recipient consumer, including the consumer, based on the inner header of the response,
96. The system of clauses 93-95, configured to provide a response to a consumer.
Article 98
The overlay network proxy
Identify the source virtual address associated with the leased producer,
98. The system of clause 97 configured to replace an address contained in an inner header associated with a leased producer with a source virtual address before providing a response to the consumer.
Article 99
The overlay network proxy is further configured to encapsulate the request with an outer header that includes a producer system host address associated with a producer system host and a consumer system host address associated with the consumer system host. The system described in.
Article 100
Fixed physical computer storage that includes computer-executable instructions that, when executed on one or more processors, direct a computing system to access services provided by a producer virtual machine in an overlay network,
Service is at least
Receives a request from the consumer virtual machine hosted by the consumer system host to access the service at the producer, including the target virtual address,
Select the leased producer virtual machine to access the service from the lease pool that contains the connection information of the producer virtual machine leased for the consumer virtual machine that is associated with the consumer virtual machine,
Replace the target virtual address in the header of the request with the producer virtual machine address associated with the leased producer virtual machine;
Determine the producer system host associated with the leased producer virtual machine,
Fixed physical computer storage accessed by allowing leased producer virtual machines to process requests to access services by providing leased producer virtual machines with requests to be sent to the producer system host .
Article 101
Selecting the leased producer virtual machine from the lease pool associated with the consumer virtual machine
Determining whether the lease pool includes connection information for at least one leased producer virtual machine that is not currently being used by the consumer virtual machine;
In response to determining that the lease pool does not include at least one leased producer virtual machine that is not currently being used by the consumer virtual machine, a computer executable instruction is provided to the computing system.
Obtain a lease for a set of producer virtual machines contained within the overlay network for the consumer virtual machine,
Initiates a connection of a set of leased producer virtual machines with individual producer virtual machines;
101. The fixed physical computer storage of clause 100, further comprising directing the connection information of the corresponding producer virtual machine to be added to the lease pool for connections established without failure.
Article 102
102. The fixed clause of clause 101, wherein selecting the leased producer virtual machine from the lease pool associated with the consumer virtual machine further comprises selecting one of the producer virtual machines whose connection information has been added to the lease pool. Physical computer storage.

Terminology Several computing systems have been described throughout this disclosure. These system descriptions are not intended to limit the teaching or applicability of the present disclosure. For example, the user systems described herein generally include desktops, laptops, video game platforms, television set-top boxes, televisions (eg, Internet TV), electronic control appliances, to name a few. And any computing device such as a wireless mobile device (eg, smart phone, PDA, tablet, etc.). Further, the user systems described herein can be different types of devices, include different applications, or otherwise configured in different ways. Further, the user systems described herein can include any type of operating system (“OS”). For example, a mobile computing system, an Android (registered trademark) OS, a Windows (registered trademark) OS, a Mac (registered trademark) OS, a Linux (registered trademark), or a UNIX (registered trademark) based OS described herein. Etc. can be executed.

  Further, the processing of the various components of the illustrated system can be distributed across multiple machines, networks, and other computing resources. In addition, two or more components of the system can be combined into fewer components. For example, the various systems illustrated as part of the lease agent 102 can be distributed across multiple computing systems or combined into a single computing system. Further, the various components of the illustrated system can be implemented in one or more virtual machines rather than in a dedicated computer hardware system. Similarly, the illustrated data repository can represent physical and / or logical data storage, including, for example, a storage area network or other distributed storage system. Further, in some embodiments, the connections between the illustrated components are not actual connections between hardware, but rather represent possible paths of data flow. Although several examples of possible connections are illustrated, any of the illustrated subsets of components can communicate with any other subset of components in various implementations.

  Depending on the embodiment, certain operations, events, or functions of the algorithms, methods, or processes described herein may be performed in a different order and may be added, integrated, or omitted collectively. (E.g., not all described acts or events are necessary for the practice of the algorithm). Further, in certain embodiments, operations or events may be, for example, multi-threaded processing, interrupt processing, or multiple processors, processor cores, or other parallel architectures, rather than sequentially. Can be run simultaneously on.

  Each of the various exemplary systems may be implemented as a computing system that is programmed and configured to perform the various functions described herein. A computing system may include a plurality of different computers or computing devices (eg, physical servers, workstations, storage arrays, etc.) that communicate and interoperate over a network to perform the functions described. Each such computing device typically includes a processor (or multiprocessor) that executes program instructions or modules stored in memory or other fixed computer-readable storage medium. Various functions disclosed herein may be embodied in such program instructions, but some or all of the disclosed functions may alternatively be in a computer system application specific circuit (eg, ASIC or FPGA). Can be realized. If a computing system includes multiple computing devices, these devices may be located at the same location but need not be located at the same location. The results of the disclosed methods and tasks can be stored persistently by converting physical storage devices such as solid state memory chips and / or magnetic disks to different states. Each described process may be implemented by one or more computing devices, such as one or more physical servers programmed with associated server code.

  In particular, the conditional languages used herein, such as “can be”, “can be”, “get”, “for example”, etc., are contextual unless otherwise stated or in use. Unless specifically understood otherwise, it is generally intended to convey that certain embodiments include certain features, elements and / or steps, but not other embodiments. Accordingly, such conditional languages generally require that features, elements and / or states be required for one or more embodiments in any respect, or for one or more embodiments, Logic for determining whether these features, elements and / or states should be included or executed in any particular embodiment, with or without author input or prompting It is not intended to mean including. Terms such as “comprising”, “including”, “having”, etc. are synonymous and are used comprehensively without limitation, excluding further elements, features, acts, operations, etc. It is not a thing. Also, the term “or” when used, for example, to relate a list of elements, the term “or” means one, some, or all of the elements in the list, Used in a comprehensive sense (and not in an exclusive sense). The articles “a” and “an” should be interpreted to mean “one or more” or “at least one” unless otherwise specified.

  Concatenated expressions, such as the expression “at least one of X, Y, and Z”, unless otherwise specified, to convey that an item, term, etc. can be X, Y, or Z in other ways To be understood with context as commonly used. Thus, such linked representations generally require that certain embodiments each have at least one of X, at least one of Y, and at least one of Z each present. It is not intended to mean to do.

While the foregoing detailed description has illustrated, described, and pointed out novel features as applied to various embodiments, various omissions, substitutions, and changes in the form or detail of exemplary devices or algorithms are disclosed herein. It will be understood that this can be done without departing from the spirit of. Thus, nothing in the foregoing description is intended to imply that any particular feature, characteristic, step, module, or block is necessary or essential. As will be appreciated, the process described herein provides all of the features and advantages defined herein so that some features can be used or practiced separately from others. It can be implemented in a non-native form. The scope of the invention is defined by the appended claims rather than the foregoing description. All changes that fall within the meaning and range of equivalency of the claims are to be embraced within the scope of the invention.

Claims (14)

A system for leasing access to a producer system to obtain access to a service hosted by the producer system,
Comprising a consumer system including one or more processors;
The consumer system is
Generate a lease request to access the producer system service,
Providing the lease request to a plurality of lease agents;
Receiving identification information of the producer system from at least some of the plurality of lease agents ;
A lease requester configured to receive from the producer system a lease time that includes a period of time that the consumer system is allowed to access the service at the producer system ;
The consumer system further comprises a connection module configured to attempt to initiate a connection with the producer system identified by the plurality of lease agents,
The consumer system further includes a configuration resource requestor as the connection module to access the service in the response producer system to establish without failure the connection between the producer system, system. The connection module is further configured to provide the lease time associated with said producer system to the producer system, system of claim 1. The resource requester further includes an existing service request to access the service at the producer system before the lease time expires in response to the amount of time remaining from the lease time for the producer system that meets a lease threshold. Is configured to calculate the probability that will not be completed,
The lease requester further comprises:
Generating an update lease request to access the service at the producer system in response to calculating that the probability satisfies an update threshold;
The system of claim 2, configured to provide the renewed lease request to the lease agent of the plurality of lease agents that provided the identification information of the producer system. Look including the current state information of at least a portion of the metadata relating to the producer system, at least part of the obtained the current state information of the meta data from the producer system, providing the identification information of the first producer system The system of claim 1, further comprising a status module configured to provide to the lease agent of the plurality of lease agents. A method of leasing access to a producer system to obtain access to a service hosted by the producer system, comprising:
Generating a lease request to access one service of a plurality of producer systems by a consumer system including one or more processors;
Providing the lease request to a plurality of lease agents;
Receiving identification information from one or more lease agents of one or more of the producer systems;
Receiving a lease time of at least some of the producer systems, the lease time comprising a period of time that the consumer system is allowed to access the service at the producer system;
Attempting to initiate a connection with at least some of the producer systems identified by the plurality of lease agents;
Accessing the service provided by the first producer system in response to establishing without failure a connection with a first producer system of at least some of the producer systems;
Including methods. Receiving the identification information of one or more of the producer systems from an individual lease agent comprises receiving at least some consumable resources of the identified producer systems;
The consumable resources are: (i) a period of time that the consumer system is authorized to access the service on at least some of the identified producer systems ; (ii) a set of computation cycles ; iii) a financial budget for use of at least some of the identified producer systems , or (iv) disk storage,
In response to the amount of consumable resources remaining from the consumable resources of the first producer system meeting a lease threshold, the method comprises:
Calculating a probability that an existing service request to access the service at the first producer will not be completed before the consumable resource expires;
Responsive to calculating that the probability satisfies an update threshold, generating an update lease request to access the service at the first producer system;
Further comprising providing the renewed lease request to the lease agents of the plurality of lease agents that provided the identification information of the first producer system;
In response to providing the renewal lease request to the lease agent, the method receives an update amount of the consumable resource of the first producer system or a consumable of a new producer system. 6. The method of claim 5 , further comprising receiving a new amount of resources, wherein the new producer system is different from the first producer system. In response to establishing the connection of the producer system with the at least some of the first producer systems without failure, the method comprises:
Further including obtaining metadata from the first producer system, wherein at least a portion of the metadata includes current status information related to the first producer system;
The method
6. The method of claim 5 , further comprising providing at least a portion of the current status information to the lease agent of the plurality of lease agents that provided the identification information of the first producer system. In response to establishing without failure the connection between the at least some of the second producer system of the producer system, access to the second service in the second producer system, according to claim 5 The method described in 1. A system that leases access to a producer system to provide access to services hosted by the producer system,
A first lease agent comprising a first lease system implemented in a computer system comprising computer hardware;
With
The first leasing system includes:
Receiving a first request from a consumer system to lease access to a service provided by some producer system;
A first of the first plurality of producer systems comprising a first subset of the several producer systems based at least in part on producer status information associated with individual producer systems of the first plurality of producer systems; Identify the producer system
Responsive to identifying the first producer system, configured to provide identification information of the first producer system to the consumer system;
The system further comprises a second lease agent that includes a second lease system, the second lease system comprising:
Receiving a second request from the consumer system to lease access to the service;
Configured to identify a second producer system of the second plurality of producer systems based at least in part on producer status information associated with the individual producer systems of the second plurality of producer systems; A plurality of producer systems comprising a second subset of the several producer systems, wherein the second subset of the several producer systems is identical to the first subset of the several producer systems The second lease system further provides identification information of the second producer system to the consumer system in response to identifying the second producer system, so that the consumer system At least the first It is configured to allow the requesting access to B inducer system and the service from the second producer system, thereby identifying the said first producer system and the second producer system Is a distributed process distributed at least between the first lease agent and the second lease agent. Wherein the first lease system is further configured to first lease time information to provide to the consumer system, the first lease time information, so that the consumer system to access the first producer system It means a period of time allowed for, the second lease system is further configured second lease time information to provide to the consumer system, the second lease time information, the consumer system The system of claim 9 , meaning a period of time that is allowed to access the second producer system. The first lease agent further includes a first status module, and the first status module includes:
Receiving first updated status information of the first producer system;
Configured to update the producer current status information of the first producer system based at least in part on the first updated current status information;
The second lease agent further includes a second current status module, and the second current status module includes:
Receiving second updated status information of the second producer system;
The system of claim 9 , wherein the system is configured to update the producer status information of the second producer system based at least in part on the second updated status information. The system of claim 11 , wherein the first updated current status information and the second updated current status information are received from the consumer system. 12. The system of claim 11 , wherein the first updated current state information is received from the first producer system and the second updated current state information is received from the second producer system. . The first lease agent further includes:
Receiving a first lease renewal request from the consumer system to obtain a further lease time of the first producer system;
Determining whether to accept the first lease renewal request based at least in part on producer status information of the first producer system;
Responsive to determining to accept the first lease renewal request, configured to provide the consumer system with a first lease renewal time of the first producer system;
In response to determining not to accept the first lease renewal request, the first lease agent further comprises:
Identifying a third producer system of the first plurality of producer systems based at least in part on producer status information associated with each producer system of the first plurality of producer systems;
The system of claim 9 , wherein the system is configured to provide identification information of the third producer system to the consumer system in response to identifying the third producer system.