[大数据]fabric1.4 单机部署kafka

简易部署fabirc1.4的kafka

部署方案

在一台服务器上部署

4个zookeeper节点

4个kafka节点

3个orderer节点

4个peer节点并分属于两个组织

1个cli节点

准备项目目录

mkdir test
cd test

生成MSP证书

在项目目录底下

vi crypto-config.yaml

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

# ---------------------------------------------------------------------------
# "OrdererOrgs" - Definition of organizations managing orderer nodes
# ---------------------------------------------------------------------------
OrdererOrgs:
  # ---------------------------------------------------------------------------
  # Orderer
  # ---------------------------------------------------------------------------
  - Name: Orderer
    Domain: example.com
    # ---------------------------------------------------------------------------
    # "Specs" - See PeerOrgs below for complete description
    # ---------------------------------------------------------------------------
    Specs:
      - Hostname: orderer1
      - Hostname: orderer2
      - Hostname: orderer3

# ---------------------------------------------------------------------------
# "PeerOrgs" - Definition of organizations managing peer nodes
# ---------------------------------------------------------------------------
PeerOrgs:
  # ---------------------------------------------------------------------------
  # Org1
  # ---------------------------------------------------------------------------
  - Name: Org1
    Domain: org1.example.com
    # ---------------------------------------------------------------------------
    # "Specs"
    # ---------------------------------------------------------------------------
    # Uncomment this section to enable the explicit definition of hosts in your
    # configuration.  Most users will want to use Template, below
    #
    # Specs is an array of Spec entries.  Each Spec entry consists of two fields:
    #   - Hostname:   (Required) The desired hostname, sans the domain.
    #   - CommonName: (Optional) Specifies the template or explicit override for
    #                 the CN.  By default, this is the template:
    #
    #                              "{{.Hostname}}.{{.Domain}}"
    #
    #                 which obtains its values from the Spec.Hostname and
    #                 Org.Domain, respectively.
    # ---------------------------------------------------------------------------
    # Specs:
    #   - Hostname: foo # implicitly "foo.org1.example.com"
    #     CommonName: foo27.org5.example.com # overrides Hostname-based FQDN set above
    #   - Hostname: bar
    #   - Hostname: baz
    # ---------------------------------------------------------------------------
    # "Template"
    # ---------------------------------------------------------------------------
    # Allows for the definition of 1 or more hosts that are created sequentially
    # from a template. By default, this looks like "peer%d" from 0 to Count-1.
    # You may override the number of nodes (Count), the starting index (Start)
    # or the template used to construct the name (Hostname).
    #
    # Note: Template and Specs are not mutually exclusive.  You may define both
    # sections and the aggregate nodes will be created for you.  Take care with
    # name collisions
    # ---------------------------------------------------------------------------
    Template:
      Count: 2
      # Start: 5
      # Hostname: {{.Prefix}}{{.Index}} # default
    # ---------------------------------------------------------------------------
    # "Users"
    # ---------------------------------------------------------------------------
    # Count: The number of user accounts _in addition_ to Admin
    # ---------------------------------------------------------------------------
    Users:
      Count: 1
  # ---------------------------------------------------------------------------
  # Org2: See "Org1" for full specification
  # ---------------------------------------------------------------------------
  - Name: Org2
    Domain: org2.example.com
    Template:
      Count: 2
    Users:
      Count: 1

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

生成对应的证书文件夹crypto-config

生成创世区块

生成configtx.yaml

vi configtx.yaml

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

---

################################################################################
#
#   Section: Organizations
#
#   - This section defines the different organizational identities which will
#   be referenced later in the configuration.
#
################################################################################
Organizations:

    # SampleOrg defines an MSP using the sampleconfig.  It should never be used
    # in production but may be used as a template for other definitions
    - &OrdererOrg
        # DefaultOrg defines the organization which is used in the sampleconfig
        # of the fabric.git development environment
        Name: OrdererOrg

        # ID to load the MSP definition as
        ID: OrdererMSP

        # MSPDir is the filesystem path which contains the MSP configuration
        MSPDir: crypto-config/ordererOrganizations/example.com/msp

    - &Org1
        # DefaultOrg defines the organization which is used in the sampleconfig
        # of the fabric.git development environment
        Name: Org1MSP

        # ID to load the MSP definition as
        ID: Org1MSP

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

        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.org1.example.com
              Port: 7051

    - &Org2
        # DefaultOrg defines the organization which is used in the sampleconfig
        # of the fabric.git development environment
        Name: Org2MSP

        # ID to load the MSP definition as
        ID: Org2MSP

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

        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

################################################################################
#
#   SECTION: Orderer
#
#   - This section defines the values to encode into a config transaction or
#   genesis block for orderer related parameters
#
################################################################################
Orderer: &OrdererExample

    # Orderer Type: The orderer implementation to start
    # Available types are "solo" and "kafka"
    OrdererType: kafka

    Addresses:
        - orderer1.example.com:7050
        - orderer2.example.com:7050
        - orderer3.example.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:

        # Max Message Count: The maximum number of messages to permit in a batch
        MaxMessageCount: 10

        # Absolute Max Bytes: The absolute maximum number of bytes allowed for
        # the serialized messages in a batch.
        # 设置最大的区块大小。每个区块最大有Orderer.AbsoluteMaxBytes个字节（不包括头部）。
        # 假定这里设置的值为A，记住这个值，这会影响怎样配置Kafka代理。
        AbsoluteMaxBytes: 99 MB

        # Preferred Max Bytes: The preferred maximum number of bytes allowed for
        # the serialized messages in a batch. A message larger than the preferred
        # max bytes will result in a batch larger than preferred max bytes.
        # 设置每个区块建议的大小。Kafka对于相对小的消息提供更高的吞吐量；区块大小最好不要超过1MB。
        PreferredMaxBytes: 512 KB

    Kafka:
        # Brokers: A list of Kafka brokers to which the orderer connects
        # NOTE: Use IP:port notation
        # 包括Kafka集群中至少两个代理的地址信息（IP:port）
        # 这个List不需要是完全的（这些是你的种子代理）
        # 这个代理表示当前Orderer所要连接的Kafka代理
        Brokers:
            - k1:9092
            - k3:9092

    # Organizations is the list of orgs which are defined as participants on
    # the orderer side of the network
    Organizations:

################################################################################
#
#   SECTION: Application
#
#   - This section defines the values to encode into a config transaction or
#   genesis block for application related parameters
#
################################################################################
Application: &ApplicationDefaults

    # Organizations is the list of orgs which are defined as participants on
    # the application side of the network
    Organizations:
    
################################################################################
#
#   Profile
#
#   - Different configuration profiles may be encoded here to be specified
#   as parameters to the configtxgen tool
#
################################################################################
Profiles:

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

创建通道文件夹channel-artifacts

mkdir channel-artifacts

生成创世区块

# 生成排序服务创世区块
export FABRIC_CFG_PATH=$PWD
configtxgen -profile TwoOrgsOrdererGenesis -outputBlock ./channel-artifacts/genesis.block

# 生成通道配置创世区块
export CHANNEL_NAME=mychannel
configtxgen -profile TwoOrgsChannel -outputCreateChannelTx ./channel-artifacts/channel.tx -channelID $CHANNEL_NAME

定义组织锚节点

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

生成节点base文件

创建base文件夹

mkdir base

再创建各个base.yaml文件

peer-base.yaml

# COPYRIGHT Hello Corp. All Rights Reserved.## Author: Haley# version: '2'services:  peer-base:    image: hyperledger/fabric-peer    environment:      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock      - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=kafka_default      - CORE_LOGGING_LEVEL=DEBUG      - CORE_PEER_TLS_ENABLED=false      - 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_ROOTCERT_FILE=/etc/hyperledger/fabric/tls/ca.crt    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer    command: peer node start

kafka-base.yaml

# COPYRIGHT Hello Corp. All Rights Reserved.# # Author: Haley#version: '2'services:  zookeeper:    image: hyperledger/fabric-zookeeper    restart: always    environment:      - quorumListenOnAllIPs=true    ports:      - '2181'      - '2888'      - '3888'  kafka:    image: hyperledger/fabric-kafka    restart: always    environment:      # message.max.bytes      # The maximum size of envelope that the broker can receive.      - KAFKA_MESSAGE_MAX_BYTES=103809024 # 99 * 1024 * 1024 B      - KAFKA_REPLICA_FETCH_MAX_BYTES=103809024 # 99 * 1024 * 1024 B      - KAFKA_UNCLEAN_LEADER_ELECTION_ENABLE=false      - KAFKA_LOG_RETENTION_MS=-1    ports:      - '9092'

orderer-base.yaml

# COPYRIGHT Hello Corp. All Rights Reserved.## Author: Haley# version: '2'services:  orderer.example.com:    image: hyperledger/fabric-orderer    environment:      - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=example_default      - ORDERER_GENERAL_LOGLEVEL=error      - 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      # enabled TLS      - ORDERER_GENERAL_TLS_ENABLED=false      - ORDERER_GENERAL_TLS_PRIVATEKEY=/var/hyperledger/orderer/tls/server.key      - ORDERER_GENERAL_TLS_CERTIFICATE=/var/hyperledger/orderer/tls/server.crt      - ORDERER_GENERAL_TLS_ROOTCAS=[/var/hyperledger/orderer/tls/ca.crt]      - 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=[k1:9092,k2:9092,k3:9092,k4:9092]    working_dir: /opt/gopath/src/github.com/hyperledger/fabric    command: orderer    volumes:      - ./channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block    networks:      default:        aliases:          - example    ports:      - "7050"

创建docker-compose

回到项目根目录

cd ..

创建.env

vi .env

COMPOSE_PROJECT_NAME=kafka

创建docker-compose.yaml

# COPYRIGHT Hello Corp. All Rights Reserved.## Author: Haley#version: '2'services:  z1:    extends:      file: base/kafka-base.yaml      service: zookeeper    container_name: z1    hostname: z1    environment:      # ID在集合中必须是唯一的并且应该有一个值在1-255之间。      - ZOO_MY_ID=1      # 组成ZK集合的服务器列表。客户端使用的列表必须与ZooKeeper服务器列表所拥有的每一个ZK服务器相匹配。      # 有两个端口号：第一个是追随者用来连接领导者的，第二个是领导人选举。      - ZOO_SERVERS=server.1=z1:2888:3888 server.2=z2:2888:3888 server.3=z3:2888:3888#    volumes:#        - /var/run/:/host/var/run/  z2:    extends:      file: base/kafka-base.yaml      service: zookeeper    container_name: z2    hostname: z2    environment:      - ZOO_MY_ID=2      - ZOO_SERVERS=server.1=z1:2888:3888 server.2=z2:2888:3888 server.3=z3:2888:3888  z3:    extends:      file: base/kafka-base.yaml      service: zookeeper    container_name: z3    hostname: z3    environment:      - ZOO_MY_ID=3      - ZOO_SERVERS=server.1=z1:2888:3888 server.2=z2:2888:3888 server.3=z3:2888:3888  k1:    extends:      file: base/kafka-base.yaml      service: kafka    container_name: k1    hostname: k1    environment:      - KAFKA_BROKER_ID=1      # min.insync.replicas=M --- 设置一个M值（例如1<M<N，查看下面的default.replication.factor）      # 数据提交时会写入至少M个副本（这些数据然后会被同步并且归属到in-sync副本集合或ISR）。      # 其它情况，写入操作会返回一个错误。接下来：      # 1. 如果channel写入的数据多达N-M个副本变的不可用，操作可以正常执行。      # 2. 如果有更多的副本不可用，Kafka不可以维护一个有M数量的ISR集合，因此Kafka停止接收写操作。Channel只有当同步M个副本后才可以重新可以写。      - KAFKA_MIN_INSYNC_REPLICAS=2      - KAFKA_DEFAULT_REPLICATION_FACTOR=3      # 指向Zookeeper节点的集合，其中包含ZK的集合。      - KAFKA_ZOOKEEPER_CONNECT=z1:2181,z2:2181,z3:2181    depends_on:      - z1      - z2      - z3  k2:    extends:      file: base/kafka-base.yaml      service: kafka    container_name: k2    hostname: k2    environment:      - KAFKA_BROKER_ID=2      - KAFKA_MIN_INSYNC_REPLICAS=2      - KAFKA_DEFAULT_REPLICATION_FACTOR=3      - KAFKA_ZOOKEEPER_CONNECT=z1:2181,z2:2181,z3:2181    depends_on:      - z1      - z2      - z3  k3:    extends:      file: base/kafka-base.yaml      service: kafka    container_name: k3    hostname: k3    environment:      - KAFKA_BROKER_ID=3      - KAFKA_MIN_INSYNC_REPLICAS=2      - KAFKA_DEFAULT_REPLICATION_FACTOR=3      - KAFKA_ZOOKEEPER_CONNECT=z1:2181,z2:2181,z3:2181    depends_on:      - z1      - z2      - z3  k4:    extends:      file: base/kafka-base.yaml      service: kafka    container_name: k4    hostname: k4    environment:      - KAFKA_BROKER_ID=4      - KAFKA_MIN_INSYNC_REPLICAS=2      - KAFKA_DEFAULT_REPLICATION_FACTOR=3      - KAFKA_ZOOKEEPER_CONNECT=z1:2181,z2:2181,z3:2181    depends_on:      - z1      - z2      - z3  orderer1.example.com:    extends:      file: base/orderer-base.yaml      service: orderer.example.com    container_name: orderer1.example.com    #environment:      #- ORDERER_GENERAL_LOCALMSPID=OrdererMSP      #- ORDERER_GENERAL_LOCALMSPDIR=/var/hyperledger/orderer/msp      #- 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]    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    depends_on:      - z1      - z2      - z3      - k1      - k2      - k3      - k4  orderer2.example.com:    extends:      file: base/orderer-base.yaml      service: orderer.example.com    container_name: orderer2.example.com    #environment:      #- ORDERER_GENERAL_LOCALMSPID=OrdererMSP      #- ORDERER_GENERAL_LOCALMSPDIR=/var/hyperledger/orderer/msp      #- 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]    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    depends_on:      - z1      - z2      - z3      - k1      - k2      - k3      - k4  orderer3.example.com:    extends:      file: base/orderer-base.yaml      service: orderer.example.com    container_name: orderer3.example.com    #environment:      #- ORDERER_GENERAL_LOCALMSPID=OrdererMSP      #- ORDERER_GENERAL_LOCALMSPDIR=/var/hyperledger/orderer/msp      #- 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]    volumes:      - ./channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block      - ./crypto-config/ordererOrganizations/example.com/orderers/orderer3.example.com/msp:/var/hyperledger/orderer/msp      - ./crypto-config/ordererOrganizations/example.com/orderers/orderer3.example.com/tls:/var/hyperledger/orderer/tls    depends_on:      - z1      - z2      - z3      - k1      - k2      - k3      - k4  peer0.org1.example.com:    extends:      file: base/peer-base.yaml      service: peer-base    container_name: peer0.org1.example.com    environment:      - CORE_PEER_ID=peer0.org1.example.com      - CORE_PEER_ADDRESS=peer0.org1.example.com:7051      - CORE_PEER_CHAINCODELISTENADDRESS=peer0.org1.example.com:7052      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.example.com:7051      - CORE_PEER_LOCALMSPID=Org1MSP    volumes:      - /var/run/:/host/var/run/      - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/msp:/etc/hyperledger/fabric/msp      - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls:/etc/hyperledger/fabric/tls    ports:      - 7051:7051      - 7052:7052      - 7053:7053  peer1.org1.example.com:    extends:      file: base/peer-base.yaml      service: peer-base    container_name: peer1.org1.example.com    environment:      - CORE_PEER_ID=peer1.org1.example.com      - CORE_PEER_ADDRESS=peer1.org1.example.com:7051      - CORE_PEER_CHAINCODELISTENADDRESS=peer1.org1.example.com:7052      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org1.example.com:7051      - CORE_PEER_LOCALMSPID=Org1MSP    volumes:      - /var/run/:/host/var/run/      - ./crypto-config/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/msp:/etc/hyperledger/fabric/msp      - ./crypto-config/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/tls:/etc/hyperledger/fabric/tls    ports:      - 8051:7051      - 8052:7052      - 8053:7053  peer0.org2.example.com:    extends:      file: base/peer-base.yaml      service: peer-base    container_name: peer0.org2.example.com    environment:      - CORE_PEER_ID=peer0.org2.example.com      - CORE_PEER_ADDRESS=peer0.org2.example.com:7051      - CORE_PEER_CHAINCODELISTENADDRESS=peer0.org2.example.com:7052      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org2.example.com:7051      - CORE_PEER_LOCALMSPID=Org2MSP    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    ports:      - 9051:7051      - 9052:7052      - 9053:7053  peer1.org2.example.com:    extends:      file: base/peer-base.yaml      service: peer-base    container_name: peer1.org2.example.com    environment:      - CORE_PEER_ID=peer1.org2.example.com      - CORE_PEER_ADDRESS=peer1.org2.example.com:7051      - CORE_PEER_CHAINCODELISTENADDRESS=peer1.org2.example.com:7052      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org2.example.com:7051      - CORE_PEER_LOCALMSPID=Org2MSP    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    ports:      - 10051:7051      - 10052:7052      - 10053:7053  cli:    container_name: cli    image: hyperledger/fabric-tools    tty: true    environment:      - GOPATH=/opt/gopath      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock      - CORE_LOGGING_LEVEL=DEBUG      - CORE_PEER_ID=cli      - CORE_PEER_ADDRESS=peer0.org1.example.com:7051      - CORE_PEER_LOCALMSPID=Org1MSP      - CORE_PEER_TLS_ENABLED=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    #command: /bin/bash -c 'sleep 30; ./scripts/script.sh ${CHANNEL_NAME}; sleep $TIMEOUT'    volumes:        - /var/run/:/host/var/run/        - ../chaincode/:/opt/gopath/src/github.com/hyperledger/fabric/examples/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:      - orderer1.example.com      - orderer2.example.com      - orderer3.example.com      - peer0.org1.example.com      - peer1.org1.example.com      - peer0.org2.example.com      - peer1.org2.example.com

启动网络

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

创建并加入通道

docker exec -it cli bashexport CHANNEL_NAME=mychannelpeer channel create -o orderer1.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/channel.txpeer channel join -b mychannel.block

切换环境变量，将peer1.org1.example.com加入通道

export CORE_PEER_ADDRESS=peer1.org1.example.com:7051export CORE_PEER_LOCALMSPID="Org1MSP"export 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.crtexport CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin\@org1.example.com/msppeer channel join -b mychannel.block

同理，改动环境变量将peer节点逐个加入通道

安装和实例化链码

首先确认在docker内的github.com/hyperledger/fabric/examples/chaincode/chaincode_example02是否有该路径，如果没有从外部拉进去

在peer0.org.example.com上安装链码：

export CORE_PEER_ADDRESS=peer0.org1.example.com:7051export CORE_PEER_LOCALMSPID="Org1MSP"export 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.crtexport CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin\@org1.example.com/msppeer chaincode install -n mycc -v 1.0 -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02# 重新打开一个终端，确认安装是否成功docker exec peer0.org1.example.com ls /var/hyperledger/production/chaincodes

同理在其他的节点上安装链码

安装完成后，任意选择一个peer节点实例化链码：

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

链码调用或查询

切换至任意节点的环境，然后可以执行调用或查询。

export CORE_PEER_ADDRESS=peer0.org2.example.com:7051export CORE_PEER_LOCALMSPID="Org2MSP"export 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.crtexport CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin\@org2.example.com/msppeer chaincode invoke -o orderer1.example.com:7050 -C $CHANNEL_NAME -n mycc -c '{"Args":["invoke", "a", "b", "10"]}'peer chaincode query -C $CHANNEL_NAME -n mycc -c '{"Args":["query","a"]}'

注：必须要安装了的节点才可以进行调用与查询，调用生成区块

链码升级

在cli的容器中调用

# 先安装peer chaincode install -n mycc -v 2.0 -p github.com/hyperledger/fabric/examples/chaincode/go/mycc2.0#后升级peer chaincode upgrade -o orderer1.example.com:7050 -C mychannel -n mycc -v 2.0 -c '{"Args":["init", "a", "100", "b", "200"]}' -P "OR ('Org1MSP.member','Org2MSP.member')"

多机部署思路

若需要多机部署只需在各peer-compose.yaml文件下加，即peer与其他的节点进行通信

extra_hosts:    - "orderer0.example.com:192.168.1.13"    - "orderer1.example.com:192.168.1.13"    - "ca.example.com:192.168.1.13"    - "peer1.org1.example.com:192.168.1.15"

在cli.yml下加，即cli与orderer通信

extra_hosts:  - "orderer0.example.com:192.168.1.13"  - "orderer1.example.com:192.168.1.13"

在kafka.yml下加，即kafka与peer进行通信

extra_hosts:    - "peer0.org1.example.com:192.168.1.14"    - "peer1.org1.example.com:192.168.1.15"

上面的yml都是在docker-compose中用到，即按照部署的方案在不同的服务器上起不同的容器

参考
https://blog.csdn.net/binbinxyz/article/details/79491254