Distributed database in software driven networks

• US 10,002,141 B2
• Filed: 06/30/2014
• Issued: 06/19/2018
• Est. Priority Date: 09/25/2012
• Status: Active Grant

• Current Assignee: A10 Networks Incorporated
• Original Assignee: A10 Networks Incorporated
• Inventors: Jalan, Rajkumar, Kamat, Gurudeep, Sankar, Swaminathan, Karampurwala, Hasnain
• Primary Examiner(s): Sison, June
• Assistant Examiner(s): NGUYEN, STEVEN C
• Application Number:
  US14/320,420
• Publication Number:
  US 20160042014A1
• Time in Patent Office: 1,450 Days
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/037 Routes obligatorily traversing service-related nodes
• CPC Class Codes: H04L 67/1012 based on compliance of requirements or conditions with available server resources
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

Provided are methods and systems for implementing a distributed database in a data network. The method comprises receiving node data associated with one or more nodes of a plurality of nodes, updating the distributed database and replicating the distributed database to each of the plurality of nodes. The plurality of nodes comprises one or more cluster device, a cluster master, a traffic classification engine, a service node, and an orchestrator. The node data comprises node health, a number of total connections, node processing unit utilization, node memory status, destination server address, destination server capacity, destination server network connectivity, node dynamic state, node responsiveness. The distributed database comprises tables containing traffic map, node health information, traffic classification mapping, and service policy.

Claims

1. A computer-implemented method for implementing a distributed database in a data network, the method comprising:

receiving node data associated with one or more nodes of a plurality of nodes, the plurality of nodes being communicatively coupled to a software-driven network (SDN), the plurality of nodes fulfilling service requests, the plurality of nodes including at least one or more traffic classification engines and a plurality of service nodes, wherein the receiving the node data includes;

connecting, by each of the one or more traffic classification engines and each of the plurality of service nodes, to the distributed database, the distributed database being maintained by a node of the one or more nodes;

updating tables in the distributed database by each of the one or more traffic classification engines, wherein each of the one or more traffic classification engines updates tables containing records relevant to each of the one or more traffic classification engines, wherein the records relevant to each of the one or more traffic classification engines include at least traffic classification data; and

updating the tables in the distributed database by each of the plurality of service nodes, wherein each of the plurality of service nodes updates tables containing records relevant to each of the plurality of service nodes, wherein the records relevant to each of the plurality of service nodes include at least service policies of one or more of the plurality of service nodes;

updating the distributed database using the node data to provide an updated distributed database;

initiating, by the node of the one or more nodes maintaining the distributed database, replication of the updated distributed database to each of the one or more traffic classification engines and each of the plurality of service nodes;

getting the node data from the distributed database;

generating a service policy using the node data; and

providing the service policy to an SDN controller, the SDN controller bringing up a new node when a load of the data network increases and bringing down an existing node of the plurality of nodes when the load of the data network decreases, using the service policy.

2. The method of claim 1, wherein replicating the distributed database comprises sending a notification to the one or more nodes of the plurality of nodes.

3. The method of claim 2, further comprising:

receiving a piece of data from the updated distributed database; and

updating, based on the received piece of data, the updated distributed database.

4. The method of claim 1, wherein the node data comprises one or more of the following:

node health, a number of total connections, node processing unit utilization, node memory status, destination server address, destination server capacity, destination server network connectivity, node dynamic state, and node responsiveness.

5. The method of claim 1, wherein the distributed database comprises tables containing traffic maps.

6. The method of claim 5, wherein updating the distributed database comprises updating the tables containing the traffic maps.

7. The method of claim 1, wherein the distributed database comprises tables containing service policies.

8. The method of claim 1, wherein the distributed database comprises tables containing node health information.

9. The method of claim 8, wherein updating the distributed database comprises updating the tables containing the node health information.

10. The method of claim 1, wherein the distributed database comprises tables containing traffic classification mapping.

11. The method of claim 10, wherein the updating of the distributed database comprises updating the tables containing the traffic classification mapping.

12. The method of claim 1, wherein the plurality of nodes include one or more cluster devices, one or more service nodes, a cluster master, a traffic classification engine, and an orchestrator.

13. The method of claim 12, wherein receiving node data, updating the distributed database, and replicating the updated distributed database is carried out by the cluster master.

14. A system for implementing a distributed database in a data network, the system comprising:

a processor executing instructions in communication with a memory storing instructions to provide;

a plurality of nodes, the plurality of nodes fulfilling service requests; and

a cluster master configured to;

receive node data associated with one or more nodes of the plurality of nodes, the plurality of nodes being communicatively coupled to a software-driven network (SDN), the plurality of nodes including at least one or more traffic classification engines and a plurality of service nodes, wherein the receiving the node data includes;

connecting, by each of the one or more traffic classification engines and each of the plurality of service nodes, to the distributed database, the distributed database being maintained by a node of the one or more nodes;

updating tables in the distributed database by each of the one or more traffic classification engines, wherein each of the one or more traffic classification engines updates tables containing records relevant to each of the one or more traffic classification engines, wherein the records relevant to each of the one or more traffic classification engines include at least traffic classification data; and

updating the tables in the distributed database by each of the plurality of service nodes, wherein each of the plurality of service nodes updates tables containing records relevant to each of the plurality of service nodes, wherein the records relevant to each of the plurality of service nodes include at least service policies of one or more of the plurality of service nodes;

update the distributed database using the node data to provide an updated distributed database;

initiate, by the node of the one or more nodes maintaining the distributed database, replication of the updated distributed database to each of the one or more traffic classification engines and each of the plurality of service nodes;

get the node data from the distributed database;

generate a service policy using the node data;

bring up a new node when a load of the data network increases, using the service policy and;

bring down an existing node of the plurality of nodes when the load of the data network decreases, using the service policy.

15. The system of claim 14, wherein the node data comprises one or more of the following:

node health, a number of total connections, node processing unit utilization, node memory status, destination server address, destination server capacity, destination server network connectivity, node dynamic state, and node responsiveness.

16. The system of claim 14, wherein the distributed database comprises tables containing traffic maps.

17. The system of claim 14, wherein the distributed database comprises tables containing service policies.

18. The system of claim 14, wherein the distributed database comprises tables containing node health information.

19. The system of claim 14, wherein the distributed database comprises tables containing traffic classification mapping.

20. The system of claim 14, wherein the plurality of nodes include one or more cluster devices, one or more service nodes, a traffic classification engine, and an orchestrator.

21. The system of claim 14, wherein the cluster master is further configured to receive node health information from the one or more nodes while replicating the distributed data base to the one or more nodes.

22. A non-transitory computer-readable storage medium having embodied thereon a program, the program being executable by one or more processors to perform a method for implementing a distributed database in a data network, the method comprising:

receiving node data associated with one or more nodes of a plurality of nodes, the plurality of nodes being communicatively coupled to a software-driven network (SDN), the plurality of nodes fulfilling service requests, the plurality of nodes including at least one or more traffic classification engines and a plurality of service nodes, wherein the receiving the node data includes;

connecting, by each of the one or more traffic classification engines and each of the plurality of service nodes, to the distributed database, the distributed database being maintained by a node of the one or more nodes;

updating tables in the distributed database by each of the one or more traffic classification engines, wherein each of the one or more traffic classification engines updates tables containing records relevant to each of the one or more traffic classification engines, wherein the records relevant to each of the one or more traffic classification engines include at least traffic classification data; and

updating the tables in the distributed database by each of the plurality of service nodes, wherein each of the plurality of service nodes updates tables containing records relevant to each of the plurality of service nodes, wherein the records relevant to each of the plurality of service nodes include at least service policies of one or more of the plurality of service nodes;

updating the distributed database using the nodes data to provide an updated distributed database;

initiating, by the node of the one or more nodes maintaining the distributed database, replication of the updated distributed database to each of the one or more traffic classification engines and each of the plurality of service nodes;

getting the node data from the distributed database;

generating a service policy using the nodes data; and

providing the service policy to an SDN controller, the SDN controller bringing up a new node when a load of the data network increases and bringing down an existing node of the plurality of nodes when the load of the data network decreases, using the service policy.

23. The non-transitory computer-readable storage medium of claim 22, wherein the node data comprises one or more of the following:

node health, a number of total connections, node processing unit utilization, node memory status, destination server address, destination server capacity, destination server network connectivity, node dynamic state, and node responsiveness.

24. The non-transitory computer-readable storage medium of claim 23, wherein the distributed database comprises tables containing one or more of the following:

traffic maps, service policies, node health information, and traffic classification mapping.