fabric多节点网络环境搭建（v2.2）

最新推荐文章于 2023-09-02 18:20:50 发布
最新推荐文章于 2023-09-02 18:20:50 发布
阅读量3.2k 收藏 19
点赞数 4
分类专栏： 区块链 # fabric
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/ory001/article/details/108375760
版权

fabric多节点网络环境搭建（v2.2）

文章目录

一、机器准备与基础环境搭建

服务器orderer节点peer节点
chain4(192.168.1.223)orderer0.example1.compeer0.org1.example1.com
chain5(192.168.1.224)orderer1.example1.com
chain6(192.168.1.225)orderer2.example1.compeer0.org2.example1.com

docker环境搭建

fabric单机网络环境搭建

转载：
fabric常用命令

防火墙端口设置：

#查看防火墙所有开放端口：
firewall-cmd --zone=public --list-ports
#开放端口（7050 order节点端口7051-7053 peer节点端口 5984 CouchDB端口 8080 基于SDK网关应用管理平台）
firewall-cmd --zone=public --add-port=7050/tcp –permanent
firewall-cmd --zone=public --add-port=7051/tcp –permanent
firewall-cmd --zone=public --add-port=7052/tcp –permanent
firewall-cmd --zone=public --add-port=7053/tcp –permanent
firewall-cmd --zone=public --add-port=7054/tcp –permanent
firewall-cmd --zone=public --add-port=5984/tcp –permanent
firewall-cmd --zone=public --add-port=8080/tcp –permanent
firewall-cmd --reload

二、创建服务部署目录

创建服务部署目录(三台机器都需要此步操作)
# mkdir $FABRIC/multipeer/
将$FABRIC/scripts/fabric-samples/目录下的bin文件夹拷贝到$FABRIC/multipeer/
# cp $FABRIC/scripts/fabric-samples/bin/ $FABRIC/multipeer/

创建证书和通道文件在chain4机器上执行

三、准备证书文件

cd $FABRIC/multipeer/
vim crypto-config.yaml

OrdererOrgs:
  - Name: Orderer
    Domain: example1.com
    Specs:
      - Hostname: orderer0
      - Hostname: orderer1
      - Hostname: orderer2
PeerOrgs:
  - Name: Org1
    Domain: org1.example1.com
    EnableNodeOUs: true
    Template:
      Count: 2 #生成peer的数量
    Users:
      Count: 1 #生成用户个数
  - Name: Org2
    Domain: org2.example1.com
    EnableNodeOUs: true
    Template:
      Count: 2
    Users:
      Count: 1

执行命令生成证书文件

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

执行后在当前目录下生成crypto-config文件夹，如下：
image2

cryptogen 命令介绍：

​ -help #显示帮助信息

​ -generate #根据配置文件生成证书信息

​ -showtemplate #显示证书模板配置文件

​ -version #显示cryptogen 的版本号

四、通道配置文件

参照$FABRIC/scripts/fabric-samples/test-network/configtx下的configtx.yaml改写我们自己的通道配置文件。

vim configtx.yaml

---
Organizations:
  - &OrdererOrg
    Name: OrdererOrg
    ID: OrdererMSP
    MSPDir: crypto-config/ordererOrganizations/example1.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.example1.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')"
      Endorsement:
        Type: Signature
        Rule: "OR('Org1MSP.peer')"

    AnchorPeers:
      - Host: peer0.org1.example1.com
        Port: 7051

  - &Org2
    Name: Org2MSP
    ID: Org2MSP
    MSPDir: crypto-config/peerOrganizations/org2.example1.com/msp
    Policies:
      Readers:
        Type: Signature
        Rule: "OR('Org2MSP.admin', 'Org2MSP.peer', 'Org2MSP.client')"
      Writers:
        Type: Signature
        Rule: "OR('Org2MSP.admin', 'Org2MSP.client')"
      Admins:
        Type: Signature
        Rule: "OR('Org2MSP.admin')"
      Endorsement:
        Type: Signature
        Rule: "OR('Org2MSP.peer')"

    AnchorPeers:
      - Host: peer0.org2.example1.com
        Port: 7051

Capabilities:
  Channel: &ChannelCapabilities
    V2_0: true
  Orderer: &OrdererCapabilities
    V2_0: true
  Application: &ApplicationCapabilities
    V2_0: true

Application: &ApplicationDefaults

  Organizations:

  Policies:
    Readers:
      Type: ImplicitMeta
      Rule: "ANY Readers"
    Writers:
      Type: ImplicitMeta
      Rule: "ANY Writers"
    Admins:
      Type: ImplicitMeta
      Rule: "MAJORITY Admins"
    LifecycleEndorsement:
      Type: ImplicitMeta
      Rule: "MAJORITY Endorsement"
    Endorsement:
      Type: ImplicitMeta
      Rule: "MAJORITY Endorsement"

  Capabilities:
    <<: *ApplicationCapabilities

Orderer: &OrdererDefaults

  OrdererType: etcdraft

  Addresses: # orderer 集群节点
    - orderer0.example1.com:7050
    - orderer1.example1.com:7050
    - orderer2.example1.com:7050
  # Batch Timeout: The amount of time to wait before creating a batch
  BatchTimeout: 2s

  # Batch Size: Controls the number of messages batched into a block
  BatchSize:

    MaxMessageCount: 10

    AbsoluteMaxBytes: 99 MB

    PreferredMaxBytes: 512 KB

  Organizations:

  Policies:
    Readers:
      Type: ImplicitMeta
      Rule: "ANY Readers"
    Writers:
      Type: ImplicitMeta
      Rule: "ANY Writers"
    Admins:
      Type: ImplicitMeta
      Rule: "MAJORITY Admins"
    # BlockValidation specifies what signatures must be included in the block
    # from the orderer for the peer to validate it.
    BlockValidation:
      Type: ImplicitMeta
      Rule: "ANY Writers"

Channel: &ChannelDefaults

  Policies:
    # Who may invoke the 'Deliver' API
    Readers:
      Type: ImplicitMeta
      Rule: "ANY Readers"
    # Who may invoke the 'Broadcast' API
    Writers:
      Type: ImplicitMeta
      Rule: "ANY Writers"
    # By default, who may modify elements at this config level
    Admins:
      Type: ImplicitMeta
      Rule: "MAJORITY Admins"

  Capabilities:
    <<: *ChannelCapabilities

Profiles:

  TwoOrgsChannel:
    Consortium: SampleConsortium
    <<: *ChannelDefaults
    Application:
      <<: *ApplicationDefaults
      Organizations:
        - *Org1
        - *Org2
      Capabilities:
        <<: *ApplicationCapabilities

  SampleMultiNodeEtcdRaft:
    <<: *ChannelDefaults
    Capabilities:
      <<: *ChannelCapabilities
    Orderer:
      <<: *OrdererDefaults
      OrdererType: etcdraft
      EtcdRaft:
        Consenters:
          - Host: orderer0.example1.com
            Port: 7050
            ClientTLSCert: crypto-config/ordererOrganizations/example1.com/orderers/orderer0.example1.com/tls/server.crt
            ServerTLSCert: crypto-config/ordererOrganizations/example1.com/orderers/orderer0.example1.com/tls/server.crt
          - Host: orderer1.example1.com
            Port: 7050
            ClientTLSCert: crypto-config/ordererOrganizations/example1.com/orderers/orderer1.example1.com/tls/server.crt
            ServerTLSCert: crypto-config/ordererOrganizations/example1.com/orderers/orderer1.example1.com/tls/server.crt
          - Host: orderer2.example1.com
            Port: 7050
            ClientTLSCert: crypto-config/ordererOrganizations/example1.com/orderers/orderer2.example1.com/tls/server.crt
            ServerTLSCert: crypto-config/ordererOrganizations/example1.com/orderers/orderer2.example1.com/tls/server.crt
      Addresses:
        - orderer0.example1.com:7050
        - orderer1.example1.com:7050
        - orderer2.example1.com:7050
      Organizations:
        - *OrdererOrg
      Capabilities:
        <<: *OrdererCapabilities
    Application:
      <<: *ApplicationDefaults
      Organizations:
        - <<: *OrdererOrg
    Consortiums:
      SampleConsortium:
        Organizations:
          - *Org1
          - *Org2

根据 configtx.yaml 生成通道配置信息

#生成创世区块：
./bin/configtxgen -profile SampleMultiNodeEtcdRaft -channelID fabric-cluster-channel -outputBlock ./channel-artifacts/genesis.block
# 创建通道配置信息：
./bin/configtxgen -profile TwoOrgsChannel -outputCreateChannelTx ./channel-artifacts/channel.tx -channelID mychannel
#为 Org1 定义锚节点：
./bin/configtxgen -profile TwoOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org1MSPanchors.tx -channelID mychannel -asOrg Org1MSP
#为 Org2 定义锚节点：
./bin/configtxgen -profile TwoOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org2MSPanchors.tx -channelID mychannel -asOrg Org2MSP

执行完成后，生成/ channel-artifacts/目录，如下：
image3

将/channel-artifacts/和/crypto-config/拷贝到chain5，chain6的$FABRIC/multipeer/目录

# scp -r channel-artifacts/ root@chain5: $FABRIC/multipeer/
# scp -r channel-artifacts/ root@chain6: $FABRIC/multipeer/
# scp -r crypto-config/ root@chain5: $FABRIC/multipeer/
# scp -r crypto-config/ root@chain6: $FABRIC/multipeer/

五、配置docker-compose.yaml文件

chain4

version: '2'

services:
  couchdb0.org1.example1.com:
    container_name: couchdb0.org1.example1.com
    image: couchdb:3.1
    environment:
      - COUCHDB_USER=admin
      - COUCHDB_PASSWORD=adminpw
    ports:
      - 5984:5984
    volumes:
      - /home/hyperledger/couchdb:/opt/couchdb/data

  orderer0.example1.com:
    container_name: orderer0.example1.com
    image: hyperledger/fabric-orderer
    environment:
      - FABRIC_LOGGING_SPEC=DEBUG
      - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
      - ORDERER_GENERAL_BOOTSTRAPMETHOD=file
      - ORDERER_GENERAL_BOOTSTRAPFILE=/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_GENERAL_CLUSTER_CLIENTCERTIFICATE=/var/hyperledger/orderer/tls/server.crt
      - ORDERER_GENERAL_CLUSTER_CLIENTPRIVATEKEY=/var/hyperledger/orderer/tls/server.key
      - ORDERER_GENERAL_CLUSTER_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/example1.com/orderers/orderer0.example1.com/msp:/var/hyperledger/orderer/msp
      - ./crypto-config/ordererOrganizations/example1.com/orderers/orderer0.example1.com/tls/:/var/hyperledger/orderer/tls
      - /home/hyperledger/orderer:/var/hyperledger/production
    ports:
      - 7050:7050
    extra_hosts:
      - "orderer0.example1.com:192.168.1.223"
      - "orderer1.example1.com:192.168.1.224"
      - "orderer2.example1.com:192.168.1.225"
      - "peer0.org1.example1.com:192.168.1.223"
      - "peer0.org2.example1.com:192.168.1.225"

  peer0.org1.example1.com:
    container_name: peer0.org1.example1.com
    image: hyperledger/fabric-peer
    environment:
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      - CORE_PEER_ID=peer0.org1.example1.com
      - CORE_PEER_ADDRESS=peer0.org1.example1.com:7051
      - CORE_PEER_LISTENADDRESS=0.0.0.0:7051
      - CORE_PEER_CHAINCODEADDRESS=peer0.org1.example1.com:7052
      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052
      - CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org1.example1.com:7051
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.example1.com:7051
      - CORE_PEER_LOCALMSPID=Org1MSP
      - FABRIC_LOGGING_SPEC=INFO
      - 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
      # Allow more time for chaincode container to build on install.
      - CORE_CHAINCODE_EXECUTETIMEOUT=300s
      - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
      - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb0.org1.example1.com:5984
      - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=admin
      - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=adminpw
    depends_on:
      - couchdb0.org1.example1.com

    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: peer node start
    volumes:
      - /var/run/:/host/var/run/
      - ./crypto-config/peerOrganizations/org1.example1.com/peers/peer0.org1.example1.com/msp:/etc/hyperledger/fabric/msp
      - ./crypto-config/peerOrganizations/org1.example1.com/peers/peer0.org1.example1.com/tls:/etc/hyperledger/fabric/tls
      - /home/hyperledger/peer:/var/hyperledger/production
    ports:
      - 7051:7051
      - 7052:7052
      - 7053:7053
    extra_hosts:
      - "orderer0.example1.com:192.168.1.223"
      - "orderer1.example1.com:192.168.1.224"
      - "orderer2.example1.com:192.168.1.225"
      - "peer0.org1.example1.com:192.168.1.223"
      - "peer0.org2.example1.com:192.168.1.225"

  cli:
    container_name: cli
    image: hyperledger/fabric-tools
    tty: true
    stdin_open: true
    environment:
      - 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.example1.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.example1.com/peers/peer0.org1.example1.com/tls/server.crt
      - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example1.com/peers/peer0.org1.example1.com/tls/server.key
      - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example1.com/peers/peer0.org1.example1.com/tls/ca.crt
      - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example1.com/users/Admin@org1.example1.com/msp
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: /bin/bash
    volumes:
      - /var/run/:/host/var/run/
      - ./chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric-cluster/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
    extra_hosts:
      - "orderer0.example1.com:192.168.1.223"
      - "orderer1.example1.com:192.168.1.224"
      - "orderer2.example1.com:192.168.1.225"
      - "peer0.org1.example1.com:192.168.1.223"
      - "peer0.org2.example1.com:192.168.1.225"

chain5

version: '2'

services:
  orderer1.example1.com:
    container_name: orderer1.example1.com
    image: hyperledger/fabric-orderer
    environment:
      - FABRIC_LOGGING_SPEC=INFO
      - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
      - ORDERER_GENERAL_BOOTSTRAPMETHOD=file
      - ORDERER_GENERAL_BOOTSTRAPFILE=/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_GENERAL_CLUSTER_CLIENTCERTIFICATE=/var/hyperledger/orderer/tls/server.crt
      - ORDERER_GENERAL_CLUSTER_CLIENTPRIVATEKEY=/var/hyperledger/orderer/tls/server.key
      - ORDERER_GENERAL_CLUSTER_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/example1.com/orderers/orderer1.example1.com/msp:/var/hyperledger/orderer/msp
      - ./crypto-config/ordererOrganizations/example1.com/orderers/orderer1.example1.com/tls/:/var/hyperledger/orderer/tls
      - /home/hyperledger/orderer:/var/hyperledger/production
    ports:
      - 7050:7050
    extra_hosts:
      - "orderer0.example1.com:192.168.1.223"
      - "orderer1.example1.com:192.168.1.224"
      - "orderer2.example1.com:192.168.1.225"
      - "peer0.org1.example1.com:192.168.1.223"
      - "peer0.org2.example1.com:192.168.1.225"

chain6

version: '2'

services:
  couchdb0.org2.example1.com:
    container_name: couchdb0.org2.example1.com
    image: couchdb:3.1
    environment:
      - COUCHDB_USER=admin
      - COUCHDB_PASSWORD=adminpw
    ports:
      - 5984:5984
    volumes:
      - /home/hyperledger/couchdb:/opt/couchdb/data

  orderer2.example1.com:
    container_name: orderer2.example1.com
    image: hyperledger/fabric-orderer
    environment:
      - FABRIC_LOGGING_SPEC=INFO
      - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
      - ORDERER_GENERAL_BOOTSTRAPMETHOD=file
      - ORDERER_GENERAL_BOOTSTRAPFILE=/var/hyperledger/orderer/orderer.genesis.block
      - ORDERER_GENERAL_LOCALMSPID=OrdererMSP
      - ORDERER_GENERAL_LOCALMSPDIR=/var/hyperledger/orderer/msp
      - 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_GENERAL_CLUSTER_CLIENTCERTIFICATE=/var/hyperledger/orderer/tls/server.crt
      - ORDERER_GENERAL_CLUSTER_CLIENTPRIVATEKEY=/var/hyperledger/orderer/tls/server.key
      - ORDERER_GENERAL_CLUSTER_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/example1.com/orderers/orderer2.example1.com/msp:/var/hyperledger/orderer/msp
      - ./crypto-config/ordererOrganizations/example1.com/orderers/orderer2.example1.com/tls/:/var/hyperledger/orderer/tls
      - /home/hyperledger/orderer:/var/hyperledger/production
    ports:
      - 7050:7050
    extra_hosts:
      - "orderer0.example1.com:192.168.1.223"
      - "orderer1.example1.com:192.168.1.224"
      - "orderer2.example1.com:192.168.1.225"
      - "peer0.org1.example1.com:192.168.1.223"
      - "peer0.org2.example1.com:192.168.1.225"

  peer0.org2.example1.com:
    container_name: peer0.org2.example1.com
    image: hyperledger/fabric-peer
    environment:
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      - CORE_PEER_ID=peer0.org2.example1.com
      - CORE_PEER_ADDRESS=peer0.org2.example1.com:7051
      - CORE_PEER_LISTENADDRESS=0.0.0.0:7051
      - CORE_PEER_CHAINCODEADDRESS=peer0.org2.example1.com:7052
      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org2.example1.com:7051
      - CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org2.example1.com:7051
      - CORE_PEER_LOCALMSPID=Org2MSP
      - FABRIC_LOGGING_SPEC=INFO
      - 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
      - CORE_CHAINCODE_EXECUTETIMEOUT=300s
      - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
      - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb0.org2.example1.com:5984
      - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=admin
      - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=adminpw
    depends_on:
      - couchdb0.org2.example1.com

    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: peer node start
    volumes:
      - /var/run/:/host/var/run/
      - ./crypto-config/peerOrganizations/org2.example1.com/peers/peer0.org2.example1.com/msp:/etc/hyperledger/fabric/msp
      - ./crypto-config/peerOrganizations/org2.example1.com/peers/peer0.org2.example1.com/tls:/etc/hyperledger/fabric/tls
      - /home/hyperledger/peer0:/var/hyperledger/production
    ports:
      - 7051:7051
      - 7052:7052
      - 7053:7053
    extra_hosts:
      - "orderer0.example1.com:192.168.1.223"
      - "orderer1.example1.com:192.168.1.224"
      - "orderer2.example1.com:192.168.1.225"
      - "peer0.org1.example1.com:192.168.1.223"
      - "peer0.org2.example1.com:192.168.1.225"
  cli:
    container_name: cli
    image: hyperledger/fabric-tools
    tty: true
    stdin_open: true
    environment:
      - GOPATH=/opt/gopath
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      - FABRIC_LOGGING_SPEC=INFO
      - CORE_PEER_ID=cli
      - CORE_PEER_ADDRESS=peer0.org2.example1.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.example1.com/peers/peer0.org2.example1.com/tls/server.crt
      - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example1.com/peers/peer0.org2.example1.com/tls/server.key
      - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example1.com/peers/peer0.org2.example1.com/tls/ca.crt
      - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example1.com/users/Admin@org2.example1.com/msp
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: /bin/bash
    volumes:
      - /var/run/:/host/var/run/
      - ./chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric-cluster/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
    extra_hosts:
      - "orderer0.example1.com:192.168.1.223"
      - "orderer1.example1.com:192.168.1.224"
      - "orderer2.example1.com:192.168.1.225"
      - "peer0.org1.example1.com:192.168.1.223"
      - "peer0.org2.example1.com:192.168.1.225"

创建好docker-compose-up.yaml文件后，在home目录下创建hyperledger/peer/、hyperledger/couchdb/和hyperledger/orderer/文件夹

mkdir -r /home/hyperledger/peer/
mkdir -r /home/hyperledger/orderer/
mkdir -r /home/hyperledger/couchdb/

六、启动服务peer节点加入通道

使用docker-compose启动服务(三台机器均需要)

docker-compose -f docker-compose-up.yaml up
docker ps -a

image4

在chain4节点上操作

#进入 cli 容器：
docker exec -it cli bash
#在容器中，创建通道：
peer channel create -o orderer0.example1.com:7050 -c mychannel -f ./channel-artifacts/channel.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example1.com/orderers/orderer0.example1.com/msp/tlscacerts/tlsca.example1.com-cert.pem
#加入通道：
peer channel join -b mychannel.block
#更新锚节点：
peer channel update -o orderer0.example1.com:7050 -c mychannel -f ./channel-artifacts/Org1MSPanchors.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example1.com/orderers/orderer0.example1.com/msp/tlscacerts/tlsca.example1.com-cert.pem
将通道文件 mychannel.block 拷贝到宿主机，然后拷贝到其他服务器上用于其他节点加入通道：
docker cp cli:/opt/gopath/src/github.com/hyperledger/fabric/peer/mychannel.block ./
scp mychannel.block root@chain6:$FABRIC/multipeer/

在chain6节点上操作

#将通道文件拷贝到容器中：
docker cp mychannel.block cli:/opt/gopath/src/github.com/hyperledger/fabric/peer/
#进入 cli 容器：
docker exec -it cli bash
#加入通道：
peer channel join -b mychannel.block
#更新 ORG2 锚节点：
peer channel update -o orderer0.example1.com:7050 -c mychannel -f ./channel-artifacts/Org2MSPanchors.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example1.com/orderers/orderer0.example1.com/msp/tlscacerts/tlsca.example1.com-cert.pem

七、智能合约（以Java为例）

1.链码打包

在chain4机器上执行以下操作

cd $FABRIC/multipeer/chaincode
#将开发工具idea打包好的文件，整个install文件夹上传到上面目录

#进入cli容器
docker exec -it cli bash
# 打包链码
peer lifecycle chaincode package myassetcontract.tar.gz --path /opt/gopath/src/github.com/hyperledger/fabric-cluster/chaincode/go --lang java --label myassetcontract_1

#退出容器，将打包的链码 mycc.tar.gz 拷贝到宿主机，然后拷贝到其他服务器
docker cp cli:/opt/gopath/src/github.com/hyperledger/fabric-cluster/chaincode/go/myassetcontract.tar.gz ./ 
scp myassetcontract.tar.gz root@chain6:/opt/gopath/src/github.com/hyperledger/fabric/multipeer
2.安装链码

每个peer节点（chain4、chain6）执行以下操作

#进入cli容器
docker cp myassetcontract.tar.gz cli:/opt/gopath/src/github.com/hyperledger/fabric/peer
docker exec -it cli bash
#安装链码
peer lifecycle chaincode install myassetcontract.tar.gz
#查询链码
peer lifecycle chaincode queryinstalled

界面输出：myassetcontract_1:b1b8dc4cb15719ef451947e67fed27823fcae3a1680f656d15ae691d0dbbc2fb

查询链码

3.批准链码

每个peer节点（chain4、chain6）执行以下操作

#批准同意链码在org1和org2上都执行一遍
peer lifecycle chaincode approveformyorg --channelID mychannel --name myassetcontract --version 1.0 --init-required --package-id myassetcontract_1:b1b8dc4cb15719ef451947e67fed27823fcae3a1680f656d15ae691d0dbbc2fb --sequence 1 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

#查看链码的状态是否就绪
peer lifecycle chaincode checkcommitreadiness --channelID mychannel --name myassetcontract --version 1.0 --init-required --sequence 1 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem --output json

就绪状态

4.提交链码
#提交链码定义，在 org1 或者 org2 上均可
peer lifecycle chaincode commit -o orderer0.example.com:7050 --channelID mychannel --name myassetcontract --version 1.0 --sequence 1 --init-required --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem --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

提交链码

5.链码初始化与调用
#链码初始化
peer chaincode invoke -o orderer0.example.com:7050 --isInit --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C mychannel -n myassetcontract    --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 '{"function":"initLedger","Args":[]}' --waitForEvent 

#查询数据
peer chaincode invoke -o orderer0.example.com:7050 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C mychannel -n myassetcontract    --peerAddresses peer1.org1.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer1.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 '{"function":"readMyAsset","Args":["ASSET1"]}' --waitForEvent 

#新增数据
peer chaincode invoke -o orderer0.example.com:7050 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer0.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C mychannel -n myassetcontract    --peerAddresses peer1.org1.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer1.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 '{"function":"createMyAsset","Args":["ASSET3","3"]}' --waitForEvent 
#查询数据
peer chaincode query -C mychannel -n myassetcontract -c '{"Args":["readMyAsset","ASSET1"]}' 
peer chaincode query -C mychannel -n myassetcontract -c '{"Args":["createMyAsset","ASSET3","3"]}'

问题汇总:
1.不同组织通信异常
通过在docker-compose.yml文件中增加host映射解决,此方法不易拓展，可使用自建DNS解决。
参照：
自建DNS

 extra_hosts:
      - "orderer0.example1.com:192.168.1.223"
      - "orderer1.example1.com:192.168.1.224"
      - "orderer2.example1.com:192.168.1.225"
      - "peer0.org1.example1.com:192.168.1.223"
      - "peer0.org2.example1.com:192.168.1.225"

2.执行docker-compose down命令，区块数据丢失
通过在docker-compose.yml文件中增加volumes映射解决。

18.1. Fabric2.2 区块链农产品溯源系统 - 多Peer部署（扩展）
菜鸟的博客
08-12 1548
> 这是一篇后补文章，看时间大家能够看出来，通过前面的学习，大家知道如何增加组织、如何部署多Orderer，本节介绍如何在一个组织内部署多个Peer节点，本节是基于上一节操作的继续，脚本也是基于上节进行修改的。...
3. 部署Fabric2.2 集群（使用官方Demo）
菜鸟的博客
02-22 3559
上节作者新购买阿里云，与大家一起操作，不遗漏每个操作步骤，保证大家都可以成功部署区块链集群。环境准备完毕，本节下载Fabric官方demo，并部署区块链集群。 1）安装git命令 yum install -y git 2）下载Fabric 2.2.1 版本代码 有点慢 或者出现中断情况，请反复操作，这是github网址 国内的支持不是很好。 git clone -b v2.2.1 https://github.com/hyperledger/fabric.git 3）下载依赖二进制、镜像 这个步骤也.
HyperLedger Fabric开发实战 – 部署单机多节点网络
01-08
第3章 部署单机多节点网络 在进行基础环境搭建和fabric环境部署完后，可以得到一个完全干净的空服务器状态。 3.1 生成证书文件 如果运行过e2e_cli案例，则执行如下命令即可做到环境清理(…/fabric/examples/e2e_cli/)： ./network_setup.sh down 在Fabric源码目录下创建一个名为 aberic 的目录，该目录为当前即将运行的单机多节点项目目录。 cd /home/zyp/development/go/src/github.com/hyperledger/fabric/ mkdir aberic 将第2章中提到的 bin/目录下的文件
fabric2.0多机多节点部署
u011271250的博客
01-05 2624
服务介绍 服务器ip orderer节点 组织 组织地址 peer节点 192.168.1.101 orderer1.test.com Org1 org1.test.com peer0.org1.test.com 192.168.1.102 orderer2.test.com Org2 org2.test.com peer0.org2.test.com 192.168.1.103 orderer3.test.com
Hyperledger Fabric 2.x 单机部署多节点网络
qq_45469783的博客
08-03 6438
本博客主要记录搭建一个3个排序节点、4个组织的每个组织各2个节点的fabric区块链网络 单机部署多节点网络1、相关环境的安装与配置2、生成相关的证书文件3、生成相关的通道配置文件4、生成docker-compose.yaml的启动文件 1、相关环境的安装与配置 go、docker、docker-compose，fabric的相关docker镜像、官方的fabric-samples文件、相关fabric二进制文件，具体配置之后补充 2、生成相关的证书文件 1）将下面的内容写入到crypto-config.y
（Fabric 学习三）Fabric2.2 多机部署 使用fabcar链码
Wannabe_hacker的博客
03-28 1万+
注：参考博客： Hyperledger Fabric多机及explorer搭建_routiao的博客-优快云博客 一、准备条件 硬件环境：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
Fabric 1.4 实战 — 2.2 单机多节点网络部署
weixin_43468183的博客
10-12 1606
文章目录一、准备工作二、生成组织结构身份证书1、crypto-config.yaml2、生成指定拓扑结构的组织关系和身份证书三、生成创世区块及应用通道1、configtx.yaml2、创建创世区块3、创建应用通道交易配置文件4、生成通道上的组织锚节点更新配置文件5、完成四、部署节点1、docker-compose-cli.yaml2、base/peer-base.yaml五、运行网络1、启动网络2、关闭网络 一、准备工作 1、创建项目目录 artec ，并在目录下创建 fabric 网络目录 networ
纪录一下Ubuntu部署Fabric2.2.0网络环境具体流程步骤
qq_42482245的博客
11-19 1875
一.环境准备 系统:Ubuntu18.04.1 1.git,curl,docker,docker-compose - 设置软件更新源为阿里云(软件和更新) - sudo apt-get update - sudo apt-git install git - sudo apt-git install vim - sudo apt-get install curl - 安装docker curl -fsSL https://get.docker.com | bash -s docker -
hyperledger fabric 2.0（一）环境搭建以及测试网络部署
热门推荐
tianshuhao521的博客
03-08 1万+
一、基础环境整理（可参照：https://blog.csdn.net/tianshuhao521/article/details/83892178 https://blog.csdn.net/tianshuhao521/article/details/83894142） 1、安装curl： # yum install curl 安装成功后查看版本： # curl --version ...
Hyperledger Fabric文档v2.2(四)
最新发布
笔记|思路|总结
09-02 347
在类中定位issue方法。JavaScriptJavaJava 标注用于标记该方法为交易定义；TypeScript 中也有等价的标注。无论何时调用此合约来发行商业票据，都会调用该方法。我们已经更改了编程样式的变量名称，但是看看这些属性几乎直接映射到issue方法变量。只要应用程序请求发行商业票据，合约就会自动调用issue方法。交易属性值通过相应的变量提供给方法。使用示例应用程序，了解应用程序如何使用应用主题中的 Hyperledger Fabric SDK 提交一笔交易。您可能已经注意到。
学习Fabric(二)：fabric部署生产网络
theonepiece的博客
06-12 5543
fabric部署生产网络
fabric2.2 多机器多节点 安装
AI炼丹师的专栏
11-16 411
fabric多节点集群部署（4+1）详解_卧船听雨眠的博客-优快云博客
【Hyperledger Fabric 2.2】在已有组织中添加peer节点
qq_39736373的博客
12-09 599
hyperledger fabric 2.2 添加节点
HyperLedger Fabric - 超级账本（2.2）启动网络 - 手动
象牙塔下的渣渣
06-20 1908
启动网络手动实现 实现步骤 生成组织关系和身份证书 确定是在 fabric-samples/first-network 路径下 $ cd hyfa/fabric-samples/first-network/ 为fabric网络生成指定拓扑结构的组织关系和身份证书 $ sudo ../bin/cryptogen generate --config=./crypto-c...
FabricV2.2测试网络搭建以及开发环境部署
Blockchain210的博客
04-16 9000
部署测试网络 Prerequisites: 安装docker、docker-compose git、cURL 要求docker版本 下载Fabric源码,Binaries和Docker Images ### 下载boostrap.sh脚本文件.并执行文件(下载Fabric和Fabric-CA的二进制文件、拉镜像) curl -sSL https://raw.githubusercontent.com/hyperledger/fabric/release-2.2/scripts/bootstrap.
022. Fabric动态添加组织流程
boss2967的博客
04-29 935
022 Fabric动态添加组织流程 主要流程 为Channel动态新增Org的流程如下： 为新的组织生成证书 为新的组织生成配置文件 生成和提交组织的配置 3.1 peer channel fetch config 获取当前通道信息,生成增量包 3.2 peer channel signconfigtx 为配置交易签名,需要网络中MAJORITY的组织都签名 3.3 peer cha...
4. Fabric2.2 创建通道与加入通道（使用官方Demo）
菜鸟的博客
02-22 3756
通过Fabric官方demo创建通道、加入通道、设置锚定节点，为安装、部署合约做准备。
Fabric单机多节点网络的搭建
weixin_44182276的博客
02-10 1750
在跑通fabric给出的e2e实例后尝试搭建了fabric的单机多节点网络，本次实验环境为Ubuntu。 1.基本文件的准备 在/home/docker/github.com/hyperledger/fabric文件夹下创建此次的实验环境文件aberic以方便以后的项目管理。 需要将Fabric1.0版本平台特定的二进制文件（bin）上传至本文件夹。bin文件夹的位置和内容如下图所示，只需要复制到...
fabric单机网络环境搭建（v2.2）
搬山境KL攻城狮的修炼手册
09-03 1103
fabric单机网络环境搭建（v2.2） 文章目录fabric单机网络环境搭建（v2.2）一、介绍二、系统环境要求三、基础环境搭建1.docker环境搭建2.其它工具安装(git、golang)四、拉取代码五、fabric单机网络环境搭建1、下载测试源码fabric-samples2、下载二进制文件3、 拉取镜像六、单机网络测试 一、介绍 This project is an Active Hyperledger project. For more information on the history of
评论 13
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

打赏作者

搬山境KL攻城狮

你的鼓励将是我创作的最大动力

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

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

打赏作者

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

抵扣说明：

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

余额充值