Shulou(Shulou.com)06/01 Report--

What this article shares with you is about how to understand Hyperledger Cello. The editor thinks it is very practical, so I share it with you to learn. I hope you can get something after reading this article.

Hyperledger Cello is a sub-project under the super ledger project, which provides on-demand deployment. Blockchains can be deployed in a variety of bare metal, virtual machines, containers and other environments. The project was originally initiated by IBM and is now sponsored by Soramitsu, Huawei and Intel.

The project is still in incubation, and there may be significant changes in the future. Here we will give a quick overview of this tool.

Brief introduction to the function of 1Cello

Cello can easily help users to achieve:

Quickly build a BaaS service from scratch

Support for customizable block chains, such as Hyperledger fabric network v1.0.

You can manage a blockchain network resource in bare metal, virtual cloud (such as virtual machines, vsphere Clouds, etc.), or container clusters (such as Docker, Swarm, Kubernates, etc.)

From dashboard, you can check the system status, adjust the number of block chains, expand resources and other functions.

Typical application scenarios are as follows:

2 installation and deployment

The architecture of the entire Cello is as follows:

Cello adopts an one-master and multi-slave deployment model. Cello Service is deployed on Master nodes. The bare metal or virtual environment that provides host resources is called Host, and the blockchain service unit managed by Cello is called Worker. Deployment of the entire environment requires at least one Master and one Worker.

Master installation and deployment

The Master node provides a hosting environment for Cello Service and usually provides an web management interface. Master is officially recommended to use the Linux runtime environment, and the Ubuntu 16.04 operating system is recommended.

The Master environment requires the following:

Hardware: 8c16g100g

Docker engine: 1.10.001.13.0 (Docker 17.0 + support is experimental)

Docker-compose: 1.8.0mm 1.12.0

The installation of the Docker environment is skipped and just follow the official Docker documentation.

$sudo aptitude install git make-y $git clone http://gerrit.hyperledger.org/r/cello & & cd cello$ make setup-master

The script then installs some dependencies and downloads the required Docker images

You can use commands such as make start/stop/restart. In addition, you can control the startup behavior by adding environment variables. For more information, please refer to the official documentation.

At this point, you can access http://ip:8080 and open the web management interface. The default user name and password are admin and pass respectively.

Worker installation and deployment

Currently, Cello only supports Docker and Swarm for Worker node, and more Worker node types will be supported in the future. Deploying Worker node supports not only Docker and Swarm itself, but also kubernates and ansible (actually deploying Docker+k8s on the client, and then automating the configuration).

In this article, we demonstrate the most basic Docker deployment Worker node. In order to demonstrate that we use the same PC, the product environment must be distributed deployment of Master and Worker.

Since Docker on the Master management Worker is accessed through the tcp port, and the default configuration of Docker is to listen on the unix domain socket, not the TCP port, we need to modify the default configuration of the Docker to listen on the TCP port. Edit the / etc/docker/daemon.json file (this file does not exist by default, you can create one by yourself):

{"registry-mirrors": ["https://registry.docker-cn.com"]," hosts ": [" tcp://0.0.0.0:2375 "," unix:///var/run/docker.sock "]," api-cors-header ":" * "}

Pay special attention if your operating system uses Systemd managed docker services (such as Ubuntu 16.04, CentOS7, Debian 8 and above all use Systemd management services), because the Systemd configuration script has specified the-H parameter in the docker startup parameters, it will conflict with the hosts configuration in daemon.json. Therefore, in this case, you need to delete the hosts configuration item in the daemon.json configuration and change it to the systemd configuration file:

$sudo mkdir-p / etc/systemd/system/docker.service.d$ sudo cat > / etc/systemd/system/docker.service.d/override.conf

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.