Back to results
US 8,805,974 B2Granted
Using static routing to optimize resource utilization
AssigneeGo Daddy Operating Company, LLC
InventorGreg Schwimer
Life of this patent
Estimating the term…
Abstract
Systems and methods for optimizing resource utilization among a group of hardware resources using static routing by migrating a hosted account and an associated IP address from a first network resource to a second network resource in response to a resource utilization change.
Claims20
A method comprising the steps of:
- A) binding, by one or more server computers in a server cluster communicatively coupled to a network, an Internet Protocol (IP) address to a website hosted on a source server computer within said server cluster;
- B) assigning, by said one or more server computers, said IP address to a loopback interface without binding said IP address to a physical network interface on said source server computer;
- C) writing, by said one or more server computers, to a routing table stored in a router servicing said server cluster, a static route to said IP address via said loopback interface on said source server computer;
- D) monitoring, by said one or more server computers, via a plurality of metrics from said router, said loopback interface and said IP address, a steady state of a network resource utilization by said website on said source server computer;
- E) responsive to said plurality of metrics reaching an overload state outside of said steady state, generating, by said one or more server computers, an alert of said overload state
- F) responsive to said alert, identifying a destination server computer within said server cluster, migrating, by said one or more server computers, said website, said IP address and said loopback interface to said destination server computer without requiring an update of one or more Domain Name System (DNS) entries for said website;
- and
- G) updating, by said one or more server computers, said static route in said routing table to direct network traffic for said website to said IP address via said loopback interface on said destination server computer.
5 more elements
A system comprising:
- A) a server cluster communicatively coupled to a network;
- B) a source server computer within said server cluster comprising a loopback interface and hosting a website accessible to one or more network components within said network via an Internet Protocol (IP) address;
- C) one or more server computers within said server cluster running a provisioning module configured to:
- i) bind said IP address to said website;
- ii) assign said IP address to said loopback interface without binding said IP address to a physical network interface on said source server computer;
- and
- iii) write, to a routing table stored in a router servicing said server cluster, a static route to said IP address via said loopback interface on said source server computer;
- and
- D) one or more of said one or more server computers within said server cluster running a network resource utilization module configured to:
- i) monitor, via a plurality of metrics from said router, said loopback interface and said IP address, a steady state of a network resource utilization by said website on said source server computer;
- ii) responsive to said plurality of metrics reaching an overload state outside of said steady state, generate an alert of said overload state;
- E) one or more of said one or more server computers within said server cluster running a migration module configured to:
- i) responsive to said alert, identify a destination server computer within said server cluster, migrate said website, said IP address and said loopback interface to said destination server computer without requiring an update of one or more Domain Name System (DNS) entries for said website;
- and
- ii) update said static route in said routing table to direct network traffic for said website to said IP address via said loopback interface on said destination server computer.
12 more elements
Dependencies are inferred from the claim text.