Hybrid cloud computing network management with synchronization features across different cloud service providers
A network manager configures a first node to participate in a node cluster that spans at least a first cloud service provider and the second cloud service provider. The network manager configures a second node to participate in the node cluster. The network manager configures a third node to participate in the node cluster. The network manager initiates the first node as a virtual machine. The network manager initiates the second node as a containerized program. The network manager initiates the third node as a containerized program. The network manager sends messages into the first cloud serves and into the second cloud service to cause the containerized program of the second node and the containerized program of the third node to synchronize data such that the containerized program of the second node and the containerized program of the first node perform the same network security actions.
1. A computer-implemented method executed by one or more processors comprising:
configuring, by a network manager operating outside of a first cloud service provider and outside of a second cloud service provider that is logically distinct from the first cloud service provider and outside of a client network, a first node to participate in a node cluster that spans at least the first cloud service provider and the second cloud service provider, wherein the first node is hosted by the first cloud service provider, and wherein participating in the node cluster includes performing one or more network security actions on traffic between remote servers and the client network, the client network separate from the first and second cloud service providers and the remote servers remote from the client network and from the first and second cloud service providers;
configuring, by the network manager, a second node to participate in the node cluster, wherein the second node is hosted by the first cloud service provider;
configuring, by the network manager, a third node to participate in the node cluster, wherein the third node is hosted by the second cloud service provider communicably coupled to the first cloud service provider via computer networking;
initiating the first node as a virtual machine instance within a virtual machine environment of the first cloud service provider;
initiating the second node as a containerized program executing within an operating-system-level virtualization environment of the first cloud service provider;
initiating the third node as a second containerized program executing within a second operating-system-level virtualization environment of the second cloud service provider; and
sending, by the network manager, messages into the first cloud service and into the second cloud service to cause the containerized program of the second node and the containerized program of the third node to synchronize data such that the containerized program of the second node and the containerized program of the third node operate with the same configuration data to perform the same network security actions regardless of the cloud service to which they belong.
2. The method of claim 1 , wherein:
instantiating the first node as a virtual machine comprises invoking a virtual-machine application programming interface (API) configured to instantiate virtual machines; and
instantiating the second node as a containerized program comprises invoking a operating-system level API configured to launch operating-system-level execution.
3. The method of claim 1 , wherein the operating-system-level virtualization environment of the first cloud service provider is a DOCKER environment.
4. The method of claim 1 , the method further comprising synchronizing data between the first node and the second node within the first cloud service provider.
5. A system comprising:
one or more processors; and
memory storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:
configuring, by a network manager operating outside of a first cloud service provider and outside of a second cloud service provider that is logically distinct from the first cloud service provider and outside of a client network, a first node to participate in a node cluster that spans at least the first cloud service provider and the second cloud service provider, wherein the first node is hosted by the first cloud service provider, and wherein participating in the node cluster includes performing one or more network security actions on traffic between remote servers and the client network, the client network separate from the first and second cloud service providers and the remote servers remote from the client network and from the first and second cloud service providers;
configuring, by the network manager, a second node to participate in the node cluster, wherein the second node is hosted by the first cloud service provider;
configuring, by the network manager, a third node to participate in the node cluster, wherein the third node is hosted by the second cloud service provider communicably coupled to the first cloud service provider via computer networking;
initiating the first node as a virtual machine instance within a virtual machine environment of the first cloud service provider;
initiating the second node as a containerized program executing within an operating-system-level virtualization environment of the first cloud service provider;
initiating the third node as a second containerized program executing within a second operating-system-level virtualization environment of the second cloud service provider; and
sending, by the network manager, messages into the first cloud service and into the second cloud service to cause the containerized program of the second node and the containerized program of the third node to synchronize data such that the containerized program of the second node and the containerized program of the third node operate with the same configuration data to perform the same network security actions regardless of the cloud service to which they belong.
6. The system of claim 5 , wherein:
instantiating the first node as a virtual machine comprises invoking a virtual-machine application programming interface (API) configured to instantiate virtual machines; and
instantiating the second node as a containerized program comprises invoking a operating-system level API configured to launch operating-system-level execution.
7. The system of claim 5 , wherein the operating-system-level virtualization environment of the first cloud service provider is a DOCKER environment.
8. The system of claim 5 , the operations further comprising synchronizing data between the first node and the second node within the first cloud service provider.
9. A non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:
configuring, by a network manager operating outside of a first cloud service provider and outside of a second cloud service provider that is logically distinct from the first cloud service provider and outside of a client network, a first node to participate in a node cluster that spans at least the first cloud service provider and the second cloud service provider, wherein the first node is hosted by the first cloud service provider, and wherein participating in the node cluster includes performing one or more network security actions on traffic between remote servers and the client network, the client network separate from the first and second cloud service providers and the remote servers remote from the client network and from the first and second cloud service providers;
configuring, by the network manager, a second node to participate in the node cluster, wherein the second node is hosted by the first cloud service provider;
configuring, by the network manager, a third node to participate in the node cluster, wherein the third node is hosted by the second cloud service provider communicably coupled to the first cloud service provider via computer networking;
initiating the first node as a virtual machine instance within a virtual machine environment of the first cloud service provider;
initiating the second node as a containerized program executing within an operating-system-level virtualization environment of the first cloud service provider;
initiating the third node as a second containerized program executing within a second operating-system-level virtualization environment of the second cloud service provider; and
sending, by the network manager, messages into the first cloud service and into the second cloud service to cause the containerized program of the second node and the containerized program of the third node to synchronize data such that the containerized program of the second node and the containerized program of the third node operate with the same configuration data to perform the same network security actions regardless of the cloud service to which they belong.
10. The medium of claim 9 , wherein:
instantiating the first node as a virtual machine comprises invoking a virtual-machine application programming interface (API) configured to instantiate virtual machines; and
instantiating the second node as a containerized program comprises invoking a operating-system level API configured to launch operating-system-level execution.
11. The medium of claim 9 , the operations further comprising synchronizing data between the first node and the second node within the first cloud service provider.