Fabric1.4单机单节点部署及测试

最新推荐文章于 2022-08-28 19:13:27 发布
最新推荐文章于 2022-08-28 19:13:27 发布
阅读量634 收藏 1
点赞数
文章标签： 运维 大数据 git
原文链接：https://my.oschina.net/u/193508/blog/3063076
版权

1.基础环境搭建

  • Docker Client 客户端
  • Docker Daemon 守护进程
  • Docker Image 镜像
  • Docker Container 容器

这块的安装相信大家通过资料都可以完成，重点是下面

2.Fabric环境搭建

2.1 创建singlepeer目录

# cd $GOPATH/github.com/hyperledger/fabric
# mkdir singlepeer
# cd singlepeer

2.2 下载源码文件

下载链接：https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric/linux-amd64-1.4.1/

把下载的hyperledger-fabric-linux-amd64-1.4.1.tar.gz二进制文件包解压，把其中的bin目录拷贝到singlepeer目录下 ，记得

chmod -R 755 ./bin

2.3 准备生成证书和区块配置文件

配置crypto-config.yaml和configtx.yaml文件，拷贝到singlepeer目录下

  • crypto-config.yaml
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

# ---------------------------------------------------------------------------
# "OrdererOrgs" - Definition of organizations managing orderer nodes
# ---------------------------------------------------------------------------
OrdererOrgs:
  # ---------------------------------------------------------------------------
  # Orderer
  # ---------------------------------------------------------------------------
  - Name: Orderer
    Domain: example.com
    # ---------------------------------------------------------------------------
    # "Specs" - See PeerOrgs below for complete description
    # ---------------------------------------------------------------------------
    Specs:
      - Hostname: orderer
# ---------------------------------------------------------------------------
# "PeerOrgs" - Definition of organizations managing peer nodes
# ---------------------------------------------------------------------------
PeerOrgs:
  # ---------------------------------------------------------------------------
  # Org1
  # ---------------------------------------------------------------------------
  - Name: Org1
    Domain: org1.example.com
    EnableNodeOUs: true
    # ---------------------------------------------------------------------------
    # "Specs"
    # ---------------------------------------------------------------------------
    # Uncomment this section to enable the explicit definition of hosts in your
    # configuration.  Most users will want to use Template, below
    #
    # Specs is an array of Spec entries.  Each Spec entry consists of two fields:
    #   - Hostname:   (Required) The desired hostname, sans the domain.
    #   - CommonName: (Optional) Specifies the template or explicit override for
    #                 the CN.  By default, this is the template:
    #
    #                              "{{.Hostname}}.{{.Domain}}"
    #
    #                 which obtains its values from the Spec.Hostname and
    #                 Org.Domain, respectively.
    # ---------------------------------------------------------------------------
    # Specs:
    #   - Hostname: foo # implicitly "foo.org1.example.com"
    #     CommonName: foo27.org5.example.com # overrides Hostname-based FQDN set above
    #   - Hostname: bar
    #   - Hostname: baz
    # ---------------------------------------------------------------------------
    # "Template"
    # ---------------------------------------------------------------------------
    # Allows for the definition of 1 or more hosts that are created sequentially
    # from a template. By default, this looks like "peer%d" from 0 to Count-1.
    # You may override the number of nodes (Count), the starting index (Start)
    # or the template used to construct the name (Hostname).
    #
    # Note: Template and Specs are not mutually exclusive.  You may define both
    # sections and the aggregate nodes will be created for you.  Take care with
    # name collisions
    # ---------------------------------------------------------------------------
    Template:
      Count: 1
      # Start: 5
      # Hostname: {{.Prefix}}{{.Index}} # default
    # ---------------------------------------------------------------------------
    # "Users"
    # ---------------------------------------------------------------------------
    # Count: The number of user accounts _in addition_ to Admin
    # ---------------------------------------------------------------------------
    Users:
      Count: 1
  • configtx.yaml
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

---
################################################################################
#
#   Section: Organizations
#
#   - This section defines the different organizational identities which will
#   be referenced later in the configuration.
#
################################################################################
Organizations:

    # SampleOrg defines an MSP using the sampleconfig.  It should never be used
    # in production but may be used as a template for other definitions
    - &OrdererOrg
        # DefaultOrg defines the organization which is used in the sampleconfig
        # of the fabric.git development environment
        Name: OrdererOrg

        # ID to load the MSP definition as
        ID: OrdererMSP

        # MSPDir is the filesystem path which contains the MSP configuration
        MSPDir: crypto-config/ordererOrganizations/example.com/msp

        # Policies defines the set of policies at this level of the config tree
        # For organization policies, their canonical path is usually
        #   /Channel/<Application|Orderer>/<OrgName>/<PolicyName>
        Policies:
            Readers:
                Type: Signature
                Rule: "OR('OrdererMSP.member')"
            Writers:
                Type: Signature
                Rule: "OR('OrdererMSP.member')"
            Admins:
                Type: Signature
                Rule: "OR('OrdererMSP.admin')"

    - &Org1
        # DefaultOrg defines the organization which is used in the sampleconfig
        # of the fabric.git development environment
        Name: Org1MSP

        # ID to load the MSP definition as
        ID: Org1MSP

        MSPDir: crypto-config/peerOrganizations/org1.example.com/msp

        # Policies defines the set of policies at this level of the config tree
        # For organization policies, their canonical path is usually
        #   /Channel/<Application|Orderer>/<OrgName>/<PolicyName>
        Policies:
            Readers:
                Type: Signature
                Rule: "OR('Org1MSP.admin', 'Org1MSP.peer', 'Org1MSP.client')"
            Writers:
                Type: Signature
                Rule: "OR('Org1MSP.admin', 'Org1MSP.client')"
            Admins:
                Type: Signature
                Rule: "OR('Org1MSP.admin')"

        AnchorPeers:
            # AnchorPeers defines the location of peers which can be used
            # for cross org gossip communication.  Note, this value is only
            # encoded in the genesis block in the Application section context
            - Host: peer0.org1.example.com
              Port: 7051

################################################################################
#
#   SECTION: Capabilities
#
#   - This section defines the capabilities of fabric network. This is a new
#   concept as of v1.1.0 and should not be utilized in mixed networks with
#   v1.0.x peers and orderers.  Capabilities define features which must be
#   present in a fabric binary for that binary to safely participate in the
#   fabric network.  For instance, if a new MSP type is added, newer binaries
#   might recognize and validate the signatures from this type, while older
#   binaries without this support would be unable to validate those
#   transactions.  This could lead to different versions of the fabric binaries
#   having different world states.  Instead, defining a capability for a channel
#   informs those binaries without this capability that they must cease
#   processing transactions until they have been upgraded.  For v1.0.x if any
#   capabilities are defined (including a map with all capabilities turned off)
#   then the v1.0.x peer will deliberately crash.
#
################################################################################
Capabilities:
    # Channel capabilities apply to both the orderers and the peers and must be
    # supported by both.  Set the value of the capability to true to require it.
    Global: &ChannelCapabilities
        # V1.1 for Global is a catchall flag for behavior which has been
        # determined to be desired for all orderers and peers running v1.0.x,
        # but the modification of which would cause incompatibilities.  Users
        # should leave this flag set to true.
        V1_1: true

    # Orderer capabilities apply only to the orderers, and may be safely
    # manipulated without concern for upgrading peers.  Set the value of the
    # capability to true to require it.
    Orderer: &OrdererCapabilities
        # V1.1 for Order is a catchall flag for behavior which has been
        # determined to be desired for all orderers running v1.0.x, but the
        # modification of which  would cause incompatibilities.  Users should
        # leave this flag set to true.
        V1_1: true

    # Application capabilities apply only to the peer network, and may be safely
    # manipulated without concern for upgrading orderers.  Set the value of the
    # capability to true to require it.
    Application: &ApplicationCapabilities
        # V1.1 for Application is a catchall flag for behavior which has been
        # determined to be desired for all peers running v1.0.x, but the
        # modification of which would cause incompatibilities.  Users should
        # leave this flag set to true.
        V1_2: true

################################################################################
#
#   SECTION: Application
#
#   - This section defines the values to encode into a config transaction or
#   genesis block for application related parameters
#
################################################################################
Application: &ApplicationDefaults

    # Organizations is the list of orgs which are defined as participants on
    # the application side of the network
    Organizations:

    # Policies defines the set of policies at this level of the config tree
    # For Application policies, their canonical path is
    #   /Channel/Application/<PolicyName>
    Policies:
        Readers:
            Type: ImplicitMeta
            Rule: "ANY Readers"
        Writers:
            Type: ImplicitMeta
            Rule: "ANY Writers"
        Admins:
            Type: ImplicitMeta
            Rule: "MAJORITY Admins"

    # Capabilities describes the application level capabilities, see the
    # dedicated Capabilities section elsewhere in this file for a full
    # description
    Capabilities:
        <<: *ApplicationCapabilities

################################################################################
#
#   SECTION: Orderer
#
#   - This section defines the values to encode into a config transaction or
#   genesis block for orderer related parameters
#
################################################################################
Orderer: &OrdererDefaults

    # Orderer Type: The orderer implementation to start
    # Available types are "solo" and "kafka"
    OrdererType: solo

    Addresses:
        - orderer.example.com:7050

    # Batch Timeout: The amount of time to wait before creating a batch
    BatchTimeout: 2s

    # Batch Size: Controls the number of messages batched into a block
    BatchSize:

        # Max Message Count: The maximum number of messages to permit in a batch
        MaxMessageCount: 10

        # Absolute Max Bytes: The absolute maximum number of bytes allowed for
        # the serialized messages in a batch.
        AbsoluteMaxBytes: 98 MB

        # Preferred Max Bytes: The preferred maximum number of bytes allowed for
        # the serialized messages in a batch. A message larger than the preferred
        # max bytes will result in a batch larger than preferred max bytes.
        PreferredMaxBytes: 512 KB

    Kafka:
        # Brokers: A list of Kafka brokers to which the orderer connects. Edit
        # this list to identify the brokers of the ordering service.
        # NOTE: Use IP:port notation.
        Brokers:
            - 127.0.0.1:9092

    # Organizations is the list of orgs which are defined as participants on
    # the orderer side of the network
    Organizations:

    # Policies defines the set of policies at this level of the config tree
    # For Orderer policies, their canonical path is
    #   /Channel/Orderer/<PolicyName>
    Policies:
        Readers:
            Type: ImplicitMeta
            Rule: "ANY Readers"
        Writers:
            Type: ImplicitMeta
            Rule: "ANY Writers"
        Admins:
            Type: ImplicitMeta
            Rule: "MAJORITY Admins"
        # BlockValidation specifies what signatures must be included in the block
        # from the orderer for the peer to validate it.
        BlockValidation:
            Type: ImplicitMeta
            Rule: "ANY Writers"

    # Capabilities describes the orderer level capabilities, see the
    # dedicated Capabilities section elsewhere in this file for a full
    # description
    Capabilities:
        <<: *OrdererCapabilities

################################################################################
#
#   CHANNEL
#
#   This section defines the values to encode into a config transaction or
#   genesis block for channel related parameters.
#
################################################################################
Channel: &ChannelDefaults
    # Policies defines the set of policies at this level of the config tree
    # For Channel policies, their canonical path is
    #   /Channel/<PolicyName>
    Policies:
        # Who may invoke the 'Deliver' API
        Readers:
            Type: ImplicitMeta
            Rule: "ANY Readers"
        # Who may invoke the 'Broadcast' API
        Writers:
            Type: ImplicitMeta
            Rule: "ANY Writers"
        # By default, who may modify elements at this config level
        Admins:
            Type: ImplicitMeta
            Rule: "MAJORITY Admins"


    # Capabilities describes the channel level capabilities, see the
    # dedicated Capabilities section elsewhere in this file for a full
    # description
    Capabilities:
        <<: *ChannelCapabilities

################################################################################
#
#   Profile
#
#   - Different configuration profiles may be encoded here to be specified
#   as parameters to the configtxgen tool
#
################################################################################
Profiles:

    OneOrgsOrdererGenesis:
        <<: *ChannelDefaults
        Orderer:
            <<: *OrdererDefaults
            Organizations:
                - *OrdererOrg
        Consortiums:
            SampleConsortium:
                Organizations:
                    - *Org1
    OneOrgsChannel:
        Consortium: SampleConsortium
        Application:
            <<: *ApplicationDefaults
            Organizations:
                - *Org1

2.4 生成公私钥和证书

# ./bin/cryptogen generate --config=./crypto-config.yaml

2.5 生成创世区块

创世区块是为了Orderer排序启动时用到，Peer节点在启动后需要创建Channel的配置文件在这里也一并生成，

# ./bin/configtxgen -profile OneOrgsChannel -outputCreateChannelTx ./channel-artifacts/mychannel.tx -channelID mychannel

2.6 部署Orderer节点

2.6.1配置Orderer节点启动文件docker-orderer.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:
      - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=aberic_default
      # - ORDERER_GENERAL_LOGLEVEL=error
      - ORDERER_GENERAL_LOGLEVEL=debug
      - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
      - ORDERER_GENERAL_LISTENPORT=7050
      #- ORDERER_GENERAL_GENESISPROFILE=AntiMothOrdererGenesis
      - ORDERER_GENERAL_GENESISMETHOD=file
      - ORDERER_GENERAL_GENESISFILE=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/channel-artifacts/genesis.block
      - ORDERER_GENERAL_LOCALMSPID=OrdererMSP
      - ORDERER_GENERAL_LOCALMSPDIR=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/msp
      #- ORDERER_GENERAL_LEDGERTYPE=ram
      #- ORDERER_GENERAL_LEDGERTYPE=file
      # enabled TLS
      - ORDERER_GENERAL_TLS_ENABLED=false
      - ORDERER_GENERAL_TLS_PRIVATEKEY=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/server.key
      - ORDERER_GENERAL_TLS_CERTIFICATE=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/server.crt
      - ORDERER_GENERAL_TLS_ROOTCAS=[/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/ca.crt]
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/singlepeer/
    command: orderer
    volumes:
    - ./channel-artifacts/genesis.block:/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/channel-artifacts/genesis.block
    - ./crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/msp:/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/msp
    - ./crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/:/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls
    networks:
      default:
        aliases:
          - aberic
    ports:
      - 7050:7050

ORDERER_GENERAL_GENESISFILE：指向生成的创世纪区块，我的目录是/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/channel-artifacts/genesis.block

ORDERER_GENERAL_LOCALMSPID：和configtx.yaml中Organizations:节点下的ID的值一致。

ORDERER_GENERAL_LOCALMSPDIR：指向msp，我的目录是/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/msp

ORDERER_GENERAL_TLS_PRIVATEKEY：指向生成证书文件，我的目录是/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/server.key

ORDERER_GENERAL_TLS_CERTIFICATE：指向生成证书文件，我的目录是/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/server.crt

ORDERER_GENERAL_TLS_ROOTCAS：指向生成证书文件，我的目录是/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/ca.crt

同理其它配置信息：working_dir，volumes：找到自己的目录指向

 

2.7部署peer0.org1节点

2.7.1配置Peer节点启动文件docker-peer.yaml

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

version: '2'

services:

  couchdb:
    container_name: couchdb
    image: hyperledger/fabric-couchdb
    # Comment/Uncomment the port mapping if you want to hide/expose the CouchDB service,
    # for example map it to utilize Fauxton User Interface in dev environments.
    ports:
      - "5984:5984"

  ca:
    container_name: ca
    image: hyperledger/fabric-ca
    environment:
      - FABRIC_CA_HOME=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/peerOrganizations/org1.example.com/ca
      - FABRIC_CA_SERVER_CA_NAME=ca
      - FABRIC_CA_SERVER_TLS_ENABLED=false
      - FABRIC_CA_SERVER_TLS_CERTFILE=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/peerOrganizations/org1.example.com/ca/ca.org1.example.com-cert.pem
      - FABRIC_CA_SERVER_TLS_KEYFILE=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/peerOrganizations/org1.example.com/ca/f5617615ea50e08358addecfa264af0a1e01b8825da987a97b58707e7d7571a8_sk
    ports:
      - "7054:7054"
    command: sh -c 'fabric-ca-server start --ca.certfile /opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/peerOrganizations/org1.example.com/ca/ca.org1.example.com-cert.pem --ca.keyfile /opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/peerOrganizations/org1.example.com/ca/f5617615ea50e08358addecfa264af0a1e01b8825da987a97b58707e7d7571a8_sk -b admin:adminpw -d'
    volumes:
      - ./crypto-config/peerOrganizations/org1.example.com/ca/:/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/peerOrganizations/org1.example.com/ca

  peer0.org1.example.com:
    container_name: peer0.org1.example.com
    image: hyperledger/fabric-peer
    environment:
      - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
      - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb:5984

      - CORE_PEER_ID=peer0.org1.example.com
      - CORE_PEER_NETWORKID=aberic
      - CORE_PEER_ADDRESS=peer0.org1.example.com:7051
      - CORE_PEER_CHAINCODELISTENADDRESS=peer0.org1.example.com:7052
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.example.com:7051
      - CORE_PEER_LOCALMSPID=Org1MSP

      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      # the following setting starts chaincode containers on the same
      # bridge network as the peers
      # https://docs.docker.com/compose/networking/
      - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=aberic
      # - CORE_LOGGING_LEVEL=ERROR
      - CORE_LOGGING_LEVEL=DEBUG
      - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=aberic_default
      - CORE_PEER_GOSSIP_SKIPHANDSHAKE=true
      - CORE_PEER_GOSSIP_USELEADERELECTION=true
      - CORE_PEER_GOSSIP_ORGLEADER=false
      - CORE_PEER_PROFILE_ENABLED=false
      - CORE_PEER_TLS_ENABLED=false
      - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
      - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
      - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
    volumes:
        - /var/run/:/host/var/run/
        - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/msp:/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/msp
        - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls:/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/singlepeer
    command: peer node start
    ports:
      - 7051:7051
      - 7052:7052
      - 7053:7053
    depends_on:
      - couchdb
    networks:
      default:
        aliases:
          - aberic

  cli:
    container_name: cli
    image: hyperledger/fabric-tools
    tty: true
    environment:
      - GOPATH=/opt/gopath
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      # - CORE_LOGGING_LEVEL=ERROR
      - CORE_LOGGING_LEVEL=DEBUG
      - CORE_PEER_ID=cli
      - CORE_PEER_ADDRESS=peer0.org1.example.com:7051
      - CORE_PEER_LOCALMSPID=Org1MSP
      - CORE_PEER_TLS_ENABLED=false
      - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
      - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
      - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
      - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/singlepeer
    volumes:
        - /var/run/:/host/var/run/
        - ./chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/chaincode/go
        - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config
        - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/channel-artifacts
    depends_on:
      - peer0.org1.example.com

以上的配置和自己目录的指向保持一致，请大家自行配置。

Peer启动文件启动的是peer0.org1.example.com节点，所以对应的证书在peer0.org1.example.com下可以找到。

dockerr-peer. yaml中有两处的加密：f5617615ea50e08358addecfa264af0a1e01b8825da987a97b58707e7d7571a8_sk请替换成自己的加密串

我这里是为了执行源码的example02例子，所以在cli下volumes:里配置要执行的智能合约程序

2.8 准备docker配置文件

2.8.1配置客户端启动文件docker-compose-cli.yaml

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=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/channel-artifacts/genesis.block
      - ORDERER_GENERAL_LOCALMSPID=OrdererMSP
      - ORDERER_GENERAL_LOCALMSPDIR=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/msp
      # enabled TLS
      - ORDERER_GENERAL_TLS_ENABLED=false
      - ORDERER_GENERAL_TLS_PRIVATEKEY=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/server.key
      - ORDERER_GENERAL_TLS_CERTIFICATE=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/server.crt
      - ORDERER_GENERAL_TLS_ROOTCAS=[/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/ca.crt]
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/singlepeer
    command: orderer
    volumes:
      - ./channel-artifacts/genesis.block:/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/channel-artifacts/genesis.block
      - ./crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/msp:/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/msp
      - ./crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/:/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls
    ports:
      - 7050:7050

  peer0.org1.example.com:
    container_name: peer0.org1.example.com
    image: hyperledger/fabric-peer
    environment:
      - CORE_PEER_ID=peer0.org1.example.com
      - CORE_PEER_ADDRESS=peer0.org1.example.com:7051
      - CORE_PEER_CHAINCODEADDRESS=peer0.org1.example.com:7052
      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.example.com:7051
      - CORE_PEER_LOCALMSPID=Org1MSP
  
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      # the following setting starts chaincode containers on the same
      # bridge network as the peers
      # https://docs.docker.com/compose/networking/
      - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=singlepeer_default
      #- CORE_LOGGING_LEVEL=ERROR
      - CORE_LOGGING_LEVEL=DEBUG
      - CORE_PEER_TLS_ENABLED=false
      - CORE_PEER_GOSSIP_USELEADERELECTION=true
      - CORE_PEER_GOSSIP_ORGLEADER=false
      - CORE_PEER_PROFILE_ENABLED=true
      - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/server.crt
      - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/server.key
      - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/ca.crt
    volumes:
        - /var/run/:/host/var/run/
        - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/msp:/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/msp
        - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls:/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: peer node start
    ports:
      - 7051:7051
      - 7052:7052
      - 7053:7053

  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=false
      - 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/Admin@org1.example.com/msp
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    volumes:
        - /var/run/:/host/var/run/
        - ./chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/singlepeer/chaincode/go
        - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
        - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
    depends_on:
      - orderer.example.com
      - peer0.org1.example.com

2.9 启动Fabric网络

2.9.1 启动orderer和peer

#docker -compose -f docker-orderer.yaml up -d
#docker -compose -f docker-peer.yaml up -d

2.9.2 启动cli容器

# docker exec -it cli bash

2.9.3 创建Channel

# peer channel create -o orderer.example.com:7050 -c mychannel -f ./channel-artifacts/mychannel.tx

2.9.4 Peer加入Channel

# peer channel join -b mychannel.block

2.10 安装与运行智能合约

2.10.1 安装智能合约

# peer chaincode install -n mycc -p github.com/hyperledger/fabric/singlepeer/chaincode/go/example02/cmd/ -v 1.0

2.10.2 实例化智能合约

# peer chaincode instantiate -o orderer.example.com:7050 -C mychannel -n mycc -v 1.0 -c '{"Args":["init","a","100","b","200"]}' -P "AND ('Org1MSP.peer')"

2.10.3 Peer上查询a，显示100

# peer chaincode query -C mychannel -n mycc -c '{"Args":["query","a"]}'

2.10.4 Peer上进行a向b转10交易

# peer chaincode invoke -C mychannel -n mycc -c '{"Args":["invoke","a","b","10"]}'

2.10.5 Peer上查询a，显示210

# peer chaincode query -C mychannel -n mycc -c '{"Args":["query","b"]}'

转载于:https://my.oschina.net/u/193508/blog/3063076

chenggen2446
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
fabric单机配置-2019-01-31
boss2967的博客
01-31 529
crypto-config.yaml OrdererOrgs: - Name: Orderer Domain: example.com Specs: - Hostname: orderer PeerOrgs: - Name: Org1 Domain: org1.example.com EnableNodeOUs: true Temp...
Hyperledger Fabric入门实战（四）——手动组建Fabric网络
聂泳的博客
04-08 990
本章主要讲解了手动搭建Fabric的过程，主要包括通过cryptogen生成证书文件，通过configtxgen生成创始块和通道以及docker-compose的配置。
Fabric部署基础篇 - 单机部署.docx
05-17
学习fabric近1年了，在大咖杨毅和灵龙的帮助下，总算学有所成，最近有很多朋友问我，有没有总结性的文档，其实有一些，但没整理，都是一些md笔记。这几天干脆整理了几个文档，放到这里，希望对新手有帮助。 先发个基础篇，看看效果，如果确实对新手有用，后面还有 Fabric部署进阶篇 - 多机部署 Fabric部署进阶篇 - 链码开发
Fabric1.0.0单机环境部署
yuch_hong的博客
07-15 389
从2018年3月份左右，开始接触fabric，搭建了单机或集群环境，也写了一些文档。最近整理电脑时发现，在这里分享出来。。。。 安装Go 1.8以上 cd /www/download/ wget https://storage.googleapis.com/golang/go1.9.linux-amd64.tar.gz 解压缩,解压后文件夹是go sudo tar -xzf go1.9.linux-amd64.tar.gz sudo vi /etc/profile exp..
Fabric1.4 单机solo部署
weixin_42663984的博客
09-01 443
创建项目目录 #进入fabirc目录底下 cd /root/gopath/src/github.com/hyperledger/fabric #创建项目目录 mkdir test/test01 #进入该项目目录下 cd test/test01 生成认证文件 证书配置文件生成 fabric网络是基于yaml文件起的，先对证书配置文件进行配置 vi crypto-config.yaml OrdererOrgs: - Name: Orderer Domain: acme.com Specs
杨毅-Fabric单机单节点部署
boss2967的博客
04-26 451
1. configtx.yaml # Copyright IBM Corp. All Rights Reserved. # # SPDX-License-Identifier: Apache-2.0 # --- ################################################################################ # # Profil...
HyperLedger Fabric开发实战 – 部署单机多节点网络
01-08
第3章 部署单机多节点网络 在进行基础环境搭建和fabric环境部署完后，可以得到一个完全干净的空服务器状态。 3.1 生成证书文件 如果运行过e2e_cli案例，则执行如下命令即可做到环境清理(…/fabric/examples/e2e_cli/...
hyperledger fabric单机单节点快速部署实例
01-20
hyperledger fabric单机单节点网络,solo共识机制，包含Java chaincode，部署之后直接run.sh脚本
Centos7 HyperLedger Fabric 1.4 生产环境部署
01-20
Centos7 HyperLedger Fabric 1.4 生产环境部署  Kafka生产环境部署案例采用三个排序（orderer）服务、四个kafka、三个zookeeper和四个节点（peer）组成，共准备八台服务器，每台服务器对应的服务如下所示： kafka...
手动搭建fabric单机多节点网络.pdf
07-20
基于hyperledger fabric2.0手动搭建单机多节点网络，所有步骤均基于fabric-sample的test-network脚本
fabric环境1.4手动部署.docx
04-24
区块链环境的搭建 第一：了解fabric的搭建流程； 第二：搭建有手动搭建和自动搭建，这里介绍的是手动搭建； 第三：作为fabric环境的入门基础。
Centos 7.6单机部署Fabric1.4.0
刘李404not_found的博客
11-04 698
文章目录一、前期准备1.1 curl版本1.2 Docker安装1.3 Docker Compose安装1.4 Go安装1.5 Node.js安装1.6 python环境1.7 Git版本二、Fabric安装2.1 下载fabric-samples2.2 安装Docker镜像三、Fabric离线安装参考资料 一、前期准备 安装环境 [root@localhost opt]# cat /etc/re...
Hyperledger Fabric 2.x 单机部署多节点网络
qq_45469783的博客
08-03 5920
本博客主要记录搭建一个3个排序节点、4个组织的每个组织各2个节点的fabric区块链网络 单机部署多节点网络1、相关环境的安装与配置2、生成相关的证书文件3、生成相关的通道配置文件4、生成docker-compose.yaml的启动文件 1、相关环境的安装与配置 go、docker、docker-compose，fabric的相关docker镜像、官方的fabric-samples文件、相关fabric二进制文件，具体配置之后补充 2、生成相关的证书文件 1）将下面的内容写入到crypto-config.y
fabric1.4 单机部署 简书
小树苗
08-30 508
开发先决条件： Git客户端 Go - 版本1.12.x Docker - 17.06.2-ce或更高版本 Docker Compose - 1.14.0或更高版本 #（macOS） 必须安装Xcode 安装git yum -y install gcc-c++ wget yum -y install git 安装docker yum install -y yum-utils ...
在Fabric1.1下单机部署多节点网络
weixin_42559083的博客
03-05 721
1、在fabric目录下新建aberic目录（目录的名字一定是这个，因为下面的配置文件会有目录结构） 2、将之前下载的为二进制文件bin复制到aberic目录 ，下面是二进制文件下载方式 curl -sSL https://raw.githubusercontent.com/hyperledger/fabric/master/scripts/bootstrap.sh | bash -s...
Fabric 1.4 实战 — 2.3 测试网络环境
weixin_43468183的博客
10-12 711
文章目录一、创建通道并将组织加入通道1、启动网络2、进入 CLI 容器3、创建通道请求4、peer0.org1.example.com 节点加入通道5、peer1.org1.example.com 节点加入通道6、更新 org1 锚节点7、peer0.org2.example.com 节点加入通道8、peer1.org2.example.com 节点加入通道9、更新 org2 锚节点二、编写并部署链码1、编写链码2、安装链码3、实例化链码4、在 Org2 中的peer0节点上安装链码三、查询调用链码1、查询
区块链架构-fabric单机测试版安装运行（centos7版本）
区块链领域填坑的java程序猿
08-28 1789
区块链之fabric的安装部署（单机版）
fabric1.0部署
l18710006370的博客
07-28 3048
一：第一种v1.0的启动模式： 这种最好不要用于开发，用于测试chaincode在fabric环境下的部署和调用 虚拟机中安装1.0步骤： 1.进去 https://github.com/yeasy/docker-compose-files/tree/master/hyperledger/1.0 2.在Clone or download中复制地址
Hyperledger Fabric1.4环境搭建及示例测试
weixin_44732379的博客
09-18 3067
环境 采用Centos7 64位操作系统。首先需要安装3个基本环境Docker、Docker-Compose、Go语言环境安装，最后Fabric安装。 一.安装Dokcer 1.安装前准备 检查内核版本，要在3以上 # uname -r 2.如果以前安装过Docker # yum remove docker \docker-client \docker-client-latest \docker-common \docker-latest \docker-latest-logrotate \docker
Fabric单机单节点部署
最新发布
08-20
Fabric的单机单节点部署相对简单，以下是一些基本步骤： 1. 安装Docker和Docker Compose：在你的机器上安装Docker和Docker Compose，这是运行Fabric网络所必需的。 2. 下载Fabric示例文件：从Hyperledger Fabric...

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值