IP Library Granted Patent US 9,391,859
Granted Patent B2
US 9,391,859 · App. 14/769,310 · Granted Jul 12, 2016

Service coordination for a data center

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,391,859
App. No.
14/769,310
Granted
Jul 12, 2016
Kind
B2
Abstract

According to an example, a service coordination apparatus may include a processor that is to determine whether each GLB node-pair in a node-pair state table is at a normal state after receiving a DNS request. If a GLB node-pair in the node-pair state table is not at the normal state, a second DNS response may be sent to a node sending the DNS request according to a DNS parsing list. If each GLB node-pair in the node-pair state table is at the normal state, a proximity list may be inquired. If a record corresponding to the DNS request is searched out from the proximity list, a first DNS response may be sent to the node sending the DNS request according to the searched out record. If not, a second DNS response may be sent to the node sending the DNS request according to the DNS parsing list.

Claims (43)

1. A service coordination apparatus for a data center, said apparatus comprising:

a processor; and

a storage that is to store a node-pair state table, a domain name system (DNS) parsing list, and a proximity list;

wherein the processor is to:

determine whether each global load balancing (GLB) node-pair in the node-pair state table is at a normal state after receiving a DNS request;

in response to at least one GLB node-pair in the node-pair state table not being at the normal state, send a second DNS response to a node that sent the DNS request according to the DNS parsing list;

in response to each GLB node-pair in the node-pair state table being at the normal state, inquire the proximity list;

in response to a record corresponding to the DNS request being searched out from the proximity list, send a first DNS response to the node that sent the DNS request according to the searched out record; and

in response to no record corresponding to the DNS request being searched out from the proximity list, send a second DNS response to the node that sent the DNS request according to the DNS parsing list.

2. The service coordination apparatus of claim 1 , wherein the processor is further to:

monitor a state of a GLB node-pair comprising a pair of GLB devices; and

update the node-pair state table according to the state of the GLB node-pair.

3. The service coordination apparatus of claim 1 , wherein the second DNS response carries a time to live (TTL) value and wherein the TTL value is smaller than a preset value.

4. The service coordination apparatus of claim 1 , wherein the processor is further to:

in response to no record corresponding to the DNS request being searched out from the proximity list, send a detection instruction to an opposite GLB device in the GLB node-pair having the GLB device to request the opposite GLB device to initiate a proximity detection for the node that send the DNS request;

initiate a proximity detection for the node that sent the DNS request, and store a current detection result in the proximity list;

synchronize the current detection result to the opposite GLB device;

compare the current detection result with a detection result returned by the opposite GLB device; and

store one of the current detection result and the detection result returned by the opposite GLB device in the proximity list.

5. The service coordination apparatus of claim 4 , wherein the current detection result is synchronized to the opposite GLB device through use of a no acknowledgement mode.

6. The service coordination apparatus of claim 4 , wherein the processor is further to regularly synchronize detection results stored in the proximity list to the opposite GLB device in batch, and send an acknowledgement message to the opposite GLB device after receipt of the detection results synchronized by the opposite GLB device in batch.

7. The service coordination apparatus of claim 1 , wherein the machine readable instructions are further to cause the processor to synchronize a DNS parsing relationship in the DNS parsing list to the opposite GLB device, and store a DNS parsing relationship synchronized by the opposite GLB device in the DNS parsing list.

8. A service coordination method for a data center, said method comprising:

determining, by a processor, whether each global load balancing (GLB) node-pair in a node-pair state table is at a normal state after receiving a DNS request;

in response to at least one GLB node-pair in the node-pair state table not being at the normal state, sending a second DNS response to a node that sent the DNS request according to a domain name system (DNS) parsing list;

in response to each GLB node-pair in the node-pair state table being at the normal state, inquiring a proximity list;

in response to a record corresponding to the DNS request being searched out from the proximity list, sending a first DNS response to the node that sent the DNS request according to the searched out record; and

in response to no record corresponding to the DNS request being searched out from the proximity list, sending a second DNS response to the node that sent the DNS request according to the DNS parsing list.

9. The service coordination method of claim 8 , further comprising:

monitoring a state of the GLB node-pair comprising a pair of GLB devices; and

updating the node-pair state table according to the state of the GLB node-pair.

10. The service coordination method of claim 8 , wherein the second DNS carries a time to live (TTL) value and wherein the TTL value is smaller than a preset value.

11. The service coordination method of claim 8 , further comprising:

in response to no record corresponding to the DNS request being searched out from the proximity list,

sending a detecting instruction to an opposite GLB device comprised in the GLB node-pair having the GLB device to request the opposite GLB device to initiate a proximity detection for the node that sent the DNS request;

initiating a proximity detection for the node that sent the DNS request, and storing a current detection result in the proximity list;

synchronizing the current detection result to the opposite GLB device;

comparing the current detection result with a detection result returned by the opposite GLB device; and storing a best detection result in the proximity list.

12. The service coordination method of claim 11 , further comprising using a no acknowledgement mode to synchronize the current detection result to the opposite GLB device.

13. The service coordination method of claim 11 , further comprising:

regularly synchronizing detection results stored in the proximity list to the opposite GLB device in batch, and sending an acknowledgement message to the opposite GLB device after receiving detection results synchronized by the opposite GLB device in batch.

14. The service coordination method of claim 8 , further comprising:

synchronizing a DNS parsing relationship in the DNS parsing list to the opposite GLB device, and storing a DNS parsing relationship synchronized by the opposite GLB device in the DNS parsing list.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 22, 2016
From: H3C TECHNOLOGIES CO., LTD.; HANGZHOU H3C TECHNOLOGIES CO., LTD.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 039767/0263 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 3, 2015
From: HUANG, FENGXIAN; SUN, SONGER
To: HANGZHOU H3C TECHNOLOGIES CO., LTD.
Reel/Frame 036486/0359 →