Control plane isolation for software defined network routing services

Abstract

Techniques for avoiding single points of failure in routing components of an SDN are disclosed. In some aspects, control nodes that provide routing management services are assigned zone identifiers. The control nodes having one zone identifier can be on separate processes and/or physical hardware from control nodes having a different zone identifier. Workloads, such as virtual machines or containers, can establish routing sessions such as Border Gateway Protocol as a Service (BGPaaS) routing sessions using different zone identifiers to ensure that separate control nodes provide routing management services for the primary and secondary compute nodes associated with a high availability service. These techniques in this way facilitate high availability by ensuring that a control node is not a single point of failure for the high availability service provided by the primary and secondary compute nodes.

What is claimed is: 
     
         1 . A method comprising:
 establishing, by a workload executable by one or more processors, based at least in part on a first zone identifier, a first routing session with a first control node of a first plurality of control nodes, the first zone identifier identifying the first plurality of control nodes; and   establishing, by the workload, based at least in part on a second zone identifier, a second routing session with a second control node of a second plurality of control nodes, the second zone identifier identifying the second plurality of control nodes, the second zone identifier different than the first zone identifier, wherein the first plurality control nodes are on different virtual or physical machines from the second plurality of control nodes.   
     
     
         2 . The method of  claim 1 ,
 wherein the workload comprises a virtual machine,   wherein the first routing session is associated with a first Internet Protocol (IP) address of the virtual machine, and   wherein the second routing session is associated with a second IP address of the virtual machine.   
     
     
         3 . The method of  claim 1 ,
 wherein establishing the first routing session comprises establishing a first Border Gateway Protocol as a Service (BGPaaS) routing session, and   wherein establishing the second routing session comprises establishing a second BGPaaS routing session.   
     
     
         4 . The method of  claim 3 ,
 wherein the first zone identifier comprises an attribute of a first BGPaaS configuration on the workload, and wherein the first zone identifier is determined from the first BGPaaS configuration to establish the first BGPaaS session; and   wherein the second zone identifier comprises an attribute of a second BGPaaS configuration on the workload, and wherein the second zone identifier is determined from the second BGPaaS configuration to establish the second BGPaaS session.   
     
     
         5 . The method of  claim 1 , further comprising:
 assigning the first zone identifier as an attribute of the first control node and communicating the first zone identifier to the workload; and   assigning the second zone identifier as an attribute of the second control node and communicating the second zone identifier to the workload.   
     
     
         6 . The method of  claim 1 , wherein the workload comprises a first workload, wherein the method further comprises:
 requesting, by a second workload, a third routing session, the third routing session associated with the first zone identifier;   selecting, based on load balancing the first plurality of control nodes, a third control node of the first plurality control nodes; and   establishing the third routing session with the third control node.   
     
     
         7 . The method of  claim 1 , further comprising:
 in response to detecting a failure of the first control node, migrating a routing management service of the first control node to a different control node of the first plurality of control nodes.   
     
     
         8 . A Software Defined Networking (SDN) system comprising:
 a first plurality of control nodes assigned a first zone identifier;   a second plurality of control nodes assigned a second zone identifier,   wherein the second zone identifier is different than the first zone identifier, and   wherein the first plurality of control nodes are on different virtual or physical machines from the second plurality of control nodes; and   a compute node hosting a workload configured to:
 establish, based at least in part on the first zone identifier, a first routing session with a first control node of the first plurality of control nodes, and 
 establish, based at least in part on the second zone identifier, a second routing session with a second control node of the first plurality of control nodes. 
   
     
     
         9 . The SDN system of  claim 8 ,
 wherein the workload comprises a virtual machine,   wherein the first routing session is associated with a first Internet Protocol (IP) address of the virtual machine, and   wherein the second routing session is associated with a second IP address of the virtual machine.   
     
     
         10 . The SDN system of  claim 8 ,
 wherein the first routing session comprises a first Border Gateway Protocol as a Service (BGPaaS) routing session, and   wherein the second routing session comprises a second BGPaaS routing session.   
     
     
         11 . The SDN system of  claim 10 ,
 wherein the first zone identifier comprises an attribute of a first BGPaaS configuration on the workload, and wherein the first zone identifier is determined from the first BGPaaS configuration to establish the first BGPaaS session; and   wherein the second zone identifier comprises an attribute of a second BGPaaS configuration on the workload, and wherein the second zone identifier is determined from the second BGPaaS configuration to establish the second BGPaaS session.   
     
     
         12 . The SDN system of  claim 8 , wherein the first control node is further configured to communicate the first zone identifier to the workload; and
 wherein the second control node is further configured to communicate the second zone identifier to the workload.   
     
     
         13 . The SDN system of  claim 8 , wherein the workload comprises a first workload, the SDN system further comprising:
 a second workload configured to request a third routing session, the third routing session associated with the first zone identifier, wherein in response to the request, the SDN system selects, based on load balancing the first plurality of control nodes, a third control node of the first plurality control nodes to establish the third routing session with the third control node.   
     
     
         14 . The SDN system of  claim 8 , wherein the SDN system is configured to, in response to detection of a failure of the first control node, migrate a routing management service of the first control node to a different control node of the first plurality of control nodes. 
     
     
         15 . The SDN system of  claim 8 , further comprising:
 a virtual router executing on the compute node, the virtual router configured to:   establish a third communication session with the first control node based, at least in part, on the first zone identifier, and   establish a fourth communication session with the second control node based, at least in part, on the second zone identifier.   
     
     
         16 . The SDN system of  claim 15 , wherein the third communication session comprises a first eXtensible Messaging and Presence Protocol (XMPP) session and wherein the fourth communication session comprises a second XMPP session. 
     
     
         17 . A method comprising:
 establishing, by a virtual router of a compute node based at least in part on a first zone identifier, a first communication session with a first control node of a first plurality of control nodes, the first zone identifier identifying the first plurality of control nodes, wherein the virtual router is configured to provide a first virtual network to a workload;   establishing, by the virtual router based at least in part on a second zone identifier, a second communication session with a second control node of a second plurality of control nodes, the second zone identifier identifying the second plurality of control nodes, the second zone identifier different than the first zone identifier, wherein the first plurality of control nodes are on different virtual or physical machines from the second plurality of control nodes.   
     
     
         18 . The method of  claim 17 ,
 wherein the first routing session is associated with a first Internet Protocol (IP) address of a virtual machine hosted on the compute node, and   wherein the second routing session is associated with a second IP address of the virtual machine.   
     
     
         19 . The method of  claim 17 ,
 wherein the first communication session comprises a first eXtensible Messaging and Presence Protocol (XMPP) session, and   wherein the second communication session comprises a second XMPP session.   
     
     
         20 . The method of  claim 17 , further comprising:
 assigning the first zone identifier as an attribute of the first control node;   communicating the first zone identifier to the virtual router;   assigning the second zone identifier as an attribute of the second control node; and   communicating the second zone identifier to the virtual router.