Hyperledger Fabric动态配置Raft节点

ShiShuo 2019-12-31

Hyperledger Fabric动态配置Raft节点

最近看官方文档发现新的共识算法etcdRaft允许动态添加或删除排序节点，所以也花了一天时间操作了以下，写篇文章把整个过程记录一下。
初始网络本文设置了4个Orderer节点，1个Peer节点(用于更新配置文件以及测试用),然后动态添加第五个Orderer节点。
本文分成两个部分:

  1. 第一部分是手动通过Fabric-CA生成每一个节点的证书文件
  2. 第二部分是更新Fabric网络配置添加新的Orderer节点。

本文基于Fabric v2.0.0-beta版本。版本号只要高于1.4.1就行

1 搭建定制化的Fabric网络

前提条件是成功跑起来Fabric的示例网络，可以看这里->Hyperledger Fabric环境搭建

首先在$GOPATH下(本文路径地址为$GOPATH/src/github.com/hyperledger/fab)建立如下几个文件夹用于之后的操作:

.  # 这里是根目录fab
├── ca    # 用于生成CA证书的ca配置文件的文件夹
│?? ├── org1
│?? │?? └── fabric-ca-server-config.yaml
│?? └── server
│??     └── fabric-ca-server-config.yaml
├── channel-artifacts    #用于保存创世区块以及通道配置文件
├── configtx.yaml      #配置文件：用于生成创世区块以及通道配置文件
├── crypto-config     #存储生成的证书文件
├── docker      # Fabric网络节点通过Docker启动，用于启动节点的Docker文件
│?? ├── base.yaml
│?? ├── docker-compose-addOrderer5.yaml
│?? ├── docker-compose-ca.yaml
│?? ├── docker-compose-orderers.yaml
│?? └── docker-compose-peer.yaml
└── store    #存储区块等信息

以下所有操作默认都在根目录文件夹内！

1.1CA配置文件

直接在这里贴出来:org1/fabric-ca-server-config.yaml:

展开查看org1/fabric-ca-server-config.yaml

version: 1.2.0

# Server's listening port (default: 7054)
port: 7054

# Enables debug logging (default: false)
debug: false

crlsizelimit: 512000

tls:
  # Enable TLS (default: false)
  enabled: true
  certfile:
  keyfile:
  clientauth:
    type: noclientcert
    certfiles:

ca:
  # Name of this CA
  name: Org1CA
  keyfile:
  certfile:
  chainfile:

crl:
  expiry: 24h

registry:

  maxenrollments: -1

  identities:
     - name: admin
       pass: adminpw
       type: client
       affiliation: ""
       attrs:
          hf.Registrar.Roles: "*"
          hf.Registrar.DelegateRoles: "*"
          hf.Revoker: true
          hf.IntermediateCA: true
          hf.GenCRL: true
          hf.Registrar.Attributes: "*"
          hf.AffiliationMgr: true

db:
  type: sqlite3
  datasource: fabric-ca-server.db
  tls:
      enabled: false
      certfiles:
      client:
        certfile:
        keyfile:

ldap:

   enabled: false
   url: ldap://<adminDN>:<adminPassword>@<host>:<port>/<base>
   tls:
      certfiles:
      client:
         certfile:
         keyfile:
   attribute:
      names: ['uid','member']
      converters:
         - name:
           value:
      maps:
         groups:
            - name:
              value:

affiliations:
   org1:
      - department1
      - department2
   org2:
      - department1

signing:
    default:
      usage:
        - digital signature
      expiry: 8760h
    profiles:
      ca:
         usage:
           - cert sign
           - crl sign
         expiry: 43800h
         caconstraint:
           isca: true
           maxpathlen: 0
      tls:
         usage:
            - signing
            - key encipherment
            - server auth
            - client auth
            - key agreement
         expiry: 8760h

csr:
   cn: ca.org1.example.com
   names:
      - C: US
        ST: "North Carolina"
        L: "Durham"
        O: org1.example.com
        OU:
   hosts:
     - localhost
     - org1.example.com
   ca:
      expiry: 131400h
      pathlength: 1

bccsp:
    default: SW
    sw:
        hash: SHA2
        security: 256
        filekeystore:
            keystore: msp/keystore

cacount:

cafiles:

intermediate:
  parentserver:
    url:
    caname:

  enrollment:
    hosts:
    profile:
    label:

  tls:
    certfiles:
    client:
      certfile:
      keyfile:


以及server/fabric-ca-server-config.yaml::

展开查看server/fabric-ca-server-config.yaml:
# Version of config file
version: 1.2.0
# Server's listening port (default: 7054)
port: 7054
# Enables debug logging (default: false)
debug: false
# Size limit of an acceptable CRL in bytes (default: 512000)
crlsizelimit: 512000
tls:
  # Enable TLS (default: false)
  enabled: true
  # TLS for the server's listening port
  certfile:
  keyfile:
  clientauth:
    type: noclientcert
    certfiles:

ca:
  # Name of this CA
  name: OrdererCA
  keyfile:
  certfile:
  chainfile:

crl:
  expiry: 24h

registry:
  maxenrollments: -1

  identities:
     - name: admin
       pass: adminpw
       type: client
       affiliation: ""
       attrs:
          hf.Registrar.Roles: "*"
          hf.Registrar.DelegateRoles: "*"
          hf.Revoker: true
          hf.IntermediateCA: true
          hf.GenCRL: true
          hf.Registrar.Attributes: "*"
          hf.AffiliationMgr: true

db:
  type: sqlite3
  datasource: fabric-ca-server.db
  tls:
      enabled: false
      certfiles:
      client:
        certfile:
        keyfile:

ldap:
   enabled: false
   url: ldap://<adminDN>:<adminPassword>@<host>:<port>/<base>
   tls:
      certfiles:
      client:
         certfile:
         keyfile:
   attribute:
      names: ['uid','member']
      converters:
         - name:
           value:
      maps:
         groups:
            - name:
              value:

affiliations:
   org1:
      - department1
      - department2
   org2:
      - department1

signing:
    default:
      usage:
        - digital signature
      expiry: 8760h
    profiles:
      ca:
         usage:
           - cert sign
           - crl sign
         expiry: 43800h
         caconstraint:
           isca: true
           maxpathlen: 0
      tls:
         usage:
            - signing
            - key encipherment
            - server auth
            - client auth
            - key agreement
         expiry: 8760h

csr:
   cn: ca.example.com
   names:
      - C: US
        ST: "New York"
        L: "New York"
        O: example.com
        OU:
   hosts:
     - localhost
     - example.com
   ca:
      expiry: 131400h
      pathlength: 1

bccsp:
    default: SW
    sw:
        hash: SHA2
        security: 256
        filekeystore:
            keystore: msp/keystore

cacount:
cafiles:

intermediate:
  parentserver:
    url:
    caname:

  enrollment:
    hosts:
    profile:
    label:

  tls:
    certfiles:
    client:
      certfile:
      keyfile:


docker-compose-ca.yaml文件:

展开查看docker-compose-ca.yaml文件
version: '2'

services:
  ca:
    image: hyperledger/fabric-ca:1.4.4
    environment:
      - FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server
      - FABRIC_CA_SERVER_CA_NAME=ca-orderer
      - FABRIC_CA_SERVER_TLS_ENABLED=true
      - FABRIC_CA_SERVER_PORT=9054
    ports:
      - "9054:9054"
    command: sh -c 'fabric-ca-server start -b admin:adminpw -d'
    volumes:
      - ../ca/server:/etc/hyperledger/fabric-ca-server
    container_name: ca_orderer

  ca0:
    image: hyperledger/fabric-ca:1.4.4
    environment:
      - FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server
      - FABRIC_CA_SERVER_CA_NAME=ca-org1
      - FABRIC_CA_SERVER_TLS_ENABLED=true
      - FABRIC_CA_SERVER_PORT=7054
    ports:
      - "7054:7054"
    command: sh -c 'fabric-ca-server start -b admin:adminpw -d'
    volumes:
      - ../ca/org1:/etc/hyperledger/fabric-ca-server
    container_name: ca_org1


将以上三个文件保存到指定的路径，然后使用以下命令启动CA服务器：
docker-compose -f docker/docker-compose-ca.yaml up -d
服务器会自动读取上面的两个配置文件，并初始化CA服务器。
当然，服务器配置文件将自动生成在ca/server/子文件夹内，其中最主要使用到的是tls-cert.pem文件。
1.2 注册Orderer节点
首先配置环境变量并登陆管理员账号:
#创建存储Order节点证书的子文件夹。
mkdir -p crypto-config/orderOrganization/example.com
export FABRIC_CA_CLIENT_HOME=${PWD}/crypto-config/orderOrganization/example.com
fabric-ca-client enroll -u https://admin::9054 --caname ca-orderer --tls.certfiles ${PWD}/ca/server/tls-cert.pem
生成节点类型分类配置文件(不知道这个文件应该称作什么，暂且使用这个名字称呼好了):
echo 'NodeOUs:
  Enable: true
  ClientOUIdentifier:
    Certificate: cacerts/localhost-9054-ca-orderer.pem
    OrganizationalUnitIdentifier: client
  PeerOUIdentifier:
    Certificate: cacerts/localhost-9054-ca-orderer.pem
    OrganizationalUnitIdentifier: peer
  AdminOUIdentifier:
    Certificate: cacerts/localhost-9054-ca-orderer.pem
    OrganizationalUnitIdentifier: admin
  OrdererOUIdentifier:
    Certificate: cacerts/localhost-9054-ca-orderer.pem
    OrganizationalUnitIdentifier: orderer' > ${PWD}/crypto-config/orderOrganization/example.com/msp/config.yaml
之后注册网络中初始的4个Orderer节点:
fabric-ca-client register -u https://admin::9054 --caname ca-orderer --id.name orderer1 --id.secret ordererpw --id.type orderer --id.attrs '"hf.Registrar.Roles=orderer"' --tls.certfiles ${PWD}/ca/server/tls-cert.pem
fabric-ca-client register -u https://admin::9054 --caname ca-orderer --id.name orderer2 --id.secret ordererpw --id.type orderer --id.attrs '"hf.Registrar.Roles=orderer"' --tls.certfiles ${PWD}/ca/server/tls-cert.pem
fabric-ca-client register -u https://admin::9054 --caname ca-orderer --id.name orderer3 --id.secret ordererpw --id.type orderer --id.attrs '"hf.Registrar.Roles=orderer"' --tls.certfiles ${PWD}/ca/server/tls-cert.pem
fabric-ca-client register -u https://admin::9054 --caname ca-orderer --id.name orderer4 --id.secret ordererpw --id.type orderer --id.attrs '"hf.Registrar.Roles=orderer"' --tls.certfiles ${PWD}/ca/server/tls-cert.pem
注册Admin节点:
fabric-ca-client register -u https://admin::9054 --caname ca-orderer --id.name ordererAdmin --id.secret ordererAdminpw --id.type admin --id.attrs '"hf.Registrar.Roles=admin"' --tls.certfiles ${PWD}/ca/server/tls-cert.pem
1.3 获取Orderer证书文件
为刚刚创建的几个用户创建各自的文件夹用于存储证书文件:
mkdir -p crypto-config/orderOrganization/example.com/orderers
mkdir -p crypto-config/orderOrganization/example.com/orderers/orderer1.example.com
mkdir -p crypto-config/orderOrganization/example.com/orderers/orderer2.example.com
mkdir -p crypto-config/orderOrganization/example.com/orderers/orderer3.example.com
mkdir -p crypto-config/orderOrganization/example.com/orderers/orderer4.example.com
接下来获取每一个Orderer节点的MSP证书文件:
fabric-ca-client enroll -u https://orderer1::9054 --caname ca-orderer -M ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer1.example.com/msp --csr.hosts orderer1.example.com --tls.certfiles ${PWD}/ca/server/tls-cert.pem
fabric-ca-client enroll -u https://orderer2::9054 --caname ca-orderer -M ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer2.example.com/msp --csr.hosts orderer2.example.com --tls.certfiles ${PWD}/ca/server/tls-cert.pem
fabric-ca-client enroll -u https://orderer3::9054 --caname ca-orderer -M ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer3.example.com/msp --csr.hosts orderer3.example.com --tls.certfiles ${PWD}/ca/server/tls-cert.pem
fabric-ca-client enroll -u https://orderer4::9054 --caname ca-orderer -M ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer4.example.com/msp --csr.hosts orderer4.example.com --tls.certfiles ${PWD}/ca/server/tls-cert.pem
还有每一个节点的TLS证书:
fabric-ca-client enroll -u https://orderer1::9054 --caname ca-orderer -M ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer1.example.com/tls --enrollment.profile tls --csr.hosts orderer1.example.com --tls.certfiles ${PWD}/ca/server/tls-cert.pem
fabric-ca-client enroll -u https://orderer2::9054 --caname ca-orderer -M ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer2.example.com/tls --enrollment.profile tls --csr.hosts orderer2.example.com --tls.certfiles ${PWD}/ca/server/tls-cert.pem
fabric-ca-client enroll -u https://orderer3::9054 --caname ca-orderer -M ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer3.example.com/tls --enrollment.profile tls --csr.hosts orderer3.example.com --tls.certfiles ${PWD}/ca/server/tls-cert.pem
fabric-ca-client enroll -u https://orderer4::9054 --caname ca-orderer -M ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer4.example.com/tls --enrollment.profile tls --csr.hosts orderer4.example.com --tls.certfiles ${PWD}/ca/server/tls-cert.pem
将之前生成的节点类型分类配置文件拷贝到每一个节点的MSP文件夹:
cp ${PWD}/crypto-config/orderOrganization/example.com/msp/config.yaml ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer1.example.com/msp/config.yaml
cp ${PWD}/crypto-config/orderOrganization/example.com/msp/config.yaml ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer2.example.com/msp/config.yaml
cp ${PWD}/crypto-config/orderOrganization/example.com/msp/config.yaml ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer3.example.com/msp/config.yaml
cp ${PWD}/crypto-config/orderOrganization/example.com/msp/config.yaml ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer4.example.com/msp/config.yaml
然后为每一个节点的TLS证书以及秘钥文件修改名字，方便之后的使用:
cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer1.example.com/tls/tlscacerts/* ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer1.example.com/tls/ca.crt
cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer1.example.com/tls/signcerts/* ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer1.example.com/tls/server.crt
cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer1.example.com/tls/keystore/* ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer1.example.com/tls/server.key

cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer2.example.com/tls/tlscacerts/* ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer2.example.com/tls/ca.crt
cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer2.example.com/tls/signcerts/* ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer2.example.com/tls/server.crt
cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer2.example.com/tls/keystore/* ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer2.example.com/tls/server.key

cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer3.example.com/tls/tlscacerts/* ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer3.example.com/tls/ca.crt
cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer3.example.com/tls/signcerts/* ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer3.example.com/tls/server.crt
cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer3.example.com/tls/keystore/* ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer3.example.com/tls/server.key

cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer4.example.com/tls/tlscacerts/* ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer4.example.com/tls/ca.crt
cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer4.example.com/tls/signcerts/* ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer4.example.com/tls/server.crt
cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer4.example.com/tls/keystore/* ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer4.example.com/tls/server.key
然后在MSP文件夹内创建tlscacerts文件夹，并将TLS文件拷贝过去:
mkdir ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer1.example.com/msp/tlscacerts
mkdir ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer2.example.com/msp/tlscacerts
mkdir ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer3.example.com/msp/tlscacerts
mkdir ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer4.example.com/msp/tlscacerts

cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer1.example.com/tls/tlscacerts/* ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer1.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer2.example.com/tls/tlscacerts/* ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer2.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer3.example.com/tls/tlscacerts/* ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer3.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer4.example.com/tls/tlscacerts/* ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer4.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
复制TLS根证书:
mkdir -p ${PWD}/crypto-config/orderOrganization/example.com/msp/tlscacerts
cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer1.example.com/tls/tlscacerts/* ${PWD}/crypto-config/orderOrganization/example.com/msp/tlscacerts/tlsca.example.com-cert.pem
最后是Admin节点的证书文件:
#首先也是创建文件夹
mkdir -p crypto-config/orderOrganization/example.com/users
mkdir -p crypto-config/orderOrganization/example.com/users/
#获取证书文件
fabric-ca-client enroll -u https://ordererAdmin::9054 --caname ca-orderer -M ${PWD}/crypto-config/orderOrganization/example.com/users//msp --tls.certfiles ${PWD}/ca/server/tls-cert.pem
cp ${PWD}/crypto-config/orderOrganization/example.com/msp/config.yaml ${PWD}/crypto-config/orderOrganization/example.com/users//msp/config.yaml
到这里Orderer节点证书已经生成完毕(可以根据实际需要修改Orderer节点数量，最少不能低于3个)，接下来是网络中唯一的peer节点的配置文件生成:
1.4 注册Peer节点
和上面步骤相同，首先创建子文件夹用于存储证书文件:
mkdir -p crypto-config/peerOrganizations/org1.example.com/
配置环境变量并登陆管理员身份:
export FABRIC_CA_CLIENT_HOME=${PWD}/crypto-config/peerOrganizations/org1.example.com/
fabric-ca-client enroll -u https://admin::7054 --caname ca-org1 --tls.certfiles ${PWD}/ca/org1/tls-cert.pem
生成节点类型分类配置文件:
echo 'NodeOUs:
  Enable: true
  ClientOUIdentifier:
    Certificate: cacerts/localhost-7054-ca-org1.pem
    OrganizationalUnitIdentifier: client
  PeerOUIdentifier:
    Certificate: cacerts/localhost-7054-ca-org1.pem
    OrganizationalUnitIdentifier: peer
  AdminOUIdentifier:
    Certificate: cacerts/localhost-7054-ca-org1.pem
    OrganizationalUnitIdentifier: admin
  OrdererOUIdentifier:
    Certificate: cacerts/localhost-7054-ca-org1.pem
    OrganizationalUnitIdentifier: orderer' > ${PWD}/crypto-config/peerOrganizations/org1.example.com/msp/config.yaml
虽然网络中只有一个peer节点，但是我们需要注册三个用户:peer0,user1,org1admin，其中第一个是必需的，第二个是用于测试的，第三个为Admin用户，安装和实例化链码需要Admin用户的证书:
fabric-ca-client register -u https://admin::7054 --caname ca-org1 --id.name peer0 --id.secret peer0pw --id.type peer --id.attrs '"hf.Registrar.Roles=peer"' --tls.certfiles ${PWD}/ca/org1/tls-cert.pem
fabric-ca-client register -u https://admin::7054 --caname ca-org1 --id.name user1 --id.secret user1pw --id.type client --id.attrs '"hf.Registrar.Roles=client"' --tls.certfiles ${PWD}/ca/org1/tls-cert.pem
fabric-ca-client register -u https://admin::7054 --caname ca-org1 --id.name org1admin --id.secret org1adminpw --id.type admin --id.attrs '"hf.Registrar.Roles=admin"' --tls.certfiles ${PWD}/ca/org1/tls-cert.pem
1.5 获取Peer节点证书文件
节点注册完毕，获取他们的证书文件:
创建子文件夹:
mkdir -p crypto-config/peerOrganizations/org1.example.com/peers
mkdir -p crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.co
获取证书文件:
#MSP文件
fabric-ca-client enroll -u https://peer0::7054 --caname ca-org1 -M ${PWD}/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/msp --csr.hosts peer0.org1.example.com --tls.certfiles ${PWD}/ca/org1/tls-cert.pem
#TLS证书
fabric-ca-client enroll -u https://peer0::7054 --caname ca-org1 -M ${PWD}/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls --enrollment.profile tls --csr.hosts peer0.org1.example.com --csr.hosts localhost --tls.certfiles ${PWD}/ca/org1/tls-cert.pem
拷贝节点分类配置文件:
cp ${PWD}/crypto-config/peerOrganizations/org1.example.com/msp/config.yaml ${PWD}/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/msp/config.yaml
修改证书以及秘钥文件，方便之后使用:
cp ${PWD}/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/tlscacerts/* ${PWD}/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
cp ${PWD}/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/signcerts/* ${PWD}/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.crt
cp ${PWD}/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/keystore/* ${PWD}/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/server.key
将TLS相关证书复制一份:
mkdir ${PWD}/crypto-config/peerOrganizations/org1.example.com/msp/tlscacerts
cp ${PWD}/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/tlscacerts/* ${PWD}/crypto-config/peerOrganizations/org1.example.com/msp/tlscacerts/ca.crt

mkdir ${PWD}/crypto-config/peerOrganizations/org1.example.com/tlsca
cp ${PWD}/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/tlscacerts/* ${PWD}/crypto-config/peerOrganizations/org1.example.com/tlsca/tlsca.org1.example.com-cert.pem

mkdir ${PWD}/crypto-config/peerOrganizations/org1.example.com/ca
cp ${PWD}/crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/msp/cacerts/* ${PWD}/crypto-config/peerOrganizations/org1.example.com/ca/ca.org1.example.com-cert.pem
获取user与Admin用户证书文件:
#创建子文件夹
mkdir -p crypto-config/peerOrganizations/org1.example.com/users
mkdir -p crypto-config/peerOrganizations/org1.example.com/users/
mkdir -p crypto-config/peerOrganizations/org1.example.com/users/
#获取证书文件
fabric-ca-client enroll -u https://user1::7054 --caname ca-org1 -M ${PWD}/crypto-config/peerOrganizations/org1.example.com/users//msp --tls.certfiles ${PWD}/ca/org1/tls-cert.pem
fabric-ca-client enroll -u https://org1admin::7054 --caname ca-org1 -M ${PWD}/crypto-config/peerOrganizations/org1.example.com/users//msp --tls.certfiles ${PWD}/ca/org1/tls-cert.pem
cp ${PWD}/crypto-config/peerOrganizations/org1.example.com/msp/config.yaml ${PWD}/crypto-config/peerOrganizations/org1.example.com/users//msp/config.yaml
1.6 启动网络之前的准备
到这里我们已经生成了所有需要的证书文件，接下来是生成用于启动网络的创世区块,生成创世区块需要一个文件configtx.yaml,直接复制过来:

展开查看configtx.yaml
Organizations:
    - &OrdererOrg
        Name: OrdererOrg
        ID: OrdererMSP
        MSPDir: ./crypto-config/orderOrganization/example.com/msp   #这里路径需要对应！！！
        Policies:
            Readers:
                Type: Signature
                Rule: "OR('OrdererMSP.member')"
            Writers:
                Type: Signature
                Rule: "OR('OrdererMSP.member')"
            Admins:
                Type: Signature
                Rule: "OR('OrdererMSP.admin')"

    - &Org1  #如果需要更多组织节点，可以按照该模板在下面添加
        Name: Org1MSP
        ID: Org1MSP
        MSPDir: ./crypto-config/peerOrganizations/org1.example.com/msp  #这里路径需要对应！！！
        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')"
            Endorsement:
                Type: Signature
                Rule: "OR('Org1MSP.peer')"
        AnchorPeers:
              Port: 7051

Capabilities:
    Channel: &ChannelCapabilities
        V2_0: true

    Orderer: &OrdererCapabilities
        V2_0: true

    Application: &ApplicationCapabilities
        V2_0: true

Application: &ApplicationDefaults
    Organizations:
    Policies:
        Readers:
            Type: ImplicitMeta
            Rule: "ANY Readers"
        Writers:
            Type: ImplicitMeta
            Rule: "ANY Writers"
        Admins:
            Type: ImplicitMeta
            Rule: "MAJORITY Admins"
        LifecycleEndorsement:
            Type: ImplicitMeta
            Rule: "MAJORITY Endorsement"
        Endorsement:
            Type: ImplicitMeta
            Rule: "MAJORITY Endorsement"
    Capabilities:
        <<: *ApplicationCapabilities

Orderer: &OrdererDefaults
    OrdererType: etcdraft
    
    Addresses:
        - orderer1.example.com:7050
    BatchTimeout: 2s
    BatchSize:
        MaxMessageCount: 10
        AbsoluteMaxBytes: 99 MB
        PreferredMaxBytes: 512 KB
    Organizations:
    Policies:
        Readers:
            Type: ImplicitMeta
            Rule: "ANY Readers"
        Writers:
            Type: ImplicitMeta
            Rule: "ANY Writers"
        Admins:
            Type: ImplicitMeta
            Rule: "MAJORITY Admins"
        BlockValidation:
            Type: ImplicitMeta
            Rule: "ANY Writers"
Channel: &ChannelDefaults
    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:
        <<: *ChannelCapabilities

Profiles:
    
    TwoOrgsChannel:   #用于生成通道配置文件
        Consortium: SampleConsortium
        <<: *ChannelDefaults
        Application:
            <<: *ApplicationDefaults
            Organizations:
                - *Org1
            Capabilities:
                <<: *ApplicationCapabilities

    SampleMultiNodeEtcdRaft:   #用于生成系统通道创世区块
        <<: *ChannelDefaults
        Capabilities:
            <<: *ChannelCapabilities
        Orderer:
            <<: *OrdererDefaults
            OrdererType: etcdraft   #指定使用etcdraft共识算法
            EtcdRaft:
                Consenters:
                - Host: orderer1.example.com
                  Port: 7050
                  ClientTLSCert: ./crypto-config/orderOrganization/example.com/orderers/orderer1.example.com/tls/server.crt
                  ServerTLSCert: ./crypto-config/orderOrganization/example.com/orderers/orderer1.example.com/tls/server.crt
                - Host: orderer2.example.com
                  Port: 8050
                  ClientTLSCert: ./crypto-config/orderOrganization/example.com/orderers/orderer2.example.com/tls/server.crt
                  ServerTLSCert: ./crypto-config/orderOrganization/example.com/orderers/orderer2.example.com/tls/server.crt
                - Host: orderer3.example.com
                  Port: 9050
                  ClientTLSCert: ./crypto-config/orderOrganization/example.com/orderers/orderer3.example.com/tls/server.crt
                  ServerTLSCert: ./crypto-config/orderOrganization/example.com/orderers/orderer3.example.com/tls/server.crt
                - Host: orderer4.example.com
                  Port: 10050
                  ClientTLSCert: ./crypto-config/orderOrganization/example.com/orderers/orderer4.example.com/tls/server.crt
                  ServerTLSCert: ./crypto-config/orderOrganization/example.com/orderers/orderer4.example.com/tls/server.crt
#                    - Host: orderer5.example.com
#                      Port: 11050
#                      ClientTLSCert: ./crypto-config/orderOrganization/example.com/orderers/orderer1.example.com/tls/server.crt
#                      ServerTLSCert: ./crypto-config/orderOrganization/example.com/orderers/orderer1.example.com/tls/server.crt
            Addresses:
                - orderer1.example.com:7050
                - orderer2.example.com:8050
                - orderer3.example.com:9050
                - orderer4.example.com:10050
#                - orderer5.example.com:11050
         
            Organizations:
            - *OrdererOrg
            Capabilities:
                <<: *OrdererCapabilities
        Application:
            <<: *ApplicationDefaults
            Organizations:
            - <<: *OrdererOrg
        Consortiums:
            SampleConsortium:
                Organizations:
                - *Org1


将该文件保存到指定位置，接下来生成创世区块:
export FABRIC_CFG_PATH=$PWD
configtxgen -profile SampleMultiNodeEtcdRaft -channelID byfn-sys-channel -outputBlock ./channel-artifacts/genesis.block
# 生成通道配置文件
export CHANNEL_NAME=mychannel
configtxgen -profile TwoOrgsChannel -outputCreateChannelTx ./channel-artifacts/mychannel.tx -channelID $CHANNEL_NAME
1.7 启动网络
首先写包含所有节点的Docker文件,这里直接贴出来:

展开查看base.yaml
version: '2'

services:
  orderer-base:
    image: hyperledger/fabric-orderer:2.0.0-beta
    environment:
      - FABRIC_LOGGING_SPEC=INFO
#      - FABRIC_LOGGING_SPEC=DEBUG
      - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
      - ORDERER_GENERAL_BOOTSTRAPMETHOD=file
      - ORDERER_GENERAL_BOOTSTRAPFILE=/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]
      - ORDERER_GENERAL_CLUSTER_CLIENTCERTIFICATE=/var/hyperledger/orderer/tls/server.crt
      - ORDERER_GENERAL_CLUSTER_CLIENTPRIVATEKEY=/var/hyperledger/orderer/tls/server.key
      - ORDERER_GENERAL_CLUSTER_ROOTCAS=[/var/hyperledger/orderer/tls/ca.crt]
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric
    command: orderer


然后是Orderer节点的Docker文件:

展开查看docker-compose-orderers.yaml
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#

version: '2'

volumes:
  orderer1.example.com:
  orderer2.example.com:
  orderer3.example.com:
  orderer4.example.com:

networks:
  byfn:

services:
  
  orderer1.example.com:
    extends:
      file: base.yaml
      service: orderer-base
    environment:
      - ORDERER_GENERAL_LISTENPORT=7050
    container_name: orderer1.example.com
    networks:
      - byfn
    volumes:
      - ../channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block
      - ../crypto-config/orderOrganization/example.com/orderers/orderer1.example.com/msp:/var/hyperledger/orderer/msp
      - ../crypto-config/orderOrganization/example.com/orderers/orderer1.example.com/tls/:/var/hyperledger/orderer/tls
      - ../store/o1:/var/hyperledger/production/orderer
    ports:
      - 7050:7050



  orderer2.example.com:
    extends:
      file: base.yaml
      service: orderer-base
    environment:
      - ORDERER_GENERAL_LISTENPORT=8050
    container_name: orderer2.example.com
    networks:
      - byfn
    volumes:
      - ../channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block
      - ../crypto-config/orderOrganization/example.com/orderers/orderer2.example.com/msp:/var/hyperledger/orderer/msp
      - ../crypto-config/orderOrganization/example.com/orderers/orderer2.example.com/tls/:/var/hyperledger/orderer/tls
      - ../store/o2:/var/hyperledger/production/orderer
    ports:
      - 8050:8050
  
  orderer3.example.com:
    extends:
      file: base.yaml
      service: orderer-base
    environment:
      - ORDERER_GENERAL_LISTENPORT=9050
    container_name: orderer3.example.com
    networks:
      - byfn
    volumes:
      - ../channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block
      - ../crypto-config/orderOrganization/example.com/orderers/orderer3.example.com/msp:/var/hyperledger/orderer/msp
      - ../crypto-config/orderOrganization/example.com/orderers/orderer3.example.com/tls/:/var/hyperledger/orderer/tls
      - ../store/o3:/var/hyperledger/production/orderer
    ports:
      - 9050:9050
  
  orderer4.example.com:
    extends:
      file: base.yaml
      service: orderer-base
    environment:
      - ORDERER_GENERAL_LISTENPORT=10050
    container_name: orderer4.example.com
    networks:
      - byfn
    volumes:
      - ../channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block
      - ../crypto-config/orderOrganization/example.com/orderers/orderer4.example.com/msp:/var/hyperledger/orderer/msp
      - ../crypto-config/orderOrganization/example.com/orderers/orderer4.example.com/tls/:/var/hyperledger/orderer/tls
      - ../store/o4:/var/hyperledger/production/orderer
    ports:
      - 10050:10050


最后一个是peer节点的Docker文件：

展开查看docker-compose-peer.yaml
version: '2'

volumes:
  peer0.org1.example.com:

networks:
  byfn:

services:

  peer0.org1.example.com:
    container_name: peer0.org1.example.com
    image: hyperledger/fabric-peer:2.0.0-beta
    environment:
      #Generic peer variables
      - 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=${COMPOSE_PROJECT_NAME}_byfn
      - FABRIC_LOGGING_SPEC=INFO
      #- FABRIC_LOGGING_SPEC=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
      # Peer specific variabes
      - CORE_PEER_ID=peer0.org1.example.com
      - CORE_PEER_ADDRESS=peer0.org1.example.com:7051
      - CORE_PEER_LISTENADDRESS=0.0.0.0:7051
      - CORE_PEER_CHAINCODEADDRESS=peer0.org1.example.com:7052
      - CORE_PEER_CHAINCODELISTENADDRESS=0.0.0.0:7052
      - CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org1.example.com:7051
      - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.example.com:7051
      - CORE_PEER_LOCALMSPID=Org1MSP
      - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
      - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb0:5984
      # The CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME and CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD
      # provide the credentials for ledger to connect to CouchDB.  The username and password must
      # match the username and password set for the associated CouchDB.
      - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=
      - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=
    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
      - ../store/p1:/var/hyperledger/production
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: peer node start
    depends_on:
      - couchdb0
    ports:
      - 7051:7051
    networks:
      - byfn

  couchdb0:
    container_name: couchdb0
    image: couchdb:2.3
    # Populate the COUCHDB_USER and COUCHDB_PASSWORD to set an admin user and password
    # for CouchDB.  This will prevent CouchDB from operating in an "Admin Party" mode.
    environment:
      - COUCHDB_USER=
      - COUCHDB_PASSWORD=
    # 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"
    networks:
      - byfn

  cli:
    container_name: cli
    image: hyperledger/fabric-tools:2.0.0-beta
    tty: true
    stdin_open: true
    environment:
      - GOPATH=/opt/gopath
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
#      - FABRIC_LOGGING_SPEC=DEBUG
      - FABRIC_LOGGING_SPEC=INFO
      - CORE_PEER_ID=peer0.org1.example.com
      - 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//msp
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: /bin/bash
    volumes:
      - /var/run/:/host/var/run/
      - ./../../chaincode/:/opt/gopath/src/github.com/hyperledger/fabric-samples/chaincode
      - ../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:
      - peer0.org1.example.com
    networks:
      - byfn


将以上文件保存到指定位置后，使用以下命令直接启动:
docker-compose -f docker/docker-compose-orderers.yaml -f docker/docker-compose-peer.yaml up -d
启动完成后可以查看每个节点的日志确认节点成功运行:
docker logs orderer1.example.com
...
docker logs peer0.org1.example.com
如果没有错误的话就可以进行第二部分了，如果出现错误则要回去检查是不是哪里漏掉了。
1.8 简单测试
先进行第一部分的测试，看一下创建通道，加入通道是否成功:
#进入CLI容器
docker exec -it cli bash
#配置环境变量
export CHANNEL_NAME=mychannel
export ORDERER_CA=${PWD}/crypto/orderOrganization/example.com/orderers/orderer1.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
export PEER0_ORG1_CA=${PWD}/crypto/peerOrganization/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt
export CORE_PEER_LOCALMSPID="Org1MSP"
export CORE_PEER_TLS_ROOTCERT_FILE=$PEER0_ORG1_CA
export CORE_PEER_MSPCONFIGPATH=${PWD}/crypto/peerOrganizations/org1.example.com/users//msp
export CORE_PEER_ADDRESS=peer0.org1.example.com:7051
创建通道:
peer channel create -o orderer1.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/mychannel.tx --tls $CORE_PEER_TLS_ENABLED --cafile $ORDERER_CA --outputBlock ./channel-artifacts/${CHANNEL_NAME}.block
加入通道:
peer channel join -b ./channel-artifacts/$CHANNEL_NAME.block
如果一切顺利的话，网络就成功搭建起来了，至于链码就不再测试了。
直接到第二部分，动态添加一个Orderer节点。
2 动态添加Raft节点
主要步骤如下：
  1. 为该节点生成证书文件
  2. 获取当前网络的配置文件
  3. 将证书文件添加到配置文件中
  4. 更新配置文件
  5. 启动新的Orderer节点
2.1 生成证书文件
2.1.1 注册该节点身份
fabric-ca-client register -u https://admin::9054 --caname ca-orderer --id.name orderer5 --id.secret ordererpw --id.type orderer --id.attrs '"hf.Registrar.Roles=orderer"' --tls.certfiles ${PWD}/ca/server/tls-cert.pem
为该节点创建存储证书的文件夹:
mkdir -p crypto-config/orderOrganization/example.com/orderers/orderer5.example.com
2.1.2 获取该节点证书
#MSP
fabric-ca-client enroll -u https://orderer5::9054 --caname ca-orderer -M ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer5.example.com/msp --csr.hosts orderer5.example.com --tls.certfiles ${PWD}/ca/server/tls-cert.pem
#TLS
fabric-ca-client enroll -u https://orderer5::9054 --caname ca-orderer -M ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer5.example.com/tls --enrollment.profile tls --csr.hosts orderer5.example.com --tls.certfiles ${PWD}/ca/server/tls-cert.pem
复制节点分类配置文件:
cp ${PWD}/crypto-config/orderOrganization/example.com/msp/config.yaml ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer5.example.com/msp/config.yaml
修改证书与秘钥文件名称:
cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer5.example.com/tls/tlscacerts/* ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer5.example.com/tls/ca.crt
cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer5.example.com/tls/signcerts/* ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer5.example.com/tls/server.crt
cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer5.example.com/tls/keystore/* ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer5.example.com/tls/server.key
创建文件夹并拷贝TLS证书文件:
mkdir ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer5.example.com/msp/tlscacerts
cp ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer5.example.com/tls/tlscacerts/* ${PWD}/crypto-config/orderOrganization/example.com/orderers/orderer5.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
2.2 获取网络配置文件
将节点添加进网络，首先需要将该节点添加到系统通道内，所以先获取系统通道的配置文件:
进入cli容器:
docker exec -it cli bash
配置环境变量，需要使用Orderer节点的身份信息:
export CORE_PEER_LOCALMSPID="OrdererMSP"
export ORDERER_CA=${PWD}/crypto/orderOrganization/example.com/orderers/orderer1.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
export CORE_PEER_TLS_ROOTCERT_FILE=${PWD}/crypto/ordererOrganization/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
export CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/orderOrganization/example.com/users//msp
export CORE_PEER_ADDRESS=peer0.org1.example.com:7051
获取系统通道配置文件:
peer channel fetch config channel-artifacts/config_block.pb -o orderer1.example.com:7050 -c byfn-sys-channel --tls --cafile $ORDERER_CA
解码该配置文件:
configtxlator proto_decode --input channel-artifacts/config_block.pb --type common.Block | jq .data.data[0].payload.data.config > channel-artifacts/config.json
2.3将证书文件添加到配置文件中
退出容器，可以在channel-artifacts文件内找到config.json文件。将该文件复制一份并在channel-artifacts文件夹下保存为update_config.json,使用编辑工具打开，并搜索.example.com字段如下：
字段一部分：
{
    "client_tls_cert": "一连串的字符串",
    "host": "orderer1.example.com",
    "port": 7050,
    "server_tls_cert": "一连串的字符串"
  }
以及匹配到的第二部分的字段:
"OrdererAddresses": {
        "mod_policy": "/Channel/Orderer/Admins",
        "value": {
          "addresses": [
            "orderer1.example.com:7050",
            "orderer2.example.com:8050",
            "orderer3.example.com:9050",
            "orderer4.example.com:10050"
          ]
        },
        "version": "0"
    }
在字段一部分，需要将我们生成的新的节点的证书添加上去，其中证书文件地址为:
crypto-config/ordererOrganizations/example.com/orderers/orderer5.example.com/tls/server.crt
使用BASE64转码:
cat crypto-config/ordererOrganizations/example.com/orderers/orderer5.example.com/tls/server.crt | base64 > cert.txt
在update_config.json文件中字段一的部分下面按照字段一的格式添加相同的代码块，并进行修改：
将cert.txt文件中的内容复制到字段一的client_tls_cert,server_tls_cert对应部分，并修改host对应部分为orderer5.example.com，port为11050.
2.4更新配置文件
接下来进入cli容器:
docker exec -it cli bash
对原有的配置文件与更新的配置文件进行编码:
configtxlator proto_encode --input channel-artifacts/config.json --type common.Config > channel-artifacts/config.pb
configtxlator proto_encode --input channel-artifacts/update_config.json --type common.Config > channel-artifacts/config_update.pb
计算出两个文件的差异:
configtxlator compute_update --channel_id byfn-sys-channel --original channel-artifacts/config.pb --updated channel-artifacts/config_update.pb > channel-artifacts/updated.pb
对该文件进行解码，并添加用于更新配置的头部信息:
configtxlator proto_decode --input channel-artifacts/updated.pb --type common.ConfigUpdate > channel-artifacts/updated.json
echo '{"payload":{"header":{"channel_header":{"channel_id":"byfn-sys-channel", "type":2}},"data":{"config_update":'$(cat channel-artifacts/updated.json)'}}}' | jq . > channel-artifacts/updated_envelope.json
编码为Envelope格式的文件:
configtxlator proto_encode --input channel-artifacts/updated_envelope.json --type common.Envelope > channel-artifacts/updated_envelope.pb
对该文件进行签名操作，用于更新配置:
peer channel signconfigtx -f channel-artifacts/updated_envelope.pb
提交更新通道配置交易:
peer channel update -f channel-artifacts/updated_envelope.pb -c byfn-sys-channel -o orderer1.example.com:7050 --tls true --cafile $ORDERER_CA
如果没有错误的话，新的Orderer节点证书已经成功添加到网络配置中，接下来可以启动新的节点了:
2.5 启动新的Orderer节点
写一下新的Orderer节点的Docker文件:

展开查看docker-compose-addOrderer5.yaml
version: '2'

volumes:
  orderer5.example.com:

networks:
  byfn:

services:
  orderer5.example.com:
    extends:
      file: base.yaml
      service: orderer-base
    environment:
      - ORDERER_GENERAL_LISTENPORT=11050
    container_name: orderer5.example.com
    networks:
      - byfn
    volumes:
      - ../channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block
      - ../crypto-config/orderOrganization/example.com/orderers/orderer5.example.com/msp:/var/hyperledger/orderer/msp
      - ../crypto-config/orderOrganization/example.com/orderers/orderer5.example.com/tls/:/var/hyperledger/orderer/tls
      - ../store/o5:/var/hyperledger/production/orderer
    ports:
      - 11050:11050


直接通过命令启动它:
docker-compose -f docker-compose-addOrderer5.yaml up -d
可以查看新节点的日志确认新的节点已经成功加入了网络。
到这里，本文成功把新的Orderer节点添加进了网络，但是只将该节点添加到了系统通道内，对于应用通道mychannel来说，新的节点并没有添加进来，将新的节点添加进mychannel通道和以上步骤相同，只需要将通道名称由系统通道修改为mychannel即可。本文便不再说明了。
而动态删除节点的过程与添加相似，只不过是从配置文件中删除节点证书。
 
 
 
 
 
  ShiShuo  
 
 
  ShiShuo  
 
 
 
 
 
  
 
 
 
 
相关推荐
  
 
 
  Hyperledger Fabric【区块链学习一】  
 
 
 
     什么是区块链在我们没有接触的时候，只知道它是一个去中心化的存储方式。当我们发生交易，或者动作的时候我们会将记录通知给所有参与者共同维护，达到去中心化的进行存储。并且我们会将记录使用加密技术保证记录一旦添加到了账本中就无法修改这个也就是区块链有时候被称为证明   
 
 
 pxy  / 0评论  2020-08-15  
 
  
 
 
  为什么要使用智能合约来构建区块链应用程序?  
 
 
 
     　　为什么要使用智能合约来构建区块链应用程序?　　区块链技术最关键的特征之一就是它的去中心化性质。这意味着其信息由网络的所有各方共享。　　以下将探讨智能合约在市场上创建区块链应用的重要性和需求。　　智能合约是一种计算机软件，它直接控制买卖双方之间数字货币的   
 
 
 hackeey  / 0评论  2020-03-26  
 
  
 
 
  Hyperledger Fabric（四）first-network案例中的主要配置文件及主要脚本  
 
 
 
     Cryptogen工具使用该文件生成“密码材料”，即Fabric网络中各种实体所需的证书及密钥。该配置文件中的“count”变量用来指定每个组织的对等点数量，文件的其余部分较容易理解。cryptogen generate --config=./crypto   
 
 
 Walter的学习笔记  / 0评论  2020-03-04  
 
  
 
 
  Hyperledger Fabric（二）运行测试网络（test-network）  
 
 
 
     ① cd fabric-samples/test-network #进入test-network目录下，关键脚本network.sh包含了启动网络，创建通道，销毁网络等功能，./network.sh -h可查看详细信息。②./network.sh up #   
 
 
 Aggressivesnail  / 0评论  2020-03-03  
 
  
 
 
  hyperledger fabric 1.4.4 + explorer搭建  
 
 
 
     基础配置：setenforce 0、关闭防火墙。上传下载的所有文件到centos中。执行如下命令进行镜像还原：。./byfn.sh up -l java -o etcdraft -s couchdb. 上面红色部分需要改成实际的fabric配置路径，默认为   
 
 
 baixiaoshi  / 0评论  2020-01-09  
 
  
 
 
  [转帖]Hyperledger Fabric 学习一：简介  
 
 
 
     Hyperledger项目：2015年12月，由开源世界的旗舰组织Linux基金会牵头，30家初始企业成员共同宣布Hyperledger联合项目成立。作为一个联合项目，旗下由面向不同的场景的子项目构成：包括Fabric、Sawtooth、Iroha、Blo   
 
 
 pxy  / 0评论  2019-12-08  
 
  
 
 
  hyperledger fabric 1.4 创建联盟  
 
 
 
     在fabric中联盟不能为空，必须包含一个组织机构，所以在创建联盟的时候必须有一个组织机构，能够添加进去，fabric中的联盟和通道是一对一的关系，联盟必须和通道channel并存，而联盟的所有配置都是记录在系统channel的配置区块中的，包括有哪些联盟   
 
 
 photoed  / 0评论  2019-11-04  
 
  
 
 
  Hyperledger Fabric原理（2）共识与交易  
 
 
 
     Fabric 的网络节点本质上是互相复制的状态机，节点之间需要保持相同的账本状态。为了实现这个目的，各个节点需要通过共识过程，对账本状态的变化达成一致性的认同。Fabric 的共识过程包括 3 个阶段：背书、排序和校验。Fabric 1.0 中的排序服务支   
 
 
 Aggressivesnail  / 0评论  2019-10-31  
 
  
 
 
  如何建立一个运行在区块链上的世界？  
 
 
 
     　　区块链如今还是一个襁褓中的婴儿，在其得到广泛应用、充分发挥潜力之前，有许多事情需要先行解决。比如，我们需要获得政府的认可。另外，我们需要统一的区块链行业公开标准。目前在此方面努力的最杰出联盟是Hyperledger项目。该项目最近发布了首个可直接运用于   
 
 
 meiguopai  / 0评论  2019-10-26  
 
  
 
 
  Hyperledger Fabric安装问题-证书生成时签名key不兼容问题  
 
 
 
     2018-08-22 11:03:23.280 UTC [orderer/multichain] newLedgerResources -> CRIT 067 Error creating configtx manager and handlers:   
 
 
 zhuce  / 0评论  2018-08-23  
 
  
 
 
  Hyperledger(超级账本)的worldstate和SAP CRM的CRMD_CUMULAT_H  
 
 
 
     Hyperledger fabric是基于区块链技术的一个开源项目，由Linux基金会于2015年发起，目的是推进区块链数字技术和交易验证的发展和落地。Hyperledger由多个区块构成了一个有序链表，每个区块里包含多条交易。而Hyperledger F   
 
 
 zhuce  / 0评论  2018-09-24  
 
  
 
 
  阿里云容器服务区块链解决方案全新升级 支持Hyperledger Fabric v1.1  
 
 
 
     摘要：全球开源区块链领域影响最为广泛的Hyperledger Fabric日前宣布了1.1版本的正式发布，带来了一系列丰富的新功能以及在安全性、性能与扩展性等方面的显著提升。阿里云容器服务区块链解决方案第一时间同步升级，在v1.1新功能的基础上，提供了弹性   
 
 
 whb  / 0评论  2018-04-03  
 
  
 
 
  如何编写一个企业级区块链Hyperledger Fabric开源框架  
 
 
 
     Convector是为企业区块链框架构建的JavaScript开发框架。它增强了开发体验，同时帮助开发人员创建更强大，更安全的智能合约系统。它通过链代码和后端一直到前端，允许开发人员以库的形式重用相同的代码库。它基于模型/控制器模式，支持Hyperledg   
 
 
 开发学习者  / 0评论  2019-07-01  
 
  
 
 
  Hyperledger Fabric Node.js如何使用基于通道的事件服务  
 
 
 
     本教程说明了基于通道的事件的使用。这些事件与现有事件类似，但是特定于单个通道。在设置侦听器时，客户端处理基于通道的事件有一些新选项。有关Fabric入门的更多信息，请查看构建你的第一个网络或者手把手教你走进Hyperledger Fabric。我们将这些称   
 
 
 加油码农  / 0评论  2019-07-01  
 
  
 
 
  利用Hyperledger Fabric开发你的第一个区块链应用  
 
 
 
     在这个例子中使用的应用程序和智能合约（链码）统称为fabcar。这个例子很好地提供了一个开始用于理解Hyperledger Fabric。在这里，你将学会如何开发一个应用程序和智能合约来查询和更新账本，如何利用CA来生成一个应用程序需要的用于和区块链交互的   
 
 
 willorfang的学习  / 0评论  2019-07-01  
 
  
 
 
  Hyperledger Fabric 2.0 Alpha发布了！  
 
 
 
     随着近期Fabric v1.4.1 LTS的发布，Fabric项目目前工作的重点正在向1.4.1和2.0的正式版推进。v2.0.0是2019年的主要目标，重点集中在更多的新特性上，包括增强的链码生命周期管理，raft共识机制，以此来循序渐进地迁移至拜占庭容   
 
 
 开发学习者  / 0评论  2019-07-01  
 
  
 
 
  Ubuntu 18 部署 Hyperledger Fabric 1.4  
 
 
 
     安装 sshsudo apt-get updatesudo apt-get install ssh安装 Go下载Go源码下载 选择对应的平台下载。准备在下载的位置打开 terminal 。安装sudo tar -zxvf goxxxxx.tar.gz -C   
 
 
 岳英豪  / 0评论  2019-07-01  
 
  
 
 
  用VSCode和IBM Hyperledger Fabric 区块链扩展开发智能合约  
 
 
 
     了解使用IBM Blockchain Platform的VSCode扩展来简化开发，测试和部署智能合约的过程。完成本教程后，你将了解如何使用VSCode在本地Hyperledger Fabric网络上快速开发，演示和部署区块链应用程序。本教程假设你对Hyp   
 
 
 ShangQuan0  / 0评论  2019-07-01  
 
  
 
 
  Hyperledger Fabric 区块链开发详解  
 
 
 
     Hyperledger是一个旨在推动区块链跨行业应用的开源项目，由Linux基金会在2015年12月主导发起该项目，成员包括金融、银行、物联网、供应链、制造和科技等多个行业的领头羊，托管了众多面向企业的区块链开源框架和工具。由于Fabric项目的目标是应用   
 
 
 withjeffrey  / 0评论  2019-07-01  
 
  
 
 
  基于Hyperledger Fabric交易系统帐户的钱包模型的java Chaincode实例  
 
 
 
     还有Go和NodeJS Chaincodes，我们将来可能会讨论它们。此外，我采用基于帐户的钱包模型作为示例，我们将使用Hyperledger Fabric构建你的第一个网络，作为我们的测试环境。如果你不知道如何启动BYFN网络，我也会提供步骤，不用担心。   
 
 
 加油码农  / 0评论  2019-07-01  
 
  
 
 
  手把手教你走进Hyperledger Fabric  
 
 
 
     现在，Blockchain是业内新的热门话题。但是，寻找良好的资源来学习这项引人入胜的技术并不是一件容易的事。为了让其他人更容易学习，我开始在区块链和分布式分类帐技术平台领域开展一系列工作。我将尽力涵盖每一步都需要掌握这些技术。Hyperledger Fa   
 
 
 永不停歇的脚步  / 0评论  2019-07-01  
 
  
 
 
  Hyperledger(超级账本)的worldstate和SAP CRM的CRMD_CUMULAT_H  
 
 
 
     Hyperledger fabric是基于区块链技术的一个开源项目，由Linux基金会于2015年发起，目的是推进区块链数字技术和交易验证的发展和落地。Hyperledger由多个区块构成了一个有序链表，每个区块里包含多条交易。而Hyperledger F   
 
 
 糨糊  / 0评论  2018-09-24  
 
  
 
 
  Hyperledger Fabric Node.js 智能合约即链码开发  
 
 
 
     Hyperledger Fabric是一种联盟区块链，Fabric区块链也支持智能合约，被称为链码。Fabric链码就是一个标准的操作系统进程，通过gRPC协议与Fabric节点通信。目前官方提供了三种开发语言的Fabric链码开发工具包：Go、Java和   
 
 
 gaolong0  / 0评论  2019-06-30  
 
  
 
 
  Hyperledger Fabric 部署for Mac  
 
 
 
     环境准备docker安装Docker最低版本要求是version 17.06.2-ce推荐在Docker官网下载Mac版本。./bootstrap.sh -s 1.2.0然后你将得到一个 fabric-samples 文件夹在fabric-samples/   
 
 
 zfeifei  / 0评论  2019-06-28  
 
  
 
 
  以太坊、EOS和Hyperledger等不同区块链的比较  
 
 
 
     不同的区块链智能合约和区块链技术现在风靡一时。越来越多的人出于某种原因试图进入这个神奇的世界。如果你是这项技术的新手并正在寻找基于区块链的开发平台的快速入门，那么本指南非常适合你。我们将重点关注和比较的平台是：。以太坊最终将利用Casper协议转向权益证明   
 
 
 xiaoeryu  / 0评论  2019-06-28  
 
  
 
 
  从Java到区块链：如何成为区块链开发人员  
 
 
 
     最近这些天，区块链是每个开发人员的谈资。来自各个领域的许多软件开发商现在正试图进入区块链市场。我们与Mobilunity的区块链软件开发人员Eugene Kyselev 讨论了他是如何走出区块链开发方面的第一步的，希望对大家有所帮助。JAXenter：Eu   
 
 
 withjeffrey  / 0评论  2019-06-28  
 
  
 
 
  Hyperledger Fabric on SAP Cloud Platform  
 
 
 
     今天的文章来自Wen Aviva, 坐Jerry面对面的程序媛。因为Jerry和Aviva就在一个组，所以我的看法是，这些评价都实至名归。在她的帮助下，原型发布顺利完成。, 或许是想通过这种方式感谢Aviva对C4C团队做出的贡献。节点收到一个交易后，会根   
 
 
 加油码农  / 0评论  2019-06-28  
 
  
 
 
  Hyperledger(超级账本)的worldstate和SAP CRM的CRMD_CUMULAT_H  
 
 
 
     Hyperledger fabric是基于区块链技术的一个开源项目，由Linux基金会于2015年发起，目的是推进区块链数字技术和交易验证的发展和落地。Hyperledger由多个区块构成了一个有序链表，每个区块里包含多条交易。而Hyperledger F   
 
 
 willorfang的学习  / 0评论  2019-06-28  
 
  
 
 
  Hyperledger Fabric（构建你的第一个网络）  
 
 
 
     构建你的第一个网络这些说明已经过验证，可以与最新的稳定Docker镜像和提供的tar文件中预编译的安装实用程序一起工作，如果使用当前主分支中的镜像或工具运行这些命令，则可能会看到配置和紧急错误。构建你的第一个网络方案提供了一个包含两个组织的示例Hyperl   
 
 
 开发学习者  / 0评论  2019-06-28  
 
  
 
 
  Hyperledger Fabric（编写你的第一个应用程序）  
 
 
 
     编写第一个应用程序如果你还不熟悉Fabric网络的基本架构，则可能需要在继续之前访问“介绍”和“构建你的第一个网络”文档。在本节中，我们将介绍一些示例程序，以了解Fabric应用程序的工作原理，这些应用程序 - 统称为fabcar - 提供了Fabric功   
 
 
 永不停歇的脚步  / 0评论  2019-06-28  
 
  
 
 
  Hyperledger Fabric（术语表）  
 
 
 
     术语表术语很重要，以便所有Hyperledger Fabric用户和开发人员都同意每个特定术语的含义，例如，什么是智能合约。ACLACL或访问控制列表，将对特定对等点资源的访问权限关联到策略。ACL是通道配置的一部分，因此它存在于通道的配置块中，并可使用标   
 
 
 gaolong0  / 0评论  2019-06-28  
 
  
 
 
  Hyperledger Fabric（身份）  
 
 
 
     身份什么是身份？区块链网络中的不同参与者包括对等点、排序者、客户端应用程序，管理员等。这些参与者中的每一个 — 网络内部或外部能够使用服务的活动元素 — 都具有封装在X.509数字证书中的数字身份，这些身份确实很重要，因为它们确定了对资源的确切权限以及对参   
 
 
 永不停歇的脚步  / 0评论  2019-06-28  
 
  
 
 
  Hyperledger Fabric（功能）  
 
 
 
     Hyperledger Fabric功能Hyperledger Fabric是分布式分类账技术的一种实现，可在模块化区块链架构中提供企业级网络安全性，可扩展性，机密性和性能，Hyperledger Fabric提供以下区块链网络功能：。身份管理为了启用许可   
 
 
 yingheone  / 0评论  2019-06-28  
 
  
 
 
  Hyperledger Fabric（关键概念介绍）  
 
 
 
     介绍Hyperledger Fabric是分布式分类账解决方案的平台，采用模块化架构，提供高度机密性，弹性，灵活性和可扩展性，它旨在支持不同组件的可插拔实现，并适应整个经济生态系统中存在的错综复杂的事物和复杂性。我们建议首次使用的用户首先阅读下面的介绍，以   
 
 
 开发学习者  / 0评论  2019-06-28  
 
  
 
 
  Hyperledger Fabric（入门）  
 
 
 
     入门在我们开始之前，如果你还没有这样做，你可能希望检查是否已经在开发区块链应用程序和/或运行Hyperledger Fabric的平台上安装了所有前提条件。一旦安装了前提条件，就可以下载并安装HyperLedger Fabric了，当我们在Fabric二进   
 
 
 加油码农  / 0评论  2019-06-28  
 
  
 
 
  Hyperledger Fabric（介绍）  
 
 
 
     介绍一般而言，区块链是一个不可变的交易分类账，维护在一个分布式对等节点网络中。这些节点通过应用已经由共识协议验证的交易来维护分类帐的副本，该交易被分组为包括将每个块绑定到前一个块的散列的块中。区块链的第一个也是最广为人知的应用是比特币加密货币，尽管其他人也   
 
 
 IT男  / 0评论  2019-06-28  
 
  
 
 
  Hyperledger Fabric（目录）  
 
 
 
     企业区块链平台企业级许可的分布式分类账平台，为广泛的行业用例提供模块化和多功能性。介绍一般而言，区块链是一个不可变的交易分类账，维护在一个分布式对等节点网络中。这些节点通过应用已经由共识协议验证的交易来维护分类帐的副本，该交易被分组为包括将每个块绑定到前一   
 
 
 yingheone  / 0评论  2019-06-28  
 
  
 
 
  Hyperledger Fabric命令详解之 up  
 
 
 
     sudo ./byfn.sh upa@ubuntu:~/hyfa/fabric-samples/first-network$ sudo ./byfn.sh up> 创建网络，peer，orderer，cliStarting with channel    
 
 
 gaolong0  / 0评论  2019-06-28  
 
  
 
 
  Hyperledger Fabric 命令详解之 down  
 
 
 
     Stopping with channel 'mychannel' and CLI timeout of '10' seconds and CLI delay of '3' seconds   
 
 
 photoed  / 0评论  2019-06-28  
 
  
 
 
  Hyperledger Fabric 命令详解之“ generate ”  
 
 
 
     sudo ./byfn.sh -m generatea@ubuntu:~/hyfa/fabric-samples/first-network$ sudo ./byfn.sh -m generate. Generating certs and genesis   
 
 
 willorfang的学习  / 0评论  2019-06-28  
 
  
 
 
  Hyperledger Fabric周周记：Composer  
 
 
 
     在上周周记的结尾，我曾经说过本周要介绍Fabric的开发和应用。按照最开始的写作计划，我打算讲讲两种开发模式：直接使用Fabric API和利用Composer框架。可在通读完Composer的文档之后，我立即取消了原定计划，直接介绍Composer。选择   
 
 
 永不停歇的脚步  / 0评论  2019-06-27  
 
  
 
 
  基于ubuntu16.04快速构建Hyperledger Fabric网络  
 
 
 
     对于如何使用VMware安装虚拟机以及让虚拟机访问网络，网上有许多教程，这里就不重复讲了。当将系统安装完成后，需要更换源，使用desktop版的可以直接在设置里面选择最佳服务器,如下图所示若使用的是服务器版本,则可以使用如下命令换成高速的源   
 
 
 zfeifei  / 0评论  2019-06-27  
 
  
 
 
  Hyperledger Fabric周周记：起源  
 
 
 
     本着“以教带学，Learning by Doing”的想法，我于上周加入了Bob组织的HiBlock区块链技术布道群。这个群可不太好混，群规要求每个成员必需每周有输出，连续两次交白卷就要被踢出群。在这样的压力之下，我决定开一个新坑：区块链周周记，记录下每周   
 
 
 IT男  / 0评论  2019-06-27  
 
  
 
 
  HyperLedger Fabcar 学习笔记（基于超级账本编写第一个应用）  
 
 
 
     HyperLedger Fabcar 学习笔记翻译自：http://hyperledger-fabric.rea...首先设置一个开发环境学习一些简单的我们app将会用到的智能合约的参数开发一个app能够更新查询一个账本。enrollAdmin.js      
 
 
 网络连接世界  / 0评论  2019-06-27  
 
  
 
 
  Fabric学习笔记(八) - cli动态添加Org  
 
 
 
     Fabric学习笔记(八) - 动态添加org前置条件升级fabric至v1.1git checkout -b release-1.1   
 
 
 蜡笔小鑫爱看雪  / 0评论  2019-06-26  
 
  
 
 
  Fabric学习笔记(一) - Fabric v1.0.5安装笔记  
 
 
 
     安装软件1.基础软件安装yum install -y docker docker-compose libtool golang m42.建立GO语言环境vi ~/.bashrc增加以下行。sudo systemctl restart dockerdocke   
 
 
 永不停歇的脚步  / 0评论  2019-06-26  
 
  
 
 
  Hyperledger Fabric V0.7 跳坑玩耍【牛排】  
 
 
 
     最近有个项目需要用到超级账本的概念，随后在网上查阅相关的信息。最后相中了Fabric作为实验玩耍的目标。要玩就要玩最新的啦，所以舍弃了v0.6的版本，但是截至这篇文章摸出来，v1.0还处于alpha阶段。验证环境利用$ docker ps查看容器是否已经成   
 
 
 willorfang的学习  / 0评论  2019-06-21  
 
  
 
 
  用大白话解释区块链分类账本Hyperledger Fabric  
 
 
 
     最后一步，提交是采取goosip协议。上面的过程称为广播，Fabric的gossip系统使用这种策略来向所有对等体分发多种消息。在Fabric中，每个对等体定期广播一条消息，表示它仍处于活动状态并连接着网络。这允许对等体保持最新，即使它们错过了“活着”消息   
 
 
 doudou  / 0评论  2018-10-18  
 
  
 
 
  Hyperledger Fabric 开发环境搭建  
 
 
 
     Hyperledge fabric项目是IBM开源的区块链项目。Hyperledge fabric的开发环境是一个运行在vagrant里的Ubuntu映像，并在虚拟机内部运行了若干Docker容器。使用vagrant集成的开发环境开发允许开发者使用自己喜欢   
 
 
 chenjaulin  / 0评论  2016-10-24