Welcome to your go-to guide for mastering Hyperledger Cello, an innovative blockchain provisioning and operation system that streamlines the management of blockchain networks.
Introduction
With Hyperledger Cello, you have the power to:
- Quickly create a Blockchain as a Service (BaaS) platform from scratch.
- Effortlessly provision customizable Blockchains, such as a Hyperledger fabric network v1.0.
- Manage a pool of operational blockchain networks across bare metals, virtual clouds (like virtual machines and vSphere Clouds), and container clusters (like Docker, Swarm, and Kubernetes).
- Observe system status, optimize chain numbers, and scale resources via intuitive dashboards.
A typical usage scenario is illustrated below:

Main Features
- Manage the lifecycle of blockchains: create, start, stop, delete, and maintain health automatically.
- Support for customized blockchain requests (size, consensus); currently focusing primarily on Hyperledger Fabric.
- Compatibility with native Docker host, Swarm, or Kubernetes as worker nodes, with more support to come.
- Support for heterogeneous architecture, including X86, POWER, and Z, from bare-metal servers to virtual machines.
- Enhance performance with monitoring, logging, health, and analytics features through additional components.
Quick Start
Let’s dive into getting Hyperledger Cello up and running.
Environmental Preparation:
- Install Docker
- Install Docker Compose V2
- Verify that the make all script for Cello service management is written in the Makefile.
- Optionally, install Kubernetes.
- Install Node.js.
Starting the Cello Service:
Once everything is in place, follow these steps:
- Set the local storage environment variable, using the current path as a storage path:
- Start the service locally:
- Optional: Build essential images for Cello service:
- Run services locally:
- Check the output for confirmation:
- To stop the service:
- To clean all containers:
- To check available make rules:
- Visit the Cello dashboard at localhost:8081.
- Refer to the troubleshoot section for any issues encountered.
export CELLO_STORAGE_PATH=$(pwd)
make local
make docker
make start
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
81e6459965ec hyperledgercello-agent-docker gunicorn server:app… 4 seconds ago Up 2 seconds 0.0.0.0:2375-2375tcp, :::2375-2375tcp, 0.0.0.0:5001-5001tcp, :::5001-5001tcp cello.docker.agent
04367ab6bd5e postgres:11.1 docker-entrypoint.s… 4 seconds ago Up 2 seconds 0.0.0.0:5432-5432tcp, :::5432-5432tcp cello-postgres
29b56a279893 hyperledgercello-api-engine binsh -c bash e… 4 seconds ago Up 2 seconds 0.0.0.0:8080-8080tcp, :::8080-8080tcp cello-api-engine
a272a06d8280 hyperledgercello-dashboard bash -c nginx -g … 4 seconds ago Up 2 seconds 80tcp, 0.0.0.0:8081-8081tcp, :::8081-8081tcp cello-dashboard
make stop
make clean
make help
Why Named Cello?
Do you know anyone better at playing chains? 🙂
Troubleshooting Ideas
If you face any challenges, consider the following:
- Ensure that all environmental dependencies are met before starting the service.
- Check Docker and Docker Compose configurations to avoid version compatibility issues.
- Monitor the console output for errors or warnings during the service startup.
- If using Kubernetes, make sure the configurations are aligned with your cluster settings.
- For more insights, updates, or to collaborate on AI development projects, stay connected with fxis.ai.
At fxis.ai, we believe that such advancements are crucial for the future of AI, as they enable more comprehensive and effective solutions. Our team is continually exploring new methodologies to push the envelope in artificial intelligence, ensuring that our clients benefit from the latest technological innovations.