Orchestrated reconnect for client-unaware rolling of network nodes
Techniques for the transparent rolling of nodes in a cloud-delivered headend service without disrupting client traffic or making users aware of the various nodes in the system being rolled are described herein. The techniques may include receiving an indication that a first node of a network is to be rolled. Based at least in part on the indication, new connection requests may not be sent to the first intermediate node. Additionally, a client device having an existing connection through the first node may be identified. In some examples, a request may be sent to the client device to prompt the client device to establish a new connection. After determining that the new connection has been established such that the new connection flows through a second node of the network, the first node may be rolled.
1. A system comprising:
one or more processors; and
one or more non-transitory computer-readable media storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:
determining to refrain from servicing virtual private network (VPN) connection requests through a first intermediate node to reach termination nodes of a cloud-based VPN headend service;
sending, to a client device that has an existing VPN connection with a first termination node that passes through the first intermediate node, an indication to cause the client device to establish a new VPN connection without terminating the existing VPN connection;
causing the new VPN connection to be established between the client device and the first termination node or a second termination node through a second intermediate node; and
subsequent to the client device establishing the new VPN connection through the second intermediate node, removing the first intermediate node from service.
2. The system of claim 1 , wherein the indication to cause the client device to establish the new VPN connection includes at least one of a hostname or an internet protocol (IP) address that is associated with the second intermediate node.
3. The system of claim 1 , wherein:
the indication to establish the new VPN connection is sent to each client device of multiple client devices that have existing connections passing through the first intermediate node, and
removing the first intermediate node from service is based at least in part on determining that each one of the multiple client devices have established new connections through other intermediate nodes that are different from the first intermediate node.
4. The system of claim 1 , the operations further comprising at least one of:
updating the first intermediate node with a new version of software while the first intermediate node is removed from service; or
deploying the second intermediate node to replace the first intermediate node based at least in part on the first intermediate node being removed from service.
5. The system of claim 4 , wherein the first intermediate node is at least one of a load balancer node, a proxy node, or a headend node of the cloud-based VPN headend service.
6. The system of claim 1 , wherein the first intermediate node is associated with a first datacenter and the second intermediate node is associated with a second datacenter, the second datacenter located in a different geographical location than the first datacenter.
7. The system of claim 1 , the operations further comprising:
receiving, at a proxy node of the cloud-based VPN headend service, a connection request from the client device, the connection request indicating a request for the new VPN connection; and
based at least in part on the first intermediate node being removed from service, sending, from the proxy node, the connection request to the second intermediate node.
8. A method comprising:
determining to refrain from servicing virtual private network (VPN) connection requests through a first intermediate node to reach termination nodes of a cloud-based VPN headend service;
sending, to a client device that has an existing VPN connection with a first termination node that passes through the first intermediate node, an indication to cause the client device to establish a new VPN connection without terminating the existing VPN connection;
causing the new VPN connection to be established between the client device and the first termination node or a second termination node through a second intermediate node; and
subsequent to the client device establishing the new VPN connection through the second intermediate node, removing the first intermediate node from service.
9. The method of claim 8 , wherein the indication to cause the client device to establish the new VPN connection includes at least one of a hostname or an internet protocol (IP) address that is associated with the second intermediate node.
10. The method of claim 8 , wherein:
the indication to establish the new VPN connection is sent to each client device of multiple client devices that have existing connections passing through the first intermediate node, and
removing the first intermediate node from service is based at least in part on determining that each one of the multiple client devices have established new connections through other intermediate nodes that are different from the first intermediate node.
11. The method of claim 8 , further comprising at least one of:
updating the first intermediate node with a new version of software while the first intermediate node is removed from service; or
deploying the second intermediate node to replace the first intermediate node based at least in part on the first intermediate node being removed from service.
12. The method of claim 11 , wherein the first intermediate node is at least one of a load balancer node, a proxy node, or a headend node of the cloud-based VPN headend service.
13. The method of claim 8 , wherein the first intermediate node is associated with a first datacenter and the second intermediate node is associated with a second datacenter, the second datacenter located in a different geographical location than the first datacenter.
14. The method of claim 8 , further comprising:
receiving, at a proxy node of the cloud-based VPN headend service, a connection request from the client device, the connection request indicating a request for the new VPN connection; and
based at least in part on the first intermediate node being removed from service, sending, from the proxy node, the connection request to the second intermediate node.
15. One or more non-transitory computer-readable media storing computer executable instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:
determining to refrain from servicing virtual private network (VPN) connection requests through a first intermediate node to reach termination nodes of a cloud-based VPN headend service;
sending, to a client device that has an existing VPN connection with a first termination node that passes through the first intermediate node, an indication to cause the client device to establish a new VPN connection without terminating the existing VPN connection;
causing the new VPN connection to be established between the client device and the first termination node or a second termination node through a second intermediate node; and
subsequent to the client device establishing the new VPN connection through the second intermediate node, removing the first intermediate node from service.
16. The one or more non-transitory computer-readable media of claim 15 , wherein the indication to cause the client device to establish the new VPN connection includes at least one of a hostname or an internet protocol (IP) address that is associated with the second intermediate node.
17. The one or more non-transitory computer-readable media of claim 15 , wherein:
the indication to establish the new VPN connection is sent to each client device of multiple client devices that have existing connections passing through the first intermediate node, and
removing the first intermediate node from service is based at least in part on determining that each one of the multiple client devices have established new connections through other intermediate nodes that are different from the first intermediate node.
18. The one or more non-transitory computer-readable media of claim 15 , the operations further comprising at least one of:
updating the first intermediate node with a new version of software while the first intermediate node is removed from service; or
deploying the second intermediate node to replace the first intermediate node based at least in part on the first intermediate node being removed from service.
19. The one or more non-transitory computer-readable media of claim 18 , wherein the first intermediate node is at least one of a load balancer node, a proxy node, or a headend node of the cloud-based VPN headend service.
20. The one or more non-transitory computer-readable media of claim 15 , wherein the first intermediate node is associated with a first datacenter and the second intermediate node is associated with a second datacenter, the second datacenter located in a different geographical location than the first datacenter.
21. The system of claim 1 , the operations further comprising:
modifying a configuration of a load balancer disposed between client devices and termination nodes to cause the load balancer to refrain from sending new VPN connections to the first intermediate node; and
routing, by the load balancer, the new VPN connection to the second intermediate node based at least in part on configuration being modified.
22. The system of claim 1 , wherein:
sending the indication to cause the client device to establish the new VPN connection comprises sending, by the first termination node, a reconnect request to the client device, wherein the reconnect request causing the client device to establish the new VPN connection.