Multi-cluster resource management

• US 10,700,991 B2
• Filed: 11/26/2018
• Issued: 06/30/2020
• Est. Priority Date: 11/27/2017
• Status: Active Grant

• Current Assignee: Nutanix Incorporated
• Original Assignee: Nutanix Incorporated
• Inventors: Khinvasara, Abhijit S., Gupta, Karan, Parthasarathy, Ranjan
• Primary Examiner(s): Nguyen, Quang N
• Application Number:
  US16/200,525
• Publication Number:
  US 20190342229A1
• Time in Patent Office: 582 Days
• Field of Search: 709203, 709205, 709206, 709217, 709219, 709223, 709224, 709226, 709228, 709230, 709232, 709238
• CPC Class Codes: G06F 2009/4557 Distribution of virtual machine instances; Migration and load balancing
• CPC Class Codes: G06F 2009/45579 I/O management, e.g. providing access to device drivers or storage
• CPC Class Codes: G06F 2009/45595 Network integration; Enabling network access in virtual machine instances
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: H04L 41/0895 Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
• CPC Class Codes: H04L 41/0896 Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 43/0805 by checking availability
• CPC Class Codes: H04L 43/0876 Network utilisation, e.g. volume of load or congestion level
• CPC Class Codes: H04L 43/20 the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
• CPC Class Codes: H04L 45/04 Interdomain routing, e.g. hierarchical routing
• CPC Class Codes: H04L 45/42 Centralised routing
• CPC Class Codes: H04L 45/46 Cluster building
• CPC Class Codes: H04L 45/70 Routing based on monitoring results
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/74 measures in reaction to resource unavailability
• CPC Class Codes: H04L 47/76 using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions

Abstract

Entries in individual portions of a network map serve to establish inter-cluster routes that are formed from routing data structures at individual clusters, which routing data structures store connection parameters pertaining to access point nodes in a multi-cluster computing environment. Upon receiving a resource management request at one of the access points, the request parameters are used in combination with the network map to identify at least one target access point having a virtual machine for responding to the resource management request. The resource management request is routed to a next hop access point node on route(s) to target access points. If the next hop access point node is not the node to respond to the resource management request, then processing at the next hop node serves to route the resource management request to a further next hop access point node on a route to the target access point.

Claims

1. A method for virtual entity resource management in a multi-cluster environment, the method comprising:

maintaining a network map of inter-cluster connections across multiple clusters, wherein an individual cluster of the multiple clusters maintains only a subset of the network map, and wherein the network map comprises routing data that refers to next hop access points;

receiving a resource management request at an access point, wherein the resource management request comprises a request parameter pertaining to a virtual machine at a cluster of the multiple clusters, and the virtual machine is associated with a target access point;

applying the request parameter to routing data at the access point to identify a next hop access point;

routing the resource management request to the next hop access point on a route to the target access point;

receiving the resource management request at the next hop access point and accessing routing data at the next hop access point to identify a further next hop on the route to the target access point; and

synchronizing at least a portion of the routing data with at least one interconnected cluster.

2. The method of claim 1, wherein the target access point is selected based at least in part on, a virtual machine identifier, an availability indicator, a capability indicator, or a resource usage measurement.

3. The method of claim 1, wherein the next hop access point is determined based at least in part on inter-cluster connections of the network map.

4. The method of claim 1, further comprising receiving the resource management request at the target access point and transmitting at least one result of processing the resource management request.

5. The method of claim 1, wherein the routing data comprises at least one of, a set of connection data, a set of mapping data, or a set of entity data.

6. The method of claim 1, wherein the routing data comprises a relationship between at least one of, an availability zone logical name, an availability zone physical identifier, a tenant identifier, a region identifier, an entity type, an entity identifier, a cluster identifier, an inter-cluster connection identifier, a request method, or a processing capability.

7. A non-transitory computer readable medium having stored thereon a sequence of instructions which, when executed by a processor causes a set of acts for virtual entity resource management in a multi-cluster environment, the set of acts comprising:

maintaining a network map of inter-cluster connections across multiple clusters, wherein an individual cluster of the multiple clusters maintains only a subset of the network map, and wherein the network map comprises routing data that refers to next hop access points;

receiving a resource management request at an access point, wherein the resource management request comprises a request parameter pertaining to a virtual machine at a cluster of the multiple clusters, and the virtual machine is associated with a target access point;

applying the request parameter to routing data at the access point to identify a next hop access point;

routing the resource management request to the next hop access point on a route to the target access point;

receiving the resource management request at the next hop access point and accessing routing data at the next hop access point to identify a further next hop on the route to the target access point; and

synchronizing at least a portion of the routing data with at least one interconnected cluster.

8. The non-transitory computer readable medium of claim 7, wherein the target access point is selected based at least in part on, a virtual machine identifier, an availability indicator, a capability indicator, or a resource usage measurement.

9. The non-transitory computer readable medium of claim 7, wherein the next hop access point is determined based at least in part on inter-cluster connections of the network map.

10. The non-transitory computer readable medium of claim 7, wherein the set of acts further comprise receiving the resource management request at the target access point and transmitting at least one result of processing the resource management request.

11. The non-transitory computer readable medium of claim 7, wherein the routing data comprises at least one of, a set of connection data, a set of mapping data, or a set of entity data.

12. The non-transitory computer readable medium of claim 7, wherein the routing data comprises a relationship between at least one of, an availability zone logical name, an availability zone physical identifier, a tenant identifier, a region identifier, an entity type, an entity identifier, a cluster identifier, an inter-cluster connection identifier, a request method, or a processing capability.

13. A system for virtual entity resource management in a multi-cluster environment, the system comprising:

a storage medium having stored thereon a sequence of instructions; and

a processor that executes the sequence of instructions to cause the processor to perform a set of acts, the set of acts comprising;

maintaining a network map of inter-cluster connections across multiple clusters, wherein an individual cluster of the multiple clusters maintains only a subset of the network map, and wherein the network map corresponds to comprises routing data that refers to next hop access points;

receiving a resource management request at an access point, wherein the resource management request comprises a request parameter pertaining to a virtual machine at a cluster of the multiple clusters, and the virtual machine is associated with a target access point;

applying the request parameter to routing data at the access point to identify a next hop access point;

routing the resource management request to the next hop access point on a route to the target access point;

receiving the resource management request at the next hop access point and accessing routing data at the next hop access point to identify a further next hop on the route to the target access point; and

synchronizing at least a portion of the routing data with at least one interconnected cluster.

14. The system of claim 13, wherein the target access point is selected based at least in part on, a virtual machine identifier, an availability indicator, a capability indicator, or a resource usage measurement.

15. The system of claim 13, wherein the next hop access point is determined based at least in part on inter-cluster connections of the network map.

16. The system of claim 13, wherein the set of acts further comprise receiving the resource management request at the target access point and transmitting at least one result of processing the resource management request.

17. The system of claim 13, wherein the routing data comprises at least one of, a set of connection data, a set of mapping data, or a set of entity data.

18. The system of claim 13, wherein the routing data comprises a relationship between at least one of, an availability zone logical name, an availability zone physical identifier, a tenant identifier, a region identifier, an entity type, an entity identifier, a cluster identifier, an inter-cluster connection identifier, a request method, or a processing capability.