当前位置： 代码迷 >> 综合 >> Fabric1.4.4源码解析及运行 first-network 网络
  详细解决方案

Fabric1.4.4源码解析及运行 first-network 网络

热度：21   发布时间：2024-02-12 11:58:55.0

构建你的第一个网络（Build Your First network，BYFN）提供了一个 fabric 的示例网络。该示例网络中由两个组织构成，每个组织维护两个 peer 节点，默认使用 solo 共识服务。

1 脚本 byfn.sh

first-network 中有一个启动脚本 byfn.sh，利用构建的 Docker 镜像快速启动网络。该脚本会启动一个 orderer 节点和四个归属两个不同组织的 peer 节点，还将启动一个容器运行脚本，它将 peer 节点加入通道（Channel）、部署和实例化链码，并根据已部署的链码驱动交易执行。

以下是 byfn.sh 脚本的帮助文档：

$ ./byfn.sh
Usage: byfn.sh <mode> [-c <channel name>] [-t <timeout>] [-d <delay>] [-f <docker-compose-file>] [-s <dbtype>] [-l <language>] [-o <consensus-type>] [-i <imagetag>] [-a] [-n] [-v]<mode> - one of 'up', 'down', 'restart', 'generate' or 'upgrade'- 'up' - bring up the network with docker-compose up- 'down' - clear the network with docker-compose down- 'restart' - restart the network- 'generate' - generate required certificates and genesis block- 'upgrade'  - upgrade the network from version 1.3.x to 1.4.0-c <channel name> - channel name to use (defaults to "mychannel")-t <timeout> - CLI timeout duration in seconds (defaults to 10)-d <delay> - delay duration in seconds (defaults to 3)-f <docker-compose-file> - specify which docker-compose file use (defaults to docker-compose-cli.yaml)-s <dbtype> - the database backend to use: goleveldb (default) or couchdb-l <language> - the chaincode language: golang (default) or node-o <consensus-type> - the consensus-type of the ordering service: solo (default), kafka, or etcdraft-i <imagetag> - the tag to be used to launch the network (defaults to "latest")-a - launch certificate authorities (no certificate authorities are launched by default)-n - do not deploy chaincode (abstore chaincode is deployed by default)-v - verbose modebyfn.sh -h (print this message)Typically, one would first generate the required certificates and 
genesis block, then bring up the network. e.g.:byfn.sh generate -c mychannelbyfn.sh up -c mychannel -s couchdbbyfn.sh up -c mychannel -s couchdb -i 1.4.0byfn.sh up -l nodebyfn.sh down -c mychannelbyfn.sh upgrade -c mychannelTaking all defaults:byfn.sh generatebyfn.sh upbyfn.sh down
  • -c：设置通道名称，默认为 mychannel，例：./byfn.sh up -c testchannel
  • -t：设置 CLI 超时参数，不设置的情况下 CLI 将放弃 10 秒后发出查询请求的默认设置
  • -l：设置智能合约的语言，默认是 go，例：./byfn.sh up -l java
  • -o：设置排序服务方式，默认是 solo，例：./byfn.sh up -o kafka

2 生成证书

执行如下命令：

$ ./byfn.sh generate
  • 运行该命令会为 fabric 网络的各种实体生成所需的证书与密钥，保存在 crypto-config 目录下。

3 启动网络

使用如下命令启动 fabric 网络：

$ ./byfn.sh up
  • 注意：该命令会检查网络实体的证书是否生成，如果没有会先生成证书。因此，可以直接执行 ./byfn.sh up 命令，而无需执行 ./byfn.sh generate 命令。

执行日志如下：

Starting for channel 'mychannel' with CLI timeout of '10' seconds and CLI delay of '3' seconds
Continue? [Y/n]
proceeding ...
Creating network "net_byfn" with the default driver
Creating peer0.org1.example.com
Creating peer1.org1.example.com
Creating peer0.org2.example.com
Creating orderer.example.com
Creating peer1.org2.example.com
Creating cli____    _____      _      ____    _____
/ ___|  |_   _|    / \    |  _ \  |_   _|
\___ \    | |     / _ \   | |_) |   | |___) |   | |    / ___ \  |  _ <    | |
|____/    |_|   /_/   \_\ |_| \_\   |_|Channel name : mychannel
Creating channel...

启动所有容器，然后驱动完整的应用程序场景。执行成功后，在终端会出现如下输出：

Query Result: 90
2017-05-16 17:08:15.158 UTC [main] main -> INFO 008 Exiting.....
===================== Query successful on peer1.org2 on channel 'mychannel' ========================================== All GOOD, BYFN execution completed =====================_____   _   _   ____
| ____| | \ | | |  _ \
|  _|   |  \| | | | | |
| |___  | |\  | | |_| |
|_____| |_| \_| |____/

幕后面发生了什么？

./byfn.sh up 启动完 orderer 节点、peer 节点和 CLI 容器之后，实际是调用 script.sh 脚本，该脚本是在 CLI 容器中执行，script.sh 脚本完成客户端交易执行操作。下面是 CLI 容器的定义，CLI 容器其实就是用户客户端，只不过是命令行客户端，运行在容器中。默认情况下，CLI 的身份是 admin.org1，连接 peer0.org1 节点，执行 script.sh 脚本。下面简略描述 script.sh 的基本函数。

3.1 创建通道

admin.org1 连接 peer0.org1 节点，向 orderer 节点传递要创建的通道名称 $CHANNEL_NAME （默认为 mychannel）和通道配置交易 channel.tx。如果创建成功，则返回一个创世区块 $CHANNEL_NANE.block，它会存储在 peer 节点的文件系统中，包含 channel.tx 指定的通道配置信息。

 

3.2 加入通道

joinChannel () {for org in 1 2; dofor peer in 0 1; dojoinChannelWithRetry $p$CHANNEL_NAMEeer $orgecho "===================== peer${peer}.org${org} joined channel '$CHANNEL_NAME' ===================== "sleep $DELAYechodonedone
}

第一个 for 循环标识两个组织 org1 和 org2；第二个 for 循环标识两个组织 peer0 和 peer1。根据 $peer $org 先后顺序，四个节点分别是：

  • peer0.org1.example.com
  • peer1.org1.example.com
  • peer0.org2.example.com
  • peer1.org2.example.com

这是 first-network 的默认网络结构，在 crypto-config.yaml 文件的 TwoOrgsChannel 部分定义，MSP 路径在 docker-compose-cli.yaml 文件中定义。

## Sometimes Join takes time hence RETRY at least 5 times
joinChannelWithRetry() {PEER=$1ORG=$2setGlobals $PEER $ORGset -xpeer channel join -b $CHANNEL_NAME.block >&log.txtres=$?set +xcat log.txtif [ $res -ne 0 -a $COUNTER -lt $MAX_RETRY ]; thenCOUNTER=$(expr $COUNTER + 1)echo "peer${PEER}.org${ORG} failed to join the channel, Retry after $DELAY seconds"sleep $DELAYjoinChannelWithRetry $PEER $ORGelseCOUNTER=1fiverifyResult $res "After $MAX_RETRY attempts, peer${PEER}.org${ORG} has failed to join channel '$CHANNEL_NAME' "
}

在 joinChannelWithRetry 函数中的 setGlobals 是设置 CLI 容器的环境变量的函数。例如：setGlobals 1 2 设置 CLI 的身份为 admin.org2，连接 peer1.org2 节点。

使用 peer channel join 命令让节点加入通道，$CHANNEL_NAME.block 就是前面创建通道成功时返回的区块，该区块在上面 org1.peer0 创建通道时保持在 CLI 容器内，所以能直接使用。节点成功加入通道后会创建 CHANNEL_NAME.block 开头的链。

 

3.3 更新锚节点

一个组织只能有一个锚节点，节点加入通道后才能进行更新。

updateAnchorPeers() {PEER=$1ORG=$2setGlobals $PEER $ORGif [ -z "$CORE_PEER_TLS_ENABLED" -o "$CORE_PEER_TLS_ENABLED" = "false" ]; thenset -xpeer channel update -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/${CORE_PEER_LOCALMSPID}anchors.tx >&log.txtres=$?set +xelseset -xpeer channel update -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/${CORE_PEER_LOCALMSPID}anchors.tx --tls $CORE_PEER_TLS_ENABLED --cafile $ORDERER_CA >&log.txtres=$?set +xficat log.txtverifyResult $res "Anchor peer update failed"echo "===================== Anchor peers updated for org '$CORE_PEER_LOCALMSPID' on channel '$CHANNEL_NAME' ===================== "sleep $DELAYecho
}

更新 org1 的锚节点 peer0.org1.example.com 和 org2 的锚节点 peer0.org2.example.com 。过程是将 Org1MSPanchors.tx 和 Org2MSPanchors.tx 交易连同通道名称 $CHANNEL_NAME 传递给 orderer。

 

3.4 安装链码

installChaincode() {PEER=$1ORG=$2setGlobals $PEER $ORGVERSION=${3:-1.0}set -xpeer chaincode install -n mycc -v ${VERSION} -l ${LANGUAGE} -p ${CC_SRC_PATH} >&log.txtres=$?set +xcat log.txtverifyResult $res "Chaincode installation on peer${PEER}.org${ORG} has failed"echo "===================== Chaincode is installed on peer${PEER}.org${ORG} ===================== "echo
}

安装链码需要指定链码的配置信息，-n 是链码的名称；-v 是版本号；-l 是语言，不是用该标志默认是 go 语言；-p 是指向链码路径，默认是 github.com/chaincode/chaincode_example02/go/。

 

3.5 实例化链码

instantiateChaincode() {PEER=$1ORG=$2setGlobals $PEER $ORGVERSION=${3:-1.0}# while 'peer chaincode' command can get the orderer endpoint from the peer# (if join was successful), let's supply it directly as we know it using# the "-o" optionif [ -z "$CORE_PEER_TLS_ENABLED" -o "$CORE_PEER_TLS_ENABLED" = "false" ]; thenset -xpeer chaincode instantiate -o orderer.example.com:7050 -C $CHANNEL_NAME -n mycc -l ${LANGUAGE} -v ${VERSION} -c '{"Args":["init","a","100","b","200"]}' -P "AND ('Org1MSP.peer','Org2MSP.peer')" >&log.txtres=$?set +xelseset -xpeer chaincode instantiate -o orderer.example.com:7050 --tls $CORE_PEER_TLS_ENABLED --cafile $ORDERER_CA -C $CHANNEL_NAME -n mycc -l ${LANGUAGE} -v 1.0 -c '{"Args":["init","a","100","b","200"]}' -P "AND ('Org1MSP.peer','Org2MSP.peer')" >&log.txtres=$?set +xficat log.txtverifyResult $res "Chaincode instantiation on peer${PEER}.org${ORG} on channel '$CHANNEL_NAME' failed"echo "===================== Chaincode is instantiated on peer${PEER}.org${ORG} on channel '$CHANNEL_NAME' ===================== "echo
}

fabric 网络上的链码是多次安装，一次实例化，该函数只需运行一遍即可。

链码在通道 $CHANNEL_NAME 上实例化。实例化将链码添加到通道上，启动目标节点的容器，初始化与链码相关的初始值，这里的初始值为 ["a","100","b","200"]。”实例化“ 过程会产生链码的容器，例如： dev-peer0-org1.example.com-mycc-1.0 。实例化过程需要指定背书策略，通过 -P 参数设置，这里的策略定义为 AND ('Org1MSP.peer','Org2MSP.peer') ，表示任何交易必须要有 org1 和 org2 节点的共同背书。此处背书的节点只能是以下四对组合：

  • peer0.org1.example.com 和 peer0.org2.example.com
  • peer0.org1.example.com 和 peer1.org2.example.com
  • peer1.org1.example.com 和 peer0.org2.example.com
  • peer1.org1.example.com 和 peer1.org2.example.com

 

3.6 调用链码

# chaincodeInvoke <peer> <org> ...
# Accepts as many peer/org pairs as desired and requests endorsement from each
chaincodeInvoke() {parsePeerConnectionParameters $@res=$?verifyResult $res "Invoke transaction failed on channel '$CHANNEL_NAME' due to uneven number of peer and org parameters "# while 'peer chaincode' command can get the orderer endpoint from the# peer (if join was successful), let's supply it directly as we know# it using the "-o" optionif [ -z "$CORE_PEER_TLS_ENABLED" -o "$CORE_PEER_TLS_ENABLED" = "false" ]; thenset -xpeer chaincode invoke -o orderer.example.com:7050 -C $CHANNEL_NAME -n mycc $PEER_CONN_PARMS -c '{"Args":["invoke","a","b","10"]}' >&log.txtres=$?set +xelseset -xpeer chaincode invoke -o orderer.example.com:7050 --tls $CORE_PEER_TLS_ENABLED --cafile $ORDERER_CA -C $CHANNEL_NAME -n mycc $PEER_CONN_PARMS -c '{"Args":["invoke","a","b","10"]}' >&log.txtres=$?set +xficat log.txtverifyResult $res "Invoke execution on $PEERS failed "echo "===================== Invoke transaction successful on $PEERS on channel '$CHANNEL_NAME' ===================== "echo
}

向 $PEER_CONN_PARM 发送一个调用，以实现从 a 中转移 10 给 b。$PEER_CONN_PARM 就是上面四对组合中的任意一对背书节点。在调用链码的过程中，如果某个节点的链码容器还没有启动，就会执行启动。

 

3.7 查询链码

chaincodeQuery() {PEER=$1ORG=$2setGlobals $PEER $ORGEXPECTED_RESULT=$3echo "===================== Querying on peer${PEER}.org${ORG} on channel '$CHANNEL_NAME'... ===================== "local rc=1local starttime=$(date +%s)# continue to poll# we either get a successful response, or reach TIMEOUTwhiletest "$(($(date +%s) - starttime))" -lt "$TIMEOUT" -a $rc -ne 0dosleep $DELAYecho "Attempting to Query peer${PEER}.org${ORG} ...$(($(date +%s) - starttime)) secs"set -xpeer chaincode query -C $CHANNEL_NAME -n mycc -c '{"Args":["query","a"]}' >&log.txtres=$?set +xtest $res -eq 0 && VALUE=$(cat log.txt | awk '/Query Result/ {print $NF}')test "$VALUE" = "$EXPECTED_RESULT" && let rc=0# removed the string "Query Result" from peer chaincode query command# result. as a result, have to support both options until the change# is merged.test $rc -ne 0 && VALUE=$(cat log.txt | egrep '^[0-9]+$')test "$VALUE" = "$EXPECTED_RESULT" && let rc=0doneechocat log.txtif test $rc -eq 0; thenecho "===================== Query successful on peer${PEER}.org${ORG} on channel '$CHANNEL_NAME' ===================== "elseecho "!!!!!!!!!!!!!!! Query result on peer${PEER}.org${ORG} is INVALID !!!!!!!!!!!!!!!!"echo "================== ERROR !!! FAILED to execute End-2-End Scenario =================="echoexit 1fi
}

向装有链码的节点发送一个查询查看 a 的值。如果返回值为 90，则表明在之前的交易中 “a” 的值被减去 10。

 

这证明了什么？

为了能成功地对账本进行读/写操作，链码必须按照在相应的节点上。只有在链码中执行初始化（Init函数）、调用（Invoke函数）交易（读/写），或者查询 “a” 的值，才会为节点启动一个链码容器（交易引起容器的启动）。另外，通道中的所有节点都维护账本的一个精确副本，该副本包括在区块中存储不可变、按顺序排列的记录的区块链，以及用户维护当前账本的状态数据库。

 

4 关闭网络

执行下面命令：

$ ./byfn.sh down
Stopping for channel 'mychannel' with CLI timeout of '10' seconds and CLI delay of '3' seconds
Continue? [Y/n] y
proceeding ...
WARNING: The BYFN_CA2_PRIVATE_KEY variable is not set. Defaulting to a blank string.
WARNING: The BYFN_CA1_PRIVATE_KEY variable is not set. Defaulting to a blank string.
Stopping cli                    ... done
Stopping peer1.org1.example.com ... done
Stopping peer1.org2.example.com ... done
Stopping peer0.org1.example.com ... done
Stopping peer0.org2.example.com ... done
Stopping orderer.example.com    ... done
Removing cli                    ... done
Removing peer1.org1.example.com ... done
Removing peer1.org2.example.com ... done
Removing peer0.org1.example.com ... done
Removing peer0.org2.example.com ... done
Removing orderer.example.com    ... done
Removing network net_byfn
Removing volume net_peer0.org3.example.com
WARNING: Volume net_peer0.org3.example.com not found.
Removing volume net_peer1.org3.example.com
WARNING: Volume net_peer1.org3.example.com not found.
Removing volume net_orderer2.example.com
WARNING: Volume net_orderer2.example.com not found.
Removing volume net_orderer.example.com
Removing volume net_peer0.org2.example.com
Removing volume net_peer0.org1.example.com
Removing volume net_peer1.org1.example.com
Removing volume net_peer1.org2.example.com
Removing volume net_orderer5.example.com
WARNING: Volume net_orderer5.example.com not found.
Removing volume net_orderer4.example.com
WARNING: Volume net_orderer4.example.com not found.
Removing volume net_orderer3.example.com
WARNING: Volume net_orderer3.example.com not found.

该命令将关闭网络，删除证书材料和组件，并从 Docker 注册表中删除链码镜像。crypto-config 文件夹会被删除，channel-artifacts 文件夹下的 channel.tx、genesis.block、Org1MSPanchors.tx 和 Org2MSPanchors.tx 这四个文件会被删除。

 

本项目为基于Hyperledger Fabric区块链的单据存储解决方案，项目主要包括链码和 Web应用两部分。Fabric链码采用JAVA开发，负责维护和存储数据及交易数据，后台为采用java开发 的Web应用，负责为用户提供访问区块链上单据的操作界面，例如数据查询、创建通道、部署链码等等操作。并提供搭建区块链浏览器，可以方便查看区块链上的数据存储情况。

典型案例：
基于Hyperledger Fabric区块链技术的疫苗监控平台
基于Hyperledger Fabric区块链技术的电动汽车充电交易信息记录溯源系统
基于Hyperledger Fabric区块链技术的疫情健康信息及外出记录监控平台
基于Hyperledger Fabric区块链技术的电子订单溯源系统
基于Hyperledger Fabric区块链技术的智慧物流信息监控系统
基于Hyperledger Fabric区块链技术的学生成绩信息管理系统
基于Hyperledger Fabric区块链技术的智慧图书馆管理系统
基于Hyperledger Fabric区块链技术的农产品溯源系统
... ... 等等

 

 

  相关解决方案

代码迷 - 您身边的软件异常，代码异常，编程异常助手（发现，解决，分享）
Copyright © 2009-2013 DAIMAMI.COM. All rights reserved.