hyperledger fabric怎么发起交易 hyperledger fabric搭建

转载

mob6454cc74c0fc 2024-03-24 09:10:27

文章标签 golang fabric docker 配置文件 github 文章分类 运维

Hyperledger Fabric搭建

一、准备工作

1. 安装golang
2. 安装Docker
3. 安装Docker-Compose

二、Fabric测试环境搭建

1. 获取github上fabric的源码
2. 配置环境变量
3. 启动fabric网络

三、Fabric环境搭建

1. Fabric网络环境规划
2. 准备工作
3. Fabric安装
4. Fabric配置
5. 启动Orderer和Peer
6. 添加用户——以admin@org1.example.com为例
7. 创建channel

一、准备工作

fabric机器名：xjcc-30-70

1. 安装golang

下载并解压

wget https://studygolang.com/dl/golang/go1.16.linux-amd64.tar.gz
tar -xzf go1.16.linux-amd64.tar.gz
rm go1.16.linux-amd64.tar.gz
sudo mv go /usr/local

创建fabric用户

sudo useradd -d /home/fabric -m fabric
sudo passwd fabric

新创建的用户赋予免密sudo权限

echo "fabric ALL = (root) NOPASSWD:ALL" | sudo tee /etc/sudoers.d/fabric
sudo chmod 0440 /etc/sudoers.d/fabric
usermod -s /bin/bash fabric  #指定新建用户的shell

配置环境变量
修改~/.bashrc文件，追加下面内容：

export PATH=$PATH:/usr/local/go/bin
export GOROOT=/usr/local/go
export GOPATH=$HOME/go
export PATH=$PATH:$HOME/go/bin

更换Go代理

go env -w GOPROXY=https://goproxy.io,direct
go env -w GO111MODULE=on

cd ~
mkdir -p go/src/github.com/hyperledger/
sudo chmod -R 775 go

2. 安装Docker

安装docker-ce

# 1. 安装必要工具
sudo apt-get install apt-transport-https ca-certificates curl software-properties-common
# 2. 安装GPG证书
curl -fsSL http://mirrors.aliyun.com/docker-ce/linux/ubuntu/gpg | sudo apt-key add -
# 3. 写入软件源信息
sudo add-apt-repository "deb [arch=amd64] http://mirrors.aliyun.com/docker-ce/linux/ubuntu $(lsb_release -cs) stable"
# 4. 更新并安装docker-ce
sudo apt-get update
sudo apt-get install docker-ce

将fabric用户添加到docker用户组

# 1. 创建docker用户组
sudo groupadd docker
# 2. 将fabric用户添加到docker用户组
sudo usermod -aG docker $USER
# 3. 需退出终端重新连接
exit

将docker镜像换为中科大镜像

# 编辑/etc/docker/daemon.json文件，如果没有则自行创建，添加以下内容：
{
	"registry-mirrors" : [
    "https://nqr0dgc3.mirror.aliyuncs.com",
    "http://registry.docker-cn.com",
    "http://docker.mirrors.ustc.edu.cn",
    "http://hub-mirror.c.163.com"
  ],
  "insecure-registries" : [
    "registry.docker-cn.com",
    "docker.mirrors.ustc.edu.cn"
  ],
  "debug" : true,
  "experimental" : true
}

重启服务

sudo systemctl daemon-reload
sudo systemctl restart docker
# 查看docker版本信息
docker -v
# 查看镜像是否配置成功
docker info

3. 安装Docker-Compose

首先安装python-pip

sudo apt-get install python3-pip

安装Docker-Compose

sudo pip3 install docker-compose
# 查看版本
docker-compose -version

二、Fabric测试环境搭建

1. 获取github上fabric的源码

git clone "git://github.com/hyperledger/fabric.git"
cd fabric/
# checkout到要编译的的分支
git checkout release-2.3 
# 下载官方给的例子和Docker镜像
# 较慢，出现错误remake即可
cd scripts/
sudo ./bootstrap.sh

若上述下载过慢，可以对源码进行编译

# 进入fabric文件夹
cd ~/go/src/github.com/hyperledger/fabric/
# 编译
make release
# 查看生成的文件
cd release/linux-amd64/bin
# 如果文件夹内有如下文件的话说明编译成功
# configtxgen configtxlator cryptogen discover idemixgen orderer peer

2. 配置环境变量

vim ~/.profile
# 追加以下内容
export PATH=$PATH:$GOPATH/src/github.com/hyperledger/fabric/release/linux-amd64/bin
# 更新
source ~/.profile

3. 启动fabric网络

# 进入test-network文件夹
cd ~/go/src/github.com/hyperledger/fabric/scripts/fabric-samples/test-network
./network.sh -h    # 查看help
sudo ./network.sh up    # 启动
sudo ./network.sh down  # 关闭

若输出下面内容，说明fabric搭建完毕

hyperledger fabric怎么发起交易 hyperledger fabric搭建_golang

三、Fabric环境搭建

1. Fabric网络环境规划

四台主机，四个组织org1-4，四个个peer：peer0@org1、peer1@org2、peer2@org3和peer3@org4

IP	主机名	描述	备注
10.10.9.20	node0	peer0@org1 orderer	证书生成节点 orderer0/peer0@org1.demo.com
10.10.9.21	node1	peer0@org2 orderer	orderer1/peer0@org2.demo.com
10.10.9.22	node2	peer0@org3 orderer	orderer2/peer0@org3.demo.com
10.10.9.23	node3	peer0@org4	peer0@org4.demo.com

2. 准备工作

修改每台机器的/etc/hosts文件

# orderers
10.10.9.20 orderer0.demo.com
10.10.9.21 orderer1.demo.com
10.10.9.22 orderer2.demo.com
# peers
10.10.9.20 peer0.org1.demo.com
10.10.9.20 peer1.org1.demo.com
10.10.9.21 peer0.org2.demo.com
10.10.9.21 peer1.org2.demo.com
10.10.9.22 peer0.org3.demo.com
10.10.9.22 peer1.org3.demo.com
10.10.9.23 peer0.org4.demo.com
10.10.9.23 peer1.org4.demo.com

安装golang
安装docker和docker-compose
3-4见：一、准备工作

3. Fabric安装

为每一台服务器创建Fabric源码文件夹并修改权限

mkdir -p ~/go/src/github.com/hyperledger/
cd ~/go/src/github.com/hyperledger/
sudo chmod -R 775 ~/go

按照二、Fabric测试环境搭建的步骤为每一台服务器安装Fabric源码并测试Fabric环境

4. Fabric配置

编写配置文件生成CA证书
编写配置文件crypto-config.yaml

OrdererOrgs:
    - Name: Orderer
      Domain: demo.com
      Specs:
          - Hostname: orderer0
          - Hostname: orderer1
          - Hostname: orderer2
PeerOrgs:
    - Name: Org1
      Domain: org1.demo.com
      EnableNodeOUs: true
      Template:
          Count: 2
      Users:
          Count: 1
    - Name: Org2
      Domain: org2.demo.com
      EnableNodeOUs: true
      Template:
          Count: 2
      Users:
          Count: 1
    - Name: Org3
      Domain: org3.demo.com
      EnableNodeOUs: true
      Template:
          Count: 2
      Users:
          Count: 1
    - Name: Org4
      Domain: org4.demo.com
      EnableNodeOUs: true
      Template:
          Count: 2
      Users:
          Count: 1

在node0执行cryptogen，生成证书

cryptogen generate --config=crypto-config.yaml --output ./crypto-config

证书分发到各个节点（注意目标主机是否有相应文件夹）

cp -r /home/fabric/mycluster/certs/ordererOrganizations/example.com/orderers/orderer.example.com/ /home/fabric/mycluster/
scp -r /home/fabric/mycluster/certs/peerOrganizations/org1.example.com/peers/peer0.org1.example.com fabric@10.100.70.31:/home/fabric/mycluster/
scp -r /home/fabric/mycluster/certs/peerOrganizations/org1.example.com/peers/peer1.org1.example.com fabric@10.100.70.32:/home/fabric/mycluster/
scp -r /home/fabric/mycluster/certs/peerOrganizations/org2.example.com/peers/peer0.org2.example.com fabric@10.100.70.33:/home/fabric/mycluster/
scp -r /home/fabric/mycluster/certs/peerOrganizations/org2.example.com/peers/peer1.org2.example.com fabric@10.100.70.36:/home/fabric/mycluster/

orderer.example.com配置
在orderer.example.com节点上创建配置目录orderer.example.com，然后将fabric/sampleconfig/orderer.yaml配置文件拷贝到此目录，然后修改相关配置。

...
    BootstrapFile: ./genesisblock
    LocalMSPDir: ./msp
    LocalMSPID: OrdererMSP
...
FileLedger:
    # Location: The directory to store the blocks in.
    Location: /home/fabric/mycluster/orderer/data
...

还需要用到一个文件夹存放orderer的数据

mkdir ~/cluster/orderer.example.com/data

peer0.org1.example.com配置
在peer0.org1.example.com节点上创建配置目录peer0.org1.example.com，然后将fabric/sampleconfig/core.yaml配置文件拷贝到此目录，然后修改相关配置。

peer:
    # The peer id provides a name for this peer instance and is used when
    # naming docker resources.
    id: peer0.org1.example.com
...
    # Path on the file system where peer will store data (eg ledger). This
    # location must be access control protected to prevent unintended
    # modification that might corrupt the peer operations.
    fileSystemPath: /home/fabric/mycluster/peer/data
...
    # Identifier of the local MSP
    # ----!!!!IMPORTANT!!!-!!!IMPORTANT!!!-!!!IMPORTANT!!!!----
    # Deployers need to change the value of the localMspId string.
    # In particular, the name of the local MSP ID of a peer needs
    # to match the name of one of the MSPs in each of the channel
    # that this peer is a member of. Otherwise this peer's messages
    # will not be identified as valid by other nodes.
    localMspId: Org1MSP
...

还需要用到一个文件夹存放peer的数据

mkdir ~/cluster/peer0.org1.example.com/data

peer1.org1.example.com配置
将peer0.org1.example.com配置文件core.yaml拷贝到peer1.org1.example.com

scp /home/fabric/mycluster/peer0.org1.example.com/core.yaml fabric@10.100.70.32:/home/fabric/mycluster/peer1.org1.example.com

修改core.yaml中的peer0.org1.example.com为peer1.org1.example.com

sed -i "s/peer0.org1.example.com/peer1\.org1\.example.com/g" core.yaml

还需要用到一个文件夹存放peer的数据

mkdir ~/cluster/peer1.org1.example.com/data

peer0.org2.example.com配置
将peer0.org1.example.com配置文件core.yaml拷贝到peer0.org2.example.com

scp /home/fabric/mycluster/peer0.org1.example.com/core.yaml fabric@10.100.70.33:/home/fabric/mycluster/peer0.org2.example.com

修改core.yaml中的peer0.org1.example.com为peer0.org2.example.com

sed -i "s/peer0.org1.example.com/peer0\.org2\.example.com/g" core.yaml

将配置文件中Org1MSP替换成Org2MSP

sed -i "s/Org1MSP/Org2MSP/g" core.yaml

还需要用到一个文件夹存放peer的数据

mkdir ~/cluster/peer0.org2.example.com/data

peer1.org2.example.com配置
将peer0.org1.example.com配置文件core.yaml拷贝到peer1.org2.example.com

scp /home/fabric/mycluster/peer0.org1.example.com/core.yaml fabric@10.100.70.36:/home/fabric/mycluster/peer1.org2.example.com

修改core.yaml中的peer0.org1.example.com为peer1.org2.example.com

sed -i "s/peer0.org1.example.com/peer1\.org2\.example.com/g" core.yaml

将配置文件中Org1MSP替换成Org2MSP

sed -i "s/Org1MSP/Org2MSP/g" core.yaml

还需要用到一个文件夹存放peer的数据

mkdir ~/cluster/peer1.org2.example.com/data

配置configtx.yaml创建创世块
在生成certs证书的节点上，创建configtx.yaml配置文件。

Organizations:
    - &OrdererOrg
        Name: OrdererOrg
        SkipAsForeign: false
        ID: OrdererMSP
        MSPDir: /home/fabric/config/certs/ordererOrganizations/example.com/msp
        Policies: &OrdererOrgPolicies
            Readers:
                Type: Signature
                Rule: "OR('OrdererOrg.member')"
            Writers:
                Type: Signature
                Rule: "OR('OrdererOrg.member')"
            Admins:
                Type: Signature
                Rule: "OR('OrdererOrg.admin')"
            Endorsement:
                Type: Signature
                Rule: "OR('OrdererOrg.member')"
        OrdererEndpoints:
            - "127.0.0.1:7050"
        AnchorPeers:
            - Host: 127.0.0.1
              Port: 7051
    - &Org1
        Name: Org1MSP
        ID: Org1MSP
        MSPDir: /home/fabric/config/certs/peerOrganizations/org1.example.com/msp
        AnchorPeers:
            - Host: peer0.org1.example.com
              Port: 7051
        Policies: &Org1Policies
            Readers:
                Type: Signature
                Rule: "OR('Org1.member')"
            Writers:
                Type: Signature
                Rule: "OR('Org1.member')"
            Admins:
                Type: Signature
                Rule: "OR('Org1.admin')"
            Endorsement:
                Type: Signature
                Rule: "OR('Org1.member')"
    - &Org2
        Name: Org2MSP
        ID: Org2MSP
        MSPDir: /home/fabric/config/certs/peerOrganizations/org2.example.com/msp
        AnchorPeers:
            - Host: peer0.org2.example.com
              Port: 7051
        Policies: &Org2Policies
            Readers:
                Type: Signature
                Rule: "OR('Org2.member')"
            Writers:
                Type: Signature
                Rule: "OR('Org2.member')"
            Admins:
                Type: Signature
                Rule: "OR('Org2.admin')"
            Endorsement:
                Type: Signature
                Rule: "OR('Org2.member')"

Capabilities:
    Channel: &ChannelCapabilities
        V2_0: true
    Orderer: &OrdererCapabilities
        V2_0: true
    Application: &ApplicationCapabilities
        V2_0: true

Application: &ApplicationDefaults
    ACLs: &ACLsDefault
        
        _lifecycle/CheckCommitReadiness: /Channel/Application/Writers
        _lifecycle/CommitChaincodeDefinition: /Channel/Application/Writers
        _lifecycle/QueryChaincodeDefinition: /Channel/Application/Writers
        _lifecycle/QueryChaincodeDefinitions: /Channel/Application/Writers
        
        lscc/ChaincodeExists: /Channel/Application/Readers
        lscc/GetDeploymentSpec: /Channel/Application/Readers
        lscc/GetChaincodeData: /Channel/Application/Readers
        lscc/GetInstantiatedChaincodes: /Channel/Application/Readers
        
        qscc/GetChainInfo: /Channel/Application/Readers
        qscc/GetBlockByNumber: /Channel/Application/Readers
        qscc/GetBlockByHash: /Channel/Application/Readers
        qscc/GetTransactionByID: /Channel/Application/Readers
        qscc/GetBlockByTxID: /Channel/Application/Readers
        
        cscc/GetConfigBlock: /Channel/Application/Readers
        cscc/GetChannelConfig: /Channel/Application/Readers
        
        peer/Propose: /Channel/Application/Writers
        peer/ChaincodeToChaincode: /Channel/Application/Writers
        
        event/Block: /Channel/Application/Readers
        event/FilteredBlock: /Channel/Application/Readers
    Organizations:
    Policies: &ApplicationDefaultPolicies
        LifecycleEndorsement:
            Type: ImplicitMeta
            Rule: "MAJORITY Endorsement"
        Endorsement:
            Type: ImplicitMeta
            Rule: "MAJORITY Endorsement"
        Readers:
            Type: ImplicitMeta
            Rule: "ANY Readers"
        Writers:
            Type: ImplicitMeta
            Rule: "ANY Writers"
        Admins:
            Type: ImplicitMeta
            Rule: "MAJORITY Admins"
    Capabilities:
        <<: *ApplicationCapabilities

Orderer: &OrdererDefaults
    OrdererType: solo
    Addresses:
        - orderer.example.com:7050
    BatchTimeout: 2s
    BatchSize:
        MaxMessageCount: 500
        AbsoluteMaxBytes: 10 MB
        PreferredMaxBytes: 2 MB
    MaxChannels: 0
    Kafka:
        Brokers:
            - kafka0:9092
            - kafka1:9092
            - kafka2:9092
    EtcdRaft:
        Consenters:
            - Host: raft0.example.com
              Port: 7050
              ClientTLSCert: path/to/ClientTLSCert0
              ServerTLSCert: path/to/ServerTLSCert0
            - Host: raft1.example.com
              Port: 7050
              ClientTLSCert: path/to/ClientTLSCert1
              ServerTLSCert: path/to/ServerTLSCert1
            - Host: raft2.example.com
              Port: 7050
              ClientTLSCert: path/to/ClientTLSCert2
              ServerTLSCert: path/to/ServerTLSCert2
        Options:
            TickInterval: 500ms
            ElectionTick: 10
            HeartbeatTick: 1
            MaxInflightBlocks: 5
            SnapshotIntervalSize: 16 MB
    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:
    SampleSingleMSPSolo:
        <<: *ChannelDefaults
        Orderer:
            <<: *OrdererDefaults
            Organizations:
                - *OrdererOrg
        Consortiums:
            SampleConsortium:
                Organizations:
                    - *Org1
                    - *Org2
    SampleSingleMSPChannel:
        <<: *ChannelDefaults
        Consortium: SampleConsortium
        Application:
            <<: *ApplicationDefaults
            Organizations:
                - *Org1
                - *Org2

使用下列命令生成创世块

configtxgen -profile SampleSingleMSPSolo -outputBlock ./genesisblock -channelID mychannel

将创世块复制到orderer节点/home/fabric/mycluster/orderer.example.com目录下

mv genesisblock orderer.example.com/

5. 启动Orderer和Peer

在orderer.example.com下启动orderer

orderer $  # &表示后台运行

为了方便查看输出的日志，可以将输出重定向到log文件

orderer 2>&1 | tee log &  # &表示后台运行

在peer.example.com下启动各个peer

peer node start $  # &表示后台运行

为了方便查看输出的日志，可以将输出重定向到log文件

peer node start 2>&1 | tee log &  # &表示后台运行

为了解决没有权限创建/var/hyperledger的问题，首先创建该文件夹并赋予操作权限

sudo mkdir -p /var/hyperledger/production
sudo chown -R $(whoami):$(whoami) /var/hyperledger

6. 添加用户——以admin@org1.example.com为例

新建一个文件夹保存用户的配置信息
本文件夹就相当于是一个用户，在上述任何一台机器上均可，但是建议在orderer节点上部署，因为所有的证书文件均在此机器上

cd ~
mkdir users

将用户证书复制到其中

cp -r ~/config/certs/peerOrganizations/org1.example.com/users/Admin@org1
.example.com/ ~/users/Admin\@org1.example.com

还需要将core.yaml复制到用户目录下

scp fabric@10.100.70.31:/home/fabric/mycluster/peer0.org1.example.com/core.yaml ~/users/Admin@org1.example.com

为了方便使用，创建一个脚本Admin@org1.example.com/peer.sh并修改权限

#!/bin/bash
PATH=`pwd`/../bin:$PATH

export FABRIC_CFG_PATH=`pwd`

export CORE_PEER_TLS_ENABLED=true
export CORE_PEER_TLS_CERT_FILE=./tls/client.crt
export CORE_PEER_TLS_KEY_FILE=./tls/client.key

export CORE_PEER_MSPCONFIGPATH=./msp
export CORE_PEER_ADDRESS=peer0.org1.example.com:7051
export CORE_PEER_LOCALMSPID=Org1MSP
export CORE_PEER_TLS_ROOTCERT_FILE=./tls/ca.crt
export CORE_PEER_ID=cli
export CORE_LOGGING_LEVEL=INFO

peer $*

chmod 777 peer.sh

其他用户的创建类似，下面给出相应的命令

# 拷贝相应的证书
cp -r ~/config/certs/peerOrganizations/org1.example.com/users/User1@org1.example.com/ ~/users/User1\@org1.example.com
cp -r ~/config/certs/peerOrganizations/org2.example.com/users/Admin@org2.example.com/ ~/users/Admin\@org2.example.com
cp -r ~/config/certs/peerOrganizations/org2.example.com/users/User1@org2.example.com/ ~/users/User1\@org2.example.com

# 拷贝相应的core.yaml
scp fabric@10.100.70.32:/home/fabric/mycluster/peer1.org1.example.com/core.yaml ~/users/User1@org1.example.com
scp fabric@10.100.70.33:/home/fabric/mycluster/peer0.org2.example.com/core.yaml ~/users/Admin@org2.example.com
scp fabric@10.100.70.36:/home/fabric/mycluster/peer1.org2.example.com/core.yaml ~/users/User1@org2.example.com

7. 创建channel

准备channel文件
在configtx.yaml文件同文件夹下创建channel

configtxgen -profile SampleSingleMSPChannel -outputCreateChannelTx mychannel.tx -channelID mychannel

为每个组织的peer生成一个anchor文件

configtxgen -profile SampleSingleMSPChannel -outputAnchorPeersUpdate Org1MSPanchors.tx -channelID mychannel -asOrg Org1MSP
configtxgen -profile SampleSingleMSPChannel -outputAnchorPeersUpdate Org2MSPanchors.tx -channelID mychannel -asOrg Org2MSP

下一步操作中要访问orderer.example.com，需要将验证orderer.example.com的根证书复制到用户目录中

cp -r /home/fabric/config/certs/ordererOrganizations/example.com/tlsca/tlsca.example.com-cert.pem ~/users/Admin@org1.example.com
cp -r /home/fabric/config/certs/ordererOrganizations/example.com/tlsca/tlsca.example.com-cert.pem ~/users/User1@org1.example.com
cp -r /home/fabric/config/certs/ordererOrganizations/example.com/tlsca/tlsca.example.com-cert.pem ~/users/Admin@org2.example.com
cp -r /home/fabric/config/certs/ordererOrganizations/example.com/tlsca/tlsca.example.com-cert.pem ~/users/User1@org2.example.com

创建channel
在Admin@org1.exampl.com目录中执行

./peer.sh channel create -o orderer.example.com:7050 -c mychannel -f ../mychannel.tx --tls true --cafile tlsca.example.com-cert.pem

将peer加入channel

本文章为转载内容，我们尊重原作者对文章享有的著作权。如有内容错误或侵权问题，欢迎原作者联系我们进行内容更正或删除文章。

上一篇：kafka分区数扩容 kafka增加分区命令

下一篇：运维技术论坛运维技术网站运维技术社区弱电安防监控 IT 智能化物联网智慧运维平台是做什么的

提问和评论都可以，用心的回复会被更多人看到评论

发布评论

相关文章

官方博客	全部文章	热门标签	班级博客
了解我们	网站地图	意见反馈

鸿蒙开发者社区	51CTO学堂
51CTO	软考资讯