Systems and methods to uniquely identify assets in a federation

• US 8,166,108 B1
• Filed: 09/29/2011
• Issued: 04/24/2012
• Est. Priority Date: 08/16/2011
• Status: Active Grant

• Current Assignee: Edgio Incorporated
• Original Assignee: EdgeCast Networks (Verizon Communications Inc.)
• Inventors: Peters, Robert J., Kazerani, Alexander A.
• Primary Examiner(s): JEAN, FRANTZ B
• Application Number:
  US13/248,552
• Time in Patent Office: 208 Days
• Field of Search: 709/203, 709/249, 707/661, 707/802, 707/803, 707/821, 707/827
• US Class Current: 709/203
• CPC Class Codes: G06F 11/1433 during software upgrading
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 16/2471 Distributed queries
• CPC Class Codes: G06F 16/256 in federated or virtual databases
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 9/46 Multiprogramming arrangements
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0605 Supply or demand aggregation
• CPC Class Codes: G06Q 30/0641 Shopping interfaces
• CPC Class Codes: G06Q 30/08 Auctions
• CPC Class Codes: H04L 12/42 Loop networks
• CPC Class Codes: H04L 41/0813 characterised by the conditions triggering a change of settings
• CPC Class Codes: H04L 41/0816 the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 63/104 Grouping of entities
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04L 67/10 : in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/535 : Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34

Abstract

Some embodiments provide different frameworks that implement conflict avoidance systems and methods for ensuring uniqueness in identifying assets for different customers that are deployed to server capacity of one or more distributed platforms participating in a federation. Specifically, different frameworks are provided whereby the distributed platforms authorize use of a domain before configuring the domain to identify assets of a customer. A method performed in one such framework includes receiving a domain that is specified for identifying assets of a first customer belonging to a first distributed platform of the federation. The method determines whether the domain conflicts with a domain that is configured by a second distributed platform of the federation. The method then communicates with the first distributed platform (i) to configure the received domain when there is no conflict and (ii) to prevent the first distributed platform from configuring the received domain when there is a conflict.

Claims

1. A method for uniquely identifying assets in a federation comprising a plurality of distributed platforms that each operate a set of servers for serving at least some of said assets, the method comprising:

at a first distributed platform of the plurality of distributed platforms, providing an interface for a customer of the first distributed platform to specify an alias to identify assets of the customer that are to be served by a server that is operated by a second distributed platform;

verifying by the first distributed platform that said alias is unique with respect to other aliases that have been configured to identify assets of other customers whose assets are served by the set of servers operated by the second distributed platform;

configuring said alias into a traffic management server of the first distributed platform to identify assets of said customer when said alias is unique relative to the other aliases that have been configured to identify the assets that are served by the set of servers operated by the second distributed platform; and

preventing configuration of said alias when said alias is not unique relative to the other aliases that have been configured to identify the assets that are served by the set of servers operated by the second distributed platform.

2. The method of claim 1, wherein said alias maps a domain that is custom specified by the customer to a domain of the first distributed platform.

3. The method of claim 1, wherein said alias maps a domain that is custom specified by the customer to a domain of the federation.

4. The method of claim 1, wherein verifying that said alias is unique comprises the first distributed platform communicating the alias to the second distributed platform for the second distributed platform to verify uniqueness of said alias relative to aliases that have been configured to identify assets of customers whose assets are served by the set of servers operated by the second distributed platform.

5. The method of claim 4, wherein verifying that said alias is unique further comprises the first distributed platform communicating the alias to each of the plurality of distributed platforms of the federation for each of the plurality of distributed platform to verify uniqueness of said alias relative to aliases that each distributed platform has configured to identify assets that are served by the set of servers operated by the distributed platform.

6. The method of claim 4, wherein verifying that said alias is unique further comprises the first distributed platform verifying uniqueness of said alias relative to aliases that have been configured to identify assets served by the set of servers operated by the first distributed platform.

7. The method of claim 1, wherein verifying that said alias is unique comprises the first distributed platform communicating the alias to a conflict avoidance server of the federation for the conflict avoidance server to verify uniqueness of said alias relative to aliases that have been configured to identify assets of customers whose assets are served by the set of servers operated by the second distributed platform.

8. The method of claim 1, wherein verifying that said alias is unique comprises the first distributed platform communicating the alias to a conflict avoidance server of the federation for the conflict avoidance server to verify uniqueness of said alias relative to aliases that have been configured to identify assets of customers whose assets are served by any server operating in the federation.

9. The method of claim 1 further comprising resolving at a traffic management server of the first distributed platform, a request specifying said alias to identify the server of the second distributed platform that serves said asset of the customer.

10. The method of claim 1, wherein said alias is a CNAME entry for a Domain Name System (DNS) record.

11. A method for uniquely identifying assets in a federation comprising a plurality of distributed platforms that each operate a set of servers for serving at least some of said assets, the method comprising:

receiving a domain specified for use in identifying assets of a first customer belonging to a first distributed platform of the plurality of distributed platforms;

determining whether said domain conflicts with at least one domain that is already configured by a second distributed platform of the plurality of distributed platforms for use in identifying assets of a second customer whose assets are served by a server that is operated by the second distributed platform;

communicating with the first distributed platform to cause said first distributed platform to configure the received domain for use in identifying assets of the first customer when there is no conflict determined for the received domain; and

communicating with the first distributed platform to prevent said first distributed platform from configuring the received domain when the received domain conflicts with at least one domain that is already configured by the second distributed platform.

12. The method of claim 11 further comprising monitoring a plurality of domains that have been configured for use in identifying assets of a plurality of customers whose assets are served by servers of the plurality of distributed platforms participating in the federation.

13. The method of claim 11, wherein said received domain is specified for use with a CNAME record to alias to a different domain that is assigned by the first distributed platform.

14. The method of claim 11, wherein determining whether said domain conflicts comprises determining whether said domain conflicts with any domain that has been configured by any distributed platform of the plurality of distributed platforms.

15. The method of claim 11 further comprising receiving identification of server capacity to which said assets of the first customer are to be deployed.

16. The method of claim 15, wherein determining whether said domain conflicts comprises determining whether said domain conflicts with domains that have already been configured by a set of distributed platforms of the plurality of distributed platforms that provide the identified server capacity to which said assets of the first customer are to be deployed, wherein the set of distributed platforms comprises the second distributed platform.

17. The method of claim 11 further comprising identifying that said assets of the first customer are to be deployed to server capacity of the second distributed platform and a third distributed platform of the plurality of distributed platforms.

18. The method of claim 17 further comprising determining whether said domain conflicts with at least one domain that is already configured by the third distributed platform for use in identifying assets of a third customer whose assets are served by servers of the third distributed platform.

19. The method of claim 11 further comprising configuring a CNAME with said domain for use in identifying assets of the first customer.

20. The method of claim 11, wherein determining whether said domain conflicts comprises communicably coupling with the second distributed platform and submitting a request to the second distributed platform for the second distributed platform to determine whether said received domain conflicts with a domain that has been configured by the second distributed platform.

21. A method for uniquely identifying assets in a federation comprising a plurality of distributed platforms that each operate a set of servers for serving at least some of said assets, the method comprising:

assigning a first domain for use in identifying assets for a particular customer of a first distributed platform of the plurality of distributed platforms;

receiving a second domain to serve as an alias to the first domain;

determining whether the second domain conflicts with any domain that a second distributed platform of the plurality of distributed platforms has configured when said assets of the particular customer are to be deployed to server capacity of the second distributed platform; and

configuring said second domain to serve as an alias to the first domain when there is no conflict.

22. The method of claim 21, wherein determining whether the second domain conflicts comprises communicably coupling to a conflict avoidance server and submitting a request to configure said second domain to the conflict avoidance server for the conflict avoidance server to determine whether the second domain conflicts with any domain that the second distributed platform has configured.

23. The method of claim 22 further comprising receiving communication from the conflict avoidance server whether said second domain is conflicting.

24. The method of claim 23, wherein said assets are to be further deployed to server capacity of a third distributed platform of the plurality of distributed platform, and wherein the conflict avoidance server is further for determining and communicating whether the second domain conflicts with any domain that the third distributed platform has configured.

25. The method of claim 21, wherein determining whether the second domain conflicts comprises communicably coupling to the second distributed platform and submitting a request to configure the second domain to the second distributed platform for the second distributed platform to determine whether the second domain conflicts with any domain that the second distributed platform has configured.

26. The method of claim 25, wherein said assets are to be further deployed to server capacity of a third distributed platform of the plurality of distributed platform, and the method further comprising communicably coupling to the third distributed platform and submitting a request to configure the second domain to the third distributed platform for the third distributed platform to determine whether the second domain conflicts with any domain that the third distributed platform has configured.

27. The method of claim 26 further comprising receiving communication from the second and third distributed platforms whether said second domain is conflicting.

28. The method of claim 21, wherein determining whether the second domain conflicts comprises submitting a request to configure the second domain to a broker that forwards the request to the second distributed platform on behalf of the first distributed platform.