Skip to content
GitLab
  1. 28 Feb, 2019 1 commit
    • Gari Singh's avatar
      Allow statically configured root CAs for TLS · 86f1c990
      Gari Singh authored 
      

When peers communicate with other peers or
orderers, the list of trusted CAs for TLS
communication is derived from the channel
configs.  For the peer, the list is the
aggregate of all roots across all channels.
For the orderer, the list is per channel.

This CR adds the option to specify a static
list of CAs via peer.tls.serverRootCAs.files
in core.yaml and a flag
peer.deliveryclient.staticRootsEnabled for the
deliveryclient to use.

Note:  the properties are intentionally not
being added to the sample config because they
should not be used in most situations.

Fixes FAB-14420

Change-Id: Ic381dc99bbb6dc5f7ceafd93738b34c5e24fe60c
Signed-off-by: default avatarGari Singh <gari.r.singh@gmail.com>
      86f1c990
  3. 15 Jan, 2019 1 commit
  5. 12 Jan, 2019 1 commit
    • muralisr's avatar
      add endorser metrics · 26aca2e3
      muralisr authored 
      

This CR adds endorser metrics
   - #proposals received
   - #successful proposals
   - #proposals that failed validation
   - #proposals that failed due to tx dup.
   - #proposals that failed due to endorsement
      failures
   - #proposals that failed chaincode instantiations
   - #duration of successful proposals

Metrics from other parts in the stack such as chaincode are left
to those components.

FAB-13088 #done

Change-Id: I16a472540b2cd6e31c93d89cce9b5e69940d2db4
Signed-off-by: default avatarmuralisr <srinivasan.muralidharan99@gmail.com>
Signed-off-by: default avatarMatthew Sykes <sykesmat@us.ibm.com>
(cherry picked from commit 2d2cd3366bf7693e5e7545682fe1e55ed913512f)
      26aca2e3
  7. 09 Jan, 2019 2 commits
  9. 18 Dec, 2018 1 commit
  11. 07 Dec, 2018 1 commit
  13. 30 Nov, 2018 2 commits
  15. 29 Nov, 2018 1 commit
  17. 27 Nov, 2018 1 commit
  19. 21 Nov, 2018 2 commits
  21. 20 Nov, 2018 1 commit
  23. 19 Nov, 2018 1 commit
  25. 16 Nov, 2018 3 commits
  27. 14 Nov, 2018 1 commit
  29. 09 Nov, 2018 1 commit
    • Matthew Sykes's avatar
      Instantiate and wire metrics provider · 7c7f9458
      Matthew Sykes authored 
      

This introduces the configuration for metrics in the peer, initializes
the metrics provider, wires grpc interceptors for metrics and logging,
and establishes basic integration tests to ensure some metrics are
exported by the peer.

FAB-12713 #done
FAB-12711 #done

Change-Id: I47f44df4e11e3aeaaf401cb6a200bd4161a6e4db
Signed-off-by: default avatarMatthew Sykes <sykesmat@us.ibm.com>
      7c7f9458
  31. 30 Oct, 2018 1 commit
  33. 25 Oct, 2018 1 commit
  35. 19 Oct, 2018 1 commit
  37. 14 Oct, 2018 1 commit
  39. 28 Sep, 2018 1 commit
  41. 26 Sep, 2018 2 commits
  43. 05 Sep, 2018 1 commit
  45. 04 Sep, 2018 1 commit
  47. 29 Aug, 2018 1 commit
    • Baohua Yang's avatar
      [FAB-11536] Improve chaincode service start · d8a9a099
      Baohua Yang authored 
      

This patchset cleans up the peer start process by moving the chaincode
service separately in a single method.

There will be several following-up patchsets to improve the entire start
process of the peer node.

FAB-11536 #done

Change-Id: I7d3eccd3dcdf3835fc02ca4ab2ac1ba9a84dca5f
Signed-off-by: default avatarBaohua Yang <yangbaohua@gmail.com>
      d8a9a099
  49. 27 Aug, 2018 1 commit
  51. 24 Aug, 2018 3 commits
    • Matthew Sykes's avatar
      [FAB-9131] wire zap based fabric logger · 97215fa6
      Matthew Sykes authored 
      

Replace go-logging with a zap based implementation. The implementation
is mostly compatible with the legacy format but differs in a two key
ways:

1. CRITICAL and NOTICE log levels no longer exist. Calls to Critical get
   mapped to error and NOTICE gets mapped to INFO. The methods
   associated with these levels will be removed in a future CR.
2. The log level constants are now sourced from the zap/zapcore packages.
   These values are incompatible wit the go-logging constants. Please be
   sure to use the appropriate constant when necessary.

The existing go-logging package is still used by the chaincode shim to
reduce the risk of negatively impacting legacy chaincode.

Change-Id: Iaf5fac807244883a8285892ccd350c5256959782
Signed-off-by: default avatarMatthew Sykes <sykesmat@us.ibm.com>
      97215fa6
    • manish's avatar
      Ledger-lscc: Implement 'DeployedChaincodeInfoProvider' · aec2ab98
      manish authored 
      

This CR implements interface 'DeployedChaincodeInfoProvider'
based on the current logic of how lscc maintains
chaincode and collection configuration information

FAB-11563 #done

Change-Id: I2ca75040e3c219b353c3140d2f326e9bc74898e6
Signed-off-by: default avatarmanish <manish.sethi@gmail.com>
      aec2ab98
    • manish's avatar
      Ledger-lscc: Interface for decoupling ledger and lscc · 3d3b4a77
      manish authored 
      

This CR
- Introduces an interface 'DeployedChaincodeInfoProvider'
for decoupling the ledger code from chaincode lifecycle code

- Declares ledger's dependency on this interface explicitly.
The intent is that ledger code will use this dependency for
listening to chaincode lifecycle events and for querying
the information about the deployed chaicodes

- Introduces a convenient function in legder that other modules
can use directly to get information about the chaincodes

FAB-11562 #done

Change-Id: I3eb0e798f00ceb18203128fd9da93822fc2bca2b
Signed-off-by: default avatarmanish <manish.sethi@gmail.com>
      3d3b4a77
  53. 20 Aug, 2018 1 commit
    • Baohua Yang's avatar
      [FAB-11571] Improve peer gossip init · 85803818
      Baohua Yang authored 
      

This patchset cleans up the peer start process by moving the gossip
service init process separately in a single method.

There will be several following-up patchsets to improve the entire start
process of the peer node. Keep each change small and focused.

Change-Id: Id59ba860e140f354991b3874c140993c39a190cb
Signed-off-by: default avatarBaohua Yang <yangbaohua@gmail.com>
      85803818
  55. 16 Aug, 2018 1 commit
  57. 15 Aug, 2018 1 commit
    • Will Lahti's avatar
      FAB-11211 Utilize old and new cc pkg in cclifecycle · 3aa60096
      Will Lahti authored 
      

This CR enables the cclifecycle to utilize both the old
ChaincodeDeploymentSpec package as well as the new
ChaincodeInstallPackage by adding a function to list
installed chaincodes to the persistence package provider.
It first searches both the persistence store as well
as the ccprovider.

FAB-11211 #done

Change-Id: I7869f0fa10f884daec1adb5616e2cd11edfb07d9
Signed-off-by: default avatarWill Lahti <wtlahti@us.ibm.com>
      3aa60096
  59. 31 Jul, 2018 1 commit
    • Will Lahti's avatar
      FAB-11201 shim pkg. provider to support both cc pkgs · 679a32e0
      Will Lahti authored 
      

This CR adds a new shim package provider which retrieves the
code package for a given chaincode name/version and updates
the peer to use it at startup. It first searches for a
ChaincodeInstallPackage with the given name/version and falls
back to searching for a ChaincodeDeploymentSpec.

FAB-11201 #done

Change-Id: I064dc2b364a1c8e1280ec1f2b3ffc21c8b3e2e96
Signed-off-by: default avatarWill Lahti <wtlahti@us.ibm.com>
      679a32e0
  61. 26 Jul, 2018 1 commit
  63. 16 Jul, 2018 1 commit
    • Jason Yellick's avatar
      FAB-11038 Disable chaincode lookup cache swizzling · 5ac11d22
      Jason Yellick authored 
      

Per comments left in the ccprovider package, the chaincode cache was
always intended to be on by default (in fact, in production, it is
always enabled).  However, the option to toggle it on and off was
preserved for some poorly written tests.  Since there seem to be no
tests which fail when the cache is enabled, removing this option
entirely.

Change-Id: Id2a74c538e9e3c72b2bafd9bb324792da2040bb4
Signed-off-by: default avatarJason Yellick <jyellick@us.ibm.com>
      5ac11d22