Ubuntu18.04hyperledgerfabric2.2.0测试网络，fabric学习(二）

一，删除以往容器

     在test-network文件夹下运行以下命令

./network.sh down

目的是删除以前运行的所有容器和工作

二，启动网络

在test-network文件夹下运行命令

./network.sh up

导出结果：

#这里只展示主要部分
Creating network "net_test" with the default driver
Creating volume "net_orderer.example.com" with default driver
Creating volume "net_peer0.org1.example.com" with default driver
Creating volume "net_peer0.org2.example.com" with default driver
Creating peer0.org1.example.com ... done
Creating peer0.org2.example.com ... done
Creating orderer.example.com    ... done
Creating cli                    ... done
CONTAINER ID   IMAGE                               COMMAND             CREATED         STATUS                  PORTS                              NAMES
60d5115b79e4   hyperledger/fabric-tools:latest     "/bin/bash"         1 second ago    Up Less than a second                                      cli
25ace0a7d9d9   hyperledger/fabric-orderer:latest   "orderer"           9 seconds ago   Up 2 seconds            0.0.0.0:7050->7050/tcp             orderer.example.com
bb780ec98bf8   hyperledger/fabric-peer:latest      "peer node start"   9 seconds ago   Up 2 seconds            0.0.0.0:7051->7051/tcp             peer0.org1.example.com
00a2f3a6b395   hyperledger/fabric-peer:latest      "peer node start"   9 seconds ago   Up 1 second             7051/tcp, 0.0.0.0:9051->9051/tcp   peer0.org2.example.com

三，创建通道

继续运行命令

#创建通道
./network.sh createChannel

导出结果：

#这里仅仅展示最后几行
2021-03-02 02:17:05.112 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initialized
2021-03-02 02:17:05.166 UTC [channelCmd] update -> INFO 002 Successfully submitted channel update
Anchor peer set for org 'Org2MSP' on channel 'mychannel'
Channel 'mychannel' joined

四，在通道启动链码

./network.sh deployCC -ccn basic -ccp ../asset-transfer-basic/chaincode-go -ccl go

导出结果：

#这里仅仅展示最后几行 这段启动过程比较长  耐心等待
Version: 1.0, Sequence: 1, Endorsement Plugin: escc, Validation Plugin: vscc, Approvals: [Org1MSP: true, Org2MSP: true]
Query chaincode definition successful on peer0.org2 on channel 'mychannel'
Chaincode initialization is not required

五，与网络进行互动

使用peer cli客户端去操作网络，可以通过cli客户端去调用部署智能合约，更新通道，或者安装部署新的智能合约（这部分我没懂什么意思，先按照步骤做，说不定后面就懂了）

在 存储库peer的bin文件夹中找到二进制文件fabric-samples。使用以下命令将这些二进制文件添加到您的CLI路径：

export PATH=${PWD}/../bin:$PATH

您还需要将设置FABRIC_CFG_PATH为指向存储库中的core.yaml文件fabric-samples：

export FABRIC_CFG_PATH=$PWD/../config/

设置允许org1操作peer cli的环境变量：

# Environment variables for Org1
export CORE_PEER_TLS_ENABLED=true
export CORE_PEER_LOCALMSPID="Org1MSP"
export CORE_PEER_TLS_ROOTCERT_FILE=${PWD}/organizations/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
export CORE_PEER_MSPCONFIGPATH=${PWD}/organizations/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
export CORE_PEER_ADDRESS=localhost:7051

运行以下命令以使用资产初始化分类帐：

peer chaincode invoke -o localhost:7050 --ordererTLSHostnameOverride orderer.example.com --tls --cafile "${PWD}/organizations/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem" -C mychannel -n basic --peerAddresses localhost:7051 --tlsRootCertFiles "${PWD}/organizations/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt" --peerAddresses localhost:9051 --tlsRootCertFiles "${PWD}/organizations/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt" -c '{"function":"InitLedger","Args":[]}'

成功结果导出：

peer chaincode invoke -o localhost:7050 --ordererTLSHostnameOverride orderer.example.com --tls --cafile "${PWD}/organizations/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem" -C mychannel -n basic --peerAddresses localhost:7051 --tlsRootCertFiles "${PWD}/organizations/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt" --peerAddresses localhost:9051 --tlsRootCertFiles "${PWD}/organizations/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt" -c '{"function":"InitLedger","Args":[]}'
2021-03-02 09:44:30.389 EET [chaincodeCmd] chaincodeInvokeOrQuery -> INFO 001 Chaincode invoke successful. result: status:200 

从cli查询分类账，运行下面的命令获取已添加到渠道分类账整的财产资产的列表：

peer chaincode query -C mychannel -n basic -c '{"Args":["GetAllAssets"]}'

导出成功结果：

[{"ID":"asset1","color":"blue","size":5,"owner":"Tomoko","appraisedValue":300},{"ID":"asset2","color":"red","size":5,"owner":"Brad","appraisedValue":400},{"ID":"asset3","color":"green","size":10,"owner":"Jin Soo","appraisedValue":500},{"ID":"asset4","color":"yellow","size":10,"owner":"Max","appraisedValue":600},{"ID":"asset5","color":"black","size":15,"owner":"Adriana","appraisedValue":700},{"ID":"asset6","color":"white","size":15,"owner":"Michel","appraisedValue":800}]

当网络成员要转移或更改分类帐上的资产时，将调用链码。使用以下命令通过调用资产转移（基本）链码来更改分类帐上资产的所有者：

peer chaincode invoke -o localhost:7050 --ordererTLSHostnameOverride orderer.example.com --tls --cafile "${PWD}/organizations/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem" -C mychannel -n basic --peerAddresses localhost:7051 --tlsRootCertFiles "${PWD}/organizations/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt" --peerAddresses localhost:9051 --tlsRootCertFiles "${PWD}/organizations/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt" -c '{"function":"TransferAsset","Args":["asset6","Christopher"]}'

调用链代码后，我们可以使用另一个查询来查看该调用如何更改了区块链分类账上的资产。由于我们已经查询过Org1对等体，因此我们可以借此机会查询Org2对等体上运行的链码。设置以下环境变量以作为Org2进行操作：

# Environment variables for Org2

export CORE_PEER_TLS_ENABLED=true
export CORE_PEER_LOCALMSPID="Org2MSP"
export CORE_PEER_TLS_ROOTCERT_FILE=${PWD}/organizations/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt
export CORE_PEER_MSPCONFIGPATH=${PWD}/organizations/peerOrganizations/org2.example.com/users/Admin@org2.example.com/msp
export CORE_PEER_ADDRESS=localhost:9051

现在，您可以查询运行在上的资产转移（基本）链码peer0.org2.example.com：

peer chaincode query -C mychannel -n basic -c '{"Args":["ReadAsset","asset6"]}'

我们可以看到资产6的所有者已经成为Christopher

到此，测试网络完成，记得关闭网络

./network.sh down

该命令将停止并删除节点和链码容器，删除组织加密材料，并从Docker注册表中移除链码映像。该命令还会从以前的运行中删除通道工件和docker卷，从而在遇到任何问题时允许您再次运行。