Add a new fabric connector to utilise the new peer gateway api

[davidkel]

Please share the technical limitation of Caliper that you encountered.

Hyperledger fabric has introduced a new client api for applications. This new client api uses a new service in peers tp perform the work of handling transaction lifecycle and querying reducing the overhead of the client and centralising the logic that is common across all the client sdks.
This api is the new standard api released in 2.4 and will be part of an LTS release soon. The other SDKs will remain but any further enhancements to the application api space are likely to be within the new standard rather than the legacy apis and so caliper should embrace the new programming model going forward

Please detail your feature idea that could alleviate the limitation.

We should implement a new fabric connector to take advantage of this new api., it will be similar to the current connectors in both implementation and the network configuration

Please share some details about your use case if possible, and how the new feature would make Caliper a better performance benchmarking framework.

Caliper needs to keep up with the changes within fabric to stay relevant

Please share any suggestions about the new feature's code/configuration API (using formatted YAML segments or pseudo-code).

• the new connector will be selected when a user binds to fabric:2.4
• the new connector will support the following network configuration

caliper:
  blockchain: fabric

organizations:
  - mspid: Org1MSP
    identities:
      certificates:
      - name: 'User1'
        clientPrivateKey:
          path: '../fabric-samples/test-network/organizations/peerOrganizations/org1.example.com/users/[email protected]/msp/keystore/priv_sk'
        clientSignedCert:
          path: '../fabric-samples/test-network/organizations/peerOrganizations/org1.example.com/users/[email protected]/msp/signcerts/[email protected]'
    connectionprofile:
      path: './Org2ConnectionProfile.json'

note that there is no discover option on the connection profile. If it is specified, as with the current 2.0.0 specification of the fabric network config it will be ignored.

Although a connection profile can contain multiple peers, only the first one found in the connection profile should be used.

[davidkel]

There are some enhancements to this connector that can be done but will be part of another further feature requests

• support endorse and commit sub timings
• mutual tls support
• gateway peer load balancing

[aklenik]

@davidkel Updating the network config version number is a good idea. We should also make this explicit in the docs, and the Fabric connectors should inspect this version, and output appropriate error messages in case of a mismatch.

[davidkel]

For this issue we won't be adding in this support

peers:
      -   endpoint: host:port
        tlsCACerts:
          pem: |
            pem-data
          path: ....
        grpcOptions:
          ssl-target-name-override: peer0.org.example.com
          hostnameOverride: peer0.org.example.com

This will be moved to a new issue

[fraVlaca]

Add new connector version to caliper repo:

Create new folder peer-gateway on the connector-versions folder with

• WalletFacade.js and WalletFacadeFactory.js implementation+ unit tests Add new connector Wallet facade and Wallet facade Fatory on the peer-gateway folder #1227
• ConnectionProfileDefinition.js update + unit tests (required to provide required information stored in a connection profile, needed by the connector) PeerGateway connector: Added new methods in the ConnectionProfileDefinition #1253
• PeerGateway.js implementation + unit tests (The connector implementation itself) Fabric Gateway connector implementation: PeerGateway.js implementation + unit tests #1270
• FabricConnectorFactory.js update + unit tests + config.yaml (required to be able to select a 2.4 SUT and then selecting the new connector)
• add integration tests

Documentation will be covered in 3 separate issues
#1284, #1256 and #1299

[davidkel]

the minimal connector implementation is now complete