US 8,738,745 B1Grant
Managing use of intermediate destination hardware devices for provided computer networks
Issue Date:2014-05-27
•35 Claims
•15 Drawing Sheets
Abstract
Techniques are described for providing a managed computer network, such as for a managed virtual computer network overlaid on another substrate computer network, and including managing communications for computing nodes of the managed computer network by using one or more particular hardware devices connected to the substrate computer network to operate as a logical network node of the managed computer network that acts as an intermediate destination to provide one or more types of functionality for at least some communications that are sent by and/or directed to one or more computing nodes of the managed computer network. For example, a communication manager module associated with a source computing node for the managed computer network may determine to direct a communication from the source computing node over the substrate network to one or more substrate hardware devices that represent a particular intermediate destination network node of the managed computer network.
Metadata
Assignee
- Amazon Technologies, Inc.
Inventors
- Eric Jason Brandwine
- Kevin Christopher Miller
Application Information
Application Number:US 12/752,054
Filing Date:2010-03-31
Priority Date:2010-03-31
Art Unit:2452
Classifications
IPC:
G06F15/16
Patent Drawings (15 sheets)
Description
Background
[0001] Many companies and other organizations operate computer networks that interconnect numerous computing systems to support their operations, with the computing systems alternatively co-located (e.g., as part of a private local area network, or “LAN”) or instead located in multiple distinct geographical locations (e.g., connected via one or more other private or shared intermediate networks). For example, data centers housing significant numbers of interconnected co-located computing systems have become commonplace, such as private data centers that are operated by and on behalf of a single organization, as well as public data centers that are operated by entities as businesses. Some public data center operators provide network access, power, and secure installation facilities for hardware owned by various customers, while other public data center operators provide “full service” facilities that also include hardware resources made available for use by their customers. However, as the scale and scope of typical data centers and computer networks has increased, the task of provisioning, administering, and managing the associated physical computing resources has become increasingly complicated.
[0002] The advent of virtualization technologies for commodity hardware has provided some benefits with respect to managing large-scale computing resources for many customers with diverse needs, allowing various computing resources to be efficiently and securely shared between multiple customers. For example, virtualization technologies such as those provided by VMWare, XEN, Linux's KVM (“Kernel-based Virtual Machine”), or User-Mode Linux may allow a single physical computing machine to be shared among multiple users by providing each user with one or more virtual machines hosted by the single physical computing machine, with each such virtual machine being a software simulation acting as a distinct logical computing system that provides users with the illusion that they are the sole operators and administrators of a given hardware computing resource, while also providing application isolation and security among the various virtual machines.
Brief Description of the Drawings
[0003] FIGS. 1A and 1B are network diagrams illustrating example embodiments of managing communications for computing nodes belonging to a managed computer network.
[0004] FIGS. 2A-2F illustrate examples of managing communications between computing nodes of a managed virtual overlay computer network.
[0005] FIG. 3 is a block diagram illustrating example computing systems suitable for executing an embodiment of a system for managing communications between computing nodes.
[0006] FIG. 4 illustrates a flow diagram of an example embodiment of a System Manager routine.
[0007] FIGS. 5A-5B illustrate a flow diagram of an example embodiment of a Communication Manager routine.
[0008] FIGS. 6A-6B illustrate a flow diagram of an example embodiment of a Translation Manager routine.
Detailed Description
[0009] Techniques are described for providing managed computer networks, such as for managed computer networks that are each implemented as a virtual computer network overlaid on one or more other computer networks used as a substrate computer network. The managed computer networks may in some embodiments be provided by a configurable network service to users or other entities who are customers (e.g., for a fee) or otherwise clients of the configurable network service, such as to remote clients that access the configurable network service and/or the provided managed computer networks from remote locations over one or more intervening networks (e.g., over the Internet). In at least some embodiments, the techniques include managing communications for various computing nodes of a managed computer network, including in situations in which one or more particular logical network devices or other network nodes of the managed computer network are configured to operate as intermediate destinations for use in handling at least some communications that are sent by and/or directed to one or more computing nodes of the managed computer network. For example, if a source computing node of a managed computer network is initiating the sending of a communication to one or more indicated final destinations, and the managed computer network is configured to forward that sent communication to one or more intermediate destination network nodes of the managed computer network before the sent communication is to be provided to those final destinations, a manager module associated with the source computing node may in at least some such embodiments operate to identify a hardware device of the substrate computer network that represents one or more of those intermediate destination network nodes and to send the communication directly from the source computing node to the identified intermediate destination substrate hardware device for further handling (e.g., for forwarding to the indicated final destination(s), optionally after performing other processing of the communication). In at least some embodiments, some or all of the described techniques are automatically performed by embodiments of one or more manager modules, such as one or more system manager modules and/or one or more communication manager modules and/or one or more translation manager modules that are part of a network-accessible configurable network service.
[0010] The managing of communications for a managed computer network may in at least some embodiments include managing one or more logical network devices or other logical network nodes of the managed computer network that are configured to be used as intermediate destinations for at least some communications intended for other final destinations. Such intermediate destination logical network nodes may be configured to provide a variety of types of functionality in various embodiments, and such functionality may be implemented for such logical network nodes in various manners. As one example, a managed computer network may be configured to have a logical network topology with at least some of the computing nodes of the managed computer network being grouped together in various manners (e.g., in multiple logical sub-networks, or “subnets”)—if so, one or more specified logical network nodes of the managed computer network may be configured to provide functionality for communications that pass between different groups of computing nodes (e.g., to provide firewall capabilities between different subnets), and thus may be used as intermediate destinations for such inter-group communications. As another example, at least some of the computing nodes of a managed computer network may be co-located at a particular first geographical location (e.g., within a first data center), and one or more specified logical network nodes of the managed computer network may be configured to handle communications between the first location and other geographical locations (e.g., to computer systems at other data centers and/or to other external computer systems that are not part of the managed computer network).
[0011] In addition, functionality may be implemented in various manners in various embodiments for logical network nodes configured for managed computer networks. In at least some embodiments in which a managed computer network is implemented as a virtual computer network overlaid on a distinct underlying substrate network, as discussed in greater detail below, the substrate network may have existing hardware devices that are available for use in acting as a logical network node that is specified for the managed virtual computer network. As one example, the substrate network may have one or more alternative hardware devices that are each designed or otherwise configured to provide a first type of functionality (e.g., to provide firewall capabilities), and the implementing of the managed virtual computer network may include selecting one of those hardware devices to operate as a logical network node specified for the managed virtual computer network that is to provide that first type of functionality. As another example, the substrate network may have one or more alternative hardware devices that are each configurable to provide multiple types of functionality (whether simultaneously or serially), and the implementing of the managed virtual computer network may include configuring one or more of those hardware devices to provide one or more particular second types of functionality to enable the one or more hardware devices to operate as one or more logical network node specified for the managed virtual computer network that provide those second types of functionality. Such actions in selecting and/or configuring substrate hardware devices may be performed in various manners in various embodiments, as discussed in greater detail below, including by a system manager module for a configurable network service.
[0012] Furthermore, the described techniques may be used to provide a variety of types of functionality by intermediate destination substrate hardware devices representing configured logical network nodes in various embodiments. For example, in some embodiments, one or more intermediate destination substrate hardware devices and represented logical network nodes may act as edge devices or other edge modules that are used as part of forwarding communications between computing nodes at a first location and other external computer systems at one or more other locations, and that may optionally provide various additional functionality to manage such communications. Such optional additional functionality may include, for example, one or more of the following: firewall functionality; network address translation (“NAT”) functionality; port address translation (“PAT”) functionality; intrusion detection functionality; intrusion prevention functionality; content analysis functionality; wide area network (“WAN”) acceleration or other network acceleration functionality; virtual private network (“VPN”) connection endpoint functionality; etc. Similar functionality may also be provided by other types of intermediate destination substrate hardware devices and represented logical network nodes that do not act as edge modules in at least some embodiments, such as to manage communications passing between two or more groups of computing nodes of a managed computer network at a single geographical location. Furthermore, the final destinations to which communications are forwarded via the intermediate destination substrate hardware devices and represented logical network nodes may be of a variety of types in various embodiments. For example, if an intermediate destination substrate hardware device and represented logical network node is an edge module at a first location, another computing node of a managed computer network at the first location may send communications to final destinations at other locations, such as to other computing nodes of the same managed computer network that are located at a remote second location, to a computer system at another location that is not part of the same managed computer network (e.g., a computer system that is part of a remote computer network of the client to whom the managed computer network is provided), etc.
[0013] In addition, the ability to use substrate hardware devices to implement specified types of functionality for configured logical network nodes of a managed computer network and to use those substrate hardware devices as intermediate destinations may be performed in various manners in various embodiments. For example, the computing nodes of the managed computer network may in some embodiments each have an associated communication manager module that manages communications to and/or from the computing node, and the communication manager module associated with a source computing node that is sending a communication to one or more indicated final destinations may in at least some situations facilitate the sending of that communication by identifying a particular substrate hardware device that represents a particular intermediate destination network node via which the communication will be forwarded, such as if the communication meets one or more defined criteria (e.g., criteria based on the identities of the source computing node and/or indicated final destinations, and/or criteria based on one or more other attributes of the communication, such as the source and/or destination virtual network addresses, the source and/or destination port numbers, a networking protocol or other protocol used with the communication, a quality of service (“QoS”) specified for the communication, a type of content of the communication, etc.). In addition, the communication manager module may in at least some embodiments identify such a particular substrate hardware device to use for the outgoing communication before the outgoing communication has been sent from the source computing node over the substrate computer network, such as in accordance with specified configuration information for the managed computer network. As discussed in greater detail below, in some embodiments the source computing node may be one of multiple virtual machines hosted on a physical computer system, and the associated communication manager module may be provided by a virtual machine hypervisor monitor executing on the physical computing system to manage those hosted virtual machines.
[0014] In other embodiments and situations, rather than identifying a particular substrate hardware device that represents a particular intermediate destination logical network node for a communication before the communication is sent over an intervening substrate network, a particular substrate hardware device may in some embodiments be selected for a communication after the communication has been sent at least partially over the intervening substrate network (e.g., by a networking device or other component that is associated with two or more intermediate destination substrate hardware devices and that operates to direct certain communications to particular ones of the associated intermediate destination substrate hardware devices)—as one example, a communication manager module in such embodiments may, before sending such a communication over an intervening substrate network, modify one or more attributes of the sent communication or otherwise include information in the sent communication that will later be used by another component in the selection of a particular intermediate destination substrate hardware device (e.g., to modify a source network address for the sent communication, such as by spoofing a specified source network address for the communication that is not actually used by the source computing node that sends the communication). Furthermore, communication manager modules may be configured in some embodiments to accommodate various changes that occur while a managed computer network is in use, such as one or more of the following non-exclusive types of changes: changes to particular alternative intermediate destination logical network nodes that are available for use, such as to reflect new intermediate destination network nodes that are added for the configured managed computer network and/or previously used intermediate destination network nodes that become unavailable; changes to particular network addresses used with alternative intermediate destination logical network nodes, such as to reflect new network addresses that are added for the managed computer network and/or previously used network addresses that become unavailable; etc. Similarly, changes may occur to substrate hardware devices that are available for use with managed virtual computer networks while those managed virtual computer networks are in use, and communication manager modules and/or other modules may be configured in some embodiments to accommodate such changes, including one or more of the following non-exclusive types of changes: changes to particular substrate hardware devices that are available for use, such as to reflect new substrate hardware devices that are added and/or previously used substrate hardware devices that become unavailable; etc. Additional details related to various techniques for managing communications for managed computer networks that are forwarded via alternative intermediate destinations are included below.
[0015] In a manner similar to using communication manager modules to manage communications sent to and from computing nodes of a managed computer network, in some embodiments each substrate hardware device that operates as a logical network node for one or more managed computer networks may have one or more associated translation manager modules that are provided to manage communications directed to and/or from the substrate hardware device. Such translation manager modules may, for example, receive communications that are sent over the substrate network to a substrate hardware device that represents a particular logical network node for a particular managed virtual computer network, and perform various actions to enable the substrate hardware device to provide functionality for the communications corresponding to specified functionality of the logical network node. For example, if the logical network node is configured to provide functionality based on a communication being formatted for the managed virtual computer network (e.g., based on source and destination virtual network addresses in the header of the communication), but the communication sent over the substrate network is encoded in a manner corresponding to the substrate network (e.g., to use source and destination substrate network addresses, and optionally to use a networking protocol or other format for the substrate network that is distinct from a networking protocol or other format used by the managed virtual computer network), an associated translation manager module for the substrate hardware device may decode the communication and provide it to the substrate hardware device in a decoded format that the substrate hardware device expects.
[0016] In addition, if a particular substrate hardware device operates as multiple logical network nodes for multiple managed virtual computer networks, an associated translation manager module for the substrate hardware device may in some embodiments perform actions for a received communication to enable the substrate hardware device to identify the particular managed virtual computer network to which the communication corresponds, such as by adding information to the decoded communication to represent or otherwise identify the particular managed virtual computer network. As one example, in some embodiments, each such managed virtual computer network may be associated with a distinct virtual local area network (“VLAN”) identifier, and an associated translation manager module for such a substrate hardware device adds the VLAN identifier to a communication for a managed virtual computer network that corresponds to the managed virtual computer network. Similarly, if the substrate hardware device forwards such a communication on to its intended final destination after performing one or more specified types of functionality for a logical network node that the substrate hardware device represents, an associated translation manager module for the substrate hardware device may remove such an added VLAN identifier or other added identifying information before forwarding the communication towards its intended final destination.
[0017] Furthermore, the one or more translation manager modules for a substrate hardware device may be provided in various manners in various embodiments. For example, in some embodiments, a particular substrate hardware device may itself implement a translation manager module associated with the substrate hardware device (e.g., by executing software instructions for a software translation manager module, such as in addition to executing other software instructions for a module corresponding to a particular type of functionality provided by a particular logical network node that the substrate hardware device represents), while in other embodiments a distinct physical hardware device may implement one or more translation manager modules that support one or more substrate hardware devices. In addition, a substrate hardware device may be configured in some situations to support multiple logical network interfaces for a particular logical network node that the substrate hardware device represents for a particular managed computer network, and in some embodiments a single translation manager module may be used to manage communications for all of the logical network interfaces for that managed computer network, while in other embodiments a distinct translation manager module may be provided for each logical network interface. Similarly, a substrate hardware device may be configured in some situations to represent multiple logical network nodes for one or more particular managed computer networks, and in some embodiments a single translation manager module may be used to manage communications for all of the logical network nodes and/or managed computer networks, while in other embodiments a distinct translation manager module may be provided for each such represented logical network node and/or managed computer network. Additional details related to substrate hardware devices and associated translation manager modules are included below.
[0018] As noted above, in at least some embodiments, the described techniques include managing communications for a managed computer network being provided, including in embodiments in which the managed computer network is a virtual computer network that is overlaid on one or more underlying substrate computer networks. In such embodiments, communications may be encoded in various manners before being sent over an underlying substrate network (e.g., to use substrate network addresses for the communication source and/or final destination in the encoded communication that are distinct from virtual network addresses used for the communication source and/or final destination in the original pre-encoded communication, as well as to format or otherwise encode the communication in a manner specific to the substrate network), and the described techniques may be used in conjunction with such encoded communications (e.g., by using the pre-encoded virtual network addresses for the source and/or final destination to select a particular intermediate destination in the substrate network to use), as discussed in greater detail below. Before discussing some additional details of managing such communications in particular manners, however, some aspects of such managed computer networks in at least some embodiments are introduced.
[0019] In particular, a managed computer network between multiple computing nodes may be provided in various ways in various embodiments, such as in the form of a virtual computer network that is created as an overlay network using one or more intermediate physical networks that separate the multiple computing nodes. In such embodiments, the intermediate physical network(s) may be used as a substrate network on which the overlay virtual computer network is provided, with messages between computing nodes of the overlay virtual computer network being passed over the intermediate physical network(s), but with the existence and use of the intermediate physical network(s) being transparent to the computing nodes (e.g., with the computing nodes being unaware of and/or being unable to detect the intermediate physical networks) in at least some such embodiments. For example, the multiple computing nodes may each have a distinct physical substrate network address that corresponds to a location of the computing node within the intermediate physical network(s), such as a substrate IP (“Internet Protocol”) network address (e.g., an IP network address that is specified in accordance with IPv4, or “Internet Protocol version 4,” or in accordance with IPv6, or “Internet Protocol version 6,” such as to reflect the networking protocol used by the intermediate physical networks). In other embodiments, a substrate network on which a virtual computer network is overlaid may itself include or be composed of one or more other virtual computer networks, such as other virtual computer networks implemented by one or more third parties (e.g., by an operator or provider of Internet or telecom infrastructure).
[0020] When computing nodes are selected to participate in a managed computer network that is being provided on behalf of a user or other entity and that is a virtual computer network overlaid on a substrate network, each computing node may be assigned one or more virtual network addresses for the provided virtual computer network that are unrelated to those computing nodes' substrate network addresses, such as from a range of virtual network addresses used for the provided virtual computer network—in at least some embodiments and situations, the virtual computer network being provided may further use a networking protocol that is different from the networking protocol used by the substrate network (e.g., with the virtual computer network using the IPv4 networking protocol, and the substrate computer network using the IPv6 networking protocol). The computing nodes of the virtual computer network inter-communicate using the virtual network addresses (e.g., by sending a communication to another destination computing node by specifying that destination computing node's virtual network address as the destination network address for the communication), but the substrate network may be configured to route or otherwise forward communications based on substrate network addresses (e.g., by physical networking router devices and other physical networking devices of the substrate network). If so, the overlay virtual computer network may be implemented from the logical edge of the intermediate physical network(s), by modifying the communications that enter the intermediate physical network(s) to encode the communications for the intermediate physical networks (e.g., to use substrate network addresses that are based on the networking protocol of the substrate network), and by modifying the communications that leave the intermediate physical network(s) to decode the communications (e.g., to use virtual network addresses that are based on the networking protocol of the virtual computer network). Additional details related to the provision of such an overlay virtual computer network are included below.
[0021] In at least some embodiments, a network-accessible configurable network service (“CNS”) is provided by a corresponding CNS system, and the CNS system provides managed overlay virtual computer networks to remote customers (e.g., users and other entities), such as by providing and using numerous computing nodes that are in one or more geographical locations (e.g., in one or more data centers) and that are inter-connected via one or more intermediate physical networks. The CNS system may use various communication manager modules at the edge of the one or more intermediate physical networks to manage communications for the various overlay virtual computer networks as they enter and leave the intermediate physical network(s), and may use one or more system manager modules to coordinate other operations of the CNS system. For example, to enable the communication manager modules to manage communications for the overlay virtual computer networks being provided, the CNS system may track and use various information about the computing nodes of each virtual computer network being managed, such as to map the substrate physical network address of each such computing node to the one or more overlay virtual network addresses associated with the computing node. Such mapping and other information may be stored and propagated in various manners in various embodiments, including centrally or in a distributed manner, as discussed in greater detail below.
[0022] In addition, in at least some embodiments, the CNS system may further provide one or more hardware devices that are accessible via the substrate network, and use those substrate hardware devices to implement functionality for logical network devices or other network nodes specified for one or more managed virtual computer networks. Furthermore, the CNS system may use various translation manager modules that operate at the edge of the one or more intermediate physical networks to manage communications for the various overlay virtual computer networks as they enter and leave the intermediate physical network(s) on their way to associated substrate hardware devices that act as intermediate destinations for those communications. To enable the translation manager modules to manage communications for the overlay virtual computer networks being provided and for associated substrate hardware devices, the CNS system may track and use various information about the substrate hardware devices and about corresponding logical network nodes of the managed virtual computer networks that the substrate hardware devices represent, such as to map the substrate physical network address of each such hardware device to one or more overlay virtual network addresses associated with the logical network nodes that the hardware device represents.
[0023] Furthermore, in order to provide managed virtual computer networks to users and other entities in a desired manner, the CNS system allows users and other entities to interact with the CNS system in at least some embodiments to configure a variety of types of information for virtual computer networks that are provided by the CNS system on behalf of the users or other entities, and may track and use such configuration information as part of providing those virtual computer networks. The configuration information for a particular managed virtual computer network having multiple computing nodes may include, for example, one or more of the following non-exclusive list: a quantity of the multiple computing nodes to include as part of the virtual computer network; one or more particular computing nodes to include as part of the virtual computer network; a range or other group of multiple virtual network addresses to associate with the multiple computing nodes of the virtual computer network; particular virtual network addresses to associate with particular computing nodes or particular groups of related computing nodes; a type of at least some of the multiple computing nodes of the virtual computer network, such as to reflect quantities and/or types of computing resources to be included with or otherwise available to the computing nodes; a geographic location at which some or all of the computing nodes of the virtual computer network are to be located; network topology information for the virtual computer network, such as to specify logical subnets and/or other logical topology of the virtual computer network, including one or more computing nodes of the virtual computer network and/or one or more logical network nodes of the virtual computer network that are configured to operate as intermediate destinations for at least some communications of the virtual computer network, and optionally to specify one or more types of functionality that each such intermediate destination computing node and/or intermediate destination network node is to provide; etc. In addition, the configuration information for a virtual computer network may be specified by a user or other entity in various manners in various embodiments, such as by an executing program of the user or other entity that interacts with an API (“application programming interface”) provided by the CNS system for that purpose and/or by a user that interactively uses a GUI (“graphical user interface”) provided by the CNS system for that purpose.
[0024] FIG. 1A is a network diagram illustrating an example of a network-accessible service that provides client-configurable managed computer networks to clients. In particular, in this example, at least some of the managed computer networks may be virtual computer networks, such as virtual computer networks that are created and configured as network extensions to existing remote private computer networks of clients, although in other embodiments the managed computer networks may have other forms and/or be provided in other manners. After configuring such a managed computer network being provided by the network-accessible service, a user or other client of the network-accessible service may interact from one or more remote locations with the provided computer network, such as to execute programs on the computing nodes of the provided computer network, to dynamically modify the provided computer network while it is in use, etc.
[0025] In particular, in the illustrated example of FIG. 1A , a configurable network service (“CNS”) 105 is available that provides functionality to clients (not shown) over one or more public networks 100 (e.g., over the Internet) to enable the clients to access and use managed computer networks provided to the clients by the CNS 105, including to enable the remote clients to dynamically modify and extend the capabilities of their remote existing private computer networks using cloud computing techniques over the public network 100. In the example of FIG. 1A , a number of clients interact over the public network 100 with a system manager module 110 of the CNS 105 to create and configure various managed computer networks 120 being provided by the CNS 105, with at least some of the provided computer networks 120 optionally being private computer network extensions to remote existing client private networks 130, and with at least some such of those provided computer network extensions 120 being configured to enable access from one or more corresponding client private networks 130 over the public network 100 (e.g., private access via VPN connections established over interconnections 100a and 100b, or access via other types of private or non-private interconnections). In this example embodiment, the system manager module 110 assists in providing functionality of the CNS 105 to the remote clients, such as in conjunction with various optional other modules 115 of the CNS 105 (e.g., various communication manager modules and/or translation manager modules), and in conjunction with various optional computing nodes 125 and/or networking devices 195 (e.g., substrate network router devices, edge devices, etc.) that are used by the CNS 105 to provide the managed computer networks 120. In this example embodiment, the CNS 105 further provides one or more substrate devices 190 that are accessible via a substrate network on which some or all of the provided computer networks 120 may be overlaid, such as to represent logical network nodes for one or more of the provided computer networks, and with each such substrate device being designed, configured and/or configurable to provide one or more types of functionality for at least some communications of those provided computer networks on behalf of the logical network node(s) that the substrate device represents. In at least some embodiments, the CNS system manager module 110 may execute on one or more computing systems (not shown) of the CNS 105, and may provide one or more APIs that enable remote computing systems to programmatically interact with the module 110 to access some or all functionality of the CNS 105 on behalf of clients (e.g., to create, configure, and/or initiate use of managed computer networks 120). In addition, in at least some embodiments, clients may instead manually interact with the module 110 (e.g., via a GUI provided by the module 110) to perform some or all such actions.
[0026] The public network 100 in FIG. 1A may be, for example, a publicly accessible network of linked networks, possibly operated by distinct parties, such as the Internet. The remote client private networks 130 may each include one or more existing private networks, such as a corporate or other private network (e.g., home, university, etc.) that is partially or wholly inaccessible to non-privileged users, and that includes computing systems and/or other networked devices (not shown) of a client. In the illustrated example, the provided computer networks 120 each include multiple computing nodes (not shown), at least some of which may be from the plurality of optional computing nodes 125 provided by or otherwise under the control of the CNS 105, while in other embodiments at least some other computing systems 135 may be used to provide some or all computing nodes for one or more of the provided computer networks 120—such other computing systems 135 may, for example, be provided by or under control of the client for whom a computer network 120 that uses those other computing systems 135 is provided, or may be computing systems that are provided by third parties (e.g., for a fee). In addition, some or all of the provided computer networks 120 may each optionally be configured to include one or more logical network devices or other logical network nodes, at least some of which may be implemented using the one or more substrate devices 190, while in other embodiments at least some other computing systems 135 may be used to represent some or all such logical network nodes. Each of the provided computer networks 120 may be configured in various ways by the clients for whom they are provided, and may each be a private computer network that is accessible only by the client that creates it, although in other embodiments at least some computer networks provided by the CNS 105 for clients may be publicly accessible. Similarly, while at least some of the provided computer networks 120 in the example may be extensions to remote client computer networks 130 that are private networks, in other embodiments the provided computer networks 120 may be standalone computer networks that are not extensions to other existing computer networks 130 and/or may be extensions to other client computer networks 130 that are not private networks.
[0027] Private access between a remote client private computer network 130 and a corresponding private computer network extension 120 provided for a client may be enabled in various ways, such as by establishing a VPN connection or other private connection between them that allows intercommunication over the public network 100 in a private manner. For example, the CNS 105 may automatically perform appropriate configuration on its computing nodes and other networking devices to enable VPN access to a particular private network extension 120 of a client, such as by automatically configuring one or more VPN mechanisms hosted by the CNS 105 (e.g., software and/or hardware VPN mechanisms, including a software VPN endpoint that is provided by one of the multiple computing nodes of the provided network extension 120), and/or may automatically provide appropriate configuration information to the client (e.g., credentials, access points, and/or other parameters) to allow a VPN mechanism hosted on the remote client private network 130 to establish the VPN access. After VPN access has been appropriately enabled and/or configured, a VPN connection may be established between the remote client private network and the provided private network extension, such as initiated by the client using IPsec (“Internet Protocol Security”) or other appropriate communication technologies, or instead a VPN connection or other private connection may be established to or between networks that use MPLS (“Multi Protocol Label Switching”) for data transmission. In addition, in the illustrated example, various network-accessible remote resource services 140 may optionally be available to remote computing systems over the public network 100, including to computing nodes on the remote client private networks 130. The resource services 140 may provide various functionality to the remote computing nodes, such as for at least some of the resource services 140 to provide remote computing nodes with access to various types of network-accessible computing-related resources (e.g., long-term storage capabilities, such as block storage that is mountable by particular computing nodes of the provided computer networks 120, or storage that is otherwise accessible from particular computing nodes of the provided computer networks 120 using API calls). Furthermore, at least some of the computer networks 120 that are provided by the CNS 105 may be configured to provide access to at least some of the remote resource services 140, with that provided access optionally appearing to computing nodes of the provided computer networks 120 as being locally provided via virtual connections 117 that are part of the provided computer networks 120, although the actual communications with the remote resource services 140 may occur over the public networks 100 (e.g., via interconnections 100b and 100c). In addition, in at least some embodiments, multiple distinct provided computer networks 120 may be configured to enable inter-access with each other.
[0028] The provided computer networks 120 may each be configured by clients in various manners. For example, in at least some embodiments, the CNS 105 provides various computing nodes 125 that are available for use with computer networks provided to clients, such that each provided computer network 120 may include a client-configured quantity of multiple such computing nodes that are dedicated for use as part of that provided computer network. In particular, a client may interact with the module 110 to configure a quantity of computing nodes to initially be included in a computer network provided for the client (e.g., via one or more programmatic interactions with an API provided by the CNS 105). In addition, the CNS 105 may provide multiple different types of computing nodes in at least some embodiments, such as, for example, computing nodes with various performance characteristics (e.g., processor speed, memory available, storage available, etc.) and/or other capabilities. If so, in at least some such embodiments, a client may specify the types of computing nodes to be included in a provided computer network for the client. In addition, in at least some embodiments, a client may interact with the module 110 to configure network addresses for a computer network provided for the client (e.g., via one or more programmatic interactions with an API provided by the CNS 105), and network addresses may later be dynamically added, removed or modified for a provided computer network of a client in at least some such embodiments, such as after the provided computer network has already been in use by the client. Furthermore, in at least some embodiments, a client may interact with the module 110 to configure network topology information for a computer network provided for the client (e.g., via one or more programmatic interactions with an API provided by the CNS 105), including to specify computing nodes and/or logical network nodes that act as intermediate destinations for at least some communications, and such network topology information may later be dynamically modified for a provided computer network in at least some such embodiments, such as after the provided computer network has already been in use by the client. Moreover, in at least some embodiments, a client may interact with the module 110 to configure various network access constraint information for a computer network provided for the client (e.g., via one or more programmatic interactions with an API provided by the CNS 105), and such network access constraint information may later be dynamically modified for a provided computer network in at least some such embodiments, such as after the provided computer network has already been in use by the client. In addition, in at least some embodiments, a client may interact with the module 110 to configure one or more logical network devices or other logical network nodes for a computer network provided for the client (e.g., via one or more programmatic interactions with an API provided by the CNS 105), including to specify one or more types of functionality to be provided by each configured logical network node (e.g., by selecting from one or more predefined types of functionality provided by existing configured substrate hardware devices, by providing one or more software modules to be executed that perform the specified one or more types of functionality, by providing one or more types of configuration information corresponding to a specified type of functionality, etc.), and such logical network node configuration information may later be dynamically modified for a provided computer network in at least some such embodiments, such as after the provided computer network has already been in use by the client.
[0029] Network addresses may be configured for a provided computer network in various manners in various embodiments. For example, the client may specify one or more address ranges (e.g., a Classless Inter-Domain Routing (“CIDR”) address block) or other groups of network addresses for the provided computer network, such that at least some of the specified network addresses are used for the computing nodes of the provided computer network, and with those specified network addresses optionally being a subset of network addresses used by an existing remote client computer network if the provided computer network is configured to be an extension to the remote client computer network. Such configured network addresses may in some situations be virtual or private network addresses that are not directly addressable from computing systems on the public network 100 (e.g., if the existing remote client computer network and the corresponding provided network extension use network address translation techniques and/or virtual networking techniques for the client computer network and its provided network extension), while in other situations at least some of the configured network addresses may be external public network addresses that are directly addressable from computing systems on the public network 100 (e.g.; a public network address that is a static Internet-routable IP address or other non-changing network address). In other embodiments, the CNS 105 may automatically select network addresses to be used for at least some computing nodes and/or specified logical network nodes of at least some provided computer networks, such as based on network addresses that are available for use by the CNS 105, based on selecting network addresses that are related to network addresses used by remote existing computer networks corresponding to the provided computer networks, etc. Furthermore, if two or more of the computer networks provided by the CNS 105 are configured to enable inter-communications between the provided computer networks (e.g., for two or more computer networks provided to a single customer, such as for different departments or groups within a single organization; for two or more computer networks provided to two or more distinct customers; etc.), the CNS 105 may in some embodiments automatically select network addresses to be used for at least some computing nodes and/or specified logical network nodes of those provided computer networks to facilitate the inter-communications, such as by using different network addresses for the various provided computer networks. In addition, in at least some embodiments in which the CNS 105 provides virtual networks to clients, such as by using overlay networks on a substrate network, each client may be allowed to specify any network addresses to be used for their provided computer networks, even if multiple clients specify the same or overlapping network addresses for their respective provided computer networks—in such embodiments, the CNS 105 manages the network addresses distinctly for each client, such that a first client may have a first computing node associated with a particular specified network address for the first client's provided computer network, while a distinct second client may have a distinct second computing node associated with the same particular specified network address for the second client's provided computer network. Once network addresses are configured or otherwise determined for a provided computer network, the CNS 105 may assign the network addresses to various of the computing nodes and/or logical network nodes of the provided computer network, such as in a random manner, by using DHCP (“Dynamic Host Configuration Protocol”) or other techniques for dynamic assignment of network addresses, etc.
[0030] Network topology information may be configured for a provided computer network in various manners in various embodiments. For example, a client may specify particular types of networking devices (e.g., routers, switches, etc.) and/or other network devices or nodes (e.g., load balancers, firewalls, proxies, network storage devices, printers, etc.) to be part of the provided computer network, and may specify interconnectivity information between networking devices and computing nodes. Furthermore, in at least some embodiments, the CNS 105 may provide available computing nodes and/or substrate devices available to represent logical network nodes in multiple geographical locations (e.g., in multiple geographically distributed data centers), and the configuration information specified by a client for a provided computer network may further indicate one or more geographical locations in which computing nodes and/or logical network devices of the provided computer network are to be located (e.g., to provide fault tolerance among the computing nodes of a provided computer network by having them located in multiple geographical locations), and/or may otherwise provide information about preferences or requirements of how the computing nodes and/or logical network devices of the provided computer network are to interoperate that is used by the CNS 105 to select one or more such geographical locations (e.g., minimum or maximum network latency or bandwidth for computing node intercommunications; minimum or maximum network proximity between computing nodes and/or logical network nodes; minimum or maximum geographic proximity between computing nodes and/or logical network nodes; having local access to particular resources or functionality that is not available in all such geographic locations; having specified locations relative to other external computing systems, such as to a remote computer network of the client and/or to a remote resource service; constraints or other preferences based on the cost of obtaining use of particular computing nodes and/or for particular types of interactions with particular computing nodes, such as costs associated with providing data to and/or from those computing nodes; etc.). As discussed in greater detail elsewhere, in at least some embodiments, the interconnections and intercommunications between computing nodes of a provided computer network are managed using an underlying substrate network (not shown) of the CNS 105, and if so, some or all of the configured network topology information may be simulated or otherwise emulated in at least some such embodiments using the underlying substrate network and corresponding modules of the CNS 105. For example, each of the computing nodes provided by the CNS 105 may be associated with a node communication manager module of the CNS 105 that manages communications to and from its associated computing node(s), and if so, the associated communication manager module for a computing node may take various actions to emulate desired functionality of a network with respect to that computing node, as discussed in greater detail elsewhere. Similarly, each substrate device used to represent a logical network node for a managed computer network may be associated with a translation manager module of the CNS 105 that manages communications to and from its associated substrate device(s), and if so, the associated translation manager module for a substrate device may take various actions to emulate desired functionality of a network with respect to that substrate device and the logical network node(s) that it represents, as discussed in greater detail elsewhere.
[0031] Network access constraint information may also be configured for a provided computer network in various manners in various embodiments. For example, a client may specify information about whether and how some or all of the computing nodes of a provided computer network are allowed to communicate with other computing nodes of the provided computer network and/or with other external computing systems, such as based on one or more of the following: directions of communications (incoming versus outgoing); types of communications (e.g., based on the types of content included and/or the types of communication protocols used, such as to allow HTTP requests for text but not images and to not allow FTP requests); locations of other computing systems (e.g., whether part of the provided computer network, part of a remote client computer network corresponding to the provided computer network, part of a remote resource service to which access has been established, external to the provided computer network and any corresponding remote client computer network, etc.); types of other computing systems; etc. In a manner similar to that for network topology information, the CNS 105 may enforce network access constraint information for provided computer networks in various manners.
[0032] Thus, managed computer networks may be provided for clients in various manners in various embodiments, and may be configured to have various types of functionality in various embodiments.
[0033] In addition, in at least some embodiments, the computing nodes of the managed computer networks may be physical computing systems and/or may be virtual machines that are each hosted on one or more physical computing systems, and the communications that are handled for managed computer networks may include transmissions of data (e.g., messages, packets, frames, streams, etc.) in various formats. As previously noted, some or all computing nodes used for a particular provided overlay virtual computer network may in some embodiments be provided by the CNS system for use by users, while in other embodiments some or all such computing nodes may instead be provided by a user who uses those computing nodes. Furthermore, in at least some situations, an embodiment of the CNS system may be part of or otherwise affiliated with a program execution service (or “PES”) that executes multiple programs on behalf of multiple customers or other users of the service, such as a program execution service that uses multiple computing systems on multiple physical networks (e.g., multiple physical computing systems and networks within a data center). In at least some such embodiments, virtual computer networks to which computing nodes belong may be selected based on associated users, such as based on the computing nodes executing programs on behalf of a user or other entity.
[0034] As previously noted, a virtual computer network may in some embodiments be provided as an overlay network that uses one or more intermediate physical networks as a substrate network, and one or more such overlay virtual computer networks may be implemented over the substrate network in various ways in various embodiments. For example, in at least some embodiments, communications between nodes of an overlay virtual computer network are managed by encoding and sending those communications over the substrate network without encapsulating the communications, such as by embedding virtual network address information for a computing node of the virtual computer network (e.g., the destination computing node's virtual network address) in a larger physical network address space used for a networking protocol of the one or more intermediate physical networks, while in other embodiments the communications are encoded in other manners (e.g., by storing virtual network address information from the pre-encoded communication in one or more header fields of the encoded communication or otherwise in a manner associated with the encoded communications, such as if the overlay virtual computer network and underlying substrate network use the same networking protocol). As one illustrative example, a virtual computer network may be implemented using 32-bit IPv4 network addresses, and those 32-bit virtual network addresses may be embedded as part of 128-bit IPv6 network addresses used by the one or more intermediate physical networks, such as by reheadering communication packets or other data transmissions (e.g., using Stateless IP/ICMP Translation, or SIIT), or otherwise modifying such data transmissions to translate them from a first networking protocol for which they are configured to a distinct second networking protocol. As another illustrative example, both the virtual computer network and substrate computer network may be implemented using the same network addressing protocol (e.g., IPv4 or IPv6), and data transmissions sent via the provided overlay virtual computer network using virtual network addresses may be modified to use different physical network addresses corresponding to the substrate network while the transmissions are sent over the substrate network, but with the original virtual network addresses being stored in the modified data transmissions or otherwise tracked so that the data transmissions may be restored to their original form when they exit the substrate network. In other embodiments, at least some of the overlay computer networks may be implemented using encapsulation of communications. Additional details related to SIIT are available at “Request For Comments 2765—Stateless IP/ICMP Translation Algorithm”, February 2000, Internet Engineering Task Force (“IETF”), which is hereby incorporated by reference in its entirety. This document is also available at the time of filing at tools<dot>ietf<dot>org<slash>html<slash>rfc2765 (where <dot> and <slash> are replaced by the corresponding characters with those names, “.” and “/”, respectively).
[0035] Furthermore, in addition to managing configured network topologies for provided virtual computer networks, the CNS system may use the described techniques to provide various other benefits in various situations, such as limiting communications to and/or from computing nodes of a particular virtual computer network to other computing nodes that belong to that virtual computer network. In this manner, computing nodes that belong to multiple virtual computer networks may share parts of one or more intermediate physical networks, while still maintaining network isolation for computing nodes of a particular virtual computer network. In addition, the use of the described techniques also allows computing nodes to easily be added to and/or removed from a virtual computer network, such as to allow a user to dynamically modify the size of a virtual computer network (e.g., to dynamically modify the quantity of computing nodes to reflect an amount of current need for more or less computing resources). Furthermore, the use of the described techniques also supports changes to an underlying substrate network—for example, if the underlying substrate network is expanded to include additional computing nodes and/or substrate devices at additional geographical locations, existing or new virtual computer networks being provided may seamlessly use those additional computing nodes and/or substrate devices, since the underlying substrate network will route communications to and from the substrate network addresses for those additional computing nodes and/or substrate devices in the same manner as for other previously existing substrate network computing nodes and/or substrate devices. In at least some embodiments, the underlying substrate network may be of any size (e.g., spanning multiple countries or continents), without regard to network latency between computing nodes at different locations.
[0036] At least some such benefits may similarly apply for logical subnets that are specified for such a particular provided virtual computer network, with the substrate network functionality used to emulate various functionality corresponding to the specified logical subnets. For example, the use of the underlying substrate network may enable different computing nodes assigned to a particular logical subnet to be located at any position within the substrate network, with the substrate network forwarding communications to destination computing nodes based on those destination computing nodes' substrate network addresses. Similarly, the use of the underlying substrate network may enable a substrate device representing a logical network node for a managed computer network to be located at any position within the substrate network, including in a manner that is independent of any computing nodes related to the logical network node, and with the substrate network forwarding communications to such substrate devices based on the substrate network addresses of those substrate devices. As such, the substrate network may support specified logical subnets or other configured network topology for a managed computer network, without any configuration for or other use of information about such specified logical subnets, and with the CNS system modules (e.g., communication manager modules) instead managing the corresponding functionality from the logical edges of the substrate network where the CNS system modules connect to the substrate network.
[0037] For illustrative purposes, some embodiments are described below in which specific types of computing nodes, networks, communications, network topologies, and configuration operations are performed. These examples are provided for illustrative purposes and are simplified for the sake of brevity, and the inventive techniques may be used in a wide variety of other situations, some of which are discussed below.
[0038] FIG. 1B is a network diagram illustrating an example embodiment of configuring and managing communications between computing nodes belonging to a virtual computer network, by overlaying the virtual computer network and the communications on one or more intermediate physical networks in a manner transparent to the computing nodes of the virtual computer network. In this example, the configuring and managing of the communications is facilitated by a system manager module, multiple communication manager modules, and multiple translation manager modules (not shown) of an example embodiment of the CNS system. The example CNS system may be used, for example, in conjunction with a publicly accessible program execution service (not shown), or instead may be used in other situations, such as with any use of virtual computer networks on behalf of one or more entities (e.g., to support multiple virtual computer networks for different parts of a business or other organization on a private network of the organization).
[0039] The illustrated example includes an example data center 190 with multiple physical computing systems operated on behalf of the CNS system. The example data center 190 is connected to an internet 185 external to the data center 190, which provides access to one or more computing systems 145a via private network 165, to one or more other globally accessible data centers 160 that each have multiple computing systems (not shown), and to one or more other computing systems 145b. The internet 185 may be, for example, a publicly accessible network of networks (possibly operated by various distinct parties), such as the Internet, and the private network 165 may be, for example, a corporate network that is wholly or partially inaccessible from computing systems external to the private network 165. Computing systems 145b may be, for example, home computing systems or mobile computing devices that each connects directly to the Internet (e.g., via a telephone line, cable modem, a Digital Subscriber Line (“DSL”), cellular network or other wireless connection, etc.).
[0040] The example data center 190 includes a number of physical computing systems 106a-106d and 155a-155n, as well as a Communication Manager module 150 that executes on one or more other computing systems or devices (not shown) to manage communications for the associated computing systems 155a-155n, and a System Manager module 110 that executes on one or more computing systems (not shown). In this example, each physical computing system 106a-106d hosts multiple virtual machine computing nodes and includes an associated virtual machine (“VM”) communication manager module (e.g., as part of a virtual machine hypervisor monitor for the physical computing system), such as VM Communication Manager module 109a and multiple virtual machines 107a on host computing system 106a, and such as VM Communication Manager module 109d and multiple virtual machines 107d on host computing system 106d. Physical computing systems 155a-155n do not execute any virtual machines in this example, and thus may each act as a computing node that directly executes one or more software programs on behalf of a user. The Communication Manager module 150 that manages communications for the associated computing systems 155a-155n may be implemented as part of various types of devices separate from the physical computing systems 155a-155n, such as, for example, a proxy computing device, a firewall device, or a networking device (e.g., a switch, router, hub, etc.) through which communications to and from the physical computing systems travel. In other embodiments, all or none of the physical computing systems at the data center may host virtual machines.
[0041] This example data center 190 further includes multiple physical networking devices, such as switches 119a-119b, edge router devices 127a-127c, and core router devices 132a-132c. Switch 119a is part of a physical sub-network that includes physical computing systems 106a-106c, and is connected to edge router 127a. Switch 119b is part of a distinct physical sub-network that includes physical computing systems 106d and 155a-155n, as well as the computing systems providing the Communication Manager module 150 and the System Manager module 110, and is connected to edge router 127b. The physical sub-networks established by switches 119a-119b, in turn, are connected to each other and other networks (e.g., the internet 185) via an intermediate interconnection network 122, which includes the edge routers 127a-127c and the core routers 132a-132c. The edge routers 127a-127c provide gateways between two or more physical sub-networks or networks. For example, edge router 127a provides a gateway between the physical sub-network established by switch 119a and the interconnection network 122, while edge router 127c provides a gateway between the interconnection network 122 and internet 185 (e.g., via the edge modules 108). The core routers 132a-132c manage communications within the interconnection network 122, such as by routing or otherwise forwarding packets or other data transmissions as appropriate based on characteristics of such data transmissions (e.g., header information including source and/or destination addresses, protocol identifiers, etc.) and/or the characteristics of the interconnection network 122 itself (e.g., routes based on the physical network topology, etc.). In addition, in this example, the one or more alternative edge modules 108 manage communications between computing nodes at the data center 190 and other external computer systems (e.g., computing systems 145a, computing systems 145b, computing systems at other data centers 160, etc.), such as in a manner analogous to a communication manager module (e.g., by decoding at least some communications that are leaving the data center 190 and that have been encoded for the substrate network at the data center 190, and/or by encoding at least some communications that are entering the data center 190 for use with the substrate network at the data center 190).
[0042] The illustrated System Manager module and Communication Manager modules may perform at least some of the described techniques in order to configure, authorize and otherwise manage communications sent to and from associated computing nodes, including to support providing various virtual networking functionality for one or more virtual computer networks that are provided using various of the computing nodes, and/or to support providing various emulated functionality for one or more virtual networking devices that are configured for one or more such provided virtual computer networks. For example, Communication Manager module 109a manages associated virtual machine computing nodes 107a, Communication Manager module 109d manages associated virtual machine computing nodes 107d, and each of the other Communication Manager modules may similarly manage communications for a group of one or more other associated computing nodes. The illustrated Communication Manager modules may configure communications between computing nodes so as to overlay one or more particular virtual networks over one or more intermediate physical networks that are used as a substrate network, such as over the interconnection network 122. Furthermore, a particular virtual computer network may optionally be extended beyond the data center 190 in some embodiments, such as if one or more other data centers 160 also provide computing nodes that are available for use by the example CNS system, and the particular virtual network includes computing nodes at two or more such data centers at two or more distinct geographical locations. Multiple such data centers or other geographical locations of one or more computing nodes may be inter-connected in various manners, including the following: directly via one or more public networks in a non-private manner, or via a private connection, not shown (e.g., a dedicated physical connection that is not shared with any third parties, such as a leased line; or a VPN or other mechanism that provides the private connection over a public network); etc. In addition, while not illustrated here, other such data centers or other geographical locations may each include one or more other Communication Manager modules that manage communications for computing systems at that data center or other geographical location, as well as over the global Internet 135 to the data center 100 and any other such data centers 160.
[0043] In addition, a particular virtual computer network may optionally be extended beyond the data center 190 in other manners in other embodiments, such as if one or more other Communication Manager modules at the data center 100 are positioned between edge router 127c and the global Internet 135 (e.g., if the edge devices 108 each provide at least some of the functionality of a Communication Manager module in encoding and decoding communications for virtual computer networks to use the underlying substrate network 122), or instead based on one or more other Communication Manager modules external to the data center 190 (e.g., if another Communication Manager module, not shown, is made part of private network 165, so as to manage communications for computing systems 145a over the internet 185 and private network 165). Thus, for example, if an organization operating private network 165 desires to virtually extend its private computer network 165 to one or more of the computing nodes of the data center 190, it may do so by implementing one or more Communication Manager modules as part of the private network 165 (e.g., as part of the interface between the private network 165 and the internet 185)—in this manner, computing systems 145a within the private network 165 may communicate with those data center computing nodes as if those data center computing nodes were part of the private network. In other embodiments, the private computer network 165 may instead be extended to one or more computing nodes of the data center 190 by the edge modules 108 of the data center 190 managing the communications between computing nodes of the private network 165 and particular data center 190 computing nodes.
[0044] Thus, as one illustrative example, one of the virtual machine computing nodes 107a on computing system 106a (in this example, virtual machine computing node 107a1) may be part of the same provided virtual computer network as one of the virtual machine computing nodes 107d on computing system 106d (in this example, virtual machine computing node 107d1), and may further both be assigned to a specified logical subnet of that virtual computer network that includes a subset of the computing nodes for that virtual computer network, such as with the IPv4 networking protocol being used to represent the virtual network addresses for the virtual computer network. The virtual machine 107a1 may then direct an outgoing communication (not shown) to the destination virtual machine computing node 107d1, such as by specifying a virtual network address for that destination virtual machine computing node (e.g., a virtual network address that is unique for the local broadcast domain of the specified logical subnet). The Communication Manager module 109a receives the outgoing communication, and in at least some embodiments determines whether to authorize the sending of the outgoing communication, such as based on previously obtained information about the sending virtual machine computing node 107a1 and/or about the destination virtual machine computing node 107d1 (e.g., information about virtual computer networks and/or entities with which the computing nodes are associated, information about any specified logical subnets to which the computing nodes belong, etc.), and/or by dynamically interacting with the System Manager module 110 (e.g., to obtain an authorization determination, to obtain some or all such information, etc.). By not delivering unauthorized communications to computing nodes, network isolation and security of entities' virtual computer networks is enhanced.
[0045] If the Communication Manager module 109a determines that the outgoing communication is authorized (or does not perform such an authorization determination), the module 109a determines the actual physical network location corresponding to the destination virtual network address for the communication. For example, the Communication Manager module 109a may determine the actual destination network address to use for the virtual network address of the destination virtual machine 107d1 by dynamically interacting with the System Manager module 110, or may have previously determined and stored that information (e.g., in response to a request from the sending virtual machine 107a1 for information about that destination virtual network address, such as a request that the virtual machine 107a1 specifies using Address Resolution Protocol, or ARP). The Communication Manager module 109a then re-headers or otherwise modifies the outgoing communication so that it is directed to Communication Manager module 109d using an actual substrate network address, such as if Communication Manager module 109d is associated with a range of multiple such actual substrate network addresses. FIGS. 2A-2B provide examples of doing such communication management in some embodiments.
[0046] When Communication Manager module 109d receives the communication via the interconnection network 122 in this example, it obtains the virtual destination network address for the communication (e.g., by extracting the virtual destination network address from the communication), and determines to which of the virtual machine computing nodes 107d managed by the Communication Manager module 109d that the communication is directed. The Communication Manager module 109d next determines whether the communication is authorized for the destination virtual machine computing node 107d1, with examples of such authorization activities discussed in further detail in the examples of FIGS. 2A-2B . If the communication is determined to be authorized (or the Communication Manager module 109d does not perform such an authorization determination), the Communication Manager module 109d then re-headers or otherwise modifies the incoming communication so that it is directed to the destination virtual machine computing node 107d1 using an appropriate virtual network address for the virtual computer network, such as by using the sending virtual machine computing node 107a1's virtual network address as the source network address and by using the destination virtual machine computing node 107d1's virtual network address as the destination network address. The Communication Manager module 109d then forwards or otherwise provides the modified communication to the destination virtual machine computing node 107d1, such as via shared memory (not shown) of the computing system 106d that is used to provide a logical network interface for the destination virtual machine computing node 107d1. In at least some embodiments, before forwarding the incoming communication to the destination virtual machine, the Communication Manager module 109d may also perform additional steps related to security, as discussed in greater detail elsewhere.
[0047] In addition, while not illustrated in FIG. 1B , in some embodiments the various Communication Manager modules may take further actions to provide virtual networking functionality corresponding to a specified network topology for the provided virtual computer network (e.g., for one or more virtual networking devices for the provided virtual computer network), such as by managing communications between computing nodes of the provided virtual computer network in specified manners and by responding to other types of requests sent by computing nodes of the virtual computer network. For example, although being separated from computing node 107a1 on physical computing system 106a by the interconnection network 122 in the example embodiment of FIG. 1B , virtual machine computing node 107d1 on physical computing system 106d may be configured to be part of the same logical sub-network of the virtual computer network as computing node 107a1 (e.g., to not be separated by any logical router devices specified for the provided virtual computer network). Conversely, despite the physical proximity of virtual machine computing node 107c1 on physical computing system 106c to virtual machine computing node 107a1 on physical computing system 106a (i.e., being part of the same physical sub-network without any intervening physical substrate router devices) in the example embodiment of FIG. 1B , computing node 107c1 may be configured to be part of a distinct logical sub-network of the virtual computer network from that of computing node 107a1 (e.g., may be configured to be separated by one or more specified router devices of the provided virtual computer network, not shown, which in this example are virtual router devices that are not physically provided for the virtual computer network). If computing nodes 107a1 and 107d1 are configured to be part of the same logical sub-network, the previous example of sending a communication from computing node 107a1 to computing node 107d1 may be performed in the manner previously described, without emulating the actions of any intervening virtual router devices (despite the use of multiple physical router devices in the substrate interconnection network 122 for forwarding the communication), since computing nodes 107a1 and 107d1 are configured to be part of single sub-network in the specified network topology.
[0048] However, if computing node 107a1 sends an additional communication to computing node 107c1, the Communication Manager modules 109a and/or 109c on the host computing systems 106a and 106c may perform additional actions that correspond to one or more virtual specified router devices configured in the specified network topology for the provided virtual computer network to separate the computing nodes 107a1 and 107c1. For example, the source computing node 107a1 may send the additional communication in such a manner as to initially direct it to a first of the virtual specified router devices that is configured to be local to computing node 107a1 (e.g., by including a virtual hardware address in the header of the additional communication that corresponds to that first virtual specified router device), with that first virtual specified router device being expected to forward the additional communication on toward the destination computing node 107c1 via the specified logical network topology. If so, the source Communication Manager module 109a may detect that forwarding of the additional communication to the virtual first router device (e.g., based on the virtual hardware address used in the header of the additional communication), or otherwise be aware of the configured network topology for the virtual computer network, and may take actions to emulate functionality of some or all of the virtual specified router devices that are configured in the specified network topology to separate the computing nodes 107a1 and 107c1. For example, each virtual router device that forwards the additional communication may be expected to take actions such as modifying a TTL (“time to live”) hop value for the communication, modify a virtual destination hardware address that is specified for the communication to indicate the next intended destination of the additional communication on a route to the destination computing node, and/or otherwise modify the communication header. If so, the source Communication Manager module 109a may perform some or all of those actions before forwarding the additional communication directly to the destination Communication Manager module 109c over the substrate network (in this case, via physical switch device 119a) for provision to destination computing node 107c1. Alternatively, some or all such additional actions to provide the virtual networking functionality for the sent additional communication may instead be performed by the destination Communication Manager module 109c after the additional communication is forwarded to the Communication Manager module 109c by the Communication Manager module 109a.
[0049] Furthermore, as part of the prior continuing example, computing node 107a1 may determine to send a third communication to a final destination computer system external to the data center, such as to a particular computing system 145a (e.g., with the particular computing system 145a not being part of the virtual computer network to which computing node 107a1 belongs). In this situation, the Communication Manager module 109a on the host computing system 106a that is associated with the source computing node 107a1 may further perform additional actions to support the use of an intermediate destination for the communication. In particular, in this example, the various edge modules 108 may be a pool of multiple alternative edge devices, such as to be optionally managed by a load balancer device (not shown). Thus, the Communication Manager module 109a determines that the final destination computing system 145a is external to the data center 190, and encodes the outgoing communication from the source computing node 107a1 for forwarding over the substrate network 122 from the host computing system 106a to one of the edge modules 108. The intermediate destination edge module 108 may then handle the encoded communication in a typical manner, such as by optionally decoding the communication, and forwarding the communication over the internet 185 to the final destination computing system 145a.
[0050] The example data center 190 of FIG. 1B further illustrates multiple substrate network devices 190 that are accessible via the interconnection network 122 used as the substrate for the virtual computer networks provided at the data center 190. In particular, the substrate network devices 190 include multiple network devices 190a-190m that are accessible in this example via switch 119b, and one or more network devices 190z that are accessible in this example via switch 119a. While not illustrated in this example, each of the substrate network devices 190 has one or more associated translation manager modules to manage communications to and from the substrate network devices, whether implemented on some or all of the network devices 190 or instead using other hardware devices (not shown), such as in a manner analogous to communication manager module 150. As described in greater detail elsewhere, such available network devices may provide a variety of types of functionality, and may in some embodiments be used to support networking functionality provided for various virtual computer networks, including to represent particular logical network nodes specified for the various virtual computer networks. As one illustrative example, network devices 190a and 190b may each be configured to provide load balancing capabilities, and a particular virtual computer network may be configured to include one or more specified load balancer logical network devices, such as to provide load balancing between multiple computing nodes of the virtual computer network that are alternatives for providing a particular type of functionality. If the multiple alternative load-balanced computing nodes are computing nodes 107a1 and 107d1 for the purpose of this example, and if network device 190a is selected to represent the load balancer logical network device for the virtual computer network, then communications directed to those computing nodes (e.g., to a common virtual network address for those computing nodes) may be routed to load balancer hardware network device 190a for handling as an intermediate destination. Thus, if computing node 107c1 initiates an outgoing communication to the multiple alternative load-balanced computing nodes, the Communication Manager module 109c associated with the computing node 107c1 receives the outgoing communication from computing node 107c1 and determines how to forward the outgoing communication, which in this situation involves identifying that the network device 190a represents the load balancer logical network device that is configured in the network topology for the virtual computer network to receive the communication, and forwarding the outgoing communication to the identified network device 190a over the substrate network (in this case, via the switch 119a, the interconnection network 122, and the switch 119b). While not illustrated here, a translation manager module associated with network device 190a may actually receive the forwarded communication from the substrate network, and perform various processing on the communication before it is provided to the substrate network device 190a, as described in greater detail elsewhere. When the network device 190a receives the forwarded communication, it determines how to further forward the communication in the manner specified for the load balancer logical network device (e.g., based on load balancing criteria specified for the load balancer logical network device), and in particular to select one of the multiple alternative load-balanced computing nodes 107a1 and 107d1 (e.g., based on load balancing criteria configured for the virtual computer network). The network device 190a then further forwards the communication to the selected computing node, in a manner similar to that discussed for other inter-node communications, and with an associated translation manager module (whether the same or a different translation manager module that handled the incoming communication to the network device 190a) optionally performing various processing on the outgoing communication before it is further forwarded over the substrate network. FIGS. 2C-2F provide examples of using substrate devices to represent configured logical network nodes of a managed virtual computer network in some embodiments.
[0051] By providing virtual networking functionality using the described techniques, the CNS system provides various benefits. For example, because the various communication manager modules and translation manager modules manage the overlay virtual network, specified networking devices and other network topology do not need to be physically implemented for virtual computer networks being provided, and thus corresponding modifications are not needed to the interconnection network 122 or switches 119a-119b to support particular configured network topologies of provided virtual computer networks. Nonetheless, if the computing nodes and software programs of a virtual computer network have been configured to expect a particular network topology for the provided virtual computer network, the appearance and functionality of that network topology may nonetheless be transparently provided for those computing nodes by the described techniques. In addition, the use of the described techniques by the CNS system enables intermediate destinations for communications to be used in various manners as desired, such as in a first manner specific to a first managed computer network that is distinct from a second manner specific to a second managed computer network (e.g., based on configuration information specified for the first and/or second managed computer networks), and/or such as to enable changes in how intermediate destinations are used to accommodate changing conditions.
[0052] Thus, various aspects of providing managed computer networks are described above, as well as elsewhere in this document, including to support virtual computer networks that are overlaid on an underlying substrate network. In addition, in at least some embodiments, the CNS system may use multiple communication manager modules and/or translation manager modules in additional manners, such as to emulate responses to networking requests made by computing nodes in the manner of a local physical networking device, including to respond to ping requests, SNMP (“Simple Network Management Protocol”) queries, etc. Furthermore, as described in greater detail below, in at least some embodiments, multiple modules of the CNS system may operate together in a distributed manner to provide a particular type of functionality (e.g., functionality corresponding to a particular logical networking device), such that no single module or physical device is singly responsible for emulating that particular type of functionality.
[0053] FIGS. 2A-2F illustrate further examples with additional illustrative details related to managing communications between computing nodes that occur via an overlay network over one or more physical networks, such as may be used by the computing nodes and networks of FIGS. 1A and/or 1B, or in other situations. In these examples, FIGS. 2A and 2B illustrate details regarding actions of various modules of an example CNS system in managing communications for computing nodes of a managed computer network that are sent directly to their final destinations, while FIGS. 2C-2F illustrate additional details regarding managing communications that are sent to final destinations via intermediate destination logical network nodes represented by substrate network devices.
[0054] In particular, FIG. 2A illustrates various example computing nodes 205 and 255 that may communicate with each other by using one or more intermediate interconnection networks 250 as a substrate network. In this example, IPv4 virtual computer networks are overlaid on an underlying substrate interconnection network 250, with the substrate network being, for example, a distinct IPv4 network or an IPv6 substrate network, although in other embodiments the interconnection network 250 and overlay virtual computer networks may use other networking protocols. In addition, in this example embodiment, the computing nodes are operated on behalf of multiple distinct entities to whom managed computer networks are provided, and a System Manager module 290 manages the association of particular computing nodes with particular entities and managed virtual computer networks, and tracks various configuration information specified for the managed virtual computer networks. The example computing nodes of FIG. 2A include four computing nodes that are executed on behalf of an example entity Z and that are part of a corresponding first managed virtual computer network provided for client entity Z, those being computing nodes 205a, 205c, 255a and 255b. In addition, other computing nodes are operated on behalf of other entities and belong to other provided virtual computer networks, such as computing node 205b that is part of a second managed virtual computer network provided for client entity Y, as well as other computing nodes 255.
[0055] In this example, the computing nodes 205 are managed by and physically connected to an associated Communication Manager module R 210, and the computing nodes 255 are managed by and physically connected to an associated Communication Manager module S 260. The CNS Communication Manager modules 210 and 260 are physically connected to an interconnection network 250, as is the System Manager module 290, although the physical interconnections between computing nodes, modules and the interconnection network are not illustrated in this example. As one example, computing nodes 205 may each be one of multiple virtual machines hosted by a single physical computing system, and Communication Manager module R may be part of a hypervisor virtual machine monitor for that physical computing system—if so, communications between the computing nodes 205 and the Communication Manager module R may be passed within that physical computing system without using any intervening computer network, such as via memory of the physical computing system, an internal bus of the physical computing system, etc. For example, with reference to FIG. 1B , computing nodes 205 may represent the virtual machines 107a, and computing nodes 255 may represent the virtual machines 107d. If so, Communication Manager module R would correspond to Communication Manager module 109a of FIG. 1B , Communication Manager module S would correspond to Communication Manager module 109d of FIG. 1B , the interconnection network 250 would correspond to interconnection network 122 of FIG. 1B , and the System Manager module 290 would correspond to System Manager module 110 of FIG. 1B . Alternatively, computing nodes 205 or 255 may instead each be a distinct physical computing system, such as to correspond to computing systems 155a-155n of FIG. 1 , or to computing nodes at other data centers or geographical locations (e.g., computing systems at another data center 160, computing systems 145a, etc.).
[0056] In this example, each of the Communication Manager modules of FIG. 2A is associated with a group of multiple physical substrate network addresses, which the Communication Manager modules manage on behalf of their associated computing nodes, although in other embodiments each Communication Manager module may instead use a single substrate network address that it shares among two or more associated computing nodes. For example, if the interconnection network 250 is an IPv4 network, Communication Manager module R may be associated with the IPv4 CIDR block 200.0.0.0/29, so as to enable at least some of the IPv4 addresses from 200.0.0.0 to 200.0.0.7 to each be treated as a substrate network address associated with one of the computing nodes, and Communication Manager module S may similarly be associated with the 16 IPv4 network addresses in the IPv4 CIDR block 200.0.20.0/28. Alternatively, if the interconnection network 250 is an IPv6 network, Communication Manager module R may, for example, be associated with the IPv6 network address range of “::0A:01/72”, which corresponds to the 128-bit addresses (in hexadecimal) from XXXX:XXXX:XXXX:XXXA:0100:0000:0000:0000 to XXXX:XXXX:XXXX:XXXA: 01FF:FFFF:FFFF:FFFF (representing 2 to the power of 56 unique IPv6 addresses), where each “X” may represent any hexadecimal character that is appropriate for a particular situation—if so, the interconnection network 250 will forward any communication with a destination network address in that range to Communication Manager module R, and with the initial 72 bits of the range specified, the Communication Manager module R may use the remaining available 56 bits to represent the computing nodes that it manages and to determine how to process incoming communications whose destination network addresses are in that range. If the interconnection network 250 is an IPv6 network, the Communication Manager module S may similarly be associated with an IPv6 network address range such as “::0B:02/72”.
[0057] For purposes of the example shown in FIG. 2A , computing nodes 205a, 205c, 255a, and 255b are part of a single managed virtual computer network provided for entity Z, and computing nodes 205a, 205c and 255a have assigned IPv4 virtual network addresses of “10.0.0.2”, “10.0.5.1” and “10.0.0.3”, respectively. Because computing node 205b is part of a distinct managed virtual computer network that is provided for entity Y, it can share the same virtual network address as computing node 205a without confusion. In this example, computing node A 205a intends to communicate with computing node G 255a, with the two computing nodes configured in this example to be part of a single common physical local area sub-network (not shown) in a configured network topology for the managed virtual computer network, and the interconnection network 250 and Communication Manager modules are transparent to computing nodes A and G in this example. In particular, despite the physical separation of computing nodes A and G, the Communication Manager modules 210 and 260 operate so as to overlay the managed virtual computer network for entity Z over the physical interconnection network 250 for communications between those computing nodes, including to emulate functionality corresponding to the configured local area sub-network of the managed virtual computer network, so that the lack of an actual local area sub-network is transparent to the computing nodes A and G.
[0058] In order to send the communication to computing node G, computing node A exchanges various messages 220 with Communication Manager module R 210, despite in the illustrated embodiment being unaware of the existence of Communication Manager module R (i.e., computing node A may believe that it is transmitting a broadcast message to all other nodes on the local sub-network, such as via a specified switching device that computing node A believes connects the nodes on the local sub-network). In particular, in this example, computing node A first sends an ARP message request 220-a that includes the virtual network address for computing node G (i.e., “10.0.0.3”) and that requests the corresponding hardware address for computing node G (e.g., a 48-bit MAC address). Communication Manager module R intercepts the ARP request 220-a, and responds to computing node A with a spoofed ARP response message 220-b that includes a virtual hardware address for computing node G.
[0059] To obtain the virtual hardware address for computing node G to use with the response message, the Communication Manager module R first checks a local store 212a of information that maps virtual hardware addresses to corresponding actual physical substrate network addresses, with each of the virtual hardware addresses also corresponding to an IPv4 virtual network address for a particular entity's managed virtual computer network. If the local store 212a does not contain an entry for computing node G (e.g., if none of the computing nodes 205 have previously communicated with computing node G and the System Manager module 290 does not push mapping information to the Communication Manager Module R without request; if a prior entry in local store 212a for computing node G has expired based on an associated expiration time; etc.), the Communication Manager module R interacts 225 with System Manager module 290 to obtain the corresponding actual physical substrate network address for computing node G on behalf of computing node A. In particular, in this example, the System Manager module 290 maintains provisioning information 292 that identifies where each computing node is actually located and to which entity and/or managed virtual computer network the computing node belongs, such as by initiating execution of programs on computing nodes for entities and virtual computer networks or by otherwise obtaining such provisioning information. As discussed in greater detail with respect to FIG. 2B , the System Manager module may determine whether the request from Communication Manager module R on behalf of computing node A for computing node G's actual physical substrate network address is valid, including whether computing node A is authorized to communicate with computing node G (e.g., such as based on being part of the same configured local area sub-network), and if so provides that actual physical substrate network address.
[0060] Communication Manager module R receives the actual physical substrate network address for computing node G from the System Manager module 290, and stores this received information as part of an entry for computing node G as part of mapping information 212a for later use (optionally with an expiration time and/or other information). In addition, in this example, Communication Manager module R determines a virtual hardware address to be used for computing node G (e.g., by generating a dummy identifier that is locally unique for the computing nodes managed by Communication Manager module R), stores that virtual hardware address in conjunction with the received actual physical substrate network address as part of the mapping information entry, and provides the virtual hardware address to computing node A as part of response message 220-b. By maintaining such mapping information 212a, later communications from computing node A to computing node G may be authorized by Communication Manager module R without further interactions with the System Manager module 290, based on the use of the virtual hardware address previously provided by Communication Manager module R. In some embodiments, the hardware address used by Communication Manager module R for computing node G may not be a dummy address, such as if System Manager module 290 further maintains information about hardware addresses used by the various computing nodes (e.g., virtual hardware addresses assigned to virtual machine computing nodes, actual hardware addresses assigned to computing systems acting as computing nodes, etc.) and provides the hardware address used by computing node G to Communication Manager module R as part of the interactions 225. In such embodiments, the Communication Manager module R may take further actions if computing nodes on different virtual networks use the same virtual hardware address, such as to map each combination of computing node hardware address and managed virtual computer network to a corresponding substrate network address.
[0061] In other embodiments, Communication Manager module R may interact with System Manager module 290 to obtain a physical substrate network address for computing node G or otherwise determine such a physical substrate network address at times other than upon receiving an ARP request, such as in response to any received communication that is directed to computing node G using the virtual network address “10.0.0.3” as part of entity Z's virtual computer network, or if the System Manager module provides that information to Communication Manager module R without request (e.g., periodically, upon changes in the information, etc.). Furthermore, in other embodiments, the virtual hardware addresses that are used may differ from this example, such as if the virtual hardware addresses are specified by the System Manager module 290, if the virtual hardware addresses are not random and instead store one or more types of information specific to the corresponding computing nodes, etc. In addition, in this example, if computing node A had not been determined to be authorized to send communications to computing node G, whether by the System Manager module 290 and/or Communication Manager module R, Communication Manager module R would not send the response message 220-b with the virtual hardware address (e.g., instead sends no response or an error message response).
[0062] In this example, if the interconnection network 250 is an IPv4 network, the returned actual physical substrate network address corresponding to computing node G in interactions 225 may be, for example, “200.0.20.4”, such as if the System Manager module 290 and/or the Communication Manager module S 260 has selected that substrate network address to represent computing node G from the substrate network address range associated with Communication Manager module S 260—thus, a communication sent over the interconnection network 250 to “200.0.20.4” will be routed to Communication Manager module S for handling. Alternatively, if the interconnection network 250 is an IP64 network, the returned IPv6 actual physical substrate network address corresponding to computing node G in interactions 225 may be “::0B:02:<Z-identifier>:10.0.0.3”, where “10.0.0.3” is stored in the last 32 bits of the 128-bit IPv6 address, and where “<Z-identifier>” is a 24-bit entity network identifier for computing node G corresponding to the managed virtual computer network for entity Z (e.g., as previously assigned by the System Manager module to that network to reflect a random number or some other number corresponding to the entity). In this example, the initial 72 bits of the IPv6 network address store the “::0B:02” designation, corresponding to the sub-network or other portion of the physical interconnection network with a network address range of “::0B:02/72” to which Communication Manager module S corresponds—thus, a communication sent over the interconnection network 250 to IPv6 destination network address “::0B:02:<Z-identifier>:10.0.0.3” will similarly be routed to Communication Manager module S for handling. In other embodiments, the entity network identifier may be other lengths (e.g., 32 bits, if Communication Manager module S has an associated network address range of 64 bits rather than 56 bits) and/or may have other forms (e.g., may be random, may store various types of information, etc.), and the remaining 56 bits used for the network address range after the “::0B:02” designation may store other types of information (e.g., an identifier for a particular entity, a tag or label for the virtual computer network, an identifier for a particular specified VLAN to which computing node G is assigned, etc.). In addition, some or all such information may instead be stored and/or transmitted with a communication to computing node G in other manners in other embodiments, such as by including the information in a header of the communication, including in situations in which the substrate network uses the IPv4 networking protocol.
[0063] After receiving the response message 220-b from Communication Manager module R, computing node A creates and initiates the sending of a communication to computing node G, shown in FIG. 2A as communication 220-c. In particular, the header of communication 220-c includes a destination network address for destination computing node G that is “10.0.0.3”, a destination hardware address for destination computing node G that is the virtual hardware address provided to computing node A in message 220-b, a source network address for sending computing node A that is “10.0.0.2”, and a source hardware address for sending computing node A that is an actual or dummy hardware address that was previously identified to computing node A (e.g., by Communication Manager module R, based on a configuration of computing node A, etc.). Since computing node A believes that computing node G is part of the same local sub-network as itself, computing node A does not need to direct the communication 220-c to any intermediate logical router devices that are configured in a network topology for the managed virtual computer network to separate the computing nodes.
[0064] Communication Manager module R intercepts the communication 220-c, modifies the communication as appropriate, and forwards the modified communication over the interconnection network 250 to computing node G. In particular, Communication Manager module R extracts the virtual destination network address and virtual destination hardware address for computing node G from the header, and then retrieves the actual physical substrate network address corresponding to that virtual destination hardware address from mapping information 212a. As previously noted, the actual physical substrate network address may be, for example, “200.0.20.4” or “::0B:02:<Z-identifier>10.0.0.3”, and Communication Manager module R creates a new IPv4 or IPv6 header for the encoded new communication (depending on whether the interconnection network is an IPv4 or IPv6 network, respectively) that includes that actual physical substrate network address as the destination address. Similarly, the Communication Manager module R extracts the virtual source network address and virtual source hardware address for computing node A from the header of the received communication, obtains an actual physical substrate network address corresponding to that virtual source hardware address (e.g., from a stored entry in mapping information 212a, by interacting with the System Manager module 290 to obtain that information if not previously obtained, etc.), and includes that actual physical substrate network address as the source network address for the new header of the new encoded communication. In this example, the actual physical substrate network address for computing node A may be “200.0.0.1” (if the interconnection network is an IPv4 network) or “::0A:01:<Z-identifier>10.0.0.2” (if the interconnection network is an IPv6 network), which if used in a reply by Communication Manager module S on behalf of computing node G will be routed to Communication Manager module R for forwarding to computing node A. The Communication Manager module R then creates communication 230-3 by modifying communication 220-c so as to replace the prior IPv4 header with the new header (e.g., in accordance with SIIT), including populating the new header with other information as appropriate for the encoded modified communication (e.g., payload length, traffic class packet priority, etc.). Thus, the communication 230-3 includes the same content or payload as communication 220-c, without encapsulating the communication 220-c within the communication 230-3 in this example. Furthermore, access to the specific information within the payload is not needed for such reheadering, such as to allow Communication Manager module R to handle communications in which the payload is encrypted without needing to decrypt that payload.
[0065] In at least some embodiments, before forwarding communication 230-3 to Communication Manager module S, Communication Manager module R may perform one or more actions to determine that communication 220-c is authorized to be forwarded to computing node G as communication 230-3, such as based on the mapping information 212a including a valid entry for the destination virtual hardware address used in communication 220-c (e.g., an entry specific to sending computing node 205a in some embodiments, or instead an entry corresponding to any of the computing nodes 205 in other embodiments). In other embodiments, such an authorization determination may not be performed by Communication Manager module R for each outgoing communication, or instead may be performed in other manners (e.g., based on a determination that the sending node and destination node are part of the same managed virtual computer network, are associated with the same entity, or are otherwise authorized to inter-communicate; based on an interaction with System Manager module 290 to obtain an authorization determination for the communication; etc.).
[0066] After Communication Manager module R forwards the modified communication 230-3 to the interconnection network 250, the interconnection network uses the physical destination substrate network address of the encoded communication to route the communication to Communication Manager module S. In doing so, the devices of the interconnection network 250 do not use information about the overlay virtual network addresses for computing nodes A or G or the entity network identifier for their virtual computer network, and thus do not need any special configuration to forward such a communication, nor even awareness that a managed virtual computer network is being overlaid on the physical interconnection network.
[0067] When Communication Manager module S receives communication 230-3 via the interconnection network 250, it performs actions similar to those of Communication Manager module R, but in reverse. In particular, in at least some embodiments, the Communication Manager module S verifies that communication 230-3 is legitimate and authorized to be forwarded to computing node G, such as via one or more interactions 240 with the System Manager module. If the communication is determined to be authorized (or if the authorization determination is not performed), the Communication Manager module S then modifies communication 230-3 as appropriate and forwards the modified communication to computing node G. Additional details related to the verification of the communication 230-3 are discussed with respect to FIG. 2B .
[0068] In particular, to modify communication 230-3, Communication Manager module S retrieves information from mapping information 262a that corresponds to computing node G, including the virtual hardware address used by computing node G (or generates such a virtual hardware address if not previously available, such as for a new computing node). Communication Manager module S then creates communication 245-e by modifying communication 230-3 so as to replace the prior header of the communication 230-3 encoded for the substrate network with a new IPv4 header for the overlay virtual computer network (e.g., in accordance with SIIT). The new IPv4 header includes the virtual network address and virtual hardware address for computing node G as the destination network address and destination hardware address for the new IPv4 header, the virtual network address and a virtual hardware address for computing node A as the source network address and source hardware address for the new IPv4 header, and includes other information as appropriate for the communication (e.g., total length, header checksum, etc.). The virtual hardware address used by Communication Manager module S for computing node A may be the same as the hardware address used by Communication Manager module R for computing node A, but in other embodiments each Communication Manager module may maintain separate hardware address information that is not related to the information used by the other Communication Manager modules (e.g., if Communication Manager module S generated its own dummy virtual hardware address for computing node A in response to a prior ARP request from one of the computing nodes 255 for computing node A's hardware address). Thus, the communication 245-e includes the same content or payload as communications 220-c and 230-3. Communication Manager module S then provides communication 245-e to computing node G.
[0069] After receiving communication 245-e, computing node G determines to send a response communication 245-f to computing node A, using the source virtual network address and source virtual hardware address for computing node A from communication 245-e. Communication Manager module S receives response communication 245-f, and processes it in a manner similar to that previously described with respect to communication 220-c and Communication Manager module R. In particular, Communication Manager module S optionally verifies that computing node G is authorized to send communications to computing node A (e.g., based on being a response to a previous communication, or otherwise based on configuration information for computing nodes A and G as previously described), and then modifies communication 245-f to create communication 230-6 by generating a new substrate network communication header using mapping information 262a. After forwarding communication 230-6 to the interconnection network 250, the communication is sent to Communication Manager module R, which processes the incoming communication in a manner similar to that previously described with respect to communication 230-3 and Communication Manager module S. In particular, Communication Manager module R optionally verifies that computing node G is authorized to send communications to computing node A and that communication 230-6 actually was sent from the substrate network location of computing node G, and then modifies communication 230-6 to create response communication 220-d by generating a new IPv4 header for the overlay virtual computer network using mapping information 212a. Communication Manager module R then provides response communication 220-d to computing node A. In some embodiments and situations, Communication Manager modules R and/or S may handle response communications differently from initial communications, such as to assume that response communications are authorized in at least some situations, and to not perform some or all authorization activities for response communications in those situations.
[0070] In this manner, computing nodes A and G may inter-communicate using a IPv4-based managed virtual computer network, without any special configuration of those computing nodes to handle the actual intervening one or more substrate networks, and substrate interconnection network 250 may forward communications encoded for it without any special configuration of any physical networking devices of the substrate interconnection network, based on the Communication Manager modules overlaying the virtual computer network over the actual physical interconnection network.
[0071] In addition, while not illustrated with respect to FIG. 2A , in at least some embodiments the Communication Manager modules may receive and handle other types of requests and communications on behalf of associated computing nodes. For example, Communication Manager modules may take various actions to support broadcast and multicast capabilities for computing nodes that they manage, including to optionally use various special reserved multicast group virtual network addresses. When a computing node sends a broadcast/multicast communication, any Communication Manager module with an associated computing node that has subscribed to that multicast/broadcast group would be identified (e.g., based on those Communication Manager modules having subscribed to the group, such as in response to prior join communications sent by those associated computing nodes), and the Communication Manager module for the sending computing node would forward the communication to each of the identified Communication Manager modules of the group, for forwarding to their appropriate managed computing nodes. In addition, in some embodiments and situations, at least some broadcast or multicast communications may not be forwarded by Communication Manager modules, such as communications with an IPv4 prefix of 224.0/16 or another designated prefix or other label or identifier. In addition to supporting broadcast and multicast capabilities for managed computing nodes, the Communication Manager modules may receive and handle other types of requests and communications on behalf of associated computing nodes that correspond to configured network topologies for the virtual computer networks to which the computing nodes belong. For example, computing nodes may send various requests that a specified local router device or other specified networking device would be expected to handle (e.g., ping requests, SNMP queries, etc.), and the associated Communication Manager modules may intercept such requests and take various corresponding actions to emulate the functionality that would have been provided by the specified networking device if it was physically implemented.
[0072] In addition, it will be appreciated that a Communication Manager module may facilitate communications between multiple of the computing nodes that are associated with that Communication Manager module. For example, with respect to FIG. 2A , computing node 205a may wish to send an additional communication (not shown) to computing node 205c. If so, Communication Manager module R would perform actions similar to those previously described with respect to the handling of outgoing communication 220-c by Communication Manager module R and the handling of incoming communication 230-3 by Communication Manager module S, but without reheadering of the additional communication to use an header for the substrate network since the communication will not travel over the interconnection network. However, if computing nodes 205a and 205c are configured in a network topology for the virtual computer network to be separated by one or more logical networking devices, the Communication Manager module R may take additional actions to emulate the functionality of those logical networking devices.
[0073] While not illustrated with respect to FIG. 2A , in at least some embodiments other types of requests and communications may also be handled in various ways. For example, in at least some embodiments, an entity may have one or more computing nodes that are managed by Communication Manager module(s) and that are part of a managed virtual computer network for that entity, and may further have one or more other non-managed computing systems (e.g., computing systems that are directly connected to the interconnection network 250 and/or that natively use the same network addressing protocol as that of the interconnection network) that do not have an associated Communication Manager module that manages their communications. If the entity desires that those non-managed computing systems be part of that virtual computer network or otherwise communicate with the managed computing nodes of the virtual computer network, such communications between managed computing nodes and non-managed computing systems may be handled by the Communication Manager module(s) that manage the one or more computing nodes in at least some such embodiments. For example, in such situations, if such a non-managed computing system is provided with an actual destination substrate network address for such a managed computing node, the non-managed computing system may send communications to the associated Communication Manager module for that managed computing node via interconnection network 250 using that destination substrate network address, and that Communication Manager module would forward those communications to that computing node (e.g., after reheadering the communications in a manner similar to that previously described) if the Communication Manager module is configured to accept communications from that non-managed computing system (or from any non-managed computing system). Furthermore, the Communication Manager module may generate a dummy virtual network address to correspond to such a non-managed computing system, map it to the actual substrate network address for the non-managed computing system, and provide the dummy virtual network address to its managed computing node (e.g., as the source address for the communications forwarded to the computing node from the non-managed computing system), thus allowing the computing node to send communications to the non-managed computing system.
[0074] In addition, as previously noted, a communication manager module manages communications for associated computing nodes in various ways, including in some embodiments by assigning virtual network addresses to computing nodes of a provided virtual computer network, and/or by assigning substrate physical network addresses to managed computing nodes from a range of substrate physical network addresses that correspond to the communication manager module. In other embodiments, some such activities may instead be performed by one or more computing nodes of the virtual computer network, such as to allow a DHCP (Dynamic Host Configuration Protocol) server or other device of a virtual computer network to specify virtual network addresses for particular computing nodes of the virtual network. In such embodiments, the communication manager module obtains such configuration information from the virtual computer network device(s), and updates its mapping information accordingly (and in some embodiments may further update one or more system manager modules that maintain information about computing nodes associated with virtual networks). In yet other embodiments, a user or other entity associated with a virtual computer network may directly configure particular computing nodes to use particular virtual network addresses. If so, the communication manager modules and/or system manager module may track which virtual network addresses are used by particular computing nodes, and similarly update stored mapping information accordingly.
[0075] FIG. 2B illustrates some of the computing nodes and communications discussed with respect to FIG. 2A , but provides additional details with respect to some actions taken by the Communication Manager modules 210 and 260 and/or the System Manager module 290 to authorize communications between computing nodes. For example, after computing node A sends message 220-a to request a hardware address for computing node G, Communication Manager module R may perform one or more interactions 225 with the System Manager module 290 in order to determine whether to provide that information, such as based on whether computing node A is authorized to communicate with computing node G, as well as to determine a corresponding substrate physical network address for computing node G based on interconnection network 250. If the Communication Manager module R has previously obtained and stored that information and it remains valid (e.g., has not expired), then the interactions 225 may not be performed. In this example, to obtain the desired physical network address corresponding to computing node G, Communication Manager module R sends a message 225-1 to the System Manager module 290 that includes the virtual network addresses for computing nodes A and G, and that includes an entity network identifier for each of the computing nodes, which in this example is an entity network identifier for the managed virtual computer network of entity Z (e.g., a 32-bit or 24-bit unique identifier). In at least some embodiments, Communication Manager module R may send message 225-1 to the System Manager module 290 using an anycast addressing and routing scheme, so that multiple System Manager modules (not shown) may be implemented (e.g., one for each data center that includes Communication Manager modules and associated computing nodes) and an appropriate one of those (e.g., the nearest, the most underutilized, etc.) is selected to receive and handle the message.
[0076] After the System Manager module 290 determines that computing node A is authorized to communicate with computing node G (e.g., based on having the same entity network identifier, based on computing node A having an entity network identifier that is authorized to communicate with computing nodes of the entity network identifier for computing node G, based on other information provided by or associated with computing node A indicating that computing node A is authorized to perform such communications, based on information provided by or associated with computing node G indicating that computing node A is authorized to perform such communications, etc.), the System Manager module 290 returns a response message 225-2 that includes the desired actual physical substrate network address corresponding to computing node G. In addition, in at least some embodiments, before sending the desired actual physical network address, the System Manager module 290 may further verify that Communication Manager module R is authorized to send the message 225-1 on behalf of computing node A, such as based on computing node A being determined to be one of the computing nodes to which Communication Manager module R is associated.
[0077] In other embodiments, Communication Manager module R may perform some or all of the actions described as being performed by System Manager module 290, such as to maintain provisioning information for the various computing nodes and/or to determine whether computing node A is authorized to send communications to computing node G, or instead no such authorization determination may be performed in some or all situations. Furthermore, in other embodiments, other types of authorization determinations may be performed for a communication between two or more computing nodes, such as based on one or more criteria associated with the communication (e.g., a type of the communication, a size of the communication, a time of the communication, etc.).
[0078] As previously noted with respect to FIG. 2A , after Communication Manager module S receives communication 230-3 intended for computing node G via the interconnection network 250, Communication Manager module S may perform one or more interactions 240 with the System Manager module 290 in order to determine whether to authorize that communication. In particular, in this example, to verify that the communication 230-3 is valid and authorized to be forwarded to computing node G, Communication Manager module S first extracts information from the encoded communication 230-3 that indicates the overlay virtual computer network source and destination virtual network addresses for computing nodes A and G and optionally the entity network identifier(s) for those computing nodes (e.g., from header fields in the encoded communication, or by extracting embedded information in the actual destination substrate network address and actual source substrate network address of the encoded communication 230-3). The Communication Manager module S next exchanges messages 240 with System Manager module 290 to obtain the corresponding actual substrate physical network address for the sending computing node A on behalf of computing node G, including a message 240-4 that includes the extracted virtual network addresses for computing nodes A and G in the overlay virtual computer network, as well as the entity network identifier for each of the computing nodes. In at least some embodiments, Communication Manager module S may send message 240-4 to the System Manager module 290 using an anycast addressing and routing scheme as previously described.
[0079] The System Manager module 290 receives message 240-4, and returns a response message 240-5 that includes the actual physical substrate network address corresponding to computing node A (e.g., “200.0.0.1” or “::0A:01:<Z-identifier>:10.0.0.2”). As previously discussed with respect to messages 225-1 and 225-2, in some embodiments the System Manager module 290 and/or Communication Manager module S may further perform one or more other types of authorization determination activities, such as to determine that computing node G is authorized to communicate with computing node A, that Communication Manager module S is authorized to send the message 240-4 on behalf of computing node G, etc. Communication Manager module S then verifies that the returned physical substrate network address in response message 240-5 matches the source substrate network address used to send the encoded communication 230-3 over the substrate network, so as to prevent attempts to spoof messages as being from computing node A that are actually sent from other computing nodes in other locations. Communication Manager module S optionally stores this received information from response message 240-5 as part of an entry for computing node A in mapping information 262a for later use, along with computing node A's virtual network address and a virtual hardware address for computing node A.
[0080] FIGS. 2C and 2D illustrate a further example of managing ongoing communications for the overlay virtual computer network described with respect to FIGS. 2A and 2B for client entity Z, but with communications being managed to support the use of a logical network node of the overlay virtual computer network that is configured to act as an intermediate destination for certain communications that are sent. In particular, FIG. 2C illustrates a logical network topology of the provided overlay virtual computer network, and FIG. 2D illustrates sending additional communications in accordance with the illustrated logical network topology. With respect to FIG. 2C , the provided overlay virtual computer network is illustrated as including two distinct logical subnets, logical subnet A 288a and logical subnet B 288b. Logical subnet A includes computing nodes A and G, as well as optionally including other computing nodes 286a of entity Z's virtual computer network that were not illustrated in FIGS. 2A and 2B . Logical subnet B includes computing node C, as well as optionally including other computing nodes 286b of entity Z's virtual computer network that were not illustrated in FIGS. 2A and 2B . In addition, the logical network topology of the provided overlay virtual computer network includes a logical network node H being configured to operate as an intermediate destination between the two logical subnets, and in particular to provide firewall capabilities in this example. Logical network node H is configured to have two logical network interfaces 213 in this example, including a first logical network interface H1 213a that corresponds to logical subnet A and has an associated network address of “10.0.0.9”, and a second logical network interface H2 213b that corresponds to logical subnet B and has an associated network address of “10.0.5.9”. It will be appreciated that configured network topologies may be more complex in other embodiments and situations, including in some situations to have a chain of multiple intermediate destination logical network nodes through which at least some communications are forwarded, such as described further with respect to FIG. 2F .
[0081] FIG. 2D provides an example of sending an additional communication in accordance with the illustrated logical network topology of FIG. 2C , and illustrates computing nodes A, C and G, Communication Manager modules R and S, System Manager module 290, and interconnection network 250 in a manner similar to that shown in FIGS. 2A and 2B . However, FIG. 2D illustrates additional substrate network address information for the computing nodes A, C and G and the Communication Manager modules R and S, and further illustrates at least one substrate hardware device that implements the functionality of logical network node H 255b of FIG. 2C , as well as at least one translation manager module that is associated with those substrate hardware devices. In particular, FIG. 2D illustrates substrate hardware device P 275 that is configured to operate as a firewall network node that handles communications being sent between the two logical subnets configured for the provided virtual computer network, and Translation Manager module M 280 that is associated with substrate hardware device P 275. In addition, the System Manager module 290 maintains and uses additional information 296 regarding the network topology information for the provided virtual computer networks in this example, including to reflect the configured logical network topology information described with respect to FIG. 2C . One or more specified logical networking devices of entity Z's managed virtual computer network that are not physically implemented may further be configured as part of the network topology, but are not illustrated or explicitly managed in the example of FIG. 2D .
[0082] In the example of FIG. 2D , computing node A is sending a communication to computing node C, with computing nodes A and C being configured to belong to distinct logical subnets of the virtual computer network as previously discussed with respect to FIG. 2C , and with network device P being configured to act as the logical network node H firewall device 255b for communications passing between those logical subnets. The actions of the physically implemented manager modules 210 and 280 and devices of network 250 in actually sending the communication are shown, as well as the actions of network device P in facilitating the sending of the communication. While only a single intermediate destination logical network node is illustrated in FIG. 2D as being used in the routing path of the virtual computer network for inter-node communications between the two logical subnets, it will be appreciated that such a routing path may instead include 0 such intermediate network nodes (e.g., as discussed with respect to FIGS. 2A and 2B ) or more than 1 such intermediate network nodes in other situations, and that such intermediate network nodes may perform other types of actions in some situations.
[0083] Thus, in a manner similar to that described with respect to FIG. 2A , computing node A determines to send a communication to computing node C, and accordingly exchanges various messages 224 with Communication Manager module R 210. In particular, in this example, computing node A first sends a message request 224-a for virtual hardware address information for computing node C. However, unlike the example of FIG. 2A in which computing nodes A and G were part of the same logical subnet and did not include any intermediate logical network nodes in the routing path between computing nodes A and G for the virtual computer network, communications from computing node A to computing node C are configured to first pass through an initial intermediate logical network node H before being forwarded to computing node G. Accordingly, the information maintained by the System Manager module 290 for use in directing communications from computing node A to computing node C reflects that logical network node H is an initial intermediate destination for such communications, and that substrate network device P implements logical network node H.
[0084] Thus, Communication Manager module R intercepts the request 224-a, and obtains a hardware address to provide to computing node A as part of spoofed response message 224-b for use in directing the inter-node communication along the configured routing path, in a manner similar to that previously discussed. The Communication Manager module R may store various hardware address information as part of mapping information 212d, as discussed in greater detail with respect to FIG. 2E , and if so may already have stored hardware address information for use with communications from computing node A to computing node C. If not, however, Communication Manager module R performs one or more interactions 229 with the System Manager module 290 to obtain information from the module 290 corresponding to the indicated virtual network address for computing node C. Rather than providing the substrate network address corresponding to computing node C, however, as performed for computing node G in FIG. 2A , the System Manager module 290 instead indicates that the virtual network address for computing node C (at least for communications sent from computing node A) corresponds to the substrate network address for network device P as part of the substrate network routing path to computing node C, and may also provide information to the Communication Manager module R that indicates a hardware address to use to represent computing node C (at least for communications sent from computing node A). In particular, the System Manager module 290 uses the network topology information 296 to provide such requested information to communication manager modules and/or translation manager modules. The Communication Manager module R then stores the received information as part of mapping information 212d for future use, with the hardware address for computing node C being associated with the substrate network address for network device P (at least for communications sent from computing node A), and provides computing node A with the hardware address corresponding to computing node C as part of response message 224-b.
[0085] After receiving the response message 224-b from Communication Manager module R, computing node A creates and initiates the sending of a communication to computing node C, shown in FIG. 2D as communication 224-c. In particular, the header of communication 224-c includes a destination network address for destination computing node C that is “10.0.5.1”, a destination hardware address that is the virtual hardware address for computing node C provided to computing node A in message 224-b, a source network address for sending computing node A that is “10.0.0.2”, and a source hardware address for sending computing node A that is an actual or dummy hardware address that was previously identified to computing node A.
[0086] The outgoing communication 224-c is intercepted and handled by Communication Manager module R in a manner similar to that previously described with respect to FIGS. 2A and 2C . In particular, as with communication 220-c in FIG. 2A , Communication Manager module R intercepts the communication 224-c, modifies the communication as appropriate, and forwards the modified communication over the interconnection network 250 to network device P. To determine the substrate network address to be used for forwarding the modified communication over the interconnection network 250, Communication Manager module R extracts the destination virtual network address and destination virtual hardware address from the header of communication 224-c. After Communication Manager module R determines the actual substrate network address corresponding to network device P, it creates a new substrate network communication header that includes that actual substrate network address as the destination address, and similarly adds a source substrate network address for computing node A to the new header. The Communication Manager module R next creates a new communication 234-3 that is encoded for the substrate network by modifying communication 224-c so as to replace the prior IPv4 header with the new header (e.g., in accordance with SIIT), including populating the new header with other information as appropriate for the new communication (e.g., payload length, traffic class packet priority, etc.), and forwards communication 234-3 over the interconnection network 250. As discussed in greater detail with respect to FIG. 2B , in response to the request message 224-a and/or communication 224-c, the Communication Manager module R and/or the System Manager module 290 may further perform various optional authentication activities.
[0087] The interconnection network then uses the destination substrate network address of the communication 234-3 to route the communication to Translation Manager module M. When Translation Manager module M receives communication 234-3 via the interconnection network 250, it performs actions similar to those described in FIG. 2A with respect to communication 230-3 and Communication Manager module S, including to optionally perform interactions 244 with the System Manager module 290 to determine if the communication is authorized, to update mapping information 282d to reflect any new information about computing node A, to decode the received communication so that it is formatted in accordance with entity Z's managed virtual computer network (e.g., by modifying the communication to include an appropriate IPv4 header for the virtual computer network), and to provide the decoded modified communication as communication 278a to network device P as part of its logical network interface for the logical subnet to which computing node A belongs. However, the communication 278a provided to network device P includes information that indicates that computing node C is the final destination for the communication, such as for use by network device P in performing its firewall analysis. In particular, in this example, the communication 278a includes a destination hardware address that corresponds to network device P, but the destination network address is the virtual network address for computing node C. In addition, Translation Manager module M may further optionally modify the decoded communication 278a to include a VLAN identifier that represents entity Z's managed virtual computer network, as described in greater detail elsewhere.
[0088] When network device P receives communication 278a, it optionally performs various firewall-related activities for the communication, based on the configuration specified for logical network node H that it represents, and in this example determines to forward the communication on to its final destination of computing node C. As discussed in greater detail elsewhere, such intermediate destination logical network nodes via which some inter-node communications may be directed may provide a variety of other types of capabilities in other embodiments and situations. Furthermore, as noted elsewhere, network device P may in some such situations determine to modify the communication in one or more manners based on its firewall policies. In order to forward the communication on to computing node C, network device P updates the received communication 278a so that it has a new destination hardware address that corresponds to computing node C (optionally after performing interactions with Translation Manager module M to obtain the hardware address for computing node C's virtual network address, not shown, in a manner similar to that of communications 224-a and 224-b). The network device P then sends the modified communication as outgoing communication 278b, using its logical network interface for the logical subnet to which computing node C belongs.
[0089] In a manner similar to that previously discussed elsewhere, the outgoing communication 278b is intercepted and handled by Translation Manager module M. In particular, Translation Manager module M intercepts the communication 278b, encodes the communication for the substrate network by modifying the communication as appropriate, and forwards the modified communication over the interconnection network 250 to computing node C. To determine the substrate network address to be used for forwarding the modified communication over the interconnection network 250, Translation Manager module M extracts the destination virtual network address and destination virtual hardware address from the header of communication 278b. After Translation Manager module M determines the actual substrate network address corresponding to computing node C, it creates a new substrate network communication header that includes that actual substrate network address as the destination address, and similarly adds a source substrate network address for network device P to the new header. The Translation Manager module M next creates a new communication 234-6 by modifying communication 278b so as to replace the prior IPv4 header with the new substrate communication header (e.g., in accordance with SIIT), including populating the new header with other information as appropriate for the new communication (e.g., payload length, traffic class packet priority, etc.), and forwards communication 234-6 over the interconnection network 250.
[0090] The interconnection network then uses the destination substrate network address of the communication 234-6 to route the communication to Communication Manager module R. When Communication Manager module R receives communication 234-6 via the interconnection network 250, it performs actions similar to those previously described, including to optionally determine if the communication is authorized, to decode the communication for entity Z's managed virtual computer network by modifying the communication to include an appropriate IPv4 header for the overlay virtual computer network of entity Z, and to provide the modified communication as communication 224-h to computing node C.
[0091] In this manner, the CNS system may provide virtual networking functionality corresponding to the configured network topology, including to support intermediate destination logical network nodes along routing paths between particular computing nodes, and again without any special configuration of the computing nodes of the managed virtual computer network or of the physical networking devices of the intervening substrate interconnection network, based on communication manager modules and translation manager modules overlaying the virtual computer network on the actual interconnection network in a manner to emulate the configured network topology. In addition, since Translation Manager module M manages communications on behalf of substrate hardware device P (including to provide communications to and receive communications from substrate device P in a form specific to the managed virtual computer network of entity Z), substrate device P may in some embodiments be any of various commercially available network devices that are designed or configurable to support the networking protocol used by the managed virtual computer network, while in other embodiments substrate device P may have other forms. Furthermore, it will be appreciated that, while FIGS. 2C and 2D correspond to an example in which an intermediate destination logical network node is used for communications passing between two configured logical subnets of a provided overlay virtual computer network, intermediate destination logical network nodes may similarly be used in various other situations, as discussed in greater detail elsewhere.
[0092] FIG. 2E illustrates examples of portions of the mapping information 212d and 282d that may be used by the Communication Manager module R and Translation Manager module M, respectively, of FIG. 2D , with the example mapping information 212d and 282d corresponding to the example network topology information discussed with respect to FIG. 2C . Each of the groups of mapping information 212d and 282d include multiple entries, with each entry including information that has some similarities to a routing table entry.
[0093] In particular, in this example, mapping information 212d includes information for each entry that includes the following: a virtual computer network identifier 213a, which in this example is a network identifier corresponding to the overlay virtual computer network provided for entity Z; a source computing node interface identifier 213b, which in this example includes an “A” to correspond to the single logical network interface for computing node A and a “C” to correspond to the single logical network interface for computing node C; a destination virtual network address identifier 213c; an associated destination substrate network address 213d; and optionally various other information 213e. The optional other information may include, for example, a destination hardware address provided to associated computing nodes for use in representing particular destination computing nodes, information about expiration times or other use criteria for particular entries, etc.
[0094] Thus, in the example of FIG. 2D , when computing node A initiates the sending of a communication to computing node C via intermediate destination network device P, the sent communication includes the destination virtual network address of “10.0.5.1” for computing node C. In this example, assuming that optional entry 213z is not present, the entry 213y provides the best match for the indicated destination virtual network address, such as based on the use of longest prefix matching to select the entry that matches the destination network address and has the longest number of matching bits that are specified. The substrate network address for entry 213y in this example is “200.0.10.3”, corresponding to intermediate destination network device P to which the communication will be initially directed. Thus, entry 213y will be used for communications sent from computing node A to computing node C, and more generally to any computing node of logical subnet B (assuming that the computing nodes of logical subnet B all have virtual network addresses between “10.0.5.0” and “10.0.5.15”).
[0095] While not discussed with respect to FIG. 2D , it is further possible to configure more specific functionality with respect to particular computing nodes in some embodiments. For example, if communications from computing node A to computing node C are specifically configured to pass through network device P without the normal firewall handling that it would provide, thus effectively skipping network device P as an intermediate destination, the mapping information 212d may further optionally include the entry 213z for source computing node A and destination computing node C. If so, the example communication discussed with respect to FIG. 2D would instead cause the entry 213z to be selected, resulting in a substrate network address for computing node C of “200.0.0.3” being selected for use with the outgoing communication. Moreover, since Communication Manager module R manages both computing nodes A and C, in that example, the outgoing communication would be forwarded to computing node C by Communication Manager module R, without the communication ever being sent over the interconnection network 250.
[0096] The example mapping information 282d includes information similar to that displayed for mapping information 212d, and in particular includes information for each of its entries that includes the following: a virtual computer network identifier 214a, which in this example is a network identifier corresponding to the overlay virtual computer network provided for entity Z; a source computing node interface identifier 214b; a destination virtual network address identifier 214c; an associated destination substrate network address 214d; and optionally various other information 214e. The example mapping information 282d illustrates that different logical network interfaces of a logical network node may be configured to have different routing information, with the illustrated entries including information for both of the example logical network interfaces of logical network node H (with the logical identifier “H1” in column 214b corresponding to the logical network interface H1 213a of FIG. 2C , and with the logical identifier “H2” in column 214b corresponding to the logical network interface H2 213b of FIG. 2C ). For example, communications received on logical network interface H2 of logical network node H from logical subnet B may validly have final destinations that are on logical subnet A (such as computing node A with virtual network address “10.0.0.2” and computing node G with virtual network address “10.0.0.3”), while communications received on logical network interface H1 of logical network node H from logical subnet A may be configured to not validly have final destinations that are also on logical subnet A. Accordingly, in this example, an entry is included to indicate that any communication received on logical network interface H1 with a destination virtual network address in the range of “10.0.0.0/28” will generate an error, although in other embodiments such invalid entries may instead be represented without such explicit invalid entries (e.g., by not including any valid entries that do match such destination network addresses). It will be appreciated that such mapping information 212d and 282d may have various other forms and be represented in other manners in other embodiments.
[0097] In this manner, the CNS system may provide functionality corresponding to the use of intermediate destination logical network nodes within a substrate network, without any special configuration of the computing nodes of the managed virtual computer network or of the physical devices of the intervening substrate interconnection network, based on communication manager modules and translation manager modules overlaying the virtual computer network on the actual physical interconnection network in such a manner as to provide the desired functionality.
[0098] FIG. 2F includes information with some similarities to that of FIG. 2C , but illustrates an example alternative logical network topology of the overlay virtual computer network provided for entity Z. In particular, with respect to FIG. 2F , the provided overlay virtual computer network is illustrated as including one or more logical subnets 288c, and with those logical subnets being separated from external computer systems 289 by a chain of multiple intermediate destination logical network nodes of the provided overlay virtual computer network. In this example, the one or more logical subnets include computing nodes A, C and G, as well as optionally including other computing nodes 286C of entity Z's virtual computer network that were not illustrated in FIGS. 2A and 2B . In addition, this example logical network topology of the provided overlay virtual computer network includes logical network node H and logical network node I 255x (an additional example logical network node of the provided overlay virtual computer network that was not previously illustrated in FIGS. 2A-2D ) being configured to operate as intermediate destinations between the logical subnet(s) and external computer systems 289. In this example, logical network node H is configured to have two logical network interfaces 213 in this example, including a first logical network interface H3 213c that corresponds to the logical subnet(s) of the provided overlay virtual computer network, and a second logical network interface H4 213d that is configured in this example to support only communications with logical network node I. Logical network node I is similarly configured in this example to have two logical network interfaces 213, including a first logical network interface H5 213e that is configured in this example to support only communications with logical network node H, and a second logical network interface H6 213f that corresponds to communications from one or more edge modules 287 for a first geographical location 294 that includes the computing nodes of the provided overlay virtual computer network and the edge modules (e.g., at a first data center).
[0099] Thus, if one of the computing nodes in the logical subnet(s) of the provided overlay virtual computer network sends a communication to one of the external computer systems 289, which are at one or more other geographical locations distinct from the first geographical location 294, the sent communication will be directed first to logical network interface H3 of logical network node H, to enable logical network node H to perform configured firewall-related activities for the communication. Assuming that logical network node H forwards the communication on, it will be sent from logical network interface H4 of logical network node H to logical network interface H5 of logical network node I, to enable logical network node I to perform configured VPN-related activities for the communication in this example—in particular, the particular destination external computer system in this example may be at a remote location that includes one or more computing systems under control of entity Z that are configured to interoperate with the provided overlay virtual computer network, including to maintain a VPN connection between the locations. Accordingly, other communications sent to other external computer system destinations that are not accessible via the VPN connection may be passed on by logical network node I without modification, or those other communications may instead be configured to use a different routing path through the logical network topology of the provided overlay virtual computer network that does not include logical network node I. In this example, the resulting communication is then passed from logical network interface H6 of logical network node I to one of the edge modules 287, which will perform activities to forward the communication on to the indicated destination external computer system 289, including to optionally perform activities analogous to those of a communication manager module to decode the communication that it receives in a form specific to a substrate network at the first geographical location 294, as discussed in greater detail elsewhere. It will be appreciated that communications sent from the external computer systems 289 to computing nodes of the provided overlay virtual computer network may pass in through the edge modules 287, logical network node I and logical network node H in the reverse manner to that previously described.
[0100] Various other types of actions than those discussed with respect to FIGS. 2A-2F may be performed in other embodiments, including for types of network addressing protocols other than IPv4 and/or IPv6.
[0101] In some embodiments, one or more modules of the configurable network service may further be configured to perform one or more additional types of functionality in at least some situations, such as by the multiple translation manager modules in a distributed manner, optionally in conjunction with multiple communication manager modules and/or the system manager module. As one example, the one or more modules may be configured in at least some embodiments to perform metering or other tracking of the use of one or more substrate devices selected to operate as one or more logical network nodes of a managed virtual computer network (e.g., as logical network nodes that operate as intermediate destinations for communications), and to provide information about such tracking for various purposes (e.g., to enable fees to be charged to a client associated with the managed virtual computer network if the corresponding tracked activities are fee-based activities; to provide information to a client associated with the managed virtual computer network and/or to another entity regarding an amount of use of one or more intermediate destination computing nodes, such as to enable corresponding monitoring activities; etc.). As another example, the one or more modules may be configured in at least some embodiments to filter at least some communications forwarded to and/or from one or more substrate devices selected to operate as one or more logical network nodes of a managed virtual computer network, including to limit the rate or total quantity of such communications to be below a specified or determined threshold of use—such rate/quantity limiting or other filtering may be configured in various manners, such as based on configuration information received by a client associated with the managed virtual computer network (e.g., to limit use of a fee-based feature of the managed virtual computer network, to correspond to limitations of the one or more logical network nodes and/or of other nodes or networking components associated with the logical network nodes, etc.), based on a capacity or other aspects of the selected substrate device; etc. The one or more modules may further be configured to filter communications received from one or more substrate devices selected to operate as one or more logical network nodes of a managed virtual computer network in at least some embodiments, such as to ensure that the communications are authorized for or otherwise allowed for the managed virtual computer network before those communications are provided to one of the computing nodes of the managed virtual computer network. In addition, the one or more modules may be configured in at least some embodiments to perform signaling activities if the unavailability of a particular logical network node and/or associated selected substrate device is detected (e.g., based on the selected substrate device failing or on a communication link to the selected substrate device failing, and as may be detected based on a lack of response or other information from the logical network node and/or selected substrate device for a period of time or to one or more forwarded communications or other messages), such as to notify other computing nodes of the managed virtual computer network of the unavailability to inhibit future communications from being forwarded to the logical network node while it is unavailable (e.g., until another substrate device may be selected and optionally configured to operate as the logical network node), as well as to optionally perform other related activities (e.g., to initiate providing a replacement for the unavailable logical network node and/or associated selected substrate device).
[0102] In addition, as previously noted, configuration information that is specified for a virtual computer network may include various network topology information, various computing nodes may be selected for the virtual computer network and configured in accordance with the network topology in various manners, and various substrate devices may be selected to represent logical network devices for the virtual computer network and configured in accordance with the network topology in various manners. For example, in some embodiments, the selection of a computing node and/or substrate device to be used in a managed virtual computer network and/or to be assigned a particular role in a configured network topology may be based at least in part on a geographical and/or network location of the computing node or substrate device, such as an absolute location, or instead a location relative to one or more other computing resources of interest (e.g., other computing nodes of the same managed virtual computer network, storage resources to be used by the computing node or substrate device, etc.), such as within a minimum and/or maximum specified geographical distance or other degree of proximity to an indicated other computing resource or other location. In addition, in some embodiments, factors used when selecting a computing node and/or substrate device may be not be based on location, such as to include one or more of the following: constraints related to capabilities of a computing node or substrate device, such as resource-related criteria (e.g., an amount of memory, an amount of processor usage, an amount of network bandwidth, and/or an amount of disk space), and/or specialized capabilities available only on a subset of available computing nodes or substrate devices; constraints related to costs, such as based on fees or operating costs associated with use of particular computing nodes or substrate devices; etc.
[0103] As previously noted, in some embodiments, a program execution service executes third-party customers' programs using multiple physical computing systems (e.g., in one or more data centers) that each host multiple virtual machines, with each virtual machine being able to execute one or more programs for a customer. In some such embodiments, customers may provide programs to be executed to the program execution service, and may reserve execution time and other resources on physical or virtual hardware facilities provided by the program execution service. In addition, customers and/or the program execution service may define virtual computer networks that will be used by the program execution service for computing nodes of the customer, so as to transparently provide computing nodes of a virtual computer network with the appearance of operating on a dedicated physical network.
[0104] In addition, the CNS system may in at least some embodiments establish and/or maintain virtual computer networks via the operation of one or more communication manager modules and/or translation manager modules at the edge of one or more intermediate physical networks, such as by configuring and otherwise managing communications for the virtual computer networks. In some situations, a communication manager module tracks or otherwise determines the virtual computer networks to which the module's associated computing nodes belong (e.g., based on entities on whose behalf the virtual computer networks operate) as part of managing the communications for the virtual computer networks, and a translation manager module tracks or otherwise determines the virtual computer networks to which the logical network nodes represented by the module's associated substrate devices belong as part of managing the communications for the virtual computer networks. The determination by a communication manager module of a corresponding virtual computer network for an associated computing node and/or the determination by a translation manager module of a corresponding virtual computer network for an associated substrate device may be performed in various ways in various embodiments, such as by interacting with a system manager module that provides that information, by tracking software modules or other programs executing on such computing nodes or substrate devices, by tracking entities associated with such computing nodes, etc. For example, when a particular computing node begins to execute one or more software programs on behalf of a user, and that user also has other software programs executing on other computing nodes, the new computing node executing the user's program(s) may be selected to be associated with a virtual computer network for the user that includes those other computing nodes. Alternatively, a user or other entity may specify a particular managed computer network to which a computing node belongs, such as if the entity maintains multiple distinct managed computer networks between different groups of computing nodes. In addition, in at least some embodiments, one or more system manager modules of the CNS system may facilitate configuring communications between computing nodes, such as by tracking and/or managing which computing nodes belong to which virtual computer networks (e.g., based on executing programs on behalf of a customer or other entity), by tracking and/or managing which substrate devices operate to implement logical network devices of virtual computer networks, and by providing information about actual substrate network addresses that correspond to virtual network addresses used for a particular virtual computer network (e.g., by a particular customer or other entity).
[0105] FIG. 3 is a block diagram illustrating example computing systems suitable for executing an embodiment of a system for managing communications between computing nodes. In particular, FIG. 3 illustrates a group 399 of computing systems and inter-network(s), such as a data center or other group of co-located computing nodes. In some embodiments, some or all of the computing systems of the group 399 may be used by an embodiment of the CNS system to provide managed virtual computer networks to users or other entities. The example group 399 includes a server computing system 300, a host computing system 350 capable of executing one or more virtual machines, other host computing systems 390 that are similar to host computing system 350, one or more network devices 370 that are available for use in implementing logical network nodes for managed computer networks, and an optional Communication Manager module 360 that manages host computing systems 390 and that executes on one of the computing systems 390 or on another computing system (not shown). The server computing system 300, host computing systems 350 and 390, and network devices 370 are connected to one another via an internal network 380, which includes a networking device 362 and other networking devices (not shown). The network 380 may be an interconnection network that joins multiple disparate physical networks (not shown) for the group 399 and possibly provides access to external networks (not shown) and/or systems, such as other computing systems 395. In the illustrated example, the networking device 362 provides a gateway from the network 380 to the host computing systems 350 and 390 and the network devices 370. In some embodiments, networking device 362 may, for example, be a router or a bridge. In addition, in this example, one or more edge module devices 365 may be used to connect the internal network 380 at the location 399 to external computer systems at other locations.
[0106] The computing system 300 in this example operates to configure and manage virtual computer networks within the group 399, as well as to provide other functions (e.g., the provisioning, initialization, and execution of programs on computing nodes). The computing system 300 includes a CPU 305, various I/O components 310, storage 330, and memory 320. The I/O components include a display 311, network connection 312, computer-readable media drive 313, and other I/O devices 315 (e.g., a mouse, keyboard, speakers, etc.).
[0107] The host computing system 350 operates to host one or more virtual machines, such as for use as computing nodes in managed virtual computer networks (e.g., computing nodes that execute programs on behalf of various users). The host computing system 350 includes a CPU 352, various I/O components 353, storage 351, and memory 355. While not illustrated here, the I/O components 353 may include similar components to those of I/O components 310. A virtual machine Communication Manager module 356 and one or more virtual machines 358 are executing in the memory 355, with the module 356 managing communications for the associated virtual machine computing nodes 358 and in some embodiments including various software instructions that when executed program the CPU 352 to provide the described functionality. The Communication Manager module 356 maintains various mapping information 354 on storage related to the computing nodes 358 and other computing nodes, such as in a manner similar to mapping information 212a, 212d, 262a and 262d of FIGS. 2A-2F . The structure of the other host computing systems 390 may be similar to that of host computing system 350, or instead some or all of the host computing systems 350 and 390 may act directly as computing nodes by executing programs without using hosted virtual machines. In a typical arrangement, the group 399 may include hundreds or thousands of host computing systems such as those illustrated here, organized into a large number of distinct physical sub-networks and/or networks.
[0108] The network devices 370 may each be designed to or otherwise configured to provide one or more types of specialized functionality related to handling network communications or otherwise providing networking functionality, as discussed in greater detail elsewhere. When the CNS system provides one or more managed virtual computer networks using systems and devices of the group 399, the CNS system may determine in some situations and embodiments to use particular network devices 370 to support those managed virtual computer networks, such as to represent specified logical network nodes of particular managed computer networks that are used as intermediate destinations for particular network communications for those managed virtual computer networks.
[0109] An embodiment of a CNS system 340 is executing in memory 320 of the computing system 300. In some embodiments, the system 340 may receive an indication of multiple computing nodes to be used as part of a managed virtual computer network (e.g., one or more virtual machine computing nodes on host computing system 350 or one or more computing nodes using one of the host computing systems 390), and in some situations may select the particular computing node(s) for the managed virtual computer network. In addition, in some embodiments, the system 340 may support particular managed virtual computer networks that have specified logical network nodes by selecting and optional configuring particular network devices 370 to represent particular such logical network nodes, such as in accordance with particular configuration information received for those virtual computer networks. In some cases, information about the structure and/or membership of various managed virtual computer networks may be stored in the provisioning database 332 on storage 330 by the system 340, and provided to communication manager modules and/or translation manager modules at various times. Similarly, in some cases, information about configured network topology information for one or more managed virtual computer networks, including information about intermediate destination logical network nodes for the one or more managed virtual computer networks and corresponding hardware devices, may be stored in the database 334 on storage 330 by the system 340, such as in a manner similar to information 296 of FIG. 2D , and used to provide corresponding information to communication manager modules and/or translation manager modules at various times. In this example, the system 340 in memory 320 includes a system manager module 342 and optionally other modules 344, with the communication manager modules 356 and 360 and other translation manager modules (not shown) being a further part of the distributed CNS system in this example. The system module 342 performs operations to facilitate the use of intermediate destination logical network nodes for managed computer networks, as discussed elsewhere. In addition, the CNS system and the modules 342 and 344 may each in some embodiments include various software instructions that when executed program the CPU 305 to provide described functionality, and the translation manager modules (not shown) may similarly in some embodiments include various software instructions that when executed program one or more processors to provide described functionality.
[0110] As discussed in greater detail elsewhere, the Communication Manager modules 356 and 360 (and other Communication Manager modules, not shown, that manage other associated computing nodes, not shown), various translation manager modules (not shown), and the other various modules 342 and 344 of the system 340 may interact in various ways to manage communications between computing nodes, including to select and use particular intermediate destination logical network nodes for particular communications of provided virtual computer networks. Such interactions may, for example, enable the computing nodes 358 and/or other computing nodes to inter-communicate over managed virtual computer networks without any special configuration of the computing nodes, by overlaying the virtual computer networks over network 380 and optionally one or more external networks (not shown) without any special configuration of networking device 362 or other networking devices (not shown), and without encapsulation of communications.
[0111] It will be appreciated that computing systems 300, 350, 390, and 395, edge devices 365, substrate network devices 370, and networking device 362, are merely illustrative and are not intended to limit the scope of the present invention. For example, computing systems 300 and/or 350 may be connected to other devices that are not illustrated, including through one or more networks external to the group 399, such as the Internet or via the World Wide Web (“Web”). More generally, a computing node, other computing system, or substrate network device or other substrate hardware device may comprise any combination of hardware or software that can interact and perform the described types of functionality, including without limitation desktop or other computers, database servers, network storage devices and other network devices, PDAs, cellphones, wireless phones, pagers, electronic organizers, Internet appliances, television-based systems (e.g., using set-top boxes and/or personal/digital video recorders), and various other consumer products that include appropriate communication capabilities. In addition, the functionality provided by the illustrated modules may in some embodiments be combined in fewer modules or distributed in additional modules, such as if the functionality of a system manager module and one or more communication manager modules are instead combined into a single module. Similarly, in some embodiments the functionality of some of the illustrated modules may not be provided and/or other additional functionality may be available.
[0112] It will also be appreciated that, while various items are illustrated as being stored in memory or on storage while being used, these items or portions of them may be transferred between memory and other storage devices for purposes of memory management and data integrity. Alternatively, in other embodiments some or all of the software modules and/or systems may execute in memory on another device and communicate with the illustrated computing systems via inter-computer communication. Furthermore, in some embodiments, some or all of the systems and/or modules may be implemented or provided in other manners, such as at least partially in firmware and/or hardware, including, but not limited to, one or more application-specific integrated circuits (ASICs), standard integrated circuits, controllers (e.g., by executing appropriate instructions, and including microcontrollers and/or embedded controllers), field-programmable gate arrays (FPGAs), complex programmable logic devices (CPLDs), etc. Some or all of the modules, systems and data structures may also be stored (e.g., as software instructions or structured data) on a non-transitory computer-readable storage medium, such as a hard disk, a memory, or a portable media article to be read by an appropriate drive or via an appropriate connection. The systems, modules and data structures may also be transmitted in some embodiments as generated data signals (e.g., as part of a carrier wave or other analog or digital propagated signal) on a variety of computer-readable transmission mediums, including wireless-based and wired/cable-based mediums, and may take a variety of forms (e.g., as part of a single or multiplexed analog signal, or as multiple discrete digital packets or frames). Such computer program products may also take other forms in other embodiments. Accordingly, the present invention may be practiced with other computer system configurations.
[0113] FIG. 4 is a flowchart of an example embodiment of a System Manager routine 400. The routine may be provided by, for example, execution of the system manager module 110 of FIGS. 1A and/or 1B, the system manager module 290 of FIGS. 2A-2F , and/or the system manager module 342 of CNS system 340 of FIG. 3 , such as to assist in managing communications between multiple computing nodes across one or more intermediate networks, including to manage communications using intermediate destination logical network nodes for managed computer networks that are provided, as well as to perform other types of management operations in some situations. In at least some embodiments, the routine may be provided as part of a system that manages communications for multiple different entities across a common intermediate substrate network, with the communications configured so as to enable each computing node to transparently communicate with other associated computing nodes using a private virtual computer network that is specific to that entity. Furthermore, the routine may facilitate preventing unauthorized communications from being provided to destination computing nodes, such as by assisting Communication Manager modules with determinations of whether communications are authorized.
[0114] In the illustrated embodiment, the routine begins at block 405, where a request is received. The routine continues to block 410 to determine the type of request. If it is determined that the type of request is to associate one or more computing nodes with a particular managed virtual computer network provided for an indicated entity, such as if those computing nodes are executing one or more programs on behalf of that entity or are to execute one or more programs on behalf of that entity, the routine continues to block 415 to associate those computing nodes with that indicated entity and virtual computer network. In some embodiments, the routine may further determine the one or more computing nodes to be associated with the indicated entity and virtual computer network, such as based on information provided by the indicated entity, while in other embodiments the selection of such computing nodes and/or execution of appropriate programs on those computing nodes may be performed in other ways. In addition, as discussed in greater detail elsewhere, in some embodiments one or more of the computing nodes may each be a virtual machine that is hosted by one or more physical computing systems. The routine then continues to block 420 to store mapping information for the computing nodes and the managed virtual computer network. In particular, in the illustrated embodiment the routine stores for each computing node an indication of a physical substrate network address corresponding to the computing node, a virtual network address used by the entity for the computing node as part of the virtual computer network, optionally a virtual hardware address assigned to the computing node, and an indication of the associated entity. As discussed in greater detail elsewhere, the physical substrate network address corresponding to the computing node may in some embodiments be a substrate network address specific to that single computing node, while in other embodiments may instead refer to a sub-network or other group of multiple computing nodes, such as may be managed by an associated Communication Manager module. In addition, as discussed in greater detail with respect to blocks 460-470, at least some managed virtual computer networks may have a configured network topology that specifies one or more logical network nodes of the managed virtual computer network that act as intermediate destinations for at least some communications involving one or more computing nodes of the managed virtual computer network—if so, the information stored for each computing node may further indicate at least a first intermediate destination logical network node to be used for communications sent from one or more source computing nodes to the computing node, along with information about one or more corresponding substrate devices that represent the intermediate destination logical network nodes, as discussed in greater detail with respect to blocks 460-470. After block 420, the routine continues to block 422 to optionally provide information about the computing nodes and their configuration to one or more communication manager modules associated with those computing nodes, although in other embodiments instead provides such information upon request from the communication manager modules.
[0115] If it is instead determined in block 410 that the received request is to configure information regarding network topology for a managed virtual computer network, such as to indicate one or more specified logical network nodes that will act as intermediate destinations for at least some communications involving one or more computing nodes of the managed virtual computer network, the routine continues to block 460. In block 460, the routine obtains and stores information about the configured logical network topology for the managed virtual computer network, including to optionally identify particular specified logical network nodes of the managed virtual computer network to use as intermediate destinations for communications between particular computing nodes of the managed virtual computer network and/or external computer systems that are not part of the managed virtual computer network. After block 460, the routine continues to block 465 to determine if any such intermediate logical network nodes are specified, and if so continues to block 470. In block 470, the routine selects and optionally configures one or more substrate hardware devices for each such intermediate logical network node to act as that intermediate logical network node, such as by providing one or more types of functionality specified for that intermediate logical network node. In addition, while not illustrated in FIG. 4 , the routine may optionally provide information about the intermediate destination logical network nodes and/or corresponding substrate network devices to one or more communication manager modules whose outgoing communications may use those intermediate destination logical network nodes, although in other embodiments the routine instead provides such information upon request from the communication manager modules.
[0116] If it is instead determined in block 410 that the type of received request is a request for address resolution for a virtual network address of a target computing node or other computer system of interest, such as from a communication manager module on behalf of a managed computing node that may send communications to that target, the routine continues instead to block 425, where it determines whether the request is authorized in one or more ways, such as based on whether the managed computing node on whose behalf the request is made is authorized to send communications to the target whose virtual network address resolution is requested (e.g., based on the virtual computer network(s) to which the two computing nodes belong), based on whether the managed computing node on whose behalf the request is made is a valid computing node that is currently part of a configured virtual computer network, and/or based on whether the request is received from the communication manager module that actually manages the indicated computing node on whose behalf the request is made. If the request is determined to be authorized, the routine continues to block 430, where it obtains a network address of interest for a particular target of interest, such as may be included with the request received in block 405, or previously stored and currently identifiable for the target based on other received information. The routine then continues to block 435 to retrieve stored information for the target that is associated with the network address, and in particular to retrieve information that associates that target network address to a physical substrate network address for a network location that corresponds to the target, such as may be previously stored with respect to blocks 420, 460 and/or 470, and optionally to other information for the target network address (e.g., an associated virtual hardware address, an indication regarding whether the target network address corresponds to a physically implemented computing node with an actual substrate network address or instead to a logical networking device that does not have an actual substrate network address, information about a role or status of the device corresponding to the virtual network address with respect to configured network topology information, whether communications to the target network address will use one or more intermediate logical network node destinations, etc.). If communications from the computing node on whose behalf the request is made to the indicated target are to be routed via one or more intermediate logical network nodes, the information that is provided may in part correspond to a first of those intermediate logical network nodes, such as to include the virtual computer network address of that first intermediate logical network node and/or an actual substrate network address of a first substrate device that implements or otherwise represents that first intermediate logical network node (whether instead of or in addition to the actual substrate network address for the indicated computing node). After block 435, the routine continues to 440 to provide an indication of the retrieved information to the requester. While not illustrated here, if the determination in block 425 determines that the request is not authorized, the routine may instead not perform blocks 430-440 for that request, such as by responding with an error message to the request received in block 405 or not responding to that received request. In addition, in other embodiments the routine may perform one or more other tests to validate a received request before responding with the requested information, such as to verify that the computing node that initiated the request is authorized to receive that information.
[0117] If it is instead determined in block 410 that the received request is of another type, the routine continues instead to block 485 to perform one or more other indicated operations as appropriate. For example, in some embodiments, the routine may receive requests to update stored information about particular computing nodes, such as if a particular computing node was previously associated with a particular entity and/or virtual computer network but that association ends (e.g., one or more programs being executed for that entity on that computing node are terminated, the computing node fails or otherwise becomes unavailable, an associated user or other client changes specified configuration information for the computing node, etc.). Similarly, in some embodiments, the routine may receive requests to update stored information about particular intermediate destination logical network nodes or otherwise about configured network topology for a particular virtual computer network, such as to add or remove particular intermediate destination logical network nodes, change network addresses or other information associated with particular intermediate destination logical network nodes, etc. The routine may also perform a variety of other actions related to managing a system of multiple computing nodes, as discussed in greater detail elsewhere, and may at times perform actions of other types, such as to perform occasional housekeeping operations to review and update stored information as appropriate (e.g., after predefined periods of time have expired). In addition, if possible validation problems are detected, such as with respect to received address resolution requests for virtual network addresses, the routine may take various actions to signal an error and/or perform other corresponding actions as appropriate.
[0118] After blocks 422, 440, 470 or 485, or if it is instead determined in block 465 that no intermediate logical network nodes are specified, the routine continues to block 495 to determine whether to continue, such as until an explicit indication to terminate is received. If it is determined to continue, the routine returns to block 405, and if not continues to block 499 and ends.
[0119] FIGS. 5A-5B are a flow diagram of an example embodiment of a Communication Manager routine 500. The routine may be provided by, for example, execution of the Communication Manager modules 109a, 109b, 109c, 109d and/or 150 of FIG. 1B , the Communication Manager modules 210 and/or 260 of FIGS. 2A-2F , the Communication Manager modules 356 and/or 360 of FIG. 3 , and/or a communication manager module (not shown) of the CNS service 105 of FIG. 1A , such as to manage communications to and from an associated group of one or more computing nodes in order to provide a private virtual computer network over one or more shared intermediate networks, including to determine whether to authorize communications to and/or from the managed computing nodes, and to support use of intermediate destination logical network nodes for at least some communications to and/or from computing nodes of one or more managed virtual computer networks.
[0120] The routine begins at block 505, where an indication is received of a node communication or other message. The routine continues to block 510 to determine the type of communication or other message and proceed accordingly. If it is determined in block 510 that the message is a request from an associated managed computing node for network address resolution, such as an ARP request, the routine continues to block 515 to identify the target network address of interest indicated in the request. The routine then continues to block 520 to send a request to a system manager module for network address resolution for the indicated target network address for the virtual computer network that is associated with the computing node that provided the request, such as discussed with respect to blocks 425-440 of FIG. 4 . As discussed in greater detail elsewhere, the routine may in some embodiments track information about a virtual computer network and/or entity associated with each managed computing node, as well as intermediate destination logical network nodes of a virtual computer network and corresponding substrate hardware devices, while in other embodiments at least some such information may instead be provided to the routine by the computing nodes and/or by the system manager module, or instead the system manager module may track and store that information without it being provided to and tracked by the current routine. While not illustrated here, in other embodiments and situations such address resolution requests may be handled in other manners. In addition, while in the illustrated embodiment the received request is a request to provide a computing node's link-layer hardware address that corresponds to an indicated networking layer address, in other embodiments the address resolution request may have other forms, or computing nodes may request other types of information about computing nodes that have indicated target network addresses.
[0121] In the illustrated embodiment, the routine next continues to block 525 to receive a response from the system manager module that includes a substrate network address and/or other information corresponding to the identified virtual network address, and stores information locally that maps that substrate network address and/or other information to a unique hardware address for later use by the routine (e.g., based on a dummy virtual hardware address generated by the routine or provided in the response), along with other information about the target destination as discussed in greater detail elsewhere. The routine then provides the hardware address to the requesting computing node, which it may use as part of one or more later communications that it sends to the target destination with the indicated target network address. As discussed in greater detail elsewhere, the substrate network address response that is provided may in some embodiments include a substrate network address that is specific to the target destination of interest, while in other embodiments the substrate network address may correspond to an intermediate logical network node of the virtual computer network via which communications to the target destination will be passed for some or all sending computing nodes (e.g., the substrate network address of a substrate network device that represents the intermediate logical network node), or may instead correspond to a sub-network or other group of multiple computing nodes to which the indicated computing node belongs, such as to correspond to another communication manager module that manages those other computing nodes. If only some inter-node communications to the target destination will be passed through a particular intermediate logical network node, such as for only some sending computing nodes, it will be appreciated that the routine may obtain and store multiple entries for the target destination, such as to include different information to use for different sending computing nodes that initiate inter-node communications to the target destination. The routine next continues to block 530 to determine if blocks 515-525 were performed as part of the handling of an outgoing node communication, as discussed with respect to blocks 540-560, and if so, continues to block 550. While not illustrated here, in some embodiments the routine may instead receive an error response from the system manager module (e.g., based on the requesting computing node not being authorized to communicate with the indicated destination computing node) or no response, and if so may not send any response to the requesting computing node or may send a corresponding error message to that computing node.
[0122] If it is instead determined in block 510 that the type of communication or other message is an outgoing node communication from a computing node managed by the routine to another indicated target final destination that is not a computing node managed by the routine, the routine continues to block 540 to identify the indicated hardware address for the indicated target final destination from the communication header. In block 545, the routine then determines whether that destination hardware address is a hardware address previously mapped to a substrate network address corresponding to the final destination, such as previously discussed with respect to block 525. If not, in some embodiments the routine continues to block 515 to perform blocks 515-525 to determine such a corresponding substrate network address for the outgoing node communication, while in other embodiments such actions are not performed (e.g., if the indicated hardware address is not a mapped address, the routine may cause the outgoing node communication to fail, such as with an error message back to the sending node; if the indicated hardware address is not mapped but the destination network address is an external address, to proceed to perform blocks 550-560; etc.).
[0123] If the indicated hardware address is a mapped address, or the check is not performed, the routine continues to block 550 to retrieve the substrate network address that is mapped to the destination hardware address. As discussed in greater detail elsewhere, if the communication is to be directed to one or more intermediate destination logical network nodes along a routing path to the final destination, the substrate network address that is used may correspond to a first such intermediate destination logical network node as an initial destination, such as the substrate network address for a selected substrate device that represents that intermediate destination logical network node. Similarly, if the communication is to be directed to a final destination that is an external computer system at a remote location, and there are not any logical network nodes of the virtual computer network that are configured to act as intermediate destinations along a routing path to the final destination, the substrate network address that is used may correspond to an edge module or similar device at the current location that will act as an initial destination to facilitate forwarding the communication on to the final destination at another location. In addition, as discussed in greater detail elsewhere, the retrieval of the substrate network address to use may include using locally stored mapping information, such as based on a longest prefix match to various entries in the stored mapping information.
[0124] In block 555, the routine next rewrites the communication header in accordance with a networking address protocol for one or more intermediate substrate networks between the sending and destination computing nodes using the substrate network address retrieved in block 550. The header re-writing may further include changing other information in the new header, including changing a virtual network address for the sending computing node to be a corresponding substrate network address, and in at least some embodiments includes modifying the received communication without encapsulation as part of an overlay of the virtual computer network over the one or more intermediate substrate networks. Furthermore, for a communication whose destination hardware address corresponds to a logical networking device, the routine in block 555 may further perform other modifications that correspond to providing logical networking functionality to emulate the actions and functionality that would be performed by the one or more logical networking devices that would be used to forward the communication to the destination computing node in accordance with the configured network topology for the virtual computer network. In block 560, the routine then facilitates providing of the modified outgoing communication to the final destination, such as by initiating forwarding of the modified outgoing communication over the substrate intermediate network(s) to the final destination, optionally via one or more intermediate destination logical network nodes. While not illustrated here, in other embodiments various additional types of processing may be performed for outgoing node communications, such as to verify that the communications are valid or otherwise authorized in various ways (e.g., to verify that the sending computing node is authorized to send communications to the destination computing node, such as based on being associated with the same entity or part of the same virtual computer network, based on the sending and destination computing nodes being associated with different entities that are authorized to inter-communicate, based on the type of communication or other information specific to the communication, etc.). In addition, while not illustrated in this example, in some embodiments incoming communications that are from external computer systems at other locations may further be received by an edge device or other edge module in order to encode those communications for forwarding over the substrate networks to their destination computing nodes, and may be handled by the edge module in a manner similar to that previously described with respect to blocks 550-560.
[0125] If it is instead determined in block 510 that the received message is an incoming node communication for one of the managed computing nodes from a source that is not managed by the same communication manager module, the routine continues to block 565 to identify the substrate network addresses for the sending and destination computing nodes from the communication header. After block 565, the routine continues to block 570 to optionally verify that the incoming communication is valid in one or more ways. For example, the routine may determine whether the substrate network address for the sending computing node is actually mapped to a computing node that corresponds to the source substrate network address location, such as based on interactions with a system manager module and/or based on other information previously obtained and stored by the routine. In addition, the routine may determine whether the substrate network address for the destination computing node corresponds to an actual managed computing node. While not illustrated here, if an incoming communication is determined to not be valid, the routine may take various actions not shown, such as to generate one or more errors and perform associated processing and/or drop the incoming communication without forwarding it to the indicated destination node. For example, if the incoming communication indicates a destination network address that does not correspond to a current managed computing node, the routine may drop the incoming communication and/or initiate an error message, although in some embodiments such error messages are not sent to the sending computing node.
[0126] In the illustrated embodiment, after block 570, the routine continues to block 575 to retrieve the hardware address and the virtual network address that are mapped to the destination substrate network address, and to rewrite the communication header for the virtual computer network so that it appears to be sent to a computing node with that virtual network address and hardware address. For example, in some embodiments the destination virtual network address may be obtained from the destination substrate network address itself, such as from a subset of the bits of the destination substrate network address. In addition, the destination hardware address may have previously been mapped to the destination substrate network address, such as previously discussed with respect to block 525. In situations in which such prior mapping has not occurred, the routine may instead perform blocks 515-525 to obtain such information, although such actions are not illustrated in this example embodiment. The routine may similarly rewrite the communication header for the virtual computer network so that it appears to be sent from a computing node with a source virtual network address and source hardware address corresponding to the sending computing node. Furthermore, in at least some embodiments, the routine in block 575 may further perform other modifications to the incoming communication that correspond to providing logical networking functionality to emulate the actions and functionality that would be performed by one or more logical networking devices that would have been used to forward the communication to the destination computing node in accordance with the configured network topology for the virtual computer network. After block 575, the routine continues to block 580 to facilitate providing of the modified incoming communication to the destination computing node, such as by initiating forwarding of the modified incoming communication to the destination node. In addition, while not illustrated in this example, in some embodiments outgoing communications that are from a source computing node of a virtual computer network to one or more final destination external computer systems at other locations may further be received by an edge device or other edge module in order to decode those communications before forwarding the communications to their final destinations, and may be handled by such an edge module in a manner similar to that previously described with respect to blocks 565-580.
[0127] If it is instead determined in block 510 that a message of another type is received, the routine continues to block 585 to perform one or more other indicated operations as appropriate, such as to store information about entities associated with particular computing nodes, store configuration information about intermediate destination logical network nodes and their corresponding substrate hardware devices for particular virtual computer networks, store configuration information about other network topology information for particular virtual computer networks, respond to requests and other messages from computing nodes in a manner to provide logical networking functionality corresponding to configured network topologies for virtual computer networks (e.g., by emulating actions and other functionalities that would be performed by specified logical networking devices if they were physically implemented), update previously mapped or stored information to reflect changes with respect to computing nodes that are being managed or to remote computing nodes, perform operations to forward communications between multiple managed computing nodes of the communication manager module without forwarding such communications over the substrate network, etc. The storing and/or updating of stored information may be initiated in various manners, such as by receiving information in response to previous requests, periodically requesting such information, receiving information that is proactively pushed to the routine without a corresponding request, etc.
[0128] After blocks 560, 580 or 585, or if it is instead determined in block 530 that the processing is not being performed with respect to an outgoing communication, the routine continues to block 595 to determine whether to continue, such as until an explicit indication to terminate is received. If it is determined to continue, the routine returns to block 505, and if not continues to block 599 and ends.
[0129] FIGS. 6A-6B are a flow diagram of an example embodiment of a Translation Manager routine 600. The routine may be provided by, for example, execution of translation manager modules of FIGS. 1A and/or 1B that are associated with the substrate network devices 190, the translation manager module(s) 280 of FIG. 2D , and/or translation manager modules of FIG. 3 that are associated with the network devices 370, such as to manage communications to and from one or more associated substrate network devices that implement functionality corresponding to one or more specified logical network devices of one or more managed virtual computer networks.
[0130] The routine begins at block 605, where an indication is received of a communication sent from and/or to a computing node of a managed computer network or of another message. The routine continues to block 610 to determine the type of communication or other message and proceed accordingly. If it is determined in block 610 that the received message is an incoming node communication for an associated substrate network device that represents a logical network node of a managed computer network, with the substrate network device acting as an intermediate destination for the communication, and with the communication being intended for a distinct final destination and being encoded in a manner specific to the substrate network, the routine continues to block 665. In block 665, the routine identifies the substrate network addresses for the sending computing node and intermediate destination substrate network device from the communication header, and to determine virtual network addresses for the sending computing node and the intended final destination. As discussed in greater detail elsewhere, the virtual network addresses may be determined in various manners, such as to in some embodiments be stored in the header of the communication. After block 665, the routine continues to block 670 to optionally verify that the incoming communication is valid in one or more ways, such as in a manner similar to that described for block 570 of FIG. 5B . While not illustrated here, if an incoming communication is determined to not be valid, the routine may take various actions not shown, such as to generate one or more errors and perform associated processing and/or drop the incoming communication without forwarding it to the intermediate destination substrate device.
[0131] In the illustrated embodiment, after block 670, the routine continues to block 675 to decode the incoming communication so that the decoded communication is formatted in a manner specific to the managed virtual computer network to which it corresponds, such as by rewriting the communication header so that it appears to be sent from the sending computing node's virtual network address and directed to the virtual network address associated with the intended final destination, and optionally otherwise formatting the decoded communication (e.g., in accordance with a networking address protocol used by the managed virtual computer network), as described in greater detail elsewhere. If the decoded communication includes hardware addresses corresponding to the sending computing node and/or intermediate destination logical network device, the routine may obtain such information in various manners, such as by obtaining such information based on interactions with a system manager module (e.g., in a manner similar to blocks 520-525 of FIG. 5A ), although such actions are not illustrated in this example embodiment. In addition, in at least some embodiments, the routine may further optionally modify the decoded communication to include information for use by the intermediate destination substrate device in identifying the managed virtual computer network to which the communication corresponds, such as if the substrate device represents multiple logical network devices for multiple managed virtual computer networks—in the illustrated embodiment, the added information may be a VLAN identifier specific to the managed virtual computer network that is tracked by the routine and/or supplied by a system manager module. Furthermore, in at least some embodiments, the routine in block 675 may further perform other modifications to the decoded incoming communication that correspond to providing logical networking functionality to emulate the actions and functionality that would be performed by one or more logical networking devices for the managed virtual computer network that would have been used to forward the communication to the intermediate destination logical network node in accordance with the configured network topology for the virtual computer network. After block 675, the routine continues to block 680 to provide the decoded modified incoming communication to the intermediate destination substrate hardware device, so as to enable the substrate hardware device to perform one or more types of functionality for the communication that correspond to the configured logical network node that the substrate device represents.
[0132] If it is instead determined in block 610 that the type of communication or other message is an outgoing communication from an associated substrate device, such as a previously received incoming communication to the substrate device as an intermediate destination that is now being further forwarded by the substrate device toward the intended final destination for that previously received incoming communication (e.g., optionally after modification or other handling by the substrate device), the routine continues to block 640. In block 640, the routine identifies the destination virtual network address for the intended final destination from the communication header, as well as the source virtual network address associated with the original sending computing node. In block 650, the routine then determines a destination substrate network address corresponding to a next destination for the communication (e.g., the intended final destination for the communication, unless one or more other intermediate destinations exist for the communication based on the configured network topology for the managed virtual computer network), as well as a source substrate network address corresponding to the substrate hardware device that initiated the sending of the outgoing communication, and proceeds to block 655 to encode the outgoing communication to be formatted in a manner specific to the substrate computer network.
[0133] The encoding of the outgoing communication may include, for example, rewriting the communication header of the outgoing communication so that it is directed to the determined destination substrate network address and so that it includes the determined source substrate network address for the substrate hardware device, as well as optionally otherwise formatting the encoded communication in a manner specific to the substrate network (e.g., in accordance with a networking address protocol used by the substrate network), as described in greater detail elsewhere. In addition, in block 657, the routine proceeds to optionally remove any identifying information corresponding to the managed virtual computer network that is included in the communication, such as a network-specific VLAN identifier previously added to the communication as part of previous handling of the communication in block 675. The routine may determine the destination substrate network address in block 650 in various manners, such as by obtaining such information based on interactions with a system manager module (e.g., in a manner similar to blocks 520-525 of FIG. 5A ), although such actions are not illustrated in this example embodiment. In addition, if the managed virtual computer network is configured to include one or more logical networking devices that are not physically implemented between the intermediate destination logical network node and the next destination, the routine may further modify the encoded communication in blocks 655 and/or 657 to correspond to such logical networking devices, as discussed in greater detail elsewhere. In block 660, the routine then proceeds to forward the encoded communication over the substrate network toward the next destination for the communication. While not illustrated here, in other embodiments various additional types of processing may be performed for outgoing node communications, such as to verify that the communications are valid or otherwise authorized in various ways.
[0134] If it is instead determined in block 610 that a message of another type is received, the routine continues to block 685 to perform one or more other indicated operations as appropriate, such as to store and/or update information about one or more managed computer networks for which an associated substrate hardware device represents a configured logical network device (e.g., information about virtual network addresses and corresponding substrate network addresses for computing nodes of a managed virtual computer network, network topology information for a managed virtual computer network, etc.). The storing and/or updating of stored information may be initiated in various manners, such as by receiving information in response to previous requests, periodically requesting such information, receiving information that is proactively pushed to the routine without a corresponding request, etc.
[0135] After blocks 660, 680 or 685, the routine continues to block 695 to determine whether to continue, such as until an explicit indication to terminate is received. If it is determined to continue, the routine returns to block 605, and if not continues to block 699 and ends.
[0136] In addition, various embodiments may provide mechanisms for customer users and other entities to interact with an embodiment of the system manager module for the purpose of configuring computing nodes and their communications. For example, some embodiments may provide an interactive console (e.g. a client application program providing an interactive user interface, a Web browser-based interface, etc.) from which users can manage the creation or deletion of virtual computer networks, the configuration of specified VLANs for virtual computer networks, the configuration of network topology information for virtual computer networks, and the specification of virtual network membership, as well as more general administrative functions related to the operation and management of hosted applications (e.g., the creation or modification of user accounts; the provision of new applications; the initiation, termination, or monitoring of hosted applications; the assignment of applications to groups; the reservation of time or other system resources; etc.). In some embodiments, some or all of the functionality of an embodiment of the CNS system may be provided in exchange for fees from users or other entities acting as customers or other clients of the CNS system, and if so the mechanisms for such clients to interact with an embodiment of the system manager module may include mechanisms for users and other entities to provide payment and payment-related information, as well as to monitor corresponding payment information. In addition, some embodiments may provide an API that allows other computing systems and programs to programmatically invoke at least some of the described functionality, such as APIs provided by libraries or class interfaces (e.g., to be invoked by programs written in C, C++, or Java) or otherwise, and/or using network service protocols such as via Web services. Additional details related to the operation of example embodiments of a program execution service with which the described techniques may be used are available in U.S. application Ser. No. 11/394,595, filed Mar. 31, 2006 and entitled “Managing Communications Between Computing Nodes;” U.S. application Ser. No. 11/395,463, filed Mar. 31, 2006 and entitled “Managing Execution of Programs by Multiple Computing Systems;” U.S. application Ser. No. 11/692,038, filed Mar. 27, 2007 and entitled “Configuring Intercommunications Between Computing Nodes;” and U.S. application Ser. No. 12/332,214, filed Dec. 10, 2008 and entitled “Providing Access To Configurable Private Computer Networks;” each of which is incorporated herein by reference in its entirety. In addition, additional details related to the management of provided virtual networks that may be used by at least some embodiments of a CNS system, such as in conjunction with an Overlay Network Manager module of such a CNS system, are available in U.S. application Ser. No. 12/060,074, filed Mar. 31, 2008 and entitled “Configuring Communications Between Computing Nodes;” and in U.S. application Ser. No. 12/414,260, filed Mar. 30, 2009 and entitled “Providing Virtual Networking Functionality For Managed Computer Networks;” each of which is also incorporated herein by reference in its entirety.
[0137] It will also be appreciated that, although in some embodiments the described techniques are employed in the context of a data center housing multiple physical machines hosting virtual machines, other implementation scenarios are also possible. For example, the described techniques may be employed in the context an organization-wide network or networks operated by a business or other institution (e.g. university) for the benefit of its employees and/or members. Alternatively, the described techniques could be employed by a network service provider to improve network security, availability, and isolation. In addition, example embodiments may be employed within a data center or other context for a variety of purposes. For example, data center operators or users that sell access to hosted applications to customers may in some embodiments use the described techniques to provide network isolation between their customers' applications and data; software development teams may in some embodiments use the described techniques to provide network isolation between various environments that they use (e.g., development, build, test, deployment, production, etc.); organizations may in some embodiments use the described techniques to isolate the computing resources utilized by one personnel group or department (e.g., human resources) from the computing resources utilized by another personnel group or department (e.g., accounting); or data center operators or users that are deploying a multi-piece application (e.g., a multi-tiered business application) may in some embodiments use the described techniques to provide functional decomposition and/or isolation for the various types of interacting pieces (e.g., Web front-ends, database servers, business rules engines, etc.). More generally, the described techniques may be used to virtualize physical networks to reflect almost any situation that would conventionally necessitate physical partitioning of distinct computing systems and/or networks.
[0138] It will also be appreciated that in some embodiments the functionality provided by the routines discussed above may be provided in alternative ways, such as being split among more routines or consolidated into fewer routines. Similarly, in some embodiments illustrated routines may provide more or less functionality than is described, such as when other illustrated routines instead lack or include such functionality respectively, or when the amount of functionality that is provided is altered. In addition, while various operations may be illustrated as being performed in a particular manner (e.g., in serial or in parallel) and/or in a particular order, those skilled in the art will appreciate that in other embodiments the operations may be performed in other orders and in other manners. Those skilled in the art will also appreciate that the data structures discussed above may be structured in different manners, such as by having a single data structure split into multiple data structures or by having multiple data structures consolidated into a single data structure. Similarly, in some embodiments illustrated data structures may store more or less information than is described, such as when other illustrated data structures instead lack or include such information respectively, or when the amount or types of information that is stored is altered.
[0139] From the foregoing it will be appreciated that, although specific embodiments have been described herein for purposes of illustration, various modifications may be made without deviating from the spirit and scope of the invention. Accordingly, the invention is not limited except as by the appended claims and the elements recited therein. In addition, while certain aspects of the invention are presented below in certain claim forms, the inventors contemplate the various aspects of the invention in any available claim form. For example, while only some aspects of the invention may currently be recited as being embodied in a computer-readable medium, other aspects may likewise be so embodied.
Claims
What is claimed is:
1. A computer-implemented method comprising:
receiving configuration information for a first virtual computer network with multiple computing nodes, the configuration information indicating a specified network topology for the first virtual computer network that includes a first network node for use in providing a specified type of functionality; and
providing, by one or more programmed computing systems, the first virtual computer network in accordance with the received configuration information by overlaying the first virtual computer network on a distinct substrate network, the overlaying of the first virtual computer network including configuring one or more devices connected to the substrate network to act as the first network node for the first virtual computer network by providing the specified type of functionality, the providing of the first virtual computer network including:
forwarding a first communication over the substrate network between computing nodes of a first group without sending the first communication to the first network node;
determining, by the one or more programmed computing systems, to use the first network node as an intermediate destination for an additional communication based at least in part on the specified network topology, wherein the additional communication is from a source computing node in the first group to a destination computing node that is not in the first group; and
after the determining, encoding the additional communication for the substrate network and initiating forwarding the encoded additional communication over the substrate network from the source computing node to a translation manager module that manages decoding of encoded communications for the configured one or more devices, to enable the configured one or more devices to manage further forwarding of the additional communication to the destination computing node in accordance with the specified type of functionality.
2. The method of claim 1 further comprising, after the forwarding of the additional communication over the substrate network, and if the configured one or more devices determine to initiate further forwarding of the additional communication to the destination computing node, performing further forwarding of the additional communication over the substrate network from the configured one or more devices to the destination computing node.
3. The method of claim 2 wherein the determining to use the first network node as the intermediate destination for the additional communication and the initiating forwarding of the encoded additional communication over the substrate network from the source computing node are performed on behalf of the source computing node by a communication manager module that manages communications for the source computing node, and wherein the further forwarding of the additional communication over the substrate network from the configured one or more devices is performed on behalf of the configured one or more devices by the translation manager module.
4. The method of claim 2 wherein the configured one or more devices includes a configured first device with multiple logical network interfaces that each has a distinct virtual network address for the first virtual computer network, a first of the multiple logical network interfaces being associated with the computing nodes of the first group, and wherein the forwarding of the encoded additional communication over the substrate network from the source computing node of the first group includes directing the encoded additional communication to the first logical network interface.
5. The method of claim 4 further comprising providing the translation manager module for use with the first logical network interface and providing a second translation manager module for use with a second logical network interface of the multiple logical network interfaces, and wherein the further forwarding of the additional communication over the substrate network from the configured one or more devices uses the second logical network interface and is performed by the second translation manager module.
6. The method of claim 1 wherein the configured one or more devices are selected from multiple configurable hardware devices connected to the substrate network, and wherein the method further comprises configuring the selected one or more devices to provide functionality of the translation manager module.
7. The method of claim 1 further comprising decoding, by the translation manager module and after the forwarding of the encoded additional communication over the substrate network, the encoded additional communication before providing the decoded additional communication to the configured one or more devices.
8. The method of claim 1 wherein the computing nodes of the first group are at least some of the multiple computing nodes of the first virtual computer network, and wherein the specified network topology further indicates that the first network node is located between the first group and a second group of one or more other computing nodes, the destination computing node being one of the other computing nodes of the second group.
9. The method of claim 7 further comprising, under control of the configured one or more devices:
receiving the provided decoded additional communication from the translation manager module;
providing the specified type of functionality for the decoded additional communication by performing processing on the decoded additional communication, the performing of the processing including providing at least one of a group of capabilities that includes firewall capabilities, intrusion detection capabilities, content analysis capabilities, network acceleration capabilities, and virtual private network (“VPN”) connection capabilities; and
after the providing of the specified type of functionality for the decoded additional communication, initiating further forwarding of the decoded additional communication to the destination computing node.
10. The method of claim 7 further comprising, under control of the configured one or more devices:
receiving the provided decoded additional communication from the translation manager module; and
performing the managing of the further forwarding of the additional communication to the destination computing node by determining not to further forward the additional communication to the destination computing node.
11. The method of claim 7 wherein the decoding of the encoded additional communication further includes adding information to the decoded additional communication to represent the first virtual computer network, the added information including one or more identifiers for a virtual local area network (“VLAN”) associated with the first virtual computer network.
12. The method of claim 11 wherein the configured one or more devices handle communications for multiple virtual computer networks that are overlaid on the substrate network for multiple clients and that each have a distinct VLAN identifier, and wherein the translation manager module manages a plurality of communications sent to and from the configured one or more devices over the substrate network for the multiple virtual computer networks and adds a VLAN identifier to each communication of the plurality that is specific to one of the multiple virtual computer networks from which the communication is sent.
13. The method of claim 8 wherein the specified network topology includes the first group having the multiple computing nodes of the first virtual computer network and the second group having one or more other computing nodes external to the first virtual computer network, the computing nodes of the first group being co-located at a first geographical location and the one or more other computing nodes of the second group being at one or more locations remote from the first geographical location, or the computing nodes of the first group being part of a first specified logical subnet of the first virtual computer network and the one or more other computing nodes of the second group being one or more of the multiple computing nodes that are part of a second specified logical subnet of the first virtual computer network.
14. The method of claim 1 wherein the one or more programmed computing systems are part of a configurable network service that provides the first virtual computer network to a first client and that provides multiple other virtual computer networks to multiple other clients, and wherein communications sent between the multiple computing nodes of the first virtual computer network are transmitted on the substrate network in an encoded form that uses information specific to the substrate network and that uses a specified destination substrate network address for forwarding over the substrate network.
15. A computing system, comprising:
one or more processors; and
a communication manager module that is associated with one or more computing nodes of a first virtual computer network overlaid on a second substrate network and that is configured to, when executed by at least one of the one or more processors, manage communications sent by the one or more computing nodes in accordance with specified network topology information for the first virtual computer network, by:
determining, before forwarding a first communication over the second substrate network, to use an indicated network node of the first virtual computer network as an intermediate destination for the first communication, the determining being based at least in part on the specified network topology information for the first virtual computer network;
identifying one or more devices accessible via the second substrate network for use as the indicated network node for the first virtual computer network, wherein the identified one or more devices are configured to provide a type of functionality specified for the indicated network node and have one or more associated translation manager modules to manage decoding of communications from the virtual computer network that are sent over the second substrate network to the identified one or more devices; and
initiating forwarding the first communication over the second substrate network to the one or more associated translation manager modules for the identified one or more devices, to enable the identified one or more devices to manage further handling of the first communication in accordance with the provided type of functionality before further forwarding of the first communication to an indicated final destination for the first communication.
16. The computing system of claim 15 wherein the identified one or more devices have an associated substrate network address corresponding to a location of the identified one or more devices in the second substrate network, and wherein the initiating forwarding of the first communication over the second substrate network includes directing the first communication to the associated substrate network address.
17. The computing system of claim 15 further comprising a system manager module configured to, when executed by at least one of the one or more processors:
obtain configuration information specified by a user on whose behalf the first virtual computer network is provided, the configuration information including the specified network topology for the first virtual computer network and specifying the type of functionality to be provided by the indicated network node, the specified network topology indicating that the indicated network node is located between a first group of computing nodes of the first virtual computer network and a second group of one or more other computing nodes, the first communication being sent between at least one computing node of the first group and at least one computing node of the second group; and
before the managing of the communications by the communication manager module, select the identified one or more devices from multiple devices connected to the substrate network.
18. The computing system of claim 15 further comprising the identified one or more devices, and wherein the identified one or more devices are further configured to perform the managing of the further handling of the first communication by determining not to perform further forwarding of the first communication to the indicated final destination for the first communication, the determining not to perform the further forwarding being based at least in part on the performing of the provided type of functionality for the first communication.
19. The computing system of claim 15 wherein the communication manager module includes software instructions for execution by the at least one processors of the computing system and is further configured to, before a second communication is forwarded to the second substrate network, determine to not use the indicated network node as an intermediate destination for the second communication based at least in part on the specified network topology information for the first virtual computer network.
20. The computing system of claim 15 wherein the communication manager module consists of a means for performing the managing of the communications sent by the one or more computing nodes in accordance with the specified network topology information for the first virtual computer network.
21. The computing system of claim 15 further comprising:
a first translation manager module that is associated with a first of the identified one or more devices and is configured to manage communications sent to and from the first identified device over the substrate network, wherein the first communication that is forwarded over the second substrate network is encoded in a manner specific to the substrate network and is forwarded to the first translation manager module, and wherein the first translation manager module is further configured to:
receive the forwarded encoded first communication;
decode the received encoded first communication to be formatted in a manner specific to the first virtual computer network; and
provide the decoded first communication to the first identified device to enable the first identified device to operate as the indicated network device by performing the type of functionality on the decoded first communication.
22. The computing system of claim 15 wherein the managing, by the communication manager module, of the communications sent by the one or more computing nodes further includes initiating forwarding a second communication over the second substrate network to an indicated final destination for the second communication without providing the second communication to the indicated network node as an intermediate destination.
23. A non-transitory computer-readable medium having stored contents that configure a computing system to manage communications sent by one or more computing nodes of a first virtual computer network in accordance with specified network topology information for the first virtual computer network, by:
determining, by the configured computing system and before forwarding a first communication over a second substrate network on which the first virtual computer network is overlaid, to use an indicated network node of the first virtual computer network as an intermediate destination for the first communication, the determining being based at least in part on the specified network topology information for the first virtual computer network;
identifying, by the configured computing system, one or more devices accessible via the second substrate network for use as the indicated network node for the first virtual computer network, wherein the identified one or more devices are configured to provide a type of functionality specified for the indicated network node and have one or more associated translation manager modules to manage communications for the virtual computer network that are sent over the second substrate network to the identified one or more devices; and
initiating, by the configured computing system, forwarding the first communication over the second substrate network to the one or more associated translation manager modules for the identified one or more devices, to enable the identified one or more devices to manage further handling of the first communication in accordance with the provided type of functionality before further forwarding of the first communication to an indicated final destination for the first communication.
24. The non-transitory computer-readable medium of claim 23 wherein the identified one or more devices have an associated substrate network address corresponding to a location of the identified one or more devices in the second substrate network, and wherein the initiating forwarding of the first communication over the second substrate network includes directing the first communication to the associated substrate network address.
25. The non-transitory computer-readable medium of claim 23 wherein the stored contents include software instructions that, when executed, further configure the computing system to:
obtain configuration information specified by a user on whose behalf the first virtual computer network is provided, the configuration information including the specified network topology for the first virtual computer network and specifying the type of functionality to be provided by the indicated network node; and
before the managing of the communications sent by the one or more computing nodes, select the identified one or more devices from multiple devices connected to the substrate network.
26. The non-transitory computer-readable medium of claim 25 wherein the specified network topology indicates that the indicated network node is located between a first group of computing nodes of the first virtual computer network and a second group of one or more other computing nodes, and wherein the first communication is sent between at least one computing node of the first group and at least one computing node of the second group.
27. The non-transitory computer-readable medium of claim 25 wherein the configured computing system is part of a configurable network service that provides the first virtual computer network to the user in exchange for one or more monetary fees and that provides multiple other virtual computer networks to multiple other users.
28. The non-transitory computer-readable medium of claim 25 wherein the stored contents include software instructions that, when executed, further configure the computing system to, before the initiating forwarding of the first communication, configure the identified one or more devices to provide the type of functionality specified for the indicated network node.
29. The non-transitory computer-readable medium of claim 28 wherein the configuring of the identified one or more devices enables the identified one or more devices to perform the managing of the further handling of the first communication, and wherein the managing of the further handling of the first communication includes determining not to perform further forwarding of the first communication to the indicated final destination based on the provided type of functionality.
30. The non-transitory computer-readable medium of claim 23 wherein the stored contents include software instructions that, when executed, further configure the computing system to, before a second communication from a computing node of the first virtual computer network is forwarded to the second substrate network, determine to not use the indicated network node as an intermediate destination for the second communication based at least in part on the specified network topology information for the first virtual computer network.
31. The non-transitory computer-readable medium of claim 23 wherein the managing of the communications for the virtual computer network by the one or more associated translation manager modules includes:
receiving the forwarded first communication, wherein the forwarded first communication is encoded in a manner specific to the second substrate network before it is forwarded to the one or more associated translation manager modules over the second substrate network;
decoding the received first communication and formatting the decoded first communication in a manner specific to the first virtual computer network; and
providing the formatted decoded first communication to at least one of the identified one or more devices, to enable the at least one identified device to operate as the indicated network device by performing the type of functionality on the formatted decoded first communication.
32. The non-transitory computer-readable medium of claim 23 wherein the stored contents include software instructions that, when executed, further configure the computing system to initiate forwarding a second communication for the virtual computer network over the second substrate network to an indicated final destination for the second communication without providing the second communication to the indicated network node as an intermediate destination.
33. The non-transitory computer-readable medium of claim 23 wherein the stored contents include software instructions that, when executed, further configure the computing system to provide the first virtual computer network in accordance with received configuration information by overlaying the first virtual computer network on the second substrate network, the overlaying of the first virtual computer network including configuring the identified one or more devices to act as the indicated network node for the first virtual computer network by providing the specified type of functionality.
34. The non-transitory computer-readable medium of claim 23 wherein the stored contents include software instructions that, when executed, further configure the computing system to, after the initiating forwarding of the first communication over the second substrate network, and if the identified one or more devices determine to initiate the further forwarding of the first communication to the indicated final destination, performing the further forwarding of the first communication over the second substrate network from the identified one or more devices to the indicated final destination.
35. The non-transitory computer-readable medium of claim 23 wherein the type of functionality specified for the indicated network node is at least one of a group of capabilities that includes firewall capabilities, intrusion detection capabilities, content analysis capabilities, network acceleration capabilities, and virtual private network (“VPN”) connection capabilities.
Patent Citations (15)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US6411967(B1) | 2002-06-01 | Van Renesse | Applicant |
| US6529953(B1) | 2003-03-01 | Van Renesse | Applicant |
| US6724770(B1) | 2004-04-01 | Van Renesse | Applicant |
| US7068666(B2) | 2006-06-01 | Foster et al. | Applicant |
| US7068667(B2) | 2006-06-01 | Foster et al. | Applicant |
| US7124289(B1) | 2006-10-01 | Suorsa | Applicant |
| US7131123(B2) | 2006-10-01 | Suorsa et al. | Applicant |
| US7152109(B2) | 2006-12-01 | Suorsa et al. | Applicant |
| US2005/0114507(A1) | 2005-05-01 | Tarui et al. | Applicant |
| US2005/0120160(A1) | 2005-06-01 | Plouffe et al. | Applicant |
| US2006/0126495(A1) | 2006-06-01 | Guichard et al. | Examiner |
| US2006/0184936(A1) | 2006-08-01 | Abels et al. | Applicant |
| US2007/0086382(A1) | 2007-04-01 | Narayanan et al. | Examiner |
| US2008/0101360(A1) | 2008-05-01 | Napierala | Examiner |
| US2012/0311108(A1) | 2012-12-01 | Brandwine et al. | Examiner |
Non-Patent Literature (46)
- “Chapter: Configuring Layer 2 Services Over MPLS,” JUNOSe Internet Software for E-series Routing Platforms: Routing Protocols Configuration Guide, vol. 2, Mar. 2004, retrieved Jan. 26, 2007, from http://www.juniper.net/techpubs/software/erx/junose52/swconfig-routing-vol2/html/title-swconfig . . . , pp. 357-382, 31 pages.Applicant
- “Cisco IP Solution Center MPLS VPN Management 4.2,” Cisco Systems, Inc., retrieved Jan. 24, 2007, from http://www.cisco.com/en/US/products/sw/netmgtsw/ps5332/products—data—sheet—09186a008017d7 . . . , 5 pages.Applicant
- “Grid Computing Solutions,” Sun Microsystems, Inc., retrieved May 3, 2006, from http://www.sun.com/software/grid, 3 pages.Applicant
- “Grid Offerings,” Java.net, retrieved May 3, 2006, from http://wiki.java.net/bin/view/Sungrid/OtherGridOfferings, 8 pages.Applicant
- “MPLS-enabled VPN Services,” Data Connection, retrieved Jan. 26, 2007, from http://www.dataconnection.com/solutions/vpn—vlan.htm, 1 page.Applicant
- “Recent Advances Boost System Virtualization,” eWeek.com, retrieved May 3, 2006, from http://www.eweek.com/article2/0,1895,1772626,00.asp, 5 pages.Applicant
- “Scalable Trust of Next Generation Management (STRONGMAN),” retrieved May 17, 2006, from http://www.cis.upenn.edu/˜dsl/STRONGMAN/, 4 pages.Applicant
- “Sun EDA Compute Ranch,” Sun Microsystems, Inc., retrieved May 3, 2006, from http://sun.com/processors/ranch/brochure.pdf, 2 pages.Applicant
- “Sun Microsystems Accelerates UltraSPARC Processor Design Program With New Burlington, Mass. Compute Ranch,” Nov. 6, 2002, Sun Microsystems, Inc., retrieved May 3, 2006, from http://www.sun.com/smi/Press/sunflash/2002-11/sunflash.20021106.3.xml, 2 pages.Applicant
- “Sun N1 Grid Engine 6,” Sun Microsystems, Inc., retrieved May 3, 2006, from http://www.sun.com/software/gridware/index.xml, 3 pages.Applicant
- “Sun Opens New Processor Design Compute Ranch,” Nov. 30, 2001, Sun Microsystems, Inc., retrieved May 3, 2006, from http://www.sun.com/smi/Press/sunflash/2001-11/sunflash.20011130.1.xml, 3 pages.Applicant
- “The Reverse Firewall™: Defeating DDoS Attacks Emerging from Local Area Networks,” Cs3, Inc., retrieved Nov. 11, 2005, from http://www.cs3-inc.com/rfw.html, 4 pages.Applicant
- “The Softricity Desktop,” Softricity, retrieved May 3, 2006, from http://www.softricity.com/products/, 3 pages.Applicant
- Bellovin, S., “Distributed Firewalls,” Nov. 1999, issue of ;login:, pp. 37-39, retrieved Nov. 11, 2005, from http://www.cs.columbia.edu/˜smb/papers/distfw.html, 10 pages.Applicant
- Blaze, M., “Using the KeyNote Trust Management System,” Mar. 1, 2001, retrieved May 17, 2006, from http://www.crypto.com/trustmgt/kn.html, 4 pages.Applicant
- Brenton, C., “What is Egress Filtering and How Can I Implement It?—Egress Filtering v 0.2,” Feb. 29, 2000, SANS Institute, http://www.sans.org/infosecFAQ/firewall/egress.htm, 6 pages.Applicant
- Chown, T., “Use of VLANs for IPv4-IPv6 Coexistence in Enterprise Networks: draft-ietf-v6ops-vlan-usage-01,” IPv6 Operations, University of Southampton, Mar. 6, 2006, retrieved Jun. 15, 2007, from http://tools.ietf.org/html/draft-ietf-v6ops-vlan-usage-01, 13 pages.Applicant
- Coulson, D., “Network Security Iptables,” Apr. 2003, Linuxpro, Part 2, retrieved from http://davidcoulson.net/writing/lxf/39/iptables.pdf, 4 pages.Applicant
- Coulson, D., “Network Security Iptables,” Mar. 2003, Linuxpro, Part 1, retrieved from http://davidcoulson.net/writing/lxf/38/iptables.pdf, 4 pages.Applicant
- Demers, A., “Epidemic Algorithms for Replicated Database Maintenance,” 1987, Proceedings of the sixth annual ACM Symposium on Principles of distributed computing, Vancouver, British Columbia, Canada, Aug. 10-12, 1987, 12 pages.Applicant
- Gruener, J., “A vision of togetherness,” May 24, 2004, NetworkWorld, retrieved May 3, 2006, from, http://www.networkworld.com/supp/2004/ndc3/0524virt.html, 9 pages.Applicant
- Ioannidis, S., “Implementing a Distributed Firewall,” Nov. 2000, (ACM) Proceedings of the ACM Computer and Communications Security (CCS) 2000, Athens, Greece, pp. 190-199, retrieved from http://www.cis.upenn.edu/˜dsl/STRONGMAN/Papers/df.pdf, 10 pages.Applicant
- Kenshi, P., “Help File Library: Iptables Basics,” Justlinux, retrieved Dec. 1, 2005, from http://www.justlinux.com/nhf/Security/Iptables—Basics.html, 4 pages.Applicant
- Shankland, S., “Sun to buy start-up to bolster N1,” Jul. 30, 2003, CNet News.com, retrieved May 3, 2006, http://news.zdnet.com/2100-35213—22-5057752.html, 8 pages.Applicant
- Strand, L., “Adaptive distributed firewall using intrusion detection,” Nov. 1, 2004, University of Oslo Department of Informatics, retrieved Mar. 8, 2006, from http://gnist.org/˜lars/studies/master/StrandLars-master.pdf, 158 pages.Applicant
- Townsley, M., et al., “Encapsulation of MPLS over Layer 2 Tunneling Protocol Version 3: draft-ietf-mpls-over-12tpv3-03.txt,” Network Working Group, Nov. 2006, retrieved Jun. 15, 2007, from http://tools.ietf.org/html/draft-ietf-mpls-over-12tpv3-03, 12 pages.Applicant
- Van Renesse, R., “Astrolabe: a Robust and Scalable Technology for Distributed System Monitoring, Management, and Data Mining,” May 2003, ACM Transactions on Computer Systems (TOCS), 21(2): 164-206, 43 pages.Applicant
- Vijayan, J., “Terraspring Gives Sun's N1 a Boost,” Nov. 25, 2002, Computerworld, retrieved May 3, 2006, from http://www.computerworld.com/printthis/2002/0,4814,76159,00.html, 3 pages.Applicant
- Virtual Iron Software Home, Virtualiron®, retrieved May 3, 2006, from http://www.virtualiron.com/, 1 page.Applicant
- Waldspurger, C.A., “Spawn: A Distributed Computational Economy,” Feb. 1992, IEEE Transactions on Software Engineering, 18(2):103-117, 15 pages.Applicant
- “Anycast,” retrieved on Mar. 16, 2009, from http://en.wikipedia.org/wiki/Anycast, 4 pages.Applicant
- “Load Balancing (Computing),” retrieved on Mar. 16, 2009, from http://en.wikipedia.org/wiki/Load—balancing—(computing), 5 pages.Applicant
- “Mobile IP,” retrieved on Dec. 19, 2008, from http://en.wikipedia.org/wiki/Mobile—ip, 3 pages.Applicant
- “Round Robin DNS,” retrieved on Dec. 17, 2008, from http://en.wikipedia.org/wiki/Round—robin—DNS, 2 pages.Applicant
- “Virtual IP Address,” retrieved on Dec. 17, 2008, from http://www.answers.com/topic/virtual-ip-address-1, 2 pages.Applicant
- “VMware VMotion,” retrieved on Mar. 16, 2009, from http://www.vmware.com/products/vi/vc/vmotion.html. 2 pages.Applicant
- “VMWare Storage VMotion,” retrieved on Mar. 16, 2009, from http://www.vmware.com/products/vi/storage—vmotion.html. 2 pages.Applicant
- Clark, C., et al. “Live Migration of Virtual Machines,” retrieved on Mar. 16, 2009, from http://www.cl.cam.ac.uk/research/srg/netos/papers/2005-migration-nsdi-pre.pdf, 14 pages.Applicant
- “EZchip Technologies—Technologies,” retrieved on Mar. 31, 2010, from http://www.ezchip.com/technologies.htm, 2 pages.Applicant
- “Link Aggregation,” retrieved on Mar. 31, 2010, from http://en.wikipedia.org/wiki/802.3ad, 6 pages.Applicant
- “Network Processor,” retrieved on Mar. 31, 2010, from http://en.wikipedia.org/wiki/Network—processor, 3 pages.Applicant
- “TippingPoint—Core—Controller,” retrieved on Mar. 31, 2010, from http://www.tippingpoint.com/pdf/resources/datasheets/401054-005—TippingPointCoreController.pdf, 3 pages.Applicant
- “TippingPoint Technologies,” retrieved on Mar. 31, 2010, from http://www.tippingpoint.com/products—core—controller.html, 2 pages.Applicant
- “VMware VMsafe Security Technology,” retrieved on Mar. 31, 2010, from http://www.vmware.com/technical-resources/security/vmsafe/faq.html, 3 pages.Applicant
- “New VMware VMsafe Technology Allows the Virtual Datacenter to Be More Secure Than Physical Environments,” Feb. 27, 2008, retrieved on Mar. 31, 2010, from http://www.vmware .com/company/news/releases/vmsafe—vmworld.html, 5 pages.Applicant
- “VMware VMsafe Security Technology,” retrieved on Mar. 31, 2010, from http://www.vmware.com/technical-resources/security/vmsafe.html?rls=com.microsoft:en-u . . . , 3 pages.Applicant