wonder4

Hyperledger Fabric 1.0 公有云安装7--集群部署记录

因为资源有限，决定在云上使用三台虚机，搭建e2e_cli的样例集群，使用的资源如下：

172.21.0.5 orderer.example.com

172.21.0.13 peer0.org1.example.com

172.21.0.15 peer0.org2.example.com

建立两个组，每个组只有一个peer，以下是各个配置文件和注意事项：

1.在各个主机上都可以支持独立运行e2e的伪分布式docker集群环境

2.在部署时，需要将各个环境初始化，特别是chaincode mycc的docker镜像，删除

3.orderer.example.com的配置文件，需要加extra_hosts，否则无法访问peer节点，这里要加全

# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

services:

  orderer.example.com:
    extends:
      file:   base/docker-compose-base.yaml
      service: orderer.example.com
    container_name: orderer.example.com
    extra_hosts:
     - "orderer.example.com:172.21.0.5"
     - "peer0.org1.example.com:172.21.0.13"
     - "peer0.org2.example.com:172.21.0.15"

docker-compose的启动和停止

$sudo cp docker-compose-cli.yaml orderer.yaml

按照上面的内容修改

$docker-compose -f orderer.yaml up -d
-d是以deamon方式启动，如果报错，则用docker ps查看时会看到docker并没有启动成功。这时可以去掉-d启动，查看输出的日志，找出问题
$docker-compose -f orderer.yaml down
关闭，会将channel等都删除，详细内容看script/scripts.sh，执行完down后，可以再次执行up，如果不执行down，关闭后再执行up则原来创建的channel都会起来

docker-compose -base.yaml内容修改，其实只修改其中的orderer段的内容即可，peer-base.yaml的内容可不动

ubuntu@VM-0-5-ubuntu:/data/gopath/src/github.com/hyperledger/fabric/examples/e2e_cli/base$ more docker-compose-base.yaml 
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

services:

  orderer.example.com:
    container_name: orderer.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]
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric
    command: orderer
    volumes:
    - ../channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block
    - ../crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/msp:/var/hyperledger/orderer/msp
    - ../crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/:/var/hyperledger/orderer/tls
    ports:
      - 7050:7050

  peer0.org1.example.com:
    container_name: peer0.org1.example.com
    extends:
      file: peer-base.yaml
      service: peer-base
    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
    volumes:
        - /var/run/:/host/var/run/
        - ../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


  peer0.org2.example.com:
    container_name: peer0.org2.example.com
    extends:
      file: peer-base.yaml
      service: peer-base
    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
    volumes:
        - /var/run/:/host/var/run/
        - ../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

4.peer节点，切换到172.21.0.13机器，保证两台机器内网可以ping通，然后修改如下的内容

拷贝一个peer节点的配置文件
$sudo cp docker-compose-cli.yaml peer.yaml
拷贝一个cli docker启动的配置文件，并且执行注册创建查询等脚本
$sudo cp docker-compose-cli.yaml cli.yaml
拷贝一个空的cli镜像脚本，用于以后的查询和操作
$sudo cp docker-compse-cli.yaml cli-no.yaml

peer.yaml

ubuntu@VM-0-13-ubuntu:/data/gopath/src/github.com/hyperledger/fabric/examples/e2e_cli$ more peer.yaml 
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

services:


  peer0.org1.example.com:
    container_name: peer0.org1.example.com
    extends:
      file:  base/docker-compose-base.yaml
      service: peer0.org1.example.com
    extra_hosts:
     - "orderer.example.com:172.21.0.5"
#     - "peer0.org1.example.com:172.21.0.13" 不要加自身，增加后启动会报错，端口绑定问题
     - "peer0.org2.example.com:172.21.0.15"

cli.yaml

ubuntu@VM-0-13-ubuntu:/data/gopath/src/github.com/hyperledger/fabric/examples/e2e_cli$ more cli.yaml 
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

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=true
      - 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/[email protected]/msp
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: /bin/bash -c './scripts/script.sh ${CHANNEL_NAME}; sleep $TIMEOUT'
    volumes:
        - /var/run/:/host/var/run/
        - ../chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/examples/chaincode/go
        - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
        - ./scripts:/opt/gopath/src/github.com/hyperledger/fabric/peer/scripts/
        - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
    extra_hosts:
     - "orderer.example.com:172.21.0.5"
     - "peer0.org1.example.com:172.21.0.13"
     - "peer0.org2.example.com:172.21.0.15"

cli-no.yaml

ubuntu@VM-0-13-ubuntu:/data/gopath/src/github.com/hyperledger/fabric/examples/e2e_cli$ more cli-no.yaml 
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

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=true
      - 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/[email protected]/msp
      - CHANNEL_NAME=mychannel
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    #command: /bin/bash -c './scripts/script.sh ${CHANNEL_NAME}; sleep $TIMEOUT'
    volumes:
        - /var/run/:/host/var/run/
        - ../chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/examples/chaincode/go
        - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
        - ./scripts:/opt/gopath/src/github.com/hyperledger/fabric/peer/scripts/
        - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
    extra_hosts:
     - "orderer.example.com:172.21.0.5"
     - "peer0.org1.example.com:172.21.0.13"
     - "peer0.org2.example.com:172.21.0.15"

scripts/scripts.sh，后半部分调用顺序

## Create channel
echo "Creating channel..."
createChannel

## Join all the peers to the channel
echo "Having all peers join the channel..."
joinChannel

## Set the anchor peers for each org in the channel
echo "Updating anchor peers for org1..."
updateAnchorPeers 0
echo "Updating anchor peers for org2..."
updateAnchorPeers 2

## Install chaincode on Peer0/Org1 and Peer2/Org2
echo "Installing chaincode on org1/peer0..."
installChaincode 0
echo "Install chaincode on org2/peer2..."
installChaincode 2

#Instantiate chaincode on Peer2/Org2
echo "Instantiating chaincode on org1/peer0..."
instantiateChaincode 0

#Query on chaincode on Peer0/Org1
echo "Querying chaincode on org1/peer0..."
chaincodeQuery 0 100

#Invoke on chaincode on Peer0/Org1
echo "Sending invoke transaction on org2/peer0..."
chaincodeInvoke 2

## Install chaincode on Peer3/Org2
#echo "Installing chaincode on org2/peer3..."
#installChaincode 3

#Query on chaincode on Peer3/Org2, check if the result is 90
echo "Querying chaincode on org2/peer0..."
chaincodeQuery 2 90

base/docker-compose-base.yaml，其实只涉及peer0.org1段的配置，注意端口映射，从docker到local的ip端口可以一致，因为docker运行在不同的主机上，在本例中，如果在一个机器上运行两个peer，则还要考虑org1的两个peer的端口映射问题。

ubuntu@VM-0-13-ubuntu:/data/gopath/src/github.com/hyperledger/fabric/examples/e2e_cli$ more base/docker-compose-base.yaml 
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

services:

  orderer.example.com:
    container_name: orderer.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]
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric
    command: orderer
    volumes:
    - ../channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block
    - ../crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/msp:/var/hyperledger/orderer/msp
    - ../crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/:/var/hyperledger/orderer/tls
    ports:
      - 7050:7050

  peer0.org1.example.com:
    container_name: peer0.org1.example.com
    extends:
      file: peer-base.yaml
      service: peer-base
    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
    volumes:
        - /var/run/:/host/var/run/
        - ../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

  peer0.org2.example.com:  
    container_name: peer0.org2.example.com
    extends:
      file: peer-base.yaml
      service: peer-base
    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
    volumes:
        - /var/run/:/host/var/run/
        - ../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

peer-base.yaml

ubuntu@VM-0-13-ubuntu:/data/gopath/src/github.com/hyperledger/fabric/examples/e2e_cli$ more base/peer-base.yaml 
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'
services:
  peer-base:
    image: hyperledger/fabric-peer
    environment:
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      # the following setting starts chaincode containers on the same
      # bridge network as the peers
      # https://docs.docker.com/compose/networking/
      - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=e2ecli_default
      #- CORE_LOGGING_LEVEL=ERROR
      - CORE_LOGGING_LEVEL=DEBUG
      - CORE_PEER_TLS_ENABLED=true
      - CORE_PEER_GOSSIP_USELEADERELECTION=true
      - CORE_PEER_GOSSIP_ORGLEADER=false
      - CORE_PEER_PROFILE_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

peer节点的启动和关闭

$docker-compose -f peer.yaml up -d
$docker-compose -f peer.yaml up 窗口输出日志
$docker-compose -f peer.yaml down 会清空peer中的内容，回到初始环境

cli镜像的启动，因为cli镜像启动时mount了script/scripts.sh脚本的内容，因此在启动cli镜像时，要考虑一下脚本中可能有执行不成功的内容，可以对脚本做修改，将peer0.org1和peer0.org2的内容分开执行，建议在peer0.org2启动后再执行cli，否则报错会比较多

ubuntu@VM-0-13-ubuntu:/data/gopath/src/github.com/hyperledger/fabric/examples/e2e_cli$ more cli.yaml 
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

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=true
      - 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/[email protected]/msp
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: /bin/bash -c './scripts/script.sh ${CHANNEL_NAME}; sleep $TIMEOUT'
    volumes:
        - /var/run/:/host/var/run/
        - ../chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/examples/chaincode/go
        - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
        - ./scripts:/opt/gopath/src/github.com/hyperledger/fabric/peer/scripts/
        - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
    extra_hosts:
     - "orderer.example.com:172.21.0.5"
     - "peer0.org1.example.com:172.21.0.13"
     - "peer0.org2.example.com:172.21.0.15"

5. peer0.org2节点的启动切换到第三台机器

peer.yaml

ubuntu@VM-0-15-ubuntu:/data/gopath/src/github.com/hyperledger/fabric/examples/e2e_cli$ more peer.yaml 
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

services:
  peer0.org2.example.com:
    container_name: peer0.org2.example.com
    extends:
      file:  base/docker-compose-base.yaml
      service: peer0.org2.example.com
    extra_hosts:
     - "orderer.example.com:172.21.0.5"
     - "peer0.org1.example.com:172.21.0.13"
#     - "peer0.org2.example.com:172.21.0.15"

cli.yaml

ubuntu@VM-0-15-ubuntu:/data/gopath/src/github.com/hyperledger/fabric/examples/e2e_cli$ more cli.yaml
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

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.org2.example.com:7051
      - CORE_PEER_LOCALMSPID=Org2MSP
      - CORE_CHAINCODE_STARTUPTIMEOUT=6000000
      - CORE_PEER_TLS_ENABLED=true
      - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/server.crt
      - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/server.key
      - 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
      - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/[email protected]/msp
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: /bin/bash -c './scripts/script.sh ${CHANNEL_NAME}; sleep $TIMEOUT'
    volumes:
        - /var/run/:/host/var/run/
        - ../chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/examples/chaincode/go
        - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
        - ./scripts:/opt/gopath/src/github.com/hyperledger/fabric/peer/scripts/
        - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
    extra_hosts:
     - "orderer.example.com:172.21.0.5"
     - "peer0.org1.example.com:172.21.0.13"
     - "peer0.org2.example.com:172.21.0.15"

cli-no.yaml

ubuntu@VM-0-15-ubuntu:/data/gopath/src/github.com/hyperledger/fabric/examples/e2e_cli$ more cli-no.yaml
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

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.org2.example.com:7051
      - CORE_PEER_LOCALMSPID=Org2MSP
      - CORE_CHAINCODE_STARTUPTIMEOUT=6000000
      - CORE_PEER_TLS_ENABLED=true
      - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/server.crt
      - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/server.key
      - 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
      - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/[email protected]/msp
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    #command: /bin/bash -c './scripts/script.sh ${CHANNEL_NAME}; sleep $TIMEOUT'
    volumes:
        - /var/run/:/host/var/run/
        - ../chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/examples/chaincode/go
        - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
        - ./scripts:/opt/gopath/src/github.com/hyperledger/fabric/peer/scripts/
        - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
    extra_hosts:
     - "orderer.example.com:172.21.0.5"
     - "peer0.org1.example.com:172.21.0.13"
     - "peer0.org2.example.com:172.21.0.15"

还是要注意修改script/scripts.sh的内容，在cli.yaml中，cli集群启动后会执行这个脚本。

scripts.sh

## Create channel
#echo "Creating channel..."
#createChannel

## Join all the peers to the channel
#echo "Having all peers join the channel..."
#joinChannel

## Set the anchor peers for each org in the channel
#echo "Updating anchor peers for org1..."
#updateAnchorPeers 0
#echo "Updating anchor peers for org2..."
#updateAnchorPeers 2

## Install chaincode on Peer0/Org1 and Peer2/Org2
#echo "Installing chaincode on org1/peer0..."
#installChaincode 0
#echo "Install chaincode on org2/peer2..."
#installChaincode 2

#Instantiate chaincode on Peer2/Org2
#echo "Instantiating chaincode on org2/peer2..."
#instantiateChaincode 2

#Query on chaincode on Peer0/Org1
#echo "Querying chaincode on org1/peer0..."
#chaincodeQuery 0 100

#Invoke on chaincode on Peer0/Org1
echo "Sending invoke transaction on org2/peer0..."
chaincodeInvoke 2

## Install chaincode on Peer3/Org2
#echo "Installing chaincode on org2/peer3..."
#installChaincode 3

#Query on chaincode on Peer3/Org2, check if the result is 90
echo "Querying chaincode on org2/peer2..."
#chaincodeQuery 3 90
chaincodeQuery 2 90

base/docker-compose-base.yaml

ubuntu@VM-0-15-ubuntu:/data/gopath/src/github.com/hyperledger/fabric/examples/e2e_cli$ more base/docker-compose-base.yaml

# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

services:

  orderer.example.com:
    container_name: orderer.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]
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric
    command: orderer
    volumes:
    - ../channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block
    - ../crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/msp:/var/hyperledger/orderer/msp
    - ../crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/:/var/hyperledger/orderer/tls
    ports:
      - 7050:7050

  peer0.org1.example.com:
    container_name: peer0.org1.example.com
    extends:
      file: peer-base.yaml
      service: peer-base
    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
    volumes:
        - /var/run/:/host/var/run/
        - ../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

  peer1.org1.example.com:
    container_name: peer1.org1.example.com
    extends:
      file: peer-base.yaml
      service: peer-base
    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_GOSSIP_BOOTSTRAP=peer0.org1.example.com:7051
      - CORE_PEER_LOCALMSPID=Org1MSP
    volumes:
        - /var/run/:/host/var/run/
        - ../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

  peer0.org2.example.com:
    container_name: peer0.org2.example.com
    extends:
      file: peer-base.yaml
      service: peer-base
    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
    volumes:
        - /var/run/:/host/var/run/
        - ../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

  peer1.org2.example.com:
    container_name: peer1.org2.example.com
    extends:
      file: peer-base.yaml
      service: peer-base
    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_GOSSIP_BOOTSTRAP=peer0.org2.example.com:7051
      - CORE_PEER_LOCALMSPID=Org2MSP
    volumes:
        - /var/run/:/host/var/run/
        - ../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

base/peer-base.yaml

ubuntu@VM-0-15-ubuntu:/data/gopath/src/github.com/hyperledger/fabric/examples/e2e_cli$ more base/peer-base.yaml 
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'
services:
  peer-base:
    image: hyperledger/fabric-peer
    environment:
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      # the following setting starts chaincode containers on the same
      # bridge network as the peers
      # https://docs.docker.com/compose/networking/
      - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=e2ecli_default
      #- CORE_LOGGING_LEVEL=ERROR
      - CORE_LOGGING_LEVEL=DEBUG
      - CORE_PEER_TLS_ENABLED=true
      - CORE_PEER_GOSSIP_USELEADERELECTION=true
      - CORE_PEER_GOSSIP_ORGLEADER=false
      - CORE_PEER_PROFILE_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

6.整体环境测试脚本执行顺序

172.21.0.5:在e2e_cli目录下
$ docker-compose -f orderer.yaml up -d
172.21.0.13:
$docker-compose -f peer.yaml up -d
172.21.0.15
$docker-compose -f peer.yaml up -d
172.21.0.13:
$docker-compose -f cli.yaml up
查看这个执行的结果

正确的执行结果输出如下：

ubuntu@VM-0-13-ubuntu:/data/gopath/src/github.com/hyperledger/fabric/examples/e2e_cli$ docker-compose -f cli.yaml up
WARNING: The CHANNEL_NAME variable is not set. Defaulting to a blank string.
WARNING: The TIMEOUT variable is not set. Defaulting to a blank string.
WARNING: Found orphan containers (peer0.org1.example.com) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
Creating cli ... done
Attaching to cli
cli    | 
cli    |  ____    _____      _      ____    _____           _____   ____    _____ 
cli    | / ___|  |_   _|    / \    |  _ \  |_   _|         | ____| |___ \  | ____|
cli    | \___ \    | |     / _ \   | |_) |   | |    _____  |  _|     __) | |  _|  
cli    |  ___) |   | |    / ___ \  |  _ <    | |   |_____| | |___   / __/  | |___ 
cli    | |____/    |_|   /_/   \_\ |_| \_\   |_|           |_____| |_____| |_____|
cli    | 
cli    | Channel name : mychannel
cli    | Creating channel...
cli    | 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
cli    | 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
cli    | CORE_PEER_LOCALMSPID=Org1MSP
cli    | CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
cli    | 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
cli    | CORE_PEER_TLS_ENABLED=true
cli    | CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/[email protected]/msp
cli    | CORE_PEER_ID=cli
cli    | CORE_LOGGING_LEVEL=DEBUG
cli    | CORE_PEER_ADDRESS=peer0.org1.example.com:7051
cli    | 2018-04-15 04:54:11.000 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
cli    | 2018-04-15 04:54:11.000 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
cli    | 2018-04-15 04:54:11.003 UTC [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized
cli    | 2018-04-15 04:54:11.004 UTC [msp] GetLocalMSP -> DEBU 004 Returning existing local MSP
cli    | 2018-04-15 04:54:11.004 UTC [msp] GetDefaultSigningIdentity -> DEBU 005 Obtaining default signing identity
cli    | 2018-04-15 04:54:11.004 UTC [msp] GetLocalMSP -> DEBU 006 Returning existing local MSP
cli    | 2018-04-15 04:54:11.004 UTC [msp] GetDefaultSigningIdentity -> DEBU 007 Obtaining default signing identity
cli    | 2018-04-15 04:54:11.004 UTC [msp/identity] Sign -> DEBU 008 Sign: plaintext: 0A88060A074F7267314D535012FC052D...53616D706C65436F6E736F727469756D 
cli    | 2018-04-15 04:54:11.004 UTC [msp/identity] Sign -> DEBU 009 Sign: digest: DE80A9F2D4F19718787BC5870D42C2015B782CC0069816A9E37FB71C4A79C3AB 
cli    | 2018-04-15 04:54:11.004 UTC [msp] GetLocalMSP -> DEBU 00a Returning existing local MSP
cli    | 2018-04-15 04:54:11.004 UTC [msp] GetDefaultSigningIdentity -> DEBU 00b Obtaining default signing identity
cli    | 2018-04-15 04:54:11.004 UTC [msp] GetLocalMSP -> DEBU 00c Returning existing local MSP
cli    | 2018-04-15 04:54:11.004 UTC [msp] GetDefaultSigningIdentity -> DEBU 00d Obtaining default signing identity
cli    | 2018-04-15 04:54:11.004 UTC [msp/identity] Sign -> DEBU 00e Sign: plaintext: 0ABF060A1508021A0608F3B5CBD60522...2DFF942434851C3A2AD6662ECA36A374 
cli    | 2018-04-15 04:54:11.004 UTC [msp/identity] Sign -> DEBU 00f Sign: digest: 4768892C9B67DE6BB523EAB3B9A7151AE43F4B7A2DABDD53E63EE8B17D1BF157 
cli    | 2018-04-15 04:54:11.097 UTC [msp] GetLocalMSP -> DEBU 010 Returning existing local MSP
cli    | 2018-04-15 04:54:11.097 UTC [msp] GetDefaultSigningIdentity -> DEBU 011 Obtaining default signing identity
cli    | 2018-04-15 04:54:11.098 UTC [msp] GetLocalMSP -> DEBU 012 Returning existing local MSP
cli    | 2018-04-15 04:54:11.098 UTC [msp] GetDefaultSigningIdentity -> DEBU 013 Obtaining default signing identity
cli    | 2018-04-15 04:54:11.098 UTC [msp/identity] Sign -> DEBU 014 Sign: plaintext: 0ABF060A1508021A0608F3B5CBD60522...DAD1528F622012080A021A0012021A00 
cli    | 2018-04-15 04:54:11.098 UTC [msp/identity] Sign -> DEBU 015 Sign: digest: 96D37D986D406473CE18CC74F1671F6D90727907B81A8AAEB8C1C7BC5B3D513F 
cli    | 2018-04-15 04:54:11.143 UTC [channelCmd] readBlock -> DEBU 016 Got status:*orderer.DeliverResponse_Status 
cli    | 2018-04-15 04:54:11.143 UTC [msp] GetLocalMSP -> DEBU 017 Returning existing local MSP
cli    | 2018-04-15 04:54:11.143 UTC [msp] GetDefaultSigningIdentity -> DEBU 018 Obtaining default signing identity
cli    | 2018-04-15 04:54:11.193 UTC [channelCmd] InitCmdFactory -> INFO 019 Endorser and orderer connections initialized
cli    | 2018-04-15 04:54:11.393 UTC [msp] GetLocalMSP -> DEBU 01a Returning existing local MSP
cli    | 2018-04-15 04:54:11.393 UTC [msp] GetDefaultSigningIdentity -> DEBU 01b Obtaining default signing identity
cli    | 2018-04-15 04:54:11.393 UTC [msp] GetLocalMSP -> DEBU 01c Returning existing local MSP
cli    | 2018-04-15 04:54:11.393 UTC [msp] GetDefaultSigningIdentity -> DEBU 01d Obtaining default signing identity
cli    | 2018-04-15 04:54:11.393 UTC [msp/identity] Sign -> DEBU 01e Sign: plaintext: 0ABF060A1508021A0608F3B5CBD60522...26C2221E87DB12080A021A0012021A00 
cli    | 2018-04-15 04:54:11.393 UTC [msp/identity] Sign -> DEBU 01f Sign: digest: B3826453EE3BB44344D3A6E29246829F32156979E09DFC020FC5949DEB61F350 
cli    | 2018-04-15 04:54:11.400 UTC [channelCmd] readBlock -> DEBU 020 Received block:0 
cli    | 2018-04-15 04:54:11.400 UTC [main] main -> INFO 021 Exiting.....
cli    | ===================== Channel "mychannel" is created successfully ===================== 
cli    | 
cli    | Having all peers join the channel...
cli    | 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
cli    | 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
cli    | CORE_PEER_LOCALMSPID=Org1MSP
cli    | CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
cli    | 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
cli    | CORE_PEER_TLS_ENABLED=true
cli    | CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/[email protected]/msp
cli    | CORE_PEER_ID=cli
cli    | CORE_LOGGING_LEVEL=DEBUG
cli    | CORE_PEER_ADDRESS=peer0.org1.example.com:7051
cli    | 2018-04-15 04:54:11.438 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
cli    | 2018-04-15 04:54:11.438 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
cli    | 2018-04-15 04:54:11.441 UTC [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized
cli    | 2018-04-15 04:54:11.442 UTC [msp/identity] Sign -> DEBU 004 Sign: plaintext: 0A86070A5C08011A0C08F3B5CBD60510...25BB45EE77B11A080A000A000A000A00 
cli    | 2018-04-15 04:54:11.442 UTC [msp/identity] Sign -> DEBU 005 Sign: digest: 9BA866AB9FEAE440806A25E21840528A4FDFA114CF6D2ADA573A7A8FA5152716 
cli    | 2018-04-15 04:54:11.487 UTC [channelCmd] executeJoin -> INFO 006 Peer joined the channel!
cli    | 2018-04-15 04:54:11.487 UTC [main] main -> INFO 007 Exiting.....
cli    | ===================== PEER0 joined on the channel "mychannel" ===================== 
cli    | 
cli    | 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
cli    | 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
cli    | CORE_PEER_LOCALMSPID=Org2MSP
cli    | CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
cli    | 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
cli    | CORE_PEER_TLS_ENABLED=true
cli    | CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/[email protected]/msp
cli    | CORE_PEER_ID=cli
cli    | CORE_LOGGING_LEVEL=DEBUG
cli    | CORE_PEER_ADDRESS=peer0.org2.example.com:7051
cli    | 2018-04-15 04:54:13.534 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
cli    | 2018-04-15 04:54:13.534 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
cli    | 2018-04-15 04:54:13.538 UTC [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized
cli    | 2018-04-15 04:54:13.539 UTC [msp/identity] Sign -> DEBU 004 Sign: plaintext: 0A8A070A5C08011A0C08F5B5CBD60510...25BB45EE77B11A080A000A000A000A00 
cli    | 2018-04-15 04:54:13.539 UTC [msp/identity] Sign -> DEBU 005 Sign: digest: ABCDB9F2CEB1E9972F32EFF9BD3277C963458B9390940B4BF1C5A6BD2BAED716 
cli    | 2018-04-15 04:54:13.581 UTC [channelCmd] executeJoin -> INFO 006 Peer joined the channel!
cli    | 2018-04-15 04:54:13.581 UTC [main] main -> INFO 007 Exiting.....
cli    | ===================== PEER2 joined on the channel "mychannel" ===================== 
cli    | 
cli    | Updating anchor peers for org1...
cli    | 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
cli    | 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
cli    | CORE_PEER_LOCALMSPID=Org1MSP
cli    | CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
cli    | 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
cli    | CORE_PEER_TLS_ENABLED=true
cli    | CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/[email protected]/msp
cli    | CORE_PEER_ID=cli
cli    | CORE_LOGGING_LEVEL=DEBUG
cli    | CORE_PEER_ADDRESS=peer0.org1.example.com:7051
cli    | 2018-04-15 04:54:15.618 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
cli    | 2018-04-15 04:54:15.618 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
cli    | 2018-04-15 04:54:15.621 UTC [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized
cli    | 2018-04-15 04:54:15.621 UTC [msp] GetLocalMSP -> DEBU 004 Returning existing local MSP
cli    | 2018-04-15 04:54:15.621 UTC [msp] GetDefaultSigningIdentity -> DEBU 005 Obtaining default signing identity
cli    | 2018-04-15 04:54:15.621 UTC [msp] GetLocalMSP -> DEBU 006 Returning existing local MSP
cli    | 2018-04-15 04:54:15.621 UTC [msp] GetDefaultSigningIdentity -> DEBU 007 Obtaining default signing identity
cli    | 2018-04-15 04:54:15.621 UTC [msp/identity] Sign -> DEBU 008 Sign: plaintext: 0A88060A074F7267314D535012FC052D...2A0641646D696E732A0641646D696E73 
cli    | 2018-04-15 04:54:15.621 UTC [msp/identity] Sign -> DEBU 009 Sign: digest: 8883F8A62AFCCCFD6198A8FD30D36AC62A6979D9469924E0F207325DC6B2226F 
cli    | 2018-04-15 04:54:15.621 UTC [msp] GetLocalMSP -> DEBU 00a Returning existing local MSP
cli    | 2018-04-15 04:54:15.621 UTC [msp] GetDefaultSigningIdentity -> DEBU 00b Obtaining default signing identity
cli    | 2018-04-15 04:54:15.622 UTC [msp] GetLocalMSP -> DEBU 00c Returning existing local MSP
cli    | 2018-04-15 04:54:15.622 UTC [msp] GetDefaultSigningIdentity -> DEBU 00d Obtaining default signing identity
cli    | 2018-04-15 04:54:15.622 UTC [msp/identity] Sign -> DEBU 00e Sign: plaintext: 0ABF060A1508021A0608F7B5CBD60522...DAC89DFC512D03F99F71668252C10F50 
cli    | 2018-04-15 04:54:15.622 UTC [msp/identity] Sign -> DEBU 00f Sign: digest: E824E39BF97357A9ECDAA6ACF47DF6F45991DDF23DCC75ECB6A6785B641C164F 
cli    | 2018-04-15 04:54:15.649 UTC [main] main -> INFO 010 Exiting.....
cli    | ===================== Anchor peers for org "Org1MSP" on "mychannel" is updated successfully ===================== 
cli    | 
cli    | Updating anchor peers for org2...
cli    | 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
cli    | 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
cli    | CORE_PEER_LOCALMSPID=Org2MSP
cli    | CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
cli    | 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
cli    | CORE_PEER_TLS_ENABLED=true
cli    | CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/[email protected]/msp
cli    | CORE_PEER_ID=cli
cli    | CORE_LOGGING_LEVEL=DEBUG
cli    | CORE_PEER_ADDRESS=peer0.org2.example.com:7051
cli    | 2018-04-15 04:54:20.693 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
cli    | 2018-04-15 04:54:20.693 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
cli    | 2018-04-15 04:54:20.696 UTC [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized
cli    | 2018-04-15 04:54:20.696 UTC [msp] GetLocalMSP -> DEBU 004 Returning existing local MSP
cli    | 2018-04-15 04:54:20.696 UTC [msp] GetDefaultSigningIdentity -> DEBU 005 Obtaining default signing identity
cli    | 2018-04-15 04:54:20.696 UTC [msp] GetLocalMSP -> DEBU 006 Returning existing local MSP
cli    | 2018-04-15 04:54:20.696 UTC [msp] GetDefaultSigningIdentity -> DEBU 007 Obtaining default signing identity
cli    | 2018-04-15 04:54:20.696 UTC [msp/identity] Sign -> DEBU 008 Sign: plaintext: 0A8C060A074F7267324D53501280062D...2A0641646D696E732A0641646D696E73 
cli    | 2018-04-15 04:54:20.696 UTC [msp/identity] Sign -> DEBU 009 Sign: digest: 59624AD92F7F9F9A3265CACBB14831CC5575BC53247FA070BFF7E1A2F226A27D 
cli    | 2018-04-15 04:54:20.697 UTC [msp] GetLocalMSP -> DEBU 00a Returning existing local MSP
cli    | 2018-04-15 04:54:20.697 UTC [msp] GetDefaultSigningIdentity -> DEBU 00b Obtaining default signing identity
cli    | 2018-04-15 04:54:20.697 UTC [msp] GetLocalMSP -> DEBU 00c Returning existing local MSP
cli    | 2018-04-15 04:54:20.697 UTC [msp] GetDefaultSigningIdentity -> DEBU 00d Obtaining default signing identity
cli    | 2018-04-15 04:54:20.697 UTC [msp/identity] Sign -> DEBU 00e Sign: plaintext: 0AC3060A1508021A0608FCB5CBD60522...27069DA9A535BB56FD39AC8B3D89D95E 
cli    | 2018-04-15 04:54:20.697 UTC [msp/identity] Sign -> DEBU 00f Sign: digest: F96E61338D134C04D90D3CE5D7C0CC0DEDEE929538673956A811E8EAB295DF44 
cli    | 2018-04-15 04:54:20.728 UTC [main] main -> INFO 010 Exiting.....
cli    | ===================== Anchor peers for org "Org2MSP" on "mychannel" is updated successfully ===================== 
cli    | 
cli    | Installing chaincode on org1/peer0...
cli    | 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
cli    | 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
cli    | CORE_PEER_LOCALMSPID=Org1MSP
cli    | CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
cli    | 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
cli    | CORE_PEER_TLS_ENABLED=true
cli    | CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/[email protected]/msp
cli    | CORE_PEER_ID=cli
cli    | CORE_LOGGING_LEVEL=DEBUG
cli    | CORE_PEER_ADDRESS=peer0.org1.example.com:7051
cli    | 2018-04-15 04:54:25.773 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
cli    | 2018-04-15 04:54:25.774 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
cli    | 2018-04-15 04:54:25.774 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc
cli    | 2018-04-15 04:54:25.774 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc
cli    | 2018-04-15 04:54:25.824 UTC [golang-platform] getCodeFromFS -> DEBU 005 getCodeFromFS github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02
cli    | 2018-04-15 04:54:25.962 UTC [golang-platform] func1 -> DEBU 006 Discarding GOROOT package fmt
cli    | 2018-04-15 04:54:25.962 UTC [golang-platform] func1 -> DEBU 007 Discarding provided package github.com/hyperledger/fabric/core/chaincode/shim
cli    | 2018-04-15 04:54:25.962 UTC [golang-platform] func1 -> DEBU 008 Discarding provided package github.com/hyperledger/fabric/protos/peer
cli    | 2018-04-15 04:54:25.962 UTC [golang-platform] func1 -> DEBU 009 Discarding GOROOT package strconv
cli    | 2018-04-15 04:54:25.962 UTC [golang-platform] GetDeploymentPayload -> DEBU 00a done
cli    | 2018-04-15 04:54:25.963 UTC [msp/identity] Sign -> DEBU 00b Sign: plaintext: 0A86070A5C08031A0C0881B6CBD60510...5F74FD270000FFFFCEF44F9B002C0000 
cli    | 2018-04-15 04:54:25.963 UTC [msp/identity] Sign -> DEBU 00c Sign: digest: 5B0E9D0ACAA73D265BEEC6557D0FC3D1FAE649C46E35A837248EA465B18F0D2C 
cli    | 2018-04-15 04:54:25.969 UTC [chaincodeCmd] install -> DEBU 00d Installed remotely response: 
cli    | 2018-04-15 04:54:25.969 UTC [main] main -> INFO 00e Exiting.....
cli    | ===================== Chaincode is installed on remote peer PEER0 ===================== 
cli    | 
cli    | Install chaincode on org2/peer2...
cli    | 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
cli    | 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
cli    | CORE_PEER_LOCALMSPID=Org2MSP
cli    | CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
cli    | 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
cli    | CORE_PEER_TLS_ENABLED=true
cli    | CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/[email protected]/msp
cli    | CORE_PEER_ID=cli
cli    | CORE_LOGGING_LEVEL=DEBUG
cli    | CORE_PEER_ADDRESS=peer0.org2.example.com:7051
cli    | 2018-04-15 04:54:26.015 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
cli    | 2018-04-15 04:54:26.015 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
cli    | 2018-04-15 04:54:26.015 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc
cli    | 2018-04-15 04:54:26.015 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc
cli    | 2018-04-15 04:54:26.062 UTC [golang-platform] getCodeFromFS -> DEBU 005 getCodeFromFS github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02
cli    | 2018-04-15 04:54:26.193 UTC [golang-platform] func1 -> DEBU 006 Discarding GOROOT package fmt
cli    | 2018-04-15 04:54:26.193 UTC [golang-platform] func1 -> DEBU 007 Discarding provided package github.com/hyperledger/fabric/core/chaincode/shim
cli    | 2018-04-15 04:54:26.193 UTC [golang-platform] func1 -> DEBU 008 Discarding provided package github.com/hyperledger/fabric/protos/peer
cli    | 2018-04-15 04:54:26.194 UTC [golang-platform] func1 -> DEBU 009 Discarding GOROOT package strconv
cli    | 2018-04-15 04:54:26.194 UTC [golang-platform] GetDeploymentPayload -> DEBU 00a done
cli    | 2018-04-15 04:54:26.196 UTC [msp/identity] Sign -> DEBU 00b Sign: plaintext: 0A89070A5B08031A0B0882B6CBD60510...5F74FD270000FFFFCEF44F9B002C0000 
cli    | 2018-04-15 04:54:26.196 UTC [msp/identity] Sign -> DEBU 00c Sign: digest: 7AC05CD4271A4B6E304EBAF6B8465182784BAF58AA93C7F5C969C7FE85BDF09E 
cli    | 2018-04-15 04:54:26.210 UTC [chaincodeCmd] install -> DEBU 00d Installed remotely response: 
cli    | 2018-04-15 04:54:26.211 UTC [main] main -> INFO 00e Exiting.....
cli    | ===================== Chaincode is installed on remote peer PEER2 ===================== 
cli    | 
cli    | Instantiating chaincode on org1/peer0...
cli    | 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
cli    | 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
cli    | CORE_PEER_LOCALMSPID=Org1MSP
cli    | CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
cli    | 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
cli    | CORE_PEER_TLS_ENABLED=true
cli    | CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/[email protected]/msp
cli    | CORE_PEER_ID=cli
cli    | CORE_LOGGING_LEVEL=DEBUG
cli    | CORE_PEER_ADDRESS=peer0.org1.example.com:7051
cli    | 2018-04-15 04:54:26.252 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
cli    | 2018-04-15 04:54:26.252 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
cli    | 2018-04-15 04:54:26.255 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc
cli    | 2018-04-15 04:54:26.255 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc
cli    | 2018-04-15 04:54:26.256 UTC [msp/identity] Sign -> DEBU 005 Sign: plaintext: 0A90070A6608031A0B0882B6CBD60510...324D53500A04657363630A0476736363 
cli    | 2018-04-15 04:54:26.256 UTC [msp/identity] Sign -> DEBU 006 Sign: digest: B469045FFCB3B68A614DD845C483B33F67F0879FBF6D0D46BE39AEE8581919A8 
cli    | 2018-04-15 04:54:26.693 UTC [msp/identity] Sign -> DEBU 007 Sign: plaintext: 0A90070A6608031A0B0882B6CBD60510...D94CDA0BBC568F20625EA86227A11815 
cli    | 2018-04-15 04:54:26.693 UTC [msp/identity] Sign -> DEBU 008 Sign: digest: 9F4D8490CF9B530DBB6547B567D63805E0698B9175704C4079CED0B4335C916F 
cli    | 2018-04-15 04:54:26.695 UTC [main] main -> INFO 009 Exiting.....
cli    | ===================== Chaincode Instantiation on PEER0 on channel 'mychannel' is successful ===================== 
cli    | 
cli    | Querying chaincode on org1/peer0...
cli    | ===================== Querying on PEER0 on channel 'mychannel'... ===================== 
cli    | 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
cli    | 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
cli    | CORE_PEER_LOCALMSPID=Org1MSP
cli    | CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
cli    | 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
cli    | CORE_PEER_TLS_ENABLED=true
cli    | CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/[email protected]/msp
cli    | CORE_PEER_ID=cli
cli    | CORE_LOGGING_LEVEL=DEBUG
cli    | CORE_PEER_ADDRESS=peer0.org1.example.com:7051
cli    | Attempting to Query PEER0 ...3 secs
cli    | 
cli    | 2018-04-15 04:54:29.738 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
cli    | 2018-04-15 04:54:29.738 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
cli    | 2018-04-15 04:54:29.738 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc
cli    | 2018-04-15 04:54:29.738 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc
cli    | 2018-04-15 04:54:29.738 UTC [msp/identity] Sign -> DEBU 005 Sign: plaintext: 0A91070A6708031A0C0885B6CBD60510...6D7963631A0A0A0571756572790A0161 
cli    | 2018-04-15 04:54:29.738 UTC [msp/identity] Sign -> DEBU 006 Sign: digest: AD98FA6F81E2C7A303D2229E78401CCF6570AF0880488718B293B94375E23D58 
cli    | Query Result: 100
cli    | 2018-04-15 04:54:29.748 UTC [main] main -> INFO 007 Exiting.....
cli    | ===================== Query on PEER0 on channel 'mychannel' is successful ===================== 
cli    | Sending invoke transaction on org2/peer0...
cli    | 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
cli    | 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
cli    | CORE_PEER_LOCALMSPID=Org2MSP
cli    | CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
cli    | 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
cli    | CORE_PEER_TLS_ENABLED=true
cli    | CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/[email protected]/msp
cli    | CORE_PEER_ID=cli
cli    | CORE_LOGGING_LEVEL=DEBUG
cli    | CORE_PEER_ADDRESS=peer0.org2.example.com:7051
cli    | 2018-04-15 04:54:29.796 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
cli    | 2018-04-15 04:54:29.796 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
cli    | 2018-04-15 04:54:29.799 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc
cli    | 2018-04-15 04:54:29.799 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc
cli    | 2018-04-15 04:54:29.799 UTC [msp/identity] Sign -> DEBU 005 Sign: plaintext: 0A95070A6708031A0C0885B6CBD60510...696E766F6B650A01610A01620A023130 
cli    | 2018-04-15 04:54:29.799 UTC [msp/identity] Sign -> DEBU 006 Sign: digest: 0F5290BBE1520FF900525296EAE67F7548780607BE0C94700BDE5D3A58B76ADA 
cli    | 2018-04-15 04:54:43.202 UTC [msp/identity] Sign -> DEBU 007 Sign: plaintext: 0A95070A6708031A0C0885B6CBD60510...B67A5E10A7E8D9D20E854DE0D41E5EF0 
cli    | 2018-04-15 04:54:43.202 UTC [msp/identity] Sign -> DEBU 008 Sign: digest: 11ACDC8EE6668208EF9FA6DD9AE386D6F51F8E26286C798A56A841CE60695730 
cli    | 2018-04-15 04:54:43.206 UTC [chaincodeCmd] chaincodeInvokeOrQuery -> DEBU 009 ESCC invoke result: version:1 response: payload:"\n \235K\027\377\035R\201\321\246A\026\nB\2619.\037\245dF!\256\251\177\022\007\311P\024\231\277\241\022Y\nE\022\024\n\004lscc\022\014\n\n\n\004mycc\022\002\010\003\022-\n\004mycc\022%\n\007\n\001a\022\002\010\003\n\007\n\001b\022\002\010\003\032\007\n\001a\032\00290\032\010\n\001b\032\003210\032\003\010\310\001\"\013\022\004mycc\032\0031.0" endorsement:H;\204\006\304f\304^l3.c\333n\370:B./\276\213\276\306\211\332\3137\014?\267(\002 K\333G\212\377\235\215\334W\n\330\206F\252K\345\266z^\020\247\350\331\322\016\205M\340\324\036^\360" > 
cli    | 2018-04-15 04:54:43.206 UTC [chaincodeCmd] chaincodeInvokeOrQuery -> INFO 00a Chaincode invoke successful. result: status:200 
cli    | 2018-04-15 04:54:43.206 UTC [main] main -> INFO 00b Exiting.....
cli    | ===================== Invoke transaction on PEER2 on channel 'mychannel' is successful ===================== 
cli    | 
cli    | Querying chaincode on org2/peer0...
cli    | ===================== Querying on PEER2 on channel 'mychannel'... ===================== 
cli    | 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
cli    | 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
cli    | CORE_PEER_LOCALMSPID=Org2MSP
cli    | CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
cli    | 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
cli    | CORE_PEER_TLS_ENABLED=true
cli    | CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/users/[email protected]/msp
cli    | CORE_PEER_ID=cli
cli    | CORE_LOGGING_LEVEL=DEBUG
cli    | CORE_PEER_ADDRESS=peer0.org2.example.com:7051
cli    | Attempting to Query PEER2 ...3 secs
cli    | 
cli    | 2018-04-15 04:54:46.249 UTC [msp] GetLocalMSP -> DEBU 001 Returning existing local MSP
cli    | 2018-04-15 04:54:46.249 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
cli    | 2018-04-15 04:54:46.249 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 003 Using default escc
cli    | 2018-04-15 04:54:46.249 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default vscc
cli    | 2018-04-15 04:54:46.249 UTC [msp/identity] Sign -> DEBU 005 Sign: plaintext: 0A94070A6608031A0B0896B6CBD60510...6D7963631A0A0A0571756572790A0161 
cli    | 2018-04-15 04:54:46.250 UTC [msp/identity] Sign -> DEBU 006 Sign: digest: 27EC67C5F67BB02306325EC6444D422A4E2EA8095F2BCB01D3E2A5AB23FA7271 
cli    | Query Result: 90
cli    | 2018-04-15 04:54:46.257 UTC [main] main -> INFO 007 Exiting.....
cli    | ===================== Query on PEER2 on channel 'mychannel' is successful ===================== 
cli    | 
cli    | ===================== All GOOD, End-2-End execution completed ===================== 
cli    | 
cli    | 
cli    |  _____   _   _   ____            _____   ____    _____ 
cli    | | ____| | \ | | |  _ \          | ____| |___ \  | ____|
cli    | |  _|   |  \| | | | | |  _____  |  _|     __) | |  _|  
cli    | | |___  | |\  | | |_| | |_____| | |___   / __/  | |___ 
cli    | |_____| |_| \_| |____/          |_____| |_____| |_____|
cli    | 
cli    | sleep: missing operand
cli    | Try 'sleep --help' for more information.
cli exited with code 1

你可能感兴趣的:(Blockchain)

区块链入门 Mindfulness code 区块链开发区块链
1.1区块链技术的发展随着2008年比特币（Bitcoin)的发明，一个被称为区块链（Blockchain)的新概念进入了人们的视野，这项新技术据信有可能彻底改变整个社会。区块链有望对每个行业产生颠覆的影响，包括但不限于IT、金融、政府、媒体、医疗、法律和艺术等。一个流派将区块链描述为一场革命，而另一个流派则认为，区块链将变得更具进化性，并且要花费很多年才能使区块链的任何实际收益变现。这种想法在某
《未来二十年，AI、区块链、云与大数据技术引领全球变革》久绊A 文献/论文人工智能区块链云计算大数据
摘要在未来二十年，全球社会与经济将深刻受到人工智能（AI）、区块链（Blockchain）、云计算（Cloud）和大数据（Data）四大核心技术的驱动。这些技术不仅从宏观上重塑产业结构，更在微观层面显著提升生活品质与效率。本文通过详尽的案例分析，结合国内外最新研究成果，深入剖析这四大技术如何在教育、智能家居、农业、金融等多个关键领域产生深远影响。关键字人工智能（AI）、区块链（Blockchain
python，Django实现区块链项目大白菜程序猿区块链区块链 python django
1.python搭建区块链数据结构importjsonimporthashlibfromtimeimporttimeclassBlockChain(object):def__init__(self):self.blockchain=[]self.current_transactions=[]self.new_block()def__str__(self):#javatostringreturnf'
2018-07-09 易付链—你绝对不能错过的消息 cherrylinn
EPC（易付链）是由美国全球电商巨头eBay及其旗下全球支付系统PayPal(贝宝支付)共同投资的区块链支付平台（Easytopayblockchaintechnology）。旨在打造一个基于区块链技术的全球支付系统。众所周知，上星期易付链路演已正式启动，下面更详细的介绍了易付链未来的规划和目标。具体情况如下：EPC易付链项目落地时间表第一，9月底前上线ETE交易所，发行ET币。并开通“交易费用分
THE WORLD BITCOIN CREATED 辣么大大大大
In2018,SatoshiNakamotopublishedapaperabouttheworld'sfirstblockchain.Hewantedtoprovidadencentralizeddigtalcurrency,whichiscalledBitcoin.Everytransferisinthedistributedledger,thankstolawsofmathematicsan
PSC：为区块链扩展性画上全新篇章 xzsean
本文引用翻译于:https://medium.com/@cherellesteereate68/psc-a-whole-new-chapter-for-blockchain-scalability-873e2b035733在数字世界的变革中，PolySmartChain（PSC）赫然出现，以其独特的技术优势和不断创新的精神，解决了区块链技术在扩展性方面的问题，颠覆了我们对传统区块链技术的认知。区块
关于区块链的略记东沙秋月
总的来说，我一向都是走马观花，不求甚解的人，但这终究只是一种不好的习惯和特点，这肯定不是我的归宿和希望！所以我决心改变下我自己：找到一个方向和目标，努力地走下去力求甚解，无论成败得失！想从来都很简单，为了解决方向与目标的问题，我盲目地选择了并不十分理解和熟悉的blockchainfield,原因无非：interestingandneedmorethinkingandactions.1.区块链来源：
排队论和区块链学术研究 lisoleg
Queueinganalysisoftransaction=confirmationtimeinbitcoinBlockchainQueueingTheory
区块链技术和Hyperledger Fabric介绍 dnice 区块链区块链
1区块链介绍1.1区块链技术形成1.1.1起源在比特币诞生之时，技术专家们开始研究比特币的底层技术，并抽象提取出来，形成区块链技术，或者称分布式账本技术。1.1.2定义简称BT（Blockchaintechnology），也称为分布式账本技术，是一种互联网数据库技术，其特点是去中心化、公开透明，让每个人均可参与数据库记录，同时数据不可篡改。1.1.3理解把数据库比喻为一个账本，一次记账的行为就是一
NFTScan | 01.01~01.07 NFT 市场热点汇总 nft区块链
欢迎来到由NFT基础设施NFTScan出品的NFT生态热点事件每周汇总。周期：2024.01.01~2024.01.07NFTHotNews01/空投|MintBlockchain将于2024年1月10号启动MintGenesisNFT空投活动1月1日，MintBlockchain宣布将于2024年1月10号启动MintGenesisNFT空投活动。MintGenesisNFT是由MintBloc
Hackathon | Mint Blockchain 启动全球 NIP 创意提案黑客松活动！ nft黑客马拉松区块链
MintBlockchain是由NFTScanLabs发起的聚焦在NFT生态的L2网络，致力于促进NFT资产协议标准的创新和NFT在现实商业应用场景中的大规模采用。为了引导更多创作者和开发者参与NFT资产协议创新，MintBlockchain联合了包括Optimism、NFTScan、HashKeyNFT、蚂蚁数科ZAN、Mask、Antalpha、BuidlerDAO、Alienswap、Ele
NFTScan | 12.04~12.10 NFT 市场热点汇总 nft区块链
欢迎来到由NFT基础设施NFTScan出品的NFT生态热点事件每周汇总。周期：2023.12.04~2023.12.10NFTHotNews01/NFTScan与MintCore联合推出适用于NFT的Layer2网络Mint12月5日，根据官方消息，NFT基础设施服务商NFTScan开发团队NFTScanLabs宣布推出以太坊L2网络：MintBlockchain。MintBlockchain早期
Mint Blockchain 2024 年发展路线图和开发计划 nft区块链
MintBlockchain是一个聚焦在NFT领域的L2网络，由NFTScanLabs和MintCore团队联合开发。今天这篇文章，我们主要为大家介绍Mint区块链在2024年的发展路线图以及开发计划。MintBlockchain2024Roadmap2024Q1启动MintPass活动2024Q2上线NIP开发者平台2024Q2上线MintTestnet2024Q3上线MintMainnet20
区块链互操作协议 mutourend 区块链区块链
1.引言AlexeiZamyatin等人2019年论文SoK:CommunicationAcrossDistributedLedgers。参考资料[1]2019年论文SoK:CommunicationAcrossDistributedLedgers[2]Alistofblockchain-relatedSoKpapers[3]2021年视频FC21:SoK:CommunicationAcrossD
华为云发起元宇宙 & Web3.0联盟，风口上的 AI 计算平台Deepbrain Chain再次登台亮相... 白话区块链-大白人工智能华为云 web3 区块链
这是白话区块链的第1867期原创作者|Bob出品｜白话区块链（ID：hellobtc）近来，亚太地区元宇宙与Web3.0主题相关的政策高频推出，各类活动高潮迭起，看点十足。继新加坡、香港之后，2月23日，在印尼巴厘岛的2023华为云亚太区合作伙伴领袖峰会期间，由华为云牵头启动了Metaverse&Web3.0联盟，同时展示了多个重量级的联盟伙伴，包括BlockChainSolutions、Deep
【Fellow 云集 | 经管主题/EI会议 | 快见刊】第三届大数据、区块链与经济管理国际学术会议 (ICBBEM 2024)，早投稿、早送审、早录用！艾思科蓝 AiScholar 学术会议大数据区块链信任链人工智能软件工程线性回归算法
第三届大数据、区块链与经济管理国际学术会议(ICBBEM2024)The3rdInternationalConferenceonBigdataBlockchainandEconomyManagement大会网站：https://ais.cn/u/YFbQru（更多会议详情）大会时间：2024年3月29-31号大会地点：中国-武汉截稿时间：以官网信息为准提交检索：EICompendex，Scopus
2021-03-19 潇洒二爷
区块链代币爱丽丝，在“币安”交易所一上市，30秒钟就上涨了60000%BlockchaingametokenALICEhad60000%upin30secondsinBinanceexchange有一种虚拟货币，名字叫“爱丽丝”（ALICE），在“币安”（Binance）虚拟货币交易所登记了，不出1分钟，便从0.1美元飙升到60美元，上涨60000%。事件经过：“我的邻居爱丽丝”（MyNeighb
一步步教你创建自己的数字货币（代币）进行ICO 半亩房顶
转自：https://learnblockchain.cn/2018/01/12/create_token/代币Token如果不那么追求精确的定义，代币就是数字货币，比特币、以太币就是一个代币。利用以太坊的智能合约可以轻松编写出属于自己的代币，代币可以代表任何可以交易的东西，如：积分、财产、证书等等。因此不管是出于商业，还是学习很多人想创建一个自己的代币，先贴一个图看看创建的代币是什么样子。ima
区块链是什么傅越驰Ameeya
区块链（blockchain）是分布式数据存储、点对点传输、共识机制、加密算法等计算机技术的新型应用模式。是一个共享的分布式账本，其中交易通过附加块永久记录。区块（block）在比特币网络中，数据会以文件的形式被永久记录，我们称这些文件为区块。一个区块是一些或所有最新比特币交易的记录集，且未被其他先前的区块记录。介绍：区块链是一种数据结构。一个项目或者应用（如比特币，EOS）使用区块链来记录一段时
truffle 创建测试合约并部署到测试网络不与天斗8866 web3 区块链 truffle
1、npm安装trufflenpminstall-gtruffle2、创建truffle项目mkdirimooc-on-blockchain-truffle&&cdimooc-on-blockchain-truffle3、初始化truffle目录，会生成如下几个目录contracts存放.sol合约文件migrations部署脚本目录test测试文件目录truffle-config.jstruff
AES加密模式总结 Dokin丶算法 AES AES加密模式 AES CBC AES ECB
目录1.ECB模式(ElectronicCodeBookMode)2.CBC模式(CipherBlockChainingMode)3.CFB模式(CipherFeedbackMode)4.OFB模式(OutputFeedbackMode)5.CTR模式(CounterMode)6.PCBC模式(PropagatingCipherBlockChainingMode)AES，即AdvancedEncr
区块链能否落地生根？ d719f6b05f08
目前，全球已有超过1500家企业进行区块链技术方面的研发和应用试验，其中既包括像IBM、微软这样的传统科技巨头，也包括JP摩根、美国银行等实力雄厚的金融巨鳄，还包括遍布全球的近千家区块链初创企业。基于区块链技术的比特币价格在2017年剧烈波动，从1000美元狂飙到最高值时的约20000美元，其价格剧烈波动以及可能引发的金融问题引发各国央行的关注。区块链技术（blockchaintechnology
Solidity介绍尽欢i #智能合约区块链开发语言智能合约
努力只能及格，拼命才能优秀前言：编写智能合约绕不过去的一个坑就是要学一种新的编程语言，这就是号称智能合约编程语言的Solidity本次学习的版本为0.8.0Solidity官方中文学习文档Solidity中文文档—Solidity中文文档—登链社区(learnblockchain.cn)Solidity学习教程Solidity教程-编程宝库(codebaoku.com)目录前言：一、Solidit
python区块链框架_GitHub - shawnsky/blockchain: 使用 Python 从零搭建一个自己的区块链... weixin_39998859 python区块链框架
blockchain本项目是naivecoin的python实现版本，包括区块链的数据结构、“挖矿”、节点同步的功能。环境Python>=3.4Flask==1.1.1介绍区块链是什么？核心就是一句话，区块链是一个分布式数据库，它维护着一个持续不断增长的、有序的记录列表。比如比特币是区块链技术的一个比较出名的应用。在数字货币的系统中，分布式数据库里保存的就是一条一条交易转账信息。在本次技术分享中，
vChain: Enabling Verifiable Boolean Range Queries over Blockchain Databases(sigmod‘2019) 咩咩姐区块链区块链
目录Abstract1Introduction2相关工作问题定义4预赛5基本解决方案5.1ADS生成和查询处理5.2多组蓄能器的结构5.3范围查询的扩展6批量验证6.1块内索引6.2块间索引6.3在线批量验证7可验证的订阅查询7.1可扩展处理的查询索引7.2惰性身份验证8安全分析8.1多集累加器分析8.2查询认证分析9绩效评估9.1设置成本9.2时间窗口查询性能9.3订阅查询性能10结论vChai
论文笔记-vChain: Enabling Verifiable Boolean Range Queries over Blockchain Databases qq_40431700 笔记区块链
核心方法：提出了一种基于累加器的可认证数据结构，可以动态聚合任意查询属性提出块内和块间索引，聚合块内和块间数据，可以做高效查询验证倒排前缀树结构，加速同时处理大量数据的订阅查询提出问题：1.range查询2.布尔查询3.没有可靠第三方、而且不能保证查询的完整性图中元素有：①全节点②矿工节点：是全节点，而且负责构建共识证明，比如计算nonce③轻节点：存nonce、区块的哈希，不存数据记录提出的Vc
区块链可验证查询论文阅读（一）vChain: Enabling Verifiable Boolean Range Queriesover Blockchain Databases lyhibo 研究生学习区块链可验证查询论文阅读区块链区块链
2019年7月发表在顶会SIGMOD上的论文《vChain:EnablingVerifiableBooleanRangeQueriesoverBlockchainDatabases》，来自香港浸会大学。1论文解决的问题如果想查询区块链中的数据，一种可行的做法是用户可以维护整个区块链数据库，并在本地查询数据。但是，通常区块链中所存储的数据量很大，下载完整的数据到本地需要很大的存储空间和网络带宽。另一
IPFS与区块链的关系 - BlockChain Storage 区块链存储 (2) 乐生活与爱IT 分布式区块链比特币 java 人工智能
经《IPFS原理与实践》主要作者董天一、戴嘉乐，以及华章出版社孙海亮老师的授权，在微信公众号“乐生活与爱IT”首发。上一篇是《什么是IPFS-BlockChainStorage区块链存储(1)》，本篇是书籍第1章的第2节，原标题为IPFS与区块链的关系第1章认识IPFS第2节1.2IPFS与区块链的关系现在提到IPFS就一定会提到区块链，那么区块链和IPFS之间到底有什么关系呢？在介绍二者关系之前
Blockchain for creative contents Vivien_like
SharingatHKOSCon2018byLikeCoinFoundationLikeCoinisanERC20tokenbasedontheEthereumblockchain.Usingthepowerofsmartcontract,weenableeasieruserattributionandcross-platformcollaborationoncreativecontents.In
最新论文笔记(+21)：Privacy-Preserving Byzantine-Robust Federated Learning via Blockchain Systems/ TIFS2022 cryptocxf 论文笔记联邦学习论文阅读区块链
Privacy-PreservingByzantine-RobustFederatedLearningviaBlockchainSystems可译为“利用区块链实现隐私保护的拜占庭鲁棒性联邦学习”这篇是今年八月份被TIFS2022（CCFA）收录的文章，写的利用全同态加密和区块链技术解决联邦学习中隐私问题和可信问题（虽然区块链仅仅只是存储的作用，也稍微提了一下）。精读完这篇文章，整体感觉还不错，毕
scala的option和some 矮蛋蛋编程 scala
原文地址： http://blog.sina.com.cn/s/blog_68af3f090100qkt8.html 对于学习 Scala 的 Java™ 开发人员来说，对象是一个比较自然、简单的入口点。在本系列前几期文章中，我介绍了 Scala 中一些面向对象的编程方法，这些方法实际上与 Java 编程的区别不是很大。我还向您展示了 Scala 如何重新应用传统的面向对象概念，找到其缺点
NullPointerException Cb123456 android BaseAdapter
java.lang.NullPointerException: Attempt to invoke virtual method 'int android.view.View.getImportantForAccessibility()' on a null object reference 出现以上异常.然后就在baidu上
PHP使用文件和目录天子之骄 php文件和目录读取和写入 php验证文件 php锁定文件
PHP使用文件和目录 1.使用include()包含文件 (1)：使用include()从一个被包含文档返回一个值 (2)：在控制结构中使用include() include_once()函数需要一个包含文件的路径，此外，第一次调用它的情况和include()一样，如果在脚本执行中再次对同一个文件调用，那么这个文件不会再次包含。在php.ini文件中设置
SQL SELECT DISTINCT 语句何必如此 sql
SELECT DISTINCT 语句用于返回唯一不同的值。 SQL SELECT DISTINCT 语句在表中，一个列可能会包含多个重复值，有时您也许希望仅仅列出不同（distinct）的值。 DISTINCT 关键词用于返回唯一不同的值。 SQL SELECT DISTINCT 语法 SELECT DISTINCT column_name,column_name F
java冒泡排序 3213213333332132 java 冒泡排序
package com.algorithm; /** * @Description 冒泡 * @author FuJianyong * 2015-1-22上午09:58:39 */ public class MaoPao { public static void main(String[] args) { int[] mao = {17,50,26,18,9,10
struts2.18 +json,struts2-json-plugin-2.1.8.1.jar配置及问题！ 7454103 DAO spring Ajax json qq
struts2.18 出来有段时间了！（貌似是稳定版）闲时研究下下！貌似 sruts2 搭配 json 做 ajax 很吃香！实践了下下！不当之处请绕过！呵呵网上一大堆 struts2+json 不过大多的json 插件都是 jsonplugin.34.jar strut
struts2 数据标签说明 darkranger jsp bean struts servlet Scheme
数据标签主要用于提供各种数据访问相关的功能，包括显示一个Action里的属性，以及生成国际化输出等功能数据标签主要包括： action ：该标签用于在JSP页面中直接调用一个Action，通过指定executeResult参数，还可将该Action的处理结果包含到本页面来。 bean ：该标签用于创建一个javabean实例。如果指定了id属性，则可以将创建的javabean实例放入Sta
链表.简单的链表节点构建 aijuans 编程技巧
/*编程环境WIN-TC*/ #include "stdio.h" #include "conio.h" #define NODE(name, key_word, help) \ Node name[1]={{NULL, NULL, NULL, key_word, help}} typedef struct node { &nbs
tomcat下jndi的三种配置方式 avords tomcat
jndi(Java Naming and Directory Interface，Java命名和目录接口)是一组在Java应用中访问命名和目录服务的API。命名服务将名称和对象联系起来，使得我们可以用名称访问对象。目录服务是一种命名服务，在这种服务里，对象不但有名称，还有属性。 tomcat配置
关于敏捷的一些想法 houxinyou 敏捷
从网上看到这样一句话：“敏捷开发的最重要目标就是：满足用户多变的需求，说白了就是最大程度的让客户满意。” 感觉表达的不太清楚。感觉容易被人误解的地方主要在“用户多变的需求”上。第一种多变，实际上就是没有从根本上了解了用户的需求。用户的需求实际是稳定的，只是比较多，也比较混乱，用户一般只能了解自己的那一小部分，所以没有用户能清楚的表达出整体需求。而由于各种条件的，用户表达自己那一部分时也有
富养还是穷养，决定孩子的一生 bijian1013 教育人生
是什么决定孩子未来物质能否丰盛？为什么说寒门很难出贵子，三代才能出贵族？真的是父母必须有钱，才能大概率保证孩子未来富有吗？-----作者：@李雪爱与自由事实并非由物质决定，而是由心灵决定。一朋友富有而且修养气质很好，兄弟姐妹也都如此。她的童年时代，物质上大家都很贫乏，但妈妈总是保持生活中的美感，时不时给孩子们带回一些美好小玩意，从来不对孩子传递生活艰辛、金钱来之不易、要懂得珍惜
oracle 日期时间格式转化征客丶 oracle
oracle 系统时间有 SYSDATE 与 SYSTIMESTAMP； SYSDATE：不支持毫秒，取的是系统时间； SYSTIMESTAMP：支持毫秒，日期，时间是给时区转换的，秒和毫秒是取的系统的。日期转字符窜：一、不取毫秒： TO_CHAR(SYSDATE, 'YYYY-MM-DD HH24:MI:SS') 简要说明， YYYY 年 MM 月
【Scala六】分析Spark源代码总结的Scala语法四 bit1129 scala
1. apply语法 FileShuffleBlockManager中定义的类ShuffleFileGroup，定义： private class ShuffleFileGroup(val shuffleId: Int, val fileId: Int, val files: Array[File]) { ... def apply(bucketId
Erlang中有意思的bug bookjovi erlang
代码中常有一些很搞笑的bug，如下面的一行代码被调用两次（Erlang beam） commit f667e4a47b07b07ed035073b94d699ff5fe0ba9b Author: Jovi Zhang <[email protected]> Date: Fri Dec 2 16:19:22 2011 +0100 erts:
移位打印10进制数转16进制-2008-08-18 ljy325 java 基础
/** * Description 移位打印10进制的16进制形式 * Creation Date 15-08-2008 9:00 * @author 卢俊宇 * @version 1.0 * */ public class PrintHex { // 备选字符 static final char di
读《研磨设计模式》-代码笔记-组合模式 bylijinnan java 设计模式
声明：本文只为方便我个人查阅和理解，详细的分析以及源代码请移步原作者的博客http://chjavach.iteye.com/ import java.util.ArrayList; import java.util.List; abstract class Component { public abstract void printStruct(Str
利用cmd命令将.class文件打包成jar chenyu19891124 cmd jar
cmd命令打jar是如下实现：在运行里输入cmd，利用cmd命令进入到本地的工作盘符。(如我的是D盘下的文件有此路径 D:\workspace\prpall\WEB-INF\classes) 现在是想把D:\workspace\prpall\WEB-INF\classes路径下所有的文件打包成prpall.jar。然后继续如下操作： cd D: 回车 cd workspace/prpal
[原创]JWFD v0.96 工作流系统二次开发包 for Eclipse 简要说明 comsci eclipse 设计模式算法工作 swing
JWFD v0.96 工作流系统二次开发包 for Eclipse 简要说明 &nb
SecureCRT右键粘贴的设置 daizj secureCRT 右键粘贴
一般都习惯鼠标右键自动粘贴的功能，对于SecureCRT6.7.5 ，这个功能也已经是默认配置了。老版本的SecureCRT其实也有这个功能，只是不是默认设置，很多人不知道罢了。菜单： Options->Global Options ...->Terminal 右边有个Mouse的选项块。 Copy on Select Paste on Right/Middle
Linux 软链接和硬链接 dongwei_6688 linux
1.Linux链接概念Linux链接分两种，一种被称为硬链接（Hard Link），另一种被称为符号链接（Symbolic Link）。默认情况下，ln命令产生硬链接。【硬连接】硬连接指通过索引节点来进行连接。在Linux的文件系统中，保存在磁盘分区中的文件不管是什么类型都给它分配一个编号，称为索引节点号(Inode Index)。在Linux中，多个文件名指向同一索引节点是存在的。一般这种连
DIV底部自适应 dcj3sjt126com JavaScript
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml&q
Centos6.5使用yum安装mysql——快速上手必备 dcj3sjt126com mysql
第1步、yum安装mysql [root@stonex ~]# yum -y install mysql-server 安装结果： Installed: mysql-server.x86_64 0:5.1.73-3.el6_5 &nb
如何调试JDK源码 frank1234 jdk
相信各位小伙伴们跟我一样，想通过JDK源码来学习Java，比如collections包，java.util.concurrent包。可惜的是sun提供的jdk并不能查看运行中的局部变量，需要重新编译一下rt.jar。下面是编译jdk的具体步骤： 1.把C:\java\jdk1.6.0_26\sr
Maximal Rectangle hcx2013 max
Given a 2D binary matrix filled with 0's and 1's, find the largest rectangle containing all ones and return its area. public class Solution { public int maximalRectangle(char[][] matrix)
Spring MVC测试框架详解——服务端测试 jinnianshilongnian spring mvc test
随着RESTful Web Service的流行，测试对外的Service是否满足期望也变的必要的。从Spring 3.2开始Spring了Spring Web测试框架，如果版本低于3.2，请使用spring-test-mvc项目（合并到spring3.2中了）。 Spring MVC测试框架提供了对服务器端和客户端（基于RestTemplate的客户端）提供了支持。 &nbs
Linux64位操作系统（CentOS6.6）上如何编译hadoop2.4.0 liyong0802 hadoop
一、准备编译软件 1.在官网下载jdk1.7、maven3.2.1、ant1.9.4，解压设置好环境变量就可以用。环境变量设置如下：（1）执行vim /etc/profile （2）在文件尾部加入: export JAVA_HOME=/home/spark/jdk1.7 export MAVEN_HOME=/ho
StatusBar 字体白色 pangyulei status
[[UIApplication sharedApplication] setStatusBarStyle:UIStatusBarStyleLightContent]; /*you'll also need to set UIViewControllerBasedStatusBarAppearance to NO in the plist file if you use this method
如何分析Java虚拟机死锁 sesame java thread oracle 虚拟机 jdbc
英文资料： Thread Dump and Concurrency Locks Thread dumps are very useful for diagnosing synchronization related problems such as deadlocks on object monitors. Ctrl-\ on Solaris/Linux or Ctrl-B
位运算简介及实用技巧（一）：基础篇 tw_wangzhengquan 位运算
http://www.matrix67.com/blog/archives/263 去年年底写的关于位运算的日志是这个Blog里少数大受欢迎的文章之一，很多人都希望我能不断完善那篇文章。后来我看到了不少其它的资料，学习到了更多关于位运算的知识，有了重新整理位运算技巧的想法。从今天起我就开始写这一系列位运算讲解文章，与其说是原来那篇文章的follow-up，不如说是一个r
jsearch的索引文件结构 yangshangchuan 搜索引擎 jsearch 全文检索信息检索 word分词
jsearch是一个高性能的全文检索工具包，基于倒排索引，基于java8，类似于lucene，但更轻量级。 jsearch的索引文件结构定义如下： 1、一个词的索引由=分割的三部分组成：第一部分是词第二部分是这个词在多少