Cloud node routing
A router architecture that facilitates cloud exchange point routing is disclosed. The architecture relies upon B-nodes to connect branch network to cloud, S-nodes to connect services, and V-nodes to connect cloud to cloud. The nodes can be essentially stateless with node configuration stored outside a router, which facilitates ripping and replacement of nodes. Multiple virtual private clouds can be implemented with respective pluralities of Kubernetes pods and a master Kubernetes cluster. Consumer premises equipment is coupled to a first virtual private cloud that forms a virtual extensible local area network with a second private cloud.
1. A system, comprising:
one or more hardware processors; and
a memory storing instructions that, when executed by the one or more hardware processors, cause the system to perform:
updating, by an external orchestration engine, a node configuration datastore with node configuration parameter values; and
triggering, by an on-demand configuration engine based on stimulus, the on-demand configuration engine to configure a stateless node with the node configuration parameter values, wherein the stimulus is indicative of a network resource consumption.
2. The system of claim 1 , wherein the node configuration parameter values include at least one of routing, security, operating system, or forwarding parameter values.
3. The system of claim 1 , wherein the stimulus includes multiple values from a plurality of configured nodes that, considered in the aggregate, provide a snapshot or estimate of network resource consumption at the plurality of configured nodes.
4. The system of claim 1 , wherein the stimulus is either pushed from the plurality of configured nodes to a resource monitor or pulled from the plurality of configured nodes to the resource monitor.
5. The system of claim 4 , wherein the resource monitor is coupled to the on-demand configuration engine.
6. The system of claim 1 , further comprising a tunnel state datastore coupled to the external orchestration engine.
7. The system of claim 1 , further comprising a tenant state datastore coupled to the external orchestration engine.
8. The system of claim 3 , wherein the plurality of configured nodes include a branch-facing node (B-node).
9. The system of claim 3 , wherein the plurality of configured nodes include a virtual private cloud (VPC) facing node (V-node).
10. The system of claim 3 , wherein the plurality of configured nodes include a service point attachment node (S-node).
11. The system of claim 10 , further comprising multiple services coupled to the S-node.
12. The system of claim 10 , wherein the plurality of configured nodes are included in a cloud service network (CSN), wherein the CSN comprises:
a distributed service stitching (DSS) engine;
a monitoring engine;
a provisioning engine;
an analytics engine;
a data ingestion engine;
a policy engine;
a multi-tenant orchestration engine, which includes at least a portion of the orchestration engine.
13. A method, comprising:
updating, by an external orchestration engine, a node configuration datastore with node configuration parameter values; and
triggering, by an on-demand configuration engine based on a stimulus, the on-demand configuration engine to configure a stateless node with the node configuration parameter values, wherein the stimulus is indicative of a network resource consumption state.