configtx.yaml中文注解

configtx.yaml是Hyperledger Fabric区块链网络运维工具configtxgen用于生成通道创世块或通道交易的配置文件&＃xff0c;configtx.yaml的内容直接决定了所生成的创世区块的内容。本文将给出configtx.yaml的详细中文说明。

如果需要快速掌握Fabric区块链的链码与应用开发&＃xff0c;推荐访问汇智网的在线互动教程&＃xff1a;

• Fabric区块链Java开发详解
• Fabric区块链NodeJS开发详解

Capabilities / 通道能力配置

Capabilities段用来定义fabric网络的能力。这是版本v1.0.0引入的一个新的配置段&＃xff0c;当与版本v1.0.x的对等节点与排序节点混合组网时不可使用。

Capabilities段定义了fabric程序要加入网络所必须支持的特性。例如&＃xff0c;如果添加了一个新的MSP类型&＃xff0c;那么更新的程序可能会根据该类型识别并验证签名&＃xff0c;但是老版本的程序就没有办法验证这些交易。这可能导致不同版本的fabric程序中维护的世界状态不一致。

因此&＃xff0c;通过定义通道的能力&＃xff0c;就明确了不满足该能力要求的fabric程序&＃xff0c;将无法处理交易&＃xff0c;除非升级到新的版本。对于v1.0.x的程序而言&＃xff0c;如果在Capabilities段定义了任何能力&＃xff0c;即使声明不需要支持这些能力&＃xff0c;都会导致其有意崩溃。

Capabilities:# Global配置同时应用于排序节点和对等节点&＃xff0c;并且必须被两种节点同时支持。# 将该配置项设置为ture表明要求节点具备该能力Global: &ChannelCapabilitiesV1_3: true# Orderer配置仅应用于排序节点&＃xff0c;不需考虑对等节点的升级。将该配置项# 设置为true表明要求排序节点具备该能力Orderer: &OrdererCapabilitiesV1_1: true# Application配置仅应用于对等网络&＃xff0c;不需考虑排序节点的升级。将该配置项# 设置为true表明要求对等节点具备该能力Application: &ApplicationCapabilitiesV1_3: true


Organizations / 组织机构配置

Organizations配置段用来定义组织机构实体&＃xff0c;以便在后续配置中引用。例如&＃xff0c;下面的配置文件中&＃xff0c;定义了三个机构&＃xff0c;可以分别使用ExampleCom、Org1ExampleCom和Org2ExampleCom引用其配置&＃xff1a;

Organizations:- &ExampleComName: ExampleComID: example.comAdminPrincipal: Role.ADMINMSPDir: ./ordererOrganizations/example.com/mspPolicies:Readers:Type: SignatureRule: OR(&＃39;example.com.member&＃39;)Writers:Type: SignatureRule: OR(&＃39;example.com.member&＃39;)Admins:Type: SignatureRule: OR(&＃39;example.com.admin&＃39;)Endorsement:Type: SignatureRule: OR(&＃39;example.com.member&＃39;)- &Org1ExampleComName: Org1ExampleComID: org1.example.comMSPDir: ./peerOrganizations/org1.example.com/mspAdminPrincipal: Role.ADMINAnchorPeers:- Host: peer0.org1.example.comPort: 7051Policies:Readers:Type: SignatureRule: OR(&＃39;org1.example.com.member&＃39;)Writers:Type: SignatureRule: OR(&＃39;org1.example.com.member&＃39;)Admins:Type: SignatureRule: OR(&＃39;org1.example.com.admin&＃39;)Endorsement:Type: SignatureRule: OR(&＃39;org1.example.com.member&＃39;)- &Org2ExampleComName: Org2ExampleComID: org2.example.comMSPDir: ./peerOrganizations/org2.example.com/mspAdminPrincipal: Role.ADMINAnchorPeers:- Host: peer0.org2.example.comPort: 7051Policies:Readers:Type: SignatureRule: OR(&＃39;org2.example.com.member&＃39;)Writers:Type: SignatureRule: OR(&＃39;org2.example.com.member&＃39;)Admins:Type: SignatureRule: OR(&＃39;org2.example.com.admin&＃39;)Endorsement:Type: SignatureRule: OR(&＃39;org2.example.com.member&＃39;)


Orderer / 排序节点配置

Orderer配置段用来定义要编码写入创世区块或通道交易的排序节点参数。

Orderer: &OrdererDefaults# 排序节点类型用来指定要启用的排序节点实现&＃xff0c;不同的实现对应不同的共识算法。# 目前可用的类型为&＃xff1a;solo和kafkaOrdererType: soloAddresses:- orderer0.example.com:7050BatchTimeout: 2sBatchSize:MaxMessageCount: 10AbsoluteMaxBytes: 98 MBPreferredMaxBytes: 512 KBMaxChannels: 0Kafka:Brokers:- kafka0:9092- kafka1:9092- kafka2:9092- kafka3:9092Organizations:# 定义本层级的排序节点策略&＃xff0c;其权威路径为 /Channel/Orderer/Policies:Readers:Type: ImplicitMetaRule: ANY ReadersWriters:Type: ImplicitMetaRule: ANY WritersAdmins:Type: ImplicitMetaRule: MAJORITY Admins# BlockValidation配置项指定了哪些签名必须包含在区块中&＃xff0c;以便对等节点进行验证BlockValidation:Type: ImplicitMetaRule: ANY Writers# Capabilities配置描述排序节点层级的能力需求&＃xff0c;这里直接引用# 前面Capabilities配置段中的OrdererCapabilities配置项Capabilities:<<: *OrdererCapabilities


Channel / 通道配置

Channel配置段用来定义要写入创世区块或配置交易的通道参数。

Channel: &ChannelDefaults# 定义本层级的通道访问策略&＃xff0c;其权威路径为 /Channel/Policies:Readers:Type: ImplicitMetaRule: ANY Readers# Writes策略定义了调用Broadcast API提交交易的许可规则Writers:Type: ImplicitMetaRule: ANY Writers# Admin策略定义了修改本层级配置的许可规则Admins:Type: ImplicitMetaRule: MAJORITY Admins# Capabilities配置描通道层级的能力需求&＃xff0c;这里直接引用# 前面Capabilities配置段中的ChannelCapabilities配置项Capabilities:<<: *ChannelCapabilities


Application / 应用配置

Application配置段用来定义要写入创世区块或配置交易的应用参数。

Application: &ApplicationDefaultsACLs: &ACLsDefault# ACLs配置段为系统中各种资源提供默认的策略。# 这里所说的“资源”&＃xff0c;可以是系统链码的函数&＃xff0c;例如qscc系统链码的GetBlockByNumber方法# 也可以是其他资源&＃xff0c;例如谁可以接收区块事件。# 这个配置段不是用来定义资源或API&＃xff0c;而仅仅是定义资源的访问控制策略# # 用户可以在通道定义中重写这些默认策略#---New Lifecycle System Chaincode (_lifecycle) function to policy mapping for access control--## _lifecycle系统链码CommitChaincodeDefinition函数的ACL定义_lifecycle/CommitChaincodeDefinition: /Channel/Application/Writers# _lifecycle系统链码的QueryChaincodeDefinition函数的ACL定义_lifecycle/QueryChaincodeDefinition: /Channel/Application/Readers# _lifecycle系统链码的QueryNamespaceDefinitions函数的ACL定义_lifecycle/QueryNamespaceDefinitions: /Channel/Application/Readers#---Lifecycle System Chaincode (lscc) function to policy mapping for access control---## lscc系统链码的getid函数的ACL定义lscc/ChaincodeExists: /Channel/Application/Readers# lscc系统链码的getdepspec函数的ACL定义lscc/GetDeploymentSpec: /Channel/Application/Readers# lscc系统链码的getccdata函数的ACL定义lscc/GetChaincodeData: /Channel/Application/Readers# lscc系统链码的getchaincodes函数的ACL定义lscc/GetInstantiatedChaincodes: /Channel/Application/Readers#---Query System Chaincode (qscc) function to policy mapping for access control---## qscc系统链码的GetChainInfo函数的ACL定义qscc/GetChainInfo: /Channel/Application/Readers# qscc系统链码的GetBlockByNumber函数的ACL定义qscc/GetBlockByNumber: /Channel/Application/Readers# qscc系统 链码的GetBlockByHash函数的ACL定义qscc/GetBlockByHash: /Channel/Application/Readers# qscc系统链码的GetTransactionByID函数的ACL定义qscc/GetTransactionByID: /Channel/Application/Readers# qscc系统链码GetBlockByTxID函数的ACL定义qscc/GetBlockByTxID: /Channel/Application/Readers#---Configuration System Chaincode (cscc) function to policy mapping for access control---## cscc系统链码的GetConfigBlock函数的ACl定义cscc/GetConfigBlock: /Channel/Application/Readers# cscc系统链码的GetConfigTree函数的ACL定义cscc/GetConfigTree: /Channel/Application/Readers# cscc系统链码的SimulateConfigTreeUpdate函数的ACL定义cscc/SimulateConfigTreeUpdate: /Channel/Application/Readers#---Miscellanesous peer function to policy mapping for access control---## 访问对等节点上的链码的ACL策略定义peer/Propose: /Channel/Application/Writers# 从链码中访问其他链码的ACL策略定义peer/ChaincodeToChaincode: /Channel/Application/Readers#---Events resource to policy mapping for access control###---## 发送区块事件的ACL策略定义event/Block: /Channel/Application/Readers# 发送过滤的区块事件的ACL策略定义event/FilteredBlock: /Channel/Application/Readers# Organizations配置列出参与到网络中的机构清单Organizations:# 定义本层级的应用控制策略&＃xff0c;其权威路径为 /Channel/Application/Policies: &ApplicationDefaultPoliciesReaders:Type: ImplicitMetaRule: "ANY Readers"Writers:Type: ImplicitMetaRule: "ANY Writers"Admins:Type: ImplicitMetaRule: "MAJORITY Admins"LifecycleEndorsement:Type: ImplicitMetaRule: "ANY Endorsement"Endorsement:Type: ImplicitMetaRule: "ANY Endorsement"# Capabilities配置描述应用层级的能力需求&＃xff0c;这里直接引用# 前面Capabilities配置段中的ApplicationCapabilities配置项Capabilities:<<: *ApplicationCapabilities


Profiles / 配置入口

Profiles配置段用来定义用于configtxgen工具的配置入口。包含委员会&＃xff08;consortium&＃xff09;的配置入口可以用来生成排序节点的创世区块。如果在排序节点的创世区块中正确定义了consortium的成员&＃xff0c;那么可以仅使用机构成员名称和委员会的名称来生成通道创建请求。

Profiles:# SampleInsecureSolo定义了一个使用Solo排序节点的简单配置SampleInsecureSolo:<<: *ChannelDefaultsOrderer:<<: *OrdererDefaultsOrganizations:- *ExampleComCapabilities:<<: *OrdererCapabilitiesApplication:<<: *ApplicationDefaultsOrganizations:- *ExampleComCapabilities:<<: *ApplicationCapabilitiesPolicies:Readers:Type: ImplicitMetaRule: ANY ReadersWriters:Type: ImplicitMetaRule: ANY WritersAdmins:Type: ImplicitMetaRule: MAJORITY AdminsLifecycleEndorsement:Type: ImplicitMetaRule: ANY EndorsementEndorsement:Type: ImplicitMetaRule: ANY EndorsementConsortiums:SampleConsortium:Organizations:- *Org1ExampleCom- *Org2ExampleCom# SampleInsecureKafka定义了一个使用Kfaka排序节点的配置SampleInsecureKafka:<<: *ChannelDefaultsOrderer:<<: *OrdererDefaultsOrdererType: kafkaAddresses:- orderer0.example.com:7050- orderer1.example.com:7050- orderer2.example.com:7050Organizations:- *ExampleComCapabilities:<<: *OrdererCapabilitiesApplication:<<: *ApplicationDefaultsOrganizations:- *ExampleComCapabilities:<<: *ApplicationCapabilitiesPolicies:Readers:Type: ImplicitMetaRule: ANY ReadersWriters:Type: ImplicitMetaRule: ANY WritersAdmins:Type: ImplicitMetaRule: MAJORITY AdminsLifecycleEndorsement:Type: ImplicitMetaRule: ANY EndorsementEndorsement:Type: ImplicitMetaRule: ANY EndorsementConsortiums:SampleConsortium:Organizations:- *ExampleCom- *Org1ExampleCom- *Org2ExampleCom# SampleSingleMSPSolo定义了一个使用Solo排序节点、包含单一MSP的配置SampleSingleMSPSolo:Orderer:<<: *OrdererDefaultsOrganizations:- *ExampleComCapabilities:<<: *OrdererCapabilitiesApplication:<<: *ApplicationDefaultsOrganizations:- *ExampleComCapabilities:<<: *ApplicationCapabilitiesPolicies:Readers:Type: ImplicitMetaRule: ANY ReadersWriters:Type: ImplicitMetaRule: ANY WritersAdmins:Type: ImplicitMetaRule: MAJORITY AdminsLifecycleEndorsement:Type: ImplicitMetaRule: ANY EndorsementEndorsement:Type: ImplicitMetaRule: ANY EndorsementConsortiums:SampleConsortium:Organizations:- *ExampleCom- *Org1ExampleCom- *Org2ExampleCom# SampleEmptyInsecureChannel定义了一个不包含成员与访问控制策略的通道SampleEmptyInsecureChannel:Capabilities:<<: *ChannelCapabilitiesConsortium: SampleConsortiumApplication:Organizations:- *ExampleComCapabilities:<<: *ApplicationCapabilitiesPolicies:Readers:Type: ImplicitMetaRule: ANY ReadersWriters:Type: ImplicitMetaRule: ANY WritersAdmins:Type: ImplicitMetaRule: MAJORITY AdminsLifecycleEndorsement:Type: ImplicitMetaRule: ANY EndorsementEndorsement:Type: ImplicitMetaRule: ANY Endorsement# SysTestChannel定义了一个用于测试的通道SysTestChannel:<<: *ChannelDefaultsCapabilities:<<: *ChannelCapabilitiesConsortium: SampleConsortiumApplication:<<: *ApplicationDefaultsOrganizations:- *Org1ExampleCom- *Org2ExampleComCapabilities:<<: *ApplicationCapabilitiesPolicies:Readers:Type: ImplicitMetaRule: ANY ReadersWriters:Type: ImplicitMetaRule: ANY WritersAdmins:Type: ImplicitMetaRule: MAJORITY AdminsLifecycleEndorsement:Type: ImplicitMetaRule: ANY EndorsementEndorsement:Type: ImplicitMetaRule: ANY Endorsement# SampleSingleMSPChannel定义了一个仅包含单一成员机构的通道。# 该配置通常与SampleSingleMSPSolo或SampleSingleMSPKafka同时使用SampleSingleMSPChannel:<<: *ChannelDefaultsCapabilities:<<: *ChannelCapabilitiesConsortium: SampleConsortiumApplication:<<: *ApplicationDefaultsOrganizations:- *Org1ExampleCom- *Org2ExampleComCapabilities:<<: *ApplicationCapabilitiesPolicies:Readers:Type: ImplicitMetaRule: ANY ReadersWriters:Type: ImplicitMetaRule: ANY WritersAdmins:Type: ImplicitMetaRule: MAJORITY AdminsLifecycleEndorsement:Type: ImplicitMetaRule: ANY EndorsementEndorsement:Type: ImplicitMetaRule: ANY Endorsement


原文链接&＃xff1a;configtx.yaml中文详解 — 汇智网