Hyperledger Cello Installation deployment and simple use under CENTOS7

Super Ledger Hyperledger Cello installation deployment and simple use

Cello GitHub

Hyperledger Cello helps manage blockchain networks effectively. use to quickly build a blockchain-as-a-service (BaaS) platform. Immediately provide customizable blockchain, such as Hyperledger Fabric Network v1.0 can be used on bare metal, virtual cloud (virtual machine, virtual cloud), container cluster (for example, docker,swarm,kubernetes) to maintain the running blockchain network pool through the dashboard to check the system status, Adjust the number of chains, expand resources ...
Documentation Guide

For new users, it is highly recommended to read tutorial or index first

Access online documentation at any time for more information. You can also run make doc to launch the local document Web site (on localhost:8000) for review. Quick Tour related Docker images

launched Docker container

Cello Login (admin:pass)

Cello

HYPERLEDGER EXPLORER

Installing cello Platform

Cello follows a typical master-slave architecture. There are two types of nodes in the cluster. Master node: The cello service provides a link to the worker nodes through the API interface management (CREATE/DELETE, etc.) provided by the worker nodes, which provides the web panel (port 8080) and RESTful APIs (port 80). worker Node: Cello supports multiple types of work nodes from a single server to a cluster. As an example of a Docker host or swarm cluster, the API interface provided by Worker nodes should be accessible from the primary node (typically on port 2375)
Master Node Installation

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

When you first run, use setup.sh to set the master node.

$ make Setup-master

Master Node uses

Make start do
stop make 
restart make
redeploy Service=dashboard

Master Node Log View

Make logs make
log Service=watchdog #查看特定服务的日志

Master Node Development mode started

Dev=true make start

THEME THEME name for operator Dashboard Basic/vue/react, default was basic
npm_registry NPM REGISTRY for install node P Ackages
DEV Start Service in dev/product mode, options are True/false, default is True
enable_email_active Whether Register user in User-dashboard need to active manually
Smtp_server SMTP SERVER address for Send active e-mail to user< C4/>smtp_port SMTP server PORT
smtp_auth_username USERNAME for authenticate of SMTP server
Smtp_auth_password Password for authenticate of SMTP server
From_email e-mail address display to user

Worker Node Installation (Docker)

$ sudo systemctl stop docker.service
$ sudo dockerd-h tcp://0.0.0.0:2375-h unix:///var/run/docker.sock--api-cors- Header= ' * '--default-ulimit=nofile=8192:16384--default-ulimit=nproc=8192:16384-d &

Finally, run the next test on the master node and get an OK response to ensure that it can successfully access the worker node.

[Master] $ docker-h worker_node_ip:2375 Info

$ make Setup-worker

In order to avoid inexplicable problems, it is best to shut down the firewall, save time to study research, production environment, said another

This is done, access to master_node_ip:8080 on the line, continue to grope forward