It is suggested to deploy Cello on multiple servers, at least 1 Master + N (N>=1) Workers.
Master: Management node to run Cello services.
Worker: Platforms (e.g., Docker, Swarm, Kubernetes, vSphere Cloud) to host blockchains. The
Workerwill be managed by the
workerthat the resource will be managed by a unique platform. Typically it can be a naive Docker host, a Swarm cluster, a Kubernetes clsuter, or other bare-metal/virtual/container clusters.
Cluster): Blockchain network including numbers of peer+orderer nodes. E.g., a Hyperledger Fabric network, a Sawthooth Lake or Iroha chain.
Master will hold the main Cello services.
This is the control panel of the whole Cello service, and most of the management work should be handled here.
Master will manage the blockchain networks running inside the
Workers will be managed by the
Master service, and help host the blockchains.
A host is a group of resources managed by the same resource controller, which can be a native Docker Host, a Swarm Cluster, a Kubernetes Cluster, or some Cloud currently.
Usually a host has several properties:
Name: Alias name for human read convenience.
Daemon URL: The url for Docker/Swarm Access.
Capacity: How many chains the host can have at most.
Logging Level: The default logging level for the chains at this host.
Logging Type: How to handle those logging messages.
Schedulable: The chains on this hosts are available to be scheduled to users.
Autofill: Always automatically fill the hosts full with chains.
A chain is typically a blockchain cluster, e.g., a fabric network.
A Chain has several properties:
Name: Alias name for human readiness.
Host: Which host the chain locates.
Size: How number nodes does the chain have.
Consensus: What kind of consensus does the chain adopts, depending on the blockchain technology.
This work is licensed under a Creative Commons Attribution 4.0 International License.