如何在 Kubernetes 设置中使用 Hyperledger Caliper 测量 Hyperledger Fabric 性能

问题描述

我的结构网络部署在本地 Kubernetes 集群(vagrant)中,使用以下命令 https://medium.com/swlh/how-to-implement-hyperledger-fabric-external-chaincodes-within-a-kubernetes-cluster-fd01d7544523 教程。 Pod 已启动并正在运行,我能够从 fabric-cli 插入/读取弹珠。

我无法配置 caliper 来衡量我的部署性能。我在同一个“hyperledger”命名空间中运行了 caliper 0.4.2 docker 镜像。

caliper 部署 yaml 文件

apiVersion: apps/v1
kind: Deployment
Metadata:
  labels:
    app: caliper
  name: caliper
  namespace: hyperledger
spec:
  selector:
    matchLabels:
      app: caliper
  replicas: 1
  strategy:
    type: Recreate
  template:
    Metadata:
      labels:
        app: caliper
    spec:
      containers:
        - env:
            - name: CALIPER_BIND_SUT
              value: fabric:2.2
            - name: CALIPER_BENCHCONfig
              value: benchmarks/myAssetBenchmark.yaml
            - name: CALIPER_NETWORKCONfig
              value: networks/networkConfig3.yaml
            - name: CALIPER_FABRIC_GATEWAY_ENABLED
              value: "true"
            - name: CALIPER_FLOW_ONLY_TEST
              value: "true"
          image: hyperledger/caliper:0.4.2
          name: caliper
          command:
            - caliper
          args:
            - launch
            - manager
          tty: true
          volumeMounts:
            - mountPath: /hyperledger/caliper/workspace
              name: caliper-workspace
            - mountPath: /hyperledger/caliper/fabric-samples
              name: fabric-workspace
          workingDir: /hyperledger/caliper/workspace
      restartPolicy: Always
      volumes:
        - name: caliper-workspace
          hostPath:
            path: /home/vagrant/caliper-workspace
            type: Directory
        - name: fabric-workspace
          hostPath:
            path: /home/vagrant/fabr          volumeMounts:
            - mountPath: /hyperledger/caliper/workspace
              name: caliper-workspace
            - mountPath: /hyperledger/caliper/fabric-samples
              name: fabric-workspace
          workingDir: /hyperledger/caliper/workspace
      restartPolicy: Always
      volumes:
        - name: caliper-workspace
          hostPath:
            path: /home/vagrant/caliper-workspace
            type: Directory
        - name: fabric-workspace
          hostPath:
            path: /home/vagrant/fabric-external-chaincodes/
            type: Directoryic-external-chaincodes/
            type: Directory

我遵循了 https://hyperledger.github.io/caliper/v0.4.2/fabric-tutorial/tutorials-fabric-existing/ 有关在现有结构网络旁边运行 caliper 的文档。 networkconfig3.yaml 文件

name: Fabric
version: '2.0.0'
mutual-tls: true

caliper:
  blockchain: fabric
  sutoptions:
    mutualTls: true 

channels:
  - channelName: mychannel
    contracts:
    - id: marbles

organizations:
  - mspid: org1MSP
    identities:
      certificates:
      - name: 'Admin'
        admin: true
        clientPrivateKey:
          path: '../fabric-samples/crypto-config/peerOrganizations/org1/users/Admin@org1/msp/keystore/priv_sk'
        clientSignedCert:
          path: '../fabric-samples/crypto-config/peerOrganizations/org1/users/Admin@org1/msp/signcerts/Admin@org1-cert.pem'
      - name: 'User1'
        clientPrivateKey:
          path: '../fabric-samples/crypto-config/peerOrganizations/org1/users/User1@org1/msp/keystore/priv_sk'
        clientSignedCert:
          path: '../fabric-samples/crypto-config/peerOrganizations/org1/users/User1@org1/msp/signcerts/User1@org1-cert.pem'
    connectionProfile:
      path: 'networks/profile-org1.yaml'
      discover: true

org1 连接配置文件看起来像

name: Fabric
version: '1.0.0'

client:
  organization: org1
  connection:
    timeout:
      peer:
        endorser: '300'

organizations:
  org1:
    mspid: org1MSP
    peers:
    - peer0-org1

peers:
  peer0-org1:
    url: grpcs://peer0-org1:7051
    grpcoptions:
      ssl-target-name-override: peer0-org1
      grpc.keepalive_time_ms: 600000
    tlsCACerts:
      path: ../fabric-samples/crypto-config/peerOrganizations/org1/peers/peer0-org1/msp/tlscacerts/tlsca.org1-cert.pem

myAssetBenchmark.yaml 文件

test:
    name: marble-benchmark
    description: test benchmark
    workers:
      type: local
      number: 2
    rounds:
    - label: initMarble
      description: init marbles benchmark
      txnumber: 100
      rateControl:
        type: fixed-load
        opts:
          tps: 25
      workload:
        module: workload/init.js
monitor:
  type:
  - none

observer:
  type: local
  interval: 1

卡尺失败,因为与对等方的连接未通过。 2021-01-05T04:37:55.592Z - ^[[32minfo^[[39m: [NetworkConfig]: buildPeer - Unable to connect to the endorser peer0-org1 due to Error: Failed to connect before the deadline on Endorser- name: peer0-org1,url:grpcs://peer0-org1:7051,connected:false,connectAttempted:true

更多错误日志

2021-01-04T01:08:35.466Z - error: [discoveryService]: send[mychannel] - no discovery results
2021-01-04T01:08:38.473Z - error: [ServiceEndpoint]: Error: Failed to connect before the deadline on discoverer- name: peer0-org1,connectAttempted:true
2021-01-04T01:08:38.473Z - error: [ServiceEndpoint]: waitForReady - Failed to connect to remote gRPC server peer0-org1 url:grpcs://peer0-org1:7051 timeout:3000
2021-01-04T01:08:38.473Z - error: [ServiceEndpoint]: ServiceEndpoint grpcs://peer0-org1:7051 reset connection Failed :: Error: Failed to connect before the deadline on discoverer- name: peer0-org1,connectAttempted:true

我当前的配置有什么问题? 有没有什么博客或文档可以看更多?

解决方法

您的连接配置文件看起来不正确,因为您没有正确指定 tlsCACert 信息。由于您需要使用适用于节点 2.2 的连接配置文件,因此以下内容可能有效

name: Fabric

organizations:
  org1:
    mspid: org1MSP
    peers:
    - peer0-org1

peers:
  peer0-org1:
    url: grpcs://peer0-org1:7051
    tlsCACerts:
      path: ../fabric-samples/crypto-config/peerOrganizations/org1/peers/peer0-org1/msp/tlscacerts/tlsca.org1-cert.pem

这里有一些关于连接配置文件的 node sdk 2.2 预期格式的详细信息,但我不确定它们有多正确https://hyperledger.github.io/fabric-sdk-node/release-2.2/tutorial-commonconnectionprofile.html

相关问答

Selenium Web驱动程序和Java。元素在(x,y)点处不可单击。其...
Python-如何使用点“。” 访问字典成员?
Java 字符串是不可变的。到底是什么意思?
Java中的“ final”关键字如何工作?(我仍然可以修改对象。...
“loop:”在Java代码中。这是什么,为什么要编译?
java.lang.ClassNotFoundException:sun.jdbc.odbc.JdbcOdbc...