Description
This feature only needs to be implemented on the Rust Client.
Due to the import protocol between dfcache and dfdaemon, it's possible to import a file from a fixed path on the host node directly into the dfdaemon process.
However, in a Kubernetes environment, Dragonfly's dfdaemon is typically deployed as a DaemonSet, meaning there is one dfdaemon instance running on each Node.
Therefore, when a user inside a Pod utilizes dfcache to import a file, it necessitates mounting the Unix Domain Socket (UDS) of the dfdaemon running on that specific Node into the user's Pod.
Subsequently, dfcache communicates via this mounted UDS to transfer the file's content to dfdaemon. Upon receiving the content, dfdaemon writes the file to its configured storage location.
Link
Client Repo: https://github.com/dragonflyoss/client
Description
This feature only needs to be implemented on the Rust Client.
Due to the import protocol between
dfcacheanddfdaemon, it's possible to import a file from a fixed path on the host node directly into thedfdaemonprocess.However, in a Kubernetes environment, Dragonfly's
dfdaemonis typically deployed as a DaemonSet, meaning there is onedfdaemoninstance running on each Node.Therefore, when a user inside a Pod utilizes
dfcacheto import a file, it necessitates mounting the Unix Domain Socket (UDS) of thedfdaemonrunning on that specific Node into the user's Pod.Subsequently,
dfcachecommunicates via this mounted UDS to transfer the file's content todfdaemon. Upon receiving the content,dfdaemonwrites the file to its configured storage location.Link
Client Repo: https://github.com/dragonflyoss/client