Fabric v2.3 测试网络 - 脚本分析（一）- 启动测试网络network.sh解析

最新推荐文章于 2023-03-04 15:05:32 发布

瘦身小蚂蚁

最新推荐文章于 2023-03-04 15:05:32 发布

阅读量3.4k

点赞数 3

分类专栏：区块链文章标签： fabric

本文链接：https://blog.csdn.net/ling1998/article/details/121311568

版权

区块链专栏收录该内容

24 篇文章 7 订阅

订阅专栏

Fabric v2.3 可以使用network.sh启动测试网络，下面是针对脚本内容进行的解析

注：文中浅蓝色字体及图片为分析备注，并根据一些备注生成了目录：

# 使用Fabric CA 生成组织及其证书

#!/bin/bash
#
# Copyright IBM Corp All Rights Reserved
#
# SPDX-License-Identifier: Apache-2.0
#

# This script brings up a Hyperledger Fabric network for testing smart contracts
# and applications. The test network consists of two organizations with one
# peer each, and a single node Raft ordering service. Users can also use this
# script to create a channel deploy a chaincode on the channel
#
# prepending $PWD/../bin to PATH to ensure we are picking up the correct binaries
# this may be commented out to resolve installed version of tools if desired
export PATH=${PWD}/../bin:$PATH
export FABRIC_CFG_PATH=${PWD}/configtx
export VERBOSE=false

# utils.sh脚本为打印输出信息功能，network.sh脚本调用了utils.sh脚本中的相关函数，如infoln、errorln、warnln、fatalln、printHelp等函数，脚本简单，自行查看下
. scripts/utils.sh

# Obtain CONTAINER_IDS and remove them
# This function is called when you bring a network down

# 函数 - 清除docker容器

function clearContainers() {
# infoln函数为utils.sh脚本文件中的函数，输出信息
infoln "Removing remaining containers"

# 删除容器服务包含hyperledger-fabric的容器
docker rm -f $(docker ps -aq --filter label=service=hyperledger-fabric) 2>/dev/null || true

# 删除容器名中以dev-peer开头的容器
docker rm -f $(docker ps -aq --filter name='dev-peer*') 2>/dev/null || true
}

# Delete any images that were generated as a part of this setup
# specifically the following images are often left behind:
# This function is called when you bring the network down

# 函数 - 清除docker镜像

function removeUnwantedImages() {
infoln "Removing generated chaincode docker images"
# 删除满足条件的镜像（引用以dev-peer开头的镜像）
docker image rm -f $(docker images -aq --filter reference='dev-peer*') 2>/dev/null || true
}

# Versions of fabric known not to work with the test network
NONWORKING_VERSIONS="^1\.0\. ^1\.1\. ^1\.2\. ^1\.3\. ^1\.4\."

# Do some basic sanity checking to make sure that the appropriate versions of fabric
# binaries/images are available. In the future, additional checking for the presence
# of go or other items could be added.

# 函数 - 检查二进制文件是否存在

function checkPrereqs() {

# 检查fabric

## Check if your have cloned the peer binaries and configuration files.
# 通过使用peer命令来检查fabric二进制文件是否存在，peer是二进制文件，文件位置如下图所示
peer version > /dev/null 2>&1

# 如果二进制文件不存在或 config目录不存在（config位置如下图所示），则显示错误信息并退出
if [[ $? -ne 0 || ! -d "../config" ]]; then
errorln "Peer binary and configuration files not found.."
errorln
errorln "Follow the instructions in the Fabric docs to install the Fabric Binaries:"
errorln "https://hyperledger-fabric.readthedocs.io/en/latest/install.html"
exit 1
fi

# use the fabric tools container to see if the samples and binaries match your
# docker images
# fabric二进制文件的版本，当前为2.3.3，执行命令输出结果如下图所示
LOCAL_VERSION=$(peer version | sed -ne 's/ Version: //p')
# fabric镜像版本当前为2.3.3
DOCKER_IMAGE_VERSION=$(docker run --rm hyperledger/fabric-tools:latest peer version | sed -ne 's/ Version: //p' | head -1)

infoln "LOCAL_VERSION=$LOCAL_VERSION"
infoln "DOCKER_IMAGE_VERSION=$DOCKER_IMAGE_VERSION"

# 若fabric二进制文件版本与镜像版本不一致，则输出警告信息
if [ "$LOCAL_VERSION" != "$DOCKER_IMAGE_VERSION" ]; then
warnln "Local fabric binaries and docker images are out of sync. This may cause problems."
fi

# 若为版本为1.4及之前版本，则抛出错误信息（不支持1.4及之前版本）
for UNSUPPORTED_VERSION in $NONWORKING_VERSIONS; do
infoln "$LOCAL_VERSION" | grep -q $UNSUPPORTED_VERSION
if [ $? -eq 0 ]; then
fatalln "Local Fabric binary version of $LOCAL_VERSION does not match the versions supported by the test network."
fi

infoln "$DOCKER_IMAGE_VERSION" | grep -q $UNSUPPORTED_VERSION
if [ $? -eq 0 ]; then
fatalln "Fabric Docker image version of $DOCKER_IMAGE_VERSION does not match the versions supported by the test network."
fi
done

## Check for fabric-ca

# 检查fabric-ca

if [ "$CRYPTO" == "Certificate Authorities" ]; then
# 通过使用fabric-ca-client命令来检查fabric-ca二进制文件是否存在，fabric-ca-client是二进制文件，文件位置如下图所示
fabric-ca-client version > /dev/null 2>&1

   # 如果二进制文件fabric-ca-client不存在，则显示错误信息并退出
if [[ $? -ne 0 ]]; then
errorln "fabric-ca-client binary not found.."
errorln
errorln "Follow the instructions in the Fabric docs to install the Fabric Binaries:"
errorln "https://hyperledger-fabric.readthedocs.io/en/latest/install.html"
exit 1
fi

   # fabric-ca二进制文件的版本，当前为1.5.2，执行命令输出结果如下图所示
CA_LOCAL_VERSION=$(fabric-ca-client version | sed -ne 's/ Version: //p')
   # fabric-ca镜像版本当前为1.5.2
CA_DOCKER_IMAGE_VERSION=$(docker run --rm hyperledger/fabric-ca:latest fabric-ca-client version | sed -ne 's/ Version: //p' | head -1)

infoln "CA_LOCAL_VERSION=$CA_LOCAL_VERSION"
infoln "CA_DOCKER_IMAGE_VERSION=$CA_DOCKER_IMAGE_VERSION"

# 若fabric-ca二进制文件版本与镜像版本不一致，则输出警告信息
if [ "$CA_LOCAL_VERSION" != "$CA_DOCKER_IMAGE_VERSION" ]; then
warnln "Local fabric-ca binaries and docker images are out of sync. This may cause problems."
fi
fi
}

# Before you can bring up a network, each organization needs to generate the crypto
# material that will define that organization on the network. Because Hyperledger
# Fabric is a permissioned blockchain, each node and user on the network needs to
# use certificates and keys to sign and verify its actions. In addition, each user
# needs to belong to an organization that is recognized as a member of the network.
# You can use the Cryptogen tool or Fabric CAs to generate the organization crypto
# material.

# By default, the sample network uses cryptogen. Cryptogen is a tool that is
# meant for development and testing that can quickly create the certificates and keys
# that can be consumed by a Fabric network. The cryptogen tool consumes a series
# of configuration files for each organization in the "organizations/cryptogen"
# directory. Cryptogen uses the files to generate the crypto material for each
# org in the "organizations" directory.

# You can also use Fabric CAs to generate the crypto material. CAs sign the certificates
# and keys that they generate to create a valid root of trust for each organization.
# The script uses Docker Compose to bring up three CAs, one for each peer organization
# and the ordering organization. The configuration file for creating the Fabric CA
# servers are in the "organizations/fabric-ca" directory. Within the same directory,
# the "registerEnroll.sh" script uses the Fabric CA client to create the identities,
# certificates, and MSP folders that are needed to create the test network in the
# "organizations/ordererOrganizations" directory.

# Create Organization crypto material using cryptogen or CAs

# 函数 - 创建组织及证书

function createOrgs() {
# 若organizations目录中存在peerOrganizations目录，则删除peerOrganizations目录
if [ -d "organizations/peerOrganizations" ]; then
rm -Rf organizations/peerOrganizations && rm -Rf organizations/ordererOrganizations
fi

# Create crypto material using cryptogen

# 使用cryptogen生成证书

if [ "$CRYPTO" == "cryptogen" ]; then
# 搜索cryptogen命令是否存在，存在则输出所在路径及别名，如下图所示，否则抛出错误信息，程序终止
which cryptogen
if [ "$?" -ne 0 ]; then
fatalln "cryptogen tool not found. exiting"
fi

infoln "Generating certificates using cryptogen tool"

infoln "Creating Org1 Identities"

set -x # 脚本调试命令，将会把下面命令打印到屏幕
# 生成组织org1且为其生成证书
cryptogen generate --config=./organizations/cryptogen/crypto-config-org1.yaml --output="organizations"
res=$?
{ set +x; } 2>/dev/null # 关闭脚本调试命令，之后的命令不会打印到屏幕了

# 若创建组织生成证书失败，则抛出错误信息，程序终止
if [ $res -ne 0 ]; then
fatalln "Failed to generate certificates..."
fi

infoln "Creating Org2 Identities"

set -x
# 生成组织org2且为其生成证书
cryptogen generate --config=./organizations/cryptogen/crypto-config-org2.yaml --output="organizations"
res=$?
{ set +x; } 2>/dev/null

# 若创建组织生成证书失败，则抛出错误信息，程序终止
if [ $res -ne 0 ]; then
fatalln "Failed to generate certificates..."
fi

infoln "Creating Orderer Org Identities"

set -x
# 生成组织orderer且为其生成证书
cryptogen generate --config=./organizations/cryptogen/crypto-config-orderer.yaml --output="organizations"
res=$?
{ set +x; } 2>/dev/null

# 若创建组织生成证书失败，则抛出错误信息，程序终止
if [ $res -ne 0 ]; then
fatalln "Failed to generate certificates..."
fi

# Create crypto material using Fabric CA

# 使用Fabric CA 生成组织及其证书

if [ "$CRYPTO" == "Certificate Authorities" ]; then
infoln "Generating certificates using Fabric CA"
# 启动fabric测试网络 docker-compose -f docker/docker-compose-ca.yaml，文件内容如下
docker-compose -f $COMPOSE_FILE_CA up -d 2>&1

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

version: '3.7'

networks:
  test:
    name: fabric_test

services:

  ca_org1:
    image: hyperledger/fabric-ca:latest
    labels:
      service: hyperledger-fabric
    environment:
      - FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server
      - FABRIC_CA_SERVER_CA_NAME=ca-org1
      - FABRIC_CA_SERVER_TLS_ENABLED=true
      - FABRIC_CA_SERVER_PORT=7054
      - FABRIC_CA_SERVER_OPERATIONS_LISTENADDRESS=0.0.0.0:17054
    ports:
      - "7054:7054"
      - "17054:17054"
    command: sh -c 'fabric-ca-server start -b admin:adminpw -d'
    volumes:
      - ../organizations/fabric-ca/org1:/etc/hyperledger/fabric-ca-server
    container_name: ca_org1
    networks:
      - test

  ca_org2:
    image: hyperledger/fabric-ca:latest
    labels:
      service: hyperledger-fabric
    environment:
      - FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server
      - FABRIC_CA_SERVER_CA_NAME=ca-org2
      - FABRIC_CA_SERVER_TLS_ENABLED=true
      - FABRIC_CA_SERVER_PORT=8054
      - FABRIC_CA_SERVER_OPERATIONS_LISTENADDRESS=0.0.0.0:18054
    ports:
      - "8054:8054"
      - "18054:18054"
    command: sh -c 'fabric-ca-server start -b admin:adminpw -d'
    volumes:
      - ../organizations/fabric-ca/org2:/etc/hyperledger/fabric-ca-server
    container_name: ca_org2
    networks:
      - test

  ca_orderer:
    image: hyperledger/fabric-ca:latest
    labels:
      service: hyperledger-fabric
    environment:
      - FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server
      - FABRIC_CA_SERVER_CA_NAME=ca-orderer
      - FABRIC_CA_SERVER_TLS_ENABLED=true
      - FABRIC_CA_SERVER_PORT=9054
      - FABRIC_CA_SERVER_OPERATIONS_LISTENADDRESS=0.0.0.0:19054
    ports:
      - "9054:9054"
      - "19054:19054"
    command: sh -c 'fabric-ca-server start -b admin:adminpw -d'
    volumes:
      - ../organizations/fabric-ca/ordererOrg:/etc/hyperledger/fabric-ca-server
    container_name: ca_orderer
    networks:
      - test

#引入脚本：生成组织及其证书（包含3个函数，下面将调用），文件位置如下图所示
. organizations/fabric-ca/registerEnroll.sh

# 检查证书是否生成成功
while :
do
if [ ! -f "organizations/fabric-ca/org1/tls-cert.pem" ]; then
sleep 1
else
break
fi
done

infoln "Creating Org1 Identities"

# 生成组织org1，调用脚本registerEnroll.sh中的函数
createOrg1

infoln "Creating Org2 Identities"

# 生成组织org2，调用脚本registerEnroll.sh中的函数
createOrg2

infoln "Creating Orderer Org Identities"

# 生成组织orderer，调用脚本registerEnroll.sh中的函数
createOrderer

# 生成通用连接配置文件（CCP）

infoln "Generating CCP files for Org1 and Org2"

# 执行脚本文件，生成通用连接配置文件，json与yaml文件格式，文件位置如下图所示
./organizations/ccp-generate.sh

# ccp-generate.sh文件内容如下所示：

#!/bin/bash

function one_line_pem {
    echo "`awk 'NF {sub(/\\n/, ""); printf "%s\\\\\\\n",$0;}' $1`"
}

function json_ccp {
    local PP=$(one_line_pem $4)
    local CP=$(one_line_pem $5)
    sed -e "s/\${ORG}/$1/" \
        -e "s/\${P0PORT}/$2/" \
        -e "s/\${CAPORT}/$3/" \
        -e "s#\${PEERPEM}#$PP#" \
        -e "s#\${CAPEM}#$CP#" \
        organizations/ccp-template.json
}

function yaml_ccp {
    local PP=$(one_line_pem $4)
    local CP=$(one_line_pem $5)
    sed -e "s/\${ORG}/$1/" \
        -e "s/\${P0PORT}/$2/" \
        -e "s/\${CAPORT}/$3/" \
        -e "s#\${PEERPEM}#$PP#" \
        -e "s#\${CAPEM}#$CP#" \
        organizations/ccp-template.yaml | sed -e $'s/\\\\n/\\\n          /g'
}

ORG=1
P0PORT=7051
CAPORT=7054
PEERPEM=organizations/peerOrganizations/org1.example.com/tlsca/tlsca.org1.example.com-cert.pem
CAPEM=organizations/peerOrganizations/org1.example.com/ca/ca.org1.example.com-cert.pem

echo "$(json_ccp $ORG $P0PORT $CAPORT $PEERPEM $CAPEM)" > organizations/peerOrganizations/org1.example.com/connection-org1.json
echo "$(yaml_ccp $ORG $P0PORT $CAPORT $PEERPEM $CAPEM)" > organizations/peerOrganizations/org1.example.com/connection-org1.yaml

ORG=2
P0PORT=9051
CAPORT=8054
PEERPEM=organizations/peerOrganizations/org2.example.com/tlsca/tlsca.org2.example.com-cert.pem
CAPEM=organizations/peerOrganizations/org2.example.com/ca/ca.org2.example.com-cert.pem

echo "$(json_ccp $ORG $P0PORT $CAPORT $PEERPEM $CAPEM)" > organizations/peerOrganizations/org2.example.com/connection-org2.json
echo "$(yaml_ccp $ORG $P0PORT $CAPORT $PEERPEM $CAPEM)" > organizations/peerOrganizations/org2.example.com/connection-org2.yaml

}

# Once you create the organization crypto material, you need to create the
# genesis block of the application channel.

# The configtxgen tool is used to create the genesis block. Configtxgen consumes a
# "configtx.yaml" file that contains the definitions for the sample network. The
# genesis block is defined using the "TwoOrgsApplicationGenesis" profile at the bottom
# of the file. This profile defines an application channel consisting of our two Peer Orgs.
# The peer and ordering organizations are defined in the "Profiles" section at the
# top of the file. As part of each organization profile, the file points to the
# location of the MSP directory for each member. This MSP is used to create the channel
# MSP that defines the root of trust for each organization. In essence, the channel
# MSP allows the nodes and users to be recognized as network members.
#
# If you receive the following warning, it can be safely ignored:
#
# [bccsp] GetDefault -> WARN 001 Before using BCCSP, please call InitFactories(). Falling back to bootBCCSP.
#
# You can ignore the logs regarding intermediate certs, we are not using them in
# this crypto implementation.

# After we create the org crypto material and the application channel genesis block,
# we can now bring up the peers and ordering service. By default, the base
# file for creating the network is "docker-compose-test-net.yaml" in the ``docker``
# folder. This file defines the environment variables and file mounts that
# point the crypto material and genesis block that were created in earlier.

# Bring up the peer and orderer nodes using docker compose.

# 函数 - 启动测试网络

function networkUp() {

# 检查二进制文件是否存在

checkPrereqs

# generate artifacts if they don't exist
# 若存在目录organizations/peerOrganizations，则创建组织及证书
if [ ! -d "organizations/peerOrganizations" ]; then
createOrgs
fi

COMPOSE_FILES="-f ${COMPOSE_FILE_BASE}"

if [ "${DATABASE}" == "couchdb" ]; then
COMPOSE_FILES="${COMPOSE_FILES} -f ${COMPOSE_FILE_COUCH}"
fi

# 启动测试网络（后台启动）

# export DOCKER_SOCK=/var/run/docker.sock
# docker-compose -f docker/docker-compose-test-net.yaml up -d
DOCKER_SOCK="${DOCKER_SOCK}" docker-compose ${COMPOSE_FILES} up -d 2>&1

# 显示容器信息

docker ps -a

# 若显示容器信息有错误，则抛出错误信息，程序终止
if [ $? -ne 0 ]; then
fatalln "Unable to start network"
fi
}

# call the script to create the channel, join the peers of org1 and org2,
# and then update the anchor peers for each organization

# 函数 - 创建通道

function createChannel() {
# Bring up the network if it is not already up.
# 若不存在目录organizations/peerOrganizations，则先启动测试网络
if [ ! -d "organizations/peerOrganizations" ]; then
infoln "Bringing up network"
# 启动测试网络
networkUp
fi

# now run the script that creates a channel. This script uses configtxgen once
# to create the channel creation transaction and the anchor peer updates.
# 使用createChannel.sh脚本创建通道，脚本详细解析另起一篇文章（可参见Fabric v2.3 测试网络 - 创建通道脚本文件createChannel.sh解析_ling1998的博客-CSDN博客），脚本位置如下图所示
# 命令中默认参数： scripts/createChannel.sh "mychannel" 3 5 false
scripts/createChannel.sh $CHANNEL_NAME $CLI_DELAY $MAX_RETRY $VERBOSE

}

## Call the script to deploy a chaincode to the channel

# 函数 - 部署智能合约

function deployCC() {
# 使用deployCC.sh 脚本创建通道，脚本详细解析另起一篇文章，脚本位置如下图所示
scripts/deployCC.sh $CHANNEL_NAME $CC_NAME $CC_SRC_PATH $CC_SRC_LANGUAGE $CC_VERSION $CC_SEQUENCE $CC_INIT_FCN $CC_END_POLICY $CC_COLL_CONFIG $CLI_DELAY $MAX_RETRY $VERBOSE

# 若显示容器信息有错误，则抛出错误信息，程序终止
if [ $? -ne 0 ]; then
fatalln "Deploying chaincode failed"
fi
}

# Tear down running network

# 函数 - 关闭测试网络

function networkDown() {
# stop org3 containers also in addition to org1 and org2, in case we were running sample to add org3

# 关闭docker-compose

DOCKER_SOCK=$DOCKER_SOCK docker-compose -f $COMPOSE_FILE_BASE -f $COMPOSE_FILE_COUCH -f $COMPOSE_FILE_CA down --volumes --remove-orphans
docker-compose -f $COMPOSE_FILE_COUCH_ORG3 -f $COMPOSE_FILE_ORG3 down --volumes --remove-orphans

# Don't remove the generated artifacts -- note, the ledgers are always removed
# 若参数不是restart，即代表不重启
if [ "$MODE" != "restart" ]; then
# Bring down the network, deleting the volumes
#Cleanup the chaincode containers

# 清除容器

clearContainers

#Cleanup images

# 清除镜像

removeUnwantedImages

# remove orderer block and other channel configuration transactions and certs

# 删除block文件及节点文件

docker run --rm -v "$(pwd):/data" busybox sh -c 'cd /data && rm -rf system-genesis-block/*.block organizations/peerOrganizations organizations/ordererOrganizations'

## remove fabric ca artifacts

# 删除证书文件

docker run --rm -v "$(pwd):/data" busybox sh -c 'cd /data && rm -rf organizations/fabric-ca/org1/msp organizations/fabric-ca/org1/tls-cert.pem organizations/fabric-ca/org1/ca-cert.pem organizations/fabric-ca/org1/IssuerPublicKey organizations/fabric-ca/org1/IssuerRevocationPublicKey organizations/fabric-ca/org1/fabric-ca-server.db'
docker run --rm -v "$(pwd):/data" busybox sh -c 'cd /data && rm -rf organizations/fabric-ca/org2/msp organizations/fabric-ca/org2/tls-cert.pem organizations/fabric-ca/org2/ca-cert.pem organizations/fabric-ca/org2/IssuerPublicKey organizations/fabric-ca/org2/IssuerRevocationPublicKey organizations/fabric-ca/org2/fabric-ca-server.db'
docker run --rm -v "$(pwd):/data" busybox sh -c 'cd /data && rm -rf organizations/fabric-ca/ordererOrg/msp organizations/fabric-ca/ordererOrg/tls-cert.pem organizations/fabric-ca/ordererOrg/ca-cert.pem organizations/fabric-ca/ordererOrg/IssuerPublicKey organizations/fabric-ca/ordererOrg/IssuerRevocationPublicKey organizations/fabric-ca/ordererOrg/fabric-ca-server.db'
docker run --rm -v "$(pwd):/data" busybox sh -c 'cd /data && rm -rf addOrg3/fabric-ca/org3/msp addOrg3/fabric-ca/org3/tls-cert.pem addOrg3/fabric-ca/org3/ca-cert.pem addOrg3/fabric-ca/org3/IssuerPublicKey addOrg3/fabric-ca/org3/IssuerRevocationPublicKey addOrg3/fabric-ca/org3/fabric-ca-server.db'

# remove channel and script artifacts

# 删除链码包文件

docker run --rm -v "$(pwd):/data" busybox sh -c 'cd /data && rm -rf channel-artifacts log.txt *.tar.gz'
fi
}

# Using crpto vs CA. default is cryptogen
CRYPTO="cryptogen"
# timeout duration - the duration the CLI should wait for a response from
# another container before giving up
MAX_RETRY=5
# default for delay between commands
CLI_DELAY=3
# channel name defaults to "mychannel"
CHANNEL_NAME="mychannel"
# chaincode name defaults to "NA"
CC_NAME="NA"
# chaincode path defaults to "NA"
CC_SRC_PATH="NA"
# endorsement policy defaults to "NA". This would allow chaincodes to use the majority default policy.
CC_END_POLICY="NA"
# collection configuration defaults to "NA"
CC_COLL_CONFIG="NA"
# chaincode init function defaults to "NA"
CC_INIT_FCN="NA"
# use this as the default docker-compose yaml definition
COMPOSE_FILE_BASE=docker/docker-compose-test-net.yaml
# docker-compose.yaml file if you are using couchdb
COMPOSE_FILE_COUCH=docker/docker-compose-couch.yaml
# certificate authorities compose file
COMPOSE_FILE_CA=docker/docker-compose-ca.yaml
# use this as the docker compose couch file for org3
COMPOSE_FILE_COUCH_ORG3=addOrg3/docker/docker-compose-couch-org3.yaml
# use this as the default docker-compose yaml definition for org3
COMPOSE_FILE_ORG3=addOrg3/docker/docker-compose-org3.yaml
#
# chaincode language defaults to "NA"
CC_SRC_LANGUAGE="NA"
# Chaincode version
CC_VERSION="1.0"
# Chaincode definition sequence
CC_SEQUENCE=1
# default database
DATABASE="leveldb"

# Get docker sock path from environment variable
SOCK="${DOCKER_HOST:-/var/run/docker.sock}"
DOCKER_SOCK="${SOCK##unix://}"

# Parse commandline args

## Parse mode
if [[ $# -lt 1 ]] ; then
printHelp
exit 0
else
MODE=$1
shift
fi

# parse a createChannel subcommand if used
if [[ $# -ge 1 ]] ; then
key="$1"
if [[ "$key" == "createChannel" ]]; then
export MODE="createChannel"
shift
fi
fi

# parse flags

while [[ $# -ge 1 ]] ; do
key="$1"
case $key in
-h )
printHelp $MODE
exit 0
;;
-c )
CHANNEL_NAME="$2"
shift
;;
-ca )
CRYPTO="Certificate Authorities"
;;
-r )
MAX_RETRY="$2"
shift
;;
-d )
CLI_DELAY="$2"
shift
;;
-s )
DATABASE="$2"
shift
;;
-ccl )
CC_SRC_LANGUAGE="$2"
shift
;;
-ccn )
CC_NAME="$2"
shift
;;
-ccv )
CC_VERSION="$2"
shift
;;
-ccs )
CC_SEQUENCE="$2"
shift
;;
-ccp )
CC_SRC_PATH="$2"
shift
;;
-ccep )
CC_END_POLICY="$2"
shift
;;
-cccg )
CC_COLL_CONFIG="$2"
shift
;;
-cci )
CC_INIT_FCN="$2"
shift
;;
-verbose )
VERBOSE=true
shift
;;
* )
errorln "Unknown flag: $key"
printHelp
exit 1
;;
esac
shift
done

# Are we generating crypto material with this command?
if [ ! -d "organizations/peerOrganizations" ]; then
CRYPTO_MODE="with crypto from '${CRYPTO}'"
else
CRYPTO_MODE=""
fi

# network.sh 参数

# Determine mode of operation and printing out what we asked for
if [ "$MODE" == "up" ]; then
infoln "Starting nodes with CLI timeout of '${MAX_RETRY}' tries and CLI delay of '${CLI_DELAY}' seconds and using database '${DATABASE}' ${CRYPTO_MODE}"
elif [ "$MODE" == "createChannel" ]; then
infoln "Creating channel '${CHANNEL_NAME}'."
infoln "If network is not up, starting nodes with CLI timeout of '${MAX_RETRY}' tries and CLI delay of '${CLI_DELAY}' seconds and using database '${DATABASE} ${CRYPTO_MODE}"
elif [ "$MODE" == "down" ]; then
infoln "Stopping network"
elif [ "$MODE" == "restart" ]; then
infoln "Restarting network"
elif [ "$MODE" == "deployCC" ]; then
infoln "deploying chaincode on channel '${CHANNEL_NAME}'"
else
printHelp
exit 1
fi

# up 启动测试网络

if [ "${MODE}" == "up" ]; then
networkUp

# createChannel 创建通道

elif [ "${MODE}" == "createChannel" ]; then
createChannel

# deployCC 部署链码

elif [ "${MODE}" == "deployCC" ]; then
deployCC

# down 关闭测试网络

elif [ "${MODE}" == "down" ]; then
networkDown

# 其它打印详细信息

else
printHelp
exit 1
fi

瘦身小蚂蚁

关注

3
点赞
踩
11

收藏

觉得还不错? 一键收藏
0
评论
Fabric v2.3 测试网络 - 脚本分析（一）- 启动测试网络network.sh解析

Fabric v2.3 可以使用network.sh启动测试网络，下面是针对脚本内容进行的解析注：文中浅蓝色字体及图片为分析备注，并根据一些备注生成了目录：目录# 函数 - 清除docker容器# 函数 - 清除docker镜像# 函数 - 检查二进制文件是否存在 # 检查fabric # 检查fabric-ca# 函数 - 创建组织及证书 # 使用cryptogen生成证书 # 使用Fabric CA 生成组织及其证书# 函数 - 启动测试网络...
复制链接

扫一扫