Dynamic establishment of application-specific network tunnels between network devices by an SDWAN controller

1. A method comprising:

receiving, by a Software-Defined Wide Area Network (SDWAN) controller associated with a private network, from a source edge associated with a first group of a plurality of groups of a plurality of network devices of the private network, a request to initiate a dynamic Virtual Private Network (VPN) link for a network session between the source edge and a destination edge responsive to network traffic of the source edge matching at least one SDWAN rule, wherein the destination edge is associated with a second group of the plurality of groups responsive to a dynamic VPN switch being enabled at the source edge and the destination edge;

receiving user configuration information through Representational State Transfer (REST) application programing interface (API);

based on the received request, for each of the source edge and the destination edge, and the user configurations received, determining, by the SDWAN controller, configuration information including VPN and SDWAN configuration information for generating the dynamic VPN link between the source edge and said destination edge and a specific role for the source edge and the destination edge as either hub or spoke by setting up Internet Protocol security (IPsec) tunnels, wherein the configuration information is determined based on a plurality of pre-configurable rules on the source edge, managed by the SDWAN controller, wherein at least one of the plurality of pre-configured rules is specific to a network application or a class of network applications; and

directing, by the SDWAN controller, the source edge and the destination edge to set up a VPN overlay tunnel in accordance with the determined configuration information by pushing the determined configuration information to each of the source edge and the destination edge.

2. The method of claim 1 , wherein the request is received by the SDWAN controller responsive to network traffic at the source edge matching the at least one of the plurality of pre-configured rules.

3. The method of claim 1 , wherein the network session is initiated by an end-point device associated with the source edge.

4. The method of claim 1 , wherein the SDWAN controller additionally determines Service Level Agreement (SLA) configuration information and pushes the SLA configuration information to each of the source edge and the destination edge.

5. The method of claim 1 , wherein the SDWAN controller determines the configuration information based on a destination Internet Protocol (IP) address associated with the network session.

6. The method of claim 1 , wherein the SDWAN controller tears down the VPN overlay tunnel when no network traffic is observed between the source edge and the destination edge via the VPN overlay tunnel for a pre-determined time period.

7. The method of claim 1 , wherein each group of the plurality of groups comprises a cluster of a subset of the plurality of network devices, which are located in a particular geographical location.

8. The method of claim 1 , wherein the plurality of network devices are network security devices and wherein the SDWAN controller is implemented within a management appliance that manages the plurality of network devices.

9. A non-transitory computer-readable storage medium embodying a set of instructions, which when executed by one or more processors of an Software-Defined Wide Area Network (SDWAN) controller associated with a private network, causes the one or more processors to perform a method comprising:

receiving from a receiving, by a Software-Defined Wide Area Network (SDWAN) controller associated with a private network, from a source edge associated with a first group of a plurality of groups of a plurality of network devices of the private network, a request to initiate a dynamic Virtual Private Network (VPN) link for a network session between the source edge and a destination edge, responsive to network traffic of the source edge matching at least one SDWAN rule, wherein the destination edge is associated with a second group of the plurality of groups responsive to a dynamic VPN switch being enabled at the source edge and the destination edge;

receiving user configuration information through Representational State Transfer (REST) application programing interface (API);

based on the received request, for each of the source edge and the destination edge, and the user configurations received, determining, by the SDWAN controller, configuration information including VPN and SDWAN configuration information for generating the dynamic VPN link between the source edge and said destination edge and a specific role for the source edge and the destination edge as either hub or spoke by setting up Internet Protocol security (IPsec) tunnels, wherein the configuration information is determined based on a plurality of pre-configurable rules on the source edge, managed by the SDWAN controller, wherein at least one of the plurality of pre-configured rules is specific to a network application or a class of network applications; and

directing, by the SDWAN controller, the source edge and the destination edge to set up a VPN overlay tunnel in accordance with the determined configuration information by pushing the determined configuration information to each of the source edge and the destination edge.

10. The non-transitory computer-readable storage medium of claim 9 , wherein the request is received by the SDWAN controller responsive to network traffic at the source edge matching the at least one of the plurality of pre-configured rules.

11. The non-transitory computer-readable storage medium of claim 9 , wherein the network session is initiated by an end-point device associated with the source edge.

12. The non-transitory computer-readable storage medium of claim 9 , wherein the SDWAN controller additionally determines Service Level Agreement (SLA) configuration information and pushes the SLA configuration information to each of the source edge and the destination edge.

13. The non-transitory computer-readable storage medium of claim 9 , wherein the SDWAN controller determines the configuration information based on a destination Internet Protocol (IP) address associated with the network session.

14. The non-transitory computer-readable storage medium of claim 9 , wherein the SDWAN controller tears down the VPN overlay tunnel when no network traffic is observed between the source edge and the destination edge via the VPN overlay tunnel for a pre-determined time period.

15. The non-transitory computer-readable storage medium of claim 9 , wherein each group of the plurality of groups comprises a cluster of a subset of the plurality of network devices, which are located in a particular geographical location.

16. The non-transitory computer-readable storage medium of claim 9 , wherein the plurality of network devices are network security devices and wherein the SDWAN controller is implemented within a management appliance that manages the plurality of network devices.

17. A system comprising:

a processing resource; and

a non-transitory computer-readable medium, coupled to the processing resource, having stored therein instructions that when executed by the processing resource cause the processing resource to:

receive, by a Software-Defined Wide Area Network (SDWAN) controller associated with a private network, from a source edge associated with a first group of a plurality of groups of a plurality of network devices of the private network, a request to initiate a dynamic Virtual Private Network (VPN) link for a network session between the source edge and a destination edge, responsive to network traffic of the source edge matching at least one SDWAN rule, wherein the destination edge is associated with a second group of the plurality of groups responsive to a dynamic VPN switch being enabled at the source edge and the destination edge;

receive user configuration information through Representational State Transfer (REST) application programing interface (API);

based on the received request, for each of the source edge and the destination edge, and the user configurations received, determine, by the SDWAN controller, configuration information including VPN and SDWAN configuration information for generating the dynamic VPN link between the source edge and said destination edge and a specific role for the source edge and the destination edge as either hub or spoke by setting up Internet Protocol security (IPsec) tunnels, wherein the configuration information is determined based on a plurality of pre-configurable rules on the source edge, managed by the SDWAN controller, wherein at least one of the plurality of pre-configured rules is specific to a network application or a class of network applications; and

direct, by the SDWAN controller, the source edge and the destination edge to set up a VPN overlay tunnel in accordance with the determined configuration information by pushing the determined configuration information to each of the source edge and the destination edge.

18. The system of claim 17 , wherein the request is received by the SDWAN controller responsive to network traffic at the source edge matching the at least one of the plurality of pre-configured rules.

19. The system of claim 17 , wherein the network session is initiated by an end-point device associated with the source edge.

20. The system of claim 17 , wherein the SDWAN controller additionally determines Service Level Agreement (SLA) configuration information and pushes the SLA configuration information to each of the source edge and the destination edge.

21. The system of claim 17 , wherein the SDWAN controller tears down the VPN overlay tunnel when no network traffic is observed between the source edge and the destination edge via the VPN overlay tunnel for a pre-determined time period.