Routing messages between cloud service providers

Patent metadata

Field	Value
Publication number	US-11070619-B2
Application number	US-201916662285-A
Country	US
Kind code	B2
Filing date	Oct 24, 2019
Priority date	May 12, 2014
Publication date	Jul 20, 2021
Grant date	Jul 20, 2021

Abstract

Technology is disclosed for bridging clouds of computing devices for compute and data storage. The technology can receive a virtual routing table (VRT), wherein the VRT indicates an association with a virtual local area network (VLAN) and defines neighbors for each route wherein at least one neighbor is defined for each of the two different cloud service providers, wherein the route definition creates a private transitive network between the neighbors; receive from a first node a first message destined for a second node; determine that the first message employs the route specified by the VRT; forward the first message to the second node; receive from a third node a second message destined for the second node; determine that the second message does not employ the route specified by the VRT; and fail to forward the second message to the second node.

First claim

The invention claimed is:

1. A method comprising:
receiving, by a storage device over a first virtual local area network (VLAN), an Internet Protocol (IP) message from a first cloud service provider to a second cloud service provider, the IP message including a header indicating in a protocol level different than IP that the second cloud service provider is to receive the IP message;
creating a port of the first VLAN on a physical interface of a storage cluster of a first tenant, wherein the physical interface is connected to a trunk port of a switch associated with the storage device, wherein the header included in the IP message from the first cloud service provider includes a field with an identifier for the first VLAN; and
routing the IP message to the second cloud service provider using a first virtual routing table (VRT) associated with the first VLAN and the first tenant in the first VLAN, wherein the first cloud service provider and the second cloud service provider are identified in the first VRT.

2. The method of claim 1 , wherein the first VRT is identified as a labeled portion of a virtual routing and forwarding (VRF) table.

3. The method of claim 1 , further comprising isolating a second tenant within a second VLAN associated with a second VRT, wherein the second VRT is partitioned from the first VRT.

4. The method of claim 1 , further comprising creating a second VLAN comprising a second tenant and a third cloud service provider, wherein the third cloud service provider shares a common internet protocol network address with the first cloud service provider.

5. The method of claim 1 , wherein the protocol level different than IP includes an item selected from the list consisting of border gateway protocol and multiprotocol label switching.

6. The method of claim 1 , wherein the first VRT indicates an association with the first VLAN.

7. The method of claim 1 , wherein the first VRT indicates an association with the first VLAN, and wherein the first VRT is one of a plurality of VRTs associated with a plurality of VLANs.

8. A non-transitory machine-readable medium having stored thereon instructions for performing a method comprising machine executable code which when executed by at least one machine, causes the at least one machine to:
create a first virtual local area network (VLAN);
create a port of the first VLAN on a physical interface of a storage cluster of a first tenant, wherein the physical interface is connected to a trunk port of a switch associated with the storage cluster; and
route, using a first virtual routing table (VRT) associated with the first VLAN and the first tenant in the first VLAN, an Internet Protocol (IP) message from a first cloud service provider to a second cloud service provider, wherein the first cloud service provider and the second cloud service provider are identified in the first VRT, and the IP message includes a header indicating in a protocol level different than IP that the second cloud service provider is to receive the IP message, wherein the header included in the IP message from the first cloud service provider includes an identifier for the first VLAN.

9. The non-transitory machine-readable medium of claim 8 , wherein the first VRT is identified as a labeled portion of a virtual routing and forwarding (VRF) table.

10. The non-transitory machine-readable medium of claim 8 , further comprising machine executable code to isolate a second tenant within a second VLAN associated with a second VRT, wherein the second VRT is partitioned from the first VRT.

11. The non-transitory machine-readable medium of claim 8 , further comprising machine executable code to create a second VLAN comprising a second tenant and a third cloud service provider, wherein the third cloud service provider shares a common internet protocol network address with the first cloud service provider.

12. The non-transitory machine-readable medium of claim 8 , wherein the first tenant is a storage virtual machine operating on the storage cluster.

13. The non-transitory machine-readable medium of claim 8 , wherein the first VRT indicates an association with the first VLAN.

14. The non-transitory machine-readable medium of claim 8 , wherein the first VRT indicates an association with the first VLAN, and wherein the first VRT is one of a plurality of VRTs associated with a plurality of VLANs.

15. A computing device comprising:
a memory containing machine-readable medium comprising machine executable code having stored thereon instructions for performing a method of exchanging data across different cloud service providers; and
a processor coupled to the memory, the processor configured to execute the machine executable code to cause the processor to:
receive, over a first virtual local area network (VLAN), an Internet Protocol (IP) message from a first cloud service provider to a second cloud service provider, the IP message including a header indicating in a protocol level different than IP that the second cloud service provider is to receive the IP message;
create a port of the first VLAN on a physical interface of a storage cluster of a first tenant, wherein the physical interface is connected to a trunk port of a switch associated with the storage cluster; and
route the IP message to the second cloud service provider using a first virtual routing table (VRT) associated with the first VLAN and the first tenant in the first VLAN, wherein the first cloud service provider and the second cloud service provider are identified as neighbors in the first VRT, wherein the header included in the IP message from the first cloud service provider includes an identifier for the first VLAN.

16. The computing device of claim 15 , wherein the first VRT is identified as a labeled portion of a virtual routing and forwarding (VRF) table.

17. The computing device of claim 15 , further comprising machine executable code to isolate a second tenant within a second VLAN associated with a second VRT, wherein the second VRT is partitioned from the first VRT.

18. The computing device of claim 15 , further comprising machine executable code to create a second VLAN comprising a second tenant and a third cloud service provider, wherein the third cloud service provider shares a common internet protocol network address with the first cloud service provider.

19. The computing device of claim 15 , wherein the first VRT indicates an association with the first VLAN.

20. The computing device of claim 15 , wherein the first VRT indicates an association with the first VLAN, and wherein the first VRT is one of a plurality of VRTs associated with a plurality of VLANs.

Assignees

• Netapp Inc

Inventors

• Fullbright John Keith
• Beaupre Mark
• Gates Lee

Classifications

• H04L45/02

  Topology update or discovery · CPC title

• H04L67/51

  Discovery or management thereof, e.g. service location protocol [SLP] or web services · CPC title

• H04L67/1097 Primary

  for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title

• H04L45/04

  Interdomain routing, e.g. hierarchical routing · CPC title

• H04L12/4641

  Virtual LANs, VLANs, e.g. virtual private networks [VPN] (LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272) · CPC title