Fabric1.4.4 多机solo共识搭建

简单记录一下fabric版本1.4.4的搭建部署，运行环境为CentOs7.8，如有错误欢迎批评指正。然后就是本编文章不对环境搭建做说明，基础环境搭建看这里。

1.总体设计

本案例部署一个排序（orderer）服务，一个组织（org1）下四个节点（peer）,共需要五台计算机。

名称	私域ip
orderer.example.com	172.23.151.6
peer0.org1.example.com	172.23.151.5
peer1.org1.example.com	172.23.151.7
peer2.org1.example.com	172.23.151.3
peer3.org1.example.com	172.23.151.4

2.部署orderer.example.com（172.23.151.6）

1. 创建multipeer目录

mkdir $GOPATH/src/github.com/hyperledger/fabric/multipeer               //这一步可以在每台机器上面都先创建好这个目录文件夹

cd $GOPATH/src/github.com/hyperledger/fabric/multipeer

2. 获取生成工具

上传hyperledger-fabric-linux-amd64-1.4.4.tar.gz二进制文件包并解压，然后赋予权限。

tar -zxvf hyperledger-fabric-linux-amd64-1.4.4.tar.gz

chmod -R 777 ./bin

3. 准备crypto-config.yaml和configtx.yaml文件

crypto-config.yaml：

OrdererOrgs:

- Name: Orderer

Domain: example.com

Specs:

- Hostname: orderer

PeerOrgs:

- Name: Org1

Domain: org1.example.com

EnableNodeOUs: true

Template:

Count: 4

Users:

Count: 4

configtx.yaml：

---

Organizations:

    - &OrdererOrg

        Name: OrdererOrg

        ID: OrdererMSP

        MSPDir: crypto-config/ordererOrganizations/example.com/msp

        Policies:

            Readers:

                Type: Signature

                Rule: "OR('OrdererMSP.member')"

            Writers:

                Type: Signature

                Rule: "OR('OrdererMSP.member')"

            Admins:

                Type: Signature

                Rule: "OR('OrdererMSP.admin')"

    - &Org1

        Name: Org1MSP

        ID: Org1MSP

        MSPDir: crypto-config/peerOrganizations/org1.example.com/msp

        Policies:

            Readers:

                Type: Signature

                Rule: "OR('Org1MSP.admin', 'Org1MSP.peer', 'Org1MSP.client')"

            Writers:

                Type: Signature

                Rule: "OR('Org1MSP.admin', 'Org1MSP.client')"

            Admins:

                Type: Signature

                Rule: "OR('Org1MSP.admin')"

        AnchorPeers:

            - Host: peer0.org1.example.com

              Port: 7051

Capabilities:

    Channel: &ChannelCapabilities

        V1_4_3: true

        V1_3: false

        V1_1: false

    Orderer: &OrdererCapabilities

        V1_4_2: true

        V1_1: false

    Application: &ApplicationCapabilities

        V1_4_2: true

        V1_3: false

        V1_2: false

        V1_1: false

Application: &ApplicationDefaults

    Organizations:

    Policies:

        Readers:

            Type: ImplicitMeta

            Rule: "ANY Readers"

        Writers:

            Type: ImplicitMeta

            Rule: "ANY Writers"

        Admins:

            Type: ImplicitMeta

            Rule: "MAJORITY Admins"

    Capabilities:

        <<: *ApplicationCapabilities

Orderer: &OrdererDefaults

    OrdererType: solo

    Addresses:

        - orderer.example.com:7050

    BatchTimeout: 2s

    BatchSize:

        MaxMessageCount: 200

        AbsoluteMaxBytes: 98 MB

        PreferredMaxBytes: 512 KB

    Kafka:

        Brokers:

            - 127.0.0.1:9092

    Organizations:

    Policies:

        Readers:

            Type: ImplicitMeta

            Rule: "ANY Readers"

        Writers:

            Type: ImplicitMeta

            Rule: "ANY Writers"

        Admins:

            Type: ImplicitMeta

            Rule: "MAJORITY Admins"

        BlockValidation:

            Type: ImplicitMeta

            Rule: "ANY Writers"

    Capabilities:

        <<: *OrdererCapabilities

Channel: &ChannelDefaults

    Policies:

        Readers:

            Type: ImplicitMeta

            Rule: "ANY Readers"

        Writers:

            Type: ImplicitMeta

            Rule: "ANY Writers"

        Admins:

            Type: ImplicitMeta

            Rule: "MAJORITY Admins"

    Capabilities:

        <<: *ChannelCapabilities

Profiles:

    TwoOrgsOrdererGenesis:

        <<: *ChannelDefaults

        Orderer:

            <<: *OrdererDefaults

            Organizations:

                - *OrdererOrg

        Consortiums:

            SampleConsortium:

                Organizations:

                    - *Org1

    TwoOrgsChannel:

        Consortium: SampleConsortium

        Application:

            <<: *ApplicationDefaults

            Organizations:

                - *Org1

4. 生成公私钥和证书

./bin/cryptogen generate --config=./crypto-config.yaml

5.生成创世区块

mkdir channel-artifacts

./bin/configtxgen -profile TwoOrgsOrdererGenesis -outputBlock ./channel-artifacts/genesis.block

6. 生成通道配置区块

./bin/configtxgen -profile TwoOrgsChannel -outputCreateChannelTx ./channel-artifacts/mychannel.tx -channelID mychannel

7.准备orderer配置文件

docker-compose-orderer.yaml：

version: '2'

services:

  orderer.example.com:

    container_name: orderer.example.com

    image: hyperledger/fabric-orderer

    environment:

      - ORDERER_GENERAL_LOGLEVEL=debug

      - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0

      - ORDERER_GENERAL_GENESISMETHOD=file

      - ORDERER_GENERAL_GENESISFILE=/var/hyperledger/orderer/orderer.genesis.block

      - ORDERER_GENERAL_LOCALMSPID=OrdererMSP

      - ORDERER_GENERAL_LOCALMSPDIR=/var/hyperledger/orderer/msp

      # enabled TLS

      - ORDERER_GENERAL_TLS_ENABLED=true

      - ORDERER_GENERAL_TLS_PRIVATEKEY=/var/hyperledger/orderer/tls/server.key

      - ORDERER_GENERAL_TLS_CERTIFICATE=/var/hyperledger/orderer/tls/server.crt

      - ORDERER_GENERAL_TLS_ROOTCAS=[/var/hyperledger/orderer/tls/ca.crt]

      - ORDERER_KAFKA_RETRY_SHORTINTERVAL=1s

      - ORDERER_KAFKA_RETRY_SHORTTOTAL=30s

      - ORDERER_KAFKA_VERBOSE=true

    working_dir: /opt/gopath/src/github.com/hyperledger/fabric

    command: orderer

    volumes:

      - ./channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block

      - ./crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/msp:/var/hyperledger/orderer/msp

      - ./crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/:/var/hyperledger/orderer/tls

    ports:

      - 7050:7050

8.启动Fabric网络

docker-compose -f docker-compose-orderer.yaml up -d

9.拷贝生成文件到其它电脑

cd ..

scp -r multipeer root@172.23.151.5:/usr/local/gopath/src/github.com/hyperledger/fabric

scp -r multipeer root@172.23.151.7:/opt/gopath/src/github.com/hyperledger/fabric

scp -r multipeer root@172.23.151.3:/opt/gopath/src/github.com/hyperledger/fabric

scp -r multipeer root@172.23.151.4:/opt/gopath/src/github.com/hyperledger/fabric

3.部署peer0.org1.example.com（172.23.151.5）

1.进入multipeer目录

cd $GOPATH/src/github.com/hyperledger/fabric/multipeer                  //进来之后应该可以看到从172.23.151.6拷贝过来的那些文件

2.上传智能合约

mkdir -p chaincode/go/example02                                         //将智能合约放在这里  xxxx.go

3.准备peer配置文件

docker-compose-peer.yaml：

version: '2'

services:

  peer0.org1.example.com:

    container_name: peer0.org1.example.com

    image: hyperledger/fabric-peer

    environment:

      - CORE_PEER_ID=peer0.org1.example.com

      - CORE_PEER_ADDRESS=peer0.org1.example.com:7051

      - CORE_PEER_CHAINCODEADDRESS=peer0.org1.example.com:7052

      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052

      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.example.com:7051

      - CORE_PEER_LOCALMSPID=Org1MSP

      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock

      # the following setting starts chaincode containers on the same

      # bridge network as the peers

      # https://docs.docker.com/compose/networking/

      - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=multipeer_default

      #- CORE_LOGGING_LEVEL=ERROR

      - CORE_LOGGING_LEVEL=DEBUG

      - CORE_PEER_TLS_ENABLED=true

      - CORE_PEER_GOSSIP_USELEADERELECTION=true

      - CORE_PEER_GOSSIP_ORGLEADER=false

      - CORE_PEER_PROFILE_ENABLED=true

      - CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/tls/server.crt

      - CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/tls/server.key

      - CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/tls/ca.crt

    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer

    command: peer node start

    volumes:

        - /var/run/:/host/var/run/

        - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/msp:/etc/hyperledger/fabric/msp

        - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls:/etc/hyperledger/fabric/tls

    ports:

      - 7051:7051

      - 7052:7052

      - 7053:7053

    extra_hosts:

      - "orderer.example.com:172.23.151.6"

  cli:

    container_name: cli

    image: hyperledger/fabric-tools

    tty: true

    environment:

      - GOPATH=/opt/gopath

      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock

      - CORE_LOGGING_LEVEL=DEBUG

      - CORE_PEER_ID=cli

      - CORE_PEER_ADDRESS=peer0.org1.example.com:7051

      - CORE_PEER_LOCALMSPID=Org1MSP

      - CORE_PEER_TLS_ENABLED=true

      - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt

      - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key

      - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt

      - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp

    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer

    volumes:

        - /var/run/:/host/var/run/

        - ./chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/multipeer/chaincode/go

        - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/

        - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts

    depends_on:

       - peer0.org1.example.com

    extra_hosts:

       - "orderer.example.com:172.23.151.6"

       - "peer0.org1.example.com:172.23.151.5"

       - "peer1.org1.example.com:172.23.151.7"

       - "peer3.org1.example.com:172.23.151.3"

       - "peer4.org1.example.com:172.23.151.4"

4.启动Fabric网络

1) 启动peer

docker-compose -f docker-compose-peer.yaml up -d

2) 启动cli容器

docker exec -it cli bash

3) 创建Channel

ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

peer channel create -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/mychannel.tx --tls --cafile $ORDERER_CA

4) Peer加入Channel

peer channel join -b mychannel.block

5) 安装智能合约

peer chaincode install -n mycc -p github.com/hyperledger/fabric/multipeer/chaincode/go/example02/ -v 1.0

6) 实例化智能合约

ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

peer chaincode instantiate -o orderer.example.com:7050 --tls --cafile $ORDERER_CA -C mychannel -n mycc -v 1.0 -c '{"Args":["init"]}' -P "AND ('Org1MSP.peer')"

7) Peer上赋值给a，后再查询

peer chaincode invoke --tls --cafile $ORDERER_CA -C mychannel -n mycc -c '{"Args":["put","a","我是天才！"]}'

peer chaincode query -C mychannel -n mycc -c '{"Args":["query","a"]}'

查询a成功结果如下图所示：

8) 保存mychannel.block

docker cp xxxxxxxx:/opt/gopath/src/github.com/hyperledger/fabric/peer/mychannel.block /usr/local/gopath/src/github.com/hyperledger/fabric/multipeer            //命令中的xxxx替换成自己的docker容器Id

9) mychannel.block拷贝到其他peer节点服务器

scp mychannel.block root@172.23.151.7:/usr/local/gopath/src/github.com/hyperledger/fabric/multipeer

scp mychannel.block root@172.23.151.3:/usr/local/gopath/src/github.com/hyperledger/fabric/multipeer

scp mychannel.block root@172.23.151.4:/usr/local/gopath/src/github.com/hyperledger/fabric/multipeer

4.部署peer1.org1.example.com（172.23.151.7）

1.进入multipeer目录

cd $GOPATH/src/github.com/hyperledger/fabric/multipeer                  //进来之后应该可以看到从172.23.151.6拷贝过来的那些文件

2.上传智能合约

mkdir -p chaincode/go/example02                                         //将智能合约放在这里  xxxx.go

3.准备docker配置文件

docker-compose-peer.yaml：

version: '2'

services:

  peer1.org1.example.com:

    container_name: peer1.org1.example.com

    image: hyperledger/fabric-peer

    environment:

      - CORE_PEER_ID=peer1.org1.example.com

      - CORE_PEER_ADDRESS=peer1.org1.example.com:7051

      - CORE_PEER_CHAINCODEADDRESS=peer1.org1.example.com:7052

      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052

      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org1.example.com:7051

      - CORE_PEER_LOCALMSPID=Org1MSP

      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock

      # the following setting starts chaincode containers on the same

      # bridge network as the peers

      # https://docs.docker.com/compose/networking/

      - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=multipeer_default

      #- CORE_LOGGING_LEVEL=ERROR

      - CORE_LOGGING_LEVEL=DEBUG

      - CORE_PEER_TLS_ENABLED=true

      - CORE_PEER_GOSSIP_USELEADERELECTION=true

      - CORE_PEER_GOSSIP_ORGLEADER=false

      - CORE_PEER_PROFILE_ENABLED=true

      - CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/tls/server.crt

      - CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/tls/server.key

      - CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/tls/ca.crt

    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer

    command: peer node start

    volumes:

        - /var/run/:/host/var/run/

        - ./crypto-config/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/msp:/etc/hyperledger/fabric/msp

        - ./crypto-config/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/tls:/etc/hyperledger/fabric/tls

    ports:

      - 7051:7051

      - 7052:7052

      - 7053:7053

    extra_hosts:

      - "orderer.example.com:172.23.151.6"

  cli:

    container_name: cli

    image: hyperledger/fabric-tools

    tty: true

    environment:

      - GOPATH=/opt/gopath

      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock

      - CORE_LOGGING_LEVEL=DEBUG

      - CORE_PEER_ID=cli

      - CORE_PEER_ADDRESS=peer1.org1.example.com:7051

      - CORE_PEER_LOCALMSPID=Org1MSP

      - CORE_PEER_TLS_ENABLED=true

      - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/tls/server.crt

      - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/tls/server.key

      - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/tls/ca.crt

      - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp

    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer

    volumes:

        - /var/run/:/host/var/run/

        - ./chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/multipeer/chaincode/go

        - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/

        - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts

    depends_on:

       - peer0.org1.example.com

    extra_hosts:

       - "orderer.example.com:172.23.151.6"

       - "peer0.org1.example.com:172.23.151.5"

       - "peer1.org1.example.com:172.23.151.7"

       - "peer3.org1.example.com:172.23.151.3"

       - "peer4.org1.example.com:172.23.151.4"

4.启动Fabric网络

1) 启动peer

docker-compose -f docker-compose-peer.yaml up -d

2) 拷贝mychannel.block到peer中

docker cp /usr/local/gopath/src/github.com/hyperledger/fabric/multipeer/mychannel.block xxxxxxxx:/opt/gopath/src/github.com/hyperledger/fabric/peer/                //xxx是自己docker容器Id

3) 启动cli容器

docker exec -it cli bash

4) Peer加入Channel

peer channel join -b mychannel.block

5) 安装智能合约

peer chaincode install -n mycc -p github.com/hyperledger/fabric/multipeer/chaincode/go/example02/ -v 1.0

6) Peer上查询a，显示"我是天才"，说明网络成功

peer chaincode query -C mychannel -n mycc -c '{"Args":["query","a"]}'

查询a成功结果如下图所示：

5.部署peer2.org1.example.com（172.23.151.3）

具体步骤与peer1一样，参考即可

6.部署peer3.org1.example.com（172.23.151.4）

具体步骤与peer1一样，参考即可

Fabric1.4.4 多机solo共识搭建的更多相关文章

appium ios真机自动化环境搭建&运行（送源码）
appium ios真机自动化环境搭建&运行(送源码) 原创: f i n 测试开发社区 6天前 Appium测试环境的搭建相对比较烦琐,不少初学者在此走过不少弯路首先是熟悉Mac的使用 ...
appium ios真机自动化环境搭建&运行（送源码）
appium ios真机自动化环境搭建&运行(送源码) 原创: f i n 测试开发社区 6天前 Appium测试环境的搭建相对比较烦琐,不少初学者在此走过不少弯路首先是熟悉Mac的使用 ...
Docker & k8s 系列二：本机k8s环境搭建
本篇将会讲解k8s是什么?本机k8s环境搭建,部署一个pod并演示几个kubectl命令,k8s dashboard安装. k8s是什么 k8s是kubernetes的简写,它是一个全新的基于容器技术 ...
基于raft共识搭建的Fabric1.4.4多机网络环境
1准备工作介绍 1各个主机ip以及节点分配情况各个主机的节点分配情况 ip地址 orderer0.example.com,peer0.org1.example.com 172.17.3.60 ord ...
Hyperledger Fabric1.4的多机部署
之前的文章深入解析Hyperledger Fabric启动的全过程主要讲解了Fabric的网络搭建,以及启动的整体流程,但是都是通过单机完成的.而区块链本身就是去中心化的,所以最终还是要完成Fabri ...
appium ios 真机自动化环境搭建
近期由于工作需要,本小菜在弄appium+ios+iphone真机的移动自动化,在网上找寻各种资料,发现针对IOS方面的资料少之又少,公司其它部门的弄过的同事也寥寥无几,即使有,也是安卓方面的.本次书 ...
MAC电脑下Appium + python3 + robotframework ios的真机测试环境搭建
本人的环境搭建前的准备,MAC电脑一台(macOS Mojave 10.14.0及以上),Xcode 10.0及以上 ,自己注册的一个Apple ID 账户,必须你的电脑能连接互联网,最好不要用公 ...
appium -ios 真机连接环境搭建
补充点一: 安装ios-deploynpm install -g ios-deploy 安装不了报错.! 后来找了找,发现sudo npm install -g ios-deploy --unsafe ...
搭建一个jumpserver跳板机
1,部署jumpserver 建立阿里云公网源yum仓库清除缓存重新建立缓存 ip后面直接回车,下面输入y 地址端口账户密码直接回车 ,询问跳过输入y,是否继续输入y 用户名回车,输入自己要设置的密 ...

随机推荐

Codeforces 1337D Xenia and Colorful Gems
题意给你3个数组\(a, b\)和\(c\),最小化\((x-y)^2+(y-z)^2+(z-x)^2\),其中\(x \in a, y \in b, z \in c\). 解题思路这题其实第一眼 ...
编程体系结构(01)：Java编程基础
一.数据类型 1.基础类型整型:byte .short .int .long 浮点型:float.double 字节型:char 2.包装类型 Byte,Short,Integer,Long Flo ...
Johnson全源最短路
例题:P5905 [模板]Johnson 全源最短路首先考虑求全源最短路的几种方法: Floyd:时间复杂度\(O(n^3)\),可以处理负权边,但不能处理负环,而且速度很慢. Bellman-Fo ...
java中包名命名规范
在idea中创建package遇到的问题发现一个问题,当我创建一个lesson-02的package时,输入这个包名后,package自动变成了文件夹在网上搜索发下java包名一般是小写字母进行命 ...
学习go的一些笔记
反射 reflect type CfgSt struct{ Match *int64 `ini:"match"` Desc string `ini:"desc" ...
RabbitMQ Server安装及显示管理界面Installing on Windows
接上一篇文章,继续讲解文件很小, 1.下载路径:http://www.rabbitmq.com/download.html 2.运行rabbitmq-server-3.6.5.exe,选择要安装的目 ...
关于bat/cmd中转义符的使用
今天笔者在cmd中准备使用echo 输出<https://www.cnblogs.com/5201351> 发现直接就报错:命令语法不正确. 然后就想到可能是<和>在cmd中有 ...
JVM学习（三）JVM垃圾回收
一.引用的分类在了解JVM垃圾回收机制之前,了解一下对象的引用类型是非常必要的. 强引用:GC时不会被回收软引用:描述有用但不是必须的对象,在发生内存溢出异常之前被回收弱引用:描述有用但不是必须 ...
Flutter中如何方便的获取音视频的长度
此次主要是flutter集成im,在发送视频时需要加上时长,但是用视频controller只能在初始化时具备路径才可以可以使用:just_audio插件中的方法进行获取详情看官方文档:https:/ ...
jpeg编解码概述
本博文为概览性介绍.后面有空了再分几篇博文分别介绍所用到的技术细节. 1.编解码目标编码和解码是个逆过程.jpeg编码的目的在于图形去冗余,进行数据压缩,解码的目的在于还原图像,使能够进行预览. 2 ...

Fabric1.4.4 多机solo共识搭建

1.总体设计

2.部署orderer.example.com（172.23.151.6）

1. 创建multipeer目录

2. 获取生成工具

3. 准备crypto-config.yaml和configtx.yaml文件

4. 生成公私钥和证书

5.生成创世区块

6. 生成通道配置区块

7.准备orderer配置文件

8.启动Fabric网络

9.拷贝生成文件到其它电脑

3.部署peer0.org1.example.com（172.23.151.5）

1.进入multipeer目录

2.上传智能合约

3.准备peer配置文件

4.启动Fabric网络

1) 启动peer

2) 启动cli容器

3) 创建Channel

4) Peer加入Channel

5) 安装智能合约

6) 实例化智能合约

7) Peer上赋值给a，后再查询

8) 保存mychannel.block

9) mychannel.block拷贝到其他peer节点服务器

4.部署peer1.org1.example.com（172.23.151.7）

1.进入multipeer目录

2.上传智能合约

3.准备docker配置文件

4.启动Fabric网络

1) 启动peer

2) 拷贝mychannel.block到peer中

3) 启动cli容器

4) Peer加入Channel

5) 安装智能合约

6) Peer上查询a，显示"我是天才"，说明网络成功

5.部署peer2.org1.example.com（172.23.151.3）

6.部署peer3.org1.example.com（172.23.151.4）

Fabric1.4.4 多机solo共识搭建的更多相关文章

随机推荐

热门专题