github.com/defanghe/fabric@v2.1.1+incompatible/internal/peer/chaincode/testdata/connectionprofile.yaml (about)

     1  name: connection-profile
     2  
     3  #
     4  # Any properties with an "x-" prefix will be treated as application-specific, exactly like how naming
     5  # in HTTP headers or swagger properties work. The SDK will simply ignore these fields and leave
     6  # them for the applications to process. This is a mechanism for different components of an application
     7  # to exchange information that are not part of the standard schema described below. In particular,
     8  # the "x-type" property with the "hlfv1" value example below is used by Hyperledger Composer to
     9  # determine the type of Fabric networks (v0.6 vs. v1.0) it needs to work with.
    10  #
    11  x-type: "hlfv1"
    12  x-loggingLevel: info
    13  
    14  #
    15  # Describe what the target network is/does.
    16  #
    17  description: "The network to be in if you want to stay in the global trade business"
    18  
    19  #
    20  # Schema version of the content. Used by the SDK to apply the corresponding parsing rules.
    21  #
    22  version: 1.2.0
    23  
    24  #
    25  # [Optional]. But most apps would have this section so that channel objects can be constructed
    26  # based on the content below. If an app is creating channels, then it likely will not need this
    27  # section.
    28  #
    29  channels:
    30    # name of the channel
    31    mychannel:
    32      # Required. list of orderers designated by the application to use for transactions on this
    33      # channel. This list can be a result of access control ("org1" can only access "ordererA"), or
    34      # operational decisions to share loads from applications among the orderers.  The values must
    35      # be "names" of orgs defined under "organizations/peers"
    36      orderers:
    37        - orderer.example.com
    38  
    39      # Required. list of peers from participating orgs
    40      peers:
    41        peer0.org1.example.com:
    42          # [Optional]. will this peer be sent transaction proposals for endorsement? The peer must
    43          # have the chaincode installed. The app can also use this property to decide which peers
    44          # to send the chaincode install request. Default: true
    45          endorsingPeer: true
    46  
    47          # [Optional]. will this peer be sent query proposals? The peer must have the chaincode
    48          # installed. The app can also use this property to decide which peers to send the
    49          # chaincode install request. Default: true
    50          chaincodeQuery: true
    51  
    52          # [Optional]. will this peer be sent query proposals that do not require chaincodes, like
    53          # queryBlock(), queryTransaction(), etc. Default: true
    54          ledgerQuery: true
    55  
    56          # [Optional]. will this peer be the target of the SDK's listener registration? All peers can
    57          # produce events but the app typically only needs to connect to one to listen to events.
    58          # Default: true
    59          eventSource: true
    60  
    61        peer0.org2.example.com:
    62          # [Optional]. will this peer be sent transaction proposals for endorsement? The peer must
    63          # have the chaincode installed. The app can also use this property to decide which peers
    64          # to send the chaincode install request. Default: true
    65          endorsingPeer: true
    66  
    67          # [Optional]. will this peer be sent query proposals? The peer must have the chaincode
    68          # installed. The app can also use this property to decide which peers to send the
    69          # chaincode install request. Default: true
    70          chaincodeQuery: true
    71  
    72          # [Optional]. will this peer be sent query proposals that do not require chaincodes, like
    73          # queryBlock(), queryTransaction(), etc. Default: true
    74          ledgerQuery: true
    75  
    76          # [Optional]. will this peer be the target of the SDK's listener registration? All peers can
    77          # produce events but the app typically only needs to connect to one to listen to events.
    78          # Default: true
    79          eventSource: true
    80  
    81  #
    82  # list of participating organizations in this network
    83  #
    84  organizations:
    85    org1:
    86      mspid: Org1MSP
    87  
    88      # This org's MSP store (absolute path or relative to client.cryptoconfig)
    89      cryptoPath:  peerOrganizations/org1.example.com/users/{username}@org1.example.com/msp
    90  
    91      peers:
    92        - peer0.org1.example.com
    93  
    94    # the profile will contain public information about organizations other than the one it belongs to.
    95    # These are necessary information to make transaction lifecycles work, including MSP IDs and
    96    # peers with a public URL to send transaction proposals. The file will not contain private
    97    # information reserved for members of the organization, such as admin key and certificate,
    98    # fabric-ca registrar enroll ID and secret, etc.
    99    org2:
   100      mspid: Org2MSP
   101  
   102      # This org's MSP store (absolute path or relative to client.cryptoconfig)
   103      cryptoPath:  peerOrganizations/org2.example.com/users/{username}@org2.example.com/msp
   104  
   105      peers:
   106        - peer0.org2.example.com
   107  
   108    # Orderer Org name
   109    ordererorg:
   110        # Membership Service Provider ID for this organization
   111        mspID: "OrdererOrg"
   112  
   113        # Needed to load users crypto keys and certs for this org (absolute path or relative to global crypto path, DEV mode)
   114        cryptoPath: ordererOrganizations/example.com/users/{username}@example.com/msp
   115  
   116  
   117  #
   118  # List of orderers to send transaction and channel create/update requests to. For the time
   119  # being only one orderer is needed. If more than one is defined, which one get used by the
   120  # SDK is implementation specific. Consult each SDK's documentation for its handling of orderers.
   121  #
   122  orderers:
   123    local.orderer.example.com:
   124      url: orderer.example.com:7050
   125  
   126      # these are standard properties defined by the gRPC library
   127      # they will be passed in as-is to gRPC client constructor
   128      grpcOptions:
   129        ssl-target-name-override: orderer.example.com
   130        # These parameters should be set in coordination with the keepalive policy on the server,
   131        # as incompatible settings can result in closing of connection.
   132        # When duration of the 'keep-alive-time' is set to 0 or less the keep alive client parameters are disabled
   133        keep-alive-time: 0s
   134        keep-alive-timeout: 20s
   135        keep-alive-permit: false
   136        fail-fast: false
   137        # allow-insecure will be taken into consideration if address has no protocol defined, if true then grpc or else grpcs
   138        allow-insecure: false
   139  
   140      tlsCACerts:
   141        # Certificate location absolute path
   142        path: /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/tlsca/tlsca.example.com-cert.pem
   143  
   144  #
   145  # List of peers to send various requests to, including endorsement, query
   146  # and event listener registration.
   147  #
   148  peers:
   149    peer0.org1.example.com:
   150      # this URL is used to send endorsement and query requests
   151      url: peer0.org1.example.com:7051
   152  
   153      grpcOptions:
   154        ssl-target-name-override: peer0.org1.example.com
   155        # These parameters should be set in coordination with the keepalive policy on the server,
   156        # as incompatible settings can result in closing of connection.
   157        # When duration of the 'keep-alive-time' is set to 0 or less the keep alive client parameters are disabled
   158        keep-alive-time: 0s
   159        keep-alive-timeout: 20s
   160        keep-alive-permit: false
   161        fail-fast: false
   162        # allow-insecure will be taken into consideration if address has no protocol defined, if true then grpc or else grpcs
   163        allow-insecure: false
   164  
   165      tlsCACerts:
   166        # Certificate location absolute path
   167        path: /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/tlsca/tlsca.org1.example.com-cert.pem
   168  
   169    peer0.org2.example.com:
   170      url: peer0.org2.example.com:7051
   171      grpcOptions:
   172        ssl-target-name-override: peer0.org2.example.com
   173        # These parameters should be set in coordination with the keepalive policy on the server,
   174        # as incompatible settings can result in closing of connection.
   175        # When duration of the 'keep-alive-time' is set to 0 or less the keep alive client parameters are disabled
   176        keep-alive-time: 0s
   177        keep-alive-timeout: 20s
   178        keep-alive-permit: false
   179        fail-fast: false
   180        # allow-insecure will be taken into consideration if address has no protocol defined, if true then grpc or else grpcs
   181        allow-insecure: false
   182  
   183      tlsCACerts:
   184        path: /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/tlsca/tlsca.org2.example.com-cert.pem