基于Kafka共识的Fabric分布式环境搭建

最新推荐文章于 2024-04-08 08:02:39 发布
最新推荐文章于 2024-04-08 08:02:39 发布
阅读量1.1k 收藏 2
点赞数 1
分类专栏： 区块链 Hyperledger Fabric 文章标签： Fabric 超级账本 Hyperledger 区块链 Kafka
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/wen942467928/article/details/84874971
版权

测试环境服务器安排：

名称

IP

Hostname

组织

备注

zookeeper1

10.16.3.97

zookeeper1

公共

 

zookeeper2

10.16.3.98

zookeeper2

公共

 

zookeeper3

10.16.3.99

zookeeper3

公共

 

kafka1

10.16.3.92

kafka1

公共

 

kafka2

10.16.3.93

kafka2

公共

 

kafka3

10.16.3.94

kafka3

公共

 

kafka4

10.16.3.95

kafka4

公共

 

orderer0

10.16.8.91

orderer0.example.com

org1

 

orderer1

10.16.8.92

orderer1.example.com

org2

 

orderer2

10.16.8.93

orderer2.example.com

org3

 

peer0org1

10.16.8.97peer0.org1.example.comorg1 

ca

10.16.8.97

peer0.org1.example.com

org1

 

 

安装步骤：

在所有机器上新建文件夹，mkdir /apps/fabric_kafka

 

在zookeeper1:/apps/fabric_kafka上新建docker-zookeeper1.yaml，内容

version: '2'
services:
 zookeeper1:
 container_name: zookeeper1
    hostname: zookeeper1
    image: hyperledger/fabric-zookeeper
    restart: always
    environment:
 - ZOO_MY_ID=1
      - ZOO_SERVERS=server.1=zookeeper1:2888:3888 server.2=zookeeper2:2888:3888 server.3=zookeeper3:2888:3888
    ports:
 - "2181:2181"
 - "2888:2888"
 - "3888:3888"
 extra_hosts:
 - "zookeeper1:10.16.3.97"
 - "zookeeper2:10.16.3.98"
 - "zookeeper3:10.16.3.99"
 - "kafka1:10.16.3.92"
 - "kafka2:10.16.3.93"
 - "kafka3:10.16.3.94"
 - "kafka4:10.16.3.95"

在zookeeper2:/apps/fabric_kafka上新建docker-zookeeper2.yaml，内容

version: '2'
services:
 zookeeper2:
 container_name: zookeeper2
    hostname: zookeeper2
    image: hyperledger/fabric-zookeeper
    restart: always
    environment:
 - ZOO_MY_ID=2
      - ZOO_SERVERS=server.1=zookeeper1:2888:3888 server.2=zookeeper2:2888:3888 server.3=zookeeper3:2888:3888
    ports:
 - "2181:2181"
 - "2888:2888"
 - "3888:3888"
 extra_hosts:
 - "zookeeper1:10.16.3.97"
 - "zookeeper2:10.16.3.98"
 - "zookeeper3:10.16.3.99"
 - "kafka1:10.16.3.92"
 - "kafka2:10.16.3.93"
 - "kafka3:10.16.3.94"
 - "kafka4:10.16.3.95"

在zookeeper3:/apps/fabric_kafka上新建docker-zookeeper3.yaml，内容

version: '2'
services:
 zookeeper3:
 container_name: zookeeper3
    hostname: zookeeper3
    image: hyperledger/fabric-zookeeper
    restart: always
    environment:
 - ZOO_MY_ID=3
      - ZOO_SERVERS=server.1=zookeeper1:2888:3888 server.2=zookeeper2:2888:3888 server.3=zookeeper3:2888:3888
    ports:
 - "2181:2181"
 - "2888:2888"
 - "3888:3888"
 extra_hosts:
 - "zookeeper1:10.16.3.97"
 - "zookeeper2:10.16.3.98"
 - "zookeeper3:10.16.3.99"
 - "kafka1:10.16.3.92"
 - "kafka2:10.16.3.93"
 - "kafka3:10.16.3.94"
 - "kafka4:10.16.3.95"

在各zk机器上启动

docker-compose -f docker-zookeeper1.yaml up -d
docker-compose -f docker-zookeeper2.yaml up -d
docker-compose -f docker-zookeeper3.yaml up -d

在kafka1:/apps/fabric_kafka上新建docker-kafka1.yaml，内容

version: '2'
services:
 kafka1:
 container_name: kafka1
    hostname: kafka1
    image: hyperledger/fabric-kafka
    restart: always
    environment:
 - KAFKA_BROKER_ID=1
      - KAFKA_MIN_INSYNC_REPLICAS=2
      - KAFKA_DEFAULT_REPLICATION_FACTOR=3
      - KAFKA_ZOOKEEPER_CONNECT=zookeeper1:2181,zookeeper2:2181,zookeeper3:2181
      - KAFKA_MESSAGE_MAX_BYTES=103809024
      - KAFKA_REPLICA_FETCH_MAX_BYTES=103809024
      - KAFKA_UNCLEAN_LEADER_ELECTION_ENABLE=false
      - KAFKA_LOG_RETENTION_MS=-1
      - KAFKA_HEAP_OPTS=-Xmx256M -Xms128M
    ports:
 - "9092:9092"
 extra_hosts:
 - "zookeeper1:10.16.3.97"
 - "zookeeper2:10.16.3.98"
 - "zookeeper3:10.16.3.99"
 - "kafka1:10.16.3.92"
 - "kafka2:10.16.3.93"
 - "kafka3:10.16.3.94"
 - "kafka4:10.16.3.95"

在kafka2:/apps/fabric_kafka上新建docker-kafka2.yaml，内容

version: '2'
services:
 kafka2:
 container_name: kafka2
    hostname: kafka2
    image: hyperledger/fabric-kafka
    restart: always
    environment:
 - KAFKA_BROKER_ID=2
      - KAFKA_MIN_INSYNC_REPLICAS=2
      - KAFKA_DEFAULT_REPLICATION_FACTOR=3
      - KAFKA_ZOOKEEPER_CONNECT=zookeeper1:2181,zookeeper2:2181,zookeeper3:2181
      - KAFKA_MESSAGE_MAX_BYTES=103809024
      - KAFKA_REPLICA_FETCH_MAX_BYTES=103809024
      - KAFKA_UNCLEAN_LEADER_ELECTION_ENABLE=false
      - KAFKA_LOG_RETENTION_MS=-1
      - KAFKA_HEAP_OPTS=-Xmx256M -Xms128M
    ports:
 - "9092:9092"
 extra_hosts:
 - "zookeeper1:10.16.3.97"
 - "zookeeper2:10.16.3.98"
 - "zookeeper3:10.16.3.99"
 - "kafka1:10.16.3.92"
 - "kafka2:10.16.3.93"
 - "kafka3:10.16.3.94"
 - "kafka4:10.16.3.95"

在kafka3:/apps/fabric_kafka上新建docker-kafka3.yaml，内容

version: '2'
services:
 kafka3:
 container_name: kafka3
    hostname: kafka3
    image: hyperledger/fabric-kafka
    restart: always
    environment:
 - KAFKA_BROKER_ID=3
      - KAFKA_MIN_INSYNC_REPLICAS=2
      - KAFKA_DEFAULT_REPLICATION_FACTOR=3
      - KAFKA_ZOOKEEPER_CONNECT=zookeeper1:2181,zookeeper2:2181,zookeeper3:2181
      - KAFKA_MESSAGE_MAX_BYTES=103809024
      - KAFKA_REPLICA_FETCH_MAX_BYTES=103809024
      - KAFKA_UNCLEAN_LEADER_ELECTION_ENABLE=false
      - KAFKA_LOG_RETENTION_MS=-1
      - KAFKA_HEAP_OPTS=-Xmx256M -Xms128M
    ports:
 - "9092:9092"
 extra_hosts:
 - "zookeeper1:10.16.3.97"
 - "zookeeper2:10.16.3.98"
 - "zookeeper3:10.16.3.99"
 - "kafka1:10.16.3.92"
 - "kafka2:10.16.3.93"
 - "kafka3:10.16.3.94"
 - "kafka4:10.16.3.95"

在kafka4:/apps/fabric_kafka上新建docker-kafka4.yaml，内容

version: '2'
services:
 kafka4:
 container_name: kafka4
    hostname: kafka4
    image: hyperledger/fabric-kafka
    restart: always
    environment:
 - KAFKA_BROKER_ID=4
      - KAFKA_MIN_INSYNC_REPLICAS=2
      - KAFKA_DEFAULT_REPLICATION_FACTOR=3
      - KAFKA_ZOOKEEPER_CONNECT=zookeeper1:2181,zookeeper2:2181,zookeeper3:2181
      - KAFKA_MESSAGE_MAX_BYTES=103809024
      - KAFKA_REPLICA_FETCH_MAX_BYTES=103809024
      - KAFKA_UNCLEAN_LEADER_ELECTION_ENABLE=false
      - KAFKA_LOG_RETENTION_MS=-1
      - KAFKA_HEAP_OPTS=-Xmx256M -Xms128M
    ports:
 - "9092:9092"
 extra_hosts:
 - "zookeeper1:10.16.3.97"
 - "zookeeper2:10.16.3.98"
 - "zookeeper3:10.16.3.99"
 - "kafka1:10.16.3.92"
 - "kafka2:10.16.3.93"
 - "kafka3:10.16.3.94"
 - "kafka4:10.16.3.95"

在各kafka机器上启动

docker-compose -f docker-kafka1.yaml up -d
docker-compose -f docker-kafka2.yaml up -d
docker-compose -f docker-kafka3.yaml up -d
docker-compose -f docker-kafka4.yaml up -d

在peer0org1:/apps/fabric_kafka上新建configtx.yaml，内容

Organizations:
 - &OrdererOrg
        Name: OrdererMSP
        ID: OrdererMSP
        MSPDir: crypto-config/ordererOrganizations/example.com/msp
    - &Org1
        Name: Org1MSP
        ID: Org1MSP
        MSPDir: crypto-config/peerOrganizations/org1.example.com/msp
        AnchorPeers:
 - Host: peer0.org1.example.com
              Port: 7051
    - &Org2
        Name: Org2MSP
        ID: Org2MSP
        MSPDir: crypto-config/peerOrganizations/org2.example.com/msp
        AnchorPeers:
 - Host: peer0.org2.example.com
              Port: 7051
Orderer: &OrdererDefaults
    OrdererType: kafka
    Addresses:
 - orderer0.example.com:7050
        - orderer1.example.com:7050
        - orderer2.example.com:7050
    BatchTimeout: 2s

    BatchSize:
 MaxMessageCount: 10
        AbsoluteMaxBytes: 98 MB
        PreferredMaxBytes: 512 KB
    Kafka:
 Brokers:
 - 10.16.3.92:9092
            - 10.16.3.93:9092
            - 10.16.3.94:9092
            - 10.16.3.95:9092
    Organizations:
Application: &ApplicationDefaults
    Organizations:
Capabilities:
 Global: &ChannelCapabilities
        V1_1: true
    Orderer: &OrdererCapabilities
        V1_1: true
    Application: &ApplicationCapabilities
        V1_1: true

Profiles:
 TwoOrgsOrdererGenesis:
 Orderer:
 <<: *OrdererDefaults
            Organizations:
 - *OrdererOrg
        Consortiums:
 SampleConsortium:
 Organizations:
 - *Org1
                    - *Org2
    TwoOrgsChannel:
 Consortium: SampleConsortium
        Application:
 <<: *ApplicationDefaults
            Organizations:
 - *Org1
                - *Org2

在peer0org1:/apps/fabric_kafka上新建crypto-config.yaml，内容

OrdererOrgs:
 - Name: Orderer
    Domain: example.com
    Specs:
 - Hostname: orderer0
      - Hostname: orderer1
      - Hostname: orderer2
PeerOrgs:
 - Name: Org1
    Domain: org1.example.com
    Template:
 Count: 2
    Users:
 Count: 1
  - Name: Org2
    Domain: org2.example.com
    Template:
 Count: 2
    Users:
 Count: 1

在peer0org1:/apps/fabric_kafka上执行

mkdir channel-artifacts

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

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

mkdir chaincode/go/chaincode_example02/go

讲fabric-example里面的chaincode_example02.go放置chaincode/go/chaincode_example02/go目录中

scp -r crypto-config channel-artifacts 10.16.8.91:/apps/fabric-kafka

scp -r crypto-config channel-artifacts 10.16.8.92:/apps/fabric-kafka

scp -r crypto-config channel-artifacts 10.16.8.93:/apps/fabric-kafka

在orderer0:/apps/fabric_kafka上新建docker-orderer0.yaml，内容

version: '2'
services:
 orderer0.example.com:
 container_name: orderer0.example.com
    image: hyperledger/fabric-orderer
    environment:
 - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=fabric_kafka_default
      - ORDERER_GENERAL_LOGLEVEL=debug
      - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
      - ORDERER_GENERAL_LISTENPORT=7050
      - 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_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]
      - ORDERER_KAFKA_RETRY_LONGINTERVAL=10s
      - ORDERER_KAFKA_RETRY_LONGTOTAL=100s
      - ORDERER_KAFKA_RETRY_SHORTINTERVAL=1s
      - ORDERER_KAFKA_RETRY_SHORTTOTAL=30s
      - ORDERER_KAFKA_VERBOSE=true
      - ORDERER_KAFKA_BROKERS=[10.16.3.92:9092,10.16.3.93:9092,10.16.3.94:9092,10.16.3.95:9092]
    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/orderer0.example.com/msp:/var/hyperledger/orderer/msp
    - ./crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/tls/:/var/hyperledger/orderer/tls
    networks:
 default:
 aliases:
 - fabric_kafka
    ports:
 - 7050:7050
    extra_hosts:
 - "kafka1:10.16.3.92"
 - "kafka2:10.16.3.93"
 - "kafka3:10.16.3.94"
 - "kafka4:10.16.3.95"

在orderer1:/apps/fabric_kafka上新建docker-orderer1.yaml，内容

version: '2'
services:
 orderer1.example.com:
 container_name: orderer1.example.com
    image: hyperledger/fabric-orderer
    environment:
 - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=fabric_kafka_default
      - ORDERER_GENERAL_LOGLEVEL=debug
      - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
      - ORDERER_GENERAL_LISTENPORT=7050
      - 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_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]
      - ORDERER_KAFKA_RETRY_LONGINTERVAL=10s
      - ORDERER_KAFKA_RETRY_LONGTOTAL=100s
      - ORDERER_KAFKA_RETRY_SHORTINTERVAL=1s
      - ORDERER_KAFKA_RETRY_SHORTTOTAL=30s
      - ORDERER_KAFKA_VERBOSE=true
      - ORDERER_KAFKA_BROKERS=[10.16.3.92:9092,10.16.3.93:9092,10.16.3.94:9092,10.16.3.95:9092]
    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/orderer1.example.com/msp:/var/hyperledger/orderer/msp
    - ./crypto-config/ordererOrganizations/example.com/orderers/orderer1.example.com/tls/:/var/hyperledger/orderer/tls
    networks:
 default:
 aliases:
 - fabric_kafka
    ports:
 - 7050:7050
    extra_hosts:
 - "kafka1:10.16.3.92"
 - "kafka2:10.16.3.93"
 - "kafka3:10.16.3.94"
 - "kafka4:10.16.3.95"

在orderer2:/apps/fabric_kafka上新建docker-orderer2.yaml，内容

version: '2'
services:
 orderer2.example.com:
 container_name: orderer2.example.com
    image: hyperledger/fabric-orderer
    environment:
 - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=fabric_kafka_default
      - ORDERER_GENERAL_LOGLEVEL=debug
      - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
      - ORDERER_GENERAL_LISTENPORT=7050
      - 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_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]
      - ORDERER_KAFKA_RETRY_LONGINTERVAL=10s
      - ORDERER_KAFKA_RETRY_LONGTOTAL=100s
      - ORDERER_KAFKA_RETRY_SHORTINTERVAL=1s
      - ORDERER_KAFKA_RETRY_SHORTTOTAL=30s
      - ORDERER_KAFKA_VERBOSE=true
      - ORDERER_KAFKA_BROKERS=[10.16.3.92:9092,10.16.3.93:9092,10.16.3.94:9092,10.16.3.95:9092]
    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/orderer2.example.com/msp:/var/hyperledger/orderer/msp
    - ./crypto-config/ordererOrganizations/example.com/orderers/orderer2.example.com/tls/:/var/hyperledger/orderer/tls
    networks:
 default:
 aliases:
 - fabric_kafka
    ports:
 - 7050:7050
    extra_hosts:
 - "kafka1:10.16.3.92"
 - "kafka2:10.16.3.93"
 - "kafka3:10.16.3.94"
 - "kafka4:10.16.3.95"

在各orderer机器上启动

docker-compose -f docker-orderer0.yaml up -d
docker-compose -f docker-orderer1.yaml up -d
docker-compose -f docker-orderer2.yaml up -d

在peer0org1:/apps/fabric_kafka上新建docker-peer0.yaml，内容

version: '2'
services:
 couchdb:
 container_name: couchdb
    image: hyperledger/fabric-couchdb
    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/555290c50d91fbfd50c03f6abb08910dab00a84403826e4ed97e48bbf287c268_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/555290c50d91fbfd50c03f6abb08910dab00a84403826e4ed97e48bbf287c268_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=10.16.8.89:5984
      - CORE_PEER_ID=peer0.org1.example.com
      - CORE_PEER_NETWORKID=fabric_kafka
      - CORE_PEER_ADDRESS=peer0.org1.example.com:7051
      - CORE_PEER_CHAINCODEADDRESS=peer0.org1.example.com:7052
      - 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
      - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=fabric_kafka_default
      - CORE_VM_DOCKER_TLS_ENABLED=false
      - CORE_LOGGING_LEVEL=DEBUG
      - 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/
        -./chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/chaincode/go
        - ./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:
 - fabric_kafka
    extra_hosts:
 - "orderer0.example.com:10.16.8.91"
 - "orderer1.example.com:10.16.8.92"
 - "orderer2.example.com:10.16.8.93"
 cli:
 container_name: cli
    image: hyperledger/fabric-tools
    tty: true
    environment:
 - GOPATH=/opt/gopath
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      - CORE_LOGGING_LEVEL=DEBUG
      - CORE_PEER_ID=cli
      - CORE_PEER_ADDRESS=peer0.org1.example.com:7051
      - CORE_PEER_CHAINCODELISTENADDRESS=peer0.org1.example.com:7052
      - 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/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:
 - "orderer0.example.com:10.16.8.91"
 - "orderer1.example.com:10.16.8.92"
 - "orderer2.example.com:10.16.8.93"
 - "peer0.org1.example.com:10.16.8.89"
 

注意：此处的555290c50d91fbfd50c03f6abb08910dab00a84403826e4ed97e48bbf287c268_sk要换成实际生成的私钥文件名

在peer0org1机器上启动

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

在peer0org1机器上执行

docker exec -it cli bash

peer channel create -o orderer0.example.com:7050 -c mychannel -f ./channel-artifacts/mychannel.tx

peer channel join -b mychannel.block
peer chaincode install -n mychannel -p github.com/hyperledger/fabric/chaincode/go/chaincode_example02/go -v 1.0
peer chaincode instantiate -o orderer0.example.com:7050 -C mychannel -n mychannel -c '{"Args":["init","A","10","B","10"]}' -P "OR ('Org1MSP.member','Org2MSP.member')" -v 1.0
peer chaincode query -C mychannel -n mychannel -c '{"Args":["query", "A"]}'
peer chaincode invoke -o orderer2.example.com:7050  -C mychannel -n mychannel -c '{"Args":["invoke","A","B","1"]}'
peer chaincode invoke -o orderer0.example.com:7050  -C mychannel -n mychannel -c '{"Args":["invoke","A","B","1"]}'
peer chaincode invoke -o orderer1.example.com:7050  -C mychannel -n mychannel -c '{"Args":["invoke","A","B","1"]}'
peer chaincode query -C mychannel -n mychannel -c '{"Args":["query", "A"]}'

 

至此，Fabric分布式环境搭建完毕！

 

Arvon_阿文
关注
  • 1
    点赞
  • 踩
  • 2
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
21. Fabric2.2 基于Kafka共识算法部署区块链集群
菜鸟的博客
03-13 9696
基于Kafka共识算法 部署Fabric2.2 集群
Fabric项目设置部署 (本地化开发 Fabric 应用-- kafka 共识模式)
fmclx的专栏
08-23 592
//本地化调试 Fabric 应用-- kafka 共识模式 Ubuntu 16.04 @ Z470本中间章节 （一）工程配置修正。 yaml工程配置脚本修改。新建一配置目录并进入 :cd cfg/fabric 拷贝工程自带的配置文件样例 ：sampleconfig/*.*， 拷贝fabric-sample-with-kafka-master/first-network/cry...
kafka和raft共识机制
BSN_yanxishe的博客
03-04 2983
id:BSN_2021 公众号：BSN研习社 两者是不同的。 在kafka共识模式中，orderer与orderer之间不会互相直接建立连接，而是与kafka连接。这种共识模式中，依赖于外部的kafka集群系统和zookeeper集群系统。 每个orderer会把自己的交易发送给kafka集群，交易在kafka对应的topic中排序后，kafka把排序后的交易推送给orderer节点。Orderer节点收到交易后对交易打包，然后发给peer. 在raft共识模式中，orderer与orderer之
Kafka 3.3 使用 KRaft 共识协议替代 ZooKeeper
最新发布
大数据星球-浪尖
04-08 71
Apache 软件基金会发布了包含许多新特性和改进的 Kafka 3.3.1。这是第一个标志着可以在生产环境中使用KRaft（Kafka Raft）共识协议的版本。在几年的开发过程中，它先是在 Kafka 2.8 早期访问版本中发布，然后又在 Kafka 3.0 预览版本中发布。KRaft 是一种共识协议，可以直接在 Kafka 中管理元数据。元数据的管理被整合到了Kafka当中，而不需要使用像Z...
Fabric Kafka入门
weixin_44239023的博客
04-28 296
　　Hyperledger Fabric推荐Kafa用于生产环境。Kafa是一个分布式、具有水平伸缩能力、崩溃容错能力的日志系统。在Hyperledger Fabric区块链中可以有多个Kafka节点，使用zookeeper进行同步管理。本文将介绍Kfaka的基本工作原理，以及在HyperledgerFabric中使用Kafka和zookeeper实现共识的原理，并通过一个实例剖析Hyperled...
Fabric1.4.0 Kafka集群环境部署
weixin_44732379的博客
04-22 885
Fabric1.4.0 Kafka集群环境部署
fabric基于kafka的多orderer的分布式部署脚本.zip
07-26
fabric基于kafka的多orderer的分布式部署脚本：3zookeeper+4kafka+3orderer+4peer+1cli，其中还包含了ca的配置：docker-compose-ca-org1.yaml和docker-compose-ca-org2.yaml，用的时候改下证书和路径就可以了。
kafka分布式集群搭建
04-27
kafka分布式集群搭建
大数据分布式集群环境搭建.docx
11-09
centos大数据分布式集群搭建，包含hadoop spark hbase hive solr elasticsearch redis zookeeper rocketmq mongodb mariadb storm kafka docker
Kafka集群调优实战+分布式集群搭建
10-19
Kafka技术实战学习的优选课程，课程内容全程实战，没有拖泥带水，但不包含基础知识的教学，需要同学们先具备一定的Kafka技术基础再进行学习。课程内容包括了Kafka java Consumer实战，Kafka集成框架等。
ELK+FileBeat+Kafka分布式系统搭建图文教程.docx
06-06
ELK+FileBeat+Kafka分布式系统搭建图文教程 本教程详细记录了ELK+FileBeat+Kafka分布式系统的搭建流程和步骤，为大家快速上手提供了详细的指导。本系统由FileBeat、Kafka、Logstash、Elasticsearch、Kibana五个组件...
Hyperledger Fabric kafka配置
03-09
Hyperledger Fabric默认使用solo共识，实际上它早就已经支持kafka共识，只是配置相对复杂点儿。该资源就是使用kafka共识的多orderer集群环境下的网络所需要使用的配置文件。你也可以参考下文帮您理解：http://blog.csdn.net/binbinxyz/article/details/79491254
Kafka 工作机制
kefeng.wang 的博客
07-24 2833
Kafka 是 Apache 的子项目，是一个高性能跨语言的分布式发布/订阅消息队列系统（没有严格实现 JMS 规范的点对点模型，但可以实现其效果），在企业开发中有广泛的应用。高性能是其最大优势，劣势是消息的可靠性（丢失或重复），这个劣势是为了换取高性能，开发者可以以稍降低性能，来换取消息的可靠性。 作者：王克锋 出处：https://kefeng.wang/2017/11/15/kafk...
fabric 1.3.1 ，全手动部署到5台机器上.支持 kafka 模式的共识机制和 couchdb 存储，以及 fabric ca ， fabric explorer的使用。
一个烂人的随手笔记
10-01 5866
fabric 1.3 ，全手动部署到5台机器上.支持 kafka 模式的共识机制和 couchdb 存储
Hyperledger Fabric基于kafka多机部署
baidu_25845567的博客
10-17 1463
各主机角色和安装的软件 主机编号 A B C D IP 45.32.103.254 149.28.146.218 207.148.75.101 66.42.57.57 角色 orderer0.example.com zookeeper1 kafka1 ca orderer1.exa...
Hyperledger fabric基于kafka共识机制单机搭建
baidu_25845567的博客
10-21 1886
cd /opt/gopath/src/github.com/hyperledger/fabric/scripts/fabric-samples mkdir 181021 cd 181021 mkdir chaincode mkdir network cp ../../first-network/crypto-config.yaml ./ cp ../../first-network/config...
【区块链之技术进阶】掰一掰区块链共识机制与分布式一致性算法
weixin_33937913的博客
09-10 895
咱们在之前的很多篇文章里简单地提起了“共识算法”以及“共识攻击”，大家应该对于我们之前提到的“共识攻击”印象还比较深刻吧，对的，就是我们所说的这和公司占有股份一个道理，当你占有整个公司“51%”的股份时，那就是控股了，岂不是可以为所欲为了呢？在区块链技术这也一样，咱们都知道区块链记账以后是不可以篡改的，就算是合理交易写错地址了也不行！but!当你能说服整...
浅析Hyperledger Fabric共识算法
予衡飞翔
10-18 5503
Hyperledger Fabric共识算法 区块链系统是一个分布式架构，交易账本信息由各个节点管理，组成一个庞大的分布式账本。在分布式系统中，各个节点收到的交易信息的顺序可能存在差异（例如，网络延迟、主机处理性能），这会导致账本信息的状态不一致，例如，小王账户只有10元，但是他同时转账给小李和小张各10元，并且将这两条交易信息分别发送到两个分布式节点上，如果不对这两条交易进行排序校验，那么，小...
Hyperledger Fabric共识机制
热门推荐
btqszl的博客
10-12 1万+
共识 交易必须按照发生的顺序写入分类帐，尽管它们可能位于网络中不同的参与者组之间。为了实现这一点，必须建立交易的顺序，并且必须建立一种拒绝错误（或恶意）插入分类帐的坏交易的方法。 Hyperledger Fabric共识机制，目前包括SOLO，Kafka，以及未来可能要使用的PBFT（实践拜占庭容错）
kafka和kafka共识
10-22
而在Hyperledger Fabric中，Kafka共识是一种共识模式，它与Solo共识不同，需要依赖外部的Kafka集群系统和Zookeeper集群系统。在Kafka共识模式中，Orderer与Orderer之间不会互相直接建立连接，而是与Kafka连接。Kafka...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值