github.com/darrenli6/fabric-sdk-example@v0.0.0-20220109053535-94b13b56df8c/imocc/deploy/crypto-config.yaml (about) 1 # Copyright IBM Corp. All Rights Reserved. 2 # 3 # SPDX-License-Identifier: Apache-2.0 4 # 5 6 # --------------------------------------------------------------------------- 7 # "OrdererOrgs" - Definition of organizations managing orderer nodes 8 # "OrdererOrgs" - 定义管理排序节点的组织 9 # --------------------------------------------------------------------------- 10 OrdererOrgs: 11 # --------------------------------------------------------------------------- 12 # Orderer 13 # --------------------------------------------------------------------------- 14 - Name: Orderer # 组织的名字 15 Domain: imocc.com # 域名 16 Specs: # 定义组织的节点信息 17 - Hostname: orderer # 单个orderer(solo),节点域名:orderer.imocc.com 18 # - Hostname: orderer1 19 # --------------------------------------------------------------------------- 20 # "PeerOrgs" - Definition of organizations managing peer nodes 21 # "PeerOrgs" - 定义管理peer节点的组织 22 # --------------------------------------------------------------------------- 23 PeerOrgs: 24 # --------------------------------------------------------------------------- 25 # Org0 组织0 26 # --------------------------------------------------------------------------- 27 - Name: Org0 28 Domain: org0.imocc.com 29 # --------------------------------------------------------------------------- 30 # "Specs" 31 # --------------------------------------------------------------------------- 32 # Uncomment this section to enable the explicit definition of hosts in your 33 # configuration. Most users will want to use Template, below 34 # 35 # Specs is an array of Spec entries. Each Spec entry consists of two fields: 36 # - Hostname: (Required) The desired hostname, sans the domain. 37 # - CommonName: (Optional) Specifies the template or explicit override for 38 # the CN. By default, this is the template: 39 # 40 # "{{.Hostname}}.{{.Domain}}" 41 # 42 # which obtains its values from the Spec.Hostname and 43 # Org.Domain, respectively. 44 # --------------------------------------------------------------------------- 45 # Specs: 46 # - Hostname: foo # implicitly "foo.org1.example.com" 47 # CommonName: foo27.org5.example.com # overrides Hostname-based FQDN set above 48 # - Hostname: bar 49 # - Hostname: baz 50 # --------------------------------------------------------------------------- 51 # "Template" 52 # --------------------------------------------------------------------------- 53 # Allows for the definition of 1 or more hosts that are created sequentially 54 # from a template. By default, this looks like "peer%d" from 0 to Count-1. 55 # You may override the number of nodes (Count), the starting index (Start) 56 # or the template used to construct the name (Hostname). 57 # 58 # Note: Template and Specs are not mutually exclusive. You may define both 59 # sections and the aggregate nodes will be created for you. Take care with 60 # name collisions 61 # --------------------------------------------------------------------------- 62 Template: # 使用模板定义peer节点 63 Count: 2 # peer0.org0.imocc.com & peer1.org0.imocc.com 64 # Start: 5 index计数的起始 65 # Hostname: {{.Prefix}}{{.Index}} # default 66 # --------------------------------------------------------------------------- 67 # "Users" 68 # --------------------------------------------------------------------------- 69 # Count: The number of user accounts _in addition_ to Admin 70 # --------------------------------------------------------------------------- 71 Users: # 组织的用户信息 72 Count: 2 # Admin & User1 & User2 73 # --------------------------------------------------------------------------- 74 # Org1 组织1 75 # --------------------------------------------------------------------------- 76 - Name: Org1 77 Domain: org1.imocc.com 78 Specs: 79 - Hostname: peer0 80 #CommonName: cpeer0.org1.imocc.com 81 - Hostname: peer1 82 Template: 83 Count: 1 84 Start: 2 85 Users: 86 Count: 3 # Admin & User1 & User2 & User3