HyperLedger Fabric 1.4.4 启动网络

待我称王封你为后i 2023-02-14 10:21 9阅读 0赞

## 启动容器之前 ##

# 为了防止之前启动过区块链网络，所以需要删除之前可能遗留的文件，以免影响搭建
    # 删除各个节点生成的主机文件（这些文件可以用来恢复数据），配置不同可能目录也不相同
    rm -rf /var/hyperledger/*
    # 删除之前生成的证书等文件
    rm -rf crypto-config
    # 删除之前生成的创世区块等文件
    rm -rf channel-artifacts/*
    # 删除之前可能生成的 docker-compose-e2e.yaml 文件
    rm -rf docker-compose-e2e.yaml
    
    
    
    # 设置一些变量
    COMPOSE_PROJECT_NAME=net
    # docker镜像的版本
    IMAGE_TAG=1.4.4
    # channel id
    SYS_CHANNEL=peer-channel
    # 通道名称
    CHANNEL_NAME=peerchannel
    
    
    # 生成 peer 和 orderer 等节点证书等文件
    cryptogen generate --config=./crypto-config.yaml
    
    # 生成 connection-org1.json 和 connection-org2.json 文件，以便SDK连接区块链服务
    # 可能需要根据实际情况修改 ccp-generate.sh 脚本
    ./ccp-generate.sh
    
    # 重新拷贝生成 docker-compose-e2e.yaml
    # 这个 docker-compose-e2e.yaml 文件后面启动ca服务的时候会用到
    cp docker-compose-e2e-template.yaml docker-compose-e2e.yaml
    
    # 将密钥等内容填充进 docker-compose-e2e.yaml 文件
    CURRENT_DIR=$PWD
    cd crypto-config/peerOrganizations/org1.example.com/ca/
    PRIV_KEY=$(ls *_sk)
    cd "$CURRENT_DIR"
    sed -i "s/CA1_PRIVATE_KEY/${PRIV_KEY}/g" docker-compose-e2e.yaml
    
    # 生成创世区块文件 genesis.block ，也可能需要根据实际情况修改configtx.yaml文件中的内容
    # 下面三条命令需要根据搭建的共识类型选择其中一条执行
    # solo共识
    configtxgen -profile TwoOrgsOrdererGenesis -channelID $SYS_CHANNEL -outputBlock ./channel-artifacts/genesis.block
    # kafka共识集群
    configtxgen -profile SampleDevModeKafka -channelID $SYS_CHANNEL -outputBlock ./channel-artifacts/genesis.block
    # raft共识集群
    configtxgen -profile SampleMultiNodeEtcdRaft -channelID $SYS_CHANNEL -outputBlock ./channel-artifacts/genesis.block
    
    
    # 生成通道配置文件 channel.tx ，也可能需要根据实际情况修改configtx.yaml文件中的内容
    configtxgen -profile TwoOrgsChannel -outputCreateChannelTx ./channel-artifacts/channel.tx -channelID $CHANNEL_NAME
    
    # 生成锚节点配置文件 Org1MSPanchors.tx ，也可能需要根据实际情况修改configtx.yaml文件中的内容
    configtxgen -profile TwoOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org1MSPanchors.tx -channelID $CHANNEL_NAME -asOrg Org1MSP

## 启动网络 ##

修改`docker-compose-e2e.yaml`文件，将除了`ca服务`以外的内容全部去掉。  
然后运行`docker-compose -f 对应的yaml文件 up -d`

## 启动容器之后进入`cli`执行 ##

首先需要先进入`cli`容器的命令行界面：`docker exec -it cli bash`

# 创建通道，这里的 channelname， 必须是上面指定的 CHANNEL_NAME
    peer channel create -o orderer.example.com:7050 -c peerchannel -f ./channel-artifacts/channel.tx --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
    
    # 切换节点加入通道
    # peer0.org1.example.com
    CORE_PEER_ADDRESS=peer0.org1.example.com:7051
    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 
    peer channel join -b peerchannel.block
    # peer1.org1.example.com
    CORE_PEER_ADDRESS=peer1.org1.example.com:8051
    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 
    peer channel join -b peerchannel.block
    # peer2.org1.example.com
    CORE_PEER_ADDRESS=peer2.org1.example.com:9051
    CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer2.org1.example.com/tls/ca.crt 
    peer channel join -b peerchannel.block
    ......................
    
    # 切换节点安装链码
    # peer0.org1.example.com
    CORE_PEER_ADDRESS=peer0.org1.example.com:7051
    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 
    peer chaincode install -n medicalcc -v 1.0.0 -l golang -p github.com/chaincode/user
    # peer1.org1.example.com
    CORE_PEER_ADDRESS=peer1.org1.example.com:8051
    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 
    peer chaincode install -n medicalcc -v 1.0.0 -l golang -p github.com/chaincode/user
    # peer2.org1.example.com
    CORE_PEER_ADDRESS=peer2.org1.example.com:9051
    CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer2.org1.example.com/tls/ca.crt 
    peer chaincode install -n medicalcc -v 1.0.0 -l golang -p github.com/chaincode/user
    ......................
    
    # 初始化链码，并配置背书策略
    peer chaincode instantiate -o orderer.example.com:7050 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C peerchannel -n medicalcc -l golang -v 1.0.0 -c '{"Args":["Init"]}'  -P 'AND ('\''Org1MSP.peer'\'','\''Org2MSP.peer'\'')' # 调用链码 invoke 方法 peer chaincode invoke -o orderer.example.com:7050 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C peerchannel -n medicalcc --peerAddresses peer0.org1.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt -c '{ "Args":["ReplaceInto","{\"username\": \"zhangsan\", \"phone\": \"1234\", \"relation\": -1, \"source\": 2}", "cce0ab936fd611ea9a29005056ad6ccb", "d51da6516fd611ea9a29005056ad6ccb", "d9bed1a26fd611ea9a29005056ad6ccb"]}' # 调用链码 query 方法 peer chaincode query -C peerchannel -n medicalcc -c '{ "Args":["query","cce0ab936fd611ea9a29005056ad6ccb"]}'

## 升级链码 ##

运行之前需要根据情况修改节点名称和端口（尤其是orderer节点的），通道名称，链码名称和版本以及ca证书的路径。  
升级链码和初始化链码命令一样，只不过安装链码的时候，版本一定要比之前的高，最后将 instantiate（初始化）命令换成 upgrade（升级）命令。

# 切换节点安装链码
    # peer0.org1.example.com
    CORE_PEER_ADDRESS=peer0.org1.example.com:7051
    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 
    peer chaincode install -n medicalcc -v 1.0.1 -l golang -p github.com/chaincode/user
    # peer1.org1.example.com
    CORE_PEER_ADDRESS=peer1.org1.example.com:8051
    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 
    peer chaincode install -n medicalcc -v 1.0.1 -l golang -p github.com/chaincode/user
    # peer2.org1.example.com
    CORE_PEER_ADDRESS=peer2.org1.example.com:9051
    CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer2.org1.example.com/tls/ca.crt 
    peer chaincode install -n medicalcc -v 1.0.1 -l golang -p github.com/chaincode/user
    ......................
    
    # 升级链码，并指定背书策略
    peer chaincode upgrade -o orderer.example.com:7050 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C mychannel -n medicalcc -l golang -v 1.0.9 -c '{"Args":["initLedger"]}'  -P 'AND ('\''Org1MSP.peer'\'','\''Org2MSP.peer'\'')'