Back to results
US 11,601,358 B2Granted
Cross datacenter communication using a mesh gateway
AssigneeHashiCorp
InventorsMatthew Keeler, Paul Banks, Mitchell Hashimoto, Armon Dadgar
Life of this patent
Estimating the term…
Abstract
A method for cross datacenter service-to-service communication over a shortest network route using mesh gateways. A mesh gateway receives a protocol message from a first service directed to a second service, identifies destination information associated with the second service, recognizes a routing configuration for routing the protocol message, determines a network route based on the routing configuration, and forwards the protocol message to another gateway associated with the second service over the determined network route.
Claims14
A method comprising:
- receiving, by a first gateway device, a protocol message directed to a service within a target datacenter;
- identifying, by the first gateway device, destination information of the service and the target datacenter;
- determining, by the first gateway device, a routing configuration for routing the protocol message to the target datacenter;
- determining, by the first gateway device, a network route for routing the protocol message to the target datacenter based on the routing configuration;
- and
- forwarding, by the first gateway device, the protocol message to a second gateway device within the target datacenter by transmitting the protocol message through the determined network route;
- wherein the routing configuration for routing the protocol message is at least one of a single-hop routing and a multi-hop routing;
- upon determining that the direct connection to the target datacenter does not exist, determining the network route for routing the protocol message to the target datacenter further comprises:
- determining, by the first gateway device, one or more distance(s) to one or more next-hop datacenter(s);
- determining, by the first gateway device, one or more distance(s) to the target datacenter as advertised by the one or more next-hop datacenter(s);
- calculating, by the first gateway device, one or more total distance(s) to the target datacenter based on the distance(s) to the one or more next-hop datacenter(s) and the distance(s) as advertised;
- and
- identifying, by the first gateway device, a route with a shortest total distance to the target datacenter from the one or more total distance(s) as the network route;
- and
- upon determining that the routing configuration configured for routing the protocol message is the multi-hop routing, determining the network route for routing the protocol message further comprises:
- determining, by the first gateway device, one or more distance(s) to one or more next-hop datacenter(s);
- determining, by the first gateway device, one or more distance(s) to the target datacenter as advertised by the one or more next-hop datacenter(s);
- calculating, by the first gateway device, one or more total distance(s) to the target datacenter based on the distance(s) to the one or more next-hop datacenter(s) and the distance(s) as advertised;
- and
- identifying, by the first gateway device, a route with a shortest total distance to the target datacenter from the one or more total distance(s) as the network route.
17 more elements
A computing device comprising:
- a processor;
- and
- a non-transitory computer readable medium having instructions embodied thereon that when executed by the processor causes the processor to perform operations comprising:
- receiving a protocol message directed to a service within a target datacenter;
- identifying a destination information of the service and the target datacenter;
- determining a routing configuration for routing the protocol message to the target datacenter;
- determining a network route for routing the protocol message to the target datacenter based on the routing configuration;
- and
- forwarding the protocol message to a second gateway device within the target datacenter by transmitting the protocol message through the determined network route wherein the routing configuration for routing the protocol message is at least one of a single-hop routing and a multi-hop routing;
- upon determining that the direct connection to the target datacenter does not exist, determining the network route for routing the protocol message to the target datacenter further comprises:
- determining, by the first gateway device, one or more distance(s) to one or more next-hop datacenter(s);
- determining, by the first gateway device, one or more distance(s) to the target datacenter as advertised by the one or more next-hop datacenter(s);
- calculating, by the first gateway device, one or more total distance(s) to the target datacenter based on the distance(s) to the one or more next-hop datacenter(s) and the distance(s) as advertised;
- and
- identifying, by the first gateway device, a route with a shortest total distance to the target datacenter from the one or more total distance(s) as the network route;
- and
- upon determining that the routing configuration configured for routing the protocol message is the multi-hop routing, determining the network route for routing the protocol message further comprises:
- determining, by the first gateway device, one or more distance(s) to one or more next-hop datacenter(s);
- determining, by the first gateway device, one or more distance(s) to the target datacenter as advertised by the one or more next-hop datacenter(s);
- calculating, by the first gateway device, one or more total distance(s) to the target datacenter based on the distance(s) to the one or more next-hop datacenter(s) and the distance(s) as advertised;
- and
- identifying, by the first gateway device, a route with a shortest total distance to the target datacenter from the one or more total distance(s) as the network route.
19 more elements
Dependencies are inferred from the claim text.