Hyperledger Fabric SDK Go構(gòu)建第一個應(yīng)用

寫在前面：
本文內(nèi)容翻譯自:https://chainhero.io/2018/03/tutorial-build-blockchain-app-2/ ，文檔中的命令操作均在實際環(huán)境進(jìn)行驗證，現(xiàn)將成果分享給大家。

目錄

一.概述

二.安裝環(huán)境

三.安裝Fabric SDK Go

四.啟動區(qū)塊鏈網(wǎng)絡(luò)

五.使用Fabric SDK Go

一. 概述

首先，為新入門的開發(fā)小白普及一下何為SDK

軟件開發(fā)工具包（外語首字母縮寫：SDK、外語全稱：Software Development Kit）一般都是一些軟件工程師為特定的軟件包、軟件框架、硬件平臺、操作系統(tǒng)等建立應(yīng)用軟件時的開發(fā)工具的集合。軟件開發(fā)工具包括廣義上指輔助開發(fā)某一類軟件的相關(guān)文檔、范例和工具的集合。軟件開發(fā)工具包是一些被軟件工程師用于為特定的軟件包、軟件框架、硬件平臺、操作系統(tǒng)等創(chuàng)建應(yīng)用軟件的開發(fā)工具的集合，一般而言SDK即開發(fā) Windows 平臺下的應(yīng)用程序所使用的 SDK。它可以簡單的為某個程序設(shè)計語言提供應(yīng)用程序接口 API 的一些文件，但也可能包括能與某種嵌入式系統(tǒng)通訊的復(fù)雜的硬件。一般的工具包括用于調(diào)試和其他用途的實用工具。SDK 還經(jīng)常包括示例代碼、支持性的技術(shù)注解或者其他的為基本參考資料澄清疑點的支持文檔。為了鼓勵開發(fā)者使用其系統(tǒng)或者語言，許多 SDK 是免費提供的。

Farbric的Peer節(jié)點和Orderer節(jié)點都提供了基于GRPC協(xié)議(Google開發(fā)的遠(yuǎn)程過程調(diào)用RPC)的接口，通過這些接口可以和Peer節(jié)點與Orderer節(jié)點進(jìn)行命令/數(shù)據(jù)交互，為了簡化開發(fā)，官方提供了多語言版本的SDK，官網(wǎng)原文

Hyperledger Fabric SDKs
Hyperledger Fabric intends to offer a number of SDKs for a wide variety of programming languages. The first two delivered are the Node.js and Java SDKs. We hope to provide Python, REST and Go SDKs in a subsequent release.

Hyperledger Fabric Node SDK documentation.
Hyperledger Fabric Java SDK documentation.

實際上目前主流支持的已經(jīng)有Go版本了，列出主流的三個：

• Fabric Nodejs SDK
• Fabric Java SDK
• Fabric Go SDK

考慮到Golang是Fabric原生的開發(fā)語言，F(xiàn)abric，F(xiàn)abric-ca,Chaincode都是采用Golang開發(fā)的，所以本文還是圍繞Golang版本的Fabric SDK進(jìn)行闡述SDK的安裝部署與測試。

二.安裝環(huán)境

在Ubuntu 16.04上發(fā)布，但Hyperledger Fabric架構(gòu)與Mac OS X，Windows和其他Linux發(fā)行版兼容。Hyperledger Fabric使用Docker輕松部署區(qū)塊鏈網(wǎng)絡(luò)。 另外，一些組件（同級）也部署docker容器來分離數(shù)據(jù)（通道）。 所以請確保所使用的平臺支持這種虛擬化。

1. 查看Docker版本

需要Docker版本17.03.0-ce或更高版本。

$docker -v

返回結(jié)果

Docker version 17.12.1-ce, build 7390fc6

2. 查看Docker-Compose版本

   $docker-compose version

返回結(jié)果

docker-compose version 1.17.1, build unknown
docker-py version: 2.5.1
CPython version: 2.7.15rc1
OpenSSL version: OpenSSL 1.1.0g  2 Nov 2017

3. 查看Golang版本

需要版本1.9.x或更高版本

$go version

返回結(jié)果

go version go1.10.3 linux/amd64

查看GOPATH,GOROOT,GOBIN環(huán)境變量

$ go env |egrep 'GOROOT|GOPATH|GOBIN'

返回結(jié)果

GOBIN="/home/bruce/go/bin"
GOPATH="/home/bruce/go"
GOROOT="/usr/local/go"

三.安裝Fabric SDK Go

1. 安裝依賴包

   $ sudo apt update
   $ sudo apt install libltdl-dev

2. 安裝SDK

(1) 下載軟件包

$ go get -u github.com/hyperledger/fabric-sdk-go 

(2) 安裝依賴包

$ cd $GOPATH/src/github.com/hyperledger/fabric-sdk-go 
$ chmod +x test/scripts/*.sh # make depend-install操作會調(diào)用dependencies.sh腳本
$ make depend //注意1.1.0版本是make depend-install

以上命令會下載如下依賴包并安裝至$GOBIN目錄下

github.com/axw/gocov/...
github.com/AlekSi/gocov-xml
github.com/client9/misspell/cmd/misspell
github.com/golang/lint/golint
golang.org/x/tools/cmd/goimports
github.com/golang/mock/mockgen

安裝完成后檢查$GOBIN目錄下文件

-rwxrwxr-x 1 bruce bruce 13128127 Jul 19 17:38 dep
-rwxrwxr-x 1 bruce bruce  4332114 Jul 19 17:50 gocov
-rwxrwxr-x 1 bruce bruce  2752093 Jul 19 17:50 gocov-xml
-rwxrwxr-x 1 bruce bruce  5220554 Jul 19 17:50 goimports
-rwxrwxr-x 1 bruce bruce  5669065 Jul 19 17:50 golint
-rwxrwxr-x 1 bruce bruce  9470763 Jul 19 17:50 misspell
-rwxrwxr-x 1 bruce bruce  5070526 Jul 19 17:51 mockgen

(3) 安裝vendor

$ make populate

返回結(jié)果

Populate script last ran 07-21-2018 on revision e230c04e with Gopkg.lock revision d489eba9
Populating vendor ...
Populating dockerd vendor ...
Cloning into 'scripts/_go/src/chaincoded/vendor/github.com/hyperledger/fabric'...
remote: Counting objects: 4530, done.
remote: Compressing objects: 100% (3778/3778), done.
remote: Total 4530 (delta 543), reused 2596 (delta 376), pack-reused 0
Receiving objects: 100% (4530/4530), 16.51 MiB | 120.00 KiB/s, done.
Resolving deltas: 100% (543/543), done.

四.啟動區(qū)塊鏈網(wǎng)絡(luò)

1. 準(zhǔn)備環(huán)境

為了構(gòu)建區(qū)塊鏈網(wǎng)絡(luò)，使用docker構(gòu)建處理不同角色的虛擬計算機。 在這里我們將盡可能保持簡單。 Hyperledger Fabric需要大量證書來確保在整個端到端流程（TSL，身份驗證，簽名塊......）期間進(jìn)行加密。 創(chuàng)建這些文件需要一點時間，為了直接了解問題的核心，我們已經(jīng)在此存儲庫的文件夾中為您準(zhǔn)備了所有相關(guān)內(nèi)容。

在GOPATH的src文件夾中新建一個目錄如下：

$ mkdir -p $GOPATH/src/github.com/ticket
$ cd $GOPATH/src/github.com/ticket

新建fixtures文件夾

$ mkdir fixtures

將 channel-artifacts 及 crypto-config 兩個文件夾復(fù)制到 fixture 目錄中

$ cd fixtures
$ sudo cp -r ~/hyfa/fabric-samples/first-network/channel-artifacts .
$ sudo cp -r ~/hyfa/fabric-samples/first-network/crypto-config .

將 channel-artifacts 文件夾名稱修改為 artifacts

$ mv channel-artifacts/ artifacts

移除無用的文件

$ sudo rm -f artifacts/.gitkeep

2. 修改配置

將 fabric-samples/basic-network/docker-compose.yml 文件復(fù)制至當(dāng)前的 fixtures 目錄下, 進(jìn)行編輯

$ sudo cp ~/hyfa/fabric-samples/basic-network/docker-compose.yml ./
$ sudo vim docker-compose.yml

(1) 修改網(wǎng)絡(luò)模式

version: '2'

networks:
  default:

(2) orderer部分

services:
 orderer.example.com:
    container_name: orderer.example.com
    image: hyperledger/fabric-orderer
    environment:
      - ORDERER_GENERAL_LOGLEVEL=debug
      - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
      - 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_LISTENPORT=7050
      # 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, /var/hyperledger/peerOrg1/tls/ca.crt, /var/hyperledger/peerOrg2/tls/ca.crt]
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric
    command: orderer
    ports:
      - 7050:7050
    volumes:
      - ./artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block
      - ./crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/msp:/var/hyperledger/orderer/msp
      - ./crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls:/var/hyperledger/orderer/tls
      - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/:/var/hyperledger/peerOrg1
      - ./crypto-config/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/:/var/hyperledger/peerOrg2
    networks:
      default:
        aliases:
          - orderer.example.com

(3) ca配置

  ca.org1.example.com:
    image: hyperledger/fabric-ca
    environment:
      - FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server
      - FABRIC_CA_SERVER_CA_NAME=ca.org1.example.com
      - FABRIC_CA_SERVER_CA_CERTFILE=/etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem
      - FABRIC_CA_SERVER_CA_KEYFILE=/etc/hyperledger/fabric-ca-server-config/b4a9a9585aebe52646e1987d4eca4a0ecf3f0ab688ca7924c07249c0303553ba_sk
      - FABRIC_CA_SERVER_TLS_ENABLED=true
      - 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/b4a9a9585aebe52646e1987d4eca4a0ecf3f0ab688ca7924c07249c0303553ba_sk
    ports:
      - "7054:7054"
    command: sh -c 'fabric-ca-server start -b admin:adminpw -d'
    volumes:
      - ./crypto-config/peerOrganizations/org1.example.com/ca/:/etc/hyperledger/fabric-ca-server-config
    container_name: ca.org1.example.com
    networks:
      default:
        aliases:
          - ca.org1.example.com

注意:

FABRIC_CA_SERVER_CA_KEYFILE與FABRIC_CA_SERVER_TLS_KEYFILE的參數(shù)值需要設(shè)置成

...fixtures/crypto-config/peerOrganizations/org1.example.com/ca目錄下面的私鑰文件,否則會啟動失敗，報錯證書與秘鑰不匹配。

(4) Peer配置

• peer0.org1.example.com 內(nèi)容如下

  peer0.org1.example.com:
  image: hyperledger/fabric-peer
  container_name: peer0.org1.example.com
  environment:

  • CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
  • CORE_VM_DOCKER_ATTACHSTDOUT=true
  • CORE_LOGGING_LEVEL=DEBUG
  • CORE_PEER_NETWORKID=bill
  • CORE_PEER_PROFILE_ENABLED=true
  • CORE_PEER_TLS_ENABLED=true
  • CORE_PEER_TLS_CERT_FILE=/var/hyperledger/tls/server.crt
  • CORE_PEER_TLS_KEY_FILE=/var/hyperledger/tls/server.key
  • CORE_PEER_TLS_ROOTCERT_FILE=/var/hyperledger/tls/ca.crt
  • CORE_PEER_ID=peer0.org1.example.com
  • CORE_PEER_ADDRESSAUTODETECT=true
  • CORE_PEER_ADDRESS=peer0.org1.example.com:7051
  • CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.example.com:7051
  • CORE_PEER_GOSSIP_USELEADERELECTION=true
  • CORE_PEER_GOSSIP_ORGLEADER=false
  • CORE_PEER_GOSSIP_SKIPHANDSHAKE=true
  • CORE_PEER_LOCALMSPID=Org1MSP
  • CORE_PEER_MSPCONFIGPATH=/var/hyperledger/msp
  • CORE_PEER_TLS_SERVERHOSTOVERRIDE=peer0.org1.example.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.example.com/peers/peer0.org1.example.com/msp:/var/hyperledger/msp
  • ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls:/var/hyperledger/tls
    ports:
  • 7051:7051
  • 7053:7053
    depends_on:
  • orderer.example.com
    links:
  • orderer.example.com
    networks:
    default:
    aliases:
    • peer0.org1.example.com

• peer1.org1.example.com內(nèi)容如下

  peer1.org1.example.com:
  image: hyperledger/fabric-peer
  container_name: peer1.org1.example.com
  environment:

  • CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
  • CORE_VM_DOCKER_ATTACHSTDOUT=true
  • CORE_LOGGING_LEVEL=DEBUG
  • CORE_PEER_NETWORKID=bill
  • CORE_PEER_PROFILE_ENABLED=true
  • CORE_PEER_TLS_ENABLED=true
  • CORE_PEER_TLS_CERT_FILE=/var/hyperledger/tls/server.crt
  • CORE_PEER_TLS_KEY_FILE=/var/hyperledger/tls/server.key
  • CORE_PEER_TLS_ROOTCERT_FILE=/var/hyperledger/tls/ca.crt
  • CORE_PEER_ID=peer1.org1.example.com
  • CORE_PEER_ADDRESSAUTODETECT=true
  • CORE_PEER_ADDRESS=peer1.org1.example.com:7051
  • CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org1.example.com:7051
  • CORE_PEER_GOSSIP_USELEADERELECTION=true
  • CORE_PEER_GOSSIP_ORGLEADER=false
  • CORE_PEER_GOSSIP_SKIPHANDSHAKE=true
  • CORE_PEER_LOCALMSPID=Org1MSP
  • CORE_PEER_MSPCONFIGPATH=/var/hyperledger/msp
  • CORE_PEER_TLS_SERVERHOSTOVERRIDE=peer1.org1.example.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.example.com/peers/peer1.org1.example.com/msp:/var/hyperledger/msp
  • ./crypto-config/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/tls:/var/hyperledger/tls
    ports:
  • 8051:7051
  • 8053:7053
    depends_on:
  • orderer.example.com
    links:
  • orderer.example.com
    networks:
    default:
    aliases:
    • peer1.org1.example.com

暫時只需要如上功能模塊即可

將 fixtures 文件的所屬修改為當(dāng)前用戶及組

$ sudo chown -R bruce:bruce ../fixtures

3. 啟動網(wǎng)絡(luò)

為了檢查網(wǎng)絡(luò)是否正常工作，使用docker-compose同時啟動或停止所有容器。 進(jìn)入fixtures文件夾，運行：

$ cd $GOPATH/src/github.com/kongyixueyuan.com/bill/fixtures
$ docker-compose up

啟動完畢，將看到：兩個peer，orderer和一個CA容器。 代表已成功創(chuàng)建了一個新的網(wǎng)絡(luò)，可以隨SDK一起使用。 要停止網(wǎng)絡(luò)，請返回到上一個終端，按Ctrl+C并等待所有容器都停止。

CONTAINER ID        IMAGE                        COMMAND                  CREATED             STATUS              PORTS                                            NAMES
932b5364664f        hyperledger/fabric-peer      "peer node start"        26 hours ago        Up 26 hours         0.0.0.0:7051->7051/tcp, 0.0.0.0:7053->7053/tcp   peer0.org1.example.com
cf9385a5e1ae        hyperledger/fabric-peer      "peer node start"        26 hours ago        Up 26 hours         0.0.0.0:8051->7051/tcp, 0.0.0.0:8053->7053/tcp   peer1.org1.example.com
a1cd2a83af57        hyperledger/fabric-orderer   "orderer"                26 hours ago        Up 26 hours         0.0.0.0:7050->7050/tcp                           orderer.example.com
6a9a54d9d82b        hyperledger/fabric-ca        "/bin/sh -c 'fabric-…"   26 hours ago        Up 26 hours         0.0.0.0:7054->7054/tcp                           ca.org1.example.com

提示 ：當(dāng)網(wǎng)絡(luò)停止時，所有使用的容器都可以訪問。 例如，這對檢查日志非常有用。 可以用docker ps -a來看它們。 為了清理這些容器，需要使用docker rm $(docker ps -aq)將其刪除，或者如果使用了docker-compose文件，請轉(zhuǎn)至此文件的位置并運行docker-compose down 。

提示 ：可以在后臺運行docker-compose命令以保持提示。 為此，請使用參數(shù)-d ，如下所示： docker-compose up -d 。 要停止容器，請在docker-compose.yaml所在的文件夾中運行命令： docker-compose stop （或docker-compose down進(jìn)行清理停止所有容器）。

五.使用Fabric SDK Go

1.創(chuàng)建配置文件

$ cd $GOPATH/src/github.com/ticket
$ vim config.yaml

配置文件內(nèi)容如下：

name: "ticket-network"

# Describe what the target network is/does.
description: "The network which will host my first blockchain"

# Schema version of the content. Used by the SDK to apply the corresponding parsing rules.
version: 2

# The client section used by GO SDK.
client:
  # Which organization does this application instance belong to? The value must be the name of an org
  organization: Org1
  logging:
    level: info

  # Global configuration for peer, event service and orderer timeouts
  peer:
    timeout:
      connection: 3s
      queryResponse: 45s
      executeTxResponse: 30s
  eventService:
    timeout:
      connection: 3s
      registrationResponse: 3s
  orderer:
    timeout:
      connection: 3s
      response: 5s

  # Root of the MSP directories with keys and certs. The Membership Service Providers is component that aims to offer an abstraction of a membership operation architecture.
  cryptoconfig:
    path: "${GOPATH}/src/github.com/kongyixueyuan.com/bill/fixtures/crypto-config"

  # Some SDKs support pluggable KV stores, the properties under "credentialStore" are implementation specific
  credentialStore:
    path: "/tmp/bill-kvs"

     # [Optional]. Specific to the CryptoSuite implementation used by GO SDK. Software-based implementations requiring a key store. PKCS#11 based implementations does not.
    cryptoStore:
      path: "/tmp/bill-msp"

  # BCCSP config for the client. Used by GO SDK. It's the Blockchain Cryptographic Service Provider.
  # It offers the implementation of cryptographic standards and algorithms.
  BCCSP:
    security:
     enabled: true
     default:
      provider: "SW"
     hashAlgorithm: "SHA2"
     softVerify: true
     ephemeral: false
     level: 256

  tlsCerts:
    systemCertPool: false

# [Optional]. But most apps would have this section so that channel objects can be constructed based on the content below.
# If one of your application is creating channels, you might not use this
channels:
  mychannel:
    orderers:
      - orderer.example.com

    # Network entity which maintains a ledger and runs chaincode containers in order to perform operations to the ledger. Peers are owned and maintained by members.
    peers:
      peer0.org1.example.com:
        # [Optional]. will this peer be sent transaction proposals for endorsement? The peer must
        # have the chaincode installed. The app can also use this property to decide which peers
        # to send the chaincode install request. Default: true
        endorsingPeer: true

        # [Optional]. will this peer be sent query proposals? The peer must have the chaincode
        # installed. The app can also use this property to decide which peers to send the
        # chaincode install request. Default: true
        chaincodeQuery: true

        # [Optional]. will this peer be sent query proposals that do not require chaincodes, like
        # queryBlock(), queryTransaction(), etc. Default: true
        ledgerQuery: true

        # [Optional]. will this peer be the target of the SDK's listener registration? All peers can
        # produce events but the app typically only needs to connect to one to listen to events.
        # Default: true
        eventSource: true

      peer1.org1.example.com:

# List of participating organizations in this network
organizations:
  Org1:
    mspid: Org1MSP
    cryptoPath: "peerOrganizations/org1.example.com/users/{userName}@org1.example.com/msp"
    peers:
      - peer0.org1.example.com
      - peer1.org1.example.com
    certificateAuthorities:
      - ca.org1.example.com

# List of orderers to send transaction and channel create/update requests to.
# The orderers consent on the order of transactions in a block to be committed to the ledger. For the time being only one orderer is needed.
orderers:
  orderer.example.com:
    url: grpcs://localhost:7050
    grpcOptions:
      ssl-target-name-override: orderer.example.com
      grpc-max-send-message-length: 15
    tlsCACerts:
      path: "${GOPATH}/src/github.com/ticket/fixtures/crypto-config/ordererOrganizations/example.com/tlsca/tlsca.example.com-cert.pem"

# List of peers to send various requests to, including endorsement, query and event listener registration.
peers:
  peer0.org1.example.com:
    # this URL is used to send endorsement and query requests
    url: grpcs://localhost:7051
    # this URL is used to connect the EventHub and registering event listeners
    eventUrl: grpcs://localhost:7053
    # These parameters should be set in coordination with the keepalive policy on the server
    grpcOptions:
      ssl-target-name-override: peer0.org1.example.com
      grpc.http2.keepalive_time: 15

    tlsCACerts:
      path: "${GOPATH}/src/github.com/ticket/fixtures/crypto-config/peerOrganizations/org1.example.com/tlsca/tlsca.org1.example.com-cert.pem"

  peer1.org1.example.com:
    url: grpcs://localhost:8051
    eventUrl: grpcs://localhost:8053
    grpcOptions:
      ssl-target-name-override: peer1.org1.example.com
      grpc.http2.keepalive_time: 15
    tlsCACerts:
      # Certificate location absolute path
      path: "${GOPATH}/src/github.com/ticket/fixtures/crypto-config/peerOrganizations/org1.example.com/tlsca/tlsca.org1.example.com-cert.pem"

# Fabric-CA is a special kind of Certificate Authority provided by Hyperledger Fabric which allows certificate management to be done via REST APIs.
certificateAuthorities:
  ca.org1.example.com:
    url: https://localhost:7054
    # the properties specified under this object are passed to the 'http' client verbatim when making the request to the Fabric-CA server
    httpOptions:
      verify: false
    registrar:
      enrollId: admin
      enrollSecret: adminpw
    caName: ca.org1.example.com

以上配置文件模板可以通過config.yaml獲取

2. 編寫初始化代碼

創(chuàng)建一個blockchain的新文件夾，其中將包含與區(qū)塊鏈網(wǎng)絡(luò)通訊的所有接口。

$ mkdir blockchain
$ vim blockchain/setup.go

代碼如下

package blockchain

import (
    "github.com/hyperledger/fabric-sdk-go/api/apitxn/resmgmtclient"
    "github.com/hyperledger/fabric-sdk-go/pkg/fabsdk"
    "github.com/hyperledger/fabric-sdk-go/pkg/config"
    "fmt"
    "github.com/hyperledger/fabric-sdk-go/api/apitxn/chmgmtclient"
    "time"
)

//定義結(jié)構(gòu)體
type FabricSetup struct {
    ConfigFile    string                           //sdk配置文件所在路徑
    ChannelID     string                           //應(yīng)用通道名稱
    ChannelConfig string                           //應(yīng)用通道交易配置文件所在路徑
    OrgAdmin      string                           // 組織管理員名稱
    OrgName       string                           //組織名稱
    Initialized   bool                             //是否初始化
    Admin         resmgmtclient.ResourceMgmtClient //fabric環(huán)境中資源管理者
    SDK           *fabsdk.FabricSDK                //SDK實例
}

//1. 創(chuàng)建SDK實例并使用SDK實例創(chuàng)建應(yīng)用通道，將Peer節(jié)點加入到創(chuàng)建的應(yīng)用通道中
func (f *FabricSetup) Initialize() error {
    //判斷是否已經(jīng)初始化
    if f.Initialized {
        return fmt.Errorf("SDK已被實例化")
    }

    //創(chuàng)建SDK對象
    sdk, err := fabsdk.New(config.FromFile(f.ConfigFile))

    if err != nil {
        return fmt.Errorf("SDK實例化失敗:%v", err)
    }
    f.SDK = sdk
    //創(chuàng)建一個具有管理權(quán)限的應(yīng)用通道客戶端管理對象
    chmClient, err := f.SDK.NewClient(fabsdk.WithUser(f.OrgAdmin), fabsdk.WithOrg(f.OrgName)).ChannelMgmt()
    if err != nil {
        return fmt.Errorf("創(chuàng)建應(yīng)用通道管理客戶端管理對象失敗,%v", err)
    }
    //獲取當(dāng)前的會話用戶對象
    session, err := f.SDK.NewClient(fabsdk.WithUser(f.OrgAdmin), fabsdk.WithOrg(f.OrgName)).Session()
    if err != nil {
        return fmt.Errorf("獲取當(dāng)前會話用戶對象失敗%v", err)
    }

    orgAdminUser := session
    //指定創(chuàng)建應(yīng)用通道所需要的所有參數(shù)
    /*
    $ peer channel create -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/channel.tx --tls --cafile \
    /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
     */
    chReq := chmgmtclient.SaveChannelRequest{ChannelID: f.ChannelID, ChannelConfig: f.ChannelConfig, SigningIdentity: orgAdminUser}

    //創(chuàng)建應(yīng)用通道

    err = chmClient.SaveChannel(chReq)
    if err != nil {
        return fmt.Errorf("創(chuàng)建應(yīng)用通道失敗:%v", err)
    }

    time.Sleep(time.Second * 5)

    //創(chuàng)建一個管理資源的客戶端對象
    f.Admin, err = f.SDK.NewClient(fabsdk.WithUser(f.OrgAdmin)).ResourceMgmt()
    if err != nil {
        return fmt.Errorf("創(chuàng)建資源管理對象失敗:%v", err)
    }
    //將peer 節(jié)點加入到應(yīng)用通道中
    err = f.Admin.JoinChannel(f.ChannelID)
    if err != nil {
        return fmt.Errorf("peer加入節(jié)點失敗:%v", err)
    }

    f.Initialized = true
    fmt.Println("SDK實例化成功")

    return nil

}

該測試代碼可以從blockchain/setup.go獲取

在這個階段

• 初始化一個客戶端，它將與 peer，CA 和 orderer進(jìn)行通信。

• 創(chuàng)建了一個新通道, 并將Peer節(jié)點加入到此通道中

3. 編寫測試代碼

為了確?？蛻舳四軌虺跏蓟薪M件，將在啟動網(wǎng)絡(luò)的情況下進(jìn)行簡單的測試。 為了做到這一點，我們需要構(gòu)建主程序代碼進(jìn)行功能調(diào)用

$ vim main.go

package main

import (
    "FabricDev/ticket/blockchain"
    "os"
    "fmt"
)

func main() {

    fsetup := blockchain.FabricSetup{
        ConfigFile:    "config.yaml",
        ChannelID:     "mychannel",
        ChannelConfig: os.Getenv("GOPATH") + "src/github.com/ticket/fixtures/artifacts/channel.tx",
        OrgAdmin:      "Admin",
        OrgName:       "Org1",
    }

    err := fsetup.Initialize()

    if err != nil {
        fmt.Errorf("Fabric SDK初始化失敗:%v", err)
        fmt.Println(err.Error())
    }

}

代碼模板:main.go

4. 打包依賴關(guān)系

在開始編譯之前，最后一件事是使用一個vendor目錄來包含我們所有的依賴關(guān)系。 在我們的GOPATH中，我們有Fabric SDK Go和其他項目。 當(dāng)嘗試編譯應(yīng)用程序時，Golang會在GOPATH中搜索依賴項，但首先會檢查項目中是否存在vendor文件夾。 如果依賴性得到滿足，那么Golang就不會去看GOPATH或GOROOT。 這在使用幾個不同版本的依賴關(guān)系時非常有用（可能會發(fā)生一些沖突，比如在例子中有多個BCCSP定義，通過使用像dep這樣的工具來處理這些依賴關(guān)系在vendor目錄中。

$ vim Gopkg.toml

配置文件內(nèi)容

[[constraint]]
  name = "github.com/hyperledger/fabric"
  revision = "014d6befcf67f3787bb3d67ff34e1a98dc6aec5f"

[[constraint]]
  name = "github.com/hyperledger/fabric-sdk-go"
  revision = "614551a752802488988921a730b172dada7def1d"

這是dep一個限制，以便在 vendor 中指定希望SDK轉(zhuǎn)到特定版本。

保存該文件，然后執(zhí)行此命令將vendor目錄與項目的依賴關(guān)系同步：

$ dep ensure

$ls vendor -l //查看vendor目錄內(nèi)容

drwxrwxr-x 13 bruce bruce 4096 Jul 20 14:06 github.com
drwxrwxr-x  3 bruce bruce 4096 Jul 20 14:06 golang.org
drwxrwxr-x  4 bruce bruce 4096 Jul 20 14:06 google.golang.org
drwxrwxr-x  3 bruce bruce 4096 Jul 20 14:06 gopkg.in

5.構(gòu)建代碼

$go build //構(gòu)建代碼生成ticket可執(zhí)行文件
$ls ticket -l
-rwxrwxr-x 1 bruce bruce 19784971 Jul 20 14:06 ticket

6.執(zhí)行命令

$ ./ticket 

[fabric_sdk_go] 2018/07/21 09:19:23 UTC - config.initConfig -> INFO config fabric_sdk_go logging level is set to: INFO
SDK實例化成功

7.清理環(huán)境

Fabric SDK生成一些文件，如證書，二進(jìn)制文件和臨時文件。 關(guān)閉網(wǎng)絡(luò)不會完全清理環(huán)境，當(dāng)需要重新啟動時，這些文件將被重復(fù)使用以避免構(gòu)建過程。 對于開發(fā)，可以快速測試，但對于真正的測試，需要清理所有內(nèi)容并從頭開始。

如何清理環(huán)境

• 關(guān)閉你的網(wǎng)絡(luò)： cd $GOPATH/src/github.com/kongyixueyuan.com/bill/fixtures && docker-compose down
• 刪除證書存儲（在配置文件中，client.credentialStore中定義）： rm -rf /tmp/bill-*
• 刪除一些不是由docker-compose命令生成的docker容器和docker鏡像：
  docker rm -f -v docker ps -a --no-trunc | grep "bill" | cut -d ' ' -f 1 2>/dev/null
  和
  docker rmi docker images --no-trunc | grep "bill" | cut -d ' ' -f 1 2>/dev/null

如何更有效率？

可以在一個步驟中自動完成所有這些任務(wù)。 構(gòu)建和啟動過程也可以自動化。 為此，將創(chuàng)建一個Makefile。 首先，確保 make 工具：

make --version

如果沒有安裝make （Ubuntu）：

sudo apt install make 

然后使用以下內(nèi)容在項目的根目錄下創(chuàng)建一個名為Makefile的文件：

$ cd $GOPATH/src/github.com/kongyixueyuan.com/bill
$ vim Makefile

.PHONY: all dev clean build env-up env-down run

all: clean build env-up run

dev: build run

##### BUILD
build:
    @echo "Build ..."
    @dep ensure
    @go build
    @echo "Build done"

##### ENV
env-up:
    @echo "Start environment ..."
    @cd fixtures && docker-compose up --force-recreate -d
    @echo "Sleep 15 seconds in order to let the environment setup correctly"
    @sleep 15
    @echo "Environment up"

env-down:
    @echo "Stop environment ..."
    @cd fixtures && docker-compose down
    @echo "Environment down"

##### RUN
run:
    @echo "Start app ..."
    @./ticket

##### CLEAN
clean: env-down
    @echo "Clean up ..."
    @rm -rf /tmp/bill-* bill
    @docker rm -f -v `docker ps -a --no-trunc | grep "ticket" | cut -d ' ' -f 1` 2>/dev/null || true
    @docker rmi `docker images --no-trunc | grep "ticket" | cut -d ' ' -f 1` 2>/dev/null || true
    @echo "Clean up done"

現(xiàn)在完成任務(wù)：

1. 整個環(huán)境將被清理干凈
2. go程序?qū)⒈痪幾g
3. 啟動區(qū)塊鏈網(wǎng)絡(luò)
4. 啟動程序

要使用它，請進(jìn)入項目的根目錄并使用make命令：

• 任務(wù)all ： make或make all
• 任務(wù)clean ：清理一切并釋放網(wǎng)絡(luò)（ make clean ）
• 任務(wù)build ：只需構(gòu)建應(yīng)用程序（ make build ）
• 任務(wù)env-up ：只需建立網(wǎng)絡(luò)（ make env-up ）