Fabric-Solo多机多节点部署方案

太过爱你忘了你带给我的痛 2022-02-21 07:06 308阅读 0赞

# Fabric-Solo多机多节点部署方案 #

Solo多机多节点部署是在单机单节点部署方案的基础上进行的，我简单介绍下我的部署方案：首先在虚拟机上搭建好单机单节点的fabric网络，然后将搭建好的虚拟机进行复制出4台，一共5台，其中一台作为Orderer节点，其余四台作为Peer节点。  
对于服务器的配置由于我电脑性能的原因，所以每台服务器都是1C+2G+40G的配置，当然配置越高越好，我这里只用作测试，所以不需要太高的配置。  
好！废话不多说，开始搭建！  
如果在搭建的过程中出现连接错误，可尝试ssh免密码登录解决！

## 第一步配置服务器 ##

这里是先搭建好一台单机单节点的服务器，然后再以这台服务器为模板去创建其他的服务器。（简单来说就是把服务器在复制一份，然后在虚拟机里直接打开就可以了）  
服务器IP Hostname 组织机构  
10.82.80.83 [orderer.example.com][] Orderer  
10.82.80.82 [peer0.org1.example.com][] Org1  
10.82.80.84 [peer0.org2.example.com][] Org2  
10.82.80.85 [peer1.org1.example.com][] Org1  
10.82.80.86 [peer1.org2.example.com][] Org2

## 第二步部署Orderer节点 ##

编写docker-orderer.yaml启动文件，具体源码如下：

# Copyright IBM Corp. All Rights Reserved.
    #
    # SPDX-License-Identifier: Apache-2.0
    #
    
    version: '2'
    
    services:
    
      orderer.example.com:
        container_name: orderer.example.com
        image: hyperledger/fabric-orderer
        environment:
          - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=aberic_default
          # - ORDERER_GENERAL_LOGLEVEL=error
          - ORDERER_GENERAL_LOGLEVEL=debug
          - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
          - ORDERER_GENERAL_LISTENPORT=7050
          #- ORDERER_GENERAL_GENESISPROFILE=AntiMothOrdererGenesis
          - ORDERER_GENERAL_GENESISMETHOD=file
          - ORDERER_GENERAL_GENESISFILE=/var/hyperledger/orderer/orderer.genesis.block
          - ORDERER_GENERAL_LOCALMSPID=OrdererMSP
          - ORDERER_GENERAL_LOCALMSPDIR=/var/hyperledger/orderer/msp
          #- ORDERER_GENERAL_LEDGERTYPE=ram
          #- ORDERER_GENERAL_LEDGERTYPE=file
          # enabled TLS
          - ORDERER_GENERAL_TLS_ENABLED=false
          - 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]
        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
        networks:
          default:
            aliases:
              - aberic
        ports:
          - 7050:7050

然后将编写好的启动文件上传到10.82.80.83服务器的~/go/src/github.com/hyperledger/fabric/aberic目录下，并运行如下命令启动Orderer排序服务节点：

~/go/src/github.com/hyperledger/fabric/aberic$ docker-compose -f docker-orderer.yaml  up –d

启动完成后查看是否启动成功：

docker ps

## 第三部部署peer0.org1节点 ##

编写docker-peer0.org1.yaml启动文件，源码如下：

# Copyright IBM Corp. All Rights Reserved.
    #
    # SPDX-License-Identifier: Apache-2.0
    #
    
    version: '2'
    
    services:
    
      couchdb:
        container_name: couchdb
        image: hyperledger/fabric-couchdb
        # Comment/Uncomment the port mapping if you want to hide/expose the CouchDB service,
        # for example map it to utilize Fauxton User Interface in dev environments.
        ports:
          - "5984:5984"
    
      ca:
        container_name: ca
        image: hyperledger/fabric-ca
        environment:
          - FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server
          - FABRIC_CA_SERVER_CA_NAME=ca
          - FABRIC_CA_SERVER_TLS_ENABLED=false
          - FABRIC_CA_SERVER_TLS_CERTFILE=/etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem
          - FABRIC_CA_SERVER_TLS_KEYFILE=/etc/hyperledger/fabric-ca-server-config/15d53ba909ffe5ef0038b1125b58e0ebc521f6693e43652307a92ee1c9c9d258_sk
        ports:
          - "7054:7054"
        command: sh -c 'fabric-ca-server start --ca.certfile /etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem --ca.keyfile /etc/hyperledger/fabric-ca-server-config/15d53ba909ffe5ef0038b1125b58e0ebc521f6693e43652307a92ee1c9c9d258_sk -b admin:adminpw -d'
        volumes:
          - ./crypto-config/peerOrganizations/org1.example.com/ca/:/etc/hyperledger/fabric-ca-server-config
    
      peer0.org1.example.com:
        container_name: peer0.org1.example.com
        image: hyperledger/fabric-peer
        environment:
          - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
          - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb:5984
    
          - CORE_PEER_ID=peer0.org1.example.com
          - CORE_PEER_NETWORKID=aberic
          - CORE_PEER_ADDRESS=peer0.org1.example.com:7051
          - CORE_PEER_CHAINCODELISTENADDRESS=peer0.org1.example.com: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=aberic
          # - CORE_LOGGING_LEVEL=ERROR
          - CORE_LOGGING_LEVEL=DEBUG
          - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=aberic_default
          - CORE_PEER_GOSSIP_SKIPHANDSHAKE=true
          - CORE_PEER_GOSSIP_USELEADERELECTION=true
          - CORE_PEER_GOSSIP_ORGLEADER=false
          - CORE_PEER_PROFILE_ENABLED=false
          - CORE_PEER_TLS_ENABLED=false
          - 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
        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
        working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
        command: peer node start
        ports:
          - 7051:7051
          - 7052:7052
          - 7053:7053
        depends_on:
          - couchdb
        networks:
          default:
            aliases:
              - aberic
        extra_hosts:
          - "orderer.example.com:10.82.80.83"
    
      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=ERROR
          - CORE_LOGGING_LEVEL=DEBUG
          - CORE_PEER_ID=cli
          - CORE_PEER_ADDRESS=peer0.org1.example.com:7051
          - CORE_PEER_LOCALMSPID=Org1MSP
          - CORE_PEER_TLS_ENABLED=false
          - 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/aberic/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:10.82.80.83"
          - "peer0.org1.example.com:10.82.80.82"

然后将编写好的启动文件上传到10.82.80.82服务器的~/go/src/github.com/hyperledger/fabric/aberic目录下，并运行如下命令启动Orderer排序服务节点：

~/go/src/github.com/hyperledger/fabric/aberic$ docker-compose -f docker-peer0.org1.yaml  up –d

启动完成后查看是否启动成功：

docker ps

启动成功后通过如下命令进入cli容器进行channel的相关操作：

~/go/src/github.com/hyperledger/fabric/aberic$ docker exec -it cli bash

创建通道：

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer channel create -o orderer.example.com:7050 -c mychannel -t 50 -f ./channel-artifacts//mychannel.tx

加入通道：

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer channel join -b mychannel.block

安装链码：

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode install -n mychannel -p github.com/hyperledger/fabric/aberic/chaincode/go/chaincode_example02 -v 1.0

实例化链码：

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode instantiate -o orderer.example.com:7050 -C mychannel -n mychannel -c'{"Args":["init","A","10","B","10"]}' -P "OR ('Org1MSP.member')" -v 1.0

查询A账户：

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode query -C mychannel -n mychannel -c '{"Args":["query","A"]}'

查询B账户：

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode query -C mychannel -n mychannel -c '{"Args":["query","B"]}'

A向B转账5

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode invoke -C mychannel -n mychannel -c '{"Args":["invoke","A","B","5"]}'

## 第四步部署peer1.org1节点 ##

编写docker-peer1.org1.yaml启动文件，源码如下：

# Copyright IBM Corp. All Rights Reserved.
    #
    # SPDX-License-Identifier: Apache-2.0
    #
    
    version: '2'
    
    services:
    
      couchdb:
        container_name: couchdb
        image: hyperledger/fabric-couchdb
        # Comment/Uncomment the port mapping if you want to hide/expose the CouchDB service,
        # for example map it to utilize Fauxton User Interface in dev environments.
        ports:
          - "5984:5984"
    
      ca:
        container_name: ca
        image: hyperledger/fabric-ca
        environment:
          - FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server
          - FABRIC_CA_SERVER_CA_NAME=ca
          - FABRIC_CA_SERVER_TLS_ENABLED=false
          - FABRIC_CA_SERVER_TLS_CERTFILE=/etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem
          - FABRIC_CA_SERVER_TLS_KEYFILE=/etc/hyperledger/fabric-ca-server-config/ab7dca5e5f6b1cc24c2023764c5b34d1f78d8614d2a11e74178d2d5509bd3be8_sk
        ports:
          - "7054:7054"
        command: sh -c 'fabric-ca-server start --ca.certfile /etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem --ca.keyfile /etc/hyperledger/fabric-ca-server-config/ab7dca5e5f6b1cc24c2023764c5b34d1f78d8614d2a11e74178d2d5509bd3be8_sk -b admin:adminpw -d'
        volumes:
          - ./crypto-config/peerOrganizations/org1.example.com/ca/:/etc/hyperledger/fabric-ca-server-config
    
      peer1.org1.example.com:
        container_name: peer1.org1.example.com
        image: hyperledger/fabric-peer
        environment:
          - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
          - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb:5984
    
          - CORE_PEER_ID=peer1.org1.example.com
          - CORE_PEER_NETWORKID=aberic
          - CORE_PEER_ADDRESS=peer1.org1.example.com:7051
          - CORE_PEER_CHAINCODELISTENADDRESS=peer1.org1.example.com: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=aberic
          # - CORE_LOGGING_LEVEL=ERROR
          - CORE_LOGGING_LEVEL=DEBUG
          - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=aberic_default
          - CORE_PEER_GOSSIP_SKIPHANDSHAKE=true
          - CORE_PEER_GOSSIP_USELEADERELECTION=true
          - CORE_PEER_GOSSIP_ORGLEADER=false
          - CORE_PEER_PROFILE_ENABLED=false
          - CORE_PEER_TLS_ENABLED=false
          - 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
        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
        working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
        command: peer node start
        ports:
          - 7051:7051
          - 7052:7052
          - 7053:7053
        depends_on:
          - couchdb
        networks:
          default:
            aliases:
              - aberic
        extra_hosts:
         - "orderer.example.com:10.82.80.83"
    
      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=ERROR
          - CORE_LOGGING_LEVEL=DEBUG
          - CORE_PEER_ID=cli
          - CORE_PEER_ADDRESS=peer1.org1.example.com:7051
          - CORE_PEER_LOCALMSPID=Org1MSP
          - CORE_PEER_TLS_ENABLED=false
          - 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/aberic/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:
          - peer1.org1.example.com
        extra_hosts:
         - "orderer.example.com:10.82.80.83"
         - "peer1.org1.example.com:10.82.80.85"

然后将编写好的启动文件上传到10.82.80.85服务器的~/go/src/github.com/hyperledger/fabric/aberic目录下，并运行如下命令启动Orderer排序服务节点：

~/go/src/github.com/hyperledger/fabric/aberic$ docker-compose -f docker-peer1.org1.yaml  up –d

启动完成后查看是否启动成功：

docker ps

首先是加入通道，peer1.org1若想加入一个通道，需要获取该通道的block文件，以 mychannel.block 文件为入口，该文件位于 peer0.org1 主机 cli 容器的 /opt/gopath/src/github.com/hyperledger/fabric/peer 目录下。在cli容器内/opt/gopath/src/github.com/hyperledger/fabric/peer目录下可以看到mychannel.block文件，现在需要将该文件从容器中复制到物理机真是路径下，退出当前容器并执行如下命令，将mychannel.block文件复制到~/go/src/github.com/hyperledger/fabric/aberic/channel-artifacts目录下：

cd ~/go/src/github.com/hyperledger/fabric/aberic
    docker cp <ContainerID>:/opt/gopath/src/github.com/hyperledger/fabric/peer/mychannel.block ./channel-artifacts/

ContainerID为容器的ID,可以用cli代替，也可以是有一串数字和字母组合成ID号。

将 mychannel.block 文件拷贝到 peer1.org1 主机 ~/go/src/github.com/hyperledger/fabric/aberic/channel-artifacts 目录下，之后登入 peer1.org1 主机，然后将mychannel.block 文件拷贝到peer1.org1 主机的cli容器中：

cd  ~/go/src/github.com/hyperledger/fabric/aberic
    docker cp ./channel-artifacts/mychannel.block cli:/opt/gopath/src/github.com/hyperledger/fabric/peer/

加入通道：

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer channel join -b mychannel.block

安装链码：

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode install -n mychannel -p github.com/hyperledger/fabric/aberic/chaincode/go/chaincode_example02 -v 1.0

查询A账户：

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode query -C mychannel -n mychannel -c '{"Args":["query","A"]}'

查询B账户：

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode query -C mychannel -n mychannel -c '{"Args":["query","B"]}'

A向B转账5

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode invoke -C mychannel -n mychannel -c '{"Args":["invoke","A","B","5"]}'

## 第五步部署peer0.org2节点 ##

编写docker-peer0.org2.yaml启动文件，源码如下：

# Copyright IBM Corp. All Rights Reserved.
    #
    # SPDX-License-Identifier: Apache-2.0
    #
    
    version: '2'
    
    services:
    
      couchdb:
        container_name: couchdb
        image: hyperledger/fabric-couchdb
        # Comment/Uncomment the port mapping if you want to hide/expose the CouchDB service,
        # for example map it to utilize Fauxton User Interface in dev environments.
        ports:
          - "5984:5984"
    
      ca:
        container_name: ca
        image: hyperledger/fabric-ca
        environment:
          - FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server
          - FABRIC_CA_SERVER_CA_NAME=ca
          - FABRIC_CA_SERVER_TLS_ENABLED=false
          - FABRIC_CA_SERVER_TLS_CERTFILE=/etc/hyperledger/fabric-ca-server-config/ca.org2.example.com-cert.pem
          - FABRIC_CA_SERVER_TLS_KEYFILE=/etc/hyperledger/fabric-ca-server-config/638c62f6073cf84d4a897b90fa31c0d53c4c2ffaa0b0be1c3c7df233eb33a27a_sk
        ports:
          - "7054:7054"
        command: sh -c 'fabric-ca-server start --ca.certfile /etc/hyperledger/fabric-ca-server-config/ca.org2.example.com-cert.pem --ca.keyfile /etc/hyperledger/fabric-ca-server-config/638c62f6073cf84d4a897b90fa31c0d53c4c2ffaa0b0be1c3c7df233eb33a27a_sk -b admin:adminpw -d'
        volumes:
          - ./crypto-config/peerOrganizations/org2.example.com/ca/:/etc/hyperledger/fabric-ca-server-config
    
      peer0.org2.example.com:
        container_name: peer0.org2.example.com
        image: hyperledger/fabric-peer
        environment:
          - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
          - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb:5984
    
          - CORE_PEER_ID=peer0.org2.example.com
          - CORE_PEER_NETWORKID=aberic
          - CORE_PEER_ADDRESS=peer0.org2.example.com:7051
          - CORE_PEER_CHAINCODELISTENADDRESS=peer0.org2.example.com:7052
          - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org2.example.com:7051
          - CORE_PEER_LOCALMSPID=Org2MSP
    
          - 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=aberic
          # - CORE_LOGGING_LEVEL=ERROR
          - CORE_LOGGING_LEVEL=DEBUG
          - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=aberic_default
          - CORE_PEER_GOSSIP_SKIPHANDSHAKE=true
          - CORE_PEER_GOSSIP_USELEADERELECTION=true
          - CORE_PEER_GOSSIP_ORGLEADER=false
          - CORE_PEER_PROFILE_ENABLED=false
          - CORE_PEER_TLS_ENABLED=false
          - 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
        volumes:
            - /var/run/:/host/var/run/
            - ./crypto-config/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/msp:/etc/hyperledger/fabric/msp
            - ./crypto-config/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls:/etc/hyperledger/fabric/tls
        working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
        command: peer node start
        ports:
          - 7051:7051
          - 7052:7052
          - 7053:7053
        depends_on:
          - couchdb
        networks:
          default:
            aliases:
              - aberic
        extra_hosts:
         - "orderer.example.com:10.82.80.83"
    
      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=ERROR
          - CORE_LOGGING_LEVEL=DEBUG
          - CORE_PEER_ID=cli
          - CORE_PEER_ADDRESS=peer0.org2.example.com:7051
          - CORE_PEER_LOCALMSPID=Org2MSP
          - CORE_PEER_TLS_ENABLED=false
          - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/server.crt
          - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/server.key
          - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt
          - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.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/aberic/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.org2.example.com
        extra_hosts:
         - "orderer.example.com:10.82.80.83"
         - "peer0.org2.example.com:10.82.80.84"

在这里需要注意要将证书的文件名替换为org2的,MSPID和IP地址要换掉。

将 mychannel.block 文件拷贝到 peer1.org1 主机 ~/go/src/github.com/hyperledger/fabric/aberic/channel-artifacts 目录下，之后登入 peer1.org1 主机，然后将mychannel.block 文件拷贝到peer0.org2 主机的cli容器中：

cd  ~/go/src/github.com/hyperledger/fabric/aberic
    docker cp ./channel-artifacts/mychannel.block cli:/opt/gopath/src/github.com/hyperledger/fabric/peer/

加入通道：

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer channel join -b mychannel.block

安装链码：

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode install -n mychannel -p github.com/hyperledger/fabric/aberic/chaincode/go/chaincode_example02 -v 1.0

查询A账户：

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode query -C mychannel -n mychannel -c '{"Args":["query","A"]}'

查询B账户：

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode query -C mychannel -n mychannel -c '{"Args":["query","B"]}'

A向B转账5（注意这里是不成功的，因为背书策略的原因）

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode invoke -C mychannel -n mychannel -c '{"Args":["invoke","A","B","5"]}'

## 第六步部署peer1.org2节点 ##

编写docker-peer0.org2.yaml启动文件，源码如下：

# Copyright IBM Corp. All Rights Reserved.
    #
    # SPDX-License-Identifier: Apache-2.0
    #
    
    version: '2'
    
    services:
    
      couchdb:
        container_name: couchdb
        image: hyperledger/fabric-couchdb
        # Comment/Uncomment the port mapping if you want to hide/expose the CouchDB service,
        # for example map it to utilize Fauxton User Interface in dev environments.
        ports:
          - "5984:5984"
    
      ca:
        container_name: ca
        image: hyperledger/fabric-ca
        environment:
          - FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server
          - FABRIC_CA_SERVER_CA_NAME=ca
          - FABRIC_CA_SERVER_TLS_ENABLED=false
          - FABRIC_CA_SERVER_TLS_CERTFILE=/etc/hyperledger/fabric-ca-server-config/ca.org2.example.com-cert.pem
          - FABRIC_CA_SERVER_TLS_KEYFILE=/etc/hyperledger/fabric-ca-server-config/638c62f6073cf84d4a897b90fa31c0d53c4c2ffaa0b0be1c3c7df233eb33a27a_sk
        ports:
          - "7054:7054"
        command: sh -c 'fabric-ca-server start --ca.certfile /etc/hyperledger/fabric-ca-server-config/ca.org2.example.com-cert.pem --ca.keyfile /etc/hyperledger/fabric-ca-server-config/638c62f6073cf84d4a897b90fa31c0d53c4c2ffaa0b0be1c3c7df233eb33a27a_sk -b admin:adminpw -d'
        volumes:
          - ./crypto-config/peerOrganizations/org2.example.com/ca/:/etc/hyperledger/fabric-ca-server-config
    
      peer1.org2.example.com:
        container_name: peer1.org2.example.com
        image: hyperledger/fabric-peer
        environment:
          - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
          - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb:5984
    
          - CORE_PEER_ID=peer1.org2.example.com
          - CORE_PEER_NETWORKID=aberic
          - CORE_PEER_ADDRESS=peer1.org2.example.com:7051
          - CORE_PEER_CHAINCODELISTENADDRESS=peer1.org2.example.com:7052
          - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org2.example.com:7051
          - CORE_PEER_LOCALMSPID=Org2MSP
    
          - 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=aberic
          # - CORE_LOGGING_LEVEL=ERROR
          - CORE_LOGGING_LEVEL=DEBUG
          - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=aberic_default
          - CORE_PEER_GOSSIP_SKIPHANDSHAKE=true
          - CORE_PEER_GOSSIP_USELEADERELECTION=true
          - CORE_PEER_GOSSIP_ORGLEADER=false
          - CORE_PEER_PROFILE_ENABLED=false
          - CORE_PEER_TLS_ENABLED=false
          - 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
        volumes:
            - /var/run/:/host/var/run/
            - ./crypto-config/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/msp:/etc/hyperledger/fabric/msp
            - ./crypto-config/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/tls:/etc/hyperledger/fabric/tls
        working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
        command: peer node start
        ports:
          - 7051:7051
          - 7052:7052
          - 7053:7053
        depends_on:
          - couchdb
        networks:
          default:
            aliases:
              - aberic
        extra_hosts:
         - "orderer.example.com:10.82.80.83"
    
      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=ERROR
          - CORE_LOGGING_LEVEL=DEBUG
          - CORE_PEER_ID=cli
          - CORE_PEER_ADDRESS=peer1.org2.example.com:7051
          - CORE_PEER_LOCALMSPID=Org2MSP
          - CORE_PEER_TLS_ENABLED=false
          - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/tls/server.crt
          - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/tls/server.key
          - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/tls/ca.crt
          - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.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/aberic/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:
          - peer1.org2.example.com
        extra_hosts:
         - "orderer.example.com:10.82.80.83"
         - "peer1.org2.example.com:10.82.80.86"

在这里需要注意要将证书的文件名替换为org2的,MSPID和IP地址要换掉。

cd  ~/go/src/github.com/hyperledger/fabric/aberic
    docker cp ./channel-artifacts/mychannel.block cli:/opt/gopath/src/github.com/hyperledger/fabric/peer/

加入通道：

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer channel join -b mychannel.block

安装链码：

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode install -n mychannel -p github.com/hyperledger/fabric/aberic/chaincode/go/chaincode_example02 -v 1.0

查询A账户：

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode query -C mychannel -n mychannel -c '{"Args":["query","A"]}'

查询B账户：

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode query -C mychannel -n mychannel -c '{"Args":["query","B"]}'

A向B转账5（注意这里是不成功的，因为背书策略的原因）

/opt/gopath/src/github.com/hyperledger/fabric/peer# peer chaincode invoke -C mychannel -n mychannel -c '{"Args":["invoke","A","B","5"]}'

到此Solo多机多节点部署完成！

[orderer.example.com]: http://orderer.example.com
[peer0.org1.example.com]: http://peer0.org1.example.com
[peer0.org2.example.com]: http://peer0.org2.example.com
[peer1.org1.example.com]: http://peer1.org1.example.com
[peer1.org2.example.com]: http://peer1.org2.example.com