[question] Is there any relationship between df-daemon and supernode? about dragonfly HOT 1 CLOSED

I'm very sorry about our unclear documents.

the supernode(or the cluster manager, BTW, why give a different name?)

There is a part of this system named cluster manage in our internal version. But in open source version, we remove it and migrate some features of it to supernode. I think we should unify the name of supernode to avoid confusion.

The df-daemon and supernode are connected by the dfget. When you execute the following command:

docker pull centos:centos6

NOTE: If you use MIRROR pattern, you should remove the registry domain because that the domain was configured in df-daemon param -registry. If you are testing on MacOS, please set the df-daemon param -hostIp to a non-loop ip of your machine.

The complete flows are:

• docker daemon requests the registry mirror(df-daemon) to get every layers' url and downloads them
• df-daemon uses dfget to download every layers of image
• dfget connects to supernode to download the layer that df-daemon assigned, just like we use dfget to download files directly.
• supernode downloads the file(layer of image) from registry

Df-daemon now support HTTP PROXY pattern but not support to pull a private image for now. We are improving documents recently and will add some content about PROXY pattern.

from dragonfly.