Edge database management of the network data plane

Abstract

Novel tools and techniques for network data plane management are provided. A system includes a host machine that includes a database, processor, and non-transitory computer readable media comprising instructions executable by the processor to obtain, via the database, a network configuration, spawn a container according to the network configuration, wherein the container is configured, based on the network configuration, to be coupled to a network overlay via a network interface, receive, via the network interface, incoming data associated with the container, the incoming data having attached one or more attached network data attributes, and identify, via the database, the attached one or more network data attributes attached to the incoming data as one or more network data attributes of the network data model.

What is claimed is: 
     
       1. A system comprising:
 a host machine configured to run a container orchestrator, the host machine comprising: 
 a database comprising a multi-dimensional data store configured to define a network data model, wherein the network data model is configured to support one or more network data attributes, the database further comprising a network configuration; 
 a processor; and 
 non-transitory computer readable media comprising instructions executable by the processor to: 
 obtain, via the database, the network configuration; 
 spawn a container according to the network configuration, wherein the container is configured, based on the network configuration, to be coupled to a network overlay via a network interface; 
 receive, via the network interface, incoming data associated with the container, the incoming data having attached one or more attached network data attributes; 
 identify, via the database, the attached one or more network data attributes attached to the incoming data as one or more network data attributes of the network data model; 
 determine whether the container is communicating with a second container within a shared pod, wherein the shared pod comprises one or more containers including the container and the second container on the host machine; and 
 for intrapod incoming data, receive a memory pointer associated with the location of the intrapod incoming data. 
 
     
     
       2. The system of  claim 1 , wherein the instructions are further executable by the processor to:
 attach one or more network data attributes associated with outgoing data, wherein outgoing data is transmitted by the container and the one or more network data attributes attached to the outgoing data are based, at least in part, on the container; and 
 transmit, via the network interface, the outgoing data. 
 
     
     
       3. The system of  claim 1 , wherein the instructions are further executable by the processor to:
 add, via the database, an additional attribute to the one or more network data attributes of the network data model. 
 
     
     
       4. The system of  claim 1 , wherein the instructions are further executable by the processor to:
 remove, via the database, at least one of the one or more network data attributes from the network data model. 
 
     
     
       5. The system of  claim 1 , wherein the instructions are further executable by the processor to:
 prioritize forwarding of the incoming data based, at least in part, on the one or more attached network data attributes. 
 
     
     
       6. The system of  claim 1 , wherein the one or more network data attributes includes at least a quality of service, security, routing, switching, proof of origin, proof of delivery, and packet behavior monitoring associated with data received and transmitted by the container. 
     
     
       7. An apparatus comprising:
 a processor; and 
 non-transitory computer readable media comprising instructions executable by the processor to: 
 obtain, via a database, a network configuration; 
 spawn a container according to the network configuration, wherein the container is configured, based on the network configuration, to be coupled to a network overlay via a network interface; 
 receive, via the network interface, incoming data associated with the container, the incoming data having attached one or more attached network data attributes; 
 identify, via the database, the attached one or more network data attributes attached to the incoming data as one or more network data attributes of a network data model; 
 determine whether the container is communicating with a second container within a shared pod, wherein the shared pod comprises one or more containers including the container and the second container on the host machine; and 
 for intrapod incoming data, receive a memory pointer associated with the location of the intrapod incoming data, 
 wherein the database comprises a multi-dimensional data store configured to define the network data model, wherein the network data model is configured to support one or more network data attributes. 
 
     
     
       8. The apparatus of  claim 7 , wherein the instructions are further executable by the processor to:
 attach one or more network data attributes associated with outgoing data, wherein outgoing data is transmitted by the container and the one or more network data attributes attached to the outgoing data are based, at least in part, on the container; and 
 transmit, via the network interface, the outgoing data. 
 
     
     
       9. The apparatus of  claim 7 , wherein the instructions are further executable by the processor to:
 add, via the database, an additional attribute to the one or more network data attributes of the network data model. 
 
     
     
       10. The apparatus of  claim 7 , wherein the instructions are further executable by the processor to:
 remove, via the database, at least one of the one or more network data attributes from the network data model. 
 
     
     
       11. The apparatus of  claim 7 , wherein the instructions are further executable by the processor to:
 prioritize forwarding of the incoming data based, at least in part, on the one or more attached network data attributes. 
 
     
     
       12. A method comprising:
 defining, at an edge database, a network data model configured to support one or more network data attributes; 
 providing, via the edge database, a network configuration; 
 obtaining, via an orchestrator, the network configuration from the edge database; 
 spawning, via the orchestrator, a container according to the network configuration, wherein spawning the container further comprises coupling the container, based on the network configuration, to a network overlay via a network interface; 
 receiving, via the network interface, incoming data associated with the container, the incoming data having attached one or more attached network data attributes; 
 identifying, via the edge database, the attached one or more network data attributes attached to the incoming data as one or more network data attributes of the network data model; 
 determine whether the container is communicating with a second container within a shared pod, wherein the shared pod comprises one or more containers including the container and the second container on the host machine; and 
 for intrapod incoming data, receive a memory pointer associated with the location of the intrapod incoming data. 
 
     
     
       13. The method of  claim 12  further comprising:
 add, via the edge database, an additional attribute to the one or more network data attributes of the network data model; and 
 removing, via the edge database, at least one of the one or more network data attributes from the network data model. 
 
     
     
       14. The method of  claim 12  further comprising:
 prioritizing forwarding of the incoming data based, at least in part, on the one or more attached network data attributes.