Edge network peer-to-peer asset distribution
Methods and systems for managing an edge compute environment comprising endpoint devices and an orchestrator are disclosed. In particular, an internal peer-to-peer file sharing infrastructure exclusive to the edge compute environment is established using the endpoint devices and the orchestrator. The internal peer-to-peer file sharing infrastructure exclusive to the edge compute environment may then be used to retrieve and distribute data used for configuring one or more of the endpoint devices to allow the endpoint devices to provide one or more computer-implemented services to one or more users associated with the edge compute environment. For security of the endpoint devices, only the orchestrator is able to communicate with data processing systems external to the edge compute environment.
1 . A method for managing an edge compute environment comprising endpoint devices and an orchestrator, the method comprising:
establishing an internal peer-to-peer file sharing infrastructure exclusive to the edge compute environment using the endpoint devices and the orchestrator, the internal peer-to-peer file sharing infrastructure using a torrent protocol, wherein the endpoint devices are air gapped from data processing systems external to the edge compute environment; and
using the internal peer-to-peer file sharing infrastructure exclusive to the edge compute environment to configure one or more of the endpoint devices to allow the endpoint devices to provide one or more computer-implemented services to one or more users associated with the edge compute environment.
2 . The method of claim 1 , wherein each of the endpoint devices and the orchestrator are peers storing data being shared using the internal peer-to-peer file sharing infrastructure, and the data being torrent data associated with one or more torrent files.
3 . The method of claim 2 , wherein the orchestrator comprises a torrent tracker that keeps track of data availability information associated with the data being shared using the internal peer-to-peer file sharing infrastructure.
4 . The method of claim 3 , wherein only the orchestrator is able to communicate with the data processing systems external to the edge compute environment.
5 . The method of claim 4 , wherein, within the internal peer-to-peer file sharing infrastructure exclusive to the edge compute environment, the orchestrator manages data retention instructions for the data being shared using the internal peer-to-peer file sharing infrastructure and causes one or more of the endpoint devices to execute one or more of the data retention instructions.
6 . The method of claim 1 , wherein using the internal peer-to-peer file sharing infrastructure exclusive to the edge compute environment to configure the endpoint devices comprises, for a first endpoint device of the endpoint devices and by the first endpoint device:
obtaining a first request for first data, the first data being for configuring the first endpoint device;
making a first determination that a first torrent file associated with the first data exists within the edge compute environment;
making a second determination, using the first torrent file and with the orchestrator, that the first data is available within the edge compute environment;
in response to the second determination, downloading the first data using the first torrent file from within the edge compute environment without accessing any data processing systems outside of the edge compute environment; and
using, after downloading the first data, the first data to configure the first endpoint device to obtain an updated first endpoint device that provides one or more computer-implemented services associated with the first data.
7 . The method of claim 6 , wherein using the internal peer-to-peer file sharing infrastructure exclusive to the edge compute environment to configure the endpoint devices further comprises, for the first endpoint device and further by the first endpoint device:
after downloading the first data, informing the orchestrator that the first endpoint device is storing a complete or partial copy of the first data such that the orchestrator is able to update data availability information specifying all data, for configuring the endpoint devices, available within the edge compute environment.
8 . The method of claim 7 , wherein the first request is transmitted by an application hosted on the first endpoint device and is obtained and processed by a torrent proxy hosted by the first endpoint device.
9 . The method of claim 6 , wherein using the internal peer-to-peer file sharing infrastructure exclusive to the edge compute environment to configure the endpoint devices further comprises, for a second endpoint device of the endpoint devices and by the second endpoint device:
obtaining a second request for second data, the second data being for configuring the second endpoint device;
making a third determination that a second torrent file associated with the first data does not exist within the edge compute environment;
in response to the third determination, downloading the second data from a source external to the edge compute environment, wherein the second data is downloaded through the orchestrator; and
using, after downloading the second data, the second data to configure the second endpoint device to obtain an updated second endpoint device that provides one or more computer-implemented services associated with the second data.
10 . The method of claim 9 , wherein using the internal peer-to-peer file sharing infrastructure exclusive to the edge compute environment to configure the endpoint devices further comprises, for the second endpoint device and further by the second endpoint device:
after downloading the second data, generating a second torrent file for the second data; and
providing data availability information associated with the second data and a copy of the second torrent file to the orchestrator, the data availability information associated with the second data specifying that the second endpoint device retains a complete or partial copy of the second data.
11 . A non-transitory machine-readable medium having instructions stored therein, which when executed by endpoint devices and an orchestrator of an edge compute environment, cause the endpoint devices and the orchestrator to perform operations comprising:
establishing an internal peer-to-peer file sharing infrastructure exclusive to the edge compute environment using the endpoint devices and the orchestrator, the internal peer-to-peer file sharing infrastructure using a torrent protocol, wherein the endpoint devices are air gapped from data processing systems external to the edge compute environment; and
using the internal peer-to-peer file sharing infrastructure exclusive to the edge compute environment to configure one or more of the endpoint devices to allow the endpoint devices to provide one or more computer-implemented services to one or more users associated with the edge compute environment.
12 . The non-transitory machine-readable medium of claim 11 , wherein each of the endpoint devices and the orchestrator are peers storing data being shared using the internal peer-to-peer file sharing infrastructure, and the data being torrent data associated with one or more torrent files.
13 . The non-transitory machine-readable medium of claim 12 , wherein the orchestrator comprises a torrent tracker that keeps track of data availability information associated with the data being shared using the internal peer-to-peer file sharing infrastructure.
14 . The non-transitory machine-readable medium of claim 13 , wherein only the orchestrator is able to communicate with the data processing systems external to the edge compute environment.
15 . The non-transitory machine-readable medium of claim 14 , wherein, within the internal peer-to-peer file sharing infrastructure exclusive to the edge compute environment, the orchestrator manages data retention instructions for the data being shared using the internal peer-to-peer file sharing infrastructure and causes one or more of the endpoint devices to execute one or more of the data retention instructions.
16 . An edge compute environment comprising:
one or more endpoint devices; and
an orchestrator,
wherein each of the one or more endpoint devices and the orchestrator comprises a processor and a memory coupled to the processor that stores instructions that when executed by the one or more endpoint devices and the orchestrator, causes the one or more endpoint devices and the orchestrator to perform operations comprising:
establishing an internal peer-to-peer file sharing infrastructure exclusive to the edge compute environment using the one or more endpoint devices and the orchestrator, the internal peer-to-peer file sharing infrastructure using a torrent protocol, wherein the endpoint devices are air gapped from data processing systems external to the edge compute environment; and
using the internal peer-to-peer file sharing infrastructure exclusive to the edge compute environment to configure one or more of the one or more endpoint devices to allow the one or more endpoint devices to provide one or more computer-implemented services to one or more users associated with the edge compute environment.
17 . The edge compute environment of claim 16 , wherein each of the one or more endpoint devices and the orchestrator are peers storing data being shared using the internal peer-to-peer file sharing infrastructure, and the data being torrent data associated with one or more torrent files.
18 . The edge compute environment of claim 17 , wherein the orchestrator comprises a torrent tracker that keeps track of data availability information associated with the data being shared using the internal peer-to-peer file sharing infrastructure.
19 . The edge compute environment of claim 18 , wherein only the orchestrator is able to communicate with the data processing systems external to the edge compute environment.
20 . The edge compute environment of claim 19 , wherein, within the internal peer-to-peer file sharing infrastructure exclusive to the edge compute environment, the orchestrator manages data retention instructions for the data being shared using the internal peer-to-peer file sharing infrastructure and causes one or more of the one or more endpoint devices to execute one or more of the data retention instructions.