Method and system for providing transparent location of computing systems to virtualized application workspaces

• US 7,934,017 B2
• Filed: 10/30/2007
• Issued: 04/26/2011
• Est. Priority Date: 12/19/2005
• Status: Active Grant

• Current Assignee: Omnissa, LLC
• Original Assignee: VMware, Inc. (Broadcom, Inc.)
• Inventors: Wilkinson, Anthony J.
• Primary Examiner(s): Avellino; Joseph
• Assistant Examiner(s): WASEL, MOHAMED A
• Application Number:
  US11/929,327
• Publication Number:
  US 20080133777A1
• Time in Patent Office: 1,274 Days
• Field of Search: 709/230, 709/245
• US Class Current: 709/245
• CPC Class Codes: G06F 16/282 Hierarchical databases, e.g. IMS, LDAP data stores or Lotus Notes
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/505 considering the load
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: H04L 61/4523 using lightweight directory access protocol [LDAP]
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1023 based on a hash applied to IP addresses or costs
• CPC Class Codes: H04L 67/1031 Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

Methods and systems for providing transparent access between computing systems connected to separate networks are provided. Example embodiments provide Grid Location Services (“GLS”) which, in one embodiment integrates multicast DNS (mDNS) technologies with DNS technology to achieve transparent configurability of servers. In one example, an Application Workspace System “AWS” provides a GLS module that transparently provides for the reconfiguration of computing systems, when an AWS service is added, removed, or fails, without reconfiguring all the entities that use those services. This abstract is provided to comply with rules requiring an abstract, and it is submitted with the intention that it will not be used to interpret or limit the scope or meaning of the claims.

Claims

1. A computing environment comprising:

a first network configured to connect a plurality of computing systems that communicate with each other using a multicast DNS (“

mDNS”

) protocol; and

a second network configured to connect a plurality of computing systems that communicate with each other and configured to include a DNS to mDNS bridge node that is configured to;

act as an authoritative DNS server for a domain of the second network; and

allow one or more of the plurality of computing systems connected to the second network to communicate with one or more of the computing systems connected to the first network, by;

receiving registrations via mDNS from the plurality of computing systems of the second network; and

responding, based on information in the received registrations, to a DNS query received from one of the plurality of computing systems of the first network;

the DNS to mDNS bridge node further comprising;

a first module that is configured to respond to DNS queries based upon information in the received registrations; and

a second module that is configured to periodically remove information for a received registration when it is determined that one of the plurality of computing systems of the second network is no longer providing a designated service.

2. The computing environment of claim 1 wherein

the first module is configured to respond to DNS requests based on contents of a registration file;

and

the second module is a registered mDNS node that alters the contents of the registration file based on received mDNS registrations.

3. The computing environment of claim 2 wherein the first module is further configured to, for every DNS request received by the first module, access the contents of the registration file.

4. The computing environment of claim 2 wherein the first module is further configured to respond to each received DNS request by setting a time to live field in a response to zero, such that downstream components will not cache the response.

5. The computing environment of claim 2 wherein the second module is further configured to be extended with one or more plug-ins that are each configured to determine whether a server on one of the computing systems connected to the second network is providing a designated service.

6. The computing environment of claim 5 wherein one of the one or more plug-ins is configured to:

periodically perform queries against servers listed in the registration file; and

in response to an incorrect response from one of the servers listed in the registration file, exclude the one server from a list of addresses in the registration file.

7. A method in a computing environment for providing configurability of servers on a first local area network transparent to computers on a second unrelated local area network, the method comprising:

providing a DNS to mDNS bridge node that allows a server on the first local area network to communicate with a computer on the second local area network, by;

receiving registrations via mDNS from the servers of the first local area network;

responding, based on information in the received registrations, to a DNS query received from the computer on the second local area network; and

periodically, removing information for a received registration when it is determined that one of the servers of the first local area network is no longer providing a designated service.

8. The method of claim 7 wherein the DNS to mDNS bridge node includes:

a first module that is configured to respond to DNS requests based on contents of a registration file; and

a second module that is a registered mDNS node that alters the contents of the registration file based on mDNS registrations.

9. The method of claim 7 wherein the DNS to mDNS bridge node is configured to, in response to every received DNS request, access a registration file.

10. The method of claim 7 wherein the DNS to mDNS bridge node is configured to respond to each received DNS request by setting a time to live field in a response to zero, such that downstream components will not cache the response.

11. The method of claim 7 wherein the DNS to mDNS bridge node is configured to:

periodically perform queries against servers listed in a registration file; and

in response to an incorrect response from one of the servers listed in the registration file, exclude the one server from a list of addresses in the registration file.

12. A computer-readable memory medium on a computing system containing content that is configured to distribute a packet to one or more other computer systems using a multicast DNS protocol, by performing a method comprising:

receiving a DNS request over a first network from a source computing system; and

responding to the received DNS request based on mDNS registrations received from computing systems connected to a second different network that is configured to include an DNS to mDNS bridge node, such that the source computing system communicates transparently with one or more of the computing systems connected to the second different network using the DNS to mDNS bridge node,

wherein the DNS to mDNS bridge node is configured to;

respond, based on information in the received registrations, to DNS requests; and

periodically, remove information for a received registration when it is determined that one of the computing systems connected to the second different network is no longer providing a designated service.

13. The computer-readable memory medium of claim 12 wherein the first network is a wide area network and the second network is a local area network.

14. The computer-readable memory medium of claim 12 wherein the source computing system is connected to a local area network and communicates with one or more computing systems connected to the local area network using a multicast DNS protocol.

15. The computer-readable memory medium of claim 12 wherein the computer-readable memory medium is a memory in a computing device.

16. The computer-readable memory medium of claim 12 wherein the content includes instructions that, when executed, cause the computing system to perform the method.

17. The computer-readable memory medium of claim 12 wherein the method further comprises:

responding to DNS requests based on contents of a registration file; and

altering the contents of the registration file based on mDNS registrations.

18. The computer-readable memory medium of claim 12 wherein the method further comprises:

in response to every received DNS request, accessing contents of a registration file.

19. The computer-readable memory medium of claim 12 wherein the method further comprises:

respond to each received DNS request by setting a time to live field in a response to zero, such that downstream components will not cache the response.

20. The computer-readable memory medium of claim 12 wherein the method further comprises:

performing a query against a server listed in a registration file; and

in response to an incorrect response from the server, excluding the server from a list of addresses in the registration file.