Intelligent peer-to-peer container filesystem
AssigneeEMC IP Holding Company LLC
InventorsVictor Fong, Xuebin He
Life of this patent
Estimating the term…
Abstract
A peer container filesystem is provided. The peer container filesystem allows peer nodes to share containers. The peer container filesystem allows the images or portions thereof to be shared without a container registry. A node send requests to the network that are configured to push or distribute an image in the network, search for an image in the network, download an image in the network, and perform updates amongst the peer nodes such that the locations of images and/or their files are known to at least some of the peers in the network.
Claims20
A method, comprising:
- receiving a request to run a container on a node in a network, the node including a peer container filesystem and a container controller, the container associated with a container image;
- requesting files associated with the container from peer nodes when the files are not present at the node, wherein an order in which the files are accessed during container execution is associated with the container;
- receiving a tracker file from a peer node that identifies required files to start the container execution;
- downloading the required files from at least one of the peer nodes;
- starting the container when the required files are downloaded;
- and
- downloading second files from the peer nodes based on the order the second files are needed for the container execution, wherein the second files are not required to be downloaded prior to starting the container on the node,
- wherein downloading the second files is initiated prior to the second files being needed for the container execution.
A non-transitory storage medium having stored therein instructions that are executable by one or more hardware processors to perform operations comprising:
- receiving a request to run a container on a node in a network, the node including a peer container filesystem and a container controller, the container associated with a container image;
- requesting files associated with the container from peer nodes when the files are not present at the node, wherein an order in which the files are accessed during container execution is associated with the container execution;
- receiving a tracker file from a peer node that identifies required files to start the container;
- downloading the required files from at least one of the peer nodes;
- starting the container when the required files are downloaded;
- and
- downloading second files from the peer nodes based on the order the second files are needed for the container execution, wherein the second files are not required to be downloaded prior to starting the container on the node,
- wherein downloading the second files is initiated prior to the second files being needed for the container execution.
Dependencies are inferred from the claim text.