Abstract: A source host device masks the hardware address of a hosted container from a network device to mitigate the use of resources in the network device. A virtual switch on the source host receives a frame from a hosted container. The frame includes a source hardware address of the hardware address corresponding to the hosted container. The frame also includes a source network address of the network address corresponding to the hosted container. The virtual switch replaces the source hardware address of the frame with the hardware address associated with the source host, and send the frame to the network device. The frame sent to the network device includes the host hardware address as the source hardware address and the container network address as the source network address.

Abstract: In one example, a network device detects when a deployment request for the network device from a network controller is stored in a directory corresponding to the network device. Deployment information is stored as a value of a first key in the directory and includes information to configure the network device to attain a set of goals. The network device retrieves the deployment information from the directory. The network device is configured to attain the set of goals by the network device applying the retrieved deployment information. The network device generates one or more status notifications indicating a status of configuring the network device, and stores the one or more status notifications as a value of a second key in the directory to indicate the status to the network controller.

Abstract: A source host device masks the hardware address of a hosted container from a network device to mitigate the use of resources in the network device. A virtual switch on the source host receives a frame from a hosted container. The frame includes a source hardware address of the hardware address corresponding to the hosted container. The frame also includes a source network address of the network address corresponding to the hosted container. The virtual switch replaces the source hardware address of the frame with the hardware address associated with the source host, and send the frame to the network device. The frame sent to the network device includes the host hardware address as the source hardware address and the container network address as the source network address.

Abstract: A source host device masks the hardware address of a hosted container from a network device to mitigate the use of resources in the network device. A virtual switch on the source host receives a frame from a hosted container. The frame includes a source hardware address of the hardware address corresponding to the hosted container. The frame also includes a source network address of the network address corresponding to the hosted container. The virtual switch replaces the source hardware address of the frame with the hardware address associated with the source host, and send the frame to the network device. The frame sent to the network device includes the host hardware address as the source hardware address and the container network address as the source network address.

Abstract: In one implementation, a method performed by a first node with interfaces configured as IP unnumbered interfaces sharing a single IP address and to communicate with a DHCP-associated second node includes: obtaining a first message that indicates a configuration status of a third node at a respective interface; obtaining a second message for the third node from the DHCP-associated second node that includes a temporary IP address for the third node and an indicator of a file server; obtaining a third message associated with the third node that includes the temporary IP address, the third message requests address information for the file server; and configuring the third node by establishing a connection between the third node and the file server to transfer at least one configuration file, where configuring the third node includes providing the temporary IP address to the DHCP-associated second node via BGP.

Abstract: A network controller deploys network management applications to containers hosted on compute nodes. For each container on each compute node, the controller determines the network connectivity required by the application; assigns to the container one or more Internet Protocol (IP) addresses that satisfy the network connectivity, and provides the one or more IP addresses to the container; upon detecting the container is lost, blocks the one or more IP addresses so that the they cannot be re-assigned to any other container; and upon detecting that the application has been re-deployed to a new container on a new compute node, unblock the blocked one or more IP addresses, and assign and send the one or more IP addresses to the new container to enable the new container to establish the network connectivity required by the application without network address translation.

Abstract: A source host device masks the hardware address of a hosted container from a network device to mitigate the use of resources in the network device. A virtual switch on the source host receives a frame from a hosted container. The frame includes a source hardware address of the hardware address corresponding to the hosted container. The frame also includes a source network address of the network address corresponding to the hosted container. The virtual switch replaces the source hardware address of the frame with the hardware address associated with the source host, and send the frame to the network device. The frame sent to the network device includes the host hardware address as the source hardware address and the container network address as the source network address.

Abstract: A network controller deploys network management applications to containers hosted on compute nodes. For each container on each compute node, the controller determines the network connectivity required by the application; assigns to the container one or more Internet Protocol (IP) addresses that satisfy the network connectivity, and provides the one or more IP addresses to the container; upon detecting the container is lost, blocks the one or more IP addresses so that the they cannot be re-assigned to any other container; and upon detecting that the application has been re-deployed to a new container on a new compute node, unblock the blocked one or more IP addresses, and assign and send the one or more IP addresses to the new container to enable the new container to establish the network connectivity required by the application without network address translation.

Abstract: In one implementation, a method performed by a first node with interfaces configured as IP unnumbered interfaces sharing a single IP address and to communicate with a DHCP-associated second node includes: obtaining a first message that indicates a configuration status of a third node at a respective interface; obtaining a second message for the third node from the DHCP-associated second node that includes a temporary IP address for the third node and an indicator of a file server; obtaining a third message associated with the third node that includes the temporary IP address, the third message requests address information for the file server; and configuring the third node by establishing a connection between the third node and the file server to transfer at least one configuration file, where configuring the third node includes providing the temporary IP address to the DHCP-associated second node via BGP.

Abstract: In one embodiment, a method includes receiving from a server, flow data for a plurality of flows at a network device, the flow data comprising for each flow, a destination address and a time indicating when a last packet was processed for the flow at the server, updating a flow table at the network device, identifying one of the flows in the flow table as an inactive flow, and removing a route for the inactive flow from a forwarding information base at the network device. An apparatus and logic are also disclosed herein.

Abstract: In one embodiment, a method includes receiving from a server, flow data for a plurality of flows at a network device, the flow data comprising for each flow, a destination address and a time indicating when a last packet was processed for the flow at the server, updating a flow table at the network device, identifying one of the flows in the flow table as an inactive flow, and removing a route for the inactive flow from a forwarding information base at the network device. An apparatus and logic are also disclosed herein.