Dynamically updating compute node location information in a distributed computing environment

A computing system, comprising:

• one or more processors;
• and
• at least one computer-readable storage medium storing instructions that, when executed, cause the one or more processors to:
• responsive to receiving a resource request from a client device, deploy, by a controller node, and for execution on a particular data center selected from a plurality of data centers, a compute node;
• store, by the controller node and in a node inventory data store, first and second Internet Protocol (IP) addresses that are each assigned to the compute node, wherein the first IP address is different than the second IP address;
• send, by the controller node an using the first IP address assigned to the compute node, a first group of one or more connectivity detection messages;
• determine, by the controller node, that the compute node is not accessible using the first IP address at least by determining that the controller node failed to receive at least one reply in response to the first group of one or more connectivity detection messages;
• and
• responsive to determining that the compute node is not accessible using the first IP address:
• send, by the controller node and using the second IP address assigned to the compute node, a second group of one or more connectivity detection messages:
• determine, by the controller node and based on information received from the particular data center, that the compute node is still available for execution on the particular data center;
• receive, by the controller node and from the particular data center, at least one updated IP address assigned to the compute node;
• and
• update, by the controller node, the node inventory data store to store the at least one updated IP address assigned to the compute node.

A computer-readable storage medium storing instructions that are executable by at least one processor to:

• responsive to receiving a resource request from a client device, deploy, by a controller node, and for execution on a particular data center selected from a plurality of data centers, a compute node;
• store, by the controller node and in a node inventory data store, first and second Internet Protocol (IP) addresses that are each assigned to the compute node, wherein the first IP address is different than the second IP address;
• send, by the controller node and using the first IP address assigned to the compute node, a first group of one or more connectivity detection messages;
• determine, by the controller node, that the compute node is not accessible using the first IP address at least by determining that the controller node failed to receive at least one reply in response to the first group of one or more connectivity detection messages;
• and
• responsive to determining that the compute node is not accessible using the first IP address:
• send, by the controller node and using the second IP address assigned to the compute node, a second group of one or more connectivity detection messages;
• determine, by the controller node and based on information received from the particular data center, that the compute node is still available for execution on the particular data center;
• receive, by the controller node and from the particular data center, at least one updated IP address assigned to the compute node;
• and
• update, by the controller node, the node inventory data store to store the at least one updated IP address assigned to the compute node.