github.com/leonlxy/hyperledger@v1.0.0-alpha.0.20170427033203-34922035d248/examples/dchackfest/samples/e2e/crypto-config.yaml (about) 1 # --------------------------------------------------------------------------- 2 # "OrdererOrgs" - Definition of organizations managing orderer nodes 3 # --------------------------------------------------------------------------- 4 OrdererOrgs: 5 # --------------------------------------------------------------------------- 6 # Orderer 7 # --------------------------------------------------------------------------- 8 - Name: Orderer 9 Domain: example.com 10 # --------------------------------------------------------------------------- 11 # "Specs" - See PeerOrgs below for complete description 12 # --------------------------------------------------------------------------- 13 Specs: 14 - Hostname: orderer 15 # --------------------------------------------------------------------------- 16 # "PeerOrgs" - Definition of organizations managing peer nodes 17 # --------------------------------------------------------------------------- 18 PeerOrgs: 19 # --------------------------------------------------------------------------- 20 # Org1 21 # --------------------------------------------------------------------------- 22 - Name: Org1 23 Domain: org1.example.com 24 # --------------------------------------------------------------------------- 25 # "Specs" 26 # --------------------------------------------------------------------------- 27 # Uncomment this section to enable the explicit definition of hosts in your 28 # configuration. Most users will want to use Template, below 29 # 30 # Specs is an array of Spec entries. Each Spec entry consists of two fields: 31 # - Hostname: (Required) The desired hostname, sans the domain. 32 # - CommonName: (Optional) Specifies the template or explicit override for 33 # the CN. By default, this is the template: 34 # 35 # "{{.Hostname}}.{{.Domain}}" 36 # 37 # which obtains its values from the Spec.Hostname and 38 # Org.Domain, respectively. 39 # --------------------------------------------------------------------------- 40 # Specs: 41 # - Hostname: foo # implicitly "foo.org1.example.com" 42 # CommonName: foo27.org5.example.com # overrides Hostname-based FQDN set above 43 # - Hostname: bar 44 # - Hostname: baz 45 # --------------------------------------------------------------------------- 46 # "Template" 47 # --------------------------------------------------------------------------- 48 # Allows for the definition of 1 or more hosts that are created sequentially 49 # from a template. By default, this looks like "peer%d" from 0 to Count-1. 50 # You may override the number of nodes (Count), the starting index (Start) 51 # or the template used to construct the name (Hostname). 52 # 53 # Note: Template and Specs are not mutually exclusive. You may define both 54 # sections and the aggregate nodes will be created for you. Take care with 55 # name collisions 56 # --------------------------------------------------------------------------- 57 Template: 58 Count: 2 59 # Start: 5 60 # Hostname: {{.Prefix}}{{.Index}} # default 61 # --------------------------------------------------------------------------- 62 # "Users" 63 # --------------------------------------------------------------------------- 64 # Count: The number of user accounts _in addition_ to Admin 65 # --------------------------------------------------------------------------- 66 Users: 67 Count: 1 68 # --------------------------------------------------------------------------- 69 # Org2: See "Org1" for full specification 70 # --------------------------------------------------------------------------- 71 - Name: Org2 72 Domain: org2.example.com 73 Template: 74 Count: 2 75 Users: 76 Count: 1