Ubuntu16.4部署fabric1.4+kafka集群最新最完整

最新推荐文章于 2022-04-22 21:31:09 发布
最新推荐文章于 2022-04-22 21:31:09 发布
阅读量720 收藏 1
点赞数 1
版权声明：本文为博主原创文章，遵循 CC 4.0 BY 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/Doudou_Mylove/article/details/103889945
版权
 
环境角色规划如下，7台服务器hosts文件统一配置：
vim /etc/hosts
10.12.237.103     orderer0.example.com
10.12.236.210     orderer1.example.com
10.12.237.112     orderer2.example.com
10.12.237.114     peer0.org1.example.com
10.12.237.120     peer1.org1.example.com
10.12.237.127     peer0.org2.example.com
10.12.237.132     peer1.org2.example.com
10.12.237.114     kafka0
10.12.237.120     kafka1
10.12.237.127     kafka2
10.12.237.132     kafka3
10.12.237.103     zookeeper0
10.12.236.210     zookeeper1
10.12.237.112     zookeeper2
 
 
第一步：更换apt源：
 
cd /etc/apt/
cp sources.list sources.list.bak
>sources.list
 
vim sources.list
deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ xenial main restricted universe multiverse
# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ xenial main restricted universe multiverse
deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ xenial-updates main restricted universe multiverse
# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ xenial-updates main restricted universe multiverse
deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ xenial-backports main restricted universe multiverse
# deb-src https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ xenial-backports main restricted universe multiverse
deb https://mirrors.tuna.tsinghua.edu.cn/ubuntu/ xenial-security main restricted universe multiverse
# deb-src [arch=amd64] https://mirrors.tuna.tsinghua.edu.cn/docker-ce/linux/ubuntu xenial stable
deb [arch=amd64] https://mirrors.tuna.tsinghua.edu.cn/docker-ce/linux/ubuntu xenial stable
 
apt-get update
这步报错:
........
gn:5 https://mirrors.tuna.tsinghua.edu.cn/docker-ce/linux/ubuntu xenial InRelease
Fetched 66.2 kB in 21s (3,031 B/s)
Reading package lists... Done
W: GPG error: https://mirrors.tuna.tsinghua.edu.cn/docker-ce/linux/ubuntu xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7EA0A9C3F273FCD8
W: The repository 'https://mirrors.tuna.tsinghua.edu.cn/docker-ce/linux/ubuntu xenial InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
 
解决方法：执行下面命令并重新update：
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 7EA0A9C3F273FCD8
apt-get update
 
#update成功之后所有参与服务器执行第一步：
scp sources.list 10.12.237.103:/etc/apt/
scp sources.list 10.12.237.112:/etc/apt/
scp sources.list 10.12.237.114:/etc/apt/
scp sources.list 10.12.237.120:/etc/apt/
scp sources.list 10.12.237.127:/etc/apt/
scp sources.list 10.12.237.132:/etc/apt/
 
 
第二步：安装开发软件（docker，docker-compose，nodejs,go）
docker：
cd
sudo apt-get -y install apt-transport-https ca-certificates curl gnupg-agent software-properties-common
curl -fsSL http://mirrors.aliyun.com/docker-ce/linux/ubuntu/gpg | sudo apt-key add -
add-apt-repository "deb [arch=amd64] http://mirrors.aliyun.com/docker-ce/linux/ubuntu $(lsb_release -cs) stable"
apt-get update
apt-cache madison docker-ce
apt-get -y install docker-ce=5:18.09.6~3-0~ubuntu-xenial docker-ce-cli=5:18.09.6~3-0~ubuntu-xenial containerd.io
sudo systemctl start docker
sudo systemctl enable docker
sudo systemctl status docker
 
docker-compose：
apt-get update
cd /var/lib/dpkg
mv info info.baksudo
mkdir info
apt-get -y install python3-pip
pip3 -v
pip3 install --default-timeout=100 --upgrade pip
pip -V
apt-get update
pip install docker-compose==1.24.0
 
nodejs：
apt-get update
curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash -
apt-get install -y nodejs
 
go：
cd /opt
mkdir golang
cd golang
wget https://dl.google.com/go/go1.12.9.linux-amd64.tar.gz
tar -zxvf go1.12.9.linux-amd64.tar.gz
vim /etc/profile
export GOPATH=/opt/gopath
export GOROOT=/opt/golang/go
export PATH=$GOROOT/bin:$PATH
source /etc/profile
 
依赖工具：
apt-get install  libtool libltdl-dev -y
 
 
第三步：所有服务器下载镜像，（可以选择部分所需）
chmod +x ./bootstrap.sh
#执行脚本之前要修改脚本内容： 这里用fabric1.4.0的版本，修改内容为标红处
 
 
./bootstrap.sh
 
第四步：所有服务器创建kafkapeer目录
mkdir -p $GOPATH/src/ github.com/hyperledger/
cd $GOPATH/src/ github.com/hyperledger/
mkdir -p fabric/kafkapeer
 
第五步：生成证书和区块配置文件，先在第一台peer服务器操作（ 10.12.237.114     peer0.org1.example.com ）
#共两个文件，下载镜像的脚本执行完成之后会生成一个fabric-samples目录，下层的basic-network目录下就有这两个文件，需要修改
 
cd $GOPATH/src/ github.com/hyperledger/fabric/kafkapeer
 
vim crypto-config.yaml 
OrdererOrgs:
 - Name: Orderer
   Domain: example.com
   CA:
       Country: US
       Province: California
       Locality: San Francisco
   Specs:
     - Hostname: orderer0
     - Hostname: orderer1
     - Hostname: orderer2
PeerOrgs:
 - Name: Org1
   Domain: org1.example.com
   EnableNodeOUs: true
   CA:
       Country: US
       Province: California
       Locality: San Francisco
   Template:
     Count: 2
   Users:
     Count: 1
 - Name: Org2
   Domain: org2.example.com
   EnableNodeOUs: true
   CA:
       Country: US
       Province: California
       Locality: San Francisco
   Template:
     Count: 2
   Users:
     Count: 1

vim configtx.yaml

---
Organizations:
   - &OrdererOrg
       Name: OrdererOrg
       ID: OrdererMSP
       MSPDir: crypto-config/ordererOrganizations/example.com/msp
       Policies:
           Readers:
               Type: Signature
               Rule: "OR('OrdererMSP.member')"
           Writers:
               Type: Signature
               Rule: "OR('OrdererMSP.member')"
           Admins:
               Type: Signature
               Rule: "OR('OrdererMSP.admin')"
   - &Org1
       Name: Org1MSP
       ID: Org1MSP
       MSPDir: crypto-config/peerOrganizations/org1.example.com/msp
       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:
           - Host: peer0.org1.example.com
             Port: 7051
   - &Org2
       Name: Org2MSP
       ID: Org2MSP
       MSPDir: crypto-config/peerOrganizations/org2.example.com/msp
       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:
           - Host: peer0.org2.example.com
             Port: 7051
Capabilities:
   Global: &ChannelCapabilities
       V1_1: true
   Orderer: &OrdererCapabilities
       V1_1: true
   Application: &ApplicationCapabilities
       V1_2: true
Application: &ApplicationDefaults
   Organizations:
   Policies:
       Readers:
           Type: ImplicitMeta
           Rule: "ANY Readers"
       Writers:
           Type: ImplicitMeta
           Rule: "ANY Writers"
       Admins:
           Type: ImplicitMeta
           Rule: "MAJORITY Admins"
   Capabilities:
       <<: *ApplicationCapabilities
Orderer: &OrdererDefaults
   OrdererType: kafka
   Addresses:
       - orderer0.example.com:7050
       - orderer1.example.com:7050
       - orderer2.example.com:7050
   BatchTimeout: 2s
   BatchSize:
       MaxMessageCount: 10
       AbsoluteMaxBytes: 98 MB
       PreferredMaxBytes: 512 KB
   Kafka:
       Brokers:
           - kafka0:9092
           - kafka1:9092
           - kafka2:9092
           - kafka3:9092
   Organizations:
   Policies:
       Readers:
           Type: ImplicitMeta
           Rule: "ANY Readers"
       Writers:
           Type: ImplicitMeta
           Rule: "ANY Writers"
       Admins:
           Type: ImplicitMeta
           Rule: "MAJORITY Admins"
       BlockValidation:
           Type: ImplicitMeta
           Rule: "ANY Writers"
   Capabilities:
       <<: *OrdererCapabilities
Channel: &ChannelDefaults
   Policies:
       Readers:
           Type: ImplicitMeta
           Rule: "ANY Readers"
       Writers:
           Type: ImplicitMeta
           Rule: "ANY Writers"
       Admins:
           Type: ImplicitMeta
           Rule: "MAJORITY Admins"
   Capabilities:
       <<: *ChannelCapabilities
Profiles:
   TwoOrgsOrdererGenesis:
       <<: *ChannelDefaults
       Orderer:
           <<: *OrdererDefaults
           Organizations:
               - *OrdererOrg
       Consortiums:
           SampleConsortium:
               Organizations:
                   - *Org1
                   - *Org2
   TwoOrgsChannel:
       Consortium: SampleConsortium
       Application:
           <<: *ApplicationDefaults
           Organizations:
               - *Org1
               - *Org2

生成公私钥和证书

cd $GOPATH/src/ github.com/hyperledger/fabric/kafkapeer
./bin/cryptogen generate --config=./crypto-config.yaml
 
生成创世区块
mkdir channel-artifacts
./bin/configtxgen -profile TwoOrgsOrdererGenesis -outputBlock ./channel-artifacts/genesis.block
 
 
生成通道配置区块
./bin/configtxgen -profile TwoOrgsChannel -outputCreateChannelTx ./channel-artifacts/mychannel.tx -channelID mychannel
 
生成锚节点配置文件
./bin/configtxgen -profile TwoOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org1MSPanchors.tx -channelID mychannel -asOrg Org1MSP
./bin/configtxgen -profile TwoOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org2MSPanchors.tx -channelID mychannel -asOrg Org2MSP
 
 
拷贝生成文件到其它服务器
scp -r ../kafkapeer/10.12.237.132:/opt/gopath/src/ github.com/hyperledger/fabric/
scp -r ../kafkapeer/10.12.237.127:/opt/gopath/src/ github.com/hyperledger/fabric/
scp -r ../kafkapeer/10.12.237.120:/opt/gopath/src/ github.com/hyperledger/fabric/
scp -r ../kafkapeer/10.12.237.112:/opt/gopath/src/ github.com/hyperledger/fabric/
scp -r ../kafkapeer/10.12.237.103:/opt/gopath/src/ github.com/hyperledger/fabric/
scp -r ../kafkapeer/10.12.236.210:/opt/gopath/src/ github.com/hyperledger/fabric/
 
 
第六步：对应的角色服务器在同一目录下准备相关角色配置文件
cd $GOPATH/src/ github.com/hyperledger/fabric/kafkapeer
 
zookeeper部分
#10.12.237.103     zookeeper0
vim 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
   ports:
     - 2181:2181
     - 2888:2888
     - 3888:3888
   extra_hosts:
     - "zookeeper0:10.12.237.103"
     - "zookeeper1:10.12.236.210"
     - "zookeeper2:10.12.237.112"
     - "kafka0:10.12.237.114"
     - "kafka1:10.12.237.120"
     - "kafka2:10.12.237.127"
     - "kafka3:10.12.237.132"
###################################################
#10.12.236.210     zookeeper1
vim 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
   ports:
     - 2181:2181
     - 2888:2888
     - 3888:3888
   extra_hosts:
     - "zookeeper0:10.12.237.103"
     - "zookeeper1:10.12.236.210"
     - "zookeeper2:10.12.237.112"
     - "kafka0:10.12.237.114"
     - "kafka1:10.12.237.120"
     - "kafka2:10.12.237.127"
     - "kafka3:10.12.237.132"
####################################################
#10.12.237.112     zookeeper2
vim 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
   ports:
     - 2181:2181
     - 2888:2888
     - 3888:3888
   extra_hosts:
     - "zookeeper0:10.12.237.103"
     - "zookeeper1:10.12.236.210"
     - "zookeeper2:10.12.237.112"
     - "kafka0:10.12.237.114"
     - "kafka1:10.12.237.120"
     - "kafka2:10.12.237.127"
     - "kafka3:10.12.237.132"
Kafka部分
#10.12.237.114     kafka0
vim 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 # 99 * 1024 * 1024 B
     - KAFKA_REPLICA_FETCH_MAX_BYTES=103809024 # 99 * 1024 * 1024 B
     - 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
   ports:
     - 9092:9092
   extra_hosts:
     - "zookeeper0:10.12.237.103"
     - "zookeeper1:10.12.236.210"
     - "zookeeper2:10.12.237.112"
     - "kafka0:10.12.237.114"
     - "kafka1:10.12.237.120"
     - "kafka2:10.12.237.127"
     - "kafka3:10.12.237.132"
##################################################
#10.12.237.120     kafka1
vim 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 # 99 * 1024 * 1024 B
     - KAFKA_REPLICA_FETCH_MAX_BYTES=103809024 # 99 * 1024 * 1024 B
     - 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
   ports:
     - 9092:9092
   extra_hosts:
     - "zookeeper0:10.12.237.103"
     - "zookeeper1:10.12.236.210"
     - "zookeeper2:10.12.237.112"
     - "kafka0:10.12.237.114"
     - "kafka1:10.12.237.120"
     - "kafka2:10.12.237.127"
     - "kafka3:10.12.237.132"
#####################################################
#10.12.237.127     kafka2
vim 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 # 99 * 1024 * 1024 B
     - KAFKA_REPLICA_FETCH_MAX_BYTES=103809024 # 99 * 1024 * 1024 B
     - 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
   ports:
     - 9092:9092
   extra_hosts:
     - "zookeeper0:10.12.237.103"
     - "zookeeper1:10.12.236.210"
     - "zookeeper2:10.12.237.112"
     - "kafka0:10.12.237.114"
     - "kafka1:10.12.237.120"
     - "kafka2:10.12.237.127"
     - "kafka3:10.12.237.132"
###################################################
#10.12.237.132     kafka3
vim 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 # 99 * 1024 * 1024 B
     - KAFKA_REPLICA_FETCH_MAX_BYTES=103809024 # 99 * 1024 * 1024 B
     - 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
   ports:
     - 9092:9092
   extra_hosts:
     - "zookeeper0:10.12.237.103"
     - "zookeeper1:10.12.236.210"
     - "zookeeper2:10.12.237.112"
     - "kafka0:10.12.237.114"
     - "kafka1:10.12.237.120"
     - "kafka2:10.12.237.127"
     - "kafka3:10.12.237.132"
peer部分
#10.12.237.114     peer0.org1.example.com
vim docker-compose-peer.yaml
# All elements in this file should depend on the docker-compose-base.yaml
# Provided fabric peer node
version: '2'
services:
   container_name: peer0.org1.example.com
   hostname: peer0.org1.example.com
   image: hyperledger/fabric-peer
   environment:
      - CORE_PEER_ID=peer0.org1.example.com
      - CORE_PEER_ADDRESS=peer0.org1.example.com:7051
      - CORE_PEER_CHAINCODELISTENADDRESS=peer0.org1.example.com:7052
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.example.com:7051
      - CORE_PEER_LOCALMSPID=Org1MSP
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      # the following setting starts chaincode containers on the same
      # bridge network as the peers
      #- CORE_LOGGING_LEVEL=ERROR
      - CORE_LOGGING_LEVEL=DEBUG
      - CORE_PEER_GOSSIP_USELEADERELECTION=true
      - CORE_PEER_GOSSIP_ORGLEADER=false
      - CORE_PEER_PROFILE_ENABLED=true
      - CORE_PEER_TLS_ENABLED=true
      - 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:
      - /var/run/:/host/var/run/
   ports:
     - 7051:7051
     - 7052:7052
     - 7053:7053
   extra_hosts:
     - "orderer1.example.com:10.12.236.210"
 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=ERROR
     - CORE_LOGGING_LEVEL=DEBUG
     - CORE_PEER_ID=cli
     - CORE_PEER_ADDRESS=peer0.org1.example.com:7051
     - CORE_PEER_LOCALMSPID=Org1MSP
     - CORE_PEER_TLS_ENABLED=true
   working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
   volumes:
       - /var/run/:/host/var/run/
       - ./chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/kafkapeer/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:
     - "orderer1.example.com:10.12.236.210"
 
##############################################################################
#10.12.237.127     peer0.org2.example.com
vim docker-compose-peer.yaml
# All elements in this file should depend on the docker-compose-base.yaml
# Provided fabric peer node
version: '2'
services:
   container_name: peer0.org2.example.com
   hostname: peer0.org2.example.com
   image: hyperledger/fabric-peer
   environment:
      - CORE_PEER_ID=peer0.org2.example.com
      - CORE_PEER_ADDRESS=peer0.org2.example.com:7051
      - CORE_PEER_CHAINCODELISTENADDRESS=peer0.org2.example.com:7052
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org2.example.com:7051
      - CORE_PEER_LOCALMSPID=Org2MSP
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      # the following setting starts chaincode containers on the same
      # bridge network as the peers
      #- CORE_LOGGING_LEVEL=ERROR
      - CORE_LOGGING_LEVEL=DEBUG
      - CORE_PEER_GOSSIP_USELEADERELECTION=true
      - CORE_PEER_GOSSIP_ORGLEADER=false
      - CORE_PEER_PROFILE_ENABLED=true
      - CORE_PEER_TLS_ENABLED=true
      - 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:
      - /var/run/:/host/var/run/
   ports:
     - 7051:7051
     - 7052:7052
     - 7053:7053
   extra_hosts:
     - "orderer1.example.com:10.12.236.210"
 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=ERROR
     - CORE_LOGGING_LEVEL=DEBUG
     - CORE_PEER_ID=cli
     - CORE_PEER_ADDRESS=peer0.org2.example.com:7051
     - CORE_PEER_LOCALMSPID=Org2MSP
     - CORE_PEER_TLS_ENABLED=true
   working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
   volumes:
       - /var/run/:/host/var/run/
       - ./chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/kafkapeer/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:
     - "orderer1.example.com:10.12.236.210"
 
##################################################################################
#10.12.237.120     peer1.org1.example.com
vim docker-compose-peer.yaml
# All elements in this file should depend on the docker-compose-base.yaml
# Provided fabric peer node
version: '2'
services:
   container_name: peer1.org1.example.com
   hostname: peer1.org1.example.com
   image: hyperledger/fabric-peer
   environment:
      - CORE_PEER_ID=peer1.org1.example.com
      - CORE_PEER_ADDRESS=peer1.org1.example.com:7051
      - CORE_PEER_CHAINCODELISTENADDRESS=peer1.org1.example.com:7052
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org1.example.com:7051
      - CORE_PEER_LOCALMSPID=Org1MSP
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      # the following setting starts chaincode containers on the same
      # bridge network as the peers
      #- CORE_LOGGING_LEVEL=ERROR
      - CORE_LOGGING_LEVEL=DEBUG
      - CORE_PEER_GOSSIP_USELEADERELECTION=true
      - CORE_PEER_GOSSIP_ORGLEADER=false
      - CORE_PEER_PROFILE_ENABLED=true
      - CORE_PEER_TLS_ENABLED=true
      - 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:
      - /var/run/:/host/var/run/
   ports:
     - 7051:7051
     - 7052:7052
     - 7053:7053
   extra_hosts:
     - "orderer1.example.com:10.12.236.210"
 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=ERROR
     - CORE_LOGGING_LEVEL=DEBUG
     - CORE_PEER_ID=cli
     - CORE_PEER_ADDRESS=peer1.org1.example.com:7051
     - CORE_PEER_LOCALMSPID=Org1MSP
     - CORE_PEER_TLS_ENABLED=true
   working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
   volumes:
       - /var/run/:/host/var/run/
       - ./chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/kafkapeer/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:
     - "orderer1.example.com:10.12.236.210"
 
############################################################################################
#10.12.237.132     peer1.org2.example.com
vim docker-compose-peer.yaml
# All elements in this file should depend on the docker-compose-base.yaml
# Provided fabric peer node
version: '2'
services:
   container_name: peer1.org2.example.com
   hostname: peer1.org2.example.com
   image: hyperledger/fabric-peer
   environment:
      - CORE_PEER_ID=peer1.org2.example.com
      - CORE_PEER_ADDRESS=peer1.org2.example.com:7051
      - CORE_PEER_CHAINCODELISTENADDRESS=peer1.org2.example.com:7052
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer1.org2.example.com:7051
      - CORE_PEER_LOCALMSPID=Org2MSP
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      # the following setting starts chaincode containers on the same
      # bridge network as the peers
      #- CORE_LOGGING_LEVEL=ERROR
      - CORE_LOGGING_LEVEL=DEBUG
      - CORE_PEER_GOSSIP_USELEADERELECTION=true
      - CORE_PEER_GOSSIP_ORGLEADER=false
      - CORE_PEER_PROFILE_ENABLED=true
      - CORE_PEER_TLS_ENABLED=true
      - 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:
      - /var/run/:/host/var/run/
   ports:
     - 7051:7051
     - 7052:7052
     - 7053:7053
   extra_hosts:
     - "orderer1.example.com:10.12.236.210"
 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=ERROR
     - CORE_LOGGING_LEVEL=DEBUG
     - CORE_PEER_ID=cli
     - CORE_PEER_ADDRESS=peer1.org2.example.com:7051
     - CORE_PEER_LOCALMSPID=Org2MSP
     - CORE_PEER_TLS_ENABLED=true
   working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
   volumes:
       - /var/run/:/host/var/run/
       - ./chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/kafkapeer/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:
     - "orderer1.example.com:10.12.236.210"
 
orderer部分
#10.12.237.103     orderer0.example.com
vim docker-compose-orderer.yaml
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#
version: '2'
services:
   container_name: orderer0.example.com
   image: hyperledger/fabric-orderer
   environment:
     - ORDERER_GENERAL_LOGLEVEL=debug
     - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
     - ORDERER_GENERAL_GENESISMETHOD=file
     - ORDERER_GENERAL_GENESISFILE=/var/hyperledger/orderer/orderer.genesis.block
     - ORDERER_GENERAL_LOCALMSPID=OrdererMSP
     - ORDERER_GENERAL_LOCALMSPDIR=/var/hyperledger/orderer/msp
     # enabled TLS
     - ORDERER_GENERAL_TLS_ENABLED=true
     - ORDERER_GENERAL_TLS_PRIVATEKEY=/var/hyperledger/orderer/tls/server.key
     - ORDERER_GENERAL_TLS_CERTIFICATE=/var/hyperledger/orderer/tls/server.crt
     - ORDERER_GENERAL_TLS_ROOTCAS=[/var/hyperledger/orderer/tls/ca.crt]
     - 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=[10.12.237.114:9092,10.12.237.120:9092,10.12.237.127:9092,10.12.237.132:9092]      
   working_dir: /opt/gopath/src/github.com/hyperledger/fabric
   command: orderer
   volumes:
     - ./channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block
   ports:
     - 7050:7050
   extra_hosts:
     - "kafka0:10.12.237.114"
     - "kafka1:10.12.237.120"
     - "kafka2:10.12.237.127"
     - "kafka3:10.12.237.132"
 
##############################################################################
#10.12.236.210     orderer1.example.com
vim docker-compose-orderer.yaml
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#
version: '2'
services:
   container_name: orderer1.example.com
   image: hyperledger/fabric-orderer
   environment:
     - ORDERER_GENERAL_LOGLEVEL=debug
     - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
     - ORDERER_GENERAL_GENESISMETHOD=file
     - ORDERER_GENERAL_GENESISFILE=/var/hyperledger/orderer/orderer.genesis.block
     - ORDERER_GENERAL_LOCALMSPID=OrdererMSP
     - ORDERER_GENERAL_LOCALMSPDIR=/var/hyperledger/orderer/msp
     # enabled TLS
     - ORDERER_GENERAL_TLS_ENABLED=true
     - ORDERER_GENERAL_TLS_PRIVATEKEY=/var/hyperledger/orderer/tls/server.key
     - ORDERER_GENERAL_TLS_CERTIFICATE=/var/hyperledger/orderer/tls/server.crt
     - ORDERER_GENERAL_TLS_ROOTCAS=[/var/hyperledger/orderer/tls/ca.crt]
     - 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=[10.12.237.114:9092,10.12.237.120:9092,10.12.237.127:9092,10.12.237.132:9092]     
   working_dir: /opt/gopath/src/github.com/hyperledger/fabric
   command: orderer
   volumes:
     - ./channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block
   ports:
     - 7050:7050
   extra_hosts:
     - "kafka0:10.12.237.114"
     - "kafka1:10.12.237.120"
     - "kafka2:10.12.237.127"
     - "kafka3:10.12.237.132"
 
################################################################
#10.12.237.112     orderer2.example.com
vim docker-compose-orderer.yaml
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#
version: '2'
services:
   container_name: orderer2.example.com
   image: hyperledger/fabric-orderer
   environment:
     - ORDERER_GENERAL_LOGLEVEL=debug
     - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
     - ORDERER_GENERAL_GENESISMETHOD=file
     - ORDERER_GENERAL_GENESISFILE=/var/hyperledger/orderer/orderer.genesis.block
     - ORDERER_GENERAL_LOCALMSPID=OrdererMSP
     - ORDERER_GENERAL_LOCALMSPDIR=/var/hyperledger/orderer/msp
     # enabled TLS
     - ORDERER_GENERAL_TLS_ENABLED=true
     - ORDERER_GENERAL_TLS_PRIVATEKEY=/var/hyperledger/orderer/tls/server.key
     - ORDERER_GENERAL_TLS_CERTIFICATE=/var/hyperledger/orderer/tls/server.crt
     - ORDERER_GENERAL_TLS_ROOTCAS=[/var/hyperledger/orderer/tls/ca.crt]
     - 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=[10.12.237.114:9092,10.12.237.120:9092,10.12.237.127:9092,10.12.237.132:9092]
   working_dir: /opt/gopath/src/github.com/hyperledger/fabric
   command: orderer
   volumes:
     - ./channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block
   ports:
     - 7050:7050
   extra_hosts:
     - "kafka0:10.12.237.114"
     - "kafka1:10.12.237.120"
     - "kafka2:10.12.237.127"
     - "kafka3:10.12.237.132"
 
 
第七步：启动应用程序：
顺序：先启动Zookeeper再启动Kafka，orderer，peer
对应的角色服务器执行如下相同的命令：
cd cd /opt/gopath/src/ github.com/hyperledger /fabric/kafkapeer
docker-compose -f docker-compose-zookeeper.yaml up -d
docker-compose -f docker-compose-kafka.yaml up -d
docker-compose -f docker-compose-orderer.yaml up -d
docker-compose -f docker-compose-peer.yaml up -d
 
第八步：验证创建通道 安装与运行智能合约
#10.12.237.114     peer0.org1.example.com 
 
进入cli容器
docker exec -it cli bash
 
为创建通道设置变量
 
创建Channel
peer channel create -o orderer0.example.com:7050 -c mychannel -f ./channel-artifacts/mychannel.tx --tls --cafile $ORDERER_CA
 
Peer加入Channel
peer channel join -b mychannel.block
 
 
保存mychannel.block到本地
cd cd /opt/gopath/src/ github.com/hyperledger /fabric/kafkapeer
docker cp d98a19fd6da7:/opt/gopath/src/ github.com/hyperledger/fabric/peer/mychannel.block /opt/gopath/src/ github.com/hyperledger/fabric/kafkapeer
 
把mychannel.block发送到其它peer节点
scp mychannel.block 10.12.237.120:/opt/gopath/src/ github.com/hyperledger/fabric/kafkapeer/
scp mychannel.block 10.12.237.127:/opt/gopath/src/ github.com/hyperledger/fabric/kafkapeer/
scp mychannel.block 10.12.237.132:/opt/gopath/src/ github.com/hyperledger/fabric/kafkapeer/
 
准备智能合约：
第三步执行下载镜像脚本之后在fabric-sample目录下层的chaincode目录下层的chaincode_example02/目录下层有一个go目录下层的chaincode_example02.go文件cope到容器对应的位置
cd /opt/gopath/src/ github.com/hyperledger/fabric-samples/chaincode/chaincode_example02/go/
docker cp chaincode_example02.go 1d18d974b787:/opt/gopath/src/ github.com/hyperledger/fabric/kafkapeer/chaincode/go/
 
安装智能合约
docker exec -it cli bash
peer chaincode install -n mycc -p github.com/hyperledger/fabric/kafkapeer/chaincode/go/ -v 1.0
 
为实例化智能合约设置环境变量
 
实例化智能合约,区块初始化数据为a为200，b为400
peer chaincode instantiate -o orderer0.example.com:7050 --tls --cafile $ORDERER_CA -C mychannel -n mycc -v 1.0 -c '{"Args":["init","a","200","b","400"]}' -P "OR ('Org1MSP.peer','Org2MSP.peer')"
 
查询：
peer chaincode query -C mychannel -n mycc -c '{"Args":["query","a"]}'
 
 
 
 
小数苗小数苗
关注
  • 1
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 1
    评论
HyperLedger Fabric 1.4.4搭建基于多节点kafka共识集群
吃顿好的
04-02 974
修改configtx.yaml配置文件 在SampleDevModeKafka下增加kafka的broker节点，我增加后的内容如下 SampleDevModeKafka: <<: *ChannelDefaults Capabilities: <<: *ChannelCapabilities Order...
Kafka 实战 - Docker-compose部署Kafka集群
最新发布
qq_33240556的博客
04-11 393
使用 Docker Compose 部署 Apache Kafka 集群可以简化多容器应用程序的定义和管理。确保您的 Linux 系统上已经安装了 Docker 以及 Docker Compose。通过以上步骤，您已经在 Docker Compose 环境中成功部署了 Kafka 集群，并进行了初步的验证。Docker Compose 使得管理和扩展集群变得更为便捷，只需修改。的文件，用于定义服务、网络、卷等配置。然后，可以使用 Kafka 工具（如。文件即可调整集群配置，使用。等命令进行相应的操作。
HyperLedger Fabric开发实战 -Kafka集群部署
张亚平的博客
01-22 941
第5章 Kafka集群部署
基于Kafka共识的Fabric分布式环境搭建
Arvon
12-07 1147
测试环境服务器安排： 名称 IP Hostname 组织 备注 zookeeper1 10.16.3.97 zookeeper1 公共   zookeeper2 ...
我对hyperledger fabric1.1.0的执着（六）：kafka集群部署
tianshuhao521的博客
12-04 1020
1、用11台服务器，如下 名称 ip Hostname 组织机构 Zk1 192.168.2.237 zookeeper1   Zk2 192.168.2.131 zookeeper2   Zk3 192.168.2.188 zookeeper3   kafka1 192.168.2.182 ka...
EFK+kafka+head日志分析集群部署.rar
07-04
日志分析集群，在本地centos7虚拟机搭建的Es+firebeat+logstash+kibana+kafka+head的完整集群部署文档，很详细，通常的EFK日志分析，加上kafka的消息队列，可以处理PB级别的日志内容。
docker-compose部署zk+kafka+storm集群的实现
01-09
集群部署总览 172.22.12.20 172.22.12.21 172.22.12.22 172.22.12.23 172.22.12.24 zoo1:2181 zoo2:2182 zoo3:2183 zkui:9090 (admin/manager) kafka1:9092 kafka2:9092 kafka3:9092 kafdrop:9000 ...
Hadoop+Spark+Hive+HBase+Oozie+Kafka+Flume+Flink+ES+Redash等详细安装部署
06-22
1、内容概要：Hadoop+Spark+Hive+HBase+Oozie+Kafka+Flume+Flink+Elasticsearch+Redash等大数据集群及组件搭建指南（详细搭建步骤+实践过程问题总结）。 2、适合人群：大数据运维、大数据相关技术及组件初学者。 3、...
fabric1.1.0 kafka集群部署及查错
shirley_vacuum的专栏
09-10 950
1.环境声明      fabric1.1.0                   go1.8.3 linux/amd64                  Docker version 17.03.2-ce        2.节点部署                      IP              Hostname 172.20.6.145 ...
Ubuntu 16.04 搭建 Hyperledger Fabric 1.4
01-08
VMware 安装 Ubuntu 16.04 请参考 https://blog.csdn.net/qq_28090573/article/details/82724910 1. 修改软件源 点击设置，然后点击软件和更新 在其他站点中找到mirrors.aliyun.com 2. 安装常用工具 安装vimsudo apt-get install vim # 验证版本 vim -v 安装gitsudo apt-get install git # 验证版本 git version 安装curlsudo apt-get install curl # 验证版本 curl -V 安装wgets
hyperledger fabric kafka集群配置文件
05-06
基于hyperledger fabric 1.4版本实现的kafka集群配置文件，环境搭建可以参考https://blog.csdn.net/u010857052/article/details/84309264。有任何问题可以评论下面留言。谢谢
在Ubuntu18.04 Linux系统下搭建Fabric1.4.0
ngums的博客
07-08 878
环境配置 Ubuntu18.04 Go最新版本 安装依赖包 编译Fabric相关代码，需要一些依赖包，可以通过如下命令安装：` $ sudo apt-get update \ && apt-get install -y libsnappy-dev zlib1g-dev libbz2-dev libltdl-dev libtool 注意：是zlib1g-dev而不是zliblg-dev 安装Docker Fabric网络目前依赖Docker服务作为链码容器的支持，因此即使是本地环
HyperLedger Fabric 1.2 kafka生产环境部署（11.1）
weixin_34122810的博客
09-08 201
11.1 Kafka模式简介 上一章介绍的Solo模式只存在一个排序（orderer）服务,是一种中心化结构，一旦排序（orderer）服务出现了问题，整个区块链网络将会崩溃，为了能在正式环境中稳定运行，需要对排序（orderer）服务采用集群方式，Hyperledger Fabric采用kafka方式实现排序（orderer）服务的集群，k...
Kafka集群搭建01-Zookeeper 集群部署
架构狮老颜
08-04 1901
kafka 集群部署 zookeeper 集群部署
HyperLedger Fabric 1.4.4搭建基于多orderer节点的kafka共识集群
吃顿好的
04-08 817
配置 主机名 ip 功能 bd223 10.1.24.223 org2的peer0和peer1节点，orderer1节点 bd225 10.1.24.225 org1的peer0和peer1节点，orderer节点，三个kafka和三个zookeeper节点 前言 其实搭建的过程很简单，主要的时间都是耗费在了kafka的搭建上。因为机器资源不够，所以kafka都是搭建在同一...
Fabric1.4.0 Kafka集群环境部署
weixin_44732379的博客
04-22 884
Fabric1.4.0 Kafka集群环境部署
docker-compose -- kafka测试
janckgger的博客
05-18 282
这里采用单zk,单kafka docker-compose.yml version: '3.7' services: zoo1: image: zookeeper hostname: zoo1 restart: always ports: - "2181:2181" environment: ZOO_MY_ID: 1 ZOO_PORT: 2181 ZOO_SERVERS: server.1=zoo1:2
在k8s上部署 zookeeper + kafka 集群的配置文件
06-13
好的，以下是一个基本的zookeeper + kafka集群的配置文件示例： 1. Zookeeper配置文件示例： ``` tickTime=2000 dataDir=/var/lib/zookeeper clientPort=2181 initLimit=5 syncLimit=2 server.1=zookeeper1:2888:3888 server.2=zookeeper2:2888:3888 server.3=zookeeper3:2888:3888 ``` 2. Kafka配置文件示例： ``` broker.id=0 listeners=PLAINTEXT://kafka1:9092 advertised.listeners=PLAINTEXT://kafka1:9092 num.network.threads=3 num.io.threads=8 socket.send.buffer.bytes=102400 socket.receive.buffer.bytes=102400 socket.request.max.bytes=104857600 log.dirs=/var/lib/kafka num.partitions=1 num.recovery.threads.per.data.dir=1 offsets.topic.replication.factor=3 transaction.state.log.replication.factor=3 transaction.state.log.min.isr=2 log.retention.hours=168 log.segment.bytes=1073741824 log.retention.check.interval.ms=300000 zookeeper.connect=zookeeper1:2181,zookeeper2:2181,zookeeper3:2181 zookeeper.connection.timeout.ms=6000 ``` 注意：实际上，以上示例文件中的IP地址和端口号需要根据实际情况进行修改。此外，还需要在每个节点上进行相应的文件配置和软件安装，才能正确部署zookeeper + kafka集群。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

小数苗小数苗

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值