kafka多机多节点部署

发表于 | 分类于

7. Solo多机多节点部署

7.1. 准备工作

所有的节点分离部署, 每台主机上有一个节点, 节点的分布如下表:

名称 IP Hostname 组织机构
orderer 192.168.247.129 orderer.wumansgy.com Orderer
peer0 192.168.247.141 peer0.orggo.com OrgGo
peer1 192.168.247.142 peer1.orggo.com OrgGo
peer0 192.168.247.131 peer0.orgcpp.com OrgCpp
peer1 192.168.247.1451 peer1.orgcpp.com OrgCpp

下面的操作在任意一台主机上做都可以, 下面的例子中, 生成证书和创始块、通道文件操作是在 Orderer节点对应的主机上进行的。

7.1.1 准备工作 - 创建工作目录

1
2
3
4
5
6
7
8
9
10
11
# N台主机需要创建一个名字相同的工作目录, 该工作目录名字自己定, 切记名字一定要相同
# 192.168.247.129
$ mkdir ~/testwork
# 192.168.247.141
$ mkdir ~/testwork
# 192.168.247.131
$ mkdir ~/testwork
# 192.168.247.142
$ mkdir ~/testwork
# 192.168.247.145
$ mkdir ~/testwork

7.1.2 生成组织节点和用户证书

  • 编写配置文件

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    # crypto-config.yaml -> 名字可以改, 一般起名为crypto-config.yaml

    OrdererOrgs:
      # ---------------------------------------------------------------------------
      # Orderer
      # ---------------------------------------------------------------------------
      - Name: Orderer
        Domain: test.com
        Specs:
          - Hostname: orderer

    PeerOrgs:
      # ---------------------------------------------------------------------------
      # Org1
      # ---------------------------------------------------------------------------
      - Name: OrgGo
        Domain: orggo.test.com
        EnableNodeOUs: false
        Template:
          Count: 2
        Users:
          Count: 1
      # ---------------------------------------------------------------------------
      # Org2: See "Org1" for full specification
      # ---------------------------------------------------------------------------
      - Name: OrgCpp
        Domain: orgcpp.test.com
        EnableNodeOUs: false
        Template:
          Count: 2
        Users:
          Count: 1

  • 使用cryptogen生成证书

    1
    $ cryptogen generate --config=crypto-config.yaml

7.1.3 生成通道文件和创始块文件

  • 编写配置文件, 名字为 configtx.yaml, 该名字不能改, 是固定的.

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    56
    57
    58
    59
    60
    61
    62
    63
    64
    65
    66
    67
    68
    69
    70
    71
    72
    73
    74
    75
    76
    77
    78
    79
    80
    81
    82
    83
    84
    85
    86
    87
    88
    89
    90
    91
    92
    93
    94
    95
    96
    97
    98
    99
    # configtx.yaml -> 名字不能变
    ---
    ################################################################################
    #
    #   Section: Organizations
    #
    ################################################################################
    Organizations:
        - &OrdererOrg
            Name: OrdererOrg
            ID: OrdererMSP
            MSPDir: ./crypto-config/ordererOrganizations/test.com/msp

        - &OrgGo
            Name: OrgGoMSP
            ID: OrgGoMSP
            MSPDir: ./crypto-config/peerOrganizations/orggo.test.com/msp
            AnchorPeers:
                - Host: peer0.orggo.test.com
                  Port: 7051

        - &OrgCpp
            Name: OrgCppMSP
            ID: OrgCppMSP
            MSPDir: ./crypto-config/peerOrganizations/orgcpp.test.com/msp
            AnchorPeers:
                - Host: peer0.orgcpp.test.com
                  Port: 7051

    ################################################################################
    #
    #   SECTION: Capabilities
    #
    ################################################################################
    Capabilities:
        Global: &ChannelCapabilities
            V1_1: true
        Orderer: &OrdererCapabilities
            V1_1: true
        Application: &ApplicationCapabilities
            V1_2: true

    ################################################################################
    #
    #   SECTION: Application
    #
    ################################################################################
    Application: &ApplicationDefaults
        Organizations:

    ################################################################################
    #
    #   SECTION: Orderer
    #
    ################################################################################
    Orderer: &OrdererDefaults
        # Available types are "solo" and "kafka"
        OrdererType: solo
        Addresses:
            - orderer.test.com:7050
        BatchTimeout: 2s
        BatchSize:
            MaxMessageCount: 10
            AbsoluteMaxBytes: 99 MB
            PreferredMaxBytes: 512 KB
        Kafka:
            Brokers:
                - 127.0.0.1:9092
        Organizations:

    ################################################################################
    #
    #   Profile
    #
    ################################################################################
    Profiles:
        TwoOrgsOrdererGenesis:
            Capabilities:
                <<: *ChannelCapabilities
            Orderer:
                <<: *OrdererDefaults
                Organizations:
                    - *OrdererOrg
                Capabilities:
                    <<: *OrdererCapabilities
            Consortiums:
                SampleConsortium:
                    Organizations:
                        - *OrgGo
                        - *OrgCpp
        TwoOrgsChannel:
            Consortium: SampleConsortium
            Application:
                <<: *ApplicationDefaults
                Organizations:
                    - *OrgGo
                    - *OrgCpp
                Capabilities:
                    <<: *ApplicationCapabilities

  • 通过命令configtxgen生成创始块和通道文件

    1
    2
    3
    4
    5
    6
    # 我们先创建一个目录 channel-artifacts 存储生成的文件, 目的是为了和后边的配置文件模板的配置项保持一致
    $ mkdir channel-artifacts
    # 生成通道文件
    $ configtxgen -profile TwoOrgsOrdererGenesis -outputBlock ./channel-artifacts/genesis.block
    # 生成创始块文件
    $ configtxgen -profile TwoOrgsChannel -outputCreateChannelTx ./channel-artifacts/channel.tx -channelID testchannel

7.2 部署 orderer 排序节点

7.2.1 编写配置文件

编写启动orderer节点容器使用的配置文件 - docker-compose.yaml

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
version: '2'

services:

  orderer.test.com:
    container_name: orderer.test.com
    image: hyperledger/fabric-orderer:latest
    environment:
      - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=testwork_default
      - ORDERER_GENERAL_LOGLEVEL=INFO
      - 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=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]
    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/test.com/orderers/orderer.test.com/msp:/var/hyperledger/orderer/msp
    - ./crypto-config/ordererOrganizations/test.com/orderers/orderer.test.com/tls/:/var/hyperledger/orderer/tls
    networks:
        default:
          aliases:
            - testwork  # 这个名字使用当前配置文件所在的目录 的名字
    ports:
      - 7050:7050

注意的细节:

  • networks的名字要跟当前配置文件所在的目录名相同
  • 环境变量CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=testwork_default的名字是网络名_default

7.2.2 启动orderer容器

通过上面编写好的docker-compose配置文件就可以启动orderer容器了

1
2
3
4
5
6
7
8
$ docker-compose up -d
Creating network "testwork_default" with the default driver
Creating orderer.test.com ... done
# 检测是否启动成功
$ docker-compose  ps
      Name         Command   State           Ports         
-----------------------------------------------------------
orderer.test.com   orderer   Up      0.0.0.0:7050->7050/tcp

7.3 部署 peer0.orggo 节点

7.3.1 准备工作

  • 切换到peer0.orggo主机 - 192.168.247.141

  • 进入到工作目录中: 

    1
    $ cd ~/testwork

  • 拷贝文件

    将orderer节点所在宿主机上生成的crypto-config和channel-artifacts目录拷贝到当前testwork目录中。

    我们可以通过scp命令实现远程拷贝, 从orderer节点宿主机拷贝到当前peer0.orggo节点.

    • orderer节点宿主机IP: 192.168.247.129, 登录用户名: wumansgy 
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    # 通过scp命令远程拷贝
    # -r : 表示要拷贝的是目录, 执行递归操作
    # wumansgy@192.168.247.129:/home/wumansgy/testwork/channel-artifacts
    # 	wumansgy@192.168.247.129: 从192.168.247.129上拷贝数据, 登录用户名为wumansgy
    #   /home/wumansgy/testwork/channel-artifacts: 要拷贝192.168.247.129上wumansgy用户的哪个目录
    #   ./ : 远程目录拷贝到本地的什么地方
    $ scp -r wumansgy@192.168.247.129:/home/wumansgy/testwork/channel-artifacts  ./
    $ scp -r wumansgy@192.168.247.129:/home/wumansgy/testwork/crypto-config  ./
    # 查看拷贝结果
    $ tree ./ -L 1
    .
    ├── channel-artifacts
    └── crypto-config

7.3.2 编写 配置文件

编写启动 peer0-orggo节点的配置文件 - docker-compose.yaml

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
# docker-compose.yaml
version: '2'

services:
    peer0.orggo.test.com:
      container_name: peer0.orggo.test.com
      image: hyperledger/fabric-peer:latest
      environment:
        - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
        - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=testwork_default
        - CORE_LOGGING_LEVEL=INFO
        #- CORE_LOGGING_LEVEL=DEBUG
        - CORE_PEER_GOSSIP_USELEADERELECTION=true
        - CORE_PEER_GOSSIP_ORGLEADER=false
        - CORE_PEER_PROFILE_ENABLED=true
        - CORE_PEER_LOCALMSPID=OrgGoMSP
        - CORE_PEER_ID=peer0.orggo.test.com
        - CORE_PEER_ADDRESS=peer0.orggo.test.com:7051
        - CORE_PEER_GOSSIP_BOOTSTRAP=peer0.orggo.test.com:7051
        - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.orggo.test.com:7051
        # TLS
        - CORE_PEER_TLS_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
      volumes:
        - /var/run/:/host/var/run/
        - ./crypto-config/peerOrganizations/orggo.test.com/peers/peer0.orggo.test.com/msp:/etc/hyperledger/fabric/msp
        - ./crypto-config/peerOrganizations/orggo.test.com/peers/peer0.orggo.test.com/tls:/etc/hyperledger/fabric/tls
      working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
      command: peer node start
      networks:
        default:
          aliases:
            - testwork
      ports:
        - 7051:7051
        - 7053:7053
      extra_hosts:  # 声明域名和IP的对应关系
        - "orderer.test.com:192.168.247.129"
        - "peer0.orgcpp.test.com:192.168.247.131"
        
    cli:
      container_name: cli
      image: hyperledger/fabric-tools:latest
      tty: true
      stdin_open: true
      environment:
        - GOPATH=/opt/gopath
        - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
        #- CORE_LOGGING_LEVEL=DEBUG
        - CORE_LOGGING_LEVEL=INFO
        - CORE_PEER_ID=cli
        - CORE_PEER_ADDRESS=peer0.orggo.test.com:7051
        - CORE_PEER_LOCALMSPID=OrgGoMSP
        - CORE_PEER_TLS_ENABLED=true
        - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orggo.test.com/peers/peer0.orggo.test.com/tls/server.crt
        - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orggo.test.com/peers/peer0.orggo.test.com/tls/server.key
        - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orggo.test.com/peers/peer0.orggo.test.com/tls/ca.crt
        - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orggo.test.com/users/Admin@orggo.test.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/
          - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
      depends_on:   # 启动顺序
        - peer0.orggo.test.com
      
      networks:
          default:
            aliases:
              - testwork
      extra_hosts:
        - "orderer.test.com:192.168.247.129"
        - "peer0.orggo.test.com:192.168.247.141"
        - "peer0.orgcpp.test.com:192.168.247.131"

7.3.3 启动容器

  • 启动容器

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    $ docker-compose up -d
    Creating network "testwork_default" with the default driver
    Creating peer0.orgGo.test.com ... done
    Creating cli                  ... done
    # 查看启动状态
    $ docker-compose ps
            Name               Command       State                       Ports                     
    -----------------------------------------------------------------------------------------------
    cli                    /bin/bash         Up                                                    
    peer0.orgGo.test.com   peer node start   Up      0.0.0.0:7051->7051/tcp, 0.0.0.0:7053->7053/tcp

7.3.4 对peer0.orggo节点的操作

  • 进入到客户端容器中

    1
    $ docker exec -it cli bash

  • 创建通道

    1
    2
    3
    $ peer channel create -o orderer.test.com:7050 -c testchannel -f ./channel-artifacts/channel.tx --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/test.com/msp/tlscacerts/tlsca.test.com-cert.pem
    $ ls
    channel-artifacts  crypto  `testchannel.block`  --> 生成的通道块文件

  • 将当前节点加入到通道中

    1
    $ peer channel join -b testchannel.block

  • 安装链码

    1
    $ peer chaincode install -n testcc -v 1.0 -l golang -p github.com/chaincode

  • 初始化链码

    1
    $ peer chaincode instantiate -o orderer.test.com:7050 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/test.com/msp/tlscacerts/tlsca.test.com-cert.pem -C testchannel -n testcc -v 1.0 -l golang -c '{"Args":["init","a","100","b","200"]}' -P "AND ('OrgGoMSP.member', 'OrgCppMSP.member')"

  • 查询

    1
    2
    $ peer chaincode query -C testchannel -n testcc -c '{"Args":["query","a"]}'
    $ peer chaincode query -C testchannel -n testcc -c '{"Args":["query","b"]}'

  • 将生成的通道文件 testchannel.block 从cli容器拷贝到宿主机

    1
    2
    3
    4
    # 从客户端容器退出到宿主机
    $ exit
    # 拷贝操作要在宿主机中进行
    $ docker cp cli:/opt/gopath/src/github.com/hyperledger/fabric/peer/testchannel.block ./

7.4 部署 peer0.orgcpp 节点

7.4.1 准备工作

  • 切换到peer0.orgcpp主机 - 192.168.247.131

  • 进入到工作目录

    1
    $ cd ~/testwork

  • 远程拷贝文件

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    # 从主机192.168.247.141的zoro用户下拷贝目录crypto-config到当前目录下
    $ scp -r zoro@192.168.247.141:/home/zoro/testwork/crypto-config  ./	
    # 链码拷贝
    $ scp -r zoro@192.168.247.141:/home/zoro/testwork/chaincode  ./
    # 从主机192.168.247.141的zoro用户下拷贝文件testchannel.block到当前目录下
    $ scp zoro@192.168.247.141:/home/zoro/testwork/testchannel.block  ./
    # 查看结果
    $ tree ./ -L 1
    ./
    ├── chaincode
    ├── crypto-config
    └── testchannel.block

  • 为了方便操作可以将通道块文件放入到客户端容器挂载的目录中

    1
    2
    3
    4
    # 创建目录
    $ mkdir channel-artifacts  
    # 移动
    $ mv testchannel.block channel-artifacts/

7.4.2 编写配置文件

编写启动peer0.orgcpp节点的配置文件 docker-compose.yaml

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
# docker-compose.yaml
version: '2'
services:
    peer0.orgcpp.test.com:
      container_name: peer0.orgcpp.test.com
      image: hyperledger/fabric-peer:latest
      environment:
        - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
        - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=testwork_default
        - CORE_LOGGING_LEVEL=INFO
        #- CORE_LOGGING_LEVEL=DEBUG
        - CORE_PEER_GOSSIP_USELEADERELECTION=true
        - CORE_PEER_GOSSIP_ORGLEADER=false
        - CORE_PEER_PROFILE_ENABLED=true
        - CORE_PEER_LOCALMSPID=OrgCppMSP
        - CORE_PEER_ID=peer0.orgcpp.test.com
        - CORE_PEER_ADDRESS=peer0.orgcpp.test.com:7051
        - CORE_PEER_GOSSIP_BOOTSTRAP=peer0.orgcpp.test.com:7051
        - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.orgcpp.test.com:7051
        # TLS
        - CORE_PEER_TLS_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
      volumes:
        - /var/run/:/host/var/run/
        - ./crypto-config/peerOrganizations/orgcpp.test.com/peers/peer0.orgcpp.test.com/msp:/etc/hyperledger/fabric/msp
        - ./crypto-config/peerOrganizations/orgcpp.test.com/peers/peer0.orgcpp.test.com/tls:/etc/hyperledger/fabric/tls
      working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
      command: peer node start
      networks:
        default:
          aliases:
            - testwork
      ports:
        - 7051:7051
        - 7053:7053
      extra_hosts:  # 声明域名和IP的对应关系
        - "orderer.test.com:192.168.247.129"
        - "peer0.orggo.test.com:192.168.247.141"
        
    cli:
      container_name: cli
      image: hyperledger/fabric-tools:latest
      tty: true
      stdin_open: true
      environment:
        - GOPATH=/opt/gopath
        - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
        #- CORE_LOGGING_LEVEL=DEBUG
        - CORE_LOGGING_LEVEL=INFO
        - CORE_PEER_ID=cli
        - CORE_PEER_ADDRESS=peer0.orgcpp.test.com:7051
        - CORE_PEER_LOCALMSPID=OrgCppMSP
        - CORE_PEER_TLS_ENABLED=true
        - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orgcpp.test.com/peers/peer0.orgcpp.test.com/tls/server.crt
        - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orgcpp.test.com/peers/peer0.orgcpp.test.com/tls/server.key
        - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orgcpp.test.com/peers/peer0.orgcpp.test.com/tls/ca.crt
        - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orgcpp.test.com/users/Admin@orgcpp.test.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/
          - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
      depends_on:   # 启动顺序
        - peer0.orgcpp.test.com
      
      networks:
          default:
            aliases:
              - testwork
      extra_hosts:
        - "orderer.test.com:192.168.247.129"
        - "peer0.orggo.test.com:192.168.247.141"
        - "peer0.orgcpp.test.com:192.168.247.131"
注意: 该配置文件中已经将` ` 映射删掉了

7.4.3 启动当前节点

  • 启动客户端容器

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    $ docker-compose up -d
    Creating network "testwork_default" with the default driver
    Creating peer0.orgcpp.test.com ... done
    Creating cli                   ... done
    # 查看启动情况
    $ docker-compose ps
            Name                Command       State                       Ports                     
    ------------------------------------------------------------------------------------------------
    cli                     /bin/bash         Up                                                    
    peer0.orgcpp.test.com   peer node start   Up      0.0.0.0:7051->7051/tcp, 0.0.0.0:7053->7053/tcp

7.4.4 对peer0.orgcpp节点的操作

  • 进入到操作该节点的客户端中

    1
    $ docker exec -it cli bash

  • 加入到通道中

    1
    $ peer channel join -b ./channel-artifacts/testchannel.block

  • 安装链码

    1
    $ peer chaincode install -n testcc -v 1.0 -l golang -p github.com/chaincode

  • 查询

    1
    2
    $ peer chaincode query -C testchannel -n testcc -c '{"Args":["query","a"]}' 
    $ peer chaincode query -C testchannel -n testcc -c '{"Args":["query","b"]}'

  • 交易

    1
    2
    3
    4
    5
    # 转账
    $ peer chaincode invoke -o orderer.test.com:7050  -C testchannel -n testcc --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/test.com/orderers/orderer.test.com/msp/tlscacerts/tlsca.test.com-cert.pem --peerAddresses peer0.orgGo.test.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orgGo.test.com/peers/peer0.orgGo.test.com/tls/ca.crt --peerAddresses peer0.orgcpp.test.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/orgcpp.test.com/peers/peer0.orgcpp.test.com/tls/ca.crt -c '{"Args":["invoke","a","b","10"]}'
    # 查询
    $ peer chaincode query -C testchannel -n testcc -c '{"Args":["query","a"]}' 
    $ peer chaincode query -C testchannel -n testcc -c '{"Args":["query","b"]}'

7.5. 其余节点的部署

关于其余节点的部署, 在此不再过多赘述, 部署方式请参考 第 7.4节内容, 步骤是完全一样的

7.6. 链码的打包

我们在进行多机多节点部署的时候, 所有的peer节点都需要安装链码, 有时候会出现链码安装失败的问题, 提示链码的指纹（哈希）不匹配，我们可以通过以下方法解决

  1. 通过客户端在第1个peer节点中安装好链码之后， 将链码打包

    1
    2
    3
    4
    5
    $ peer chaincode package -n testcc -p github.com/chaincode -v 1.0 mycc.1.0.out
    	-n: 链码的名字
    	-p: 链码的路径
    	-v: 链码的版本号
    	-mycc.1.0.out: 打包之后生成的文件

  2. 将打包之后的链码从容器中拷贝出来

    1
    $ docker cp cli:/xxxx/mycc.1.0.out ./

  3. 将得到的打包之后的链码文件拷贝到其他的peer节点上

  4. 通过客户端在其他peer节点上安装链码

    1
    $ peer chaincode install mycc.1.0.out
-------------本文结束感谢您的阅读-------------

本文标题:kafka多机多节点部署

文章作者:Wuman

发布时间:2019年01月19日 - 20:01

最后更新:2019年01月19日 - 20:01

原始链接:http://yoursite.com/2019/01/19/kafka多机多节点部署/

许可协议: 署名-非商业性使用-禁止演绎 4.0 国际 转载请保留原文链接及作者。