A SlapOS network can be divided into two conceptual layers:
The administrative layer consists of two nodes - the SlapOS Master (COMP-ROOT) and the first network node (COMP-0) which provides connectivity between nodes via a Re6st Registry and Frontend (Apache).
All other nodes in a network belong to the user layer. They are simple nodes with Re6st and SlapOS installed. They wait for the SlapOS Master to instruct them which software to install and instantiate for users.
Note, that during installation, the SlapOS Master node starts out as a regular (formatted) node with just the SlapOS Kernel. It is only through SlapProxy (a minimal SlapOS Master), which is run during installation of a SlapOS Master, and which installs and instantiates the actual SlapOS Master/ERP5 Cloud Engine along with a Frontend (Apache) for accessing it, that the COMP-ROOT node is created. This means, that SlapOS is used to deploy SlapOS recursively and that there are in fact two networks - the one during installation with SlapProxy acting as Master and the first node being COMP-ROOT and the second actual network of COMP-ROOT and COMP-0,1,2,3....