fabric v1.4 kafka模式(未開啓TLS)，多節點服務器部署，實現動態添加組織
fabric v1.4 kafka模式(未開啓TLS)，多節點服務器部署，實現動態添加組織node
1、環境準備linux
這裏採用阿里雲ECS主機(2核4G，生產環境按實際環境提高配置)git
必須指定hostsnamegithub
fabric官網 github https://github.com/hyperledger/fabricgolang
centos7 x64docker
1.全部節點服務器指定以下hosts(含後續新增組織，也必須同步全部hosts)json
172.31.1.89 zookeeper0vim
172.31.1.90 zookeeper1centos
172.31.1.91 zookeeper2api
172.31.1.89 kafka0
172.31.1.90 kafka1
172.31.1.91 kafka2
172.31.1.92 kafka3
172.31.1.89 orderer0.example.com
172.31.1.90 orderer1.example.com
172.31.1.91 orderer2.example.com
172.31.1.89 peer0.org1.example.com
172.31.1.90 peer1.org1.example.com
172.31.1.91 peer0.org2.example.com
172.31.1.92 peer1.org2.example.com
;;;##後續模擬新增org3組織-備用
172.31.1.101 peer0.org2.example.com
172.31.1.102 peer1.org2.example.com
2.環境初始(全部節點服務均部署)
#####注意！注意！注意！說三遍########
阿里雲ECS 註釋(options timeout:2 attempts:3 rotate single-request-reopen)，否則會報錯
# vim /etc/resolv.conf
;options timeout:2 attempts:3 rotate single-request-reopen
nameserver 100.100.2.136
nameserver 100.100.2.138
#######注意！注意！注意！說三遍##########
1)關閉防火牆（或開放端口）、selinux
systemctl disable firewalld.service systemctl stop firewalld.service
2)安裝配置docker(17.06.2-ce or later)
# step 1: 安裝必要的一些系統工具 yum install -y yum-utils device-mapper-persistent-data lvm2 # Step 2: 添加軟件源信息 yum-config-manager --add-repo http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo # Step 3: 更新並安裝 Docker-CE yum makecache fast yum list docker-ce --showduplicates | sort -r #安裝指定docker 版本 yum install docker-ce-17.12.0.ce-1.el7.centos # Step 4: 開啓Docker服務 service docker start systemctl enable docker.service
3)docker-compose(1.14.0 or later)
#下載docker-compose # curl -L "https://github.com/docker/compose/releases/download/1.24.1/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose #爲docker-compose配置執行權限 #chmod +x /usr/local/bin/docker-compose #檢查是否安裝成功 #docker-compose -v
4)git、go(version 1.10.x)
#下載安裝git #yum install git -y #go安裝下載，預先建立/opt/soft/(後續存配置文件)、/opt/gopath(存放fabric源代碼) #mkdir -p /opt/gopath #mkdir /opt/soft/ # 國外地址 #wget https://storage.googleapis.com/golang/go1.10.linux-amd64.tar.gz # 國內地址 #wget https://studygolang.com/dl/golang/go1.10.linux-amd64.tar.gz # 解壓 #tar -C /usr/local/ -xzvf go1.10.linux-amd64.tar.gz # 配置環境變量 #vi /etc/profile 添加以下 # go env export PATH=$PATH:/usr/local/go/bin export GOPATH=/opt/gopath # 生效配置 source /etc/profile # 查看配置 go version
5)域名ip映射(/etc/hosts),如開篇設置
2、生成配置信息
####如下操做均在第一節點服務器 172.31.1.89
1.下載Hyperledger Fabric 源碼
# 下載 Fabric 源碼, 源碼中 import 的路徑爲github.com/hyperledger/fabric ,因此咱們要按照這個路徑
#mkdir -p /opt/gopath/src/github.com/hyperledger #cd /opt/gopath/src/github.com/hyperledger #git clone https://github.com/hyperledger/fabric [root@xxxx fabric]# pwd /opt/gopath/src/github.com/hyperledger/fabric [root@xxxxx fabric]# ll total 1412 .................省略部分 drwxr-xr-x 6 root root 4096 Aug 25 02:06 msp drwxr-xr-x 6 root root 4096 Aug 25 02:06 orderer drwxr-xr-x 13 root root 4096 Aug 29 12:48 peer drwxr-xr-x 14 root root 4096 Aug 25 02:06 protos -rw-r--r-- 1 root root 7303 Aug 25 02:06 README.md drwxr-xr-x 3 root root 4096 Aug 25 02:06 release drwxr-xr-x 2 root root 4096 Aug 25 02:06 release_notes drwxr-xr-x 3 root root 4096 Aug 25 02:06 sampleconfig drwxr-xr-x 2 root root 4096 Aug 25 02:06 scripts -rw-r--r-- 1 root root 316 Aug 25 02:06 settings.gradle -rw-r--r-- 1 root root 3816 Aug 25 02:06 testingInfo.rst -rw-r--r-- 1 root root 438053 Aug 25 02:06 test-pyramid.png drwxr-xr-x 8 root root 4096 Aug 25 02:06 token -rw-r--r-- 1 root root 495 Aug 25 02:06 tox.ini drwxr-xr-x 2 root root 4096 Aug 25 02:06 unit-test drwxr-xr-x 9 root root 4096 Aug 25 02:06 vendor
2.生成 Hyperledger Fabric 證書，證書生成只須要生成一次
# 下載官方證書生成軟件工具(均爲二進制文件) #進入目錄 #cd /opt/soft #工具爲1.4版本：wget https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric/linux-amd64-1.4.0/hyperledger-fabric-linux-amd64-1.4.0.tar.gz #解壓 tar zxvf hyperledger-fabric-linux-amd64-1.4.0.tar.gz # 解壓後是 一個 bin 與 一個 config 目錄 [root@xxxx bin]# tree ├── configtxgen ├── configtxlator ├── cryptogen ├── get-docker-images.sh ├── orderer └── peer # 設置環境變量 vi /etc/profile # fabric env export PATH=$PATH:/opt/soft/bin # 使文件生效 source /etc/profile
# 從git(release-1.3版本)下載，或者從其餘途徑下載默認 configtx.yaml 、crypto-config.yaml ，並上傳至/opt/soft目錄，待修改
配置文件在目錄下 https://github.com/hyperledger/fabric/tree/release-1.3/examples/e2e_cli
###編輯修改crypto-config.yaml 以下(主要修改組織區域與增長orderer)：
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#
# ---------------------------------------------------------------------------
# "OrdererOrgs" - Definition of organizations managing orderer nodes
# ---------------------------------------------------------------------------
OrdererOrgs:
# ---------------------------------------------------------------------------
# Orderer
# ---------------------------------------------------------------------------
- Name: Orderer
Domain: example.com
CA:
Country: CN
Province: GuangDong
Locality: ShenZhen
# ---------------------------------------------------------------------------
# "Specs" - See PeerOrgs below for complete description
# ---------------------------------------------------------------------------
Specs:
- Hostname: orderer0
- Hostname: orderer1
- Hostname: orderer2
# ---------------------------------------------------------------------------
# "PeerOrgs" - Definition of organizations managing peer nodes
# ---------------------------------------------------------------------------
PeerOrgs:
# ---------------------------------------------------------------------------
# Org1
# ---------------------------------------------------------------------------
- Name: Org1
Domain: org1.example.com
EnableNodeOUs: true
CA:
Country: CN
Province: GuangDong
Locality: ShenZhen
# ---------------------------------------------------------------------------
# "Specs"
# ---------------------------------------------------------------------------
# Uncomment this section to enable the explicit definition of hosts in your
# configuration. Most users will want to use Template, below
#
# Specs is an array of Spec entries. Each Spec entry consists of two fields:
# - Hostname: (Required) The desired hostname, sans the domain.
# - CommonName: (Optional) Specifies the template or explicit override for
# the CN. By default, this is the template:
#
# "{{.Hostname}}.{{.Domain}}"
#
# which obtains its values from the Spec.Hostname and
# Org.Domain, respectively.
# ---------------------------------------------------------------------------
# Specs:
# - Hostname: foo # implicitly "foo.org1.example.com"
# CommonName: foo27.org5.example.com # overrides Hostname-based FQDN set above
# - Hostname: bar
# - Hostname: baz
# ---------------------------------------------------------------------------
# "Template"
# ---------------------------------------------------------------------------
# Allows for the definition of 1 or more hosts that are created sequentially
# from a template. By default, this looks like "peer%d" from 0 to Count-1.
# You may override the number of nodes (Count), the starting index (Start)
# or the template used to construct the name (Hostname).
#
# Note: Template and Specs are not mutually exclusive. You may define both
# sections and the aggregate nodes will be created for you. Take care with
# name collisions
# ---------------------------------------------------------------------------
Template:
Count: 2
# Start: 5
# Hostname: {{.Prefix}}{{.Index}} # default
# ---------------------------------------------------------------------------
# "Users"
# ---------------------------------------------------------------------------
# Count: The number of user accounts _in addition_ to Admin
# ---------------------------------------------------------------------------
Users:
Count: 1
# ---------------------------------------------------------------------------
# Org2: See "Org1" for full specification
# ---------------------------------------------------------------------------
- Name: Org2
Domain: org2.example.com
EnableNodeOUs: true
CA:
Country: CN
Province: GuangDong
Locality: ShenZhen
Template:
Count: 2
Users:
Count: 1
#用cryptogen 工具執行生成相應的證書
[root@xxxx soft]# cryptogen generate --config=./crypto-config.yaml
org1.example.com
org2.example.com
# 生成一個 crypto-config 證書目錄
# 可用 tree crypto-config 查看
#生成 Hyperledger Fabric 創世區塊
#/opt/soft目錄下建立channel-artifacts，存放生成塊信息
[root@xxxx soft]# mkdir -p /opt/soft/channel-artifacts
# 編輯修改configtx.yaml(orderer 多節點 peer 多節點),以下：
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#
---
################################################################################
#
# Section: Organizations
#
# - This section defines the different organizational identities which will
# be referenced later in the configuration.
#
################################################################################
Organizations:
# SampleOrg defines an MSP using the sampleconfig. It should never be used
# in production but may be used as a template for other definitions
- &OrdererOrg
# DefaultOrg defines the organization which is used in the sampleconfig
# of the fabric.git development environment
Name: OrdererOrg
# ID to load the MSP definition as
ID: OrdererMSP
# MSPDir is the filesystem path which contains the MSP configuration
MSPDir: crypto-config/ordererOrganizations/example.com/msp
# Policies defines the set of policies at this level of the config tree
# For organization policies, their canonical path is usually
# /Channel/<Application|Orderer>/<OrgName>/<PolicyName>
Policies:
Readers:
Type: Signature
Rule: "OR('OrdererMSP.member')"
Writers:
Type: Signature
Rule: "OR('OrdererMSP.member')"
Admins:
Type: Signature
Rule: "OR('OrdererMSP.admin')"
- &Org1
# DefaultOrg defines the organization which is used in the sampleconfig
# of the fabric.git development environment
Name: Org1MSP
# ID to load the MSP definition as
ID: Org1MSP
MSPDir: crypto-config/peerOrganizations/org1.example.com/msp
# Policies defines the set of policies at this level of the config tree
# For organization policies, their canonical path is usually
# /Channel/<Application|Orderer>/<OrgName>/<PolicyName>
Policies:
Readers:
Type: Signature
Rule: "OR('Org1MSP.admin', 'Org1MSP.peer', 'Org1MSP.client')"
Writers:
Type: Signature
Rule: "OR('Org1MSP.admin', 'Org1MSP.client')"
Admins:
Type: Signature
Rule: "OR('Org1MSP.admin')"
AnchorPeers:
# AnchorPeers defines the location of peers which can be used
# for cross org gossip communication. Note, this value is only
# encoded in the genesis block in the Application section context
- Host: peer0.org1.example.com
Port: 7051
- &Org2
# DefaultOrg defines the organization which is used in the sampleconfig
# of the fabric.git development environment
Name: Org2MSP
# ID to load the MSP definition as
ID: Org2MSP
MSPDir: crypto-config/peerOrganizations/org2.example.com/msp
# Policies defines the set of policies at this level of the config tree
# For organization policies, their canonical path is usually
# /Channel/<Application|Orderer>/<OrgName>/<PolicyName>
Policies:
Readers:
Type: Signature
Rule: "OR('Org2MSP.admin', 'Org2MSP.peer', 'Org2MSP.client')"
Writers:
Type: Signature
Rule: "OR('Org2MSP.admin', 'Org2MSP.client')"
Admins:
Type: Signature
Rule: "OR('Org2MSP.admin')"
AnchorPeers:
# AnchorPeers defines the location of peers which can be used
# for cross org gossip communication. Note, this value is only
# encoded in the genesis block in the Application section context
- Host: peer0.org2.example.com
Port: 7051
################################################################################
#
# SECTION: Capabilities
#
# - This section defines the capabilities of fabric network. This is a new
# concept as of v1.1.0 and should not be utilized in mixed networks with
# v1.0.x peers and orderers. Capabilities define features which must be
# present in a fabric binary for that binary to safely participate in the
# fabric network. For instance, if a new MSP type is added, newer binaries
# might recognize and validate the signatures from this type, while older
# binaries without this support would be unable to validate those
# transactions. This could lead to different versions of the fabric binaries
# having different world states. Instead, defining a capability for a channel
# informs those binaries without this capability that they must cease
# processing transactions until they have been upgraded. For v1.0.x if any
# capabilities are defined (including a map with all capabilities turned off)
# then the v1.0.x peer will deliberately crash.
#
################################################################################
Capabilities:
# Channel capabilities apply to both the orderers and the peers and must be
# supported by both.
# Set the value of the capability to true to require it.
Channel: &ChannelCapabilities
# V1.3 for Channel is a catchall flag for behavior which has been
# determined to be desired for all orderers and peers running at the v1.3.x
# level, but which would be incompatible with orderers and peers from
# prior releases.
# Prior to enabling V1.3 channel capabilities, ensure that all
# orderers and peers on a channel are at v1.3.0 or later.
V1_3: true
# Orderer capabilities apply only to the orderers, and may be safely
# used with prior release peers.
# Set the value of the capability to true to require it.
Orderer: &OrdererCapabilities
# V1.1 for Orderer is a catchall flag for behavior which has been
# determined to be desired for all orderers running at the v1.1.x
# level, but which would be incompatible with orderers from prior releases.
# Prior to enabling V1.1 orderer capabilities, ensure that all
# orderers on a channel are at v1.1.0 or later.
V1_1: true
# Application capabilities apply only to the peer network, and may be safely
# used with prior release orderers.
# Set the value of the capability to true to require it.
Application: &ApplicationCapabilities
# V1.3 for Application enables the new non-backwards compatible
# features and fixes of fabric v1.3.
V1_3: true
# V1.2 for Application enables the new non-backwards compatible
# features and fixes of fabric v1.2 (note, this need not be set if
# later version capabilities are set)
V1_2: false
# V1.1 for Application enables the new non-backwards compatible
# features and fixes of fabric v1.1 (note, this need not be set if
# later version capabilities are set).
V1_1: false
################################################################################
#
# SECTION: Application
#
# - This section defines the values to encode into a config transaction or
# genesis block for application related parameters
#
################################################################################
Application: &ApplicationDefaults
# Organizations is the list of orgs which are defined as participants on
# the application side of the network
Organizations:
# Policies defines the set of policies at this level of the config tree
# For Application policies, their canonical path is
# /Channel/Application/<PolicyName>
Policies:
Readers:
Type: ImplicitMeta
Rule: "ANY Readers"
Writers:
Type: ImplicitMeta
Rule: "ANY Writers"
Admins:
Type: ImplicitMeta
Rule: "MAJORITY Admins"
# Capabilities describes the application level capabilities, see the
# dedicated Capabilities section elsewhere in this file for a full
# description
Capabilities:
<<: *ApplicationCapabilities
################################################################################
#
# SECTION: Orderer
#
# - This section defines the values to encode into a config transaction or
# genesis block for orderer related parameters
#
################################################################################
Orderer: &OrdererDefaults
# Orderer Type: The orderer implementation to start
# Available types are "solo" and "kafka"
OrdererType: kafka
Addresses:
- orderer0.example.com:7050
- orderer1.example.com:7050
- orderer2.example.com:7050
# Batch Timeout: The amount of time to wait before creating a batch
BatchTimeout: 2s
# Batch Size: Controls the number of messages batched into a block
BatchSize:
# Max Message Count: The maximum number of messages to permit in a batch
MaxMessageCount: 10
# Absolute Max Bytes: The absolute maximum number of bytes allowed for
# the serialized messages in a batch.
AbsoluteMaxBytes: 98 MB
# Preferred Max Bytes: The preferred maximum number of bytes allowed for
# the serialized messages in a batch. A message larger than the preferred
# max bytes will result in a batch larger than preferred max bytes.
PreferredMaxBytes: 512 KB
Kafka:
# Brokers: A list of Kafka brokers to which the orderer connects. Edit
# this list to identify the brokers of the ordering service.
# NOTE: Use IP:port notation.
Brokers:
- kafka0:9092
- kafka1:9092
- kafka2:9092
- kafka3:9092
# Organizations is the list of orgs which are defined as participants on
# the orderer side of the network
Organizations:
# Policies defines the set of policies at this level of the config tree
# For Orderer policies, their canonical path is
# /Channel/Orderer/<PolicyName>
Policies:
Readers:
Type: ImplicitMeta
Rule: "ANY Readers"
Writers:
Type: ImplicitMeta
Rule: "ANY Writers"
Admins:
Type: ImplicitMeta
Rule: "MAJORITY Admins"
# BlockValidation specifies what signatures must be included in the block
# from the orderer for the peer to validate it.
BlockValidation:
Type: ImplicitMeta
Rule: "ANY Writers"
# Capabilities describes the orderer level capabilities, see the
# dedicated Capabilities section elsewhere in this file for a full
# description
Capabilities:
<<: *OrdererCapabilities
################################################################################
#
# CHANNEL
#
# This section defines the values to encode into a config transaction or
# genesis block for channel related parameters.
#
################################################################################
Channel: &ChannelDefaults
# Policies defines the set of policies at this level of the config tree
# For Channel policies, their canonical path is
# /Channel/<PolicyName>
Policies:
# Who may invoke the 'Deliver' API
Readers:
Type: ImplicitMeta
Rule: "ANY Readers"
# Who may invoke the 'Broadcast' API
Writers:
Type: ImplicitMeta
Rule: "ANY Writers"
# By default, who may modify elements at this config level
Admins:
Type: ImplicitMeta
Rule: "MAJORITY Admins"
# Capabilities describes the channel level capabilities, see the
# dedicated Capabilities section elsewhere in this file for a full
# description
Capabilities:
<<: *ChannelCapabilities
################################################################################
#
# Profile
#
# - Different configuration profiles may be encoded here to be specified
# as parameters to the configtxgen tool
#
################################################################################
Profiles:
TwoOrgsOrdererGenesis:
<<: *ChannelDefaults
Orderer:
<<: *OrdererDefaults
Organizations:
- *OrdererOrg
Consortiums:
SampleConsortium:
Organizations:
- *Org1
- *Org2
TwoOrgsChannel:
Consortium: SampleConsortium
Application:
<<: *ApplicationDefaults
Organizations:
- *Org1
- *Org2
#使用configtxgen工具，建立 創世區塊 TwoOrgsOrdererGenesis 名稱爲 configtx.yaml 中 Profiles 字段下定義的
#[root@xxxx soft]#configtxgen -profile TwoOrgsOrdererGenesis -outputBlock ./channel-artifacts/genesis.block 2019-08-25 02:25:31.256 CST [common.tools.configtxgen] main -> WARN 001 Omitting the channel ID for configtxgen for output operations is deprecated. Explicitly passing the channel ID will be required in the future, defaulting to 'testchainid'. 2019-08-25 02:25:31.256 CST [common.tools.configtxgen] main -> INFO 002 Loading configuration 2019-08-25 02:25:31.268 CST [common.tools.configtxgen.localconfig] completeInitialization -> INFO 003 orderer type: kafka 2019-08-25 02:25:31.268 CST [common.tools.configtxgen.localconfig] Load -> INFO 004 Loaded configuration: /opt/soft/configtx.yaml 2019-08-25 02:25:31.279 CST [common.tools.configtxgen.localconfig] completeInitialization -> INFO 005 orderer type: kafka 2019-08-25 02:25:31.279 CST [common.tools.configtxgen.localconfig] LoadTopLevel -> INFO 006 Loaded configuration: /opt/soft/configtx.yaml 2019-08-25 02:25:31.280 CST [common.tools.configtxgen] doOutputBlock -> INFO 007 Generating genesis block 2019-08-25 02:25:31.281 CST [common.tools.configtxgen] doOutputBlock -> INFO 008 Writing genesis block
# 下面來生成一個 peer 服務 中使用的 tx 文件 TwoOrgsChannel 名稱爲 configtx.yaml 中 Profiles 字段下定義的，這裏必須指定上面的 channelID
# [root@xxxx soft]# configtxgen -profile TwoOrgsChannel -outputCreateChannelTx ./channel-artifacts/channel.tx -channelID mychannel 2019-08-25 02:26:53.395 CST [common.tools.configtxgen] main -> INFO 001 Loading configuration 2019-08-25 02:26:53.406 CST [common.tools.configtxgen.localconfig] Load -> INFO 002 Loaded configuration: /opt/soft/configtx.yaml 2019-08-25 02:26:53.417 CST [common.tools.configtxgen.localconfig] completeInitialization -> INFO 003 orderer type: kafka 2019-08-25 02:26:53.417 CST [common.tools.configtxgen.localconfig] LoadTopLevel -> INFO 004 Loaded configuration: /opt/soft/configtx.yaml 2019-08-25 02:26:53.417 CST [common.tools.configtxgen] doOutputChannelCreateTx -> INFO 005 Generating new channel configtx 2019-08-25 02:26:53.418 CST [common.tools.configtxgen] doOutputChannelCreateTx -> INFO 006 Writing new channel tx
#查看生成文件，是否正確
[root@xxx soft]# ls -lt channel-artifacts/ -rw-r--r-- 1 root root 346 8月 25 03:18 channel.tx -rw-r--r-- 1 root root 12484 8月 25 03:17 genesis.block
# 定義組織，生成錨節點更新文件
# Org1MSP
[root@xxxx soft]# configtxgen -profile TwoOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org1MSPanchors.tx -channelID mychannel -asOrg Org1MSP 2019-08-25 02:28:04.205 CST [common.tools.configtxgen] main -> INFO 001 Loading configuration 2019-08-25 02:28:04.216 CST [common.tools.configtxgen.localconfig] Load -> INFO 002 Loaded configuration: /opt/soft/configtx.yaml 2019-08-25 02:28:04.227 CST [common.tools.configtxgen.localconfig] completeInitialization -> INFO 003 orderer type: kafka 2019-08-25 02:28:04.227 CST [common.tools.configtxgen.localconfig] LoadTopLevel -> INFO 004 Loaded configuration: /opt/soft/configtx.yaml 2019-08-25 02:28:04.227 CST [common.tools.configtxgen] doOutputAnchorPeersUpdate -> INFO 005 Generating anchor peer update 2019-08-25 02:28:04.227 CST [common.tools.configtxgen] doOutputAnchorPeersUpdate -> INFO 006 Writing anchor peer update
# Org2MSP
[root@xxxx soft]# configtxgen -profile TwoOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org2MSPanchors.tx -channelID mychannel -asOrg Org2MSP 2019-08-25 02:28:37.381 CST [common.tools.configtxgen] main -> INFO 001 Loading configuration 2019-08-25 02:28:37.392 CST [common.tools.configtxgen.localconfig] Load -> INFO 002 Loaded configuration: /opt/soft/configtx.yaml 2019-08-25 02:28:37.403 CST [common.tools.configtxgen.localconfig] completeInitialization -> INFO 003 orderer type: kafka 2019-08-25 02:28:37.403 CST [common.tools.configtxgen.localconfig] LoadTopLevel -> INFO 004 Loaded configuration: /opt/soft/configtx.yaml 2019-08-25 02:28:37.403 CST [common.tools.configtxgen] doOutputAnchorPeersUpdate -> INFO 005 Generating anchor peer update 2019-08-25 02:28:37.403 CST [common.tools.configtxgen] doOutputAnchorPeersUpdate -> INFO 006 Writing anchor peer update
#拷貝 crypto-config 、channel-artifacts 目錄到其餘節點服務器
#scp -r crypto-config channel-artifacts root@172.31.1.90:/opt/soft #scp -r crypto-config channel-artifacts root@172.31.1.91:/opt/soft #scp -r crypto-config channel-artifacts root@172.31.1.92:/opt/soft
3、部署Zookeeper(3個節點) Kafka(4個節點) 集羣
注：zk 集羣，容器中須要相互指定extra_hosts，而且注意zookeeper定義的ID不要重複，否則沒法啓動！！！！
1.第一節點 (172.31.1.89)，在/opt/soft目錄下，編寫docker-compose-zookeeper.yaml，以下：
version: '2' services: zookeeper0: container_name: zookeeper0 hostname: zookeeper0 image: hyperledger/fabric-zookeeper restart: always environment: - ZOO_MY_ID=1 - ZOO_SERVERS=server.1=zookeeper0:2888:3888 server.2=zookeeper1:2888:3888 server.3=zookeeper2:2888:3888 volumes: - /etc/localtime:/etc/localtime:ro - /etc/timezone:/etc/timezone:ro ports: - 2181:2181 - 2888:2888 - 3888:3888 extra_hosts: - "zookeeper0:172.31.1.89" - "zookeeper1:172.31.1.90" - "zookeeper2:172.31.1.91" - "kafka0:172.31.1.89" - "kafka1:172.31.1.90" - "kafka2:172.31.1.91" - "kafka3:172.31.1.92"
2.第一節點 (172.31.1.89)，在/opt/soft目錄下，編寫docker-compose-kafka.yaml，以下
version: '2' services: kafka0: container_name: kafka0 hostname: kafka0 image: hyperledger/fabric-kafka restart: always environment: - KAFKA_MESSAGE_MAX_BYTES=103809024 - KAFKA_REPLICA_FETCH_MAX_BYTES=103809024 - KAFKA_UNCLEAN_LEADER_ELECTION_ENABLE=false environment: - KAFKA_BROKER_ID=1 - KAFKA_MIN_INSYNC_REPLICAS=2 - KAFKA_DEFAULT_REPLICATION_FACTOR=3 - KAFKA_ZOOKEEPER_CONNECT=zookeeper0:2181,zookeeper1:2181,zookeeper2:2181 - KAFKA_LOG_RETENTION_MS=-1 volumes: - /etc/localtime:/etc/localtime:ro - /etc/timezone:/etc/timezone:ro - /var/hyperledger/kafka/kafka-logs:/tmp/kafka-logs ports: - 9092:9092 extra_hosts: - "zookeeper0:172.31.1.89" - "zookeeper1:172.31.1.90" - "zookeeper2:172.31.1.91" - "kafka0:172.31.1.89" - "kafka1:172.31.1.90" - "kafka2:172.31.1.91" - "kafka3:172.31.1.92"
3.第二節點 (172.31.1.90)，在/opt/soft目錄下，編寫docker-compose-zookeeper.yaml，以下
version: '2' services: zookeeper1: container_name: zookeeper1 hostname: zookeeper1 image: hyperledger/fabric-zookeeper restart: always environment: - ZOO_MY_ID=2 - ZOO_SERVERS=server.1=zookeeper0:2888:3888 server.2=zookeeper1:2888:3888 server.3=zookeeper2:2888:3888 volumes: - /etc/localtime:/etc/localtime:ro - /etc/timezone:/etc/timezone:ro ports: - 2181:2181 - 2888:2888 - 3888:3888 extra_hosts: - "zookeeper0:172.31.1.89" - "zookeeper1:172.31.1.90" - "zookeeper2:172.31.1.91" - "kafka0:172.31.1.89" - "kafka1:172.31.1.90" - "kafka2:172.31.1.91" - "kafka3:172.31.1.92"
4.第二節點 (172.31.1.90)，在/opt/soft目錄下，編寫docker-compose-kafka.yaml，以下
version: '2' services: kafka1: container_name: kafka1 hostname: kafka1 image: hyperledger/fabric-kafka restart: always environment: - KAFKA_MESSAGE_MAX_BYTES=103809024 - KAFKA_REPLICA_FETCH_MAX_BYTES=103809024 - KAFKA_UNCLEAN_LEADER_ELECTION_ENABLE=false environment: - KAFKA_BROKER_ID=2 - KAFKA_MIN_INSYNC_REPLICAS=2 - KAFKA_DEFAULT_REPLICATION_FACTOR=3 - KAFKA_ZOOKEEPER_CONNECT=zookeeper0:2181,zookeeper1:2181,zookeeper2:2181 - KAFKA_LOG_RETENTION_MS=-1 volumes: - /etc/localtime:/etc/localtime:ro - /etc/timezone:/etc/timezone:ro - /var/hyperledger/kafka/kafka-logs:/tmp/kafka-logs ports: - 9092:9092 extra_hosts: - "zookeeper0:172.31.1.89" - "zookeeper1:172.31.1.90" - "zookeeper2:172.31.1.91" - "kafka0:172.31.1.89" - "kafka1:172.31.1.90" - "kafka2:172.31.1.91" - "kafka3:172.31.1.92"
5.第三節點 (172.31.1.91)，在/opt/soft目錄下，編寫docker-compose-zookeeper.yaml，以下
version: '2' services: zookeeper2: container_name: zookeeper2 hostname: zookeeper2 image: hyperledger/fabric-zookeeper restart: always environment: - ZOO_MY_ID=3 - ZOO_SERVERS=server.1=zookeeper0:2888:3888 server.2=zookeeper1:2888:3888 server.3=zookeeper2:2888:3888 volumes: - /etc/localtime:/etc/localtime:ro - /etc/timezone:/etc/timezone:ro ports: - 2181:2181 - 2888:2888 - 3888:3888 extra_hosts: - "zookeeper0:172.31.1.89" - "zookeeper1:172.31.1.90" - "zookeeper2:172.31.1.91" - "kafka0:172.31.1.89" - "kafka1:172.31.1.90" - "kafka2:172.31.1.91" - "kafka3:172.31.1.92"
6.第三節點 (172.31.1.91)，在/opt/soft目錄下，編寫docker-compose-kafka.yaml，以下
version: '2' services: kafka2: container_name: kafka2 hostname: kafka2 image: hyperledger/fabric-kafka restart: always environment: - KAFKA_MESSAGE_MAX_BYTES=103809024 - KAFKA_REPLICA_FETCH_MAX_BYTES=103809024 - KAFKA_UNCLEAN_LEADER_ELECTION_ENABLE=false environment: - KAFKA_BROKER_ID=3 - KAFKA_MIN_INSYNC_REPLICAS=2 - KAFKA_DEFAULT_REPLICATION_FACTOR=3 - KAFKA_ZOOKEEPER_CONNECT=zookeeper0:2181,zookeeper1:2181,zookeeper2:2181 - KAFKA_LOG_RETENTION_MS=-1 volumes: - /etc/localtime:/etc/localtime:ro - /etc/timezone:/etc/timezone:ro - /var/hyperledger/kafka/kafka-logs:/tmp/kafka-logs ports: - 9092:9092 extra_hosts: - "zookeeper0:172.31.1.89" - "zookeeper1:172.31.1.90" - "zookeeper2:172.31.1.91" - "kafka0:172.31.1.89" - "kafka1:172.31.1.90" - "kafka2:172.31.1.91" - "kafka3:172.31.1.92"
7.第四節點 (172.31.1.92)，在/opt/soft目錄下，編寫docker-compose-kafka.yaml，以下
version: '2' services: kafka3: container_name: kafka3 hostname: kafka3 image: hyperledger/fabric-kafka restart: always environment: - KAFKA_MESSAGE_MAX_BYTES=103809024 - KAFKA_REPLICA_FETCH_MAX_BYTES=103809024 - KAFKA_UNCLEAN_LEADER_ELECTION_ENABLE=false environment: - KAFKA_BROKER_ID=4 - KAFKA_MIN_INSYNC_REPLICAS=2 - KAFKA_DEFAULT_REPLICATION_FACTOR=3 - KAFKA_ZOOKEEPER_CONNECT=zookeeper0:2181,zookeeper1:2181,zookeeper2:2181 - KAFKA_LOG_RETENTION_MS=-1 volumes: - /etc/localtime:/etc/localtime:ro - /etc/timezone:/etc/timezone:ro - /var/hyperledger/kafka/kafka-logs:/tmp/kafka-logs ports: - 9092:9092 extra_hosts: - "zookeeper0:172.31.1.89" - "zookeeper1:172.31.1.90" - "zookeeper2:172.31.1.91" - "kafka0:172.31.1.89" - "kafka1:172.31.1.90" - "kafka2:172.31.1.91" - "kafka3:172.31.1.92"
#啓動服務 啓動服務順序先啓動zookeeper集羣,再啓動kafka集羣 docker-compose -f docker-compose-zookeeper.yaml up -d docker-compose -f docker-compose-kafka.yaml up -d
4、部署Hyperledger Fabric Orderer排序服務集羣，3個節點
1.第一個節點 (172.31.1.89)，在/opt/soft目錄下，編寫docker-compose-orderer.yaml，以下：
version: '2' services: orderer0.example.com: container_name: orderer0.example.com image: hyperledger/fabric-orderer environment: - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=soft_default - 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_TLS_ENABLED=false - 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] - ORDERER_KAFKA_RETRY_LONGINTERVAL=10s - ORDERER_KAFKA_RETRY_LONGTOTAL=100s - ORDERER_KAFKA_RETRY_SHORTINTERVAL=1s - ORDERER_KAFKA_RETRY_SHORTTOTAL=30s - ORDERER_KAFKA_VERBOSE=true - ORDERER_KAFKA_BROKERS=[kafka0:9092,kafka1:9092,kafka2:9092,kafka3:9092] working_dir: /opt/gopath/src/github.com/hyperledger/fabric command: orderer volumes: - /etc/localtime:/etc/localtime:ro - /etc/timezone:/etc/timezone:ro - /var/hyperledger/order_data/:/var/hyperledger/production/ - ./channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block - ./crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/msp:/var/hyperledger/orderer/msp - ./crypto-config/ordererOrganizations/example.com/orderers/orderer0.example.com/tls/:/var/hyperledger/orderer/tls ports: - 7050:7050 extra_hosts: - "zookeeper0:172.31.1.89" - "zookeeper1:172.31.1.90" - "zookeeper2:172.31.1.91" - "kafka0:172.31.1.89" - "kafka1:172.31.1.90" - "kafka2:172.31.1.91" - "kafka3:172.31.1.92"
2.第二個節點 (172.31.1.90)，在/opt/soft目錄下，編寫docker-compose-orderer.yaml，以下：
version: '2' services: orderer1.example.com: container_name: orderer1.example.com image: hyperledger/fabric-orderer environment: - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=soft_default - 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_TLS_ENABLED=false - 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] - ORDERER_KAFKA_RETRY_LONGINTERVAL=10s - ORDERER_KAFKA_RETRY_LONGTOTAL=100s - ORDERER_KAFKA_RETRY_SHORTINTERVAL=1s - ORDERER_KAFKA_RETRY_SHORTTOTAL=30s - ORDERER_KAFKA_VERBOSE=true - ORDERER_KAFKA_BROKERS=[kafka0:9092,kafka1:9092,kafka2:9092,kafka3:9092] working_dir: /opt/gopath/src/github.com/hyperledger/fabric command: orderer volumes: - /etc/localtime:/etc/localtime:ro - /etc/timezone:/etc/timezone:ro - /var/hyperledger/order_data/:/var/hyperledger/production/ - ./channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block - ./crypto-config/ordererOrganizations/example.com/orderers/orderer1.example.com/msp:/var/hyperledger/orderer/msp - ./crypto-config/ordererOrganizations/example.com/orderers/orderer1.example.com/tls/:/var/hyperledger/orderer/tls ports: - 7050:7050 extra_hosts: - "zookeeper0:172.31.1.89" - "zookeeper1:172.31.1.90" - "zookeeper2:172.31.1.91" - "kafka0:172.31.1.89" - "kafka1:172.31.1.90" - "kafka2:172.31.1.91" - "kafka3:172.31.1.92"
3.第三個節點 (172.31.1.91)，在/opt/soft目錄下，編寫docker-compose-orderer.yaml，以下：
version: '2' services: orderer2.example.com: container_name: orderer2.example.com image: hyperledger/fabric-orderer environment: - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=soft_default - 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_TLS_ENABLED=false - 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] - ORDERER_KAFKA_RETRY_LONGINTERVAL=10s - ORDERER_KAFKA_RETRY_LONGTOTAL=100s - ORDERER_KAFKA_RETRY_SHORTINTERVAL=1s - ORDERER_KAFKA_RETRY_SHORTTOTAL=30s - ORDERER_KAFKA_VERBOSE=true - ORDERER_KAFKA_BROKERS=[kafka0:9092,kafka1:9092,kafka2:9092,kafka3:9092] working_dir: /opt/gopath/src/github.com/hyperledger/fabric command: orderer volumes: - /etc/localtime:/etc/localtime:ro - /etc/timezone:/etc/timezone:ro - /var/hyperledger/order_data/:/var/hyperledger/production/ - ./channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block - ./crypto-config/ordererOrganizations/example.com/orderers/orderer2.example.com/msp:/var/hyperledger/orderer/msp - ./crypto-config/ordererOrganizations/example.com/orderers/orderer2.example.com/tls/:/var/hyperledger/orderer/tls ports: - 7050:7050 extra_hosts: - "zookeeper0:172.31.1.89" - "zookeeper1:172.31.1.90" - "zookeeper2:172.31.1.91" - "kafka0:172.31.1.89" - "kafka1:172.31.1.90" - "kafka2:172.31.1.91" - "kafka3:172.31.1.92"
#啓動服務，按照節點順序啓動 docker-compose -f docker-compose-orderer.yaml up -d # docker logs xxx 2019-08-25 15:35:35.436 CST [orderer.common.server] Start -> INFO 008 Beginning to serve requests 2019-08-25 15:35:35.436 CST [orderer.consensus.kafka] setupTopicForChannel -> INFO 009 [channel: testchainid] Setting up the topic for this channel... 2019-08-25 15:35:35.475 CST [orderer.consensus.kafka] setupProducerForChannel -> INFO 00a [channel: testchainid] Setting up the producer for this channel... 2019-08-25 15:35:35.487 CST [orderer.consensus.kafka] startThread -> INFO 00b [channel: testchainid] Producer set up successfully 2019-08-25 15:35:35.487 CST [orderer.consensus.kafka] sendConnectMessage -> INFO 00c [channel: testchainid] About to post the CONNECT message... 2019-08-25 15:35:35.842 CST [orderer.consensus.kafka] startThread -> INFO 00d [channel: testchainid] CONNECT message posted successfully 2019-08-25 15:35:35.842 CST [orderer.consensus.kafka] setupParentConsumerForChannel -> INFO 00e [channel: testchainid] Setting up the parent consumer for this channel... 2019-08-25 15:35:35.849 CST [orderer.consensus.kafka] startThread -> INFO 00f [channel: testchainid] Parent consumer set up successfully 2019-08-25 15:35:35.849 CST [orderer.consensus.kafka] setupChannelConsumerForChannel -> INFO 010 [channel: testchainid] Setting up the channel consumer for this channel (start offset: -2)...
5、部署Hyperledger Fabric Peer排序服務集羣，4個節點
注意：Peer節點下都必須啓動一個數據存儲，如 file 或者 couchdb 等，示例採用couchdb，而且強烈建議另外掛載可擴容的存儲設備(阿里云云盤，NAS,OSS)！！！
如示例中，掛載阿里云云盤至節點主機 /mnt/data/couchdb0/data(宿主掛載路徑)
下列容器couchdb0配置項中，增長以下
volumes:
# 數據持久化，用於存儲鏈碼值
- /mnt/data/couchdb0/data:/opt/couchdb/data
1.第一個節點 (172.31.1.89)，在/opt/soft目錄下，編寫docker-compose-peer.yaml，以下：
注：配置參數CORE_PEER_TLS_ENABLED=false,若是啓用tls認證，必須改成true
version: '2' services: couchdb0: container_name: couchdb0 image: hyperledger/fabric-couchdb environment: - COUCHDB_USER= - COUCHDB_PASSWORD= ports: - "5984:5984" volumes: # 數據持久化，用於存儲鏈碼值 - /mnt/data/couchdb0/data:/opt/couchdb/data peer0.org1.example.com: container_name: peer0.org1.example.com hostname: peer0.org1.example.com image: hyperledger/fabric-peer environment: - CORE_LEDGER_STATE_STATEDATABASE=CouchDB - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb0:5984 - CORE_PEER_ID=peer0.org1.example.com - CORE_PEER_NETWORKID=soft - CORE_PEER_ADDRESS=peer0.org1.example.com:7051 - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.example.com:7051 - CORE_PEER_LOCALMSPID=Org1MSP - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=soft - CORE_LOGGING_LEVEL=DEBUG - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=soft_default - CORE_PEER_GOSSIP_SKIPHANDSHAKE=true - CORE_PEER_GOSSIP_USELEADERELECTION=true - CORE_PEER_GOSSIP_ORGLEADER=false - CORE_PEER_PROFILE_ENABLED=false - CORE_CHAINCODE_EXECUTETIMEOUT=1000s - CORE_CHAINCODE_DEPLOYTIMEOUT=1000s - CORE_PEER_TLS_ENABLED=false - 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 working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer command: peer node start volumes: - /etc/localtime:/etc/localtime:ro - /etc/timezone:/etc/timezone:ro - /var/run/:/host/var/run/ - /var/hyperledger/peer_data/:/var/hyperledger/production/ - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/msp:/etc/hyperledger/fabric/msp - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls:/etc/hyperledger/fabric/tls ports: - 7051:7051 - 7052:7052 - 7053:7053 depends_on: - couchdb0 extra_hosts: - "couchdb0:172.31.1.89" - "orderer0.example.com:172.31.1.89" - "orderer1.example.com:172.31.1.90" - "orderer2.example.com:172.31.1.91"
2.第二個節點 (172.31.1.90)，在/opt/soft目錄下，編寫docker-compose-peer.yaml，以下：
注：配置參數CORE_PEER_TLS_ENABLED=false,若是啓用tls認證，必須改成true
version: '2' services: couchdb1: container_name: couchdb1 image: hyperledger/fabric-couchdb environment: - COUCHDB_USER= - COUCHDB_PASSWORD= ports: - "5984:5984" volumes: # 數據持久化，用於存儲鏈碼值 - /mnt/data/couchdb1/data:/opt/couchdb/data peer1.org1.example.com: container_name: peer1.org1.example.com hostname: peer1.org1.example.com image: hyperledger/fabric-peer environment: - CORE_LEDGER_STATE_STATEDATABASE=CouchDB - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb1:5984 - CORE_PEER_ID=peer1.org1.example.com - CORE_PEER_NETWORKID=soft - CORE_PEER_ADDRESS=peer1.org1.example.com:7051 - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org1.example.com:7051 - CORE_PEER_LOCALMSPID=Org1MSP - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=soft - CORE_LOGGING_LEVEL=DEBUG - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=soft_default - CORE_PEER_GOSSIP_SKIPHANDSHAKE=true - CORE_PEER_GOSSIP_USELEADERELECTION=true - CORE_PEER_GOSSIP_ORGLEADER=false - CORE_PEER_PROFILE_ENABLED=false - CORE_CHAINCODE_EXECUTETIMEOUT=1000s - CORE_CHAINCODE_DEPLOYTIMEOUT=1000s - CORE_PEER_TLS_ENABLED=false - 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 working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer command: peer node start volumes: - /etc/localtime:/etc/localtime:ro - /etc/timezone:/etc/timezone:ro - /var/run/:/host/var/run/ - /var/hyperledger/peer_data/:/var/hyperledger/production/ - ./crypto-config/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/msp:/etc/hyperledger/fabric/msp - ./crypto-config/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/tls:/etc/hyperledger/fabric/tls ports: - 7051:7051 - 7052:7052 - 7053:7053 depends_on: - couchdb1 extra_hosts: - "couchdb1:172.31.1.90" - "orderer0.example.com:172.31.1.89" - "orderer1.example.com:172.31.1.90" - "orderer2.example.com:172.31.1.91"
3.第三個節點 (172.31.1.91)，在/opt/soft目錄下，編寫docker-compose-peer.yaml，以下：
version: '2' services: couchdb2: container_name: couchdb2 image: hyperledger/fabric-couchdb environment: - COUCHDB_USER= - COUCHDB_PASSWORD= ports: - "5984:5984" volumes: # 數據持久化，用於存儲鏈碼值 - /mnt/data/couchdb2/data:/opt/couchdb/data peer0.org2.example.com: container_name: peer0.org2.example.com hostname: peer0.org2.example.com image: hyperledger/fabric-peer environment: - CORE_LEDGER_STATE_STATEDATABASE=CouchDB - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb2:5984 - CORE_PEER_ID=peer0.org2.example.com - CORE_PEER_NETWORKID=soft - CORE_PEER_ADDRESS=peer0.org2.example.com:7051 - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org2.example.com:7051 - CORE_PEER_LOCALMSPID=Org2MSP - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=soft - CORE_LOGGING_LEVEL=DEBUG - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=soft_default - CORE_PEER_GOSSIP_SKIPHANDSHAKE=true - CORE_PEER_GOSSIP_USELEADERELECTION=true - CORE_PEER_GOSSIP_ORGLEADER=false - CORE_PEER_PROFILE_ENABLED=false - CORE_CHAINCODE_EXECUTETIMEOUT=1000s - CORE_CHAINCODE_DEPLOYTIMEOUT=1000s - CORE_PEER_TLS_ENABLED=false - 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 working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer command: peer node start volumes: - /etc/localtime:/etc/localtime:ro - /etc/timezone:/etc/timezone:ro - /var/run/:/host/var/run/ - /var/hyperledger/peer_data/:/var/hyperledger/production/ - ./crypto-config/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/msp:/etc/hyperledger/fabric/msp - ./crypto-config/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls:/etc/hyperledger/fabric/tls ports: - 7051:7051 - 7052:7052 - 7053:7053 depends_on: - couchdb2 extra_hosts: - "couchdb2:172.31.1.91" - "orderer0.example.com:172.31.1.89" - "orderer1.example.com:172.31.1.90" - "orderer2.example.com:172.31.1.91"
4.第四個節點 (172.31.1.92)，在/opt/soft目錄下，編寫docker-compose-peer.yaml，以下：
version: '2' services: couchdb3: container_name: couchdb3 image: hyperledger/fabric-couchdb environment: - COUCHDB_USER= - COUCHDB_PASSWORD= ports: - "5984:5984" volumes: # 數據持久化，用於存儲鏈碼值 - /mnt/data/couchdb3/data:/opt/couchdb/data peer1.org2.example.com: container_name: peer1.org2.example.com hostname: peer1.org2.example.com image: hyperledger/fabric-peer environment: - CORE_LEDGER_STATE_STATEDATABASE=CouchDB - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb3:5984 - CORE_PEER_ID=peer1.org2.example.com - CORE_PEER_NETWORKID=soft - CORE_PEER_ADDRESS=peer1.org2.example.com:7051 - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org2.example.com:7051 - CORE_PEER_LOCALMSPID=Org2MSP - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=soft - CORE_LOGGING_LEVEL=DEBUG - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=soft_default - CORE_PEER_GOSSIP_SKIPHANDSHAKE=true - CORE_PEER_GOSSIP_USELEADERELECTION=true - CORE_PEER_GOSSIP_ORGLEADER=false - CORE_PEER_PROFILE_ENABLED=false - CORE_CHAINCODE_EXECUTETIMEOUT=1000s - CORE_CHAINCODE_DEPLOYTIMEOUT=1000s - CORE_PEER_TLS_ENABLED=false - 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 working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer command: peer node start volumes: - /etc/localtime:/etc/localtime:ro - /etc/timezone:/etc/timezone:ro - /var/run/:/host/var/run/ - /var/hyperledger/peer_data/:/var/hyperledger/production/ - ./crypto-config/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/msp:/etc/hyperledger/fabric/msp - ./crypto-config/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/tls:/etc/hyperledger/fabric/tls ports: - 7051:7051 - 7052:7052 - 7053:7053 depends_on: - couchdb3 extra_hosts: - "couchdb3:172.31.1.92" - "orderer0.example.com:172.31.1.89" - "orderer1.example.com:172.31.1.90" - "orderer2.example.com:172.31.1.91" #啓動peer節點服務 #docker-compose -f docker-compose-peer.yaml up -d #docker logs xxx 2019-08-25 02:05:20.638 UTC [nodeCmd] serve -> INFO 124 Starting peer with ID=[name:"peer0.org1.example.com" ], network ID=[soft], address=[peer0.org1.example.com:7051] 2019-08-25 02:05:20.638 UTC [nodeCmd] serve -> INFO 125 Started peer with ID=[name:"peer0.org1.example.com" ], network ID=[soft], address=[peer0.org1.example.com:7051]
6、部署Hyperledger Fabric cli 客戶端服務
1.在第一節點(172.31.1.89)只須要配置一個既可,其餘節點可不用部署,用於調用建立 channel 與 智能合約
#在/opt/soft目錄下，編寫docker-compose-peer.yaml，以下：
version: '2' services: cli: container_name: cli image: hyperledger/fabric-tools tty: true environment: - GOPATH=/opt/gopath - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock - CORE_LOGGING_LEVEL=DEBUG - CORE_PEER_ID=cli - CORE_PEER_ADDRESS=peer0.org1.example.com:7051 - CORE_PEER_LOCALMSPID=Org1MSP - CORE_PEER_TLS_ENABLED=false - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer volumes: - /etc/localtime:/etc/localtime:ro - /etc/timezone:/etc/timezone:ro - /var/run/:/host/var/run/ - /usr/local/go:/opt/go - /opt/gopath:/opt/gopath - ./chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/examples/chaincode/go - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts extra_hosts: - "orderer0.example.com:172.31.1.89" - "orderer1.example.com:172.31.1.90" - "orderer2.example.com:172.31.1.91" - "peer0.org1.example.com:172.31.1.89" - "peer1.org1.example.com:172.31.1.90" - "peer0.org2.example.com:172.31.1.91" - "peer1.org2.example.com:172.31.1.92" ##啓動服務 #docker-compose -f docker-compose-cli.yaml up -d
7、Hyperledger Fabric 建立 Channel
1.在第一節點(172.31.1.89),進入 cli 容器，咱們能夠直接進入 容器裏操做
[root@xxxxx soft]# docker exec -it cli bash root@77962643125a:/opt/gopath/src/github.com/hyperledger/fabric/peer#
# 執行 建立命令 (未開啓認證) #peer channel create -c mychannel -f ./channel-artifacts/channel.tx --orderer orderer0.example.com:7050
# 建立之後生成文件 mychannel.block
2.繼續在第一節點(172.31.1.89),cli 容器中，執行把現有全部節點服務peer節點加入到Channel中，示例現有4個peer
# peer0.org1.example.com 加入 此 channel 中，首先須要查看以下 環境變量
echo $CORE_PEER_LOCALMSPID echo $CORE_PEER_ADDRESS echo $CORE_PEER_TLS_ROOTCERT_FILE echo $CORE_PEER_MSPCONFIGPATH # echo $CORE_PEER_LOCALMSPID Org1MSP # echo $CORE_PEER_ADDRESS peer0.org1.example.com:7051 # echo $CORE_PEER_MSPCONFIGPATH /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp # echo $CORE_PEER_TLS_ROOTCERT_FILE /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
# 加入 channel #peer channel join -b mychannel.block 輸出： 2019-08-25 16:40:10.255 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-25 16:40:10.259 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-25 16:40:10.260 CST [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized 2019-08-25 16:40:10.371 CST [channelCmd] executeJoin -> INFO 004 Successfully submitted proposal to join channel
# peer1.org1.example.com 加入 此 channel 中，這裏配置一下環境變量
export CORE_PEER_LOCALMSPID="Org1MSP" export CORE_PEER_ADDRESS=peer1.org1.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp #peer channel join -b mychannel.block 輸出： 2019-08-25 16:43:09.353 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-25 16:43:09.357 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-25 16:43:09.358 CST [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized 2019-08-25 16:43:09.473 CST [channelCmd] executeJoin -> INFO 004 Successfully submitted proposal to join channe
# peer0.Org2.example.com 加入 此 channel 中，這裏配置一下環境變量
export CORE_PEER_LOCALMSPID="Org2MSP" export CORE_PEER_ADDRESS=peer0.org2.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp #peer channel join -b mychannel.block 輸出： 2019-08-25 16:45:17.626 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-25 16:45:17.630 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-25 16:45:17.632 CST [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized 2019-08-25 16:45:17.757 CST [channelCmd] executeJoin -> INFO 004 Successfully submitted proposal to join channel
# peer1.org2.example.com 加入 此 channel 中，這裏配置一下環境變量
export CORE_PEER_LOCALMSPID="Org2MSP" export CORE_PEER_ADDRESS=peer1.org2.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp #peer channel join -b mychannel.block 輸出： 2019-08-25 16:46:58.401 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-25 16:46:58.405 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-25 16:46:58.407 CST [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized 2019-08-25 16:46:58.523 CST [channelCmd] executeJoin -> INFO 004 Successfully submitted proposal to join channel
8、Hyperledger Fabric 錨節點
1.錨節點經過廣播的方式通知有新節點加入
# 使用Org1的管理員身份更新錨節點配置
# 一樣須要先配置變量
export CORE_PEER_LOCALMSPID="Org1MSP" export CORE_PEER_ADDRESS=peer0.org1.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
# 未開啓認證的方式 #peer channel update -o orderer0.example.com:7050 -c mychannel -f ./channel-artifacts/Org1MSPanchors.tx 輸出： 2019-08-25 16:49:42.877 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-25 16:49:42.881 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-25 16:49:42.882 CST [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized 2019-08-25 16:49:43.018 CST [channelCmd] update -> INFO 004 Successfully submitted channel update
# 使用Org2的管理員身份更新錨節點配置
# 一樣須要先配置變量
export CORE_PEER_LOCALMSPID="Org2MSP" export CORE_PEER_ADDRESS=peer0.org2.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp #peer channel update -o orderer0.example.com:7050 -c mychannel -f ./channel-artifacts/Org2MSPanchors.tx 輸出： 2019-08-25 16:52:44.317 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-25 16:52:44.321 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-25 16:52:44.322 CST [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized 2019-08-25 16:52:44.362 CST [channelCmd] update -> INFO 004 Successfully submitted channel update
##把當前cli環境變量恢復爲最初配置
export CORE_PEER_LOCALMSPID="Org1MSP" export CORE_PEER_ADDRESS=peer0.org1.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
9、Hyperledger Fabric 實例化測試
1.安裝智能合約
## cli 容器部分預先掛載了目錄： ./chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/examples/chaincode/go
#第一節點(172.31.1.89)拷貝了官方的例子，在 chaincode 下, 下面咱們來測試一下
#cd /opt/soft/ #[root@xxxx soft]# cp -r /opt/gopath/src/github.com/hyperledger/fabric/examples/chaincode/go/example0* ./chaincode/go/ [root@xxxx soft]# cd chaincode/go/ [root@xxx go]# ll total 20 drwxr-xr-x 3 root root 4096 Aug 25 16:57 example01 drwxr-xr-x 3 root root 4096 Aug 25 16:57 example02 drwxr-xr-x 3 root root 4096 Aug 25 16:57 example03 drwxr-xr-x 3 root root 4096 Aug 25 16:57 example04 drwxr-xr-x 3 root root 4096 Aug 25 16:57 example05
#這裏示例測試引用example02，須要對example02進行下面修改
# 注: 這裏面的 example02 的 package 爲 example02 會報錯
Error: could not assemble transaction, err Proposal response was not successful, error code 500, msg failed to execute transaction 819b581ce88604e9b6651764324876f2ca7a47d7aeb7ee307f273af867a4a134: error starting container: error starting container: API error (404): oci runtime error: container_linux.go:247: starting container process caused "exec: \"chaincode\": executable file not found in $PATH"
# 將 chaincode.go chaincode_test.go 中 package 修改爲 main 而後在最下面增長 main()函數
func main() {
err := shim.Start(new(SimpleChaincode))
if err != nil {
fmt.Printf("Error starting Simple chaincode: %s", err)
}
}
# 安裝指定合約到 全部的 peer 節點中，每一個節點都必須安裝一次
# 一樣須要先配置變量
##peer0.org1.example.com
export CORE_PEER_LOCALMSPID="Org1MSP" export CORE_PEER_ADDRESS=peer0.org1.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
# 安裝 合約 #peer chaincode install -n example2 -p github.com/hyperledger/fabric/examples/chaincode/go/example02 -v 1.0 輸出： 2019-08-25 17:09:28.929 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-25 17:09:28.933 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-25 17:09:28.936 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc 2019-08-25 17:09:28.937 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc 2019-08-25 17:09:30.612 CST [chaincodeCmd] install -> INFO 005 Installed remotely response:<status:200 payload:"OK" >
##peer1.org1.example.com
export CORE_PEER_LOCALMSPID="Org1MSP" export CORE_PEER_ADDRESS=peer1.org1.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp #peer chaincode install -n example2 -p github.com/hyperledger/fabric/examples/chaincode/go/example02 -v 1.0 輸出： 2019-08-25 17:13:15.194 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-25 17:13:15.197 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-25 17:13:15.201 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc 2019-08-25 17:13:15.201 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc 2019-08-25 17:13:15.544 CST [chaincodeCmd] install -> INFO 005 Installed remotely response:<status:200 payload:"OK" >
##peer0.org2.example.com
export CORE_PEER_LOCALMSPID="Org2MSP" export CORE_PEER_ADDRESS=peer0.org2.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp #peer chaincode install -n example2 -p github.com/hyperledger/fabric/examples/chaincode/go/example02 -v 1.0 輸出： 2019-08-25 17:15:16.573 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-25 17:15:16.577 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-25 17:15:16.581 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc 2019-08-25 17:15:16.581 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc 2019-08-25 17:15:16.860 CST [chaincodeCmd] install -> INFO 005 Installed remotely response:<status:200 payload:"OK" >
##peer1.org2.example.com
export CORE_PEER_LOCALMSPID="Org2MSP" export CORE_PEER_ADDRESS=peer1.org2.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp #peer chaincode install -n example2 -p github.com/hyperledger/fabric/examples/chaincode/go/example02 -v 1.0 輸出： 2019-08-25 17:16:43.117 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-25 17:16:43.121 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-25 17:16:43.124 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc 2019-08-25 17:16:43.124 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc 2019-08-25 17:16:43.396 CST [chaincodeCmd] install -> INFO 005 Installed remotely response:<status:200 payload:"OK" >
#恢復當前cli環境變量
export CORE_PEER_LOCALMSPID="Org1MSP" export CORE_PEER_ADDRESS=peer0.org1.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
10、實例化 Chaincode
1.第一節點(172.31.1.89)，進入cli容器,不管多少個 peer 節點, 實例化只須要實例化一次便可。
# 實例化合約 (未認證)
#peer chaincode instantiate -o orderer0.example.com:7050 -C mychannel -n example2 -c '{"Args":["init","A","200","B","500"]}' -P "OR ('Org1MSP.member','Org2MSP.member')" -v 1.0
輸出：
2019-08-25 17:19:32.439 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable
2019-08-25 17:19:32.443 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable
2019-08-25 17:19:32.447 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc
2019-08-25 17:19:32.447 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc
2.操做智能合約
# query 查詢方法
# 查詢 A 帳戶裏的餘額
#peer chaincode query -C mychannel -n example2 -c '{"Args":["query","A"]}'
輸出：
2019-08-25 17:25:55.246 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable
2019-08-25 17:25:55.250 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable
200
# 查詢 B 帳戶裏的餘額
#peer chaincode query -C mychannel -n example2 -c '{"Args":["query","B"]}'
輸出：
2019-08-25 17:31:17.138 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable
2019-08-25 17:31:17.143 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable
500
# invoke 轉帳方法
# 從A帳戶 轉帳 100 個幣 到 B 帳戶
#peer chaincode invoke -C mychannel -n example2 -c '{"Args":["invoke", "A", "B", "100"]}'
輸出：
2019-08-25 17:34:39.040 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable
2019-08-25 17:34:39.045 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable
2019-08-25 17:34:39.054 CST [chaincodeCmd] InitCmdFactory -> INFO 003 Retrieved channel (mychannel) orderer endpoint: orderer0.example.com:7050
2019-08-25 17:34:39.177 CST [chaincodeCmd] chaincodeInvokeOrQuery -> INFO 004 Chaincode invoke successful. result: status:200
# B 帳戶餘額
#peer chaincode query -C mychannel -n example2 -c '{"Args":["query","B"]}'
輸出：
2019-08-25 17:35:40.335 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable
2019-08-25 17:35:40.339 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable
600
# 查看 peer0.org1.example.com 節點裏 生成的容器
# docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES a32b63ecbc06 soft-peer0.org1.example.com-example2-1.0-d0878f91cfdef1f96b45622ea9fb58a5c15c5df7fa1c97e1f40fac8ce325793d "chaincode -peer.add…" 16 minutes ago Up 15 minutes soft-peer0.org1.example.com-example2-1.0
11、其餘Hyperledger Fabric 經常使用操做命令，或者--help參數參考
peer 命令
peer chaincode # 對鏈進行操做
peer channel # channel相關操做
peer logging # 設置日誌級別
peer node # 啓動、管理節點
peer version # 查看版本信息
# 查看 已經建立的 通道 (channel)
peer channel list
# 查看通道(channel) 的狀態 -c(小寫) 加 通道名稱
peer channel getinfo -c mychannel
# 查看已經 安裝的 智能合約(chincode)
peer chaincode list --installed
# 查看已經 實例化的 智能合約(chincode) 須要使用 -C(大寫) 加通道名稱
peer chaincode -C mychannel list --instantiated
12、###########如下爲測試驗證動態添加組織(未開啓tls認證)#############
場景：在已有上面2個組織，4個節點正在運行區塊鏈集羣網絡下，須要動態新增組織、節點
總結概括大體流程：
-->爲新 org 生成證書
-->爲新 org 生成配置文件
-->生成和提交新 org 的配置
--> peer channel fetch config 獲取當前通道信息，生成增量包
--> peer channel signconfigtx 爲配置交易簽名
--> peer channel update 提交簽名後的配置交易至 orderer
-->將新 org 添加入 channel 通道
-->啓動新 org 集羣
-->peer channel join 將新 org 下的 peer 加入 channel
-->升級chaincode和背書策略
-->peer chaincode install 爲新 org 的 peer 安裝 chaincode
-->peer chaincode install 爲原有org的peer升級 chaincode
-->peer chaincode upgrade 升級背書策略
-->交易查詢測試
1.初始化新增兩個節點服務器環境 (與上面節點服務器環境一致，如採用阿里雲ECS可克隆其餘服務器配置好的鏡像做爲自定義鏡像)，模擬新增org3組織，新增兩個節點hosts 映射以下：
172.31.1.101 peer0.org3.example.com
172.31.1.102 peer1.org3.example.com
2.在第一節點(172.31.1.89)服務器上，從新生成證書文件,
#進入/opt/soft目錄，存在crypto-config.yaml、configtx.yaml原先配置文件
#cd /opt/soft
# 拷貝 crypto-config.yaml 新建一個證書配置文件，命名爲crypto-config-org3.yaml，並修改成以下：
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#
PeerOrgs:
# ---------------------------------------------------------------------------
# Org3
# ---------------------------------------------------------------------------
- Name: Org3
Domain: org3.example.com
EnableNodeOUs: true
CA:
Country: CN
Province: GuangDong
Locality: ShenZhen
# ---------------------------------------------------------------------------
# "Specs"
# ---------------------------------------------------------------------------
# Uncomment this section to enable the explicit definition of hosts in your
# configuration. Most users will want to use Template, below
#
# Specs is an array of Spec entries. Each Spec entry consists of two fields:
# - Hostname: (Required) The desired hostname, sans the domain.
# - CommonName: (Optional) Specifies the template or explicit override for
# the CN. By default, this is the template:
#
# "{{.Hostname}}.{{.Domain}}"
#
# which obtains its values from the Spec.Hostname and
# Org.Domain, respectively.
# ---------------------------------------------------------------------------
# Specs:
# - Hostname: foo # implicitly "foo.org1.example.com"
# CommonName: foo27.org5.example.com # overrides Hostname-based FQDN set above
# - Hostname: bar
# - Hostname: baz
# ---------------------------------------------------------------------------
# "Template"
# ---------------------------------------------------------------------------
# Allows for the definition of 1 or more hosts that are created sequentially
# from a template. By default, this looks like "peer%d" from 0 to Count-1.
# You may override the number of nodes (Count), the starting index (Start)
# or the template used to construct the name (Hostname).
#
# Note: Template and Specs are not mutually exclusive. You may define both
# sections and the aggregate nodes will be created for you. Take care with
# name collisions
# ---------------------------------------------------------------------------
Template:
Count: 2
# Start: 5
# Hostname: {{.Prefix}}{{.Index}} # default
# ---------------------------------------------------------------------------
# "Users"
# ---------------------------------------------------------------------------
# Count: The number of user accounts _in addition_ to Admin
# ---------------------------------------------------------------------------
Users:
Count: 1
##獲取新增組織證書 [root@xxxx soft]#cryptogen generate --config=./crypto-config-org3.yaml org3.example.com
##在configtx.yaml配置文件中新增建立通道的一些組織信息，新增組織在Organizations段中寫明，最後只增長了一個Org3
- &Org3 # DefaultOrg defines the organization which is used in the sampleconfig # of the fabric.git development environment Name: Org3MSP # ID to load the MSP definition as ID: Org3MSP MSPDir: crypto-config/peerOrganizations/org3.example.com/msp AnchorPeers: # AnchorPeers defines the location of peers which can be used # for cross org gossip communication. Note, this value is only # encoded in the genesis block in the Application section context - Host: peer0.org3.example.com Port: 7051
#######如下是建立新通道部分,本示例不示範################
對於新增通道，通道文件建立依賴於profiles，根據本身須要添加不一樣組織
Profiles: TwoOrgsOrdererGenesis: Capabilities: <<: *ChannelCapabilities Orderer: <<: *OrdererDefaults Organizations: - *OrdererOrg Capabilities: <<: *OrdererCapabilities Consortiums: SampleConsortium: Organizations: - *Org1 - *Org2 TwoOrgsChannel: Consortium: SampleConsortium Application: <<: *ApplicationDefaults Organizations: - *Org1 - *Org2 Capabilities: <<: *ApplicationCapabilities NewOrgsChannel: Consortium: SampleConsortium Application: <<: *ApplicationDefaults Organizations: - *Org1 - *Org2 - *Org3 Capabilities: <<: *ApplicationCapabilities OneOrgsChannel: Consortium: SampleConsortium Application: <<: *ApplicationDefaults Organizations: - *Org3 Capabilities: <<: *ApplicationCapabilities ##獲取通道更新增量包 ##根據新增組織獲取組織信息，注意Org3Msp必須與你在configtx.yaml中新增組織名稱一致 #configtxgen -printOrg Org3MSP -profile ./configtx.yaml > channel-artifacts/org3.json 輸出： 2019-08-28 17:47:50.947 CST [common.tools.configtxgen] main -> INFO 001 Loading configuration 2019-08-28 17:47:50.958 CST [common.tools.configtxgen.localconfig] completeInitialization -> INFO 002 orderer type: kafka 2019-08-28 17:47:50.958 CST [common.tools.configtxgen.localconfig] LoadTopLevel -> INFO 003 Loaded configuration: /opt/soft/configtx.yaml [root@xxx channel-artifacts]# ll -rw-r--r-- 1 root root 346 Aug 25 02:26 channel.tx -rw-r--r-- 1 root root 12906 Aug 25 02:25 genesis.block -rw-r--r-- 1 root root 284 Aug 25 02:28 Org1MSPanchors.tx -rw-r--r-- 1 root root 284 Aug 25 02:28 Org2MSPanchors.tx -rw-r--r-- 1 root root 8484 Aug 28 17:47 org3.json
3.進入cli容器，拉取通道二進制文件而且轉換爲json格式
#docker exec -it cli bash
#認證未開啓 如tls是關閉的，執行 #peer channel fetch config mychannel.pb -o orderer0.example.com:7050 -c mychannel #configtxlator proto_decode --input mychannel.pb --type common.Block | jq .data.data[0].payload.data.config > mychannel.json
#將以前獲取的新增組織信息加入到通道信息json文件
#jq -s '.[0] * {"channel_group":{"groups":{"Application":{"groups": {"Org3MSP":.[1]}}}}}' mychannel.json ./channel-artifacts/org3.json > mychannel_config.json
輸出：
root@ae3f95d0f32d:/opt/gopath/src/github.com/hyperledger/fabric/peer# ll
.............
drwxr-xr-x 2 root root 4096 Aug 25 02:06 mocks/
-rw-r--r-- 1 root root 15874 Aug 25 16:28 mychannel.block
-rw-r--r-- 1 root root 35653 Aug 28 18:09 mychannel.json
-rw-r--r-- 1 root root 16869 Aug 28 18:07 mychannel.pb
-rw-r--r-- 1 root root 46704 Aug 28 18:24 mychannel_config.json
#把更新先後的文件打包成二進制文件
#configtxlator proto_encode --input mychannel.json --type common.Config > original_mychannel.pb #configtxlator proto_encode --input mychannel_config.json --type common.Config > modified_mychannel.pb 輸出： root@ae3f95d0f32d:/opt/gopath/src/github.com/hyperledger/fabric/peer# ll .............. drwxr-xr-x 2 root root 4096 Aug 25 02:06 mocks/ -rw-r--r-- 1 root root 17369 Aug 28 18:26 modified_mychannel.pb -rw-r--r-- 1 root root 15874 Aug 25 16:28 mychannel.block -rw-r--r-- 1 root root 35653 Aug 28 18:09 mychannel.json -rw-r--r-- 1 root root 16869 Aug 28 18:07 mychannel.pb -rw-r--r-- 1 root root 46704 Aug 28 18:24 mychannel_config.json drwxr-xr-x 3 root root 4096 Aug 25 02:06 node/ -rw-r--r-- 1 root root 12853 Aug 28 18:26 original_mychannel.pb
#獲取增量包而且補全，轉換成二進制文件
#configtxlator compute_update --channel_id mychannel --original original_mychannel.pb --updated modified_mychannel.pb > mychannel_update.pb
#configtxlator proto_decode --input mychannel_update.pb --type common.ConfigUpdate > mychannel_update.json
#echo '{"payload":{"header":{"channel_header":{"channel_id":"mychannel", "type":2}},"data":{"config_update":'$(cat mychannel_update.json)'}}}' | jq . > mychannel_update_envelope.json
#configtxlator proto_encode --input mychannel_update_envelope.json --type common.Envelope > mychannel_update_Org_envelope.pb
輸出：
root@ae3f95d0f32d:/opt/gopath/src/github.com/hyperledger/fabric/peer# ll
..............
-rw-r--r-- 1 root root 1561 Aug 25 02:06 main_test.go
drwxr-xr-x 2 root root 4096 Aug 25 02:06 mocks/
-rw-r--r-- 1 root root 17369 Aug 28 18:26 modified_mychannel.pb
-rw-r--r-- 1 root root 15874 Aug 25 16:28 mychannel.block
-rw-r--r-- 1 root root 35653 Aug 28 18:09 mychannel.json
-rw-r--r-- 1 root root 16869 Aug 28 18:07 mychannel.pb
-rw-r--r-- 1 root root 46704 Aug 28 18:24 mychannel_config.json
-rw-r--r-- 1 root root 11149 Aug 28 18:28 mychannel_update.json
-rw-r--r-- 1 root root 4751 Aug 28 18:28 mychannel_update.pb
-rw-r--r-- 1 root root 4777 Aug 28 18:29 mychannel_update_Org_envelope.pb
-rw-r--r-- 1 root root 15177 Aug 28 18:28 mychannel_update_envelope.json
drwxr-xr-x 3 root root 4096 Aug 25 02:06 node/
-rw-r--r-- 1 root root 12853 Aug 28 18:26 original_mychannel.pb
4.原有組織對新加組織進行簽名已獲取承認，必須使用Org1MSP、Org2MSP admin用戶
export CORE_PEER_LOCALMSPID="Org1MSP" export CORE_PEER_ADDRESS=peer0.org1.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp #peer channel signconfigtx -f mychannel_update_Org_envelope.pb 輸出： 2019-08-28 18:52:07.273 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 18:52:07.277 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 18:52:07.277 CST [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized export CORE_PEER_LOCALMSPID="Org2MSP" export CORE_PEER_ADDRESS=peer0.org2.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp #peer channel signconfigtx -f mychannel_update_Org_envelope.pb 輸出： 2019-08-28 18:53:15.765 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 18:53:15.770 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 18:53:15.770 CST [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized
5.獲取簽名以後通知orderer更新通道信息
#未開啓認證 #peer channel update -f mychannel_update_Org_envelope.pb -c mychannel -o orderer0.example.com:7050 報錯： 2019-08-28 18:59:52.082 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 18:59:52.086 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable Error: failed to create deliver client: orderer client failed to connect to orderer0.exeample.com:7050: failed to create new connection: context deadline exceeded 解決方案：發現寫錯了orderer0.exeample.com:7050，實際上是orderer0.example.com:7050 修正後輸出： 2019-08-28 19:17:33.604 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 19:17:33.608 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 19:17:33.609 CST [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized 2019-08-28 19:17:33.747 CST [channelCmd] update -> INFO 004 Successfully submitted channel update
6.配置org3的yaml文件，並上傳172.31.1.10一、172.31.1.102服務器，啓動服務。
#172.31.1.101 --->peer0.org3.example.com----->docker-compose-peer.yaml
#新增172.31.1.101節點，docker-compose-peer.yaml文件配置以下：
version: '2' services: couchdb4: container_name: couchdb4 image: hyperledger/fabric-couchdb environment: - COUCHDB_USER= - COUCHDB_PASSWORD= ports: - "5984:5984" volumes: # 數據持久化，用於存儲鏈碼值 - /mnt/data/couchdb4/data:/opt/couchdb/data peer0.org3.example.com: container_name: peer0.org3.example.com hostname: peer0.org3.example.com image: hyperledger/fabric-peer environment: - CORE_LEDGER_STATE_STATEDATABASE=CouchDB - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb4:5984 - CORE_PEER_ID=peer0.org3.example.com - CORE_PEER_NETWORKID=soft - CORE_PEER_ADDRESS=peer0.org3.example.com:7051 - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org3.example.com:7051 - CORE_PEER_LOCALMSPID=Org3MSP - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=soft - CORE_LOGGING_LEVEL=DEBUG - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=soft_default - CORE_PEER_GOSSIP_SKIPHANDSHAKE=true - CORE_PEER_GOSSIP_USELEADERELECTION=true - CORE_PEER_GOSSIP_ORGLEADER=false - CORE_PEER_PROFILE_ENABLED=false - CORE_CHAINCODE_EXECUTETIMEOUT=1000s - CORE_CHAINCODE_DEPLOYTIMEOUT=1000s - CORE_PEER_TLS_ENABLED=false - 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 working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer command: peer node start volumes: - /etc/localtime:/etc/localtime:ro - /etc/timezone:/etc/timezone:ro - /var/run/:/host/var/run/ - /var/hyperledger/peer_data/:/var/hyperledger/production/ - ./crypto-config/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/msp:/etc/hyperledger/fabric/msp - ./crypto-config/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/tls:/etc/hyperledger/fabric/tls ports: - 7051:7051 - 7052:7052 - 7053:7053 depends_on: - couchdb4 extra_hosts: - "couchdb4:172.31.1.101" - "orderer0.example.com:172.31.1.89" - "orderer1.example.com:172.31.1.90" - "orderer2.example.com:172.31.1.91"
#172.31.1.102 --->peer1.org3.example.com----->docker-compose-peer.yaml
#新增172.31.1.102節點，docker-compose-peer.yaml文件配置以下：
version: '2' services: couchdb5: container_name: couchdb5 image: hyperledger/fabric-couchdb environment: - COUCHDB_USER= - COUCHDB_PASSWORD= ports: - "5984:5984" volumes: # 數據持久化，用於存儲鏈碼值 - /mnt/data/couchdb5/data:/opt/couchdb/data peer1.org3.example.com: container_name: peer1.org3.example.com hostname: peer1.org3.example.com image: hyperledger/fabric-peer environment: - CORE_LEDGER_STATE_STATEDATABASE=CouchDB - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb5:5984 - CORE_PEER_ID=peer1.org3.example.com - CORE_PEER_NETWORKID=soft - CORE_PEER_ADDRESS=peer1.org3.example.com:7051 - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org3.example.com:7051 - CORE_PEER_LOCALMSPID=Org3MSP - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=soft - CORE_LOGGING_LEVEL=DEBUG - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=soft_default - CORE_PEER_GOSSIP_SKIPHANDSHAKE=true - CORE_PEER_GOSSIP_USELEADERELECTION=true - CORE_PEER_GOSSIP_ORGLEADER=false - CORE_PEER_PROFILE_ENABLED=false - CORE_CHAINCODE_EXECUTETIMEOUT=1000s - CORE_CHAINCODE_DEPLOYTIMEOUT=1000s - CORE_PEER_TLS_ENABLED=false - 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 working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer command: peer node start volumes: - /etc/localtime:/etc/localtime:ro - /etc/timezone:/etc/timezone:ro - /var/run/:/host/var/run/ - /var/hyperledger/peer_data/:/var/hyperledger/production/ - ./crypto-config/peerOrganizations/org3.example.com/peers/peer1.org3.example.com/msp:/etc/hyperledger/fabric/msp - ./crypto-config/peerOrganizations/org3.example.com/peers/peer1.org3.example.com/tls:/etc/hyperledger/fabric/tls ports: - 7051:7051 - 7052:7052 - 7053:7053 depends_on: - couchdb5 extra_hosts: - "couchdb5:172.31.1.102" - "orderer0.example.com:172.31.1.89" - "orderer1.example.com:172.31.1.90" - "orderer2.example.com:172.31.1.91"
#從 172.31.1.89 節點/opt/soft，拷貝channel-artifacts，crypto-config 目錄文件 至172.31.1.10一、172.31.1.102服務器，/opt/soft目錄下
scp -r crypto-config channel-artifacts root@172.31.1.101:/opt/soft scp -r crypto-config channel-artifacts root@172.31.1.102:/opt/soft
#更新其餘全部節點服務器的channel-artifacts，crypto-config，防止peer或orderer發生重啓時加載不到最新文件
scp -r crypto-config channel-artifacts root@172.31.1.90:/opt/soft scp -r crypto-config channel-artifacts root@172.31.1.91:/opt/soft scp -r crypto-config channel-artifacts root@172.31.1.92:/opt/soft
#啓動 #docker-compose -f docker-compose-peer.yaml up -d
7.修改第一節點(172.31.1.89),/opt/soft目錄下對 docker-compose-cli.yaml 文件增長配置修改，並重啓cli服務
#修改增長peer0.org3.example.com:172.31.1.10一、peer1.org3.example.com:172.31.1.102 extra_hosts
extra_hosts: - "orderer0.example.com:172.31.1.89" - "orderer1.example.com:172.31.1.90" - "orderer2.example.com:172.31.1.91" - "peer0.org1.example.com:172.31.1.89" - "peer1.org1.example.com:172.31.1.90" - "peer0.org2.example.com:172.31.1.91" - "peer1.org2.example.com:172.31.1.92" - "peer0.org3.example.com:172.31.1.101" - "peer1.org3.example.com:172.31.1.102"
#重啓構建 #docker-compose -f docker-compose-cli.yaml up -d
8.Org3MSP加入通道 ，進入172.31.1.89 cli容器
#切換到org3的節點上環境變量而後執行peer channel join 加入通道
export CORE_PEER_LOCALMSPID="Org3MSP" export CORE_PEER_ADDRESS=peer0.org3.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org3.example.com/users/Admin@org3.example.com/msp #peer channel join -b mychannel.block 輸出： 2019-08-28 20:24:13.880 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 20:24:13.884 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 20:24:13.885 CST [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized 2019-08-28 20:24:14.104 CST [channelCmd] executeJoin -> INFO 004 Successfully submitted proposal to join channel
9.更新鏈碼 (全部peer節點(現有6個節點)上的鏈碼都必須從新安裝！！！！！)
#在新增org3的全部節點上安裝鏈碼，版本號爲2.0(注意是全部節點都要)
#peer0.org3.example.com export CORE_PEER_LOCALMSPID="Org3MSP" export CORE_PEER_ADDRESS=peer0.org3.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org3.example.com/peers/peer0.org3.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org3.example.com/users/Admin@org3.example.com/msp peer chaincode install -n example2 -p github.com/hyperledger/fabric/examples/chaincode/go/example02 -v 2.0 輸出： 2019-08-28 20:28:33.592 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 20:28:33.596 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 20:28:33.600 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc 2019-08-28 20:28:33.600 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc 2019-08-28 20:28:33.903 CST [chaincodeCmd] install -> INFO 005 Installed remotely response:<status:200 payload:"OK" > #peer1.org3.example.com export CORE_PEER_LOCALMSPID="Org3MSP" export CORE_PEER_ADDRESS=peer1.org3.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org3.example.com/peers/peer1.org3.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org3.example.com/users/Admin@org3.example.com/msp #peer chaincode install -n example2 -p github.com/hyperledger/fabric/examples/chaincode/go/example02 -v 2.0 輸出： 2019-08-28 20:33:16.276 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 20:33:16.280 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 20:33:16.284 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc 2019-08-28 20:33:16.284 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc 2019-08-28 20:33:16.565 CST [chaincodeCmd] install -> INFO 005 Installed remotely response:<status:200 payload:"OK" > #切換環境變量到原有的org1和org2上分別全部節點更新鏈碼，版本號必須對應(注意是全部節點都要更新) #切換到org1環境變量 peer0.org1.example.com export CORE_PEER_LOCALMSPID="Org1MSP" export CORE_PEER_ADDRESS=peer0.org1.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp #peer chaincode install -n example2 -p github.com/hyperledger/fabric/examples/chaincode/go/example02 -v 2.0 輸出： 2019-08-28 20:36:58.948 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 20:36:58.952 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 20:36:58.955 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc 2019-08-28 20:36:58.955 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc 2019-08-28 20:36:59.228 CST [chaincodeCmd] install -> INFO 005 Installed remotely response:<status:200 payload:"OK" > peer1.org1.example.com export CORE_PEER_LOCALMSPID="Org1MSP" export CORE_PEER_ADDRESS=peer1.org1.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer1.org1.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp #peer chaincode install -n example2 -p github.com/hyperledger/fabric/examples/chaincode/go/example02 -v 2.0 輸出： 2019-08-28 20:38:04.091 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 20:38:04.095 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 20:38:04.098 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc 2019-08-28 20:38:04.098 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc 2019-08-28 20:38:04.372 CST [chaincodeCmd] install -> INFO 005 Installed remotely response:<status:200 payload:"OK" peer0.org2.example.com export CORE_PEER_LOCALMSPID="Org2MSP" export CORE_PEER_ADDRESS=peer0.org2.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp #peer chaincode install -n example2 -p github.com/hyperledger/fabric/examples/chaincode/go/example02 -v 2.0 輸出： 2019-08-28 20:39:35.826 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 20:39:35.830 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 20:39:35.834 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc 2019-08-28 20:39:35.834 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc 2019-08-28 20:39:36.110 CST [chaincodeCmd] install -> INFO 005 Installed remotely response:<status:200 payload:"OK" > peer1.org2.example.com export CORE_PEER_LOCALMSPID="Org2MSP" export CORE_PEER_ADDRESS=peer1.org2.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer1.org2.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp #peer chaincode install -n example2 -p github.com/hyperledger/fabric/examples/chaincode/go/example02 -v 2.0 輸出： 2019-08-28 20:40:35.467 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 20:40:35.471 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable 2019-08-28 20:40:35.475 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc 2019-08-28 20:40:35.475 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc 2019-08-28 20:40:35.747 CST [chaincodeCmd] install -> INFO 005 Installed remotely response:<status:200 payload:"OK" >
10.更新背書策略，在原有的兩個組織策略上增長新增組織
#第一節點(172.31.1.89),進入cli 容器，切換到org1環境變量
peer0.org1.example.com export CORE_PEER_LOCALMSPID="Org1MSP" export CORE_PEER_ADDRESS=peer0.org1.example.com:7051 export CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
#認證未開啓
#peer chaincode upgrade -o orderer0.example.com:7050 -C mychannel -n example2 -v 2.0 -c '{"Args":["init","A","100","B","50"]}' -P "OR ('Org1MSP.peer','Org2MSP.peer','Org3MSP.peer')"
# 舊版本的合約, 目前，fabric不支持合約的啓動與暫停。要暫停或刪除合約，只能到peer上手動刪除容器。
2019-08-28 20:47:05.750 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable
2019-08-28 20:47:05.754 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable
2019-08-28 20:47:05.758 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc
2019-08-28 20:47:05.758 CST [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc
11.測試查詢
# 這裏再查詢 A 與 B 的帳戶
# A 帳戶餘額
#peer chaincode query -C mychannel -n example2 -c '{"Args":["query","A"]}'
輸出：
2019-08-28 20:49:13.846 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable
2019-08-28 20:49:13.850 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable
100
# peer chaincode query -C mychannel -n example2 -c '{"Args":["query","B"]}'
輸出：
2019-08-28 20:49:31.416 CST [main] InitCmd -> WARN 001 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable
2019-08-28 20:49:31.420 CST [main] SetOrdererEnv -> WARN 002 CORE_LOGGING_LEVEL is no longer supported, please use the FABRIC_LOGGING_SPEC environment variable
50
12.(非必要)暴露相應排序orderer/peer對外地址，可供外部SDK訪問上鍊
orderer0.example.com 7050 112.xxx.xxx.xxx:13150 orderer1.example.com 7050 112.xxx.xxx.xxx:13151 orderer2.example.com 7050 112.xxx.xxx.xxx:13152 peer0.org1.example.com 7051 112.xxx.xxx.xxx:13250 peer1.org1.example.com 7051 112.xxx.xxx.xxx:13251 peer0.org2.example.com 7051 112.xxx.xxx.xxx:13252 peer1.org2.example.com 7051 112.xxx.xxx.xxx:13253
相關文章
- 1. HyperLedger Fabric 1.4 生產環境動態添加組織及節點
- 2. fabric-sdk-java 動態添加組織
- 3. fabric組織動態添加peer
- 4. fabric-1.1多機多節點部署
- 5. 集中管理服務器 PUPPET（一） 部署 與 添加節點
- 6. hyperledger fabric 1.4 動態添加組織之 eyfn.sh詳解
- 7. linux jenkins添加windows節點，實現自動化部署
- 8. 基於Hyperledger Fabric的多節點部署
- 9. 《HyperLedger Fabric 實戰》—— 4、Fabric Solo 單機多節點部署
- 10. Hyperledger Fabric 1.0 快速搭建 -------- 多機部署 Fabric CA節點服務
- 更多相關文章...
- • 啓動MySQL服務 - MySQL教程
- • SVN 啓動模式 - SVN 教程
- • Spring Cloud 微服務實戰(三) - 服務註冊與發現
- • 使用阿里雲OSS+CDN部署前端頁面與加速靜態資源
相關標籤/搜索
每日一句
-
每一个你不满意的现在，都有一个你没有努力的曾经。
最新文章
- 1. Duang!超快Wi-Fi來襲
- 2. 機器學習-補充03 神經網絡之**函數(Activation Function)
- 3. git上開源maven項目部署 多module maven項目（多module maven+redis+tomcat+mysql）後臺部署流程學習記錄
- 4. ecliple-tomcat部署maven項目方式之一
- 5. eclipse新導入的項目經常可以看到「XX cannot be resolved to a type」的報錯信息
- 6. Spark RDD的依賴於DAG的工作原理
- 7. VMware安裝CentOS-8教程詳解
- 8. YDOOK：Java 項目 Spring 項目導入基本四大 jar 包 導入依賴，怎樣在 IDEA 的項目結構中導入 jar 包 導入依賴
- 9. 簡單方法使得putty（windows10上）可以免密登錄樹莓派
- 10. idea怎麼用本地maven
歡迎關注本站公眾號,獲取更多信息
相關文章
- 1. HyperLedger Fabric 1.4 生產環境動態添加組織及節點
- 2. fabric-sdk-java 動態添加組織
- 3. fabric組織動態添加peer
- 4. fabric-1.1多機多節點部署
- 5. 集中管理服務器 PUPPET（一） 部署 與 添加節點
- 6. hyperledger fabric 1.4 動態添加組織之 eyfn.sh詳解
- 7. linux jenkins添加windows節點，實現自動化部署
- 8. 基於Hyperledger Fabric的多節點部署
- 9. 《HyperLedger Fabric 實戰》—— 4、Fabric Solo 單機多節點部署
- 10. Hyperledger Fabric 1.0 快速搭建 -------- 多機部署 Fabric CA節點服務