docker-compose-files/hyperledger_fabric/latest/crypto-config.yaml

113 lines
4.4 KiB
YAML
Raw Normal View History

2017-09-01 20:09:18 +08:00
# Copyright IBM Corp. All Rights Reserved.
#
# SPDX-License-Identifier: Apache-2.0
#
# ---------------------------------------------------------------------------
# "OrdererOrgs" - Definition of organizations managing orderer nodes
# ---------------------------------------------------------------------------
OrdererOrgs:
# ---------------------------------------------------------------------------
# Orderer
# ---------------------------------------------------------------------------
- Name: Orderer
Domain: example.com
2018-09-10 14:22:00 +08:00
CA:
Country: US
Province: California
Locality: San Francisco
2018-10-12 11:33:24 +08:00
# Template:
# Count: 2
2017-09-01 20:09:18 +08:00
# ---------------------------------------------------------------------------
2019-04-01 16:21:22 +08:00
# "Specs" - See OrdererOrgs below for complete description
2017-09-01 20:09:18 +08:00
# ---------------------------------------------------------------------------
2018-10-12 11:33:24 +08:00
Specs:
- Hostname: orderer0
- Hostname: orderer1
2019-04-01 16:21:22 +08:00
- Hostname: orderer2
2019-12-28 09:43:08 +08:00
- Hostname: orderer3
2017-09-01 20:09:18 +08:00
# ---------------------------------------------------------------------------
# "PeerOrgs" - Definition of organizations managing peer nodes
# ---------------------------------------------------------------------------
PeerOrgs:
# ---------------------------------------------------------------------------
# Org1
# ---------------------------------------------------------------------------
- Name: Org1
Domain: org1.example.com
EnableNodeOUs: true
2018-09-10 14:22:00 +08:00
CA:
Country: US
Province: California
Locality: San Francisco
2017-09-01 20:09:18 +08:00
# ---------------------------------------------------------------------------
# "Specs"
# ---------------------------------------------------------------------------
# Uncomment this section to enable the explicit definition of hosts in your
# configuration. Most users will want to use Template, below
#
# Specs is an array of Spec entries. Each Spec entry consists of two fields:
# - Hostname: (Required) The desired hostname, sans the domain.
# - CommonName: (Optional) Specifies the template or explicit override for
# the CN. By default, this is the template:
#
# "{{.Hostname}}.{{.Domain}}"
#
# which obtains its values from the Spec.Hostname and
# Org.Domain, respectively.
# ---------------------------------------------------------------------------
# Specs:
# - Hostname: foo # implicitly "foo.org1.example.com"
# CommonName: foo27.org5.example.com # overrides Hostname-based FQDN set above
# - Hostname: bar
# - Hostname: baz
# ---------------------------------------------------------------------------
# "Template"
# ---------------------------------------------------------------------------
# Allows for the definition of 1 or more hosts that are created sequentially
# from a template. By default, this looks like "peer%d" from 0 to Count-1.
# You may override the number of nodes (Count), the starting index (Start)
# or the template used to construct the name (Hostname).
#
# Note: Template and Specs are not mutually exclusive. You may define both
# sections and the aggregate nodes will be created for you. Take care with
# name collisions
# ---------------------------------------------------------------------------
Template:
Count: 2
# Start: 5
# Hostname: {{.Prefix}}{{.Index}} # default
# ---------------------------------------------------------------------------
# "Users"
# ---------------------------------------------------------------------------
# Count: The number of user accounts _in addition_ to Admin
# ---------------------------------------------------------------------------
Users:
Count: 1
# ---------------------------------------------------------------------------
# Org2: See "Org1" for full specification
# ---------------------------------------------------------------------------
- Name: Org2
Domain: org2.example.com
EnableNodeOUs: true
2018-09-10 14:22:00 +08:00
CA:
Country: US
Province: California
Locality: San Francisco
2017-09-01 20:09:18 +08:00
Template:
Count: 2
Users:
Count: 1
2019-12-28 09:43:08 +08:00
- Name: Org3
Domain: org3.example.com
EnableNodeOUs: true
CA:
Country: US
Province: California
Locality: San Francisco
Template:
Count: 2
Users:
Count: 1