crypto-config.yaml 4.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293
  1. # Copyright IBM Corp. All Rights Reserved.
  2. #
  3. # SPDX-License-Identifier: Apache-2.0
  4. #
  5. # ---------------------------------------------------------------------------
  6. # "OrdererOrgs" - Definition of organizations managing orderer nodes
  7. # ---------------------------------------------------------------------------
  8. OrdererOrgs:
  9. # ---------------------------------------------------------------------------
  10. # Orderer
  11. # ---------------------------------------------------------------------------
  12. - Name: Orderer
  13. Domain: example.com
  14. CA:
  15. Country: US
  16. Province: California
  17. Locality: San Francisco
  18. # ---------------------------------------------------------------------------
  19. # "Specs" - See PeerOrgs below for complete description
  20. # ---------------------------------------------------------------------------
  21. Specs:
  22. - Hostname: orderer
  23. # ---------------------------------------------------------------------------
  24. # "PeerOrgs" - Definition of organizations managing peer nodes
  25. # ---------------------------------------------------------------------------
  26. PeerOrgs:
  27. # ---------------------------------------------------------------------------
  28. # Org1
  29. # ---------------------------------------------------------------------------
  30. - Name: Org1
  31. Domain: org1.example.com
  32. CA:
  33. Country: US
  34. Province: California
  35. Locality: San Francisco
  36. # ---------------------------------------------------------------------------
  37. # "Specs"
  38. # ---------------------------------------------------------------------------
  39. # Uncomment this section to enable the explicit definition of hosts in your
  40. # configuration. Most users will want to use Template, below
  41. #
  42. # Specs is an array of Spec entries. Each Spec entry consists of two fields:
  43. # - Hostname: (Required) The desired hostname, sans the domain.
  44. # - CommonName: (Optional) Specifies the template or explicit override for
  45. # the CN. By default, this is the template:
  46. #
  47. # "{{.Hostname}}.{{.Domain}}"
  48. #
  49. # which obtains its values from the Spec.Hostname and
  50. # Org.Domain, respectively.
  51. # ---------------------------------------------------------------------------
  52. # Specs:
  53. # - Hostname: foo # implicitly "foo.org1.example.com"
  54. # CommonName: foo27.org5.example.com # overrides Hostname-based FQDN set above
  55. # - Hostname: bar
  56. # - Hostname: baz
  57. # ---------------------------------------------------------------------------
  58. # "Template"
  59. # ---------------------------------------------------------------------------
  60. # Allows for the definition of 1 or more hosts that are created sequentially
  61. # from a template. By default, this looks like "peer%d" from 0 to Count-1.
  62. # You may override the number of nodes (Count), the starting index (Start)
  63. # or the template used to construct the name (Hostname).
  64. #
  65. # Note: Template and Specs are not mutually exclusive. You may define both
  66. # sections and the aggregate nodes will be created for you. Take care with
  67. # name collisions
  68. # ---------------------------------------------------------------------------
  69. Template:
  70. Count: 2
  71. # Start: 5
  72. # Hostname: {{.Prefix}}{{.Index}} # default
  73. # ---------------------------------------------------------------------------
  74. # "Users"
  75. # ---------------------------------------------------------------------------
  76. # Count: The number of user accounts _in addition_ to Admin
  77. # ---------------------------------------------------------------------------
  78. Users:
  79. Count: 1
  80. # ---------------------------------------------------------------------------
  81. # Org2: See "Org1" for full specification
  82. # ---------------------------------------------------------------------------
  83. - Name: Org2
  84. Domain: org2.example.com
  85. CA:
  86. Country: US
  87. Province: California
  88. Locality: San Francisco
  89. Template:
  90. Count: 2
  91. Users:
  92. Count: 1