Method for modifying an SD-WAN using metric-based heat maps
Some embodiments provide a method for dynamically deploying a managed forwarding element (MFE) in a software-defined wide-area network (SD-WAN) for a particular geographic region across which multiple SaaS applications is distributed. The method determines, based on flow patterns for multiple flows destined for the multiple SaaS applications distributed across the particular geographic region, that an additional MFE is needed for the particular geographic region. The method configures the additional MFE to deploy at a particular location in the particular geographic region for forwarding the multiple flows to the multiple SaaS applications. The method provides, to a particular set of MFEs that connect a set of branch sites to the SD-WAN, a set of forwarding rules to direct the particular set of MFEs to use the additional MFE for forwarding subsequent data messages belonging to the multiple flows to the multiple SaaS applications.
1. A method of dynamically deploying a managed forwarding element (MFE) in a software-defined wide-area network (SD-WAN) for a particular geographic region across which a plurality of SaaS applications is distributed, the method comprising:
determining, based on flow patterns for a plurality of flows destined for the plurality of SaaS applications distributed across the particular geographic region, that an additional MFE is needed for the particular geographic region;
configuring the additional MFE to deploy at a particular location in the particular geographic region for forwarding the plurality of flows to the plurality of SaaS applications; and
providing, to a particular set of MFEs that connect a set of branch sites to the SD-WAN, a set of forwarding rules to direct the particular set of MFEs to use the additional MFE for forwarding subsequent data messages belonging to the plurality of flows to the plurality of SaaS applications.
2. The method of claim 1 , wherein determining that the additional MFE is needed for the particular geographic region based on flow patterns for the plurality of flows destined for the plurality of SaaS applications comprises receiving a plurality of quality of experience (QoE) scores associated with the plurality of SaaS applications from a particular compute machine that collects QoE metrics from existing MFEs connected by the SD-WAN.
3. The method of claim 2 , wherein the method is performed by a management and control server, wherein the particular compute machine consolidates the collected QoE metrics to compute the plurality of QoE scores to provide to the management and control server for analysis.
4. The method of claim 3 , wherein in addition to the QoE metrics, the particular compute machine collects location context associated with destination network addresses of the plurality of SaaS applications to provide to the management and control server along with the QoE scores.
5. The method of claim 4 further comprising using the location context (i) to identify one or more groups of geographically proximate destination network addresses and (ii) to identify centroids for each of the one or more identified groups of destination network addresses.
6. The method of claim 1 , wherein configuring the additional MFE to deploy at the particular location in the particular geographic region for forwarding the plurality of flows to the plurality of SaaS applications further comprises:
performing a proximity scoping operation to identify a set of potential locations at which to deploy the additional MFE; and
selecting, from the set of potential locations, the particular location.
7. The method of claim 6 , wherein the particular location is selected from the set of potential locations based on an operation for identifying a capacitated P-center, wherein the capacitated P-center comprises the particular location.
8. The method of claim 1 , wherein configuring the additional MFE to deploy at the particular location in the particular geographic region for forwarding the plurality of flows to the plurality of SaaS applications further comprises (i) registering the additional MFE with a management and control server for the SD-WAN, and (ii) deploying the additional MFE at the particular location.
9. The method of claim 1 , wherein:
the plurality of flows is a first plurality of flows;
the additional MFE is a first MFE;
the set of forwarding rules is a first set of forwarding rules; and
the set of edge routers use a second MFE to forward data messages belonging to a second plurality of flows according to a second set of forwarding rules.
10. The method of claim 9 , wherein the second set of forwarding rules comprises default forwarding rules and the second MFE comprises a default MFE.
11. The non-transitory machine readable medium of claim 9 , wherein the second set of forwarding rules comprises default forwarding rules and the second MFE comprises a default MFE.
12. The method of claim 1 , wherein:
the additional MFE comprises a cloud gateway router; and
the particular set of MFEs comprises a set of edge routers.
13. A non-transitory machine readable medium storing a program for execution by a set of processing units, the program for dynamically deploying a managed forwarding element (MFE) in a software-defined wide-area network (SD-WAN) for a particular geographic region across which a plurality of SaaS applications is distributed, the program comprising sets of instructions for:
determining, based on flow patterns for a plurality of flows destined for the plurality of SaaS applications distributed across the particular geographic region, that an additional MFE is needed for the particular geographic region;
configuring the additional MFE to deploy at a particular location in the particular geographic region for forwarding the plurality of flows to the plurality of SaaS applications; and
providing, to a particular set of MFEs that connect a set of branch sites to the SD-WAN, a set of forwarding rules to direct the particular set of MFEs to use the additional MFE for forwarding subsequent data messages belonging to the plurality of flows to the plurality of SaaS applications.
14. The non-transitory machine readable medium of claim 13 , wherein the set of instructions for determining that the additional MFE is needed for the particular geographic region based on flow patterns for the plurality of flows destined for the plurality of SaaS applications comprises a set of instructions for receiving a plurality of quality of experience (QoE) scores associated with the plurality of SaaS applications from a particular compute machine that collects QoE metrics from existing MFEs connected by the SD-WAN.
15. The non-transitory machine readable medium of claim 14 , wherein the method is performed by a management and control server, wherein the particular compute machine consolidates the collected QoE metrics to compute the plurality of QoE scores to provide to the management and control server for analysis.
16. The non-transitory machine readable medium of claim 15 , wherein:
in addition to the QoE metrics, the particular compute machine collects location context associated with destination network addresses of the plurality of SaaS applications to provide to the management and control server along with the QoE scores; and
the program further comprises a set of instructions for using the location context (i) to identify one or more groups of geographically proximate destination network addresses and (ii) to identify centroids for each of the one or more identified groups of destination network addresses.
17. The non-transitory machine readable medium of claim 13 , wherein the set of instructions for configuring the additional MFE to deploy at the particular location in the particular geographic region for forwarding the plurality of flows to the plurality of SaaS applications further comprises sets of instructions for:
performing a proximity scoping operation to identify a set of potential locations at which to deploy the additional MFE; and
selecting, from the set of potential locations, the particular location based on an operation for identifying a capacitated P-center, wherein the capacitated P-center comprises the particular location.
18. The non-transitory machine readable medium of claim 13 , wherein the set of instructions for configuring the additional MFE to deploy at the particular location in the particular geographic region for forwarding the plurality of flows to the plurality of SaaS applications further comprises a set of instructions for (i) registering the additional MFE with a management and control server for the SD-WAN, and (ii) deploying the additional MFE at the particular location.
19. The non-transitory machine readable medium of claim 13 , wherein:
the plurality of flows is a first plurality of flows;
the additional MFE is a first MFE;
the set of forwarding rules is a first set of forwarding rules; and
the set of edge routers use a second MFE to forward data messages belonging to a second plurality of flows according to a second set of forwarding rules.
20. The method of claim 13 , wherein:
the additional MFE comprises a cloud gateway router; and
the particular set of MFEs comprises a set of edge routers.