Maintenance unit architecture for a scalable internet engine

• US 20050080891A1
• Filed: 08/30/2004
• Published: 04/14/2005
• Est. Priority Date: 08/28/2003
• Status: Abandoned Application

• Current Assignee: RPX Corporation
• Original Assignee: RPX Corporation
• Inventors: Cauthron, David M.
• Application Number:
  US10/929,776
• Publication Number:
  US 20050080891A1
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: G06F 11/2023 Failover techniques
• CPC Class Codes: G06F 11/2028 eliminating a faulty processor or activating a spare
• CPC Class Codes: G06F 11/2033 switching over of hardware resources
• CPC Class Codes: G06F 11/2035 without idle spare hardware
• CPC Class Codes: G06F 11/2041 with more than one idle spare processing component
• CPC Class Codes: G06F 11/2046 where the redundant components share persistent storage G06F11/2043 takes precedence
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: H04L 61/5014 using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
• 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/1017 based on a round robin mechanism
• CPC Class Codes: H04L 67/1029 using data related to the state of servers by a load balancer
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

A scalable Internet engine that dynamically reassigns server operations in the event of a failure of an ADSS (Adaptive Data Storage System) server. A first and a second ADSS server mirror each other and include corresponding databases with redundant data, domain host control protocol servers, XML interfaces and watchdog timers. The ADSS servers are communicatively coupled to at least one engine operating system and a storage switch; the storage switch being coupled to at least one storage element. The second ADSS server detects, via a heartbeat monitoring algorithm, the failure of the first ADSS server and automatically initiates a fail over action to switch over functions to the second ADSS server. The architecture also includes a supervisory data management arrangement that includes a plurality of reconfigurable blade servers coupled to a star configured array of data management units.

Claims

1. An architecture for a scalable Internet engine for providing dynamic reassignment of server operations in the event of a failure of a server, the architecture comprising:

at least one blade server operatively connected to an ethernet switching arrangement;

a first active data storage system (ADSS) server programmatically coupled to the at least one blade server via the ethernet switching arrangement, the first ADSS server comprising;

a first database adapted to interface with a first internet protocol (IP) address server adapted to assign IP addresses within the architecture and a first ADSS module adapted to provide a directory service to a user; and

a first XML interface daemon adapted to interface between an engine operating system and the first ADSS module;

a second active data storage system (ADSS) server programmatically coupled to the at least one blade server via the ethernet switching arrangement, the second ADSS server comprising;

a second database adapted to interface with a second internet protocol (IP) address server adapted to assign IP addresses within the architecture upon failure of the first ADSS server, the second database also adapted to interface with a second ADSS module adapted to provide the directory service to the user, wherein the second database is programmatically coupled to the first database and includes redundant information from the first database; and

a second XML interface daemon adapted to interface between the second ADSS module and the engine operating system, wherein the second ADSS server is adapted to detect a failure in the first ADSS server, via a heartbeat monitoring circuit connected to the first ADSS server, and initiate a failover action that switchovers the functions of the first ADSS server to the second ADSS server;

at least one supervisory data management arrangement programmatically coupled to the engine operating system and adapted to be responsive to the first and second ADSS modules;

a storage switch programmatically coupled to the first and second ADSS servers; and

a disk storage arrangement coupled to the storage switch.

2. The architecture of claim 1, wherein the first and second IP address servers utilize a communications protocol selected from the group consisting of a Dynamic Host Configuration Protocol (DHCP) and a Bootstrap Protocol (BOOTP).

3. The architecture of claim 1, wherein the first and second databases store target and initiator device addresses, available volume locations and storage mapping information.

4. The architecture of claim 1, wherein each of the first and second ADSS servers further include a watchdog timing circuit, respectively, to reinitiate the server.

5. The architecture of claim 1, wherein the supervisory data management arrangement is adapted to process commands from the first and second ADSS servers to alter mapping to a plurality of slave ADSS servers.

6. The architecture of claim 1, wherein the supervisory data management arrangement comprises a supervisory data management unit (SMU) that interfaces with a plurality of data management units (DMU) in a star configuration, wherein each DMU interfaces with a plurality of reconfigurable blade servers.

7. The architecture of claim 1, further comprising a plurality of slave ADSS servers that are communicatively connected to and controlled by the first and second ADSS servers, wherein the slave ADSS servers are adapted to service virtual volume duties of the architecture via a round robin scheme.

8. The architecture of claim 1, further comprising a plurality of ADSS slave servers adapted to visualize any client blade and any RAID storage unit storing virtual volumes such that the ADSS slave servers are adapted to service any client blade, wherein the plurality of ADSS slave servers increase the combined bandwidth of the architecture so as to achieve distributed virtualization.

9. The architecture of claim 8, wherein any client blade is adapted to be mapped to any ADSS slave server on demand as a function of a predefined condition that includes a failover and a redistribution of load.

10. The architecture of claim 1, wherein the ADSS modules are further adapted to automate management of user data and facilitate a single log-on process so as to permit access to authorized resources throughout the architecture.

11. A supervisory data management arrangement adapted to interact within the architecture of a scalable Internet engine, the supervisory data management arrangement comprising:

a plurality of reconfigurable blade servers adapted to interface with data management units (DMUs), each of said blade servers adapted to monitor health, control and power functions and switch between individual blades within each blade server in response to a command from an input/output (I/O) device;

a plurality of data management units (DMUs), each data management unit adapted to interface with at least one blade server and to control and monitor various blade functions, the data management unit further adapted to arbitrate management communications to and from the blade server via a management bus and an I/O bus; and

a supervisory data management unit (SMU) adapted to interface with the data management units in a star configuration at the management bus and the I/O bus connection, wherein the SMU is adapted to communicate with the DMUs via commands transmitted via management connections to the DMUs.

12. The data management arrangement of claim 11, wherein each blade within each reconfigurable blade server is connected to a communications bus and is adapted to electronically disengage from the communications bus upon receipt of a signal to release all blades, and wherein the release signal is broadcast on a backplane supporting the blades.

13. The data management arrangement of claim 12, wherein a selected blade is adapted to electronically engage the communications bus after all the blades are released from the communications bus.

14. The data management arrangement of claim 11, wherein the SMU further comprises a first output configured for I/O devices and a second output configured for Ethernet management.

15. The data management arrangement of claim 11, wherein each of the blade servers comprises a plurality of blades, each of the blades comprising a microcontroller mounted on a circuit board adapted to monitor health of the circuit board, store status of the blade on a rotating log, report blade status when polled and accept commands for a plurality of blade functions.

16. The data management arrangement of claim 11, wherein each DMU is adapted to monitor the health and control the power supply function of the blades.

17. The data management arrangement of claim 16, wherein each DMU is further adapted to switch between individual blades within the blade server in response to a command from an I/O device.

18. An architecture for a scalable internet engine for providing dynamic reassignment of server operations in the event of a redistribution of a load, the architecture comprising:

at least one blade server operatively connected to an ethernet switching arrangement, the blade server comprised of a plurality of individual blades;

a first active data storage system (ADSS) server programmatically coupled to the at least one blade server via the ethernet switching arrangement, the first ADSS server including a first database that interfaces with an first internet protocol (IP) address server and a first ADSS module that provides a directory service to a user, and a first XML interface daemon that interfaces between an engine operating system and the first ADSS module;

a second active data storage system (ADSS) server programmatically coupled to the at least one blade server via the ethernet switching arrangement, the second ADSS server including a second database that interfaces with a second IP address server that assigns IP addresses upon failure of the first ADSS server, the second database adapted to interface with a second ADSS module and to interface with the first database so as to include redundant information from the first database, and a second XML interface daemon that interfaces between the second ADSS module and the engine operating system;

at least one supervisory data management arrangement programmatically coupled to the engine operating system and adapted to be responsive to the first and second ADSS modules;

a storage switch programmatically coupled to the first and second ADSS servers;

a plurality of disk storage units coupled to the storage switch; and

a plurality of slave ADSS modules programmatically coupled to the supervisory data management arrangement, each of the ADSS modules adapted to visualize the disk storage units and the individual blades, wherein the ADSS servers are adapted to provide distributed virtualization within the architecture by reconfiguring the mapping from between a first blade and a first slave ADSS module to between the first blade to a second slave ADSS module in response to an overload condition on any of the slave ADSS modules.

19. The architecture of claim 18, wherein the IP address servers are configured to utilize extended fields in the DHCP standard to transmit the iSCSI parameters to a selected individual blade so as to find the associated ADSS server that will service the disk and the log-in authentication needs of the individual blade.

20. The architecture of claim 18, wherein the supervisory data management arrangement is comprised of a plurality of reconfigurable blade servers, each blade within each reconfigurable server is supported on a backplane and is adapted to electronically disengage from a communications bus upon receipt of a signal to release all blades, wherein a selected blade is adapted to electronically engage the communications bus after all the blades are released from the communications bus.