Fabric部署多机版本

最新推荐文章于 2023-04-26 11:32:00 发布
最新推荐文章于 2023-04-26 11:32:00 发布
阅读量787 收藏 3
点赞数
分类专栏： Fabric 区块链 文章标签： fabric 多机部署 solo模式
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/sanqima/article/details/119361230
版权

    Fabric v1.4.3的First-network默认是单机版本，采用solo模式。下面介绍其多机版本的部署方法，即4 peer+1 order 它们都在不同的机器上运行。

1、节点描述

节点IP说明所在组织
order192.168.30.11排序节点独立
peer0.org1192.168.30.22普通节点org1
peer1.org1192.168.30.33普通节点org1
peer0.org2192.168.30.44普通节点org2
peer1.org2192.168.30.55普通节点org2

2、软件环境

    fabric-samples v1.4.3
    fabric v1.4.3
    fabric ca v1.4.3
    Ubuntu 16.04

3、将First-network复制一份,重命名为one,然后精简one文件夹

3.1 精简first-network

cd $GOPATH/src/github.com/hyperledger/fabric-samples
cp -r first-network one
cd one

    在order节点，对one/文件夹进行精简，得到2个文件夹+7个文件，如图(2)所示：

图(1) first-network复制之后，再精简得到one文件夹

    下面的创世区块、身份证书、通道配置文件，都是通过工具，在$GOPATH/src/github.com/hyperledger/fabric-samples/one里生成的。

3.2 修改端口

    a) 修改one/configtx.yaml里org2的锚节点peer0.org2，将其端口改为7051，如下所示:

        AnchorPeers:
            # AnchorPeers defines the location of peers which can be used
            # for cross org gossip communication.  Note, this value is only
            # encoded in the genesis block in the Application section context
            - Host: peer0.org2.example.com
              Port: 7051  ##修改此处

    b) 修改one/base/docker-compose-base.yaml里4个peer节点的端口，如下：
    order节点，使用7050端口。
    4个peer节点，除了CHAINCODEADDRESS=7052，CHAINCODELISTENADDRESS=7052以外，其他端口统一使用7051。

# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

services:

  orderer.example.com:
    container_name: orderer.example.com
    extends:
      file: peer-base.yaml
      service: orderer-base
    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
        - orderer.example.com:/var/hyperledger/production/orderer
    ports:
      - 7050:7050

  peer0.org1.example.com:
    container_name: peer0.org1.example.com
    extends:
      file: peer-base.yaml
      service: peer-base
    environment:
      - CORE_PEER_ID=peer0.org1.example.com
      - CORE_PEER_ADDRESS=peer0.org1.example.com:7051
      - CORE_PEER_LISTENADDRESS=0.0.0.0:7051
      - CORE_PEER_CHAINCODEADDRESS=peer0.org1.example.com:7052
      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052
      - CORE_PEER_GOSSIP_BOOTSTRAP=peer1.org1.example.com:7051
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.example.com:7051
      - CORE_PEER_LOCALMSPID=Org1MSP
    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
        - peer0.org1.example.com:/var/hyperledger/production
    ports:
      - 7051:7051

  peer1.org1.example.com:
    container_name: peer1.org1.example.com
    extends:
      file: peer-base.yaml
      service: peer-base
    environment:
      - CORE_PEER_ID=peer1.org1.example.com
      - CORE_PEER_ADDRESS=peer1.org1.example.com:7051
      - CORE_PEER_LISTENADDRESS=0.0.0.0: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_GOSSIP_BOOTSTRAP=peer0.org1.example.com:7051
      - CORE_PEER_LOCALMSPID=Org1MSP
    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
        - peer1.org1.example.com:/var/hyperledger/production

    ports:
      - 7051:7051

  peer0.org2.example.com:
    container_name: peer0.org2.example.com
    extends:
      file: peer-base.yaml
      service: peer-base
    environment:
      - CORE_PEER_ID=peer0.org2.example.com
      - CORE_PEER_ADDRESS=peer0.org2.example.com:7051
      - CORE_PEER_LISTENADDRESS=0.0.0.0:7051
      - CORE_PEER_CHAINCODEADDRESS=peer0.org2.example.com:7052
      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org2.example.com:7051
      - CORE_PEER_GOSSIP_BOOTSTRAP=peer1.org2.example.com:7051
      - CORE_PEER_LOCALMSPID=Org2MSP
    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
        - peer0.org2.example.com:/var/hyperledger/production
    ports:
      - 7051:7051

  peer1.org2.example.com:
    container_name: peer1.org2.example.com
    extends:
      file: peer-base.yaml
      service: peer-base
    environment:
      - CORE_PEER_ID=peer1.org2.example.com
      - CORE_PEER_ADDRESS=peer1.org2.example.com:7051
      - CORE_PEER_LISTENADDRESS=0.0.0.0:7051
      - CORE_PEER_CHAINCODEADDRESS=peer1.org2.example.com:7052
      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org2.example.com:7051
      - CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org2.example.com:7051
      - CORE_PEER_LOCALMSPID=Org2MSP
    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
        - peer1.org2.example.com:/var/hyperledger/production
    ports:
      - 7051:7051

3.3 制作身份证书

    cryptogen工具通过读取crypto-config.yaml配置文件，来生成组织结构与身份证书

cd ./fabric-sample/one
../bin/cryptogen generate --config=./crypto-config.yaml

3.4 生成创世区块

    configtxgen 工具通过读取 configtx.yaml 配置文件，来生成网络启动的配置文件

## 使能FABRIC_CFG_PATH 变量
export FABRIC_CFG_PATH=$PWD

## 生成创世区块
cd $GOPATH/src/github.com/hyperledger/fabric-samples/one
../bin/configtxgen -profile TwoOrgsOrdererGenesis -outputBlock ./channel-artifacts/genesis.block

3.5 生成通道配置文件

    创建一个mychannel的通道，并生成通道配置文件channel.tx，其保存在one/channel-artifacts目录下。

export CHANNEL_NAME=mychannel && ../bin/configtxgen -profile TwoOrgsChannel -outputCreateChannelTx ./channel-artifacts/channel.tx -channelID $CHANNEL_NAME

3.6 生成2个组织的锚节点文件

../bin/configtxgen -profile TwoOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org1MSPanchors.tx -channelID $CHANNEL_NAME -asOrg Org1MSP

../bin/configtxgen -profile TwoOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org2MSPanchors.tx -channelID $CHANNEL_NAME -asOrg Org2MSP

    把这个one文件夹，使用scp命令，或者ftp拷贝其他4个节点。

4、设置/etc/hosts

    order、peer0.org1、peer1.org1、peer0.org2、peer1.org2这5台主机都需要配置/etc/hosts，如下所示。
    a）打开/etc/hosts

sudo vim /etc/hosts

    b) 添加5个域名解析

192.168.30.11 orderer.example.com     
192.168.30.22 peer0.org1.example.com  
192.168.30.33 peer1.org1.example.com  
192.168.30.44 peer0.org2.example.com  
192.168.30.55 peer1.org2.example.com

    c) 重启网络

sudo /etc/init.d/networking restart

5、设置配置文件

5.1 order节点配置

    a) 复制docker-compose-cli.yaml，并重命名为docker-compose-orderer.yaml

cd $GOPATH/src/github.com/hyperledger/fabric-samples/one
cp docker-compose-cli.yaml docker-compose-orderer.yaml

    b) 精简docker-compose-orderer.yaml文件，如下：
    //docker-compose-orderer.yaml

# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

volumes:
  orderer.example.com:


networks:
  byfn:

services:

  orderer.example.com:
    extends:
      file:   base/docker-compose-base.yaml
      service: orderer.example.com
    container_name: orderer.example.com
    networks:
      - byfn

5.2 peer0.org1节点配置

    a) 复制docker-compose-cli.yaml，并重命名为docker-compose-peer0-Org1.yaml

cd $GOPATH/src/github.com/hyperledger/fabric-samples/one
cp docker-compose-cli.yaml docker-compose-peer0-Org1.yaml

    b) 精简docker-compose-peer0-Org1.yaml文件，如下：
//docker-compose-peer0-Org1.yaml

# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

volumes:
  peer0.org1.example.com:


networks:
  byfn:

services:

  peer0.org1.example.com:
    container_name: peer0.org1.example.com
    extends:
      file:  base/docker-compose-base.yaml
      service: peer0.org1.example.com
    networks:
      - byfn
    extra_hosts:  ##填写与该结点相连的其他节点IP
      - "orderer.example.com:192.168.30.11"
      - "peer1.org1.example.com:192.168.30.33"
      - "peer0.org2.example.com:192.168.30.44"
      - "peer1.org2.example.com:192.168.30.55"     


  cli:
    container_name: cli
    image: hyperledger/fabric-tools:$IMAGE_TAG
    tty: true
    stdin_open: true
    environment:
      - SYS_CHANNEL=$SYS_CHANNEL
      - GOPATH=/opt/gopath
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      #- FABRIC_LOGGING_SPEC=DEBUG
      - FABRIC_LOGGING_SPEC=INFO
      - 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
    command: /bin/bash
    volumes:
        - /var/run/:/host/var/run/
        - ./../chaincode/:/opt/gopath/src/github.com/chaincode
        - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
        - ./scripts:/opt/gopath/src/github.com/hyperledger/fabric/peer/scripts/
        - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
    depends_on:
      - peer0.org1.example.com
    networks:
      - byfn
    extra_hosts:  ##填写所有的节点IP
      - "orderer.example.com:192.168.30.11"
      - "peer0.org1.example.com:192.168.30.22" 
      - "peer1.org1.example.com:192.168.30.33"
      - "peer0.org2.example.com:192.168.30.44"
      - "peer1.org2.example.com:192.168.30.55"

5.3 peer1.org1节点配置

    a) 复制docker-compose-cli.yaml，并重命名为docker-compose-peer1-Org1.yaml

cd $GOPATH/src/github.com/hyperledger/fabric-samples/one
cp docker-compose-cli.yaml docker-compose-peer1-Org1.yaml

    b) 精简docker-compose-peer11-Org1.yaml文件，如下：
    //docker-compose-peer1-Org1.yaml

# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

volumes:
  peer1.org1.example.com:


networks:
  byfn:

services:

  peer1.org1.example.com:
    container_name: peer1.org1.example.com
    extends:
      file:  base/docker-compose-base.yaml
      service: peer1.org1.example.com
    networks:
      - byfn
    extra_hosts:  ##填写与该结点相连的其他节点IP
      - "orderer.example.com:192.168.30.11"
      - "peer0.org1.example.com:192.168.30.22" 
      - "peer0.org2.example.com:192.168.30.44"
      - "peer1.org2.example.com:192.168.30.55"   


  cli:
    container_name: cli
    image: hyperledger/fabric-tools:$IMAGE_TAG
    tty: true
    stdin_open: true
    environment:
      - SYS_CHANNEL=$SYS_CHANNEL
      - GOPATH=/opt/gopath
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      #- FABRIC_LOGGING_SPEC=DEBUG
      - FABRIC_LOGGING_SPEC=INFO
      - 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
    command: /bin/bash
    volumes:
        - /var/run/:/host/var/run/
        - ./../chaincode/:/opt/gopath/src/github.com/chaincode
        - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
        - ./scripts:/opt/gopath/src/github.com/hyperledger/fabric/peer/scripts/
        - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
    depends_on:
      - peer1.org1.example.com
    networks:
      - byfn
    extra_hosts:  ##填写所有的节点IP
      - "orderer.example.com:192.168.30.11"
      - "peer0.org1.example.com:192.168.30.22" 
      - "peer1.org1.example.com:192.168.30.33"
      - "peer0.org2.example.com:192.168.30.44"
      - "peer1.org2.example.com:192.168.30.55"

5.4 peer0.org2节点配置

    a) 复制docker-compose-cli.yaml，并重命名为docker-compose-peer0-Org2.yaml

cd $GOPATH/src/github.com/hyperledger/fabric-samples/one
cp docker-compose-cli.yaml docker-compose-peer0-Org2.yaml

    b) 精简docker-compose-peer0-Org2.yaml文件，如下：
    //docker-compose-peer0-Org2.yaml

# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

volumes:
  peer0.org2.example.com:


networks:
  byfn:

services:

  peer0.org2.example.com:
    container_name: peer0.org2.example.com
    extends:
      file:  base/docker-compose-base.yaml
      service: peer0.org2.example.com
    networks:
      - byfn
    extra_hosts:  
      - "orderer.example.com:192.168.30.11"
      - "peer0.org1.example.com:192.168.30.22" 
      - "peer1.org1.example.com:192.168.30.33"
      - "peer1.org2.example.com:192.168.30.55"   


  cli:
    container_name: cli
    image: hyperledger/fabric-tools:$IMAGE_TAG
    tty: true
    stdin_open: true
    environment:
      - SYS_CHANNEL=$SYS_CHANNEL
      - GOPATH=/opt/gopath
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      #- FABRIC_LOGGING_SPEC=DEBUG
      - FABRIC_LOGGING_SPEC=INFO
      - CORE_PEER_ID=cli
      - CORE_PEER_ADDRESS=peer0.org2.example.com:7051
      - CORE_PEER_LOCALMSPID=Org2MSP
      - CORE_PEER_TLS_ENABLED=true
      - 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
    command: /bin/bash
    volumes:
        - /var/run/:/host/var/run/
        - ./../chaincode/:/opt/gopath/src/github.com/chaincode
        - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
        - ./scripts:/opt/gopath/src/github.com/hyperledger/fabric/peer/scripts/
        - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
    depends_on:
      - peer0.org2.example.com
    networks:
      - byfn
    extra_hosts:  
      - "orderer.example.com:192.168.30.11"
      - "peer0.org1.example.com:192.168.30.22" 
      - "peer1.org1.example.com:192.168.30.33"
      - "peer0.org2.example.com:192.168.30.44"
      - "peer1.org2.example.com:192.168.30.55"

5.5 peer1.org2节点配置

    a) 复制docker-compose-cli.yaml，并重命名为docker-compose-peer1-Org2.yaml

cd $GOPATH/src/github.com/hyperledger/fabric-samples/one
cp docker-compose-cli.yaml docker-compose-peer1-Org2.yaml

    b) 精简docker-compose-peer1-Org2.yaml文件，如下：
    //docker-compose-peer1-Org2.yaml

# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

volumes:
  peer1.org2.example.com:


networks:
  byfn:

services:

  peer1.org2.example.com:
    container_name: peer1.org2.example.com
    extends:
      file:  base/docker-compose-base.yaml
      service: peer1.org2.example.com
    networks:
      - byfn
    extra_hosts:  
      - "orderer.example.com:192.168.30.11"
      - "peer0.org1.example.com:192.168.30.22" 
      - "peer1.org1.example.com:192.168.30.33"
      - "peer0.org2.example.com:192.168.30.44" 
   


  cli:
    container_name: cli
    image: hyperledger/fabric-tools:$IMAGE_TAG
    tty: true
    stdin_open: true
    environment:
      - SYS_CHANNEL=$SYS_CHANNEL
      - GOPATH=/opt/gopath
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      #- FABRIC_LOGGING_SPEC=DEBUG
      - FABRIC_LOGGING_SPEC=INFO
      - CORE_PEER_ID=cli
      - CORE_PEER_ADDRESS=peer1.org2.example.com:7051
      - CORE_PEER_LOCALMSPID=Org2MSP
      - CORE_PEER_TLS_ENABLED=true
      - 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
    command: /bin/bash
    volumes:
        - /var/run/:/host/var/run/
        - ./../chaincode/:/opt/gopath/src/github.com/chaincode
        - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
        - ./scripts:/opt/gopath/src/github.com/hyperledger/fabric/peer/scripts/
        - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
    depends_on:
      - peer1.org2.example.com
    networks:
      - byfn
    extra_hosts:  
      - "orderer.example.com:192.168.30.11"
      - "peer0.org1.example.com:192.168.30.22" 
      - "peer1.org1.example.com:192.168.30.33"
      - "peer0.org2.example.com:192.168.30.44"
      - "peer1.org2.example.com:192.168.30.55"

5.6 peer0.org1的CouchDB配置

    a) 复制docker-compose-couch.yaml，并重命名为docker-compose-peer0-Org1-couch.yaml

cd $GOPATH/src/github.com/hyperledger/fabric-samples/one
cp docker-compose-couch.yaml docker-compose-peer0-Org1-couch.yaml

    b) 精简docker-compose-peer0-Org1-couch.yaml文件，如下：
    //docker-compose-peer0-Org1-couch.yaml

# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

networks:
  byfn:

services:
  couchdb0:
    container_name: couchdb0
    image: hyperledger/fabric-couchdb
    # Populate the COUCHDB_USER and COUCHDB_PASSWORD to set an admin user and password
    # for CouchDB.  This will prevent CouchDB from operating in an "Admin Party" mode.
    environment:
      - COUCHDB_USER=
      - COUCHDB_PASSWORD=
    # 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"
    networks:
      - byfn

  peer0.org1.example.com: ##指定节点域名
    environment:
      - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
      - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb0:5984
      # The CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME and CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD
      # provide the credentials for ledger to connect to CouchDB.  The username and password must
      # match the username and password set for the associated CouchDB.
      - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=
      - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=
    depends_on:
      - couchdb0

5.7 peer1.org1的CouchDB配置

    a) 复制docker-compose-couch.yaml，并重命名为docker-compose-peer1-Org1-couch.yaml

cd $GOPATH/src/github.com/hyperledger/fabric-samples/one
cp docker-compose-couch.yaml docker-compose-peer1-Org1-couch.yaml

    b) 精简docker-compose-peer1-Org1-couch.yaml文件，如下：
    //docker-compose-peer1-Org1-couch.yaml

# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

networks:
  byfn:

services:
  couchdb0:
    container_name: couchdb0
    image: hyperledger/fabric-couchdb
    # Populate the COUCHDB_USER and COUCHDB_PASSWORD to set an admin user and password
    # for CouchDB.  This will prevent CouchDB from operating in an "Admin Party" mode.
    environment:
      - COUCHDB_USER=
      - COUCHDB_PASSWORD=
    # 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"
    networks:
      - byfn

  peer1.org1.example.com: ##指定节点域名
    environment:
      - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
      - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb0:5984
      # The CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME and CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD
      # provide the credentials for ledger to connect to CouchDB.  The username and password must
      # match the username and password set for the associated CouchDB.
      - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=
      - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=
    depends_on:
      - couchdb0

5.8 peer0.org2的CouchDB配置

    a) 复制docker-compose-couch.yaml，并重命名为docker-compose-peer0-Org2-couch.yaml

cd $GOPATH/src/github.com/hyperledger/fabric-samples/one
cp docker-compose-couch.yaml docker-compose-peer0-Org2-couch.yaml

    b) 精简docker-compose-peer0-Org2-couch.yaml文件，如下：
    //docker-compose-peer0-Org2-couch.yaml

# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

networks:
  byfn:

services:
  couchdb0:
    container_name: couchdb0
    image: hyperledger/fabric-couchdb
    # Populate the COUCHDB_USER and COUCHDB_PASSWORD to set an admin user and password
    # for CouchDB.  This will prevent CouchDB from operating in an "Admin Party" mode.
    environment:
      - COUCHDB_USER=
      - COUCHDB_PASSWORD=
    # 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"
    networks:
      - byfn

  peer0.org2.example.com:
    environment:
      - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
      - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb0:5984
      # The CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME and CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD
      # provide the credentials for ledger to connect to CouchDB.  The username and password must
      # match the username and password set for the associated CouchDB.
      - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=
      - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=
    depends_on:
      - couchdb0

5.9 peer1.org2的CouchDB配置

    a) 复制docker-compose-couch.yaml，并重命名为docker-compose-peer1-Org2-couch.yaml

cd $GOPATH/src/github.com/hyperledger/fabric-samples/one
cp docker-compose-couch.yaml docker-compose-peer1-Org2-couch.yaml

    b) 精简docker-compose-peer1-Org2-couch.yaml文件，如下：
    //docker-compose-peer1-Org2-couch.yaml

# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

networks:
  byfn:

services:
  couchdb0:
    container_name: couchdb0
    image: hyperledger/fabric-couchdb
    # Populate the COUCHDB_USER and COUCHDB_PASSWORD to set an admin user and password
    # for CouchDB.  This will prevent CouchDB from operating in an "Admin Party" mode.
    environment:
      - COUCHDB_USER=
      - COUCHDB_PASSWORD=
    # 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"
    networks:
      - byfn

  peer1.org2.example.com:
    environment:
      - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
      - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb0:5984
      # The CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME and CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD
      # provide the credentials for ledger to connect to CouchDB.  The username and password must
      # match the username and password set for the associated CouchDB.
      - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=
      - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=
    depends_on:
      - couchdb0

5.10 节点的目录结构

    a) order节点的目录结构

图(1) order节点的目录结构

    b) peer0.org1节点的目录结构

图(2) peer0.org1节点的目录结构

    c) peer1.org1节点的目录结构

图(3) peer1.org1节点的目录结构

    d) peer0.org2节点的目录结构

图(4) peer0.org2节点的目录结构

    f) peer1.org2节点的目录结构

图(f) peer1.org2节点的目录结构

6、启动order和peer节点

6.1 启动order

cd /usr/local/gocode/src/github.com/hyperledger/fabric-samples/one
sudo docker-compose -f docker-compose-orderer.yaml up

6.2 启动peer0.org1

sudo docker-compose -f docker-compose-peer0-Org1.yaml -f docker-compose-peer0-Org1-couch.yaml up

6.3 启动peer1.org1

sudo docker-compose -f docker-compose-peer1-Org1.yaml -f docker-compose-peer1-Org1-couch.yaml up

6.4 启动peer0.org2

sudo docker-compose -f docker-compose-peer0-Org2.yaml -f docker-compose-peer0-Org2-couch.yaml up

6.5 启动peer1.org2

sudo docker-compose -f docker-compose-peer1-Org2.yaml -f docker-compose-peer1-Org2-couch.yaml up

7、创建通道文件，并拷贝到其他3个peer节点

    通道文件，保存了通道里的组织个数，它只需要创建一次，把拷贝到各个peer节点即可。这里从peer0.org1节点创建通道文件mychannel.block，然后把它拷贝到peer0.org2、peer1.org1、peer1.org2节点里。具体如下：

7.1 进入peer0.org1的cli容器

docker exec -it cli bash

7.2 设置环境，并创建通道文件

export CHANNEL_NAME=mychannel
export 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 $CHANNEL_NAME -f ./channel-artifacts/channel.tx --tls --cafile $ORDERER_CA

    得到mychannel.block，将这个mychannel.block文件，拷贝peer0.org2、peer1.org1、peer.org2的peer目录里，方法如下：

    a）另外打开一个终端2，将mychannel.block从peer0.org 的cli容器拷贝到 one/myblcok文件夹

## 创建myblock文件夹
cd /usr/local/gocode/src/github.com/hyperledger/fabric-samples/one
mkdir myblock

## 将mychannel.block文件拷贝出来
sudo docker cp cli:/opt/gopath/src/github.com/hyperledger/fabric/peer/mychannel.block /usr/local/gocode/src/github.com/hyperledger/fabric-samples/one

    b) 然后，用ftp工具把mychannel.block拷贝其他3个peer节点的/usr/local/gocode/src/github.com/hyperledger/fabric-samples/one/myblock目录，
再使用sudo docker cp命令，将其拷贝到peer0.org2、peer1.org1、peer.org2的cli容器里如下所示：

sudo docker cp /usr/local/gocode/src/github.com/hyperledger/fabric-samples/one/myblock/mychannel.block cli:/opt/gopath/src/github.com/hyperledger/fabric/peer/

8、加入通道，并设置锚节点

8.1 将4个peer节点加入通道

    下面这3条命令，分别在4个peer的cli容器，都运行一遍即可。

export CHANNEL_NAME=mychannel
export 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 join -b mychannel.block

8.2 设置锚节点，并安装链码

    a) 将peer0.org1设为组织org1的锚节点，同时安装链码

peer channel update -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/Org1MSPanchors.tx --tls --cafile $ORDERER_CA
peer chaincode install -n mycc -v 1.0 -p github.com/chaincode/chaincode_example02/go/

    b) 将peer0.org2设为组织org2的锚节点，同时安装链码

peer channel update -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/Org2MSPanchors.tx --tls --cafile $ORDERER_CA
peer chaincode install -n mycc -v 1.0 -p github.com/chaincode/chaincode_example02/go/

9、实例化链码，并测试

9.1 实例化

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

9.2 查询

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

9.3 调用

peer chaincode invoke -o orderer.example.com:7050 --tls --cafile $ORDERER_CA -C $CHANNEL_NAME -n mycc --peerAddresses peer0.org1.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt --peerAddresses peer0.org2.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt -c '{"Args":["invoke","a","b","10"]}'

    效果如下：

图(2) 链码的实例化和调用

10、关闭并清空fabric网络

    当不需要使用fabric时，请关闭fabric网络，如下：

10.1 关闭并清空order

sudo docker-compose -f docker-compose-orderer.yaml down 
sudo docker-compose -f docker-compose-orderer.yaml down --volumes

10.2 关闭并清空peer0-Org1

sudo docker-compose -f docker-compose-peer0-Org1.yaml -f docker-compose-peer0-Org1-couch.yaml down
sudo docker-compose -f docker-compose-peer0-Org1.yaml -f docker-compose-peer0-Org1-couch.yaml down --volumes

10.3 关闭并清空peer1-Org1

sudo docker-compose -f docker-compose-peer1-Org1.yaml -f docker-compose-peer1-Org1-couch.yaml down
sudo docker-compose -f docker-compose-peer1-Org1.yaml -f docker-compose-peer1-Org1-couch.yaml down --volumes

10.4 关闭并清空peer0-Org2

sudo docker-compose -f docker-compose-peer0-Org2.yaml -f docker-compose-peer0-Org2-couch.yaml down
sudo docker-compose -f docker-compose-peer0-Org2.yaml -f docker-compose-peer0-Org2-couch.yaml down --volumes

10.5 关闭并清空peer1-Org2

sudo docker-compose -f docker-compose-peer1-Org2.yaml -f docker-compose-peer1-Org2-couch.yaml down
sudo docker-compose -f docker-compose-peer1-Org2.yaml -f docker-compose-peer1-Org2-couch.yaml down --volumes
sanqima
关注
专栏目录
多机部署Hyperledger Fabric+Composer(两台机器)
03-01
Land-network网络由两个组织组成：Org1和Org2。组织Org1使用域名org1.example.com。会员服务提供商（MSP）Org1被称为Org1MSP。组织Org2使用域名org2.example.com。MSP for Org2被称为Org2MSP。在本教程中，您将部署一个blockchain业务网络，无论是组织Org1，Org2并能与之交互。 两台机器分别是VM1(192.168.1.101)和VM2(192.168.1.102)。Composer版本采用0.20.5，Hyperledger Fabric的版本采用1.3. VM1(192.168.1.101): orderer.example.com，ca.org1.example.com，peer0.org1.example.com，couchdb0，peer1.org1.example.com，couchdb1，mongo，landTransaction，loginapp VM2(192.168.1.102): ca.org1.example.com，peer0.org2.example.com，couchdb0，peer1.org2.example.com，couchdb1，mongo，landTransaction，loginapp
HyperLedger Fabric开发实战 – 部署单机多节点网络
01-08
第3章 部署单机多节点网络 在进行基础环境搭建和fabric环境部署完后，可以得到一个完全干净的空服务器状态。 3.1 生成证书文件 如果运行过e2e_cli案例，则执行如下命令即可做到环境清理(…/fabric/examples/e2e_cli/...
Fabric 1.0的多机部署
weixin_33835103的博客
07-26 217
Fabric1.0已经正式发布一段时间了，官方给出的单机部署的脚本也很完备，基本上傻瓜式的一键部署，直接运行官方的network_setup.sh up即可。但是在实际生产环境，我们不可能把所有的节点都放在一台机器中，所以必然会遇到多级部署的问题。下面我们就来讲讲怎么实现多机部署和测试官方的ChainCode。 1.环境准备 我们要部署的是4Peer+1Orderer的架构，也就是官方的e2c...
fabric 多机部署
qq_26563551的博客
11-17 2195
Fabric多机部署步骤 1 Fabric CA生成 1.1 环境准备和yaml文件编写 CA 镜像装载，版本根据需求而定，本次版本是1.4.4。 CA 的yaml文件编写。 需要⚠️yaml文件有标准格式 //版本 version: '2' //网络名称 networks: rootchain: //定义服务 services: //服务名称 lzsk.ca.chain.com: //容器名称 container_name: lzsk.ca.chai...
fabric多机部署（一点笔记）
Tree_sea的博客
03-27 2401
对文章（多机部署fabric） https://blog.csdn.net/bean_business/article/details/110100669 的步骤遇到问题记录一下
fabric手动多机部署
阿苏丶丶的博客
08-29 596
网络中有1个orderer节点，４个组织，每个组织各有１个节点。 名称 ｉｐ 节点Hostname Organization Server 1 10.11.6.118 orderer.example.com     ...
Fabric部署进阶篇 - 多机部署.docx
05-20
### Fabric部署进阶篇 - 多机部署 #### 一、基础环境 Hyperledger Fabric的多机部署相较于单机部署更为复杂但也更加贴近实际应用场景的需求。为了构建一个多机的Fabric网络，首先需要确保具备合适的基础环境。对于...
hyperledger fabric多机部署
09-22
多机部署是Fabric网络的重要组成部分，特别是在生产环境中，为了提高系统的容错性、性能和安全性，通常会在多个物理或虚拟节点上分散部署不同的组件。 在Hyperledger Fabric 1.4的多机部署中，主要涉及以下几个关键...
Fabric Docker：多机多节点部署生产网络
最新发布
06-25
docker-yaml peer-yaml bin config-yaml
Fabric Raft共识多机部署教程
01-20
Raft是Hyperledger Fabric 1.4.1中新增的排序服务模块，这个教程将介绍如何部署一个基于Raft排序服务的多机Fabric网络。 相关教程推荐： Hyperledger Fabric Java开发详解 Hyperledger Fabric Node.JS开发详解 1、用...
Fabric多机部署
12-05
自己亲身实践搭建环境的文档总结，根据文档步骤100%可以搭建自己的Fabric运行环境
Hyperledger fabric 多机部署
weixin_46698113的博客
04-26 1189
Hyperledger fabric多机部署
Hyperledger Fabric 2.2.1 多机部署教程
qq_62778805的博客
01-09 820
Fabric 多机部署教程
Fabric 2.3多机部署
TBBetter的博客
01-17 1万+
Fabric 2.3多机部署Fabric 2.3多机部署安装Go Fabric 2.3多机部署 你好！ 这是fabric 2.3.2多机（两台云服务器）部署教程 安装Go wget https://dl.google.com/go/go1.14.linux-amd64.tar.gz tar -zxvf go1.14.linux-amd64.tar.gz -C /usr/local/ vim .bashrc export GOROOT="/usr/local/go" export GOPATH="$HOME
fabric1.4.3多机多节点部署(二)
willzhengxian的博客
05-19 403
fabric1.4.3多机多节点部署： （一）项目环境 多机多节点指多台电脑上部署多个组织和节点，本案例部署一个排序（orderer）服务，两个组织（org1，org2）和四个节点（peer）,每个组织包括两个节点，需要三台服务器，规划如下： orderer.example.com 101.201.253.208 peer0.org1.example.com 123.56.48.16 peer1.org1.example.com 123.56.48.16 peer0.org2.example.com 39.
（Fabric 学习三）Fabric2.2 多机部署 使用fabcar链码
Wannabe_hacker的博客
03-28 9926
注：参考博客： Hyperledger Fabric多机及explorer搭建_routiao的博客-CSDN博客 一、准备条件 硬件环境：Ubuntu虚拟机两台，一共两台主机：主机1的IP：192.168.235.147；主机2的IP： 192.168.235.146 部署方案：1个orderer、2个组织、每个组织1个普通节点，通过静态IP的方式实现Hyperledger Fabric多机部署；orderer和org1放在192.168.235.147；org2放在192.168.235.146
Hyperledger Fabric 部署在多个主机上
热门推荐
风色幻想的博客
04-15 4万+
前言 在实验Hyperledger Fabric无排序组织以Raft协议启动多个Orderer服务、TLS组织运行维护Orderer服务中，我们已经完成了使用提供 TLS-CA 服务的 council 组织运行维护 Raft 协议的三个 orderer 节点。但目前我们都是在单个主机上启动 Fabric 网络，本文将尝试将 Hyperledger Fabric无排序组织以Raft协议启动多个Orderer服务、TLS组织运行维护Orderer服务 中的网络结构部署在多个主机上。 工作准备 本文工作 将 Hy
Fabric多机部署实战指南
本文档还将指导安装Go语言和Docker，这是Fabric部署的关键组件。" 在进行IBM Fabric的多机部署时，首要任务是确保硬件和软件环境的准备。在这个例子中，我们构建了一个包含4个组织（每个组织拥有一个Peer节点）和1...
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

sanqima

一键三连，多多益善

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值