Key-configured topology with connection management

Abstract

Systems, methodologies, media, and other embodiments associated with key-configured topology connection management are described. One exemplary system embodiment includes a logic for mapping a resource to a port through which it can be accessed and a logic for determining whether a requestor will be granted a connection to the machine on which the resource resides based, at least in part, on membership in a key-configured topology. Membership in the key-configured topology may be determined by a connection management logic analyzing a key provided by the requestor in a request related to accessing the resource. The key may be internally generated by a key maintenance logic.

1 . A system, comprising:
 a graphical user interface for defining a key-configured topology group that identifies a group of member nodes that are authorized to communicate with each other, and for causing a key to be generated that validates membership of a node in the key-configured topology group;   a mapping logic, implemented in a computer-readable storage medium, configured to produce a port mapping between a resource located on a first node and a port located on the first node, and to selectively provide to a second node a port mapping data that describes the mapping between the resource and the port in response to receiving a port request and a key from the second node; and   a connection management logic, implemented in a computer-readable storage medium and operably connected to the mapping logic, the connection management logic being configured to control one or more of, whether the mapping logic will provide the port mapping data to the second node, and whether a connection that facilitates the second node having remote direct memory access to the resource via a first networking protocol will be established between the first node and the second node, and   where the connection management logic causes the connection to be established that allows the second node to have remote direct memory access to the resource on the first node if the key received from the second node is a valid key from the key-configured topology group and the second node is a member node in the key-configured topology group.   
     
     
         2 . The system of  claim 1 , where the mapping logic comprises a port mapper configured to listen on a well-known port for port requests for port mapping data. 
     
     
         3 . The system of  claim 1 , the connection management logic being further configured to facilitate establishing a fallback connection between the first node and the second node according to a second networking protocol, the second protocol being different from the first networking protocol the second protocol not allowing remote direct memory access to the first node via the port mapped to the resource, where the second node may request the fallback connection after the mapping logic has been controlled to not provide the port mapping data to the second node or the mapping logic has prevented the establishment of a connection between the first node and the second node according to the first networking protocol. 
     
     
         4 . The system of  claim 1 , where the resource supports remote direct memory access (RDMA) between the first node and the second node. 
     
     
         5 . The system of  claim 1 , the resource comprising one or more of, a computer memory, a data communication connection, a license, and a processor cycle. 
     
     
         6 . The system of  claim 1 , where one or more of, the mapping logic, and the connection management logic are located on one or more of, a network interface card (NIC), and a remote direct memory access (RDMA) NIC (RNIC). 
     
     
         7 . The system of  claim 1 , where the connection management logic exerts its control based on analyzing the key and one or more of, time of day, network traffic, load, and resource availability. 
     
     
         8 . The system of  claim 1 , where the connection management logic operates at a session layer associated with the first networking protocol. 
     
     
         9 . The system of  claim 8 , where the first networking protocol includes a Transmission Control Protocol (TCP) transport layer and an Internet Protocol (IP) network layer. 
     
     
         10 . The system of  claim 1 , where the key is generated by a key-generating logic that accepts an input data received from a user via the graphical user interface. 
     
     
         11 . The system of  claim 1 , comprising a computer configured to include the mapping logic and the connection management logic. 
     
     
         12 - 18 . (canceled) 
     
     
         19 . A method, comprising:
 in a first node, receiving from a second node a first request for a port mapping data that describes a relationship between a resource on the first node and a port on the first node;   selectively providing the port mapping data to the second node based on the presence and validity of a key in the first request, where the key is configured to establish that the second node is a member of a key-configured topology group that includes the first node;   receiving from the second node a second request to establish a connection between the first node and the second node via a first networking protocol, where the connection facilitates accessing the resource;   selectively establishing the connection based on the presence and validity of the key in the second request; and   selectively providing a notification to the second node that the connection was established.   
     
     
         20 . The method of  claim 19 , further including:
 defining a key-configured topology group that identifies a group of member nodes that are authorized to communicate with each other, and for causing a key to be generated that validates membership of a node in the key-configured topology group; and   where the selectively establishing the connection includes determining whether the key is a valid group member key from the key-configured topology group and whether the second node is a member node in the key-configured topology group.   
     
     
         21 . The method of  claim 20 , where the resource is located on one or more of, a network interface card (NIC), and a remote direct memory access (RDMA) NIC (RNIC) associated with the first node. 
     
     
         22 . The method of  claim 21 , where the resource supports RDMA between the first node and the second node. 
     
     
         23 . The method of  claim 22 , where the method is performed in a session layer logic associated with the first networking protocol. 
     
     
         24 . The method of  claim 23 , where the first networking protocol includes a Transmission Control Protocol (TCP) transport layer and an Internet Protocol (IP) network layer. 
     
     
         25 . The method of  claim 24 , including providing to the second node a communication that confirms that a connection was established between the first node and the second node via the first networking protocol. 
     
     
         26 . The method of  claim 25 , including receiving from the second node a third request to establish a fallback connection between the first node and the second node, where the third request does not include the key included in the second request, and where the third request requests that the fallback connection be established via a second networking protocol, where the fallback connection granted in response to the third request will not provide access to the resource via the first networking protocol. 
     
     
         27 - 31 . (canceled) 
     
     
         32 . A non-transitory, computer-readable medium storing processor executable instructions operable to perform a method, the method comprising:
 from a client node, making a first request to a well-known port on a server node for a mapping data that describes a port through which a resource on the server node can be accessed, where the first request includes a key configured to identify the client node as a member of a key-configured topology group to which the server node belongs, where the resource is located on a remote direct memory access (RDMA) NIC (RNIC) associated with the server node and where the resource supports RDMA between the client node and the server node;   upon determining that the mapping data has been received, making a second request to the server node to establish a connection to the resource through the port via a first computer networking protocol, where the first computer networking protocol includes a Transmission Control Protocol (TCP) transport layer and an Internet Protocol (IP) network layer; and   upon determining that the mapping data has not been received, making a third request to the server node to establish a fallback connection to the server node via a second computer networking protocol, the second computer networking protocol being different from the first computer networking protocol.   
     
     
         33 - 34 . (canceled) 
     
     
         35 . A set of application programming interfaces embodied on a non-transitory, computer-readable medium for execution by a computer component in conjunction with key-configured topology connection management, comprising:
 a first interface for communicating a key configured to facilitate determining whether a client node is a member of a key-configured topology group to which a server node belongs; and   a second interface for communicating a verification data produced by analyzing a request related to accessing a network resource, where the request includes the key;   wherein the verification data causes a connection to be established that enables the client node to have a remote direct memory access to the memory of the server node.