Capability Requirements 能力需求 ———————–

Because Fabric is a distributed system that will usually involve multiple organizations (sometimes in different countries or even continents), it is possible (and typical) that many different versions of Fabric code will exist in the network. Nevertheless, it’s vital that networks process transactions in the same way so that everyone has the same view of the current network state.

由于Fabric是一个分布式系统,通常会涉及多个组织(有时在不同的国家甚至大洲),所以网络中可能(而且是典型的)存在许多不同版本的Fabric代码。然而,重要的是,网络以相同的方式处理交易,这样每个人对当前网络状态都有相同的看法。

This means that every network – and every channel within that network – must define a set of what we call “capabilities” to be able to participate in processing transactions. For example, Fabric v1.1 introduces new MSP role types of “Peer” and “Client”. However, if a v1.0 peer does not understand these new role types, it will not be able to appropriately evaluate an endorsement policy that references them. This means that before the new role types may be used, the network must agree to enable the v1.1 channel capability requirement, ensuring that all peers come to the same decision.

这意味着每个网络,以及该网络中的每个通道,必须定义一组我们称为“功能”的东西,以便能够参与处理交易。例如,Fabric v1.1引入了新的MSP角色类型“Peer”和“Client”。但是,如果1.0版本的节点不理解这些新角色类型,那么它将无法恰当地验证引用它们的背书策略。这意味着在使用新角色类型之前,网络必须同意启用v1.1的“通道”功能需求,确保所有节点都做出相同的决定。

Only binaries which support the required capabilities will be able to participate in the channel, and newer binary versions will not enable new validation logic until the corresponding capability is enabled. In this way, capability requirements ensure that even with disparate builds and versions, it is not possible for the network to suffer a state fork.

只有支持所需功能的二进制文件才能参与通道,较新的二进制版本在启用相应功能之前不会启用新的验证逻辑。通过这种方式,功能需求确保即使使用不同的构建和版本,网络也不可能出现状态分支。

Defining Capability Requirements 定义功能需求 ================================

Capability requirements are defined per channel in the channel configuration (found in the channel’s most recent configuration block). The channel configuration contains three locations, each of which defines a capability of a different type.

功能需求是在通道配置中为每个通道定义的(可以在通道的最新配置区块中找到)。通道配置包含三个位置,每个位置定义了一个不同类型的功能。

Capability Type Canonical Path JSON Path
Channel /Channel/Capabilities .channel_group.values.Capabilities
Orderer /Channel/Orderer/Capabilities .channel_group.groups.Orderer.values.Capabilities
Application /Channel/Application/Capabilities .channel_group.groups.Application.values. Capabilities
  • Channel: these capabilities apply to both peer and orderers and are located in the root Channel group.
  • Orderer: apply to orderers only and are located in the Orderer group.
  • Application: apply to peers only and are located in the Application group.
  • **通道:**这些能力适用于Peer和orders,并且位于根 通道 组中。
  • **排序节点:**仅适用于orders,并且位于 Orderer 组中。
  • **应用程序:**仅适用于peers,并且位于 Application 组中。

The capabilities are broken into these groups in order to align with the existing administrative structure. Updating orderer capabilities is something the ordering orgs would manage independent of the application orgs. Similarly, updating application capabilities is something only the application admins would manage. By splitting the capabilities between “Orderer” and “Application”, a hypothetical network could run a v1.6 ordering service while supporting a v1.3 peer application network.

为了与现有的管理结构保持一致,这些能力被分解到这些组中。更新orderer能力是ordering组织自己的事,独立与application orgs。 类似的,更新application能力只是application管理员的事情, 与ordering无关。 通过将“Orderer”和“Application”之间的能力分离,假设一个网络可以运行在v1.6的ordering service, 同时又支持运行在v1.3的peer网络。

However, some capabilities cross both the ‘Application’ and ‘Orderer’ groups. As we saw earlier, adding a new MSP role type is something both the orderer and application admins agree to and need to recognize. The orderer must understand the meaning of MSP roles in order to allow the transactions to pass through ordering, while the peers must understand the roles in order to validate the transaction. These kinds of capabilities – which span both the application and orderer components – are defined in the top level “Channel” group.

然而,有些能力跨越了“Application”和“Orderer”组。正如我们前面看到的,添加新的MSP角色类型是orderer管理员和application管理员都同意并且需要认识到的。 orderer必须理解MSP角色的含义,以便允许事务通过排序,而peers必须理解角色,以便验证事务。 这种能力 – 它跨越了applitaion和orderer组件 – 在顶层“Channel”组中定义。

注解

It is possible that the channel capabilities are defined to be at version v1.3 while the orderer and application capabilities are defined to be at version 1.1 and v1.4, respectively. Enabling a capability at the “Channel” group level does not imply that this same capability is available at the more specific “Orderer” and “Application” group levels.

注解

channel能力可能被定义为v1.3版本,而orderer和application分别被定义为1.1版本和v1.4版本。 在“Channel”组级别启用能力并不意味着在特定的“Orderer”和“Application”组级别可以使用相同的能力。

Setting Capabilities 设置能力 ====================

Capabilities are set as part of the channel configuration (either as part of the initial configuration – which we’ll talk about in a moment – or as part of a reconfiguration).

能力被设置为通道配置的一部分(或者作为初始配置的一部分(我们将稍后讨论),或者作为重新配置的一部分)。

注解

We have a two documents that talk through different aspects of channel reconfigurations. First, we have a tutorial that will take you through the process of 向通道添加组织. And we also have a document that talks through 更新通道配置 which gives an overview of the different kinds of updates that are possible as well as a fuller look at the signature process.

注解

我们有两个文档讨论了通道重新配置的不同方面。首先,我们有一个教程,为您演示 向通道添加组织 。我们也有另一个文档,讨论了如何 更新通道配置, 它给出了各种更新的概述以及对签名过程的更全面的了解 Updating a Channel Configuration 。

Because new channels copy the configuration of the Orderer System Channel by default, new channels will automatically be configured to work with the orderer and channel capabilities of the Orderer System Channel and the application capabilities specified by the channel creation transaction. Channels that already exist, however, must be reconfigured.

因为在默认情况下,新通道会复制Orderer系统通道的配置,因此在新通道创建时会使用和Orderer系统通道 一样的Orderer和channel能力,以及application能力自动配置新通道。 然而,已经存在的通道必须重新配置。

The schema for the Capabilities value is defined in the protobuf as:

Capabilities在protobuf中定于的结构如下:

message Capabilities {
      map<string, Capability> capabilities = 1;
}

message Capability { }

As an example, rendered in JSON:

用JSON格式举例:

{
    "capabilities": {
        "V1_1": {}
    }
}

Capabilities in an Initial Configuration 初始化配置中的Capabilities ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

In the configtx.yaml file distributed in the config directory of the release artifacts, there is a Capabilities section which enumerates the possible capabilities for each capability type (Channel, Orderer, and Application).

Fabric源代码 config 路径下的 configtx.yaml 文件中, 在 Capabilities 部分列举了每种能力类型 (Channel, Orderer, and Application)。

The simplest way to enable capabilities is to pick a v1.1 sample profile and customize it for your network. For example:

启用能力的最简单方法是选择一个v1.1示例概要文件并为您的网络定制它。例如:

SampleSingleMSPSoloV1_1:
    Capabilities:
        <<: *GlobalCapabilities
    Orderer:
        <<: *OrdererDefaults
        Organizations:
            - *SampleOrg
        Capabilities:
            <<: *OrdererCapabilities
    Consortiums:
        SampleConsortium:
            Organizations:
                - *SampleOrg

Note that there is a Capabilities section defined at the root level (for the channel capabilities), and at the Orderer level (for orderer capabilities). The sample above uses a YAML reference to include the capabilities as defined at the bottom of the YAML.

注意,在根级别(用于channel capabilities)和在Orderer级别(用于Orderer能力)定义了一个 Capabilities 部分。 上面的示例使用YAML引用的方式将定义在文件底部的capabilities部分包含进来。

When defining the orderer system channel there is no Application section, as those capabilities are defined during the creation of an application channel. To define a new channel’s application capabilities at channel creation time, the application admins should model their channel creation transaction after the SampleSingleMSPChannelV1_1 profile.

在定义orderer系统通道时,不存在Application部分,因为这些能力是在创建application通道时定义的。 要在通道创建时定义新通道的application能力,application管理员应该在 SampleSingleMSPChannelV1_1 中对其通道创建事务建模。

SampleSingleMSPChannelV1_1:
     Consortium: SampleConsortium
     Application:
         Organizations:
             - *SampleOrg
         Capabilities:
             <<: *ApplicationCapabilities

Here, the Application section has a new element Capabilities which references the ApplicationCapabilities section defined at the end of the YAML.

Applicatoin部分的 Capabilities 元素引用了定义在YAML文件底部的 ApplicationCapabilities 部分。

注解

The capabilities for the Channel and Orderer sections are inherited from the definition in the ordering system channel and are automatically included by the orderer during the process of channel creation.

注解

应用通道中的Channel和Orderer capabilities继承自ordering系统通道中的定义,在创建通道的时候被自动包含进来。